Wow, that sounds great. I guess this means you can put both Bitburner XXs and Furys to the same CAN-bus and control all boards from one cgminer :-?
In principle, yes, since the CAN-bus protocol is also the same. But in practice, you will get HW errors because of how cgminer's Avalon driver is implemented*. Also, frequency settings are broadcast across the CAN-bus and it's unlikely that you would want Avalon and BitFury to run at exactly the same frequency.Maybe in the future, when a well-designed cgminer driver and corresponding firmware is written, you will be able to mix Avalon/BitFury/Cointerra/whatever BitBurner boards.
cgminer doesn't control the voltage of any miner to date. All existing miners (and almost certainly this product as well) operate on a fixed voltage. Changing the voltage requires changing a resistor on the board.
Voltage control for BitBurner boards from within cgminer was added in August (see https://github.com/ckolivas/cgminer/commit/b0f4d55be77adfacc3fd3e1bf0540a0252610455).Thanks someone42, that's just the update we were looking for. This all sounds very positive. So do you have somebody on the team working on the cgminer tweaks, so that we can get hashing as soon as the boards arrive?
See https://github.com/ckolivas/cgminer/pull/499.*cgminer's Avalon driver rotates through an array of work units. Mixing Avalon and BitFury will cause the array rotation to happen too fast for the Avalon boards, causing cgminer to forget about work units and resulting in "no matching work" errors.
. Thanks for putting this straight. So that's potentially a positive thing right, as long as the bitfury burner boards emulate something that is supported by cgminer then we're not too far off? 