you are a genious lol
it seems to be working
I am running the script on a L3++ now no error, will let you know the outcome

Dont be sor hard on yourself
It works like a charm now
Thanks so so much
send me your BTC adress please for your time and help

The script shows a BTC and LTC address of mine when it finishes or gets aborted (CTRL-C), though it is really not necessary, your patience and help in getting this fixed were greatly appreciated and as you can see the topic now proudly claims "L3+/L3++..." 



Just for curiousity: Did that happen on all your L3++, multiples or just one?

Sounds like the sv binary on the Antminer got corrupted from the power outage, the easiest way to resolve this is by removing the file:

- ssh to the l3++ in question as root
- remove the file with "rmconfig/sv"

Once it is removed (you can check this with "ls -laconfig/") you just run the script again and it will install a fresh copy of it when it finds it missing.

HTH

Any chance you can mod this script to work with the BlissZ firmware?

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}

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

Wohoo, it works! Thanks 

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).

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.

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