Jump to content
Private Messaging is activated - check "How to" on how to disable it ×

Unhandled exception: Message not understood: #rotationHead


---
 Share

Recommended Posts

---

Why is connecting to the CMM (Planner in this case) reliant on the rotation of a stylus? (Assuming this because I was editing a stylus, and the error report appears to be related to that task).

I was editing a stylus system, Calypso crashed. The name and rotation were changed prior to the crash.

There was no other recourse than to End Task Calypso.

And now I'm here, I Calypso will not connect using the RDS sensor.

I am hoping there is some file I can edit to change the Stylus name and rotation or have a Zeiss tech remote in and fix this.

Calypso 2022.

Please sign in to view this quote.

 

Edited
Link to comment
Share on other sites

---

Hello Richard,

this can happen if CALYPSO crashes when there is a SQL Database change and the Probe remains in an unknown condition, if you use CALYPSO 2024 you can send me your "equip" folder as a .zip file so i could try to repair it.

Path: C:\Users\Public\Documents\Zeiss\CALYPSO 7.8

 

image.png.6d6302ce5e11684a4cfc377d75b6ac5e.png

 

Link to comment
Share on other sites

---

I did not notice I left out my version, it is v2022. (A little frustrated over this).

Link to comment
Share on other sites

---
Posted (edited)

I have resolved this.

I renamed "actuConfig.dat" to "actuConfig.dat.old" and pasted in a slightly older file.

Lost a few articulations and maybe one stylus.

The big change was (It's not a text file, but it has clues) "sensorNameUnknown" and "holderNamenot_defined".

Both of these are from the older file, this eliminated the invalid probe name and or rotation.

The affected file had "sensorName3_2mm +X" and "holderNameCombo91".

The string "3_1mm +X" was 5_2mm -X" prior to the software crash.

Edited
Link to comment
Share on other sites

---

Edit for my reply above.

Calypso must be shut down prior to renaming and or pasting files.

Link to comment
Share on other sites

---

Good Morning Richard,

well done!

The easiest way is always to replace the Config with an up to date Backup. I can't stress the importance of regular backups enough 😄

I've never tried the solution that you mentioned, within Software Support we have this issue once every couple of month and most of the time we can fix it with access through a developer tool on the customer PC.

 

I will test your solution the next time im facing that issue again.

Link to comment
Share on other sites

 Share

×
×
  • Create New...