Duet 3. ? faulty Driver0. Post requested by Duet

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!

DavidSimcock

@davidsimcock The issue does seem to be resolved with changing the kinematics M669 command.
A BIG THANKS to all who have made suggestions to resolve the issue. It is much appreciated.

T3P3Tony

@davidsimcock thanks for confirming this. May I ask where the config came from?

DavidSimcock

@t3p3tony I took it from the Ooznest Workbee configuration that I had on a duet 2 wifi, and adapted it for the parameters of my machine. Why there should have been those kinematis commands I don't know. And I confess to not really understanding why there were 4 entry's...

T3P3Tony

@davidsimcock thanks, I will follow up with Ooznest. Thanks agin with your patience as we worked through this.

jay_s_uk

@t3p3tony M669 was also a feature of this workbee config https://forum.duet3d.com/topic/27923/x-axis-stops-working-after-moving-y

T3P3Tony

@jay_s_uk thank you for linking these two together I did not see that post.

We have captured the issue with M669 to review.

dc42

I've added the behaviour when M669 has too many entries per matrix row to the bug list.