[Ri...] Posted September 20, 2022 Share Posted September 20, 2022 We have a Vision system called "O-Detect", similar to "O-Inspect" except it runs off some type of controller: Zeiss O-Detect CMM-OS NEO I've run into a problem where this controller doesn't like "Program Stops" being used. Once activated by a feature, it will crash the software and your only course of action is to shut it all down and restart. I've attached screen shots and the contents of the "Error Report". They should be viewed in this order: 1. Zeiss O-Detect CMM-OS NEO_Error 1.jpg 2. Zeiss O-Detect CMM-OS NEO_Error 2.jpg 3. Zeiss O-Detect CMM-OS NEO_using Programmable Stop Error.jpg 4. Zeiss O-Detect CMM-OS NEO_Error Report contents.txt They are in a ZIP file for uploading: Please sign in to view this quote. Due to multiple parts, this program has to run from the "Feature List". If ran from the "Characteristics List" the features for alignments run Secondary and or Tertiary features prior to Primary features. The primary Feature (Plane's in a Pattern) MUST RUN FIRST to establish a Z height and spatiality per part. I do have a Result Element as a Stop for now, but that is not a viable solution, as that runs from the Characteristic List. Any help is appreciated.Zeiss O-Detect CMM-OS NEO_using Programmable Stop Error.zip Link to comment Share on other sites More sharing options...
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in