205 Command/macro

[[Ri...]]

Anyone encounter this error, and have a solution for it?

I have a measurement plan that I've ran for over a year now that when I gave it to another person to run, there is a particular set of features that when measured cause this error pop up. They can continue the run by unchecking clear existing results, but it's annoying.

I've tried the usual of deleting those features, and re-programming them, updating Service Packs, and I even created a brand new measurement plan, but I did bring over all of the characteristics/features from the original. Nothing seems to work.

I have two hail-marys of deleting Calypso and starting with a fresh install, and/or writing the measurement plan from scratch. I really don't want to do the second option.

Any and all help is greatly appreciated.

Thanks.

[[Ja...]]

I had this error once where some of my start alignment features were being used later to guide other features. Since the start alignment was manual, we would occasionally shank on this one chamfer, throwing the vectors for that cylinder (and its resulting axis) way off (somehow the alignment was still good enough to navigate through base alignment though). Then, when it was time for those actuals to be recalled, I'd get the error. I don't know if you're using a manual start alignment or not, or if any of your features are at risk of shanking, but that's my .02 cents.

[[Sc...]]

Richard,

We had been encountering this error at the end of 2019 - and had noted this in a different forum...

All,

After speaking with an Applications Engineer on the Zeiss help line he suggested updating our service pack, as we were three back on the 6.6 (2018 Calypso). To date we haven't seen this again, and shortly we'll be updating to 2019 so hopefully this has eliminated the issue. He did note that he looked (some) for the specific error and couldn't find anything specific on it and based on our conversation noted the service pack update should (most likely) take care of it.

Ttocs72


Note: Since updating to 6.8 in January we haven't seen this issue at all.

[[Ri...]]

Please sign in to view this quote.

Already on 2019, and tried updating, and it didn't help.

[[Ri...]]

Seems to stop in a particular location, but not always.

I pulled the Calypso Log file, and it wasn't that helpful. Lol.

2020-08-26T16:54:01.850Z	error	Unknown	Unknown	0000	Key not found: #actualCFName
2020-08-26T16:54:04.741Z	error	Unknown	Unknown	0000	Key not found: #actualCFName     X 1
2020-08-26T16:54:04.743Z	error	Unknown	Unknown	0000	Key not found: #actualCFName
2020-08-26T16:56:27.531Z	error	Unknown	Unknown	0000	Key not found: #actualCFName     X 1
2020-08-26T16:56:27.534Z	error	Unknown	Unknown	0000	Key not found: #actualCFName