Bitcoin Forum

Bitcoin => Mining support => Topic started by: FotG on October 31, 2013, 06:02:44 AM



Title: USB block erupters long LED blink
Post by: FotG on October 31, 2013, 06:02:44 AM
I have 7 block erupters and I read that a blink means a share was found. I assume this is the short, less than half a second blink, but all 7 of mine periodically have blink where the LED stays on for 3 seconds. I can't find this mentioned anywhere. What does this mean?


Title: Re: USB block erupters long LED blink
Post by: camolist on October 31, 2013, 06:04:23 AM
i think this is from rejected shares? maybe someone can confirm


Title: Re: USB block erupters long LED blink
Post by: demonmaestro on October 31, 2013, 06:09:18 AM
i think this is from rejected shares? maybe someone can confirm

correct. it happens from time to time. i got over 100 of them and they do the same thing. it happpens.  however if it stays green for a real long time there is other issues,


Title: Re: USB block erupters long LED blink
Post by: FotG on October 31, 2013, 06:10:52 AM
Ok thanks, I guess I get a lot of rejected shares then.


Title: Re: USB block erupters long LED blink
Post by: demonmaestro on October 31, 2013, 06:15:24 AM
Ok thanks, I guess I get a lot of rejected shares then.

if its real often do check your settings. Also make sure all your hardware is compatable with each other.. aka amperage


Title: Re: USB block erupters long LED blink
Post by: FotG on October 31, 2013, 06:44:32 AM
It is quite often. Difficulty is set to 1 on bitparking. I split them between two powered hub, so I'm sure power isn't the issue.


Title: Re: USB block erupters long LED blink
Post by: cxboyminer on October 31, 2013, 07:08:12 AM
i think this is from rejected shares? maybe someone can confirm

My BE's long blick = accepted shares, just like short blinks. I have no idea what is going on, but yeah... hope this helps.


Title: Re: USB block erupters long LED blink
Post by: frankenmint on October 31, 2013, 09:50:40 AM
i think this is from rejected shares? maybe someone can confirm

My BE's long blick = accepted shares, just like short blinks. I have no idea what is going on, but yeah... hope this helps.

No I was under the impression that it was your BE being set to a different timing for a higher difficulty.  I've seen various ones do this long blink in a random sequence as if the timing was adjusted by the mining software.


Title: Re: USB block erupters long LED blink
Post by: FotG on October 31, 2013, 08:28:30 PM
After looking at this closer, I am convinced this is a USB bandwidth issue. I believe the long blink is actually idle time. I can't even copy files from a USB drive when they are running.


Title: Re: USB block erupters long LED blink
Post by: os2sam on October 31, 2013, 10:14:34 PM
Solid green means miner idle.  CGMiner will usually say something about the pool not providing work fast enough.  A 2 or 3 second green is a solid green.


Title: Re: USB block erupters long LED blink
Post by: rpg on November 01, 2013, 01:37:59 AM
After looking at this closer, I am convinced this is a USB bandwidth issue. I believe the long blink is actually idle time. I can't even copy files from a USB drive when they are running.

from my experience that is due to power issues. remove a stick or 2 and see if the problem continues. Also power issues create a ton hardware errors, well over the 1% expected rate. ow many amps is your transformer supplying for how many sticks?


Title: Re: USB block erupters long LED blink
Post by: madcratebuilder on November 02, 2013, 04:13:48 PM
Solid green means miner idle.  CGMiner will usually say something about the pool not providing work fast enough.  A 2 or 3 second green is a solid green.

Bingo!  The bright green for 1-4 seconds is miner waiting for work.  Found share is the short dim blink.


Title: Re: USB block erupters long LED blink
Post by: FotG on November 04, 2013, 10:36:59 PM
I have 7 on an anker 9 port hub providing 5amps, and 2 on another hub providing 3 amps. Using verbose in cgminer I notice the solid green is happening during a libUSB pipe error. 2 of them I just received today, and they do not have the same issue, though they are all REV 3. The two new ones also have less hardware errors.