Bitburner Fury - Hashrate Protection

[TXSteve]

TXSteve,

In the part that says "115200:32:10:d:277" what's the "d" do?  Also I notice you identify only 32 miners.  If two boards are CAN-BUS connected wouldn't the number of miners be 64 (i.e. 2 * the number of miner chips)?

H@shKraker

D= default and cgminer will calcuculate the proper value

I don't think you multiply by 2, I am using 32 for 2 boards

Steve

[h@shKraker]

It seems I'm up to 60.97 Ghash across two boards.  That *IS* better.  Does it climb-N-normalize over time?

H2shKRaker

[scotjam]

These are my best stable settings for 2 boards with 1 failed USB  --avalon-options 115200:32:10:d:277 --bitburner-voltage 1355 
(change 64 to 32)
I am getting steady 100ghz

btw, I don't see any evidence that the fan varies in speed according temp. It seems to just run slow all the time

Steve

Am I doing something wrong? I have one board and when I run with the above settings I get only about 46-47

When I have been running with  --avalon-options 115200:32:10:47:260 --bitburner-voltage 1300
I get 46 and change, and the device has been rock-solid (no restarts in days).

So I guess the question is: is it worth increasing from 260 -> 277 and increasing the voltage to 1355 for the extra 1-2% performance? Or is there a way to get these up to 50 per board?

Also my fan does seem to go from very slow to slow as the board warms up at the beginning.

scotjam

PS in case there are any n00bs like me using a raspberry pi or other linux-based "embedded" device for this, and sshing in:
(quit cgminer)

Code:

sudo apt-get install screen
screen
./cgminer.sh (or however you start it)

press CTRL+a+d
[disconnect and reconnect freely]

Code:

screen -RD

it's magic!!

[Roy Badami]

TXSteve,

In the part that says "115200:32:10:d:277" what's the "d" do?  Also I notice you identify only 32 miners.  If two boards are CAN-BUS connected wouldn't the number of miners be 64 (i.e. 2 * the number of miner chips)?

H@shKraker

D= default and cgminer will calcuculate the proper value

I don't think you multiply by 2, I am using 32 for 2 boards

Steve

I'm sure it was posted here that you only needed to multiply by 2 if using an old version of cgminer.  There should be no need now AIUI.

[Picmin]

Code:

./cgminer --config <insert pool config file here> --avalon-options 115200:16:10:d:256 --bitburner-voltage 1230

Here's an explanation of the avalon-options parameter:

• 115200: baud rate. Ignored by firmware.
• 16: number of miners. Set this to 16 * number of boards.
• 10: chips per miner. Ignored by firmware.
• d: timeout. Ignored by firmware.
• 256: frequency. This sets the frequency of the external clock. The theoretical hashrate is 11.63 * frequency.

Like with the BitBurner XX boards, --bitburner-voltage controls the core voltage. However, since BitFury is 55 nm instead of Avalon gen1's 110 nm, the actual core voltage will be 300 mV less than what you set here. So "--bitburner-voltage 1230" will set core voltage to 930 mV. (Future versions of the firmware/cgminer will probably use a different identifier to avoid confusion.)

It is normal to get hundreds of HW errors/duplicate work on the first run after power up. This is a firmware bug. It should resolve itself in 30 seconds. If you do want to get accurate measurements of HW errors, run cgminer for 30 seconds, then restart cgminer.

If this is correct we can expect  : 11.63*282*16 = 52474 MH/s (theoretical)
And timing parameter d or 50,47,45 values are ignored by firmware

(Not sure this informations are relevant for the stock firmware)

I get headache trying to tune parameters too.

So far it's seems to be exact and voltage must be tuned to lower HW errors %


I'm running the last cgminer 3.6.2 version on rpi, with --avalon-options 115200:16:10:47:274 --bitburner-voltage 1370

[someone42]

For those with both Avalon and BitFury-based BitBurners, here is some firmware which will cause the BitBurner Fury boards to be recognised as "BBF" in cgminer >= 3.6.0:
https://www.dropbox.com/s/ae86stw2amyntna/bitburner-fury-firmware_1.2.5_BBF.hex.
This update does not fix any bugs or improve the hashrate in any way (over any previously released firmware). All it mainly does is change the USB product string so that cgminer uses a different identifier. Also, if you run "./cgminer -n", the Avalon and BitFury BitBurners should be easily distinguishable due to the new product string.

If using this firmware, note that voltage is now set in cgminer using "--bitburner-fury-voltage" instead of "--bitburner-voltage". "--bitburner-fury-voltage" will set the actual voltage, so there's no need for any 300 mV offset. Also, "--bitburner-fury-voltage" only affects boards which identify as "BBF", and "--bitburner-voltage" will only affect boards which identify as "BTB". This makes it more difficult to accidentally swap voltage settings.

The maximum core voltage for the BitBurner Fury boards is 1100 mV. This is a hard limit; if you really want to increase it, you will need to replace R35 (normally 12 k ohm) with something smaller.

[fydel]

Thanks for the update, someone42.

Do you have any idea what kind of Micro-USB-Port I need in case the orignal port fell off and is fubar?
My local mobil phone repair shop has not the same port in stock. So I checked on eBay but there are very much different kinds of Micro-USBs available.

Would this one fit?
http://www.ebay.de/itm/Micro-Mini-USB-Jack-5P-Female-Socket-buchse-Einbaubuche-connector-5-Pin-phone-3-/321219798980

Edit: removed confusion

[RoadStress]

For those with both Avalon and BitFury-based BitBurners, here is some firmware which will cause the BitBurner Fury boards to be recognised as "BBF" in cgminer >= 3.6.0:
https://www.dropbox.com/s/ae86stw2amyntna/bitburner-fury-firmware_1.2.5_BBF.hex.
This update does not fix any bugs or improve the hashrate in any way (over any previously released firmware). All it mainly does is change the USB product string so that cgminer uses a different identifier. Also, if you run "./cgminer -n", the Avalon and BitFury BitBurners should be easily distinguishable due to the new product string.

If using this firmware, note that voltage is now set in cgminer using "--bitburner-fury-voltage" instead of "--bitburner-voltage". "--bitburner-fury-voltage" will set the actual voltage, so there's no need for any 300 mV offset. Also, "--bitburner-fury-voltage" only affects boards which identify as "BBF", and "--bitburner-voltage" will only affect boards which identify as "BTB". This makes it more difficult to accidentally swap voltage settings.

The maximum core voltage for the BitBurner Fury boards is 1100 mV. This is a hard limit; if you really want to increase it, you will need to replace R35 (normally 12 k ohm) with something smaller.

Thank you very much for this. Could you also please tell me the default voltage and speed of the chip?

[mgio]

Is there a way to recover from the dreaded "usb_write error on avalon_write" error without power cycling the miner?

I'm getting it now and I'm not at home to power cycle it. No matter how many times I reboot my pi or restart cgminer seems to fix it.

[Picmin]

Thanks someone42 

So it's just a cosmetic change ? ... BBF is cool , but i'll try this later 

[solosequenosenada]

https://www.dropbox.com/s/2sehjkytbclyk0o/bbf-cgminer.jpg

cgminer --avalon-options 115200:32:10:46:280 --bitburner-voltage 1360

 

[Japs2013]

Is there a way to recover from the dreaded "usb_write error on avalon_write" error without power cycling the miner?

I'm getting it now and I'm not at home to power cycle it. No matter how many times I reboot my pi or restart cgminer seems to fix it.

+1 fixing this would be great! This already drove me this angry that I've put the device for sale... However, after seeing the bids I don't think I will sell the device

[Picmin]

https://www.dropbox.com/s/2sehjkytbclyk0o/bbf-cgminer.jpg

cgminer --avalon-options 115200:32:10:46:280 --bitburner-voltage 1360

 

Your HW error rate is about 4%  ...


--avalon-options 115200:16:10:d:276 --bitburner-voltage 1360  --> HW  = 3 %  
--avalon-options 115200:16:10:d:274 --bitburner-voltage 1360  --> HW  = 2 %

Quite same effective hashrate for the 3


276 mhz :

Code:

 cgminer version 3.6.3 - Started: [2013-10-17 20:37:46]
--------------------------------------------------------------------------------
 (5s):49.52G (avg):50.94Gh/s | A:8250  R:0  HW:194  WU:710.8/m
 ST: 6  SS: 0  NB: 1  LW: 11744  GF: 0  RF: 0
 Connected to stratum.bitcoin.cz diff 33 with stratum as user xxxx
 Block: 0000025096915921...  Diff:268M  Started: [20:37:46]  Best share: 5.25K
________________________________________________________________________________
 [P]ool management [S]ettings [D]isplay options [Q]uit
 BTB 0: 51C 276 1079mV | 51.56G/51.27Gh/s | A:8316 R: 0 HW:196 WU: 715.8/m
________________________________________________________________________________

 [2013-10-17 20:50:44] Accepted 000e85bc Diff 4.51K/33 BTB 0 pool 0
 [2013-10-17 20:50:46] Accepted 03270438 Diff 81/33 BTB 0 pool 0
 [2013-10-17 20:50:52] Accepted 032aa2e8 Diff 80/33 BTB 0 pool 0
 [2013-10-17 20:50:56] Accepted 06091f8b Diff 42/33 BTB 0 pool 0

Edit : and should be --avalon-options 115200:16:10:xx:yyy  for one board

[solosequenosenada]

https://www.dropbox.com/s/2sehjkytbclyk0o/bbf-cgminer.jpg

cgminer --avalon-options 115200:32:10:46:280 --bitburner-voltage 1360

 

Your HW error rate is about 4%  ...


--avalon-options 115200:32:10:d:276 --bitburner-voltage 1360  --> HW  = 3 %  
--avalon-options 115200:32:10:d:274 --bitburner-voltage 1360  --> HW  = 2 %

Quite same effective hashrate for the 3


276 mhz :

Code:

 cgminer version 3.6.3 - Started: [2013-10-17 20:37:46]
--------------------------------------------------------------------------------
 (5s):49.52G (avg):50.94Gh/s | A:8250  R:0  HW:194  WU:710.8/m
 ST: 6  SS: 0  NB: 1  LW: 11744  GF: 0  RF: 0
 Connected to stratum.bitcoin.cz diff 33 with stratum as user xxxx
 Block: 0000025096915921...  Diff:268M  Started: [20:37:46]  Best share: 5.25K
________________________________________________________________________________
 [P]ool management [S]ettings [D]isplay options [Q]uit
 BTB 0: 51C 276 1079mV | 51.56G/51.27Gh/s | A:8316 R: 0 HW:196 WU: 715.8/m
________________________________________________________________________________

 [2013-10-17 20:50:44] Accepted 000e85bc Diff 4.51K/33 BTB 0 pool 0
 [2013-10-17 20:50:46] Accepted 03270438 Diff 81/33 BTB 0 pool 0
 [2013-10-17 20:50:52] Accepted 032aa2e8 Diff 80/33 BTB 0 pool 0
 [2013-10-17 20:50:56] Accepted 06091f8b Diff 42/33 BTB 0 pool 0

Nice, i will try

[Min€r]

https://www.dropbox.com/s/2sehjkytbclyk0o/bbf-cgminer.jpg

cgminer --avalon-options 115200:32:10:46:280 --bitburner-voltage 1360

 

Have you flashed your boards with new firmware to get this numbers? My 8 boards stack is approx 15 degree hotter than your miner & if I use configs above 1300 the whole thing get ideled (60 degree) with stock firmware what was on the boards. Room has just about 20 so something must be different I think.

[Japs2013]

Would it be possible to make it listen to "--bitburner-fury-options" instead of the --avalon-options parameter? That would make it possible to run both Bitburner XX and Bitburner Fury devices in 1 CGminer window.

[Min€r]

Would it be possible to make it listen to "--bitburner-fury-options" instead of the --avalon-options parameter? That would make it possible to run both Bitburner XX and Bitburner Fury devices in 1 CGminer window.

I think you have to contact Kano or SomeOne42 - should be makeable I think. Just saw there is a new firmware what displays the fury different than the avalon.

[solosequenosenada]

https://www.dropbox.com/s/2sehjkytbclyk0o/bbf-cgminer.jpg

cgminer --avalon-options 115200:32:10:46:280 --bitburner-voltage 1360

 

Have you flashed your boards with new firmware to get this numbers? My 8 boards stack is approx 15 degree hotter than your miner & if I use configs above 1300 the whole thing get ideled (60 degree) with stock firmware what was on the boards.

I dont flash anything, is stock firmware. There is a 120mm fan in top of heatsink.

[mtbitcoin]

Is there a way to recover from the dreaded "usb_write error on avalon_write" error without power cycling the miner?

I'm getting it now and I'm not at home to power cycle it. No matter how many times I reboot my pi or restart cgminer seems to fix it.

+1 fixing this would be great! This already drove me this angry that I've put the device for sale... However, after seeing the bids I don't think I will sell the device

+2 . Would like to upvote this. Running on a PI and then doing a sudo reboot. The only way to get it back is to power cycle the boards

[Roy Badami]

Would it be possible to make it listen to "--bitburner-fury-options" instead of the --avalon-options parameter? That would make it possible to run both Bitburner XX and Bitburner Fury devices in 1 CGminer window.

I think you have to contact Kano or SomeOne42 - should be makeable I think. Just saw there is a new firmware what displays the fury different than the avalon.

I think it should be easy enough.  I was planning to submit a patch to do that but won't have time to work on it until the weekend so if someone else (or even someone42 else ) has time to do it before me...

roy