hexagon logo
Register Sign in
  • Replies 7 replies
  • Subscribers 223 subscribers
  • Views 74 views
  • Users 0 members are here
Options
Related

Global HTA Probe Crash Error

dsmith8532
Hi, all. I am brand new to this forum and brand new to CMMs. I have been coming across an error with the Hexagon Global HTA where it detects a probe crash (running PC-DMIS and Blades) when there is no contact made with the part. I'm just curious if anyone else has come across this issue or if this is some known issue that has a fix for it. I'm unsure if this error is the result of excessive vibration (I don't believe it is but have been unable to reproduce the error while monitoring vibrations using Pulse) or if there is some software bug that is causing the error...or even if one of the optical probes is going bad.

I wish I had more information, but since I'm new to all of this, I just wanted to pick the brains of the forum users to see if there is any information out there. Thanks.
  • Is this a machine alarm, or a PC-DMIS alert from some kind of Collision Detection analysis? PC-DMIS' simulation-based collision detection often shows things as crashes that aren't. It's still useful, but you have to know what to ignore. Slight smile
  • I had to look up that HTA, that's a really cool piece of equipment! I agree with , you are probably programming the measurement somehow without enabling enough clearance to avoid collision with the machine and the part. Based on the video on the hexagon page, i'm absolutely in the dark about this, but if you have an edit window, you surely would need to incorporate a clearance cube or clearance plane within your routine to avoid this error from presenting itself. You are lucky it has a warning, lol. Back in the day, you would just wreck your probe sensor and part with just one wrong move command!
  • in reply to mbatten
    It is either a PC-DMIS error or a Blades error, but definitely not a machine alert. The problem is that it ends the program and must be restarted, so I can't really ignore it unfortunately.

    I also was monitoring crash and vibration data real time using Pulse and that software doesn't register excessive vibration or a crash, even when the error is thrown that it crashed.
  • in reply to louisd
    It is very cool for sure. These programs have existed before my time here, but I can say with 100% certainty that the probe is not actually crashing into anything. I have observed it multiple times while running to ensure that it is not physically crashing and to determine where the "crash" occurs, and it appears to be happening in the same location when it happens. Sometimes a re-calibration temporarily fixes it, and we can run a few more parts, but not always.

    We have 5 of these machines that all run the same parts with the same fixtures, but this one in particular is giving this issue consistently.
  • in reply to louisd
    Have you done a code comparison between machines to make sure they are all the same routine/method of measure?
    In PCDMIS, you can go file: edit window print, then select print to pdf (and choose a directory). Press F4 to print/Spit out the routine for each machine. Then go into MS word and there's a comparison tool within the "Review" section, that works great for this, it can even bring in the PDF format routines.
  • in reply to louisd
    I have not done that, but that's a good idea, so I will give it a shot. Thanks
  • So just to update anyone interested, I'm a fool. These machines use Quindos, not PC-DMIS...oops. Hexagon came to look at the machine and there was a failed pressure electric switch, and the rotary table pressure was a little too high which was causing the rotary table bearing to vibrate during operation. He replaced the switch, turned down the pressure, and the machine ran fine all night, so it looks like it's good now. Thanks for your replies, though.
© 2024 Hexagon AB and/or its subsidiaries. Privacy Policy | Cloud Services Agreement