I recently discovered an unsettling characteristic with PCDMIS reporting. If an operator skips a feature being measured because a part feature is so far out of tolerance the CMM faults out, PCDMIS will print out the value for that feature from the previously inspected part. For example: Say an operator bores a hole undersize to the point that the probe makes an unexpected hit and faults out, the operator can click the "SKIP" button and continue through the program and PCDMIS will fill in the value for that skipped feature from the previously reported part. IF the previous part was good then the report for the deviant part is good and the customer gets a bad part. I experimented with this by skipping every feature on a part by interrupting the probe with my finger and "skipping" to the next feature. I got a full report that was the exact duplicate of the part I inspected beforehand. I have yet to get this resolved by Hexagon tech support and would appreciate your help. I am new to PCDMIS(9 months) and I have not delved into report templates. I am using what became the standard here set down by my predecessor. Thanks in advance.
Later versions of PC-DMIS (I don't know from exactly which version) have the possibility to output skipped features in 'text mode' when using (at least) the TEXTONLY report. In that way, it is quite obvious which features were skipped.
This behavior may have been turned off in SettingsEditor, entry IgnoreSkippedFeatureRule, which should be 0 (zero) if you want to distinguish skipped and executed results.
Later versions of PC-DMIS (I don't know from exactly which version) have the possibility to output skipped features in 'text mode' when using (at least) the TEXTONLY report. In that way, it is quite obvious which features were skipped.
This behavior may have been turned off in SettingsEditor, entry IgnoreSkippedFeatureRule, which should be 0 (zero) if you want to distinguish skipped and executed results.
