Mastering Move Points

what version of PC-D? I have only seen that when a program is run online, but then "someone' makes edits offline or changes an alignment. search "RECALL" and make sure your alignments coincide with the previous alignment.  I normally run the whole program offline to "zero" everything out. then recheck my move points. on an offline seat select whatever you are measuring before the move point and execute it "CTRL+E" then insert your move point to see where it is at after you run offline.  Check to see if your measured points / features are "polar" but you are trying to create move points based on XYZ, if that makes sense.

what version of PC-D? I have only seen that when a program is run online, but then "someone' makes edits offline or changes an alignment. search "RECALL" and make sure your alignments coincide with the previous alignment.  I normally run the whole program offline to "zero" everything out. then recheck my move points. on an offline seat select whatever you are measuring before the move point and execute it "CTRL+E" then insert your move point to see where it is at after you run offline.  Check to see if your measured points / features are "polar" but you are trying to create move points based on XYZ, if that makes sense.

I'm using PC-DMIS CAD++ 2024. The move point values themselves don't change when I program on the computer offline vs online. Or if I reset nominals by executing the program offline which is what I normally do. Although it seems the <x, y, z> values don't match what I would expect relative to the CAD origin and the machine. 

I program in command mode so I'm always checking if my alignment recalls the previous and don't believe this to be the issue either.

Are they moving in the correct direction, but the wrong amounts? Or are they moving the correct amount, in the wrong direction?

might be a bug in 2024, can you resave to a lower version like 2022 and open it on a system with a lower version to confirm?

I might be able to I'll have to see if we have it. The company I worked for when I didn't have any issues was 2022. Although I had this same issue on the 2023 version as well before I moved to 2024.

I haven't ever been able to test the movements because they are usually out of the machine axis. But from what I understand I don't get an incorrect direction or amount necessarily. Just that the number is much larger or shifted than it should be.

Austin Lee said:

I'm using PC-DMIS CAD++ 2024. The move point values themselves don't change when I program on the computer offline vs online. Or if I reset nominals by executing the program offline which is what I normally do. Although it seems the values don't match what I would expect relative to the CAD origin and the machine.

I assume you are not manually typing in the values so how are you creating the move points when you're offline?  Are you going through the menu to open the dialog (Insert>Move>move point) or are you using some other method?  If the XYZ values of the move point do not match what you expect, check that your offline probe files do not contain any actual calibration data (if they were copied from a machine for example).  The easiest way to accomplish this is to open the probe utilities dialog on your offline seat and select "reset tips".

.

If you ARE typing in the XYZ values by manually editing the move point in the edit window, then the machine should drive to that location, assuming your alignments are correct.

I have always typed in the code for a move point and added my <x, y, z> values. Do you see an issue with that method? I will check today to see if possible that my probe files offline contain calibration data.

If you are manually typing the XYZ coordinates into a move point command in the edit window, the machine should move to those co-ordinates when the move point is executed.  For example, If I have a square block and I level ZPLUS to the top face and origin Z, rotate Y Minus to the front face and origin Y and the set the X origin on on the left hand face, my co-ordinate system will start at the top front left corner of the block.  If I add a move point X=0, Y=0, Z=10, my probe should move to 10mm above that corner.  If that is not happening for you then something is wrong with your alignment.  If you index the probe to a different tip angle, and add an identical move point (X0, Y0,Z10) it should move to the same place.  If it does not, there is something wrong with the probe calibration because you have lost the inter-tip relationship.

This may be working now. I may have misunderstood something with a programs alignment awhile ago and misunderstood it for a move point issue. I will have to look at this more later this week.