Giving out 263 FRC at once? Not bad, I thought it would release only 8-10 FRC...  |
|
|
|
|
Now I also have a problem with one Bitburner Fury out of a stack of 4. It's the only board lacking a Micro USB connector (broken). And its not hashing anymore (It did before). LED is blinking green and yellow, but never red. The other boards are delivering 50Ghs.
As it didn't work at all (tried restarting, power cycling, other order of connecting it to the CAN) I flashed the boards with a Pickit3. My first try with the firmware BitBurnerFury_for_bootloader.hex was not successful, the board didn't blink at all after programming it. In my second try, I used BitBurnerFury_for_production.hex and it worked out. Now the board is blinking again, but still not mining. I know that the other three boards all have BitBurnerFury_for_bootloader.hex.
What could be the problem?
- That the firmware of the board without connector is different?
- How can that be solved?
- Is there other firmware that can be flashed with the Pickit3 than the production firmware?
The first hint leading to solve the problem will be awarded 30$ worth of Bitcoin.
|
|
|
|
Hi dego, here we go, all it took was a full reboot [2013-11-26 22:54:36] Started cgminer 3.5.0
[2013-11-26 22:54:36] BTB0: Reset failed! not an Avalon? (0: c0 2a c3 b6)
[2013-11-26 22:54:37] BTB 0 usb write error: **UNKNOWN**
Could you please post your cgminer.conf? You should find it in ~/.cgminer/cgminer.conf It could be that a certain usb bus is set in your config, so if cgminer starts it checks the bus that is set in your config and it will only find something if it has the same bus number... |
|
|
|
Hi,
I have 8 boads in two stacks, first stack is hashing ok at 197 GHs.
BUT I have to connect it to the upper USB port of my RasPi, otherwise boards are not recognized, cgminer -n says it found no boards.
If I put a usb hub on the upper USB port of my RasPi no board is recognized, even if I connect a single board through its usb connector.
You have 2 stacks of 4 boards, each connected by CAN, right? You have two USB cables running to the Pi, right? What does Raspian or whatever Linux you use say if you type ? |
|
|
|
|
I don't know what the "is not an avalon" message means but it seems to work correctly if it hashes*. Maybe you should delete your cgminer.conf file. Maybe there are old settings in there and also your current settings might be saved in there... maybe thats the reason why changing the *.bat does not work.
I see you use standard values, not overvolted or something. I had around 42 Ghs per board with exactly those values. That would be what you get now. Just play around a bit with frequency and voltage values and I am sure you can get out some Ghs more.
eg, try to use these options on your your BBF ( use this line now and have 201.2 Ghs constantly):
--bitburner-fury-options 115200:128:10:40:282 --bitburner-fury-voltage 1360 --avalon-cutoff 63 --avalon-fan 80 --avalon-temp 55
you could also try these:
115200:128:10:d:280 at 1060
If you do not reach 198Ghs with this, then try to change frequency and voltage in controlled steps, until you find the right settings. just try it out but leave the boards running for at least 50k shares for each try because in the beginning the boards often throw a lot of HW-Errors...
*If you want to find out more here, try to check each board separately, maybe its only one board causing failures...
|
|
|
|
HW-Error Rate is: 3.87
Where can i find this info in cgminer screen? calculate it... (100/accepted shares)*HW |
|
|
|
Just fyi: 4 boards, connected by CANBus: This firmware from asic-shop.com: https://www.dropbox.com/s/tz9xukd4d75g5uq/BitBurnerFury_for_bootloader.hex using this: cgminer --usb 1:7 --disable-gpu --avalon-options 115200:128:10:45:280 --bitburner-voltage 1360 --avalon-cutoff 63 --avalon-fan 80 --avalon-temp 55 HW-Error Rate is: 3.87 might try to tweak further, will keep you posted.. |
|
|
|
|
Ok now wait a while.. during the first minutes the HW rate is usually a bit higher...
If you are not getting close to 100Ghs, then try to reduce frequency in steps of 2 to find better settings. I always mine 100'000 shares before I change settings.
|
|
|
|
|
Ah no, you are still using the wrong voltage command!
you have to use --bitburner-fury-voltage with your firmware
leave the boards connected by CAN bus (not sure if the missing jumpers really matter) and try this line (copy paste!)
--avalon-options 115200:64:10:47:280 --bitburner-fury-voltage 960 --avalon-cutoff 63 --avalon-fan 80 --avalon-temp 55
|
|
|
|
|
If that is tha hasrate of 1 board then it's pretty good....
Maybe you could shut it down, deconnect 1 board and try again to see if its only the mini usb connected board...
|
|
|
|
Not really...  What did you do? - Terminated Can Bus correctly? - command? |
|
|
|
I don't have 100ghs, my avg is 80-85, how can I improve it?  1. Your HW-Error rate is far too high, its above 15%. Should be down to 5% or less. (100/Accepted)*HWErrors=HW Error Rate in percent. 2. You don't have the right number of miners in your line. It is 32 per board, so you should have 64 in your command. 3. You have the Firmware which shows the miners as BBF, so the +300mvolt calculation is not necessary, and the right voltage option for that firmware is --bitburner-fury-voltage (with values form 900 - 1100). Try this line: --avalon-options 115200:64:10:47:280 --bitburner-fury-voltage 960 --avalon-cutoff 63 --avalon-fan 80 --avalon-temp 55 From asic-hardware.com: The first part is the baudrate, always 115200.
The next value is the number of miners, this must be the total number of chips in cluster multiplied by 2 (32 for 16 chips or one board).
Then the number of chips, always 10.
then of CRUCIAL IMPORTANCE the timeout value this is frequency dependent.
at last the clock frequency of the asic chips (this sets the hashing speed)
example timeout values / clock frequencies:
45:282
47:270
50:256 (default) |
|
|
|
dego one question, I have 2 boards and only have two jumpers in one, would I need two more in the other board?
Yes. If you connect 2 or more boards with a CAN-Bus cable you need 4 Jumpers in toto, 2 on the board on top and 2on the board on the bottom. Cryptx was getting that wrong and didn't send enough jumpers. But Burning stated clearly that you had to terminate BOTH ends of the bus. So you are missing two jumpers. If you have some old harddisks or Mobos around, you might find some jumpers there... |
|
|
|
Anyways, I have 8 boards running at 1325 mv (probably could do 1375 and be ok) and 115200:128:10:45:282 for the options settings. They are drawing about 800 watts and get an average of 381 GH/s.
They should make more I think. Please calculate percentage of HW errors. My 4 boards run at 198.5 Ghs currently. With the following line: --avalon-options 115200:128:10:47:280 --bitburner-voltage 1360 --avalon-cutoff 63 --avalon-fan 80 --avalon-temp 55 The produce a HW error rate of 4.84%. If you find settings below 5% they get close to 50Ghs each. Stick with a frequency of 280 and then try different Voltage settings from 1200 to 1400 in steps of 10mvolts and let em run for 100000 shares and calculate, then note Hashrate and HW Error rate. Please note also that if you are running the firmware which shows the miners as BTB, then you have to add 300mvolts to the --bitburner-voltage option (as I did above, my 1360 mvolts are 960mvolts in reality). But if you have the firmware that shows em as BBF, then the +300mvolt is not necessary (My line would be --bitburner-fury-voltage 960). So: If cgminer shows the device as BTB -> try --bitburner-voltage 1360 If cgminer shows the device as BBF -> try --bitburner-fury-voltage 960 |
|
|
|
While moving these guys to upgrade my Saturn yesterday, I heard a crack as I unplugged one of the USB ports with little resistance (Seriously a piss poor job). Now the board doesn't hash at all, the green and yellow lights are blinking right when I CANBUS it to another board, but when I start cgminer, it doesn't blink red anymore and just cycles through yellow and green as if its communicating with the other board but now doesn't work with any of the other boards.
1. Did you terminate the CANBUS correctly? This means that the boards on BOTH ends of the CAN cable need to be terminated by 2 Jumpers each? 2. How many boards are in your stack? 3. What are u using to start cgminer? Please copy&paste the whole line 4. Did you do any firmware upgrades? 5. Did you try to plug mini usb in another board (not the one that might have a defective mini usb)? |
|
|
|
|
I have 4 boards connected by CAN-BUS, running at 196.3Ghs 197.5Ghs with the following line (as bbxx indicated):
--avalon-options 115200:128:10:d:280 --bitburner-voltage 1360 --avalon-cutoff 63 --avalon-fan 80 --avalon-temp 55
--avalon-options 115200:128:10:47:280 --bitburner-voltage 1360 --avalon-cutoff 63 --avalon-fan 80 --avalon-temp 55
So I am happy too. Only weak point is that when I ordered 3 boards lately and a CAN cable to add to the one I already had, cryptx sent me 1 board with a missing miniusb (and a handwritten black cross on it). I know that he did that for people who ordered stacks as the units can be connected by CANBUS, but they can not be updated and of course you won't sell that unit as standalone.
Is there a way to update em by CANBUS? Or is there a second mini usb connector?
Might try to resolder, but the miniusb connector is missing, so I have to see where I can find a similar...
Last night the stack stalled and I have no monitoring/restart scripts in place yet...
|
|
|
|
|
Are you cooling your board properly? Mine sits in a garage where its around 10 degrees and 2 x 12mm fans are working...
And what kind of pool are you mining on?
What kind of psu do you use?
|
|
|
|
|
Show Posts
