I see this new cgminer reads them as bbf, does it give some better performance than 3.5.0?
I believe it was the latest firmware that would show them as BBF instead of BTB To recognize the boards as BBF, you need both the BBF firmware and a recent cgminer - either 3.6.0+ or the someone42 fork. (I think the official cgminer is the preferred solution now - should be no reason to use someone42's fork now his changes have been merged back into the official cgminer unless you have problems with 3.6. ETA: Aparently 3.6 isn't quite stable on Windows or OSX yet) roy |
|
|
|
Edit: what is the max safe temp? 55? 60?
My boards run at around 58C give or take a degree or two. The default setting in cgminer's Avalon driver (which is used to drive all Bitburner boards, including the Fury boards) is to shut down the boards if the stack reaches 60C - but you can adjust this with --avalon-cutoff. I set this to 62C on my boards because I was worried about accidental shutdowns - particularly because in my tests I was hitting a bug where the boards didn't auto-restart after they cooled down and I had to restart cgminer to get them hashing again (but that may be fixed in newer firmware and/or newer cgminer - dunno.) No idea how safe those temps are though....not seen any official discussion of temperatures.... or actually any discussion of temperatures.... roy |
|
|
|
BUT: Be aware, the numbers you are used to putting in for --bitburner-voltage are not true voltages; they are Avalon-compatible voltages that are 300mV higher than what the boards really run at. (Bitfury chips run at 900mV compared to Avalon chips which run at 1200mV).
So if you're used to saying, for example "--bitburner-voltage 1350" to overvolt your Bitburner Fury boards with the old firmware then with BBF firmware you will need to use "--bitburner-fury-voltage 1050" to achieve the same effect - both cause the board to run at 1050mV. Fortunately I think cgminer will reject "--bitburner-fury-voltage 1350", and even if it didn't the boards are incapable of complying - which is just as well, because if you really put 1350mV through the Bitfury chips that would pretty much certainly fry them.
But still, be careful with your voltages!
roy
Finally some good information. I used 1300mV, but in cgminer i see ~1060mV. Shouldn't it be 1000mV? Edit: what is the max safe temp? 55? 60? Right... the original firmware (which most of us are running) simulates an Avalon-based board..... so you ask for 1300mV and get (approx) 1000mV I guess there is some variation.... my boards tend to report about 25-30mV above what you'd expect.... I'm still running the BTB firmware so I set "--bitburner-voltage 1350" to select 1050mv, but cgminer shows the voltage varying between about 1075mV and 1080mV. The discrepancy you see is more than I do - but ultimately the voltages we are talking about are pretty small and some level of variation is to be expected, I guess.... roy ETA: There are presumably two separate circuits in there: one that sets the voltage, and one that measures the voltage. Neither of them will be perfect, so the voltage that the chips will actually run at will not be exactly the voltage you ask for. And then the voltage that is measured will not be exactly the voltage that the chips are running at. It's the nature of the world - most all measurements are imperfect. So it's unsurprising that the voltage measured isn't exactly the voltage set. And the voltage the chips are running at? Difficult to say, exactly... As I said, measuring things accurately is hard... |
|
|
|
Just a reminder to everyone - because I know lots of people don't have time to read every post in this thread: The BBF firmware - recomended (by me, at least, if not necessarily by anyone else LOL) means that if you are overvolting your Bitburner Fury boards you need to use --bitburner-fury-voltage rather than --bitburner-voltage BUT: Be aware, the numbers you are used to putting in for --bitburner-voltage are not true voltages in the case of Fury boards; they are Avalon-compatible voltages that are 300mV higher than what the boards really run at. (Bitfury chips run at 900mV compared to Avalon chips which run at 1200mV). So if you're used to saying, for example "--bitburner-voltage 1350" to overvolt your Bitburner Fury boards with the old firmware then with BBF firmware you will need to use "--bitburner-fury-voltage 1050" to achieve the same effect - both cause the board to run at 1050mV. Fortunately I think cgminer will reject "--bitburner-fury-voltage 1350", and even if it didn't the boards are incapable of complying - which is just as well, because if you really put 1350mV through the Bitfury chips that would pretty much certainly fry them. But still, be careful with your voltages! roy |
|
|
|
|
BTW, someone42, I have a problem whereby if cgminer idles the board due to reaching avalon-cutoff temperature, something about the way cgminer idles the board causes it to lose communcation with the board until cgminer is restarted. Easily reproducible in my setup by setting avalon-cutoff to a low value..... But I'm not running latest firmware, so don't worry too much... Will attempt to repro again after I've flashed, and report back.
roy
|
|
|
|
I don't care
I know the parameters - I asked whether anyone cared. It appears you don't :-) |
|
|
|
There is more than 2 parameters for the avalon driver... How do you do if you want different fan speeds and so on ? So you should duplicate every parameter with 'bitfury' and make a 2 in 1 driver  Or create a new BBF (avalon base) driver ...  Are there other parameters many people really care about? roy |
|
|
|
[I think somebody mentioned in an earlier post that the fan control on the boards is a bit conservative and the fans on these things run pretty slow most of the time. My experience is that it's definitely worth plugging the fan directly into a 12V supply (using a molex adaptor etc.) It's a bit noisier, but my board temp went down by nearly 10 oC and so far its been stable like this - fingers crossed it stays this way! Is there any chance that the "usb_write error on avalon_write" error is related to one of the components overheating?
I assumed the fan is controlled by cgminer, like on the real Avalon rigs. So if you want the fan to run faster, either set the target temperature lower (e.g. --avalon-temp 40) - but note that it will take longer to cool down again to the target temperature if the unit shuts down due to overheat. Or alternatively just force the fan to full speed (i.e. --avalon-fan 100) roy ETA: Or perhaps it was just my imagination that these made any difference.... and it is all controlled by the firmware? In any case, I'm hashing fine without either of the above options. My boards usually run about 56-58C, so I've increased the shutdown temperature slightly from 60C to 62C to avoid the very occasional accidental shutdown.... Obviously increasing that is risky so you do this at your own risk. |
|
|
|
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 Just to prevent double work  I've also posted the question here: https://bitcointalk.org/index.php?topic=28402.msg3357797#msg3357797Well, when I get my XX boards set up and my Fury boards reflashed then either there'll be something already there I can download - or I'll have the incentive to do the work so I can mine with my XX boards :-) I'll be perfectly happy if someone else works on this, since I'm not giving any guarantees I'll work on this this weekend -roy ETA: But I have to pluck up the courage to do the reflashing - and that means plugging in another USB cable, which is kinda scary from what I've read here |
|
|
|
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 |
|
|
|
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. |
|
|
|
Although, really, this is the thread about the (Avalon-based) Bitburner X/Bitburner XX boards. If you need info about setting up the (Bitfury-based) Bitburner Fury boards you're better off checking out the other thread: https://bitcointalk.org/index.php?topic=294735.0 |
|
|
|
BTB 0: 46C 256 933mV | 365.7G/348.7Gh/s | A:463040 R:6848 HW:49688 WU: 4871.8/m I think your settings are not very good. I have best performens with this options: --avalon-options 115200: XX:10:45:275 --bitburner-voltage 1320 XX = how many chips you use in one stack (128??) Does "d" instead of "45" works? Bitfury Boards have a modified BitburnerXX Avalon Firmware for Bitburner XX: --avalon-options <arg> Set avalon options baud:miners:asic:timeout:freq The first part is the baudrate, always 115200. The next value is the number of miners, this must be the number of boards in cluster multiplied by 2. (?) Then the number of chips, always 10. (? i dont know if bitfury boards need 8 or 10 multiplied by 2, or 16 chips. I will test it soon) 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) Timeout =( 2^32 /( frequency (in Mhz) * 10,000,000) ) * 29.8 ( http://www.burninmining.com/news/) Pretty sure someone42 said the Fury boards ignore the third parameter of avalon-options (usually set to 10). I think he said they ignore the timeout (fourth parameter) too, but I just set it to 'd' to let cgminer calculate the default and don't worry about it. ETA: AIUI the only important parameters in avalon-options for the Fury boards are the second parameter (should equal the number of chips - although apparently had to be twice the number of chips in old versions of cgminer) and the last parameter (clock speed). And of course, the value of bitburner-voltage if you're overvolting. roy |
|
|
|
Does that mean paypal refunds for all orders - for BTC orders too?
Regards
Also, some of us paid by SEPA transfer. roy |
|
|
|
Despite all my efforts the Paypal Account is still locked
AIUI usually once it's frozen, you won't get access to the money for six months. I hope I'm wrong, but.... roy |
|
|
|
What, you're planning to sue burnin for failing to honour the original terms of Bitburner assembly service (which was that the service was not refundable)? He really should have just sent boards without chips to all those who failed to send him chips as agreed.... It saddens me that burnin offers more than he is contractually obliged to offer, and all he gets in return is threats of lawsuits...
roy
How else do I get my 50% back when burnin is not talking to anyone? The way I saw it, the 50% refund was a goodwill gesture on the part of burnin, not something you are contractually entitled to. Anyway, pretty sure burnin posted a while back saying he's lost 20,000 Euros on the Avalon boards so far, and that he has no money to refund right now.... but that he does still intend to refund people.... |
|
|
|
This is really quite amusing now, we can either have 50% of our funds stolen, or accept a device that will likely never give a ROI, and in fact its actually out of stock! haha
Or you can cancel your order, and get your money back (Paypal if you used that). And then either go after Burnin for the rest of your money in a small claims court, or wait a little while and let things settle, and see if burnin sells directly at a lower price. Isn't today the day CryptX loose exclusivity? What, you're planning to sue burnin for failing to honour the original terms of Bitburner assembly service (which was that the service was not refundable)? He really should have just sent boards without chips to all those who failed to send him chips as agreed.... It saddens me that burnin offers more than he is contractually obliged to offer, and all he gets in return is threats of lawsuits... roy |
|
|
|
I use this settings --avalon-options 115200:16:10:d:274 --bitburner-voltage 1270
Hello, Just installed my BB Bitfury I adapted your settings and have also ~48 GHash/s per board. THX for that. Is there any collection of good settings out there? and what about the "10" in the avalon-options? there are 2 rows with "8" chips, so I tested "115200:16:8:d:274" with no difference. Greetings The second 10 is always fix. It means one row of chips. A bitburner x has 1 row and a bitburner xx has 2 rows. But bitburner x and bitburner xx both are counted as 2 x 10 rows. So if you have 6 bitburner x or xx then you use 12:10 which means 12 times 10 chip rows. Its only for delivering the work or so. The Bitfury boards have only 16 chips but nobody knows what settings to use. The third parameter ('10') is ignored by the Fury boards. The second paramater should be 16 per board for the Fury, unless you are running an old version of cgminer, in which case it should be 32 per board. someone42 posted a while back in the Fury thread - I suggest you go look there as this thread is mainly about the Avalon boards. -roy |
|
|
|
I got an email reply from Joeri at cryptx.com and said person indicated you only want the jumpers on the board that is furthest away from the USB connected board (to TERMINATE the CAN-BUS). IOW you only want the J7 and J8 jumpers on the LAST CAN-BUS connected board but not on the others. That person isn't correct. You need terminators at both ends of the CAN bus. From http://www.ni.com/white-paper/9759/en/: For high-speed CAN, both ends of the pair of signal wires (CAN_H and CAN_L) must be terminated. This is because communication flows both ways on the CAN bus. For low-speed/fault-tolerant CAN, each device on the network needs a termination resistor for each data line: R(RTH) for CAN_H and R(RTL) for CAN_L. Unlike the high-speed CAN termination, low-speed CAN requires the termination to be on the transceiver rather than on the cable. The CAN "flavour" in use here is most likely a high-speed CAN, so terminators are needed at both ends. Take note that the jumpers aren't the terminators itself, but they connect an inline resistor, aka. terminator, which are on the boards already. Seconded. burnin has always said you needed terminators at both ends of the CAN-BUS on the Bitburner XX, so I'd be astonished if the Bitburner Fury is any different. In general terminating only one end of a bus makes no sense (although some low speed buses do allow you to fudge it and put both terminations in the same place if the bus is short enough - effectively allowing you to terminate just one end with restistors of half the value). If the people at CryptX are confused that would explain why only one of my two boards shipped with terminators attached. I imagine there must have been some confusion as to what the 'end of the bus' means. To anyone who understands hardware, a bus has two ends. To someone who doesn't, perhaps they think a bus has a beginning and an end :-) |
|
|
|
|
Since no one has mentioned it here, just thought I'd say:
Not tried it myself yet, but the official cgminer 3.6.0 release merges the changes from someone42's fork, so there should be no reason to run a custom cgminer any more.
roy
|
|
|
|
|
Show Posts
