Not sure why I’m getting this alarm during Tls probing . It probes the initial tool after its first job then it calls for tool change , I change the tool and just as it finishes the probe sequence the z raises up , triggers hard limit alarm .
Fwiw I have soft limits turned off. [EDIT] fixed , 3rd pic shows $13 needs to be disabled .
Any ideas on a fix ?
@Gravesj1s how much is it moving up after doing the probe? It sounds like maybe between your bit stickout, the height of your TLS, and how high it’s moving up it’s maxxing out the Z-axis travel of your machine
Ok , so let me just give a brief idea of how the TLS is setup and that may make better sense .
I got Tls properly wired up and set in position on my wasteboard . In gsender , I select the “fixed tool probe option . Jog over it , selecting “ grab current location “
Now I home machine , load new file that calls for 3 bit changes . I have x0y0 already set , so I go to . Using the probe block as a first probing , set the magnet , probe for z0 per wizard . All set .
Start file runs perfectly . As it finishes the spindle goes over pause over the TLS , per wizard , I touch off the tool before changing to the 2nd bit , it proves then I change the bit , proves that bit on the Tls , then I press resume .
And this is where the z triggers a soft alarm . Soft alarm disabled it will then just trigger hard stop, and if I disable hard stops as well , it will raise as high as it can triggering the estop .
What I think is happening is grbl is trying to raise the z height using inches instead of mm . I do have inches set in the firmware , but that doesnt seem to matter ,
A work around I found is with $13 in the firmware disabled the tls works perfectly . The results are repeatable going back and forth over and over .
I hope this helps clarify what I was seeing .
Thanks for replying back .
Chris ,
Sorry , I just noticed you commented her too. I just gave a detailed reply in the edge post , so I’ll skip it here .
The gist of it , for whatever reason in $13 seems it needs to be turned off in firmware and then the tls sensor works perfectly .
As I said the results are repeatable . Let me know if you see something different .
Thanks for reaching out
So does it seem then like your machine is moving up by 1 inch at the end of the tls routine and that’s causing the issue? If so then we can probably account for that
Chris,
Honestly I think it’s atleast an inch before triggering an alarm .
Not only that but if I were to press “ go to” z0 after the Tls probing , the bit would plunge past what should be z0 .I can visually see the value in z coordinate box by manually lowering to the wasteboard ( zero to stock bottom ) that it will go past the waste board .
