Secondary Tool move breaks Z homing
-
@optical Did you try any of my suggestions?
-
@Phaedrux @dc42
My maching was unavailable due to some maintanance.Yes i hae tried your suggestion with M400. It did not work.
As i said i discovered in past comment that the issue is with the induction sensor on input pin. The pin stops reading correct value.The machine thinks that the sensor is always triggered after movement with Tool 1.
Is there some other way how to configure the endstop to stop this issue ?
-
May i ask if this is correct way of setting Endstop for Z axis, because the input just breaks on tool change. Is it possible that the machine starts to expect different endstop for its movements ?
M574 Z2 P"!io0.in" S1
Homez:
; homez.g ; called to home the Z axis G91 ; relative positioning M400 M913 Z25 G1 H1 Z+40 F500 G1 H2 Z-5 F500 G1 H1 Z+5 F500 M400 M913 Z100 G90 ; absolute positioning G92 Z12 G1 Z0 F500; Park
-
Yes that looks ok for a zmax endstop switch, but it depends on the kind of switch. NO or NC.
@optical said in Secondary Tool move breaks Z homing:
G1 H2 Z-5 F500
Remove the H2 on that move to back away from the switch.
-
@Phaedrux Keep in mind that the homing Z is working properly until i use commands:
T1 G0 X10
After these commands the input sensor stops working. So it must be related to the movement of the second tool.
I think there has to be bug in the firmware. Otherwise the homing before the movement would be also faulty. -
@optical said in Secondary Tool move breaks Z homing:
the input sensor stops working.
Meaning the inductive probe? Does the switch also stop?
Sorry, I'm having a hard time visualizing what's all going on. Can you post a video showing step by step what's happening?
-
-
Your video link is private.
-
@Phaedrux I have edited the post to make it public.
-
Thanks.
Ok, so just to clarify what I'm seeing. The left head does the G28 Z it goes down, triggers, backs up, and goes down again. T1 is sent, it switches to the right head, G0 X150 is sent to make it spin and then G28Z is send again but this time the Z endstop is already triggered at the start of the move.
@optical said in Secondary Tool move breaks Z homing:
G92 Z12
Where does this value come from?
@optical said in Secondary Tool move breaks Z homing:
G1 H2 Z-5 F500
Did you remove that H2?
@optical said in Secondary Tool move breaks Z homing:
homing Z is working properly until i use commands:
T1 G0 X10Does the behaviour change if you don't also send the G0 X10 command? Does it behave different if you send G1 X10 instead?
What are you using for the Z endstop now? Is it still a probe or is it a simple switch?
-
@optical said in Secondary Tool move breaks Z homing:
I do not have any tool change files tfree0.g, tpre0.g and tpost0.g in /sys on the SD card
Could you try creating them? Even if they are empty.
-
Can you also post your config.g as it currently stands.
-
-
-
This is because the Z Axis has to have 0 coordinate in the neutral position. When the nozzles are at the same height. The induction probe is not all the way at the end of the heads movement range.
Or do you have some other idea how to tell the board that the end switch is not at maximum or minimum coordinate?
-
-
This post is deleted! -
@Phaedrux @dc42
I have found that there is M119 Command to report endstop states so i made the test where the Z endstop stops working.Image upload does not work...
It shows that the M119 state does not change when the endstop stops working. There must be some kind of mapping associated with the tool changing.
The reason why i think the endstop is not working is that when i disconnect the probe for the expected broken homing the head is behaving as the switch is open.
However when connected for the expected broken homing it reads it as closed.
(Open, Closed in terms of active switch not the voltage level.)When the machine is in the broken state when i activate the switch manually the M119 reports correctly that it is stopped.
Endstops - X: not stopped, Y: not stopped, Z: at max stop, U: not stopped, V: not stopped, Z probe: at min stop
There must be some kind of issue in move command that it is checking wrong input or something. After the tool change
-
Sorry for the lapse in replies. Was not intentional.
And that's still with empty tool change files?
-
@Phaedrux Yes