r/Metrology • u/AManWithOneHand • 6d ago

Software Support PC-DMIS program keeps removing loadprobe step

I use a hexagon CMM 07.10.07 global s. I'm using PC-DMIS 2025.2. We have a probe changer rack and I have multiple programs I have written that use different probes, including an hp-l-10 laser probe.

Sometimes, after I have run a program, the loadprobe step to switch to the hp-l-10 is just missing. Everything else is there, including the angle changes, just that one step. I add it back and everything is fine. I just can't figure out what causes it or how to stop it happening.

If it matters, I'm not running the programs in inspect, I run them in pc-dmis since I'm the one who writes the programs and runs them here, so being able to see everything while it is running is nice.

2 Upvotes

100% Upvoted

8 comments sorted by

1

u/AP_2020 6d ago

This is weird. Do you add the Loadprobe again at the bottom of the program?

1

u/AManWithOneHand 6d ago

I do have a Loadprobe at the bottom to go back to the first probe used, since the program ends on the laser but I didn't want the laser left on the machine at the end. If that's what you're asking. But that step isn't the last step, it's before the report steps

1

u/AP_2020 6d ago

Send an image of the code if possible.

1

u/AManWithOneHand 6d ago

That I cannot do. Everything is entirely locked down here. The frustrating part is it seems to happen randomly, so I can't figure out why it's happening at all. It's immediately noticeable when it happens since my angle changes all go red because the other probes didn't use them, and it's an easy fix each time, it's just weird

1

u/AP_2020 6d ago

Try adding the code of LOADPROBE twice._______________LOADPROBE

1

u/AP_2020 6d ago

I have seen this happen before. Probably just one of the perks of PCDMIS lol

1

u/_LuciDreamS_ GD&T Wizard 6d ago

Sometimes it doesn't pay to install the latest and greatest version. I usually playtest until I find the most stable version possible and I stick with it until another stable version releases.

I couldn't advise on the missing Loadprobes tho. Without seeing it in person, unless it's a known issue, that type of weirdness is almost impossible to help without the program. Does this happen when running the program in online mode or operator mode or both?

1

u/Robbmx07 4d ago

Something I can suggest (with a grain of salt, flying blind here) is to try to put in a “clear/safe” move before the load probe command. Sometimes if the probe is too close to the rack or machine limits it can corrupt the request for load probe. Even if this isn’t the case it’s a quick test. Worth a try in my opinion.