Solved motor phase A may be disconnected reported by driver(s) 1

[Phaedrux]

Alright, then it's going to be the default.

On the wiring diagram you can see the drivers listed along the top along with what axis they are associated with by default.

So if it's your Y driver that is giving issues, and we want to connect the Y motor to the unused E axis driver, we'd need to tell the firmware a new association with M584.

M584 must come before several other commands, so it would be best to add this line near the top.

M584 X0 Y4 Z2 E3

This has X on driver 0, Y on driver 4, Z on driver 2, and the extruder on driver 3. You'd then switch the Y plug to the E1/Driver 4 plug.

I think that should work.

[keith]

@phaedrux
Hmm same issue. The motor gets jerky and the Y fails to home.

[Phaedrux]

So there may be a problem with the motor itself.

Does it still produce the same motor phase error?

Are you sure the motor phases are wired correctly?

[Phaedrux]

I'm guess this is a cartesian printer?
Does the bed move freely and smoothly by hand with the belt detached from the motor?

What are the specs of the motor?
Is 800ma enough current for it?
Do you have another motor to test with?

[keith]

@phaedrux
Yea all the same issues. But it's acting like a bad connection. I'm thinking there has to be bad wire somewhere even though all the connections look good. I'll deal with it tomorrow.

[Phaedrux]

Yeah a bad wire could fit the description. A continuity tester / multimeter may be helpful. Redoing the crimps/replacing the wire hopefully helps. Hopefully the issue isn't in the motor. But at least it doesn't seem like the issue is on the board.

[keith]

@phaedrux
I hope its not the board. I really like the Duet2Wifi. I just don't have the tools here so I'll have to look at it again tomorrow. Tried 3 different LDO motors that I know work and it's all the same, so I'm thinking a bad wire somewhere since it did the same thing on the E1 driver.

[tekkydave]

You could also try swapping the cable with one of the others (if possible) to see if the fault also moves.

[mrehorstdmd]

Be careful about swapping cables. If you do have an intermittent connection, you may kill the motor driver. It's best to test the cables off the board- use a meter and move the cable as you read the resistance- it should remain constant. Visually inspect the connector(s) to make sure that all looks right there.

[tekkydave]

@mrehorstdmd said in motor phase A may be disconnected reported by driver(s) 1:

Be careful about swapping cables. If you do have an intermittent connection, you may kill the motor driver. It's best to test the cables off the board- use a meter and move the cable as you read the resistance- it should remain constant. Visually inspect the connector(s) to make sure that all looks right there.

That's a good point. I would remake or replace the cable completely just to be sure. Intermittent faults, by their nature can be hard to track down especially if you have no test equipment (DVM etc).

[HarveyS]

@keith
@dc42

What version of the reprap firmware are you running? I am / was having the same "phase A" problem you have, but on the extruder stepper drive(s). Replaced the cabling and stepper motor with known good units and tried both E0 & E1 stepper drivers on my DuetWiFi board.

I made the mistake of doing multiple simultaneous upgrades to my delta printer without incrementally testing the changes. While I was waiting on a Zesty Nimble extruder I tore down my delta printer and upgraded the firmware on the DuetWiFi from version 1.19.2 to version 2.03 (also tried 2.04RC1) and on the PanelDue from version 1.17 to version 1.22.1 while I was waiting. Now I get / got the same "phase A" error with both sets of wiring, stepper motors or stepper drivers.

Managed to downgrade the firmware on the DuetWifi to 1.21 with some difficulty(?)

Firmware Name: RepRapFirmware for Duet 2 WiFi/Ethernet
Firmware Electronics: Duet WiFi 1.02 or later
Firmware Version: 1.21 (2018-03-21)
WiFi Server Version: 1.23
Web Interface Version: 1.21

Completed more testing and with version 1.21 I do not get "phase A" errors on either E0(Drive 3) or E1(Drive 4) stepper drivers with previously good Titan Aero wiring & motor. Re-tested again with the wiring and stepper motor I ordered to go with the Zesty nimble and again there are no "phase A" errors, even driving the extruder to the point where it starts chewing the filament. (The Zesty Nimble has a fixed drive "tension".)

At this point (at least to me,) the problem seems to reside in the version 2.0+ firmware. Which is a shame as Christian Hammacher's new Duet web control 2 interface which works with it is really nice. I haven't been able to run it with RepRapFirmware version 1.21.

[dc42]

Please post a link to the specification for your stepper motors you were using when you had the warning messages, and tell us what motor current you had set.

The "motor open circuit" warning is new in recent firmware versions. We are aware that it is unreliable in some situations, which is why it is disabled at low motor current settings.

[HarveyS]

@dc42

I had the same problem with the e3d stepper motor supplied with my Titan Aero (Genuine) extruder and the stepper motor I ordered to use with the new Zesty Nimble.

Titan Aero supplied stepper motor - P/N MT1703HSM168RE Current set to 1000ma.

Ordered for the Zesty Nimble:
Stepperonline - P/N 70HS10-0704S Current (set to various values) up to 700ma. "phase A" errors at all values.

0_1567974400991_Stepper-Motor_MT1703HSM168RE.pdf
0_1567974463817_StepperMotor_70HS10-0704S.pdf

(Made many successful prints with the Titan Aero on RRF version 1.19.2 before starting the updates.)

[keith]

@dc42
NEMA 17.
1.8° Step Angle.
200 Steps Per Revolution.
1A Phase.
0.48Nm Holding Torque.
40mm Body.
19mm Output Shaft (5mm diameter)
750mm wire lead with Molex connector

Motor current set to .8 amp.

I think I have it sorted out. One of the wires in the cable has a short. I cut the connectors off and checked the wires without any connectors which is surprising considering the Y axis motor and motor wires never move. I might expect a wire to wear down on something like the direct drive motor over time but not the Y axis. Seems to be working now with a new cable. What Molex connectors are these? I want to order some backup connectors.

[Phaedrux]

@keith said in motor phase A may be disconnected reported by driver(s) 1:

What Molex connectors are these?

https://duet3d.dozuki.com/Wiki/Connector_and_spare_part_numbers

[keith]

@phaedrux
Thanks phaedrux. BTW it is cartesian I designed for IDEX, I only have one X head setup on it for now though.

[dc42]

@keith, I'm glad you solved it.

@HarveyS, do you get the error reports only when loading or retracting filament at high speed? Or at low speed?

[HarveyS]

@dc42
I think its related to speed also. Manual extrusion / retraction with DWC > ~15 mm/s or greater and > 5~ 10 mm length with a Zesty Nimble, e3dv6 hot end with a 0.4 mm nozzle and a 30 W heating element. PLA @ 200 C. Tried Both stepper motors and had basically the same results. The inductance on the 17HS10-704S. is a little higher ~ 5.5 mH and the current rating a little lower, but the e3d stepper motor yields about the same results. (And yes prior to testing I had completed a PID tune and a measured 100m extrusion to set the steps/mm correctly.)

When trying to print a real gcode file I get multiple errors and the filament basically retracts right up out of the nimble even though retractions were set to 1 mm. Now the strangeness. After aborting a print I sometimes had something strange occur. It looks / acts like the direction of the stepper was reversed afterwards(!) and I had to cycle power on the printer to recover... (Weird right?)

Just for the heck of it I have a 17HS08-1004 (~$8) on order that others have reported to work correctly ( 4 mH, 1000 ma rating, and lower inertia) when set to 500 ma with the Duet WiFi.

[HarveyS]

@HarveyS
@dc42
Just a quick reply to myself for anyone reading further on this thread.
Replaced the stepper motor with a 17HS08-1004S, set the current to 500 ma as others have used and low and behold - no phase A disconnect errors with Reprap version 2.04RC1. Even when over driving the extruder to the point where it chews filament, so problem solved. Now I can go on and start tuning / tweaking my slicer settings for best prints.
Thanks everyone.....

[dc42]

Thanks for the update. I think the issue is that fast retractions using a highly-geared extruder such as the Nimble require high motor speeds. I see that Trinamic says on one of their recent datasheets that open load detection shouldn't be relied on at high speeds. So in the next firmware version I'll set an upper speed limit for open load detection, in addition to the existing lower speed limit.