T17 help please

[jds1119]

I have a T17 40th thatn when it power it on both the red light and the green light both constantly stay on and never starts hashing or obtains an IP address. I have tried to reset it from the machine but it wont reset. Any suggestions would be really appreciated.

[1715415992]

1715415992

[1715415992]

1715415992

[yrk1957]

It has a long auto-tune process before it starts hashing. At least 5 minutes. Have you waited enough?

But it should have got an IP very quickly. How are checking that it has not?

[jds1119]

I run about 50 machines and this is the first time Ive had a problem with one. I use angry IP scanner plus it was assigned a static IP. I waited more than 5 minutes prob more. I am going to go back to my shop and mess with again, but Im concerned the board may have went

[philipma1957]

nah they can be flakey.

try a different eth cable.

try advanced ip

plug and unplug the eth jack 10 times

sometimes new gear has coats of electric resistant materials in spots it should not have.

Power switches on heavy duty audio amplifers can be guilty of this.

I assume this is a new unit.

If it is try blowing canned air in the ethernet jack.

if you have had it for months the contacts could have oxidized a bit.

clean with q-tip and 90% alcohol.

blow out with air
try new cable.


also be sure to try a different jack in the switch.

good luck.🍀

[BitMaxz]

I heard someone with the same issue both red and green light blinking. According to them, it is related to program issues resetting it should be fixed the issue.

If the reset button won't work to you try to use the IP reporter button. Hold it for 15 seconds make sure to run the miner first at least in 10 minutes before you perform this.
That method works on s9 miner but if not maybe the IP reporter button is stuck that is why both LEDs are blinking.
Try to keep pressing the button repeatedly until both LEDs stop blinking.

If this doesn't work the miner might be defective.

Since it's new you can send it back to bitmain to replace it with the working one.

[jds1119]

This is my oldest t17. I bought it off ebay in august and dont even want to admit what I paid for it. I was running fine until yesterday when I hooked up 4 new ones that were delivered.
I tried everything philipma1957 recommended but nothing worked, but thank you for the suggestions.
Ive tried letting it run for a bit 2-10 minutes and using the reset button but that does nothing
Ive tried the IP reporting button, but not for 15 seconds, I'll try that next time and see if that works.
Im going to check the warranty but think its going to be close.
I uploaded a video to shows what its doing, thats is all just stay like this.

Smash that like button,jk.

https://www.youtube.com/watch?v=G4VIaTRIBLY

[BitMaxz]

~snip~

Do you have extra control board for t17?

Try to replace it then test if it works without any issue your problem is the control board you need to find the cause of the issue.

You might need to flash the control board with the SD card. The problem is Bitmain didn't release a program recovery for the t17 control board you might need to contact them to request for the t17 software/program.

Look at this S17/S17Pro/S9 SE/S9k/Z11 control board program recovery (SD card flashing with customized PW)

[jds1119]

I wound up ordering a new board off of ebay and everything works now. I may try to salvage the old board with an sd card but the machine is running. Thanks for all the input

[lightfoot]

Just for giggles, can you plug the controller board into a power supply and see if any of the chips get hot or warm? I had a S15 come in dead and it turned out the CPU chip was getting extremely hot. Traced it down to damage in one of the I2C lines, I think what happens is that the boards I2C goes straight to the CPU without any buffers or schmidt triggers. And when the line causes the CPU to go bad you have a short in the chip that gets the CPU very hot and eventually fails.

Only reason I figured this out was because KNC Titans had the same problem with the serial lines from the FPGA directly driving the hashing chips. A surge or spark or oddness would blow up the line, and the FPGA would get hot and eventually fail/burn out.