All Drivers give me disconnected reported by driver
-
It looks like the jumpers bridging the second (parallel) z stepper connector are missing.
-
@oliof said in All Drivers give me disconnected reported by driver:
It looks like the jumpers bridging the second (parallel) z stepper connector are missing.
iam using 2 z steppers. but neither of them is connected because of the problems i have ..atm just x and y are conncted.
-
Have you disabled the z motors in the config while they are not connected?
Also, can we see a shot of the underside of the board just to make sure there is no accidental bridging there affecting your board?
-
@oliof said in All Drivers give me disconnected reported by driver:
Have you disabled the z motors in the config while they are not connected?
Also, can we see a shot of the underside of the board just to make sure there is no accidental bridging there affecting your board?
As seen in my config i didnt disable them. But i got the same erros with both of them connected. The underside is completely clean and doesnt touch anything conductive.
-
You say you try to move them, but do the motors actually move? I'm curious, as on my HEVO I get these warnings nearly every print for no apparent reason. The printer runs hours and hours without issue, but these warnings keep randomly coming. It's mostly for Drivers 0, 1 but also sometimes 2 and so on. This started happening some time after I switched to 0.9 steppers.
I've been checking connections and ignoring this for months now. I use these motors: 17HM19-2004S on firmware 2.02 tho. I have a suspicion that at some point the console is flooded with these messages, but I couldn't verify yet because so far the web app crashes during the night.
Fun fact, I've had one different ACT motor (out of two) short out between phases one hour into the print without apparent damage to the Duet a year ago. I've stopped using them since.
-
@Edgars-Batna said in All Drivers give me disconnected reported by driver:
You say you try to move them, but do the motors actually move? I'm curious, as on my HEVO I get these warnings nearly every print for no apparent reason. The printer runs hours and hours without issue, but these warnings keep randomly coming. It's mostly for Drivers 0, 1 but also sometimes 2 and so on. This started happening some time after I switched to 0.9 steppers.
I've been checking connections and ignoring this for months now. I use these motors: 17HM19-2004S on firmware 2.02 tho. I have a suspicion that at some point the console is flooded with these messages, but I couldn't verify yet because so far the web app crashes during the night.
Fun fact, I've had one different ACT motor (out of two) short out between phases one hour into the print without apparent damage to the Duet a year ago. I've stopped using them since.
No mine dont move at all. Sadly.
-
@DruckKlaus have you told the printer it is homed before trying to move the motors (Or issued the cmd to override that safety feature)
-
@Dougal1957 said in All Drivers give me disconnected reported by driver:
@DruckKlaus have you told the printer it is homed before trying to move the motors (Or issued the cmd to override that safety feature)
i try moving the motors by trying to home.
-
add M564 H0 to config.g to allow axis movement before homing for testing
-
The problem is rly just about the drivers.
-
Understood that the motors just have wires, no connector.
Still, if these are going to the same model of motor, they cannot BOTH be correct. If you numbered the pins on a duet motor connector 1234, the coils are 12 then 34.
For example the left connector 12 are blue-green. In the right connector blue is in 3 (which puts it in the 34 coil) and green is in 2 (which puts it in the 12 coil). One or the other of these connectors has to be wrong.
Therefore, try this method of finding coils:
With the motor wires not connected, spin the spindle between your fingers. Short two of the wires together, then spin the spindle again. If it is much harder to spin than before, those two wires belong to the same phase (coil).
-
@Danal u saw the pictures above? The phases are 11 22 on both motors...
-
The wiki page describing how to wire steppers is confusing. First, when identifying the stepper motor phases, it states:
There should be a few ohms resistance between two wires that belong to the same phase, and no continuity between wires that belong to different phases.
So, assume a stepper with green/black/blue/red wires, and there's a few ohms resistance between green/black, and a few ohms between blue/red (but no continuity between any other combinations.)
So, that means that green/black belong to the same phase and red/blue belong to the other phase, right?
Earlier in the same page, it states:
. You must connect the two wires for one phase of the stepper motor between the two pins at one end of the connector, and the wires for the other phase to the two pins at the other end.
Based on an earlier determination of phases, that suggests that pins 1/2 should have green/black or blue/red, and pins 3/4 should have the other pair, right?
That's what I thought based on the wording, but it's wrong.
As a very recent example, I was wiring up a 17HS08-1004S from omc-stepperonline and the wires tested as mentioned above. When I tried to turn the stepper, it'd do nothing but vibrate. In order to get it working, I had to wire it as black, red, green, blue.
-
The 3rd picture in the post (raw wires twisted to test leads) shows continuity on Red/Blue, the PDF spec sheet for the stepper motor shows the pairs as Red/Blue - Black/Green (though that could be wrong).
The remaining pictures have connectors on them and continuity is being shown on Red/Black and Blue/Green.
Are the pictures and test results of(from) the same motor?
The test described by @Danal is the best way to verify the motor pairs.
-
@bricor no there are not. as said, these motor are from a test setup because i need my printer running again ..
i dont know how often i have to tell you that (as shown) the pairs of cables are right... last option would be to short them direct on the board to see what the drivers are reporting. -
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
-
@dc42 any more suggestions?
-
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
Bed-slinger - Mini5+ WiFi/1LC | RRP Fisher v1 - D2 WiFi | Polargraph - D2 WiFi | TronXY X5S - 6HC/Roto | CNC router - 6HC | Tractus3D T1250 - D2 Eth
-
@droftarts Commenting it (M667 S1 eg M669 K1) out and testing G92 X50 or G92 Y50 doesnt produce any errors. But also nothing moves.
-
Did you issue any G1 commands (Or jogging) after the G92 commands?
