Duet3 6HC not homing
-
Hi All,
I've taken my old [cartesian] Geeetech A30 (that was acting up) and, as a learning project for 3dp controllers (before fabrication of my corexy design) I decided to replace the controller in my A30 with a D3-6HC + SBC (separate power supplies).
I've got the steppers working and going in the right direction [hurray].
The weird thing is that when i home X/Y, the Z axis goes up ~10mm and then the X or Y moves in the positive direction for about 15mm and then stops, and the printer says that it's homed.
So... there's two things wrong there...
- They move in the positive direction when homing (I've got endstops set to low-end)
- When i test the endstops using M119, I get the behavior that I'm expecting (test by manually pressing)
I can issue G1 codes to my hearts content to move the axes in the positive and negative directions (obviously up to where the printer things it's homed) - and the axes are moving in the right directions when using G1.
I just don't get what the dwc is doing to home the axes.
Also, an aside question, when I upload a new config.zip to the DWC, what do I need to do to get it to accept the changes? Right now I'm powering the board down and powering it back on (because just uploading the file doesn't seem to be enough).
Is it enough to restart the duetcontrolserver service?
-
That homing behaviour might indicate that the endstops are either configured incorrectly or are otherwise indicating they are triggered when they are not.
Please post your config.g and homing files. Also the results of sending M122 and M98 P"config.g" would be helpful.
Normally uploading a config.zip to the system tab would trigger the board to prompt a restart. Does that not happen?
-
@phaedrux said in Duet3 6HC not homing:
Normally uploading a config.zip to the system tab would trigger the board to prompt a restart. Does that not happen?
No, it doesn't. When I first started tinkering, i thought that it was picking up the configs live so I didn't bother doing a power-cycle every time I uploaded new configs.
I spent a long time trying different endstop configs (and wiring, basically doing trial and error at one point) and then though, "oh... crap... what if i need to power cycle to get it to pick up the new configs"
This might be the best place to start. Can i just restart duetcontrolserver or duetwebcontrol services on the sbc to force a reload of the config?
Note: I didn't expect a response that quick so I was just in the workshop rewiring the endstops to do another test.
-
Does it look like the zip file is being detected and extracted?
I think all you'd need to do to have the new config to take effect is use the estop button to restart the controller.