Programmatically add tips to the probes list...

Caemgen I am doing a lot more than what I posted . I am opening pcdmis and searching through a program for the probe build and all tip angles, deleting any duplicates , then writing those to a text file. Closing, then reopening pcdmis and reading in both the probe build and tip angles, then calibrating said tips. But the problem is the guy before me who set up everything when we converted from measure-max to pcdmis, made all probe builds machine unique. So for example on our Sheffield Endeavor CMM’s he called a probe, “1mm_with_extension”, but for our globals he called it “1mm_with_extension_adapter”. Then on our D8’s it’s called “1mm_with_extension_tip1”, because that head does not index. And now we have thousands and thousands of programs saved with these unique probe files So the challenge for making a one shoe fits all auto-calibration routine has become quite cumbersome. I have a text file on each CMM that I read in, then based on what machine the probe is being calibrated on , I need to input the correct probe builds or else my script will error out . So I think the sporadic behavior might be due to doing so much, opening/closing/re-opening the app, some kind of timing issue, or something else. I haven’t gotten a chance to test more. At first, I noticed multiple instances of pcdmis being opened, and I thought I fixed that because my application seems to work great when I run it on my offline seat. But, when I run it on the cmm it’s telling me an object is not declared for my “Currprb” string. So the string is empty which results in it bombing out because it has no probe file to add the tips into. And also I’m not the only one who has experienced weird behavior when dealing with the probe objects . I’ll keep tinkering whenever I get some free time. If I get it working properly I will share it with y’all!

Caemgen I am doing a lot more than what I posted . I am opening pcdmis and searching through a program for the probe build and all tip angles, deleting any duplicates , then writing those to a text file. Closing, then reopening pcdmis and reading in both the probe build and tip angles, then calibrating said tips. But the problem is the guy before me who set up everything when we converted from measure-max to pcdmis, made all probe builds machine unique. So for example on our Sheffield Endeavor CMM’s he called a probe, “1mm_with_extension”, but for our globals he called it “1mm_with_extension_adapter”. Then on our D8’s it’s called “1mm_with_extension_tip1”, because that head does not index. And now we have thousands and thousands of programs saved with these unique probe files So the challenge for making a one shoe fits all auto-calibration routine has become quite cumbersome. I have a text file on each CMM that I read in, then based on what machine the probe is being calibrated on , I need to input the correct probe builds or else my script will error out . So I think the sporadic behavior might be due to doing so much, opening/closing/re-opening the app, some kind of timing issue, or something else. I haven’t gotten a chance to test more. At first, I noticed multiple instances of pcdmis being opened, and I thought I fixed that because my application seems to work great when I run it on my offline seat. But, when I run it on the cmm it’s telling me an object is not declared for my “Currprb” string. So the string is empty which results in it bombing out because it has no probe file to add the tips into. And also I’m not the only one who has experienced weird behavior when dealing with the probe objects . I’ll keep tinkering whenever I get some free time. If I get it working properly I will share it with y’all!