qtdragon - probing issues

thanks.
I installed the new on bookworm. but that should be ok.
Now I will bring the ssd out and get it running on the mill. network stuff is the toughest, but I think I can get it as the current one works and i'll just copy a lot of stuff. Same with the configs and all. Hopefully I'll get the _fix to work.

probably have to do a pull, and check out branch again. then make all over.....no worries.

Seb's debs stay up to date pretty quickly with pushes to master and 2.9, like a day or 2. Cheers to Seb.
And ya can always look for the changes in the listed in the .changes file in the debs directories.

 

rodw wrote:

Ok, Back on topic!

Chris,
I've been through all of the basic probe routines except inside corners and edge angle.
there is  a regression on the height probe as its adding the extre depth in again

 

So I repulled and started testing again. It does look like I forgot to run the rip-environment script yesterday...
So the regression was mine!

ok hole probing will calculate if it should skip rapid positioning.
It also does some basic error calculation to make sure (if it skips rapid positioning) that the max probe length is long enough.
Oh and if diameter hint is smaller the probe diameter a error message appears.
and if probe finishes, the history output shows in the statusbar.

and changed the calculation for long side probe to:
(2x radius) - latch_return- xy_clearance
instead of:
2x (radius - xy_clearance)

Ok, definitely on the right branch now but before any of the changes you just mentioned.

Used a piece of 50mm square section which lets me do inside, outside, ridges and valleys


Tested Basic Probe only 

Outside corners all OK
Inside probe in general.
The probe lowers into pocket, commences movement in the oposite direction to the first probe before starting to probe. Makes no sense. Should just lower and stat moving the right way

Inside corners, inside pockets, ridges and valleys.
When contact is made the second and final time, the probe goes the wrong way (eg toward what it just probed and hits the side again in a non-probe (is this related to the commencement bug above?

Have a look at those and I will retest it all tomorrow.

Can you post a pic of the settings on the probe page?
I don't see a back off before first probe move in my tests but maybe it's setting defendant.

I'm concentrating on the probe inside hole code ATM.