I guess I can only respond a few times per day, with a new account. As the reply window was missing for 24hrs. I could have been more clear and used better phrasing. I was referring to being on the machine, not in Mastercam. If you call up a X/Y position, when rotated, without DWO active, the X/Y position will not be using the calculated/adjusted work offset on the machine at Axxx.xxx Cxxx.xxx . It will be from your work offset at A0/C0. If you rotate, call up DWO and then your ref point, it will be what you see in Mastercam (retaliative to your T/C plane). In Mastercam using a Haas DWO/TCPC post, if you program from the top of your part with a single offset and multiple planes, the program will be the same if you have a 2" or 20" tall fixture. The simulation will be different because of your change in fixture height, just as the machine motion will be different. But, the actual code will be the same as DWO/TCPC is handling the relationship change. The problem occurs when the initial position does not use DWO, there is no way to account for the relationship between the COR and the work offset on the initial move before TCPC. The second program should not be used as it is calling a rotation when DWO is being used. How much movement are you seeing on the first, are you seeing physical movement?

It is fine if you are programming Center Line of Rotation. But, you lose the associativity when programming from any other point, as the ref point will be in X/Y coordinates in the non rotated view. If a standard retract is used with DWO it will follow the part, if your fixture height changes. One note, Haas TCPC and DWO does have differences in the rules and commands to that of a FANUC. Also, with the new NGC software release Rapid to feed moves is now an option on all 5 axis rapid moves.

This is from a UMC with the IHS post, different rotary configuration but the general idea. (MILL ANGLE ON OUTSIDE) M31 (T2 - 1/2 FLAT ENDMILL - H2 - D2 - DIA .5") N201 T2 M06 G00 G17 G90 G54 S6500 M03 M11 (C-AXIS UNLOCK) M13 (B-AXIS UNLOCK) C0. B-12. G254 <-Activate DWO X3.3023 Y2.1369 <- Preposition G255 <- Cancel DWO G234 H2 X3.1969 Y2.1369 Z.8427 <-TCPC call X3.5088 Z-.6246 G94 G01 X3.592 Z-1.0158 F80. X3.5038 Y2.1813 Z-1.0538 F30. X3.412 Y2.2163 Z-1.0933 X3.3175 Y2.2415 Z-1.1341 X3.2211 Y2.2568 Z-1.1756 X3.1237 Y2.2619 Z-1.2176 Y2.2568 Y2.2516 Y2.2465 Y2.2414 Y2.2362

You need to rotate to your desired angle, activate G254 and then call your X/Y location. Then call G255 to deactivate DWO. Now you are ready to call up G234 to do your simultaneous operation. On larger machines with smaller trunnions, it is not as big of a problem. It is a safer practice to have the program call your initial rotation up, activate DWO for your preposition and then cancel DWO before TCPC. "The problem is the X-1.7192 Y2.1279 are not accurate." This is not true, it is because the position is from A0/C0 and you are not at A0/C0, you must activate DWO so the position is reflected to the rotated point.

So when the UMC first came out, they were using a 45 degree Ball artifact. Which is probably what this machine is using, 2015 ish. The probe cycle for MRZP stores the calculated center point in macro variables. If the artifact is not properly positioned on the table, the probe can shank out. It will run through the process, however your center point will be off considerably. By storing it in a macro variable 1st and not over writing your parameter it allows the user to see how much it is off. If its off by .010 it's a dead give away that it was not setup correctly. Also, if your work probe and tool setter are not properly calibrated the value will significantly be off. This again should be a flag to the user and do some inquiring to figure out why it is off. I typically warm up the machine, calibrate the probes, and then run MRZP a few times to make a chart and compare deviation. Followed by making any required parameter change. Then there is software like AxiSet, that will plot your error. If you had in fact fudged a number, you would see it in the plot. Doing this process, the individual really needs to have an understanding of what they are actually preforming.

Not a good idea to auto populate. If you had a bad hit from having the artifact in the wrong spot, your center point would be updated incorrectly, without giving you a chance to rationalize it.

Make sure no one inverted a sign when they entered in the MRZP parameters(CHC) or settings (NGC). The MRZP cycle stores the offset in macro variables, then you have to type it in manually into the settings or parameters depending on the control. Very possible being this far off. Plus if something was in G52 or G92 you would see it when not using DWO as well.