Get current tip position to variable in PC-DMIS

            ASSIGN/V1=GETSETTING("LASTHITMOVE(X)") 

Also works... change the x to y or z based on what you need. 

I was also playing with this, and it is essentially giving you the X, Y, Z of the last hit of the feature you measured. If you have avoidance moves, clearplanes or move increments after features this won't truly be your probe tip's X, Y, and Z. But this was definitely on my radar. I tested it and it did not update the X, Y, Z after any move commands. This could still work, so long as you know that it's the last position the probe physically touched the part. Readpoint is more accurate like Dismas said, because it gets active probe tip location, and doesn't need to move or touch anything to acquire it.

yep, you're right, mine updates, but randomly. 

It's actually quite frustrating, because you can get the Tip A angle, B angle, IJK, and last parameter "Angle", but you cannot get the XYZ. If there is a secret way to find the X, Y, and Z this way please share. These are displayed in the status window. So I feel like there IS a way.

            TIP/T1A0B0, SHANKIJK=0, 0, 1, ANGLE=0
            ASSIGN/V1=GETCOMMAND("Set Active Tip", "UP",1)
            ASSIGN/WRIST=GETTEXT(3, "TOP", V1)
            ASSIGN/TIPI=GETTEXT(229, "TOP", V1)
            ASSIGN/TIPJ=GETTEXT(230, "TOP", V1)
            ASSIGN/TIPK=GETTEXT(231, "TOP", V1)
            ASSIGN/TIPANG=GETTEXT(38, "TOP", V1)
            COMMENT/REPT,
            "Active Tip is " +WRIST+ " ShankIJK is " +TIPI+","+TIPJ+","+TIPK+" and angle is " +TIPANG

There is a way, but it involves scripting. The object model includes a "machine" object. You would have to create an instance of that class and monitor the Readout Event. It just doesn't seem to be exposed to the pc-dmis program itself. If you were automating, however, and responding already to application events, you could always add that in.

There is a way, but it involves scripting. The object model includes a "machine" object. You would have to create an instance of that class and monitor the Readout Event. It just doesn't seem to be exposed to the pc-dmis program itself. If you were automating, however, and responding already to application events, you could always add that in.