Occasionally, when I start a new program offline, the simulated probe graphic location will get messed up and be completely offset from the simulated points that it is taking. Graphically, the probe will be be performing its motions out in space many inches from the CAD and feature while it is simulating measuring said feature. This does not correct itself when I move the program online, for the program it seems as though the live probe graphic is permanently cursed. This makes the probe graphic totally useless when programming offline, I've never even attempted collision detection when it is like this, seems like it would be a pointless waste of time. I suspect this has something to do with the machine graphic, because when I delete the machine graphic the probe gets closer to proper position, but still far enough away to be useless. I don't know if this a CAD problem, an alignment problem, a machine graphic problem, a transform problem, a bad setting, a bug?? I'm using 2020.2 CAD++ on a Hexagon Global S Blue with a HP-S-X1H on an HH-AS8-T2.5.
How do I prevent this in the future? How do I fix the programs that already have this condition... such as the one I'm trying to work on now.
Possibly an issue/disagreement with a readpoint and the remainder of the program.
Could be an alignment issue. Possibly a question answered incorrectly after working on an alignment - "Do you want to update nominals . . . etc"
Possibly have actuals in the program that correct themselves when you execute offline. Look to see if actuals and nominals do not match in offline program prior to execution. Should match after you execute offline . . . then SAVE.
Possibly an issue/disagreement with a readpoint and the remainder of the program.
Could be an alignment issue. Possibly a question answered incorrectly after working on an alignment - "Do you want to update nominals . . . etc"
Possibly have actuals in the program that correct themselves when you execute offline. Look to see if actuals and nominals do not match in offline program prior to execution. Should match after you execute offline . . . then SAVE.
.
