Here is a wizard that creates a program to Probe a 4th axis object.  Fill in the needed info and it creates the probing G code to run Mach3.

AS always be carefull it is new code generating the Parametric Gcode Routine. Test carefully before you jump in the water(;-)

If you run into a problem please let me know.

You need to unzip the file into the mach3 addons directory.


(;-) TP

I added it to the addons folder... it shows up in my wizards... but it says .set file is missing?

I just checked and the SET file is there in the ZIP file. It loads a runs here. Look in the directory and see IF there is a .set file.

?
(;-) TP

The reason it says that there is no .set file is when you unzip the file, it creates a folder with a sub folder(\4thaxisprobemasterV101\4thaxisprobemaster.) Move everything out of the sub folder and into the main folder(\4thaxisprobemasrV101), then it will work fine.

Hi,
I know this is a very old topic, but as the wizard is still present in Mach3 I gave it a try and I am quite disappointed seeing that the point cloud file generated only has x y z values but no A angle value.
How do you handle the result file then ?

As the process of the wizard is known, I was thinking to deduce the angle because I have, say, 30 points probed in Y before A turns by 10°, so I could have managed it like that.
But, another strange thing for me (also true for the other 3D digitizing wizard) is the order in which the points are recorded in the file.
It does not seems to be the order of scan ?
Can someone tell me in what order are they recorded, is it deterministic ?
I have spend several hours scanning a part, I am still hoping to do something usefull with my point cloud file.

Thanks !
C.M

Config -> Ports&Pins -> Mill Options -> Digitizing -> 4 Axis Point Clouds

@TPS
Great !
Thanks for the tip !
Any idea about the order of recording of the points ?
Are you aware of some soft that would post process the angle value to build a real 3D point cloud ?
(I am in the mood to develop one myself, but if it already exists ...)
Thanks again.