All Drivers give me disconnected reported by driver

bricor

I was trying to remove ambiguity since the pictures, documentation and words do not jive. Thats all. (and for the record you never told me a thing)

I was also in the middle of updating my post to include

I believe all the motors need to be plugged in (correctly) or you will get the error, especially if you hit home all.

I was Just trying to get a clear understanding of exactly what's going on so I could possibly help.

I see you have it all under control.

Good luck

DruckKlaus

@dc42 any more suggestions?

droftarts

I had a look at your config.g that you posted at the beginning of this thread. Everything looks okay, except that I notice you're running it in CoreXY mode (M667 S1). Can you comment that out? Then connect only one motor to the board, on the X driver, and test movement on X (set G92 X50 to give the axis a position before trying to move, but I'm sure you know this). My theory is that one of your motors is broken. But as any X or Y move needs both motors to work in CoreXY (and, though I haven't tested it, probably two motors connected to X and Y), any pure X or Y move is causing the driver to trip.

Sorry if this is going over old ground, I'm sure you're pretty frustrated. I can't remember if you said you had tried the motors on the Z axis. I also realise now that, as you've got a Duet v1.03, you don't have a 7.5A fuse protecting the drivers and heaters, so it's possible that an overvoltage has killed the drivers. I'd go back to the friend you got it from and ask what he did to it!

Ian

DruckKlaus

@droftarts Commenting it (M667 S1 eg M669 K1) out and testing G92 X50 or G92 Y50 doesnt produce any errors. But also nothing moves.

Dougal1957

Did you issue any G1 commands (Or jogging) after the G92 commands?

Danal

@DruckKlaus said in All Drivers give me disconnected reported by driver:

@Danal u saw the pictures above? The phases are 11 22 on both motors...

Yes, I did see the pics. In fact, the first pic I posted back was a zoom in on your picture.

I know you have verified the coils seven ways from sunday... and it can become very frustrating communicating to all of us how firmly all those test show the coils are plugged in correctly.

At the same time, if the two motors are the same model/manufacturer, then it is not possible that they are both wired correctly.

If the two motors are different, then I am just as convinced as you are, from your ohmmeter pics that the coils are correct. And that makes me just as stumped.

Therefore, on to other troubleshooting methods: Any chance you have other steppers? Or an old printer controller board? Or any other stepper drivers on anything? You see where I'm going, swap things around to find ONE working 'thing' and then use it as a known good to verify other things.

DruckKlaus

@Danal I have already tested other motors. First try was with the act motors in my printer. After failing i rebuild it like before with skr1.3 controller. No problems with that setup.
After this I tried different motors. all working working with other system but sadly nothing works with the duet. Iam pretty confident it's not a motor problem.

droftarts

@DruckKlaus said in All Drivers give me disconnected reported by driver:

Iam pretty confident it's not a motor problem.

It really looks that way. Like I said earlier, “as you've got a Duet v1.03, you don't have a 7.5A fuse protecting the drivers and heaters, so it's possible that an overvoltage has killed the drivers. I'd go back to the friend you got it from and ask what he did to it!“

Ian

dc42

When you send M122, what status do the drivers return? Sorry if I have asked this before, this thread is getting too long to navigate easily.

I think over-voltage would be more likely to make drivers give short circuit warnings than open circuit warnings. The core of the TMC2660 drivers is rated at 60V, it's just the output mosfets that are rated at 30V.

One other thing that might (I'm not sure whether it does) cause all drivers to report open circuit would be if the common TMC2660 enable wire is stuck high. This is the pin on the expansion connector labelled ENN. It should be high (+3.3V) if only 5V power is present (e.g. via USB), and go low shortly after VIN power is applied.

DruckKlaus

@dc42 i tested 24v and 12v.

M122 before trying to move:
Supply voltage: min 13.3, current 13.3, max 13.5, under voltage events: 0, over voltage events: 0, power good: yes
Driver 0: standstill, SG min/max not available
Driver 1: standstill, SG min/max not available
Driver 2: standstill, SG min/max not available
Driver 3: standstill, SG min/max not available
Driver 4: standstill, SG min/max not available

M122 after trying to move them:
Supply voltage: min 13.3, current 13.3, max 13.5, under voltage events: 0, over voltage events: 0, power good: yes
Driver 0: standstill, SG min/max 0/1023
Driver 1: standstill, SG min/max 0/1023
Driver 2: standstill, SG min/max not available
Driver 3: standstill, SG min/max not available
Driver 4: standstill, SG min/max not available

When VIN is applied probing between ground and ENN i get 5V (4.8V) ...
When USB power is applied probing between ground and ENN i get 1.3V...

gueee78

@dc42 what could be the reason that the ENN is stuck high. rather damaged hardware like a cap, or a firmware problem?

dc42

@gueee78 said in All Drivers give me disconnected reported by driver:

@dc42 what could be the reason that the ENN is stuck high. rather damaged hardware like a cap, or a firmware problem?

Blown microcontroller pin caused by a wiring short to that pin; or short circuit, or poor soldered joint on the microcontroller pin.

if you have a multimeter, you could measure the voltage on that pin.