2019R2 Autocalibrate command will not run

[mmaxvbawizard]

So we were successfully running our tip cal program on an older CMM that was just replaced with a new global. The computer was never replaced, just plugged into the new processor. After the technician setup and calibrated/mapped the new CMM, we ran our old tip calibration with success after making a few coding adjustments (like move points to tell the probe to go ot the new sphere position). We then ran a part and everything jived correctly.

Then we cam back from our holiday vacation and I load and try to run the tip cal program again and it skips over the autocalibrate command.

We can edit the loadprobe commands and calibrate that way, but not by running the program from the beginning.

[DAN_M]

Plz post code so we can see whats happening.

Code goes on forum like this (remove spaces in the brackets when you do it)-->

[c o d e]


copy/paste code here


[/c o d e]

[KIRBSTER269]

F3????????????? or Mark Checked????

[mmaxvbawizard]

Before I post code, another problem I forgot to mention is that this crashes the software. And no, F3 was not a factor, and mark used and global used did nothing.

The real pain is that WE ALREADY RAN THIS ONCE. And now it won't run.

Apparently going on vacation was the issue.

[DAN_M]

something changed that you're not seeing..happens to the best of us.. thats my first bet.

its possible that your code is "corrupt" and there are ways to address that as well.... before we go down that rabbithole lets see your work

[KIRBSTER269]

You already do a complete shutdown and reboot?

[John Kugler]

You already do a complete shutdown and reboot?

Numerous times. Parts still run OK as well. Older versions of the program will not work, and a program from another machine will not work either.

[KIRBSTER269]

I have a brand new machine, numerous times issues pop up, machine stalls, loses communication, during Calibration knuckle crashes into Calibration sphere, Reboot, and machine restart, fixed it. Not saying it will, but that would be the first place I started with and sometimes it fixed it, sometimes it didn't. trying to rule out the easy.

[mmaxvbawizard]

So this is the original code from when we ran it on 12/22/2020:

AUTOCALIBRATE/PROBE, PARAMETER_SET=STATION421, QUALTOOL_MOVED=YES_MANUAL,
CHECK COLLISION=NO, SHOW_SUMMARY=YES, OVERWRITE_RESULTSFILE=NO
BEGIN AUTOCALIBRATE RESULTS FOR PROBE REFERENCE TIP USING SET STATION421
Probe file=REFERENCE TIP Date=12/22/2020 Time=2:52:17 AM
Check Collision Disabled
0DEG_0_0_1 CENT X 541.963 Y 1001.919 Z -724.088 D 24.996
T1A0B0 THEO X 0.000 Y 0.000 Z 161.520 D 2.000
T1A0B0 MEAS X -0.835 Y -0.313 Z 161.532 D 1.990 StdDev 0.001
END AUTOCALIBRATE RESULTS FOR PROBE REFERENCE TIP USING SET STATION421




After trying to run the program, and it skipping over the autocal command, and me stopping the program the code changes to this:

AUTOCALIBRATE/PROBE, PARAMETER_SET=STATION421, QUALTOOL_MOVED=YES_DCC,
CHECK COLLISION=NO, SHOW_SUMMARY=YES, OVERWRITE_RESULTSFILE=NO
BEGIN AUTOCALIBRATE RESULTS FOR PROBE REFERENCE TIP USING SET STATION421
END AUTOCALIBRATE RESULTS FOR PROBE REFERENCE TIP USING SET STATION421



Also the Loadprobe dialog pops up for the station where I stopped it....if I hit OK the software crashs, if I hit Cancel twice, it closes to the edit window, and when I do file close it throws a PCDLRN error:
The save process can not find the start of the Measurement Routine.

[mmaxvbawizard]

You already do a complete shutdown and reboot?

I've already done that numerous times

[KIRBSTER269]

Just trying to rule the simple out.

[mmaxvbawizard]

Oh yeah, me too! I'm hoping it is something simple

[MetsoMetrology]

Are your parameter sets still good? Why not create the program again?

[mmaxvbawizard]

Computer never changed, so parameter sets are still good. program is huge and as mentioned this ran right before christmas.

Somehow I wonder if COVID is involved...it screwed up everything in 2020, why not this?

[cvelisetty]

Hello @mmaxvbawizard,

I have seen this type of issue at one of our customers in India. After 3 days of doing trial and errors, we were not able to find the root cause. We moved all the files (probe, probe result files) to a different drive and mapped them again in the search directory.

For some reason it worked. This is one in a million case (IMHO). May be this could work for you. You may want to give it a try?

[mmaxvbawizard]

Thanks for the suggestion, yup tried this, didn't work

[JEFMAN]

December :
AUTOCALIBRATE/PROBE, PARAMETER_SET=STATION421, QUALTOOL_MOVED=YES_MANUAL,
January :
AUTOCALIBRATE/PROBE, PARAMETER_SET=STATION421, QUALTOOL_MOVED=YES_DCC,

Did you try to calibrate once, just F9 on the loadprobe, then selecting A0B0 and calibrate the tip using sphere moved manual ?
And then running the autocal.

[mmaxvbawizard]

Thanks for the suggestion, yup tried this, didn't work

[benj118]

Rebuild probe file, possibly corrupted?

[mmaxvbawizard]

Thanks for the suggestion, yup tried this, didn't work

[DAN_M]

This may be painful depending on how you calibrate...but the probefile might be corrupted. You may have to delete it & rebuild it along with your parameter set(s) associated with that file.

[mmaxvbawizard]

Thanks for the suggestion, yup tried this, didn't work

[DAN_M]

sorry thats all i've got =/