Machine error?

[[Jo...]]

Hello!

Anyone familiar with this message? I came in this morning and the below error was on my screen from over the weekend. I tried to start Calypso but the error comes up and I can't connect. I powered the controller completely off and restarted the process, The drives don't want to turn on. Any ideas of something I can try??

Thanks!

image.png

[[Ri...]]

That error is when Calypso cannot communicate with the controller. Please make sure that the ethernet cord from the controller is plugged into the correct ethernet port on the back of the PC. In addition, please make sure that your IT department has not made any changes to the network settings for that ethernet card.

Sometimes it also just helps to reboot both the pc and controller.

If the drives aren't coming on, that is a separate issue. Make sure there is adequate air supply to the machine. In addition, the most common reason for the drives not starting (other than air) is that you are on a hardware stop.

[[Ow...]]

Just a shot in the dark here but, is the CMM computer connected to the companies network or world wide web?
I've seen I.T. make changes to IP addresses with their security software erasing the IP addresses.

You can ping the Zeiss Controller IP address to look for connection to CMM.

Click the start button in windows and type "cmd" in the search bar, hit enter, command window pops up, enter "ipconfig" this will tell you if you are connected to the controller and any other networks.
the cmm controller ip should be something like 192.4.1.199.

[[Jo...]]

I did find the below thread, but my hosts file looked ok


Re: KMGIO.DLL error-Can't make connection
Post by Lincoln Knott » Wed Oct 11, 2023 2:29 pm

We finally got this resolved. I had to enter lines to the host file located at C:/Windows/System32/drivers/etc. The host file was missing information. Pasted below is what a host file should look like. The host file that was not allowing connection on our Prismo was missing all 8 lines below. I could not ping "cmm_1"

192.4.1.200 cmm_1 CMM_1 #controler1
192.4.1.201 cmm_2 CMM_2 #controler2
192.4.1.202 cmm_3 CMM_3 #controler3
192.4.1.203 cmm_4 CMM_4 #controler4
192.4.1.55 cmmws_1 CMMWS_1 #computer1
192.4.1.56 cmmws_2 CMMWS_2 #computer2
192.4.1.57 cmmws_3 CMMWS_3 #computer3
192.4.1.58 cmmws_4 CMMWS_4 #computer4

These lines need to be in the host file.
The below is what a host file looks like on one of our CMM's that is functioning properly. I dont not know what casued the file to get corrupted. My guess is our IT security updates caused this somehow. You may not see carbonblack. It is something we use for IT security at our company.