Autorun loads, but icons won't open.

[[Li...]]

So yesterday I was called out to one of the CMM's because the operator in the cell said the CMM is locked up (screen).  There are two icons on the main/home screen.  Each for the two machines that are in the cell. Each "Mazak" machine icon opens up to all the parts that specific machine runs.  

So, we are running into an issue where we can't get past the home screen of Autorun.  We pretty much need to go to task manager and kill Calypso all together. 

Currently we just have Calypso open, the programs are open and showed them how to switch programs between programs from the "window" drop down.

 

I will say that I have noticed that sometimes clicking autorun icons there has been an extended wait time, but they eventually open. On other CMM here they are all pretty fast, instantly opening. 

I don't know if this is a PC issue because we do need to have many security features/additions on all our PC's (Aerospace/DOD) or is this a Calypso issue.  I have older versions of the Autorun saved just in case they get wiped out or deleted on a Network location. I do this on all the CMM's, I've had one completely deleted before, how I don't know.  

On this specific PC the Autorun lives in the Inspection folder with the programs. On some I just have it in Windows "Documents"

 

What are some things I can look into, or have IT check out?  I don't want to recreate a new Autorun. UGH!!!! I don't think that would be the fix. I created a new one who's to say that will open as it should, per part number needing inspection. 

 

[[Ke...]]

If you haven't made a change to Calypso/your Calypso setup, then I would start with asking IT what changed since the last time you know for sure it was working. Even if they didn't make the changes themselves, they should be able to look at log files and find out if there is that level of monitoring and security, and possibly have you try running the autorun to see if they see any security flag or block it. If there was nothing changed on that side, then start digging into the autorun related items like programs, filepaths, harddrive space, etc. You could also make a backup of the ARN file, and try dropping a copy  of the ARN from the working machine to the nonworking one, if they are identical, or try making a new simplified autorun just to test if opening a few layers deep like your old one works, in which case it may just be your old autorun being busted somehow, or if autorun is being jammed up by something at the pc level. 

[[Li...]]

I will get with IT and see if they can help.  On the main screen there are other links that seem to open up fine.  I was messing around with this issue today. The thing just seems to be acting funny. 

Every month on usually a Friday all the PC on the shop (floor PC's and personal) have security files installed. This is forced by corp IT.  I'm not sure if anything happened over the last two weeks of December IT wise because a lot of people were off including me.  Monday was our first day back and to my knowledge this is the start of our issue with this one CMM PC. 

I'll make a new "quick" Autorun and see if it has any issues.  Regular Calypso works just fine.  I did try an older version of this CMM's Autorun file (backed up from 5/2025) and it didn't act right either, still froze up when trying to open up an Icon. That's what makes me think something was recently changed by some sort of forced IT security packet or update. 

[[No...]]

In the past I noticed extremely long loading times of the *.arn file when Autorun accessed resources on the network (like icon images stored on a network location). But from a certain Calypso release on this issue was gone. I can't say if Zeiss had done something to speed it up or if there was simply a change in our network infrastructure that happened around the same time that release was installed. Nevertheless, it may be worth to check for any network stuff being accessed in the *.arn file. You can do this by loading the file in a text editor. It doesn't necessarily have to be something that is actively used right now. It could as well be an old path that is no longer present but still shows up in the file and may make Calypso cough. If I scan my *.arn, which has grown for nearly two decades now, I always find old stuff like that.

Edited 11 hours ago