Homeall.g fails when homing all axes
-
@fcwilt said in Homeall.g fails when homing all axes:
Does each nozzle have it's own endstop sensor?
Yes, Each Nozzle has its own endstop . With CAM kind of shared axis when it moves down 1 nozzle the other stays at zero or is lifted back to zero point by the spring to where there is a stopper to prevent it from flying over.
-
@developeralgo222 said in Homeall.g fails when homing all axes:
Does each nozzle have it's own endstop sensor?
Yes, Each Nozzle has its own endstop . With CAM kind of shared axis when it moves down 1 nozzle the other stays at zero or is lifted back to zero point by the spring to where there is a stopper to prevent it from flying over.
OK.
Since you are using NPN sensors the outputs pull the inputs they are connected to to ground (GND)
I'm assuming only one of the sensors has the beam of light blocked when the nozzle is down.
If I am reading the spec sheet correctly the white wire is pulled to ground when the beam is blocked.
If so, you would want to connect both of the white wires to the Duet input and use the ! prefix character to treat the low input signal as active.
As before you would have a G1 H1 move in the direction of the sensor.
Are these nozzles simply up or down OR do they move over a range of vertical travel?
Frederick
-
@fcwilt said in Homeall.g fails when homing all axes:
Are these nozzles simply up or down OR do they move over a range of vertical travel?
They move over a vertical range of travel actually from 0 to -/+ 70 before they trigger the endstop . all have a range of -90:90 but technically
so
(1) On Z-Axis Motor , Z1 has a move range from 0 to -90 and Z2 has a move range from 0 to +90. When one is down , then other is always at zero
(2) On U-Axis Motor , Z3 has a move range from 0 to -90 and Z4 has a move range from 0 to +90. When one is down , then other is always at zero
(3) On V-Axis Motor , Z5 has a move range from 0 to -90 and Z6 has a move range from 0 to +90. When one is down , then other is always at zero
