Z-drives not moving, new Duet3

Heide

The Hall effect sensor is wired correctly.

Heide

@Gixxerfast I was on a small road trip when I read you text, and have misread it. I have now read it again, and can see that I also have the high end in the bottom of the right side. I will now reconfigure the Config and home files to this. Let see if this helps

Heide

I have now tested all possible variations, high and low end with and with out ^!. It stops working after homing X and Y.

Now I'm thinking it could be the endstop of Z that is blocking, not the X or Y. It would make sence, since it stops there. If it sees the endstop on, then it won't go. Or maybe the signal should be inverted. I will try this tomorrow.

droftarts

@heide I'm sure your config.g has changed since you did this, but this is your config.g from earlier:

M574 X1 S1 P"!io1.in"                                      ; configure switch-type (e.g. microswitch) endstop for low end on X via pin !io0.in
M574 Y1 S1 P"!io2.in"                                      ; configure switch-type (e.g. microswitch) endstop Y1 = low-end on Y via pin !io1.in
M574 Z1 S1 P"io3.in"                                       ; configure switch-type (e.g. microswitch) endstop U1 = low-end, S1 = active-high (NC) on Z via pin io3.in

If all endstops are these hall effect sensors, then they should all be the same. And they will either have active high or active low outputs (not to be confused with 'high' and 'low' end of the axis, though). So they will need to either all have ! before the pin name (as X and Y do) or none of them will. From https://docs.duet3d.com/User_manual/Connecting_hardware/Sensors_endstops#h-33v-compatible-hall-sensor

Simple Hall sensors normally have active low outputs, so put ! at the start of the pin name if using RRF 3.x
...
If your Hall sensor is a circuit board with a sensitivity adjustment potentiometer on it, then it may provide an active high output instead of active low.

Realistically, use M119 with the axes away from the endstops to check the endstop status. They should all report "[axis letter]: not stopped". With each axis at the endstop, they should report "[axis letter]: at [min or max] stop". If an axis is reporting the wrong way around, add or remove the ! in front of the pin name for that axis.

Don't use pull up resistor ^ with Duet 3. The Duet 3 already has a pull up resistor built-in.

Ian

JoergS5

@heide to add to what @droftarts said, if you use a second hall sensor for Z and it is connected like on the image above at IO_3, then the 5V of this sensor needs to be connected to 5V also. Otherwise the signal has no reference and the sensor has no power.
edit: if Z is microswitch, see next comment.

IO_4 Z probe is also strange, it has only one wire connected.

droftarts

@heide I realise that there are only two wires going to IO_3 (on GND and IO3.in), so likely it's a microswitch endstop on Z, and hall sensors on X and Y. The Voron guide is here: https://docs.vorondesign.com/build/electrical/#endstop-wiring and it is recommended to use NC connections with Duet, too. This should means you don't need the ! before the pin name for the Z endstop.

However, a broken wire on an NC configured endstop will always register as triggered, ie at min/max stop. So test the endstop with M119, and check it changes state.

Ian

Heide

@droftarts yes it is correct, there is a microswitch.

I have now installt new FW, and relocated the endstop to io5. To be sure that there shouldt be any problem with that port. But now I have to connect via YAT and configure the IP. Why, I do not know. But it's every time I save the Config after changing the Config? I will figuret it out in a later stage.

I have made a New Config in the Config tool. Because I want it all to be New and in sync. Working with it at this moment.

I will get back when I have news about how it goes

Heide

I do not know why, but it helped to instal new Firmware. I think there must have been somekind of corruption, I do not know. Maybe it is like what @droftarts said, it can be corrupted. What I know is that I had alot of restarts, alot of changing the code, alot of inspecting my wiring to see if there should be a problem there. Maybe the change of code and the restarts has done something to the Firmware. Anyway yesterday evening I had succes in getting the Z-axel touching the endstop and I am of cause very happy with that.
So for a small moment I will leave your experience a little, I hope. So you can use it else were

I would like to thank you all for your time. Thanks

Solved Z-drives not moving, new Duet3