Probe Basic in QTDragon

Hello,
I noticed that probing Z down in the probe basic screen inside qtdragon only takes the Max XY distance into consideration when probing for z height. Is this normal? I see that the routine in the widget python handler is using a data_maxtravel but I'm not sure how this is getting set

 

Just to be sure - you are referring to linuxcnc 2.9 right?
I'll have to confirm in the source.

Are you building from source by chance?
I have a planned update from Qtdragon's parent project but it makes changes in the probing routines that make me nervous to release without more testing.
After that I have another update from Jim's project for auto level adjustment from probing.

Chris

max travel comes from the 'Max XY Dist' linedit in the parameters setting in Prob Basic.
This recorded and read back on opening and closing of qtdragon, in the preference file.

Right so Z Distance max is essentially ignored?


I am building 2.9(sorry should have been more clear) from source and would be very happy to help with testing if needed.

Yes it looks like max Z is not used in the code.

This branch adds auto height probe routines, mostly used for setting up auto tool probing.
It also improves error catching of the probe routines.
The update affects touchplate probing.
github.com/LinuxCNC/linuxcnc/commits/cmo...ragon_hd_auto_height

If you could test it _carefully_ That would be super helpful.
Do you use metric or imperial usually?

Chris

Thanks Chris, I’ll checkout this branch and compile/test on one my machines. I’m setup for metric but can switch to imperial for more complete testing. What I struggled with when I moved to qtdragon is understanding the auto tool height mechanism, so I currently bypassed that logic and using my own M6 remaps. I also couldn’t get the qtvcp manual tool change dialogue to pop up so using the component version at the moment.

I’ll give it another try and hope you don’t mind me reaching out to confirm my understanding of the documentation or to clarify how to setup certain things if I can’t figure it out from the code.

I'll do my best to help. I don't currently use qtdragon on a machine.
Your input on problems of integration is very helpful to making the project better - thanks for you patients.

i don't expect big problems with probing - bit when ever the code changes I get nervous of putting it out in the wild... probes are expensive to break.

Did you get a chance to test this branch?

In progress and so far so good.

Thank you for testing. I think I'll merge this soon to shake it out some more.

Chris