Running PC-DMIS 2013 MR1 SP5 on Windows 7 PC connected to an Optiv Performance z443
------------------------------------------------------------------------
Hello!
I have several part programs that run though to completion using touch probes
I received a part that requires vision due to the crossholes (there are a lot) being generally too small
So I created the part program and was faced with many issues...
(Such as all of the numbers randomly changing by thousandths, leaving me to clean up everything with 0+0's!)
However, it is done, and I'm trying to check it, but it crashes at the first measurement.
Strangely enough, it worked before!
I have not been able to run this program all of the way through, it only crashes when it measures a crosshole.
The way the program is set up is it performs an alignment using the touch probe, then switches to the camera
The camera looks for a crosshole, and if it does not find it, it rotates 180° and tries again (where it will find it, or we made the part wrong!) Otherwise it continues as normal.
However pretty much since I added the "OnError" stuff it starts crashing at the hole.
I was able to verify that it works (the OnError) previously, and, upon this discovery, moved on to programming the rest of the part.
I needed to get the crosshole perfect or I couldn't measure the part, you see.
So it worked for a bit, but not anymore, and it keeps crashing. Strange!
I tried to measure a different hole in the same program, and had the same issue.
Can you start from scratch and rewrite the program? Maybe some how the program is corrupted.
I honestly haven't played with On Error and vision. I know some machines don't function correctly with On Error. Maybe On Error doesn't function correctly with version 2013? Try contacting Hexagon to validate.
Can you start from scratch and rewrite the program? Maybe some how the program is corrupted.
I honestly haven't played with On Error and vision. I know some machines don't function correctly with On Error. Maybe On Error doesn't function correctly with version 2013? Try contacting Hexagon to validate.