Bitminter client (Windows/Linux/Mac)

[jason60069]

Hi, I'm trying to make my usb asicminer block erupter work with the bitminter client.
I have the silabs drivers installed, and my computer can recognize the miner.
However, the bitminter client returns the error "Probe of port COM3 failed: timeout".
Any ideas on what's wrong?

[DrHaribo]

Hi, I'm trying to make my usb asicminer block erupter work with the bitminter client.
I have the silabs drivers installed, and my computer can recognize the miner.
However, the bitminter client returns the error "Probe of port COM3 failed: timeout".
Any ideas on what's wrong?

Is COM3 where the block erupter stick is? If you go "devices" -> "probe all ports" in the menu without the block erupter plugged in, there is no message about COM3 ?

Is it plugged directly into the computer? Or do you have a USB hub, perhaps with several block erupters connected?

I get the impression that most often the problem is that the block erupter doesn't get enough power. Often because powered USB hubs ship with weak power supplies.

[jason60069]

It is plugged directly into the computer.

Also, when the block erupter is not plugged in, and I probe all ports, I just get the message "Probe failed: No serial ports found."

[MikeMike]

Hi, I'm trying to make my usb asicminer block erupter work with the bitminter client.
I have the silabs drivers installed, and my computer can recognize the miner.
However, the bitminter client returns the error "Probe of port COM3 failed: timeout".
Any ideas on what's wrong?

CTL-ALT -Delete bitminter as it erases any hangups.
Uninstall drivers reboot reinstall drivers plug usb in port restart bitminter few times as well as unplug and replug usb.
That you can do first too.

Mostly underpowered ports....

[jason60069]

Actually, here's what I get now.

https://i.imgur.com/54JAT2G.png

[DrHaribo]

Actually, here's what I get now.

Do you have another computer you could try it on?

[jason60069]

Ok, I'll try it now.

[jason60069]

On a different computer, I still got the same errors...

[DrHaribo]

On a different computer, I still got the same errors...

Can you try bfgminer? There is a link at the frontpage of https://bitminter.com to get it and you can run it from the command line like so:

Code:

bfgminer -o stratum+tcp://mint.bitminter.com:3333 -u user_worker -p password

At this point I would think the erupter stick is broken, but there has been 1 user reporting that bfgminer works for him and not BitMinter client.

[MikeMike]

On a different computer, I still got the same errors...

Can you try bfgminer? There is a link at the frontpage of https://bitminter.com to get it and you can run it from the command line like so:

Code:

bfgminer -o stratum+tcp://mint.bitminter.com:3333 -u user_worker -p password

At this point I would think the erupter stick is broken, but there has been 1 user reporting that bfgminer works for him and not BitMinter client.

IMO-Something to do with the MB controllers etc. with Bitminter.

[ThatFatGuy]

Hi,
I started on the .333 usb sticks, and BitMinter was the only mining program that would work with them on XP, despite successful installs of the other products.

First: each .333 Ghs stick takes 0.5 amps to run.  That means you need a powered hub to run them. I use the DLink powered hub which has 7 slots and 6 amps total, which means one usb slot per power hub has to stay open. 

So my first suggestion to see if it can run at all is to use a powered hub and see if it clears up the mining software issues, because if there is not enough juice to activate hardware, software can malfunction.

Second: start with only one in the hub. 

Third: expect to have to install at least two different sets of drivers until the item is found (But given it doesn't see the stick in the usb, I would say it is underpowered).  I have found success with Silicon Graphics USBXpress_SDK.exe which automatically installs the drivers for you I think I remember.

These were far more successful than the CP210x_VCP_Windows drivers I think.

Hope this helps, and come back as you make progress. Thanks.
Drunken Afficianado

[MikeMike]

Hi,
I started on the .333 usb sticks, and BitMinter was the only mining program that would work with them on XP, despite successful installs of the other products.

First: each .333 Ghs stick takes 0.5 amps to run.  That means you need a powered hub to run them. I use the DLink powered hub which has 7 slots and 6 amps total, which means one usb slot per power hub has to stay open. 

So my first suggestion to see if it can run at all is to use a powered hub and see if it clears up the mining software issues, because if there is not enough juice to activate hardware, software can malfunction.

Second: start with only one in the hub. 

Third: expect to have to install at least two different sets of drivers until the item is found (But given it doesn't see the stick in the usb, I would say it is underpowered).  I have found success with Silicon Graphics USBXpress_SDK.exe which automatically installs the drivers for you I think I remember.

These were far more successful than the CP210x_VCP_Windows drivers I think.

Hope this helps, and come back as you make progress. Thanks.
Drunken Afficianado

Thanks for the info on optional drivers. That should do it.
I just heard yesterday a guy measured the USB's when under heavy hashing and they run up to 1A!

[a2offrb]

I have tried to get client work with BFL LS, downloaded this virtual com port software
but dont know what drivers i should use for BFL device, BitMinter client doesnt found BFL device.
 Currently using CGMiner with WinUsb drivers.

[DrHaribo]

I have tried to get client work with BFL LS, downloaded this virtual com port software
but dont know what drivers i should use for BFL device, BitMinter client doesnt found BFL device.
 Currently using CGMiner with WinUsb drivers.

This driver is used by all mining clients except CGMiner for BFL units:

http://www.ftdichip.com/Drivers/VCP.htm

I don't know if you need to uninstall or disable the winusb stuff for the normal FTDI driver to work. Anyone know?

[ewibit]

upgraded to Ubuntu 13.04 and same problem again with BFL LS that it stops after ~1-2 hours and not starting automatically again (exept for starting BitMinter client manually new)

Code:

2013.09.09 [12:52]  Work rejected. Server says: Stale proof of work 
2013.09.09 [12:54]  BitFORCE (ttyUSB0) ERROR: Unexpected response without command: BitForce SHA256 SC 1.0 
2013.09.09 [12:54]  BitFORCE (ttyUSB0) ERROR: Command timed out. Retries: 0 
2013.09.09 [12:54]  Probe of port /dev/ttyUSB0 failed: timeout

Code:

2013.09.09 [17:11]  BitFORCE (ttyUSB0) ERROR: Unexpected response without command: BitForce SHA256 SC 1.0 
2013.09.09 [17:11]  BitFORCE (ttyUSB0) ERROR: Command timed out. Retries: 0 
2013.09.09 [17:11]  Probe of port /dev/ttyUSB0 failed: timeout 
2013.09.09 [17:13]  BitFORCE (ttyUSB0) ERROR: Unexpected response to work results poll command: BitForce SHA256 SC 1.0 
2013.09.09 [17:13]  BitFORCE (ttyUSB0) ERROR: Unexpected response to temperature check command: INPROCESS:1 
2013.09.09 [17:13]  BitFORCE (ttyUSB0) ERROR: Unexpected response to temperature check command: COUNT:16 
2013.09.09 [17:13]  BitFORCE (ttyUSB0) ERROR: Unexpected response to temperature check command: 283DF32FA7E2E8C4E19BFDFC0E59355142FF2A3B01C658891AD9D0743EEA14A2,B7C23A1A522DE58E1931679C,5,1,6BC1B0FE 
2013.09.09 [17:13]  BitFORCE (ttyUSB0) ERROR: Unexpected response to work queue flush command: 283DF32FA7E2E8C4E19BFDFC0E59355142FF2A3B01C658891AD9D0743EEA14A2,B7C23A1A522DE5981931679C,2,3,1B251CAF,28F291D5,B0A3BE86 
2013.09.09 [17:13]  BitFORCE (ttyUSB0) ERROR: Unexpected response to queue job pack command: 283DF32FA7E2E8C4E19BFDFC0E59355142FF2A3B01C658891AD9D0743EEA14A2,B7C23A1A522DE59D1931679C,0,2,66804588,851B4256 
2013.09.09 [17:13]  BitFORCE (ttyUSB0) ERROR: Unexpected response to queue job pack command: 283DF32FA7E2E8C4E19BFDFC0E59355142FF2A3B01C658891AD9D0743EEA14A2,B7C23A1A522DE59C1931679C,7,0 
2013.09.09 [17:13]  BitFORCE (ttyUSB0) ERROR: Unexpected response to temperature check command: 283DF32FA7E2E8C4E19BFDFC0E59355142FF2A3B01C658891AD9D0743EEA14A2,B7C23A1A522DE5A21931679C,4,0 
2013.09.09 [17:13]  BitFORCE (ttyUSB0) ERROR: Unexpected response to temperature check command: 283DF32FA7E2E8C4E19BFDFC0E59355142FF2A3B01C658891AD9D0743EEA14A2,B7C23A1A522DE5AC1931679C,3,1,E9C671B0 
2013.09.09 [17:13]  BitFORCE (ttyUSB0) ERROR: Command timed out. Retries: 0 
2013.09.09 [17:13]  Probe of port /dev/ttyUSB0 failed: timeout

[DrHaribo]

upgraded to Ubuntu 13.04 and same problem again with BFL LS that it stops after ~1-2 hours and not starting automatically again (exept for starting BitMinter client manually new)

I'll add an option in the next version to rescan the same ports over and over. It will be spammy but I think in your case it can help to re-detect the device after it apparently breaks down for a while and suddenly begins working again.

Is it possible for you to test it on a different computer, does it run the same?

[Trekkie]

Actually, here's what I get now.

https://i.imgur.com/54JAT2G.png

I rebooted my Windows 8 machine running this and two of those miner sticks and got those messages, however shortly after they started mining no issues.

Did you happen to let it sit for a bit after pushing start?

[DrHaribo]

How long after you start the engine is it before the hashing begins?  The GUI shows that it has been running for 38 minutes and no activity.

It should start immediately if name/pass is already entered, otherwise it pops up a window and waits for that.

Did you enter names and password?

Any messages in the log? If not, try turning on verbose logging in the "settings" menu and see if there are any.

[DrHaribo]

Further, at the bottom left it says 'Icarus Com8 started'.

And no error messages about Icarus timing out, or so?

Does it show "Icarus (COM8)" in the device list above the log?

[DrHaribo]

The website stats for my worker shows that I'm hashing, but the GUI speedometer is stuck at zero.  In addition I have a lot of connection messages:

Ah. This is a weird bug I'm trying to track down. Sometimes the hashrate display doesn't update.

If you see the hashrate on the website and you see accepted proofs of work ticking up (yellow boxes in the client), then things are working. I'll hopefully figure out the broken hashrate display in the client soon.

The connect/disconnect messages are normal. The client connects and disconnects to the server on demand.