Rename Machine Tab - All Data Lost?

[[No...]]

Recently, I tried to rename our new Contura in Calypso 2022. After doing so, all machine data was erased, including stylus systems. Practically everything in the config folder had been reset to defaults. Luckily I had a backup.

Now, I can't completely rule out the possibility that I clicked the wrong button, but I doubt it.
So, is it normal that renaming the machine results in a complete wipeout? If so, is there an alternative way to rename without losing any data? Maybe by manipulating the config (values) files?

[[Je...]]

Please sign in to view this quote.

Norbert, I've experienced this in the past as well. It seems to work a lot like saved measuring points in that when you change the feature's name (or machine tab's name), the string that joins the feature to the saved data doesn't dynamically update.

[[No...]]

Our second Contura will be ready by toworrow. Then I'll have the chance to explore, as it needs to be renamed as well. 🙄

[[Je...]]

Were you connected to the CMM/Simulation Machine tab? Connected to any machine tab? I have seen issues specifically when connected to the tab that was attempting to be renamed. SQL likes to get in the way of proper migration of files.

If you encounter an error with a machine tab (after renaming or it disappears altogether), review the link below from our Portal Knowledge Base.

https://portal.zeiss.com/knowledge-base ... &id=483015

[[No...]]

Please sign in to view this quote.

Unfortunately, I don't remember. Possibly yes. But why should it reset my Contura to a Prismo with a default measuring volume and set everything else in there to defaults?

On the the second CMM, I'll first copy away the whole CALYPSO folder, then I can experiment freely 😉

Please sign in to view this quote.

Sorry, but the knowledge base is.....

[[No...]]

Update:
I tried to rename the second machine, but almost the same thing happened: The machine type stayed the same, but things like the park position after homing and several other settings were reset.The machine was not connected at that time.

I think 'll be going the hard way, making screenshots of every setting and reconfiguring everything from scratch. 🙄
I've got to do that with a lot of other settings anyway.

[[Je...]]

Please sign in to view this quote.

The important directory to keep is the C:\Users\Public\Documents\Zeiss\CALYPSO\config directory. Make sure you turn off SQL Server before copying or do a fresh restart. If you get ANY copy error prompt then that is the indication that your SQL database did not fully transfer and that backup config will not work when needed.

Please sign in to view this quote.

Sorry Norbert, the US Portal Knowledge Base is limited to US region only. FYI - A common workaround for regionalized restrictions is to use a VPN or sometimes even web browser "incognito mode" may allow you to set a region to view...

[[No...]]

My problem is that as a common user I don't have permission to shut down SQL. But it doesn't matter as there are currently no styli in the database anyway. I'll be doing this only after I successfully set up the CMM. I've created a new machine tab now and copied all the settings over from the existing one. When everything else is configured properly, I will delete the old tab. Seems to be the safest way.

[[Je...]]

Please sign in to view this quote.

If you do not have proper user rights then a fresh restart should be sufficient. Copy the config directory BEFORE starting CALYPSO (initiating CALYPSO links the SDCO to SQL).

Every user should do this on a regular basis as losing your config directory is a very frustrating experience. Backing up your PCF files is definitely a step in the right direction as well. Config directories are very often corrupted by dirty power sources (power outages, surges etc). It is extremely highly recommended to put your PC at the very least, CMM also if possible, on a back-up power supply. Even if it only lasts 1-2 minutes but initiates a shut-down routine immediately after power-loss. Preventing the loss of a config directory even 1 time is usually worth the cost of the UPS.
The reason for the corruption is, in a nutshell, SQL is actively reading/writing the SDCO SQL all the time. If a power interruption occurs during data write then it corrupts the SQL database.

[[No...]]

Please sign in to view this quote.

I knew most of this and I regularly back up with Calypso's backup function. Our power source is quite stable. Outages are very rare.
But what I'm asking myself: When renaming a machine tab, why can't Calypso simply change the name in every location it is stored in? Instead it seems like it copies the existing config folder with the new name and tries to migrate the files in it to the new folder. Why all this hassle? If I would design such a process I'd do it in a way that would need the least possible amount of changes (only the name), just BECAUSE it's so error-prone.

[[Je...]]

Each individual version of Calypso may not control another versions files simultaneously. So "Renaming" isn't an option as a 7.4 install config folder cannot be renamed by a 7.0 install. Files must be copied and renamed during copy to allow for multiple installs. Also, as newer versions incorporate new functionality, older versions may not recognize the new code and cause errors. Hence the copied files so they can be properly amended for backward-compatibility.

Remember, Calypso, like most software packages, is backward-compatible. Almost no software is forward-compatible so moving something new into an older version will likely not be compatible.

[[No...]]

We don't talk about multiple versions of Calypso here. It's a new Contura with (currently) only Calypso 7.4 installed. I'm renaming the machine tab only within the same version (how would I even do it otherwise?), so it should "know" everything it has to deal with in the process.
I could understand if the Calypso developers had used the same internal functions for 'simple' renaming as well as for data migration between versions, but still something like this shouldn't happen.