Dfncdh

[robertw]

Hello Everyone,
Occasionally our Leitz (running Quindos 6) 'stalls' with error S_2 CMWAIT CMWT$2 (A COM error I think). A simple 'Gold Enter' and it continues. I would like to trap this error using DFNCDH. My plan is to simply continue from the current point. All of the help in the LANEXT and PALLET manuals seems to want you to go to the start of the element or skip the points completely. Any ideas? Is it as simple as using SKIPPTS with NBR=0?

Thanks

Rob

[swojciechowski]

Please be careful, programming a error handler for an error of unknown cause is a bit risky. The better option would be to determine the cause of the error and fix it, especially if it is a machine communication issue. To progam the CDH to just 'continue' regardless of where the probe may be, could lead to a collision. One must think of the scenario in which this 'stalling' may occur prior to a probe change or with the probe under a part, to just blindly continue is risky.

Typically, if an error occurs during measurement, the safest would be to always prompt/warn the operator to ensure the probe is free to complete the next move, thus the CDH procedure would involve some sort of operator intervention and acknowledgement, similar to what you have to do now to continue.

To blindly continue with a CDH is more suited for calculation or analysis commands. For example, if while radius correcting APT's with the RCOR2D command and it errors, a CDH is very well suited to remove erroneous points and continue, without affecting machine movement. CDH's are also commonly used to 'trigger' after the probe has located, or not located a part, during a programmed 'search' probing. But again, to just blindly assume that the probe/machine is always free to continue after a generic error (or random error such as a communication erorr) is risky. Again, it is better to find the cause of this 'communication' error and fix it.

Please contact us for further help

Steven Wojciechowski
Hexagon Metrology

steven.wojciechowski@hexagonemetrology.com
401-886-2715

tech support 800-343-7933

[robertw]

Thanks for the reply.
When we had the machine calibrated last, we had the engineer take a look. The serial cable was replaced, but still the issue persists. It is very intermittent, but it always seems to rear it's ugly head just after everybody has left the building for the weekend and the machine has been left running. I appreciate your concern about letting the machine blindly continue after this error, but looking through many an error log I cannot see the error appear in any other situation. It is usually during either a CLP or PRBing, but it is not a collision. It's timing is random, but it does seem to occur during DO loops.
Any thoughts?
Thanks
Rob