PanelDue and Motors will not function properly with Duet Wifi

[firex726]

@Danal said in PanelDue and Motors will not function properly with Duet Wifi:

@firex726 said in PanelDue and Motors will not function properly with Duet Wifi:

different board with the same pin out.

Re-wire the plug going to the motor connector (power off first, hot-plugging motors WILL burn the driver chips) so that it has Black Green on 12 and Red-Blue on 34.

To be clear, the board is labeled as phase:
B
A
A
B

And when I wire a motor to the extruder as I had it, it'll work.
It's only the X, Y, Z that have issues.

But I did rewire as you suggested, and now it reports that both phase A & B are both disconnected with no humming or holding torque present.

[jay_s_uk]

You need to home an axis to be able to move it.
Or allow movements without homing. M564 H0

[A Former User]

@firex726 said in PanelDue and Motors will not function properly with Duet Wifi:

To be clear, the board is labeled as phase:
B
A
A
B

It's also labelled ..
1
1
2
2
.. if you want to look at half the picture like that

The two coils are supposed to be on the first & second, and on the third & fourth pin respectively, if that doesn't work you might have damaged the board from having it wired incorrectly in the first place.

[dc42]

@firex726 said in PanelDue and Motors will not function properly with Duet Wifi:

To be clear, the board is labeled as phase:
B
A
A
B

No, on the Duet (as on every other board I know of), one phase is at one end of the connector and the other phase is at the other end. So you should connect the wires in order red-blue-green-black, or any other order that keeps red/blue together and green/black together.

The labels on the Duet motor connectors match the output labels on the Trinamic motors drivers. Unfortunately, Trinamic label the phases 1 and 2, whereas most of the rest of the industry labels them A and B.

The standard colours for Nema 17 motors when the wires come directly out of the motor are that red-blue is one phase, and green-black is the other. But if the motor has a connector and the cable plugs into it, you must not rely on this, because different motor manufacturers use different connector pinouts.

[firex726]

So to be clear...

I'm using the Home command as the means to control the motors, but even using G92 to assign the current position as home it's the same behavior.

All the motors work on the extruder/E0 driver. But when I simply swap it to any other driver it starts complaining about phases A & B being disconnected so that's why I swapped the wiring initially. (Thinking it was phase A&B not 1&2)

In the config if I assign E0 to Y it'll have the same issues.

I also thought maybe the motor config was an issue, so I copied the config of E0 (known good) to all the axes and it still had the same issues.

[dc42]

The correct way to test individual axis motors is to send G91 to select relative mode, followed by G1 H2 commands. For example, G91 followed by G1 H2 X20 should move the X motor by the equivalent of 20mm.

[firex726]

@dc42 said in PanelDue and Motors will not function properly with Duet Wifi:

The correct way to test individual axis motors is to send G91 to select relative mode, followed by G1 H2 commands. For example, G91 followed by G1 H2 X20 should move the X motor by the equivalent of 20mm.

The issue appears to be with homing:

2/8/2020, 7:44:40 AM G1 H2 Y20 <--- Motors does not move
2/8/2020, 7:44:34 AM G91
2/8/2020, 7:44:28 AM G28 Y *<--- The motor is making an audible hum and torque
2/8/2020, 7:44:10 AM G1 H2 Y20 <--- Motors moves
2/8/2020, 7:43:50 AM G91

[firex726]

2/8/2020, 7:44:28 AM G28 Y *<--- The motor is making an audible hum and torque

Thinking issue is with Homing I wired up an endstop and re-enabled it in the config.

The motor works just fine till I trigger the endstop and then it locks up as before, and now reports the phases are disconnected:

2/8/2020, 8:15:30 AM G28 Y
Warning: motor phase A may be disconnected reported by driver(s) 0
Warning: motor phase B may be disconnected reported by driver(s) 0
2/8/2020, 8:15:13 AM G1 H2 Y20 <--- Motors moves
2/8/2020, 8:14:46 AM G91

[A Former User]

@firex726 said in PanelDue and Motors will not function properly with Duet Wifi:

now reports the phases are disconnected

If you look closer at the actual output it says they may be disconnected. Could be a settings issue. Motor specs and config to confirm/rule out.

[firex726]

@bearer said in PanelDue and Motors will not function properly with Duet Wifi:

@firex726 said in PanelDue and Motors will not function properly with Duet Wifi:

now reports the phases are disconnected

If you look closer at the actual output it says they may be disconnected. Could be a settings issue. Motor specs and config to confirm/rule out.

It just moved literally 17 seconds earlier.
I copied the default E0 settings to the others since the motors worked when plugged into that driver.

[dc42]

Please post your config.g and homing files.

[firex726]

@dc42 said in PanelDue and Motors will not function properly with Duet Wifi:

Please post your config.g and homing files.

Oh boy that's a tall order with how many revisions I made.
Here is the ones I'm using as of my previous post. The endstops I was not sure of so did one as NO and one as NC; see which one works the way I expect.

homez.g
homey.g
homex.g
homeall.g
config.g

*Also someone may have burned out the Y driver so I reassigned it to E1.

[firex726]

I'll have to do more testing at home, reading the files I wonder if maybe it's because I only have one motor connected?
Looks like wen homing Y it's also giving commands to Z and since there is no Z wired...

Just curious, why use G1 over G28?

[Phaedrux]

@firex726 said in PanelDue and Motors will not function properly with Duet Wifi:

Just curious, why use G1 over G28?

Because G1 allows you to target a specific axis. G28 executes homeall.g which has moves for all the axis. As you noticed there is also a move to lift the Z axis slightly to get it out of the way for travel. So having no motor connected will result in errors.

Here's a guide that goes through some commissioning steps that may help.

https://duet3d.dozuki.com/Guide/Ender+3+Pro+and+Duet+Maestro+Guide+Part+3:+Commissioning/39

[Danal]

@firex726 said in PanelDue and Motors will not function properly with Duet Wifi:

one as NO and one as NC

If at all possible, physically wire them as NC.

[A Former User]

@firex726 said in PanelDue and Motors will not function properly with Duet Wifi:

Oh boy that's a tall order with how many revisions I made.

We're not psychics and the devil is usually in the details. So you'll need to keep us up to date if we are to help you efficiently; something to keep in mind going forward

[firex726]

Good news had a bunch of progress...
Motors seems to be working mostly.

Z motors were working in opposite directions so I inverted the wiring on one and now they work in unison.

Only trouble bit now is when I'm homing the X and Y. The motors don't seem like they are entirely in sync with each other. I thought with a CoreXY it'll differ the movements of the motors to produce the same carriage movement of a Cartesian, is that correct? (Forward/Back, Left/Right)

When homing Y it'll draw the carriage forward but there will also be lateral movement too. About 100mm Left from the most extreme point to Home; but not smoothly, it'll travel a bit and then jerk over, and travel more OK, then jerk again, etc... (I double checked to make sure the belts are taught)

Similarly, X will do the same, moving the carriage back towards the extreme away from Home and latterly about 100mm Right.

I'm using those Drylin bearings on the carriage, when mounted they are snug with the rail. And on the Y i'm using normal linear bearings.

So I can't seem to get X to Home since for that I'd need what? 600mm Y travel? (300mm cubed is my intention)

*Not sure if related but I'll still almost randomly get warnings of Drive 0 having it's phases disconnected and have to reset the machine, at which point it'll be OK again till the next random warning. Could the motor itself be bad, or not enough current?

If I try just movement it does the same...

G1 X50 Y50

Which I would expect a 45 degree movement is again a very small movement on X but a much greater one on Y. It's hard to tell exact since the machine think's it's done 50 on each axis.

*Also does the "M564 H0" as mentioned earlier in this thread override the endstops? I had used it and then was moving the axis to test the endstops but they did not stop the movement even thought they triggered. But when using the default Homing commands the axis did stop as expected.

Please let me know if you need any additional files, or config's to test.

homez.g
homey.g
homex.g
homeall.g
config.g

[dc42]

I suggest you test the motor individual using G91 followed by G1 H2 Xnn and G1 H2 Ynn commands. Check that the other motor doesn't move and that movement is at 45 degrees to the axes. https://duet3d.dozuki.com/Wiki/ConfiguringRepRapFirmwareCoreXYPrinter#Section_Testing_motor_movement.

Have you made sure that the belt runs whose lengths vary with carriage position run exactly parallel to the X and Y axes? User @mrehorstdmd has posted a useful diagram to illustrate this in other threads.

[Phaedrux]

@firex726 said in PanelDue and Motors will not function properly with Duet Wifi:

*Also does the "M564 H0" as mentioned earlier in this thread override the endstops? I had used it and then was moving the axis to test the endstops but they did not stop the movement even thought they triggered. But when using the default Homing commands the axis did stop as expected.

Endstops will only stop movement if they are triggered during a homing move, which is denoted by G1 H1 . The H1 switch (or in older firmware versions S1) denotes it as a homing move.

I believe this is the diagram that DC42 mentioned.

[dc42]

Thanks @Phaedrux, that's the diagram.

@firex726, belt sections A thru H in that diagram must run parallel to the axes. Sections JKM don't need to.