hexagon logo

Vision Crashes When Measuring Circles

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.

What's going on?
Parents


  • The alignment takes 4 cylinders, 7 hits per ring, two rings, along the OD.
    1 point is taken on the face, and a plane of 6 points is taken inside a notch (to align upright)

    I level Y+ to the cylinder, rotate ZPlus to the plane about YPlus, Rotate YPlus to the cylinder about XPlus, Set X&Z axes to cylinder, set Y axis to face point.

    Then I measure a line on the face using vision, and I measure a line on an undercut. After that is the hole that crashes.

    If the hole is there, it crashes right away.
    If it's not, the program rotates 180° and measures the hole, and crashes right away


    Can you post the code ?
    Why do you rotate twice ?
    Did you change any parameter on the PC (driver, video card...) ?
    Does the rtary gives correct values when it turns ? (for example, if the rotary turns around Y+ (part coordinates), Z and X should change of sign on a 180° rotation.

    You could also check all the dlls...
Reply


  • The alignment takes 4 cylinders, 7 hits per ring, two rings, along the OD.
    1 point is taken on the face, and a plane of 6 points is taken inside a notch (to align upright)

    I level Y+ to the cylinder, rotate ZPlus to the plane about YPlus, Rotate YPlus to the cylinder about XPlus, Set X&Z axes to cylinder, set Y axis to face point.

    Then I measure a line on the face using vision, and I measure a line on an undercut. After that is the hole that crashes.

    If the hole is there, it crashes right away.
    If it's not, the program rotates 180° and measures the hole, and crashes right away


    Can you post the code ?
    Why do you rotate twice ?
    Did you change any parameter on the PC (driver, video card...) ?
    Does the rtary gives correct values when it turns ? (for example, if the rotary turns around Y+ (part coordinates), Z and X should change of sign on a 180° rotation.

    You could also check all the dlls...
Children
No Data