Path element does not exist

[[No...]]

Today I was in the process of setting up Calypso 2023 for productive use when I encountered the following error in Autorun that never before occured in older releases:

"Path element <XYZ> does not exist"

The program that causes it is very old and contains no measurements at all. All it does is get a certain stylus from the rack and drive to a park position. BUT: It doesn't use any path elements and no 'official' park position! Instead the positioning is done by a strategy element in a point feature. The reasons for this don't matter here.

I suspect this error may have to do with the new park posiiton option in Autorun:
But I can't find any information on what it does, neither in the release notes nor the help file.

The name of the path element in the message appears in the inspset file of the program, but it's probably only a remnant from when the program was written and the once existing path element was deleted later on.

So does anybody know why this error occurs and how to fix it without editing the program? I fear this might happen with more old programs in the future, so I'd really hate having to find and edit them all.

Update:
It also happens when starting a normal CNC run outside of Autorun.

[[No...]]

After some research I was able to identify the cause of the problem. There's currently no remedy, but a workaround. Support has been notified.

The issue occurs in Calypso 2023 with all programs where an existing park position has been deleted in the way that was common up to version 2022:
Avoid doing this in Calypso 2023, as the item won't be removed completely!
Calypso 2023 has now built-in checks for the presence of path elements prior to CNC start and will display the above error if it finds an incompletely removed position.

Instead, open the new park position dialog and use the trashcan button:
If you already deleted the position the old-fashioned way, just open this dialog, close again with OK and resave the program. This will remove the path element completely and also works with old programs.

[[Ky...]]

Hello Norbert,

Can you tell me which service pack of 2023 you are using? This looks very similar to a bug that was resolved a while ago. If it is what I think it is, then yes, it does have to do with that park position option in autorun, though I have not seen it happen in normal Calypso.

If you aren't on the latest service pack, I would recommend updating and checking it then.

[[No...]]

I'm using 7.6.12 which is the latest service pack according to the portal. I didn't apply the latest patch yet, but the patch notes say nothing about this issue. By the way, support has registered the error as #387777.

[[Ky...]]

Hello Nobert,

I see. Then it doesn't seem to be the same thing. It just sounded strangely similar so I thought I would ask.

The issue I was thinking of was resolved already in 7.6.12, so no need to go to the patch (unless whoever you are working with on support tells you otherwise).

[[No...]]

Meh.....once again a typical answer from Zeiss support. 🙄

In a nutshell:
We won't make any changes to Calypso, since there's now the new park posiiton dialog, and when you use that, it won't happen.

Sigh...yes, BUT it happens with OLD programs from OLD CALYPSO VERSIONS where the park position was deleted the OLD WAY!
And by the way, now that there is this new shiny dialog window, why don't you at least REMOVE the old list of path elements, so it can't happen ACCIDENTALLY in the future??

Sometimes I get the impression I'm talking to a group of toddlers 🙄 😭
Is that really what we pay 4000 EUR per year and CMM for?

[[Ke...]]

So, I have been experiencing this a few times in the last with running in Calypso.
I have tried the latest service pack Version 7.6.16 (24.06.2024) and still no fix.
It's a real issue when it happens on second shift because they have no ability to correct it because they can't alter programs.
Is there any knowledge of this happening in 2024 version?

[[No...]]

I've described the workaround somewhere above, but as you say, operators without permission to alter programs won't be able to use it.

I fear it will continue to be an issue even in future versions unless the workaround is applied once to each program concerned. The change that caused the problem was not the way park positions are created or deleted, but a new check for the presence of the path elements that was added in 2023.
So the basic issue (incomplete removal of deleted path elements) has always been there but didn't cause an error in previous versions.