Bitminter client (Windows/Linux/Mac)

[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

[DrHaribo]

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

Doesn't sound like something that would make a difference. Oh well, as long as it works I guess.

[SgtSpike]

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

A friend of mine is getting the same error about 3 times a day with the latest mining client.  He only runs two SC Singles.

[DrHaribo]

A friend of mine is getting the same error about 3 times a day with the latest mining client.  He only runs two SC Singles.

The auto rescan isn't finding them I guess because they don't work properly for a while after they come back. It sees a new COM port, probes it, determines there is no mining device. After that it doesn't try again, but the single starts working again a couple minutes later. At least that is what this sounds like.

I think I'll need to put in a new option for the auto rescan to keep retrying all ports not just new ones. It will produce a lot of errors on computers with COM ports that are not for mining. But it seems useful in this case.

[philipma1957]

A friend of mine is getting the same error about 3 times a day with the latest mining client.  He only runs two SC Singles.

The auto rescan isn't finding them I guess because they don't work properly for a while after they come back. It sees a new COM port, probes it, determines there is no mining device. After that it doesn't try again, but the single starts working again a couple minutes later. At least that is what this sounds like.

I think I'll need to put in a new option for the auto rescan to keep retrying all ports not just new ones. It will produce a lot of errors on computers with COM ports that are not for mining. But it seems useful in this case.

doc I got 3 blades today  I only use java and bitminter  will java probe an ethernet jack I know it looks at usb ports and will find asic miner usb sticks pretty well or do I need to use a different client?

I have been reading bfgminer trying to figure out how to setup with bitminter pool.

[DrHaribo]

doc I got 3 blades today  I only use java and bitminter  will java probe an ethernet jack I know it looks at usb ports and will find asic miner usb sticks pretty well or do I need to use a different client?

No, you have to use the built-in mining software. I don't have a blade myself, but tried to write some instructions here, based on info from blade users:

https://bitcointalk.org/index.php?topic=27062.msg3046129#msg3046129

Maybe in the future BitMinter client can work as a stratum proxy, but not yet.