Great work, its simpler than it looks!
I think this should confirm the branch
Code:
git branch --show-current
My machine runs Bullseye too so there is no reason to change.
Chris has been working on the 2.9 branch so when he merges this branch remember to
(The default branch on an initial clone is master branch eg 2.10)
Re version, just trust git, it tells you the branch you are on when you git checkout <branch>
My instructions show how to build a Deb. That takes a long time.
A RIP build is covered in the Linuxcnc developer docs. basically once the dependencies are installed
Code:
cd ~/linuxcnc-dev/src
git checkout qtvcp_probe_max_z_fix
make
sudo make setuid
Now we need to set the environment so linuxcnc looks in your linuxcnc-dev folder
Code:
. ~/linuxcnc-dev/scripts/rip-environment
(the leading fullstop and space is critical)
Now if you run linuxcnc normally IN THE SAME CONSOLE WINDOW, you get the RIP
Closing the window, destroys the RIP until you run rip-environment again.
If you have installed a Deb you built you may not be able to run rip-environment.
If that's the case uninstall the deb, something like
[/code]
sudo dpkg -r linuxcnc-uspace
[/code]
And reinstall one of sebs debs
Then the RIP will be happy.
I think it's a good thing to bake the probing in once it's debugged with tears and broken probes.
I agree there is only 5 probe types My observations are:
There is redundant code on the corner probes. They should call the primitive 5!
Using G38.4 would substantially simplify the probing, eliminate a lot of code and speed up the process.
It seems like the the original probing came stuff running from Mach3 or some other less sophisticated gcode environment. Linuxcnc is smarter so we should use those smarts! (eg G38.4)
