Bitburner Fury - Hashrate Protection

[Roy Badami]

Anyone tried undervolting the chips?

Edit: I can't seem to find the right voltage for 270. I get the same performance as 265 with many voltage settings.

Haven't tried with the latest firmware, but neither undervolting nor underclocking seemed possible when I tried it.  Which is a bit disappointing - I hope the boards will gain this feature as it will extend their usable life significantly.

[Roy Badami]

What voltage do you use for 275? I mine at 265 with 980 and i get 48GH/s per board with very low hw errors.

Oh, maybe I need to experiment a bit more then.  I'm using 1050mV - I'll try your parameters.

It seems mine need more voltage than yours to get the HW error rate down.  I need more than 900mV even at 256MHz.  But you're right, 265 works better than 275 for me, too.  Although I still need around 1050mV to make it work well.

Edit: I can't seem to find the right voltage for 270. I get the same performance as 265 with many voltage settings.

I'm coming to the conclusion that unless you're very lucky, 265 is probably about the limit.  Above that there's no performance increase for me, and it just consumes more power and gives more hw errros.

[Roy Badami]

Another thing is that the second board also got as warm as the first.  If it weren't hashing wouldn't it be noticeably cooler?

H@shKraker

Spending some time tuning my frequency and voltage this evening, I found it's easy to get a board into a bad state by excessive overclocking and/or excessive overvolting (and you're doing both to the extreme).  Once it gets in this state, I see exactly what you do.... the board will not hash (yellow light flashes but no activity on the red light) until it is power-cycled.

I'd suggest that to start with, you don't overclock or overvolt at all.  Use a frequency of 256 and a core voltage of 900mV and see how you get on.  Even that should give you a higher hash rate then you're getting at the moment.

Then, once you've got it stable, gradually increase the frequency.  You might not be able to go much above 265.  Overvolt the minimum necessary to get hardware errors down to an acceptably low level (I have to overvolt even at 256).  Also, I find you need to leave it running for an hour or so to get a realistic picture of what's going on, as the hw error rate starts off high and then drops.

[QuiveringGibbage]

http://imgur.com/a/vurFX#QnaSLTZ

Updated firmware on both units and started mining with cgminer version 3.6.4

Now hashing at ~96GHs



Cheers,
QG

[Tursk]

Instructions for updating boards with broken USB port.

I was successful on my first attempt to update the board using these instructions.

The instructions came from asic-hardware email reply

Required Item: PICkit 3 DV164131 (I was told this version only)

Thanks for the info.

Can you say if DV164131 can be replaced with PG164130, just the PICkit 3 In-circuit debugger/programmer
http://www.microchip.com/stellent/idcplg?IdcService=SS_GET_PAGE&nodeId=1406&dDocName=en538340

Is there some software not included with plain PICkit 3 or why the package with demo board should be used?

Watching the video using PICkit 3 seems very simple, and the programmer itself has 5-pin connector, so no adapters needed.
http://www.youtube.com/watch?v=We4ZZc1l6zk

Power up the board and place the PicKit3 on the 5 pins on the board (you see 5 pins aligned on the board, first pin is the one closest to you, the front-side of the pickKit3 (side with the text ans arrow) should be faced towards the left side of the board (the side where the CAN-BUS is located).

Picture would tell much clearer what 5 pins this means
Is this the secondary CAN-BUS connector, marked J9?

[RoadStress]

http://imgur.com/a/vurFX#QnaSLTZ

Updated firmware on both units and started mining with cgminer version 3.6.4

Now hashing at ~96GHs



Cheers,
QG

You should try running them at 265 with 980-1050mV because you should get the same results with less heat and consumption.

[h@shKraker]

Roy Badami,

Here are my avalon-options options I've been running since last night at 6:00 p.m. Central US time ->

--avalon-options 115200:32:10:d:260 --avalon-fan 100 --bitburner-fury-voltage 1100

With those options I am seeing that both boards are hashing (via all three LEDs blinking) *BUT* I'm getting a whopping 57Ghash for the two board pair (yep ... that's 23.5Ghash per board).  I'll  try the avalon-options and volt options you mention and get back to you with results.

H@shKraker

[RoadStress]

Roy Badami,

Here are my avalon-options options I've been running since last night at 6:00 p.m. Central US time ->

--avalon-options 115200:32:10:d:260 --avalon-fan 100 --bitburner-fury-voltage 1100

With those options I am seeing that both boards are hashing (via all three LEDs blinking) *BUT* I'm getting a whopping 57Ghash for the two board pair (yep ... that's 23.5Ghash per board).  I'll  try the avalon-options and volt options you mention and get back to you with results.

H@shKraker

Wow. Lower your voltage. Try with 950 for 260 freq. The 1100 i think it's the max of the chip and you don't want to stress it so much. If 950 isn't working try with 940 or 960. I found that for 265 the best voltage is between 980 and 1000 depending on the hardware errors.

[h@shKraker]

Yeppers.  Now running with ->

--avalon-options 115200:32:10:d:256 --avalon-fan 100 --bitburner-fury-voltage 900

That has thus far yielded 47.19Ghash (that's roughly 23.6Ghash per board).

H@shKraker

[Roy Badami]

Yeppers.  Now running with ->

--avalon-options 115200:32:10:d:256 --avalon-fan 100 --bitburner-fury-voltage 900

That has thus far yielded 47.19Ghash (that's roughly 23.6Ghash per board).

H@shKraker

Did you power cycle the boards?  Are you getting activity on the red LED on both boards?  If you don't see activity on the red LED then it's not hashing.

roy

[RoadStress]

Yeppers.  Now running with ->

--avalon-options 115200:32:10:d:256 --avalon-fan 100 --bitburner-fury-voltage 900

That has thus far yielded 47.19Ghash (that's roughly 23.6Ghash per board).

H@shKraker

So you get the same results. That's weird. Try with 950 voltage and same speed. Or just try various voltages (increment by 10). Both boards hashing?

[h@shKraker]

Roy Badami,

Yeppers sir, I surely did power cycle them.

RoadStress,

I've take your advice and now I'm running -> --avalon-options 115200:32:10:d:256 --avalon-fan 100 --bitburner-fury-voltage 950 (after another power cycle).  I'll give it an hour and report back my results.

H@shKraker

[h@shKraker]

Adjusting the voltage to 950 has yielded roughly 52Ghash for the pair (26Ghash each).  The settings I'm using now are ->

--avalon-options 115200:32:10:d:256 --avalon-fan 100 --bitburner-fury-voltage 950

Insofar as are both boards hashing I believe they are.  The board that is USB attached has all LEDs feverishly blinking and the second board that is CAN-BUS attached has the green led blinking regularly, then the yellow led blink, blink, blink and then a bit after that the red led blinks feverishly and then back to the green led blinking by itself (lather, rinse, repeat).  I think I got boards with chips from the "special needs" bin.

H@shKraker

[RoadStress]

Adjusting the voltage to 950 has yielded roughly 52Ghash for the pair (26Ghash each).  The settings I'm using now are ->

--avalon-options 115200:32:10:d:256 --avalon-fan 100 --bitburner-fury-voltage 950

Insofar as are both boards hashing I believe they are.  The board that is USB attached has all LEDs feverishly blinking and the second board that is CAN-BUS attached has the green led blinking regularly, then the yellow led blink, blink, blink and then a bit after that the red led blinks feverishly and then back to the green led blinking by itself (lather, rinse, repeat).  I think I got boards with chips from the "special needs" bin.

H@shKraker

Try hashing only with one board and see results. If you have one board that is flashing only the green led then that board isn't hashing.

[Roy Badami]

Adjusting the voltage to 950 has yielded roughly 52Ghash for the pair (26Ghash each).  The settings I'm using now are ->

--avalon-options 115200:32:10:d:256 --avalon-fan 100 --bitburner-fury-voltage 950

Insofar as are both boards hashing I believe they are.  The board that is USB attached has all LEDs feverishly blinking and the second board that is CAN-BUS attached has the green led blinking regularly, then the yellow led blink, blink, blink and then a bit after that the red led blinks feverishly and then back to the green led blinking by itself (lather, rinse, repeat).  I think I got boards with chips from the "special needs" bin.

H@shKraker

You should see a similar patern of blinking lights on both boards.  Sounds like there's either a problem with the second board or a problem with communication between the boards.  Sounds like your first board is exceptionally good (if you say it will go up to 64GH/s) and your second board is not hashing.

roy

[h@shKraker]

Roy,

I thought there was a possibility that the second board isn't hashing as well.  The pair has been producing this same hash rate even when I first received boards and had them both connected via USB.  I wonder if cryptx will replace said board.

H@shKraker

[shep80]

Roy,

I thought there was a possibility that the second board isn't hashing as well.  The pair has been producing this same hash rate even when I first received boards and had them both connected via USB.  I wonder if cryptx will replace said board.

H@shKraker

If you had them both connected via USB, you should see hash rate for each board. Try hooking them up that way and see what you get from cgminer.

[zulover]

Roy Badami,

Yeppers sir, I surely did power cycle them.

RoadStress,

I've take your advice and now I'm running -> --avalon-options 115200:32:10:d:256 --avalon-fan 100 --bitburner-fury-voltage 950 (after another power cycle).  I'll give it an hour and report back my results.

H@shKraker

this is in my script in BAT file, single board has been running for 2 weeks non stop at 49.15ghs stable, doesnt flinch from that rate. i got it to 52 on other settings with overclock but left on this to be safe.


http://stratum.mining.eligius.st:3334 -u <your address> -p  --avalon-options 115200:16:10:d:270 --bitburner-voltage 1330 --disable-gpu

[h@shKraker]

shep80,

I'd f-ing love to do that *BUT* I've been afflicted with the "my mini-USB connector tore off under only the weight of the USB cable" thing on that second board .....

H@shKraker

[RoadStress]

shep80,

I'd f-ing love to do that *BUT* I've been afflicted with the "my mini-USB connector tore off under only the weight of the USB cable" thing on that second board .....

H@shKraker

What firmware do you use? Original?

Edit: Found a better setting. Higher speed, lower voltage, ~good WU. 270 with 970mV.