qtdragon - probing issues

Roguish wrote:

I have done RIPs for many years, but not on my current mill.
I just copied the 2 files, and will test 'em by replacing the current files with the new copies. should work since it's a .ui and a .py, not compiled.

I thought you'd know how. I don't think your shortcut will work. There are other significant changes to probing in that branch and a lot more files than a .ui and handler have been touched. If you are using sebs Debs, there are not many dependencies to install. configure should list them. Just copy the list to a text editor, clean up the list and install them. It would be good to have another tester.. I feel lonely.....
 

I'll think about it..... it's definitely better to have more than 1 tester.....

well, trying.  but no luck..  won't compile
not sure what your line   'make -j4'  is doing. 
I get error   'Makefile.inc must specify RTPREFIX and other  variables.  stop.'


also looking at:  linuxcnc.org/docs/devel/html/code/building-linuxcnc.html

 

drop the -j4 if it's a problem. All it does is specifies the number cores when compiling to add a bit of speed (eg multiple threads run instances of compile). Maybe you don't have a CPU with 4 cores. It worked for me yesterday 
The Docs are very good so follow them and you should be right.

If it helps I grumbled a bit when I had to do a RIP on my mill too.
Ethercat was failing until I copied the .so file to the correct RIP folder and I had to compile a couple of custom components.

hey, one more thing with the probing routines.....
all the dimensions and distances, etc., should be displayed as 4 decimal places. like 1.2345
and used internally even better, maybe at least 6 places.....
all the round offs can really add up
i'm trying to cut bearing bores, with +-.0002 accuracies...

and another small question.... can the NCGUI_SUBFILE_PATH have more than one entry? like the regular SUBROUTINE_PATH ??? with : separators?

gotta keep at this.     it took a bunch of years for axis to get worked out.....

Roguish wrote:

gotta keep at this.     it took a bunch of years for axis to get worked out.....
​​​
 

Agreed. This is an amazing interface already. 
There is a lot of refinement I can see could be done in the probing routines but let's get it working first!

Re accuracy:
What is the repeatibility of your probe? 
What is the resolution of your machine?
Three digits is nice for metric machines. That's down to 1 micron, same as a Reinshaw.
Some of us are using probes with  resolution much worse than that.

I am no expert but I'm pretty sure you could change the number format yourself just by altering the stylesheet. Hit F12 and you will see what I mean...