Your Products have been synced, click here to refresh
I wonder what it will do to vpt’s original program when AdjustLevelCommandRotation is set to False
I'm traveling so can't check this myself in pc-DMIS but there is another check box in the f5 setup window called "allow fine tuning of alignments". I have never really understood what this does. It kind of sounds like it is allowing pc-DMIS to make alignment modifications but I'm not sure this is actually what it is referring to.
Has anyone verified the idea that if you use a recalled external alignment at the beginning of the program it will lock down the nominals? I have almost never had a problem with nominals changing and I almost always start programs with external alignments. The one time that I did not do this recently I had all of the nominals change. This same program also started with a level and origin to a plane with no rotation before going to DCC. I'm curious if the same program would have changed nominals if I had recalled a complete external alignment and then used this as the recall alignment for my level/origin alignment. Perhaps pc-DMIS has trouble referencing the machine csys but does not have trouble if you give it an explicit external alignment to reference.
Anyhow, I can't test any of this right now. It would be very nice to lock down exactly what causes this behavior, exactly how to avoid it, and put that in a sticky so everyone who comes to this site can learn how to avoid this.
I wonder what it will do to vpt’s original program when AdjustLevelCommandRotation is set to False
I'm traveling so can't check this myself in pc-DMIS but there is another check box in the f5 setup window called "allow fine tuning of alignments". I have never really understood what this does. It kind of sounds like it is allowing pc-DMIS to make alignment modifications but I'm not sure this is actually what it is referring to.
Has anyone verified the idea that if you use a recalled external alignment at the beginning of the program it will lock down the nominals? I have almost never had a problem with nominals changing and I almost always start programs with external alignments. The one time that I did not do this recently I had all of the nominals change. This same program also started with a level and origin to a plane with no rotation before going to DCC. I'm curious if the same program would have changed nominals if I had recalled a complete external alignment and then used this as the recall alignment for my level/origin alignment. Perhaps pc-DMIS has trouble referencing the machine csys but does not have trouble if you give it an explicit external alignment to reference.
Anyhow, I can't test any of this right now. It would be very nice to lock down exactly what causes this behavior, exactly how to avoid it, and put that in a sticky so everyone who comes to this site can learn how to avoid this.
© 2024 Hexagon AB and/or its subsidiaries. | Privacy Policy | Cloud Services Agreement |