s19pro fail to read pic temp for chain 0
已回答
Dear Bitmain employee,
After one month of normal operation i'm getting this error:
2021-06-05 05:44:00 _pic_read_iic failed! read_back_data[0] = 0x07, read_back_data[1] = 0x3c, read_back_data[2] = 0x00
2021-06-05 05:44:00 fail to read pic temp for chain 0
2021-06-05 05:44:02 _pic_read_iic failed! read_back_data[0] = 0x07, read_back_data[1] = 0x3c, read_back_data[2] = 0x00
2021-06-05 05:44:02 fail to read pic temp for chain 0
2021-06-05 05:44:04 _pic_read_iic failed! read_back_data[0] = 0x07, read_back_data[1] = 0x3c, read_back_data[2] = 0x00
2021-06-05 05:44:04 fail to read pic temp for chain 0
2021-06-05 05:44:05 _pic_read_iic failed! read_back_data[0] = 0x07, read_back_data[1] = 0x3c, read_back_data[2] = 0x00
2021-06-05 05:44:05 fail to read pic temp for chain 0
2021-06-05 05:44:07 _pic_read_iic failed! read_back_data[0] = 0x07, read_back_data[1] = 0x3c, read_back_data[2] = 0x00
2021-06-05 05:44:07 fail to read pic temp for chain 0
2021-06-05 05:44:11 _pic_read_iic failed! read_back_data[0] = 0x07, read_back_data[1] = 0x3c, read_back_data[2] = 0x00
2021-06-05 05:44:11 fail to read pic temp for chain 0
2021-06-05 05:44:11 _pic_write_iic failed! read_back_data[0] = 0x3b, read_back_data[1] = 0x00
2021-06-05 05:44:11 pic_read_iic: select slave: 0x49, reg/command: 0x00 is failed
2021-06-05 05:44:11 fail to read pic temp for chain 0
2021-06-05 05:44:11 _pic_write_iic failed! read_back_data[0] = 0x3b, read_back_data[1] = 0x00
2021-06-05 05:44:11 pic_read_iic: select slave: 0x4a, reg/command: 0x00 is failed
2021-06-05 05:44:11 fail to read pic temp for chain 0
2021-06-05 05:44:13 _pic_read_iic failed! read_back_data[0] = 0x07, read_back_data[1] = 0x3c, read_back_data[2] = 0x00
2021-06-05 05:44:13 fail to read pic temp for chain 0
2021-06-05 05:44:13 _pic_write_iic failed! read_back_data[0] = 0x3b, read_back_data[1] = 0x00
2021-06-05 05:44:13 pic_read_iic: select slave: 0x49, reg/command: 0x00 is failed
2021-06-05 05:44:13 fail to read pic temp for chain 0
2021-06-05 05:44:13 _pic_write_iic failed! read_back_data[0] = 0x3b, read_back_data[1] = 0x00
2021-06-05 05:44:13 pic_read_iic: select slave: 0x4a, reg/command: 0x00 is failed
2021-06-05 05:44:13 fail to read pic temp for chain 0
2021-06-05 05:44:13 _pic_write_iic failed! read_back_data[0] = 0x3b, read_back_data[1] = 0x00
2021-06-05 05:44:13 pic_read_iic: select slave: 0x4b, reg/command: 0x00 is failed
2021-06-05 05:44:13 fail to read pic temp for chain 0
2021-06-05 05:44:14 _pic_read_iic failed! read_back_data[0] = 0x07, read_back_data[1] = 0x3c, read_back_data[2] = 0x00
2021-06-05 05:44:14 fail to read pic temp for chain 0
2021-06-05 05:44:14 _pic_write_iic failed! read_back_data[0] = 0x3b, read_back_data[1] = 0x00
2021-06-05 05:44:14 pic_read_iic: select slave: 0x49, reg/command: 0x00 is failed
2021-06-05 05:44:14 fail to read pic temp for chain 0
2021-06-05 05:44:14 _pic_write_iic failed! read_back_data[0] = 0x3b, read_back_data[1] = 0x00
2021-06-05 05:44:14 pic_read_iic: select slave: 0x4a, reg/command: 0x00 is failed
2021-06-05 05:44:14 fail to read pic temp for chain 0
2021-06-05 05:44:14 _pic_write_iic failed! read_back_data[0] = 0x3b, read_back_data[1] = 0x00
2021-06-05 05:44:14 pic_read_iic: select slave: 0x4b, reg/command: 0x00 is failed
2021-06-05 05:44:14 fail to read pic temp for chain 0
2021-06-05 05:44:16 _pic_read_iic failed! read_back_data[0] = 0x07, read_back_data[1] = 0x3c, read_back_data[2] = 0x00
2021-06-05 05:44:16 fail to read pic temp for chain 0
2021-06-05 05:44:16 _pic_write_iic failed! read_back_data[0] = 0x3b, read_back_data[1] = 0x00
2021-06-05 05:44:16 pic_read_iic: select slave: 0x49, reg/command: 0x00 is failed
2021-06-05 05:44:16 fail to read pic temp for chain 0
2021-06-05 05:44:16 _pic_write_iic failed! read_back_data[0] = 0x3b, read_back_data[1] = 0x00
2021-06-05 05:44:16 pic_read_iic: select slave: 0x4a, reg/command: 0x00 is failed
2021-06-05 05:44:16 fail to read pic temp for chain 0
2021-06-05 05:44:16 _pic_write_iic failed! read_back_data[0] = 0x3b, read_back_data[1] = 0x00
2021-06-05 05:44:16 pic_read_iic: select slave: 0x4b, reg/command: 0x00 is failed
2021-06-05 05:44:16 fail to read pic temp for chain 0
2021-06-05 05:44:17 over max temp, pcb temp 47 (max 80), chip temp 62(max 95) pcb temp rise 0 chip temp rise 0, total_exit_failure 7
2021-06-05 05:44:17 ERROR_TEMP_TOO_HIGH: over max temp
2021-06-05 05:44:17 stop_mining: over max temp
2021-06-05 05:44:17 uninit_temp_info
2021-06-05 05:44:17 do not read temp anymore...
2021-06-05 05:44:17 cancel thread
2021-06-05 05:44:17 cancel thread
2021-06-05 05:44:17 cancel thread
2021-06-05 05:44:17 ****power off hashboard****
2021-06-05 05:44:19 temp monitor thread exit
2021-06-05 06:01:03 avg rate is lower than ideal rate, 49389.50 in 30 mins
2021-06-05 06:01:03 chain 0 hash rate 0.00 low in 15 mins
2021-06-05 06:01:03 chain 1 hash rate 0.00 low in 15 mins
2021-06-05 06:01:03 chain 2 hash rate 0.00 low in 15 mins
2021-06-05 06:31:03 avg rate is lower than ideal rate, 0.00 in 30 mins
I have tried the following:
- Restart miner several times
- Restore factory setting several times
- Re-install firmware
- Remove power and wait 10 minutes before restart
- Try to run with fan 100
One some occasions the miner is unable to find all hashboards
After restart it finds the boards again but the error will happen again
"fail to read pic temp for chain 0"
Can you advise me how to proceed?
Kind regards,
Cedric
-
正式评论
Dear
there is high temp caused the pic error could you please try the below instructions
1 Unplug the power cord 20 minutes then restart it again,
2 restore the antminer to the factory settings ,
3 change the power supply, plug the cable,
4 upgrade to the latest firmware,
5 clean up the dust for the antminer
6 check the ambient temperature
评论操作 -
Dear
there is high temp caused the pic error could you please try the below instructions
1 Unplug the power cord 20 minutes then restart it again,
2 restore the antminer to the factory settings ,
3 change the power supply, plug the cable,
4 upgrade to the latest firmware,
5 clean up the dust for the antminer
6 check the ambient temperature
-
Thank you I have tried above steps to no avail.
The issue was resolved by sending three S19's with this issue back to Bitmain for repair under warrenty.
Unfortunately two other units have developed the same pic temp error now.
This makes 5 out of 24 of my S19's have developped the same error.
The other 19 s19 units have been running with no problems since april.
-
This is unfortunate. I have tried all these steps Linda and am having the same issue here as Cedric. Is this an issue with the S19 specifically? I am very dissapointed, i do not think my miners have warranty anymore. Cedric, how long did it take for Bitmain to repair? Is it something i can repair myself, e.g. a new temperature sensor perhaps?
-
My importer has requested information on the repairs but had gotten no in depth reply. He suspects corrupted firmware on one of the hashboards cpu’s. If he finds a solution I will be sure to post it here. You can try running the miner with one hashboard attached to find which hashboard is causing the problem. If no luck we might have to wait for a firmware update or if you have no more warranty, custom firmware.
-
Dear
there is high temp caused the pic error could you please try the below instructions
1 Unplug the power cord 20 minutes then restart it again,
2 restore the antminer to the factory settings ,
3 change the power supply, plug the cable,
4 upgrade to the latest firmware,
5 clean up the dust for the antminer
6 check the ambient temperature
-
My importer has found a solution to this problem.
1. Disconnect all hashboards and flash the main board firmware
2. Connect only hashboard 1 and flash the firmware
3. Connect only hashboard 2 and flash the firmware
4. Connect only hashboard 3 and flash the firmware
5. Restart the miner with all hashboards connected.
This has resoved the issue for two of my S19pro 110ths units.
Hopefully it will work for others too -
Hi
I had the same problem with my new S19J Pro.
The Problem has been since the beginning.
restart, SD flash, upgrade, PIC chip new program, nothing helped.
I found the problem myself after 3 weeks.
If you need help with this problem, you can write to me arcrinfo@gmail.com -
Hi, i was having the same issue with a used Antminer purchase a few months ago.
I have tried everything with no success, so with my knowledge in repair electronics i try to check the hashboard for myself.
Situation the IN AIR SENSOR, was dirty. looks like the miner was exposed to humidity and dust causing damaged on the soldering of the TEMP Sensor.
Solution, Replace or resolder the sensor.
In my case i have tested the sensor and the sensor was ok, so i proceed with re-solder it.
The final fix will be purchase a new sensor and replace it.
THIS SITUATION IS COMMON IN USED MACHINES, BECAUSE IN CHINA THEY DON'T TAKE CARE ABOUT THE ENVIRONMENT BEHAVIOR LIKE TEMP AND DUST, AND THE USED MACHINES ARE EXPOSE TO EXTREME SITUATION LIKE HIGH TEMPS, DUST. AND HUMIDITY CAUSING THIS TYPE OF DAMAGES, IF YOU ARE NOT READY TOP FACE THIS TYPE OF ISSUE KEEP AWAY OF USED MACHINES.
this type of damages can be checked on the log, request a copy of the logs to you vendor before purchase any used machine.
i am purchasing a ultrasonic cleaner for clean the hashboards, because the most affected sensor are that one located in the air intake.
Currently my machine is working good, after this FIX. as i know bitmain tech support or other representative like zeusbtc could repair this for you with the related logistics, parts and repair cost.
I live in Panama, central America if anyone need repairs here i will help. netstat.services@gmail.com
请先登录再写评论。
评论
11 条评论