Compiling probekins and using probe2stl

I'll try and answer both at the same time.

That's the command I used:Sorry I left that bit off.

I get the same error with my compiled version as I do with yours. "Unknown symbol in module"

Since I believe that we are all using the same distro "LinucCNC" that the build/dev environment would be the same.

The divdi3 is a system level function that is used to do long long / long long which is int64 / int64. 64bit division. I had thought that it was because I was running a 32bit platform so I switched to a 64bit one. Got the same issue, so that wasn't it. I'm now assuming that you had compiled it differently by including something?

I guess the question is, do you get the same warning with the divdi3 when you compile it? if so, I'm assuming you changed the config for LinuxCNC some how. If not then you have probably included/added some library on to the system that didn't come with the distro.

ok, having the full source tree works.

Thanks for the help

I'll continue trying to get the rest of it working.

So I have it working and it seems that if the gcode command doesn't have a Z move then it doesn't adjust the depth. It only adjusts on the initial plunge.

I'm guessing the simple fix is to make sure that all the gcode commands have a Z move?

Keep in mind that the offset is behind the scenes, and the Z dro wont show the offset that is applied.
It should show up in the pyvcp deltaz display when it is enabled. Does it behave as expected with jogs?

So I based the depth test on a warped PCB surface and with probekins turned off it didn't touch the surface at all. The cut is a small circle. With it turned on, the small circle was cut but there is a long cut across the pcb and it starts on the low side and goes through a high spot. probekins did not adjust for it. I could tell just by the cut depth as it moved across the surface.

as for the jogging, there is that weird behaviour that you described when in joint mode. But when I switch to world mode it jogs fine except for touchprobe doesn't work.

What do you have the increment set for probing?
for a pcb, I'd do 10 per inch maybe? See if that helps compensate better.
Or does it not adjust at all?
Also make sure when you do the probing there are no x or y offsets applied.
Then when it finishes with the probing, enable the Z correction before doing anything else.
Then set your offsets for the job.

Here is a piece of acrylic I engraved.
I did 1 probe per inch, and it had 1/2" drop over the surface with the wrench holding it up.

ok, so I'm missing something. I first ran the probing before setting up all the prokins configs. But now when I run it with prokins loaded it says that I will exceeed the min joint limit. So these are my steps:

1. launch linuxcnc with prokins
2. Home xyz axis to the material (PCB), in joint mode
3. load gridprobe.ngc
4. Run gridprobe.ngc (Throws error exceed joints min)
5. load cut path (in this case top of pcb)
6. convert gridprode results to stl
7. load stl into memory using stlcorr.py
8. Switch to world mode
9. run loaded cut path

all the help is greatly appreciated.

oh, and the stepping I'm using on the gridprobe is 2mm