Quote from: zefir on June 07, 2012, 06:23:51 AM

Quote from: BFL-Engineer on June 07, 2012, 06:08:45 AM

Quote from: zefir on June 07, 2012, 06:01:42 AM

Quote from: rjk on June 07, 2012, 02:34:11 AM

After 900 accepted shares, my U seems to be a little higher, but I'm going to leave it for a while.

BTW, why does cgminer occasionally (after about 50K shares) stop sending work to the BFL box? It stays running and shows longpolls as they come in, but no shares...

Since when do you observe this? One of my BFLS (running at 872) happened to just quit working two times this week. No indication that communication failed or any other log messages from cgminer. The only thing I noticed is the right LED being off, indicating that device is not hashing. Since restarting cgminer makes it work again, I assume it is only communication that hangs.

Before I updated to cgminer-2.4.2 and played with the different firmwares, the BFLS worked for weeks non-stop. Would be a pity if the FW with the higher clock caused the device idling around two nights Sad

The communication protocol on the unit side is rock-solid. Probably it's the cgminer upgrade that
has caused this. The firmware only affects hashing engine and how they work, and does not affect
the MCU on board which handles communication protocol. Most likely this is due to cgminer change.

Regards,
BF Labs Inc.

Hey, great you are around.

I'll try with previous cgminer if this happened again.

While you are here, could you give a hint whether changing the FTDI baudrate has any effect on the communication (and idle hashing) time as is discussed above? Just to save us from tapping around in the dark. Thanks.

The baud-rate is not used anywhere. It's just a formality.

Regards,
BF Labs Inc.