I'm looking at developing a vba script in Excel to pull the theo, target, and dimension nominal values and generate a worksheet showing them. I would then apply conditional formatting to highlight the Target and Theo values that do not match the nominal values in the dimension statement. We have hundreds of CMM Programs that have been used and modified over many years and versions of PC-DMIS. I have been manually auditing data and finding points here and there where the T does not correlate with the XYZ coordinate deviations. I have found many auto vector features where the target and theo do not match the nominal in the dimension. A script that actually grabbed all the nominal, including the ijk vectors would be very useful to identify these issues. The operator would need to then verify the feature and correct the nominal that was deemed incorrect. Maybe there is such a tool within PC-DMIS to check for this. If that is the case, maybe one of the Guru's on here can point me to it. I am not a PC-DMIS user myself, so I cannot poke around in PC-DMIS to look for such a tool, but I work very closely with a group that does offline programming.
If all of your programs have random Target deviations, then it sounds like you have/had a systemic issue. The target value should match the THEO, unless it is specifically changed in the edit window, or it could mean that the alignments are not fully constraining the part. If the latter then, even when the target values are fixed, it will just keep happening.
Not necessarily - the target values may have changed when the feature is so off that the CMM can't find it/hits it too early and the user/operator ansers "yes" to the question "update target values..." after measuring the feature.
If all of your programs have random Target deviations, then it sounds like you have/had a systemic issue. The target value should match the THEO, unless it is specifically changed in the edit window, or it could mean that the alignments are not fully constraining the part. If the latter then, even when the target values are fixed, it will just keep happening.
Not necessarily - the target values may have changed when the feature is so off that the CMM can't find it/hits it too early and the user/operator ansers "yes" to the question "update target values..." after measuring the feature.
