Homeall.g fails when homing all axes

developeralgo222

@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.

fcwilt

@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

developeralgo222

@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

fcwilt

@developeralgo222

Thanks, that makes things more clear.

The homing code should be pretty much the same as before, though I don't actually know how the firmware handles two endstops.

How do you convert stepper position to nozzle position?

Frederick

developeralgo222

@fcwilt said in Homeall.g fails when homing all axes:

How do you convert stepper position to nozzle position?

its just Z-axis as any other , no difference .The CAM on the motor just moves or rotates clockwise or counterclockwise to move the nozzles on the Z-based axes up or down

droftarts

@developeralgo222 As each endstop is triggered at the end of movement for each nozzle, I would think you are best off redefining the endstop when a different tool is requested, followed by a move to trigger that endstop. eg something like

; home Z1
M574 Z1 S1 P"1.io0.in"  ; configure active high endstop switch for low end on Z via pin 1.io0.in
G91                     ; Use relative positioning
G1 H1 Z-180             ; go to endstop
G90                     ; Use absolute positioning

; home Z2
M574 Z2 S1 P"1.io1.in"             ; configure active high endstop switch for High end on Z via pin 1.io1.in
G91                     ; Use relative positioning
G1 H1 Z180              ; go to endstop
G90                     ; Use absolute positioning

I'm not sure how this would interact with OpenPNP, though.

Ian

developeralgo222

@droftarts said in Homeall.g fails when homing all axes:

I'm not sure how this would interact with OpenPNP, though.

this is where i am also having doubts how that would work with OpenPNP