1 hour is nowhere near enought to come to such a conclusion, unless ofcourse the rate is way off, in which case, evn 10 mins would do.


They are all BM1382's, though the earlier S3's (apparently) have different voltage regulators (and who knows what else!). Cooling wise, you may have a point, though debatable, with the earlier S3's, but not relating to S3+'s. Again, I have to say you did not run them for long enough .... at the very least I'd run it for 4hrs. And the clear jumps you refer to, is that with the 5s or the avg hash-rate? For the 5s I've seen as high as 700Gh/s and as low as 12Gh/s, so it does not really matter, rather the avg rate.

EDIT: Finally, it is not a case of increasing / decreasing the voltage at which the chips run, it is about setting the appropriate voltage for the frequency you are running at. At the very least, you'll notice a decrease in the HW errors as the S3's (and S3+'s) seem to ship with an non-datasheet freq - voltage setting. For other units, you'll also see an improvement in hash-rate but more pertinently, if you are overclocking, then you'll be able to do it at its appropriate voltage and will be in a better position to decide when you've stretched your unit far enough. In my case, I have one unit (an S1 to S3 upgrade) that I am limited by the PSU and datasheet voltage settings as I feel it can be pushed further!

You are welcome, mind though that the pleasure, like custom dictates, is all mine!
PS. Would be nice if you explained how and why you had to update the firmware of your S3 for other users .....

While we are at it, everyone, stop whingeing! Block found at last .... fingers crossed it does not turn out to be stale.

That's that then.

You got a PM.

If anyone still running the new firmware, would you please post here the line used to start cgminer? It "should" be in the System Log (under Status) immediately after starting up (I think that is where I saw it before, but may be wrong!) or even better, if you SSH into the rig open the file /etc/init.d/cgminer with vi editor and scroll down to the line that starts PARAMS= (not #PARAMS=). I think the issue of dropping hash-rate may be due to the setting of auto-voltage / frequency (and the startup line may reveal that!).

I'd hazard to say thats your answer!

Have you got a killawatt and have you measured / monitored? I'd hazard to say thats your answer; but bitmain (or someone else) may have other empirical evidence / knowledge.

Mind what you ask for, else you'll get it!
I'd say not worth it getting bitmain parts (more relevant though not worth for bitmain!). They'll charge you a packet for shipping, as they'd rightly have to, and their prices are ridiculous to say the least.
A replacement S3 controller board, for example, is nothing short of $ 110 plus shipping (or you'll have to make an order for an S3 and they'll ship both together at no extra shipping cost).
At the end of the day, the parts bitmain use, aside from their custom chip, are OEM parts which you can get on the open market.

It does not reset to default so long as you save it once you have set it. I simply do a Save & Apply after setting and do not need to reboot as that action restarts cgminer.

This has probably been asked before, but I can not seem to find it.
I have added a script (to an S3's scheduled tasks) that runs every 6 hours to restart cgminer depending on some condition, however I get the following response when the conditions are met and it tries to restart cgminer:


The critical line that call for the restart is


Do I need to add any options to how I call the script or to the command to restart?

EDIT: OK got this figured out, I changed the PARAMS line in the file /etc/init.d/cgminer to included  --api-allow $_aa and restarted cgminer, and now I get:
Though it seems the UI shows cgminer has stopped, it does not restart, I have to manually restart it. Is there a delay before cgminer restarts and / or can this be set / changed?
[/code]

Is that a new S3+ and / or have you updated the firmware to the November release?
Ther have been several reports of rigs upgraded to the November firmware slowing down, and the symptoms look like the ones yours is displaying.

Pete ...!? You talking to me? High fives all over then, and the pleasure is all mine.
I also noticed that the default voltage setting that bitmain ship with is 0725 but there is no mention of any 5 thousandth in the datasheet, so naturally, I tried it on one of my rigs that I had running at 0750 (aka tried 0755) ...... not bad!

* */2 * * * /etc/init.d/cgminer restart

I can not say definitively that 0725 is the max undervolt setting, but the BM1380 BM1382 datasheet lists 0.7v as the lowest voltage setting; it is possible that you can set it lower (and there is nothing to stop you from trying!).

No such thing as a silly question, simply a question.
Yes, type the voltage setting inside that box and click Save & Apply (cgminer will restart after that and no need to reboot), else if you click Save, the setting will be applied next time you reboot the rig.

That is the lowest voltage mentioned in the BM1382 datasheet (the chips inside S3's), so I'd say you are undervolted to the hilt according to bitmain. I am not sure how low the voltage regulators used will go, but I'd guess you'll need to modify some hardware (caps? / resistors?).
As far as I am aware, there are no recomended ambients as the rig will try its best to cool the chips, thus running the fans faster (and louder!). You could try reducing the frequency, but I doubt you'll maintain the hashrate, more like it will drop, and I am not at all sure that will reduce the temperature either.

Wehey! I like the update to the dashboard .... we can now see the details about the current round.
Any chance of reloading my developer points then?

You are the man!
Yes you are right, it is a timing issue as the timings are for a chain of 32 chips. I'd hazard a guess that if you set it to a fraction of the timing you have for the frequency you are running at, then you'll have less HW errors and a hash-rate improvement.
Once again, YOU are the man and well done for taking one for the rest of us mere mortals!

EDIT: Any chance of photo's of the mod on both boards? That will be super.
Also, (and I am sure you can handle this), but if you want some input on the timings that you can try, could you advise what freq you are running the boards at?

Running at a freq of 262.5 with a voltage setting of 0850 will not be as efficient as running with a voltage setting of 0750, as you'll get more HW errors. At the very worst though (assuming you have an an adequate PSU), you'll be wasting power as the combined wattage is 544W whereas at 0750 it is ~294W. (note the wattage I mention here is theoretical and will actually be more!)

Classically, that is what we have been doing wrong all along, i.e running / overclocking the rigs with different frequencies at the same voltage setting! It should have been setting a voltage for a range of frequencies, but now we are wiser.