Homing problem after Duet2 WiFi Upgrade
-
@droftarts: the z-axis grinds and does not move with the command G1 H2 Z10 F6000. I am also seeing the following error message: Warning: motor phase A may be disconnected reported by driver(s) 2.
-
@droftarts : I've just rechecked what happens when I send the command G1 H1 Y-10 X-10 F1800. There's no grinding and no error messages are shown. The problem appears to be with the z-axis, not x or y as I originally thought...
-
If normal moves are grinding, that generally indicates miswired stepper motors. If you move an X-axis motor to your Z-axis stepper driver and do a Z move, what. happens?
-
-
@droftarts: slowing speed to F60 does not resolve the problem. I will recheck the wiring on the stepper motors. I've done a visual inspection to ensure that the wire are inserted into the correct pin locations. They all look correct. I'll double check each connector to make sure I don't have a bad crimp - I needed to re-wire/re-crimp all the connectors to make the transition and I may have missed one. I'll also try the suggestion of @elmoret after I check the integrity of the connectors.
-
Also verify that your motor phases are correctly wired
Each of your Z motors are going to one of the Z motor ports, correct?
-
Thank you all! One problem seems to be solved: I double checked to ensure the motor phases are correctly wired as recommended by @Phaedrux. That aspect of the wiring is OK. I then found one bad crimp on a wire inserted into one of the new z-axis connectors. I repaired it and verified that all the other connectors are sound. The z-axis now moves smoothly and quietly following issuance of the commands provided by @droftarts.
My remaining problem is that x- and y-axis homing is not yet working properly. When the build platform reaches either the x or y end stop after a home x or y command is issued, it hits the end and does not stop running until I hit the emergency stop. The error message, homing failed, is shown. I'm going to run through the motor stall detection configuration procedures in the link recommended by @JamesM above. Please LMK if you have other suggestions on what I might need to do to solve this one.
Thanks again everyone. I'm very grateful for the kind help you've provided.
-
@lhbru The link that @JamesM provided is just the gcode dictionary link, and should be used in conjunction with this guide: https://duet3d.dozuki.com/Wiki/Stall_detection_and_sensorless_homing
Ian
-
@droftarts My x- and y-axis homing problems are now solved. After reading the the stall detection and sensorless homing guide, I changed the speed settings in the G1 command lines homex.g and homey.g from F1800 to F4800 so that the homing speed is greater than the minimum F2400 that derives from the default stall detection threshold of 200 steps/second. I also commented out the lines associated with the second slow fine homing moves. Now, when I command home x or home y, the build platform moves quietly to the endstops and the platform stops as expected. Thanks so much for pointing me in the right direction
I have final question related to specifying a stall detection configuration using M915. I haven't yet added M915 line to my config.g. because the changes I made in the homex.g and homey.g seem to have solved my homing problems. I take this to mean that the default M915 settings do not need to be modified by adding a M915 line to config.g. Is this the right way to think about this, or would it better for me to add the M915 line to config.g? And if I add the line would you please confirm where it should be placed? I'm thinking it should follow the two M574 commands in the Endstops section of config.g?
Again thanks to all for your help.
-
I would always add an explicit line, so you are not dependent on defaults, and so that you can easily see what to change if there is an issue. 'hidden' configuration can be very hard to diagnose.
-
@lhbru said in Homing problem after Duet2 WiFi Upgrade:
I'm thinking it should follow the two M574 commands in the Endstops section of config.g?
Sounds like a good place.
-
All problems are solved - and just completed a first print with the new Duet2. Thanks again to all who helped - I'm very grateful!
