AValon 1246 83T unstable

[Havane]

Hello

Since few days, I have difficulties with my Avalon1246 83T : Hashrate drops, and it reboots often. Problems occur in normal or turbo mode
Previously, It worked without problem.

Here are log and picture.

I could catch a log with SYSTEMSTATU[Work: Out Over Hot, Hash Board: 3 ] error ; but I always see 26° / 66° in the dashboard, not high
https://pastebin.com/uGH0PH9w


It's not an internet provider problem, because just next to it in the same room an other 1246 85T runs perfectly.

Note that fans run at 6500 RPM (whereas on other 1246 85T runs at 3500. Maybe it's ok)




Here a view of minerstat where ou can see it works during hours (days) and then it has problems



Any idea of the problem ?

[1715035661]

1715035661

[1715035661]

1715035661

[1715035661]

1715035661

[1715035661]

1715035661

[1715035661]

1715035661

[BitMaxz]

According to your logs, one of the ASIC chips reach 110c which I guess is the maximum chip temp before the temp protection was activated.

Here are the logs that I'm talking about check the PVT_T0 begin counting on the last 27 to the left

Code:

PVT_T0[ 66 69 77 74 68 69 67 69 72 72 70 66 67 72 76 75 69 69 70 72 75 76 70 68 67 70 73 73 70 67 67 71 74 73 71 67 67 69 73 75 74 70 66 69 74 70 67 67 64 67 68 70 69 65 62 68 68 62 64 64 59 61 58 61 62 62 64 61 60 63 60 63 64 67 66 64 65 64 66 64 61 63 65 82 66 65 61 64 66 64 65 63 64 110 65 67 65 65 64 62 68 66 66 64 61 61 83 66 64 63 63 61 67 62 65 66 59 57 63 64]
PVT_T1[ 61 64 69 67 67 64 62 67 67 73 68 65 65 68 72 76 69 68 67 67 76 72 70 69 65 69 77 72 68 65 65 69 71 70 85 68 65 70 74 73 70 67 65 67 69 71 65 66 63 65 66 69 68 65 60 66 68 63 64 62 59 56 57 59 61 63 62 61 59 59 63 63 64 63 61 61 65 65 61 63 62 62 65 66 64 66 64 63 65 65 64 62 62 62 64 62 67 63 62 65 67 65 62 64 65 62 62 65 64 61 59 62 64 64 64 64 60 60 64 64] 
PVT_T2[ 66 69 70 69 69 70 69 73 73 72 70 64 66 81 72 71 73 119 67 74 73 73 69 69 67 73 74 74 94 67 68 73 72 76 74 67 69 73 74 75 72 69 69 69 73 71 73 68 64 68 70 69 67 67 65 66 68 63 65 64 59 61 59 64 63 59 61 64 64 62 66 66 66 67 65 65 68 69 69 64 63 63 68 67 64 67 62 67 69 68 65 68 104 67 68 66 67 67 65 66 68 66 68 67 79 68 69 64 68 70 68 68 68 66 67 67 79 60 67 68] 
PVT_V0[305 308 309 307 305 305 303 306 304 298 301 297 302 301 301 298 299 297 298 304 301 298 302 301 303 299 299 300 303 301 295 299 301 302 301 303 302 301 301 297 298 299 298 299 298 306 301 302 306 302 298 303 303 307 307 307 307 305 309 312 313 308 306 309 308 310 313 311 312 311 310 307 305 309 306 306 305 303 301 302 301 309 311 323 309 307 309 305 305 308 305 307 305 350 305 303 305 306 307 305 305 305 310 309 307 307 317 303 305 307 305 304 305 306 309 306 307 310 307 312] 
PVT_V1[303 307 304 310 307 305 318 312 312 303 300 298 299 299 300 306 307 309 302 299 296 301 299 300 306 304 298 309 300 298 299 298 294 297 309 297 309 305 306 293 298 297 306 307 307 298 293 294 302 301 299 304 303 301 301 306 306 303 304 313 319 312 310 313 309 312 306 307 306 306 311 313 302 301 311 305 305 307 301 305 307 305 302 309 301 302 304 309 315 313 306 307 303 302 302 307 310 311 309 310 304 302 316 315 315 309 307 313 306 305 307 312 314 307 313 309 304 301 302 303] 
PVT_V2[299 302 302 301 301 303 310 314 315 305 302 303 309 309 298 308 305 345 305 301 301 299 300 301 299 304 296 306 316 300 298 299 294 295 299 297 299 299 306 297 299 305 298 301 295 307 303 301 301 302 298 300 304 305 306 306 314 306 305 310 317 309 307 305 304 305 301 303 301 303 302 304 302 301 303 309 311 309 301 303 302 305 303 303 307 308 311 307 304 305 308 308 336 310 311 309 309 307 311 301 302 307 309 312 326 310 312 314 308 303 305 306 307 304 301 303 312 306 305 307]

I just include voltage because I saw 350 under PVT_V0 of the first chip before the next chip reaches 110 temps. That was your 1st hashboard the 2nd hashboard doesn't show any high temp and the 3rd hashboard it has 104c.

What I guess may be the first hashboard has a bad heatsink bad adhesive or solder on that chip same on the 3rd hashboard. However, would you mind try replacing the PSU I see weird under Vo it shows 0 so it might be your PSU giving a false signal?

[Havane]

What I guess may be the first hashboard has a bad heatsink bad adhesive or solder on that chip same on the 3rd hashboard. However, would you mind try replacing the PSU I see weird under Vo it shows 0 so it might be your PSU giving a false signal?

Thanks for your help. Where do you see "weird under V0" ? As the avalon is still under waranty, with log problem I coul'd ask for a new one

[Havane]

I see high voltage where there is high temp chips. Is it that ?

[BitMaxz]

Thanks for your help. Where do you see "weird under V0" ? As the avalon is still under waranty, with log problem I coul'd ask for a new one

Check your whole logs again you can find it there not on the part that I posted above.
Look for this "Vo[0]" without quotes it shouldn't be 0 as I said above it's just my theory that it could be a PSU. You can also try to flash it first with the latest version since it is still under warranty we couldn't do anything inside your miner it can only void your warranty.

Since your miner is still under warranty why not contact the support and send it back there for replacement or repair?

[Havane]

It's what I have done. They said open it to see if everything is OK 😂

[Havane]

I get the  new firmware "A1246-A3201-Plus-P3600W-New-Temp65_21071301" from canaan.

Same temp problem, and with it, it can't go up to 73 TH in turbo mode


here are the temp from log

[NotFuzzyWarm]

I get the  new firmware "A1246-A3201-Plus-P3600W-New-Temp65_21071301" from canaan.
Same temp problem, and with it, it can't go up to 73 TH in turbo mode
here are the temp from log

1st, it's nice that Canaan is still using temp sensors in each chip
Seeing that table tells me that either those specific chips have faulty sensors or the chips/cores themselves have issues. Either way, assuming the miner is happy running in normal mode that's how I'd run it and not bother with repair because of the time involved.

Query: In normal mode I take it those chips are still reading higher temps than the others but are not in the danger zone?

That said, I'd 1st see what Canaan has to say about it. With the Avalons at least the end user can actually replace bad hash boards themselves if they are comfortable doing it.

[Havane]

After a power on off, it loops and can't mine. It doen't accept temp > 110° on a chip.  
Same problem if y put it outsite where it's 13° C


Will try canaan support by email.



I captured the log just before the crash and after a crash

before crash after 202s, where we have theses max value for temp : MTmax[108 74 111] MTavg[62 59 63]
https://pastebin.com/xNDqrmRG

after crash 206s, where we see "out over hot", and wrong PS value : PS[0 1214 2 0 0 1272]
https://pastebin.com/ZtejwG4x


if someone have the previous firmware (Version 21042001_4ec6bb0_61407fa), i'm interested

[Havane]

Quick news. After contacting canaan by email, they gave me a firmware. And with a command to  auto-tune the frequency and voltage , it works fine at initial hashrate, with still few high temperature, but ignored.

For them, "The temperature is faulty caused by the IC temperature sensor" ,but I "could ignore the issue ,because the actual temperature is almost same with nearby IC temp. "

[NotFuzzyWarm]

Glad to hear it's working now 
Merit given for getting back to us and letting us know your progress 

[mmert]

Quick news. After contacting canaan by email, they gave me a firmware. And with a command to  auto-tune the frequency and voltage , it works fine at initial hashrate, with still few high temperature, but ignored.

For them, "The temperature is faulty caused by the IC temperature sensor" ,but I "could ignore the issue ,because the actual temperature is almost same with nearby IC temp. "

can you please share contact adress of canaan , i have similar problem with my 1246....

[BitMaxz]

i have similar problem with my 1246 85th, could you please share me contact adress of canaan technic service e mail?

You can try to contact them through their email you can find it here https://canaan.io/about

Or you can contact them through their social media accounts check this links below

- https://www.instagram.com/canaantech/
- https://www.facebook.com/Canaansupercomputing/?modal=admin_todo_tour
- https://twitter.com/canaanio

[Holldem1992]

Quick news. After contacting canaan by email, they gave me a firmware. And with a command to  auto-tune the frequency and voltage , it works fine at initial hashrate, with still few high temperature, but ignored.

For them, "The temperature is faulty caused by the IC temperature sensor" ,but I "could ignore the issue ,because the actual temperature is almost same with nearby IC temp. "

Hello! I have the same problem. Can you shared here the answer from canaan with the link and command please?
Thanks

[iamsanjeev]

Quick news. After contacting canaan by email, they gave me a firmware. And with a command to  auto-tune the frequency and voltage , it works fine at initial hashrate, with still few high temperature, but ignored.

For them, "The temperature is faulty caused by the IC temperature sensor" ,but I "could ignore the issue ,because the actual temperature is almost same with nearby IC temp. "

can you send the command for autotuning of chips, my one chip is exceeding 120c mark and voltage is around 338, although miner is working good at 82th stable.

can you share the command line please,
thanks , looking forward for your reply

[HagssFIN]

Quick news. After contacting canaan by email, they gave me a firmware. And with a command to  auto-tune the frequency and voltage , it works fine at initial hashrate, with still few high temperature, but ignored.

For them, "The temperature is faulty caused by the IC temperature sensor" ,but I "could ignore the issue ,because the actual temperature is almost same with nearby IC temp. "

can you send the command for autotuning of chips, my one chip is exceeding 120c mark and voltage is around 338, although miner is working good at 82th stable.

can you share the command line please,
thanks , looking forward for your reply

It can also be bad thermal contact between that particular chip and the heatsink

[BitMaxz]

can you send the command for autotuning of chips, my one chip is exceeding 120c mark and voltage is around 338, although miner is working good at 82th stable.

can you share the command line please,
thanks , looking forward for your reply

Try to refresh the miner's ASIC chips through the FMS tool you can download it from this link below

- https://canaan.io/wp-content/uploads/2020/03/FMS_V2.3.3_Windows.zip

And then look for the aging tab and select any hashboard with high ASIC chip temp.


If it still overheating manually set the fan speed to 100% to test if it can help to cool down those chips

To set the fan speed you must have the FMS tool and then go to diagnostic and put this command below

Code:

[b][{"command":"ascset","parameter":"0,fan-spd,90"}] [/b]

Fan-spd,90 it's a fan speed with 90% you can replace it with 80% or 100% to try if it fixes the issue.

[unicornmangle]

Fan-spd,90 it's a fan speed with 90% you can replace it with 80% or 100% to try if it fixes the issue.

Do you know why an avalon 1166pro fails to start hashing after a firmware flash? The first time i ended up having to order a new control board and it fixed the problem and after a few weeks i flashed it with upgraded firmware that was emailed to me from canaan and now it just boots and says IDLE in the webui it connects to the pool just will not start hashing.

Canaan has been horrible with customer service i dont understand how you can sell a machine at such a high price and just brush off anyone who asks questions. at the very least they could give the tools required for people to diagnose their own machines. canaan told me if i buy a lot of machines i get support and warranty. im not rich and this is truly a hobby for me and i have bled about 15k so far on mining equipment in the last 6 months.

My avalon experience lost controlboard after 3 days(had to order from ebay for $300 canaan wouldn't sell me one), lost a hashboard after 3 weeks, lost whole machine now after 8 weeks. I wrote canaan it was under warranty when they ran the serial number but there was so many steps to get it returned and they wanted me to remove the hashboard and heatsink which i started doing but they put thermal paste all over every part of that board even the slots on the case the board slides into. So many steps as in (let us remote to your machine, disassemble whole hashboard, waybill, give us your company full information(im an individual), ship, insurance, wait time etc)

I even found a broken drillbit that was used to drill the holes in the avalons enclosure stuck in the fins of one of the hashboards. I know it was for this purpose because of the size of the drillbit and it still has 4 or 5 rings of alumnium attached to it.

[BitMaxz]

~snip~

Actually, I don't know why but if you can give us the whole API logs maybe we can see the issue there.

And what pool do you mine? Take note if you are mining on Nicehash ASICboost pool even their non ASICboost pool expect for the abnormal status of your miner you should mine on other pool. Canaan gears are mostly do not support Nicehash pool so I suggest you try other pools like ViaBTC, slushpool or kano or you can try any pool from this https://miningpoolstats.stream/bitcoin

[unicornmangle]

Here is the log I had flashed to this newest firmware that was sent to me from canaan through email as its not listed on their website on the original board that came with this miner and it ended up doing exactly what its doing now. I bought a replacement board and it ran by then around thanksgiving 1 hashboard went out so i ran it with just two hashboards then thought maybe updating the firmware could fix hashboard as the hashboard didnt have any physical signs that something was wrong. After flashing it just says IDLE at the top.

I'm assuming its a firmware problem FMS does not let me roll back the firmware. I have tried all of the top pools so its definitely not a pool problem Im just trying to get this working so i can sell it and recoup what i can. This miner is under warranty but the process is too much for me to do. 3 weeks of usage and a hashboard dies. I realize im a nobody but i can't afford a total loss. any help is appreciated thank you.

Also im curious if in the manuals from canaan it says web ui upgrade will always fail, if this is the case why does it even have the option in the ui?

Here is the pastebin link its easier to read: https://pastebin.com/XERpdQuS

Code:

{'STATUS':[{'STATUS':'S','When':0,'Code':11,'Msg':'Summary','Description':'cgminer 4.11.1'}],'SUMMARY':[{'Elapsed':46,'MHS av':0.00,'MHS 30s':0.00,'MHS 1m':0.00,'MHS 5m':0.00,'MHS 15m':0.00,'Found Blocks':0,'Getworks':5,'Accepted':0,'Rejected':0,'Hardware Errors':0,'Utility':0.00,'Discarded':471647,'Stale':0,'Get Failures':0,'Local Work':4,'Remote Failures':0,'Network Blocks':1,'Total MH':0.0000,'Work Utility':0.00,'Difficulty Accepted':0.00000000,'Difficulty Rejected':0.00000000,'Difficulty Stale':0.00000000,'Best Share':0,'Device Hardware%':0.0000,'Device Rejected%':0.0000,'Pool Rejected%':0.0000,'Pool Stale%':0.0000,'Last getwork':0}
{'STATUS':[{'STATUS':'S','When':0,'Code':70,'Msg':'CGMiner stats','Description':'cgminer 4.11.1'}],'STATS':[{'STATS':0,'ID':'AVA100','Elapsed':46,'Calls':0,'Wait':0.000000,'Max':0.000000,'Min':99999999.000000,'MM ID0':'Ver[1246-21022602_4ec6bb0_5f74eeft] DNA[020100000012c7bf] MEMFREE[1216344.0] NETFAIL[0 0 0 0 0 0 0 0] SYSTEMSTATU[Work: In Idle, Hash Board: 2 ] Elapsed[56] BOOTBY[0x04.00000000] LW[0] MH[0 0 0] HW[0] DH[0.000%] Temp[17] TMax[17] TAvg[17] Fan1[4465] Fan2[4411] Fan3[4437] Fan4[4416] FanR[58%] Vo[0] PS[0 1218 1 0 0 1240] PLL0[0 0 0 0] PLL1[0 0 0 0] PLL2[0 0 0 0] GHSspd[0.00] DHspd[0.000%] GHSmm[0.00] GHSavg[0.00] WU[0.00] Freq[0.00] Led[0] MGHS[0.00 0.00 0.00] MTmax[-273 -273 -273] MTavg[0 0 0] TA[240] Core[A3201] PING[0] POWS[0] HASHS[0 1 0] POOLS[0] SoftOFF[3] ECHU[1 131073 1] ECMM[1] SF0[300 300 300 300] SF1[300 300 300 300] SF2[300 300 300 300] PVT_T0[-273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273] PVT_T1[-273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273] PVT_T2[-273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273 -273] PVT_V0[0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0] PVT_V1[0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0] PVT_V2[0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0] MW[0 0 0] MW0[0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0] MW1[0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0] MW2[0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0] ASICCRC0[0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0] ASICCRC1[0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0] ASICCRC2[0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0] CRC[0 0 0] POW_I2C[OK] FACOPTS0[] FACOPTS1[] ATAOPTS0[] ATAOPTS1[] ADJ[2] Bar[0%] COP[0 0 0] MPO[3200] MVL[87] ATABD0[0 0 0 0] ATABD1[0 0 0 0] ATABD2[0 0 0 0] WORKMODE[0]','MM Count':1,'Smart Speed':1,'Voltage Level Offset':0,'Nonce Mask':25}