Antminer T17 Problems

[tps_star]

HI
I have 2 antminer t17 and this 2 miner have 2 diffrent problem
1: first miner have hashrate but no mining and Priority   Accepted Diff1#   DiffA# show zero
i see in kernel log this error :

Code:

2020-02-15 15:13:54 temperature.c:1072:read_temp_func: PCB low 30, high 45. CHIP low 51, high 70
2020-02-15 15:13:54 pic.c:145:volt_clamp: failed on Chain[0], b[0] = 254, b[2] = 254!
2020-02-15 15:13:56 pic.c:145:volt_clamp: failed on Chain[0], b[0] = 254, b[2] = 254!
2020-02-15 15:13:57 temperature.c:1072:read_temp_func: PCB low 30, high 45. CHIP low 50, high 70
2020-02-15 15:13:58 pic.c:145:volt_clamp: failed on Chain[0], b[0] = 254, b[2] = 254!
2020-02-15 15:13:59 pic.c:145:volt_clamp: failed on Chain[1], b[0] = 254, b[2] = 254!
2020-02-15 15:13:59 temperature.c:1072:read_temp_func: PCB low 30, high 45. CHIP low 50, high 70
2020-02-15 15:14:01 pic.c:145:volt_clamp: failed on Chain[1], b[0] = 254, b[2] = 254!
2020-02-15 15:14:02 temperature.c:1072:read_temp_func: PCB low 30, high 45. CHIP low 50, high 70
2020-02-15 15:14:03 pic.c:145:volt_clamp: failed on Chain[1], b[0] = 254, b[2] = 254!
2020-02-15 15:14:05 temperature.c:1072:read_temp_func: PCB low 30, high 44. CHIP low 50, high 69
2020-02-15 15:14:05 pic.c:145:volt_clamp: failed on Chain[2], b[0] = 254, b[2] = 254!
2020-02-15 15:14:07 pic.c:145:volt_clamp: failed on Chain[2], b[0] = 254, b[2] = 254!
2020-02-15 15:14:07 temperature.c:1072:read_temp_func: PCB low 30, high 44. CHIP low 50, high 69
2020-02-15 15:14:08 pic.c:145:volt_clamp: failed on Chain[2], b[0] = 254, b[2] = 254!
2020-02-15 15:14:10 temperature.c:1072:read_temp_func: PCB low 30, high 44. CHIP low 50, high 69
2020-02-15 15:14:13 temperature.c:1072:read_temp_func: PCB low 29, high 44. CHIP low 50, high 69
2020-02-15 15:14:15 temperature.c:1072:read_temp_func: PCB low 29, high 44. CHIP low 50, high 69

second miner power supply all 3 fan is defective and not working
i changed all 3 fan now fan is working 12v output fan and controller board working but no have hashboard voltage and is 0.3 volt
in kernel log see this error :

Code:

2020-02-15 14:41:38 power_api.c:124:check_voltage_multi: retry time: 28
2020-02-15 14:41:40 power_api.c:86:get_average_voltage: chain[0], voltage is: 1.604238 
2020-02-15 14:41:42 power_api.c:86:get_average_voltage: chain[1], voltage is: 1.530762 
2020-02-15 14:41:42 power_api.c:97:get_average_voltage: aveage voltage is: 1.567500 
2020-02-15 14:41:42 power_api.c:110:check_voltage: target_vol = 17.00, actural_vol = 1.57, more than 0.5v diff.
2020-02-15 14:41:43 power_api.c:124:check_voltage_multi: retry time: 29
2020-02-15 14:41:45 power_api.c:86:get_average_voltage: chain[0], voltage is: 1.475654 
2020-02-15 14:41:48 power_api.c:86:get_average_voltage: chain[1], voltage is: 1.396055 
2020-02-15 14:41:48 power_api.c:97:get_average_voltage: aveage voltage is: 1.435854 
2020-02-15 14:41:48 power_api.c:110:check_voltage: target_vol = 17.00, actural_vol = 1.44, more than 0.5v diff.
2020-02-15 14:41:49 power_api.c:182:set_iic_power_by_voltage: now set voltage to : 17.000000 
2020-02-15 14:41:49 driver-btm-api.c:200:set_miner_status: ERROR_POWER_LOST
2020-02-15 14:41:49 driver-btm-api.c:141:stop_mining: stop mining: power set failed!
2020-02-15 14:41:49 thread.c:829:cancel_read_nonce_reg_thread: cancel thread
2020-02-15 14:41:49 driver-btm-api.c:127:killall_hashboard: ****power off hashboard****

please help me for repair this problems
best regard

[philipma1957]

Don't cut the logs short.

use [ c ode ] all of the    log   [ / c ode ]  


see correct way to code the log

by quoting this

Code:

 the whole log 

once i read the whole log i can guess better.


first guess what volts do you have 210-240?

did they ever work?

do you have any that do work?


both the t17 controller and the t17 power supplies are sold out on bitmain’s website.

what country are you in?

i may know a seller that has a t17 controller and t17 power supply.

He is located  on the east coast of usa . north carolina if i recall correctly.