Topic: L3+/L3++ voltage tuning script (Read 3421 times)

Have limit with messages , cant answer in inbox

Hello psycodad,
Have job for you, can contact on email [email protected] discord burth#2357 , telegram: @bonds11

My advice too you: Do it manually. Its really easy and you have the full control over everything. Put in a high number and check the HW errors a hour later. If just a few HW, drop one more step down until you see too many of them. Then go back one step and done.

I came across similar voltage tuner: https://github.com/gotaproblem/L3-AutoTune

Any idea it is working same way?

All credit to cryptodad.

Can someone check advise if it is legit? And can someone advise how I can decode these files to see what are they going to do before I try with the miner?

Thank you

The voltage settings are stored in the EEPROM of the PIC controllers for the blades and are persistent over reboots and power-cycles. That is, even if you re-flash firmware the settings *should* persist (didn't have to try that yet).
Though when you change frequencies (i.e. to adapt to higher or lower ambient temperatures), you should retune again.

psycodad, one more question: does that tuning survive after reboot? or i need to redo the tuning every time after reboot?

psycodad, you have been quoted in the following messages:

 

• Alternate cryptocurrencies - Announcements (Altcoins) - Re: [ANN] New Crypto Currency FRANKO [v0.16][Resurrection]
  
  Quote from: ACGCrypto on November 24, 2018, 05:45:52 AM
  It will most likely be listed on the AltMarket, though I'm not sure whether it'll be in December when A.M.

psycodad, thanks for that, i will try.

Most probably your chain 4 did not report back all chips and therefor the script aborts. Your chain 4 looks like it emits a lot of errors, it might be possible to get that down by increasing voltage further (a setting below 0x50) but from past experience I doubt that.

First check your miners GUI if chain 4 has no crosses. If it has, try rebooting the miner and see if all chips come back to work. If not, try to shut it down and restart it after letting it cool down for 15-20mins.

From there on, I'd recommend to hand-tune chain 4 by ssh'ing to your L3 and running /config/sv manually.
Otherwise you can change the script to use higher voltage by changing line 73 from 0x50 to a lower number (meaning to allow the script to try higher voltages).

Again, I would not recommend this, I have my doubts you'd get much less errors on chain 4 with even higher voltages @450MHz. Try to tune the other three by adding -s 4 to skip chain 4 in tuning and try the best value for chain 4 manually.

HTH

after ~20 mins, it is aborted:

Skipped chain 4, max overvolt reached, tune manually if you dare!!
= Running since: 00:41.21, now sleeping for 40.3s =
| 10.10.11.48  [450] |  49  |  45  |  45  |  46  |
+ Current voltages   + 0x85 + 0xc2 + 0xad + 0x50 +
|Errors/min (5min)   | 0.20 | 0.40 | 0.00 | 6.20 | 1 2 0 31 |
|Errors/min (10min)  | 0.30 | 0.30 | 0.10 | 5.30 | 3 3 1 53 |
|Errors/min (15min)  | 0.33 | 0.33 | 0.13 | 5.00 | 5 5 2 75 |
|Errors/min (all)    | 0.17 | 0.14 | 0.05 | 4.66 | 7 6 2 196 |
= Running since: 00:42.11, now sleeping for 49.9s =
Invalid boards read, aborted!
9 0

Thank you very much, greatly appreciated!
Have a merit for generously supporting open source software development!

I found back the btc adress : 14kfN1siTWYsLxteeDxXJBfk8ZP74u2Pbz
Sent to you
Sorry for the delay
check your pm please

Awesome, thanks for clearing that up for me.

The voltages you yourself (w/ set_voltage) or my tuning tool set are persistent over cold and warm reboots as they are set in the non-volatile memory of the PIC controller on each hashboard.

Thanks for the help. I will give that a try. I'm wondering if there is a way to make the voltage changes persistent.

This means that the voltage tool couldn't read voltage of all 4 blades during this run.
If the error persists over several tries, a cold reboot can cure it normally. I've only seen this on one of my miners that ran for more than 180 days and after a cold boot it went away.

Personally and if possible I recommend a cold boot (switching the miner off for 10-15min and back on).

"= Running since: 00:08.06, now sleeping for 54.7s =
Invalid boards read, aborted!
9 3
"

= Running since: 00:00.06, now sleeping for 54.8s =

Wohoo, it works! Thanks 

Thank you, it seems I ‎unintentionally never followed up on arnold_mad who reported this problem previously and thought it to be fixed. It's just a blind guess that the json output of the Blissz firmware has the same unprintable character at the end as all others have.

Could you do a 'git pull' and try to re-run the script and see if you get any further?

TIA

Failed to decode json reply:
Extra data: line 1 column 1479 - line 1 column 1480 (char 1478 - 1479)

{"STATUS":[{"STATUS":"S","When":1532684339,"Code":70,"Msg":"CGMiner stats","Description":"cgminer 4.10.0"}],"STATS":[{"CGMiner":"4.10.0","Miner":"1.0.1.3","CompileTime":"Sun Jan 14 00:00:57 CST 2018","Type":"Antminer L3+ Blissz v1.02"},{"STATS":0,"ID":"L30","Elapsed":9059,"Calls":0,"Wait":0.000000,"Max":0.000000,"Min":99999999.000000,"GHS 5s":"556.241","GHS av":552.29,"miner_count":4,"frequency":"425","frequency1":425,"frequency2":425,"frequency3":425,"frequency4":425,"volt1":"7","volt2":"7","volt3":"7","volt4":"7","watt1":216,"watt2":216,"watt3":216,"watt4":216,"fan_num":2,"fan1":3114,"fan2":2508,"temp_num":4,"temp1":52,"temp2":53,"temp3":50,"temp4":50,"temp2_1":60,"temp2_2":60,"temp2_3":57,"temp2_4":57,"temp31":0,"temp32":0,"temp33":0,"temp34":0,"temp4_1":0,"temp4_2":0,"temp4_3":0,"temp4_4":0,"temp_max":53,"Device Hardware%":0.0000,"no_matching_work":23,"chain_acn1":72,"chain_acn2":72,"chain_acn3":72,"chain_acn4":72,"chain_acs1":" oooooooo oooooooo oooooooo oooooooo oooooooo oooooooo oooooooo oooooooo oooooooo","chain_acs2":" oooooooo oooooooo oooooooo oooooooo oooooooo oooooooo oooooooo oooooooo oooooooo","chain_acs3":" oooooooo oooooooo oooooooo oooooooo oooooooo oooooooo oooooooo oooooooo oooooooo","chain_acs4":" oooooooo oooooooo oooooooo oooooooo oooooooo oooooooo oooooooo oooooooo oooooooo","chain_hw1":0,"chain_hw2":0,"chain_hw3":0,"chain_hw4":23,"chain_rate1":"139.20","chain_rate2":"139.48","chain_rate3":"138.91","chain_rate4":"138.65"}],"id":1}