Author

Topic: issue on innosilicon t2tz 30th (Read 64 times)

legendary
Activity: 3248
Merit: 2971
Block halving is coming.
February 27, 2022, 07:39:40 PM
#5
There might be a connection problem between the PSU and hashboards what I would like to suggest is to replug all cable between PSU and hashboard.

If not, try to factory reset the miner by holding the reset/IP set button for 4-15 seconds then release.
Then set up the pool and test it again.

If it doesn't work your only option is to contact support but if you bought it 2nd hand I don't know if they can help you.

Try the troubleshooting guide from the link below

- https://www.zeusbtc.com/articles/asic-miner-troubleshooting/1753-how-does-innosilicon-quickly-determine-the-location-of-the-fault-through-the-fault-code
legendary
Activity: 3458
Merit: 6231
Crypto Swap Exchange
February 27, 2022, 08:29:33 AM
#4
Try sending an email to their support: [email protected]
Also, give it some time here for others to reply, there may be someone with a bit more knowledge about the innosilicon miners then me who can help.

Good luck.

-Dave
newbie
Activity: 35
Merit: 0
February 27, 2022, 08:10:59 AM
#3
no, it not mining, its why im upset  Sad
legendary
Activity: 3458
Merit: 6231
Crypto Swap Exchange
February 27, 2022, 08:05:05 AM
#2
Error code 35 is a power issue (Abnormal power output)
Error code 25 is a hash board fault. If that board is hashing normally you can ignore it.

At a guess, and this IS ONLY A GUESS, the your power supply is marginal and the newer firmware is just showing it a bit more.
I have not had an inno unit for a while so I really can't help more. Sorry.
If it's working then just ignore it for the moment, unless you have a spare PS to check. If you don't have a spare I would keep in mind that you may need a new PS soon.

-Dave
newbie
Activity: 35
Merit: 0
February 27, 2022, 07:56:33 AM
#1
Hello
i have an strange issue
all was fine, but Firmware was for 2019, i updated it to 2020 and codes errors showing now...

sometimes 35 and sometimes 25

how i can fix this?
there is any firmware able fix this this errors?

im sure this is known issue, but hope someone can help me.

Thanks.
Jump to: