Duet 3. ? faulty Driver0. Post requested by Duet

DavidSimcock

Ooznest supplied me with a Duet 3 Mainboard on 17th March. They request that I post the issue here, so that a replacement board (if that is what is needed) can be authorised. See text to Ooznest below:

"Hi
Referring to the below order, I have an issue with the Duet 3 mainboard, which I will attempt to describe below.
I have configured the Duet 3, using your excellent Workbee software as a starting point. I have a reasonable degree of experience with the firmware as I have for a few years been an owner and user of one of your machines, with a Duet 2 wi-fi.
Anyway, the issue is that when I perform a home all process, at the end of the homing process, the x axis motor is no longer energised and has no holding torque – i.e I can rotate the x axis ballscrew by hand. The other axes are held rigid by their stepper motors. I have spent a couple of days troubleshooting this, assuming there was an error in the configuration. I would add that I have tried different motors but the issue persisted.
Eventually, I tried connecting the x axis motor (which was connected to Driver 0) to Driver 5, and making appropriate changes to the drive mapping. The issue was resolved.
So, I suspect Driver 0 is faulty, and should this be the case, I would of course be grateful if you would exchange the board.
I have attached my configuration files in case they are of any help. These are prior to swapping to Driver 5
You are welcome to call me on 07850084600 if you need clarification.
I look forward to hearing from you.
Many thanks
David Simcock"

config.g
config-axes.g
config-axes-endstops.g
homeall.g
homex.g
homey.g
homez.g

Ooznest order.pdf

I look forward to hearing from you.
Thanks
David Simcock

T3P3Tony

@davidsimcock thanks for the explanation of your troubleshooting thus far.

What is slightly confusion for me is it sounds like your homeall process is working, but then after homing has completed the axis is then not powered. Is that an accurate description?

When you are homing X is there an error or warning in DWC?

Please send through the output of M122 following the homing move.

DavidSimcock

@t3p3tony
"What is slightly confusion for me is it sounds like your homeall process is working, but then after homing has completed the axis is then not powered. Is that an accurate description?"
Exactly so Tony.

"When you are homing X is there an error or warning in DWC?"
There is neither error nor warning displayed.

M122s below

M122 with driver0 for x axis after homing.txt

M122 with driver5 for x axis after homing.txt

Thanks
David

T3P3Tony

@davidsimcock thanks for those M122s. There is nothing in there to indicate the driver is sensing a fault. that does not necessarily mean its not faulty, but if the X homing sequence is working correctly then its something different from any driver failure i have seen before.

Can you upload the other files called by config.g:

M98 P"config-network.g"
M98 P"config-drives.g"
M98 P"config-axes-limits.g"
M98 P"config-axes-calibration.g"
M98 P"config-probe.g"
M98 P"config-spindle.g"
M98 P"config-laser.g"

along with config-override.g so i can have a look at those. Also once you have homed and the X axis is displaying the lack of motor torque please send M917 so see the holding current configured.

DavidSimcock

@t3p3tony

config-network.g
config-drives.g
config-axes-limits.g
config-probe.g
config-spindle.g
config-laser.g

M917 with x axis on Driver0.txt
M917 with x axis on Driver5.txt

Thanks Tony

David

DavidSimcock

@t3p3tony
config-user-settings.g

config-override.g

oliof

slightly offtopic: you might want to redact your original post so the phone number isn't shared.

T3P3Tony

@davidsimcock I can't see anything in any of the files that indicates why the X motor would be turned off after homing. With the motor on driver 0 does the axis stall easily during homing?

DavidSimcock

@t3p3tony
No stalling at all. The homing move is completed. Thereafter minus X movements do not happen (the DWC reports that the x position HAS changed according to the request). And the x motor is no longer energised (sorry for repetition).
Changing to Driver5, and everything behaves as would be expected.

T3P3Tony

@DavidSimcock I should have been clearer. When the X homing move runs, can you easily stop it with your hand? (Obviously be careful not to put your hand anywhere it could get trapped/pinched) if you can't stop it.

dc42

@davidsimcock where in those files do you use M906 to set the motor current?

DavidSimcock

@t3p3tony
re stalling...I cannot stop the movement with even strong pressure.
In the process of trying this I have more information though. When the x axis is homed (homex.g) independently of the y axis, the x axis motor holds torque after the homing sequence. When the y axis is subsequently homed (homey.g), holding torque disappears from the x axis motor. I hope I have explained that adequately.

DavidSimcock

@dc42 said in Duet 3. ? faulty Driver0. Post requested by Duet:

@davidsimcock where in those files do you use M906 to set the motor current?

M906 is set in the config-axes.g

dc42

@davidsimcock the G92 commands in your homing files are redundant, although I don't see how they would cause this problem. The M584 P3 command in homey.g also appears to me to be redundant. What happens if you remove all those G92 and M584 commands?

DavidSimcock

@dc42 said in Duet 3. ? faulty Driver0. Post requested by Duet:

@davidsimcock the G92 commands in your homing files are redundant, although I don't see how they would cause this problem. The M584 P3 command in homey.g also appears to me to be redundant. What happens if you remove all those G92 and M584 commands?

Thanks dc42. Suspending those commands, unfortunately, makes no difference.

T3P3Tony

@davidsimcock said in Duet 3. ? faulty Driver0. Post requested by Duet:

@t3p3tony
re stalling...I cannot stop the movement with even strong pressure.
In the process of trying this I have more information though. When the x axis is homed (homex.g) independently of the y axis, the x axis motor holds torque after the homing sequence. When the y axis is subsequently homed (homey.g), holding torque disappears from the x axis motor. I hope I have explained that adequately.

Hi David, that's interesting. what happens if you reverse the sequence, from startup, first home Y, then home X I note that Z is home in both those individual files.

DavidSimcock

@t3p3tony said in Duet 3. ? faulty Driver0. Post requested by Duet:

@davidsimcock said in Duet 3. ? faulty Driver0. Post requested by Duet:

@t3p3tony
re stalling...I cannot stop the movement with even strong pressure.
In the process of trying this I have more information though. When the x axis is homed (homex.g) independently of the y axis, the x axis motor holds torque after the homing sequence. When the y axis is subsequently homed (homey.g), holding torque disappears from the x axis motor. I hope I have explained that adequately.

Hi David, that's interesting. what happens if you reverse the sequence, from startup, first home Y, then home X I note that Z is home in both those individual files.

In the above case, i.e homey followed by homex, the x axis motor retains it's holding torque.

T3P3Tony

@davidsimcock ok so something is causing the X axis to loose its holding torque as part of the Y homing.

Can you try the following minimalistic homey.g temporarily.

; homey.g
; called to home the Y axis

G91 ; relative positioning
G1 H1 Y1500 F1500 ; move quickly to Y axis endstops and stop there (first pass)
G1 Y-3 F150 ; go back a few mm
G1 H1 Y1500 F150 ; move slowly to Y axis endstops once more (second pass)
G90 ; absolute positioning

Caution this file no longer homes homes Z as part of the Y move so please ensure the Z axis is in a safe position before running it.

The idea is to see if the X axis is still disabled if X is homes first, then Y homed. both as individual moves. (so homeall.g is not modified yet.)

DavidSimcock

@t3p3tony said in Duet 3. ? faulty Driver0. Post requested by Duet:

@davidsimcock ok so something is causing the X axis to loose its holding torque as part of the Y homing.

Can you try the following minimalistic homey.g temporarily.

; homey.g
; called to home the Y axis
G91 ; relative positioning
G1 H1 Y1500 F1500 ; move quickly to Y axis endstops and stop there (first pass)
G1 Y-3 F150 ; go back a few mm
G1 H1 Y1500 F150 ; move slowly to Y axis endstops once more (second pass)
G90 ; absolute positioning
Caution this file no longer homes homes Z as part of the Y move so please ensure the Z axis is in a safe position before running it.

The idea is to see if the X axis is still disabled if X is homes first, then Y homed. both as individual moves. (so homeall.g is not modified yet.)

Just to check Tony...are you suggesting I suspend all the commands in my homey.g and paste your commands beneath? Followed by sending homex.g and following this with sending homey.g ?

T3P3Tony

@davidsimcock I would rename the current homey.g to homey.g.backup then make a new homey.g with the contents above. then yes G28 X, then G28 Y

DavidSimcock

@t3p3tony said in Duet 3. ? faulty Driver0. Post requested by Duet:

@davidsimcock I would rename the current homey.g to homey.g.backup then make a new homey.g with the contents above. then yes G28 X, then G28 Y

OK...I've done that. The result is that the x axis motor is de-energised at the end of the process.

Phaedrux

After homing is complete can you send M906 and M913 by itself and report back what it says?

Another thing to try is to completely backup your current config, remove it all, and start with a fresh basic config from the online tool.

https://configtool.reprapfirmware.org/Start

DavidSimcock

@phaedrux said in Duet 3. ? faulty Driver0. Post requested by Duet:

After homing is complete can you send M906 and M913 by itself and report back what it says?

Another thing to try is to completely backup your current config, remove it all, and start with a fresh basic config from the online tool.

https://configtool.reprapfirmware.org/Start

Thanks. Here are the M906 and M913

M906.txt

M913.txt

dc42

@davidsimcock from your config-axes.g file:

; Axes configuration executed by config.g
M584 X0.0 Y0.1:0.3 Z0.2:0.4
...
M669 K0 X1:0:0:0 Y0:1:0:1 Z0:0:1:0

You are defining 3 physical axes but your M669 command assumes 4. Try changing the M669 command to this:

M669 K0 X1:0:0 Y0:1:0 Z0:0:1

DavidSimcock

@dc42 said in Duet 3. ? faulty Driver0. Post requested by Duet:

@davidsimcock from your config-axes.g file:

; Axes configuration executed by config.g
M584 X0.0 Y0.1:0.3 Z0.2:0.4
...
M669 K0 X1:0:0:0 Y0:1:0:1 Z0:0:1:0

You are defining 3 physical axes but your M669 command assumes 4. Try changing the M669 command to this:

M669 K0 X1:0:0 Y0:1:0 Z0:0:1

Right...I've revised the M669 as suggested. Homing now functions as it should, with the x axis motor holding torque. Thanks for the suggestion!

Solved Duet 3. ? faulty Driver0. Post requested by Duet