Search content
Sort by
Showing 6 of 6 results by jacktman
Hello mikeywith.
I have to say, you were right.
I've already solved this problem.
The problem was at PSU, It was so dirty in the air intake where the fans are, that it couldn't get any fresh air in, It was completely covered with dirt. I guess the PSU components overheated and sent the wrong voltage to the hashboards
After cleaning the PSU my T17 works correctly again.
Thanks!!!
I have to say, you were right.
I've already solved this problem.
The problem was at PSU, It was so dirty in the air intake where the fans are, that it couldn't get any fresh air in, It was completely covered with dirt. I guess the PSU components overheated and sent the wrong voltage to the hashboards
After cleaning the PSU my T17 works correctly again.
Thanks!!!
thanks for sharing the information you received, I don't have much knowledge of electronics and unfortunately I must trust what they tell me 
It really makes a lot of sense what you say in reference to the 4 temperature sensors, how probable it is that all 4 will be damaged at once?
but is it also possible that if one fails it will send incorrect information to the other 3? I don't know, as I mentioned before I have no technical knowledge of electronics and I don't know if this is possible.
In my case the 4 sensors of the 3 hashboards are failing, so I read this failure is related to the PSU?
Something that also disconcerts me is that my T17 in the cooler hours of the day works normally.
Which is why I thought it made sense that the temperature sensor.
you say you solved the problem by pressing on chip 1
Did your t17 fail on just one sensor or all of them like mine?
It really makes a lot of sense what you say in reference to the 4 temperature sensors, how probable it is that all 4 will be damaged at once?
but is it also possible that if one fails it will send incorrect information to the other 3? I don't know, as I mentioned before I have no technical knowledge of electronics and I don't know if this is possible.
In my case the 4 sensors of the 3 hashboards are failing, so I read this failure is related to the PSU?
Something that also disconcerts me is that my T17 in the cooler hours of the day works normally.
Which is why I thought it made sense that the temperature sensor.
you say you solved the problem by pressing on chip 1
Did your t17 fail on just one sensor or all of them like mine?
⭐ Merited by mikeywith (1)
Hello, I have the same problem with my T17. I contacted the Zeusminig authorized service in my country and the technician confirmed that this problem is very recurrent in T17 and T17+ models. Mostly it is because at some point the machine was exposed to high temperatures, damaging the temperature sensor, the good news is that they have already repaired this fault by replacing the sensor, the bad news is repair cost is $80 for each board. If I have any new news I share it.
Re: Firmware for S17+ 95th/s and T17+ - 80th/s T17 44t@45w/t • S17/T17/S17 Pro
Bitmain doesn't publish the recovery files anymore and they want you to email them and request the exact recovery files you need, but you can get it here https://asic.to/download/s17-and-t17-sd-card-image-to-downgrade/ although that file contains more firmware than you need, it has S17+, T17+, S17, and T17, simply keep what you need and delete the rest.
Thanks for your response, I have tried to download the file but the download stops without completing, I have tried from different browsers and with different ISP.
will you have the file on another server?
thanks
Re: Firmware for S17+ 95th/s and T17+ - 80th/s T17 44t@45w/t • S17/T17/S17 Pro
Quote
... or flashing the recovery firmware then flashing back.
taserz, thanks for your answer, yes it seems to be a common problem in this model
, where can I find the recovery firmware file?I was looking in bitmain and I couldn't find it
thanks
Re: Firmware for S17+ 95th/s and T17+ - 80th/s T17 44t@45w/t • S17/T17/S17 Pro
⭐ Merited by suchmoon (4)
Hello greetings to all, currently my T17 after 5 months running smoothly has started to give me some problems;
and stop mining, this occurs between 12 noon and 6 or 7 p.m.,then it seems to work normally, the ambient temperature is about 31°c to 34°c
I'm not sure if it's a room temperature problem or a temperature sensor problem.
looking for some information I found your firmware, I have some questions;
1) Does your firmware solve this problem?
2) i have developed a script to keep control and check all my miners (hashrate, temperature, fans, ASIC status, etc) it shows the status of all the miners on one screen, it sends me email alerts if something is below the set values, i use socket connections and get the "json" response, with your firmware can i keep asking the miner for this information and get the same response by json?
here you can see a screenshot of my script: https://imgur.com/a/j5uKQOr
thanks.
Code:
2020-04-25 22:20:38 driver-btm-api.c:1443:dhash_chip_send_job: Verion num 4
2020-04-25 22:25:37 thread.c:384:is_zero_nonce_happened: chain_nonce[0] = 15645
2020-04-25 22:25:37 thread.c:384:is_zero_nonce_happened: chain_nonce[1] = 15748
2020-04-25 22:25:37 thread.c:384:is_zero_nonce_happened: chain_nonce[2] = 15840
2020-04-25 22:39:39 register.c:290:get_register: !!! REG_TYPE = 1. 939572226
2020-04-25 22:40:00 temperature.c:683:get_temp_info: read temp sensor failed: chain = 0, chip = 64, reg = 1
2020-04-25 22:40:19 temperature.c:683:get_temp_info: read temp sensor failed: chain = 0, chip = 48, reg = 1
2020-04-25 22:40:39 temperature.c:683:get_temp_info: read temp sensor failed: chain = 0, chip = 168, reg = 1
2020-04-25 22:40:59 temperature.c:683:get_temp_info: read temp sensor failed: chain = 0, chip = 184, reg = 1
2020-04-25 22:25:37 thread.c:384:is_zero_nonce_happened: chain_nonce[0] = 15645
2020-04-25 22:25:37 thread.c:384:is_zero_nonce_happened: chain_nonce[1] = 15748
2020-04-25 22:25:37 thread.c:384:is_zero_nonce_happened: chain_nonce[2] = 15840
2020-04-25 22:39:39 register.c:290:get_register: !!! REG_TYPE = 1. 939572226
2020-04-25 22:40:00 temperature.c:683:get_temp_info: read temp sensor failed: chain = 0, chip = 64, reg = 1
2020-04-25 22:40:19 temperature.c:683:get_temp_info: read temp sensor failed: chain = 0, chip = 48, reg = 1
2020-04-25 22:40:39 temperature.c:683:get_temp_info: read temp sensor failed: chain = 0, chip = 168, reg = 1
2020-04-25 22:40:59 temperature.c:683:get_temp_info: read temp sensor failed: chain = 0, chip = 184, reg = 1
and stop mining, this occurs between 12 noon and 6 or 7 p.m.,then it seems to work normally, the ambient temperature is about 31°c to 34°c
I'm not sure if it's a room temperature problem or a temperature sensor problem.
looking for some information I found your firmware, I have some questions;
1) Does your firmware solve this problem?
2) i have developed a script to keep control and check all my miners (hashrate, temperature, fans, ASIC status, etc) it shows the status of all the miners on one screen, it sends me email alerts if something is below the set values, i use socket connections and get the "json" response, with your firmware can i keep asking the miner for this information and get the same response by json?
here you can see a screenshot of my script: https://imgur.com/a/j5uKQOr
thanks.