Bitminter client (Windows/Linux/Mac)

[ewibit]

around every ~2 hours I have BFL LS errors

Code:

2013.08.24 [20:48] FPGA device detected on ttyUSB11: Icarus 
2013.08.24 [20:48] ASIC device detected on ttyUSB6: BitFORCE SC 1.0 
2013.08.24 [20:48] Icarus (ttyUSB10): Tuning timers. 
2013.08.24 [20:48] Icarus (ttyUSB11): Tuning timers. 
2013.08.24 [20:50]  Work rejected. Server says: Stale proof of work 
2013.08.24 [20:51]  Work rejected. Server says: Stale proof of work 
2013.08.24 [21:14]  BitFORCE (ttyUSB6) ERROR: Unexpected response to work results poll command: C5A29 
2013.08.24 [21:14]  BitFORCE (ttyUSB6) ERROR: Unexpected response to queue job pack command: OK 
2013.08.24 [21:14]  BitFORCE (ttyUSB6) ERROR: Unexpected response to work results poll command: OK:QUEUED 4 
2013.08.24 [21:25]  BitFORCE (ttyUSB6) ERROR: Disconnected while working 
2013.08.24 [21:25]  Cannot write to ttyUSB6: device disconnected (output stream gone) 
2013.08.24 [21:25]  Probe of port ttyUSB6 failed: timeout
2013.08.24 [21:26]  Cannot write to ttyUSB6: device disconnected (output stream gone) 
2013.08.24 [21:27]  Cannot write to ttyUSB6: device disconnected (output stream gone) 
2013.08.24 [21:27]  Cannot write to ttyUSB6: device disconnected (output stream gone) 
2013.08.24 [21:27]  Probe of port ttyUSB6 failed: timeout

the Jalapeno and Eruptors are working though
I have tried different USB ports and now BFL LS on a Anker USB 3.0 Hub -> same errors
only resolving is if I kill client and start new
1.4.1Beta2

[1714247957]

1714247957

[1714247957]

1714247957

[1714247957]

1714247957

[1714247957]

1714247957

[DrHaribo]

I have tried different USB ports and now BFL LS on a Anker USB 3.0 Hub -> same errors
only resolving is if I kill client and start new
1.4.1Beta2

Looks pretty much the same as other USB failures. But I don't get why restarting the client fixes it. It closes the port after timing out while probing the port. Are you sure it's not just taking a short break that fixes it?

[ewibit]

perhaps this will tell you something, because you know the difference of the versions:
with v. 1.4.0 the BFL LS does nothing; - only errors

Code:

2013.08.24 [22:30]  BitFORCE (ttyUSB6) ERROR: Unexpected response to work results poll command: 7263D42502FF3564936F793A8A4EFBE44AA37627B96C0B48D117F6F3837EF0C4,F52D848A521917BC19415257,3,0 
2013.08.24 [22:30]  BitFORCE (ttyUSB6) ERROR: Unexpected response to queue job pack command: 7263D42502FF3564936F793A8A4EFBE44AA37627B96C0B48D117F6F3837EF0C4,F52D848A521917BD19415257,2,2,41B5ACB6,7BA5BD9B 
2013.08.24 [22:30]  BitFORCE (ttyUSB6) ERROR: Unexpected response to work results poll command: 7263D42502FF3564936F793A8A4EFBE44AA37627B96C0B48D117F6F3837EF0C4,F52D848A521917BE19415257,5,2,681FBEFD,A6F2A3DC 
2013.08.24 [22:30]  BitFORCE (ttyUSB6) ERROR: Unexpected response to queue job pack command: OK 
2013.08.24 [22:30]  BitFORCE (ttyUSB6) ERROR: Unexpected response to work results poll command: 7263D42502FF3564936F793A8A4EFBE44AA37627B96C0B48D117F6F3837EF0C4,F52D

all other devices are working...

[DrHaribo]

perhaps this will tell you something, because you know the difference of the versions:
with v. 1.4.0 the BFL LS does nothing; - only errors

Yes, the beta has 2 bugfixes to work on BFL ASIC singles and minirigs.

[ewibit]

last night the BFL LS was away again; - in the morning when I came I have done
"probe all ports for external devices"
and BFL LS was here again
therefore it will be a good feature in the menu
Perform scheduled actions
to do "probe all ports for external devices"
~ all 2 hours
TIA

[DrHaribo]

last night the BFL LS was away again; - in the morning when I came I have done
"probe all ports for external devices"
and BFL LS was here again
therefore it will be a good feature in the menu
Perform scheduled actions
to do "probe all ports for external devices"
~ all 2 hours
TIA

Go to "settings" -> "options..." in the menu. On the left side where it says "when new devices connect" make sure you set it to "always start device". This will automatically start mining on devices that are detected. Then go under the "devices" tab in the same window. Make sure "rescan for added/removed devices" is on. Set the rescan interval as you please.

Now it should automatically re-discover any ASICs that disconnect and start mining on them again.

[DrHaribo]

BitMinter client version 1.4.1 is out.

This is just a small bugfix release to make the client run with the new firmware used in BFL ASIC singles and minirigs.

Changes from 1.4.0 to 1.4.1:

• Fix incompatibility with new BFL ASIC firmware

Try it out:


If you have issues with 1.4.1 then you can still get the previous release (1.4.0) at https://bitminter.com/client/1.4.0/bitminter.jnlp

[ewibit]

Go to "settings" -> "options..." in the menu. On the left side where it says "when new devices connect" make sure you set it to "always start device". This will automatically start mining on devices that are detected. Then go under the "devices" tab in the same window. Make sure "rescan for added/removed devices" is on. Set the rescan interval as you please.

Now it should automatically re-discover any ASICs that disconnect and start mining on them again.

thx, exactly so I had it configured (rescan is @default @10s), but last 10h LS was not discovered...

[DrHaribo]

thx, exactly so I had it configured (rescan is @default @10s), but last 10h LS was not discovered...

Yeah, if you have to restart the client for the device to show up again, then I guess it wouldn't help... I'm not sure why that helps for you, I've never seen that before. I'm also not sure why some garbled data is received from the device and then it disappears.

Is it possible for you to try the LS on another computer?

[bt2084]

Ack! Nack!!!

The new version does not automatically pull up my saved username, workername and password.

BitMinter client version 1.4.1 is out.

This is just a small bugfix release to make the client run with the new firmware used in BFL ASIC singles and minirigs.

Changes from 1.4.0 to 1.4.1:

• Fix incompatibility with new BFL ASIC firmware

Try it out:


If you have issues with 1.4.1 then you can still get the previous release (1.4.0) at https://bitminter.com/client/1.4.0/bitminter.jnlp

[DrHaribo]

Ack! Nack!!!

The new version does not automatically pull up my saved username, workername and password.

Ah. It's because I started moving things to HTTPS and clients loaded from different URLs save their settings in different files.

Try this one with HTTP:

[ewibit]

its really strange every ~1-2 hours BFL LS is stopping and

Code:

2013.08.27 [15:02]  Work rejected. Server says: Stale or alien proof of work 
2013.08.27 [15:27]  Work rejected. Server says: Stale proof of work 
2013.08.27 [15:30]  Work rejected. Server says: Stale or alien proof of work 
2013.08.27 [15:30]  Work rejected. Server says: Stale proof of work 
2013.08.27 [15:36]  BitFORCE (ttyUSB7) ERROR: Disconnected while working 
2013.08.27 [15:36]  Cannot write to ttyUSB7: device disconnected (output stream gone) 
2013.08.27 [15:36]  Cannot write to ttyUSB7: device disconnected (output stream gone) 
2013.08.27 [15:36]  Probe of port ttyUSB7 failed: timeout

it stops and is only recovered if I manually probe all ports for external devices
(after a few minutes)

Code:

2013.08.27 [15:40] Device detected on ttyUSB7: BitFORCE SC 1.0

or I restart (stop and make a new instance) BitMinter client
BE and Jalapeno are working further
is there any way to automatically stop and restart BitMinter client every ~1-2 hours?
TIA

[DrHaribo]

it stops and is only recovered if I manually probe all ports for external devices
(after a few minutes)

Sounds like some sort of USB problem. Are you able to test the LS on a different computer to see whether it or something else is the problem?

If it works when you wait a while and try manually, but doesn't work scanning automatically, maybe it will help increasing the delay between automated attempts?

[ewibit]

If it works when you wait a while and try manually, but doesn't work scanning automatically, maybe it will help increasing the delay between automated attempts?

I have changed the delay between automated attempts to 120s, but no recover..

[ewibit]

Code:

2013.08.27 [20:03] Icarus (ttyUSB4): Tuning timers. 
2013.08.27 [20:03] Device detected on ttyUSB6: Icarus 
2013.08.27 [20:03]  Probe of port ttyUSB7 failed: JTermios call returned -1 at class purejavacomm.PureJavaSerialPort line 1115 
2013.08.27 [20:03] Icarus (ttyUSB5): Tuning timers.

[DrHaribo]

I have changed the delay between automated attempts to 120s, but no recover..

Can you try running it on a computer without a bunch of block erupters hooked up? It could be that they are causing the USB instability.

[ewibit]

Can you try running it on a computer without a bunch of block erupters hooked up? It could be that they are causing the USB instability.

ok, will try tomorrow..

[ewibit]

hi DrHaribo

I have located the reason for the error -> it is the bad thermal design of the BFL LS
because it was so noisy I looked and have seen that if I remove one plate of the chassis it is not only less noise, - it runs now without any errors for half a day (before after 2 hours it was tilt..)
 

[DrHaribo]

I have located the reason for the error -> it is the bad thermal design of the BFL LS
because it was so noisy I looked and have seen that if I remove one plate of the chassis it is not only less noise, - it runs now without any errors for half a day (before after 2 hours it was tilt..)
 

Hey, congrats on getting it stable. Did it show a high temperature before? What about now?

[ewibit]

Hey, congrats on getting it stable. Did it show a high temperature before? What about now?

no, temperature was ~62°C, now it is ~59°C