If the gh-speed doesnt start initially from high value, then miner settles down to lower value. This is strange but perhaps there is some "initial modification" done on cgminer that sets the rate for rest of the session.
Sometimes i have to restart like 10 times to get this "high catch" effect. Its pain to wait in between, because without delay you just get fault 96/97 on vrms. Which means restarting the miner from the page (I dont like to switch off power but had to do that some times)I always wait like at least 45 seconds if vrms have been running for a while to let them cool down.
I've noticed that too, but my unit almost does it every time...if you mess with the spi freq. that can do it i think...cause i just increased mine and it didn't do it anymore...went back to stock and it did it again...
well on 251 with oct. jup...thxs to the graph i was able to finally get the hw error down to .4% and 718-723gh/s on cgminer, bertmod says 700w same as 241, but that was before better cooling fans added...have one board at 240a :O hope it doesn't fry..and also 1 board at 200a but its at 42c
Hopefully pool will report higher hash now that i got the hw % down
i'll know morrow morning
ok 251 is very high for october ? Could you please tell me you spi settings with frequency ? ( screenshot please ?)
yes 251 very high...have 10 fans cooling it and still have have amps...my spi volts are 3.3 and the freq is 201442
after running it all nite...pool reported as high 723gh and cgminer avg settled at 714...thinking about trying the next step up or 261 but idk...amps are pretty high on one board
You are my hero
1) have you changed the settings of the individual die (more volts ?) ?
2) or just general spi ? (in addition to frequency)?
3) How many amps and watts marks every single day? With a cooler master V850 can set the miner to 251 according to you?
Now I have 666 average with 231 setting (3.3 spi and 256 k freq) with october jupiter and 4 45 degrees fans and 1 megaflow
yes i've been tuning individual dies since going on 251...been a struggle but Nil's graph has helped me tremendously...just now got it down to .38% and i hope it says that low..might be lower if i could disable the core that get 160hw errors an hr but oh well
told you my spi settings...tryed your 256k freq and i don't think it helped, but i might start trying diff. volt n freq next as i think i got the die volts locked in almost
3rd...i don't understand this question...but i'm on a 1000w seasonic plat. psu, but you might be able to swing it if you keep the vrms cool enough
Have you tried lowering the spi freq and volt settings with the same OC settings ?
I found that lowering those values, AFTER adjusting the individual die-voltage settings for optimal performance,
resulted in slightly better GH/s performance,better WU, lower HW% and much lower watts!
before spi freq/v change:
OC: 231
spi freq: 201 kHz (default)
spi volt: 1.95 V (default)
Avg. Hash Rate:663 Gh/s WU:9216 HW:2.3% R:1.4%
Watts: +- 755W
after spi freq/v change:
OC: 231
SPI freq: 170666 Hz
SPI volt: 1.80 V
Avg. Hash Rate:677 Gh/s WU:9459 HW:1.6% R:0.8%
Watts: +- 715W
BTW,having the same Gh/s results with 241, 251,..(and counting) with the only difference: more watts per Gh/s