Hello again!
Running PC-DMIS 2013 MR1 SP5 on a Windows 7 Desktop for an Optiv Performance 443
---------------------------------------------------------------------------------------------------------------------------
(I posted something similar in Vision, but I'm not sure if the problem is directly related to Vision, or the items in the title.)
Having some trouble again, I'm not really sure to begin.
The problem I'm having is I can't measure a hole without PC-DMIS crashing and having to restart!
Essentially I have a part mounted in a rotary table.
I do an alignment with a TP200, then switch to the Camera, where I perform a measurement and then check for the location of a hole.
Using OnError, I check if the hole is there (If EDGE_NOT_DETECTED, GOTO/{label})
The label moves the rotab 180°, adjusts the alignment 180°, and remeasures the hole (it goes to a label above the hole)
It repeats this process until it detects the hole, or does not detect it twice.
The construction of the hole has constants for the THEO values, and uses the "plus 0" rule for the TARG values.
And this is where the problems arise.
I can't use the data!
I'm not entirely sure if it's the alignments, the OnError, a bug in Vision, or my hardware,
however...
As soon as I measure the hole, it attempts to either create a variable or an alignment with the circle measurement.
It freezes at this point, and crashes, and attempts to send the report to Hexagon.
I will post the necessary code, but I could certainly use some help. Things that would help the most:
- A better (as in working) method for checking a hole, if not there rotating and remeasuring
- A summation of the process for how to go about something like that (as in 'do this, then do this, but
don't do that)
- An idea of what I may be doing wrong
- A simple test program that checks for something (a point would work, I really don't care) and if it doesn't find it, rotates and rechecks, then
actually uses the data!
Things that will
NOT help:
- Worrying about the alignment, or construction of OnError (because it works; the current program rotates and remeasures, but doesn't like when I try to use the points)
- Different ways to measure the hole. (The hole gets measured, there is a feature that is the hole, and I can recall the hole. Changing to FIXED_RAD or other won't help)
- Generally useless questions (like what kind of part it is, how the initial alignment happens, how many points I'm using, etc) that don't pertain to crashing at a hole.
---------------
I wish to reiterate.
The Alignment
WORKS, the construction of the circle and corresponding OnError/Label section is
OKAY, the probe is able to
SUCCESSFULLY find the hole, whether
it be at 0° or 180°, and take a circle measurement. The circle measurement
IS ABLE to draw the little green dots, therefore more-or-less measuring the hole.
It just crashes when trying to pull any info from the hole.
As always, any help would be appreciated.
