PanelDue and Motors will not function properly with Duet Wifi

firex726

Hello,

First time working with a Duet and Reprap (Marlin on current printer), I tried following the setup guide listed on this site but no luck.

This is now my second board with the same issues so I would assume it's my config.

I first got the Wifi config setup via YAT with no trouble, and uploaded my config from the reprap config tool.

I then connected the PanelDue (ribbon) and upon powering on the panel showed a backlight but no image displayed. Web interfaced worked no issues.
I then replaced the ribbon with the included 4 pin wire and same behavior when powering it back on. *fixed

I then set the display aside and wired up the motors, with the end stops in the config disabled so as to limit the causes of the motors not running.

I sent the command:

G91

G1 S2 X10 F3000

The motor then had an audible hum and holding torque but would not actually rotate.

I hooked up my Oscope and recorded the following waveform.

I then wired up three motors that work using my Melzi board (Marlin) to the Duet. I try and Home All but no luck, it makes noise but complains about the phases being disconnected, shorted to ground and the motors make a quiet hum sound and have noticeable holding torque. But otherwise don't move. (Melzi controls them with no issues, double checked the phases are wired as below)

I then try another separate motor on just the Z, same complaints.

The board says, and is wired to:

1B -> 1B (Black)
1A -> 1A (Red)
2A -> 2A (Blue)
2B -> 2B (Green)

Black <-> Green 2.4Ohms
Red <-> Blue 2.4Ohms

And of course no luck either. So now I'm out of ideas.
It seems odd that both the PanelDue and motors would all not work.

A Former User

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

I then connected the PanelDue (ribbon) and upon powering on the panel showed a backlight but no image displayed. Web interfaced worked no issues.
I then replaced the ribbon with the included 4 pin wire and same behavior when powering it back on.

Does the display show the interface if you connect just to USB? Blank screen is usually a problem with getting enough current, but could also indicate firmware issues. Connecting via USB to a USB port with sufficient current will indicate if following the firmware upgrade instructions for the PanelDue would be needed.

PanelDue will show the interface as long as it has power and the firmware is ok. It will just say "connecting" until it gets a response from the Duet.

firex726

Well that's one problem solved. Re-uploading the firmware got the display working like normal. Thanks!

Any ideas on the motors?

elmoret

Motors are wired incorrectly.

firex726

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

Motors are wired incorrectly.

I dont see how... There are only 4 wires, and 2 phases. And I am using motors I know work with a different board with the same pin out. How can I have both a phase disconnected and short to ground?

Add to that the waveform the motor is being sent is very different than the waveform from the working config.

Hooked up the 2nd phase to ch2 on the Oscope and now I got a very different waveform than before.

Danal

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

different board with the same pin out.

Some boards have a "center pair" and an "outer pair". Duet has a "left pair" and a "right" pair. So two boards may or may not be "the same". Colors are meaningless... there is no industry standard for colors.

Your post at the top says:

Black <-> Green 2.4Ohms
Red <-> Blue 2.4Ohms

That means that Black-Green is a coil. Labeling the pins on the Duet board as just 1234, you show Black-Green on pin 1 and 4 of the duet connector. This splits the coil, and will not work. Same thing for Red-Blue.

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.

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