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.
The feature nominals, feature graphic, green probe paths, and physical machine probe are all correct relative to the CAD in the window and the part on the machine. The only thing wrong is the simulated probe graphic location and motion relative to the displayed features the computer is stimulating/physical features the machine is measuring. When the green paths are shown, they are correct in relation to the CAD, and when the features are executed the machine probe follower the correct path as the green path lines displayed, the only thing not synching with the path lines is the simulated probe graphic. I resetted the actuals on both the feature level, and the program level before I wrote this post. I think if the alignment or the actual values were the problem, the green path lines or the machine motion would be wrong, and they are not wrong. All the actuals match the nominals when I execute offline. If Center Probe was engaged, the graphic should still follow the correct path, it just brings you along for the ride. I would think if the rotary programming was a problem, it would manifest itself in ALL of our programs, but I will check that setting out just in case even though we have not purchased that option.
Does this have to with the LOADMACHINE setting? Offline probe calibrations? CAD or Animation settings? What happens if the ReadPoint is executed outside the virtual machine extents? What if the rotation head in the stylus definition doesn't match the graphic in the load machine settings?
The feature nominals, feature graphic, green probe paths, and physical machine probe are all correct relative to the CAD in the window and the part on the machine. The only thing wrong is the simulated probe graphic location and motion relative to the displayed features the computer is stimulating/physical features the machine is measuring. When the green paths are shown, they are correct in relation to the CAD, and when the features are executed the machine probe follower the correct path as the green path lines displayed, the only thing not synching with the path lines is the simulated probe graphic. I resetted the actuals on both the feature level, and the program level before I wrote this post. I think if the alignment or the actual values were the problem, the green path lines or the machine motion would be wrong, and they are not wrong. All the actuals match the nominals when I execute offline. If Center Probe was engaged, the graphic should still follow the correct path, it just brings you along for the ride. I would think if the rotary programming was a problem, it would manifest itself in ALL of our programs, but I will check that setting out just in case even though we have not purchased that option.
Does this have to with the LOADMACHINE setting? Offline probe calibrations? CAD or Animation settings? What happens if the ReadPoint is executed outside the virtual machine extents? What if the rotation head in the stylus definition doesn't match the graphic in the load machine settings?
.
