OK guys, I am confuzzled. I no longer continuously program, but have multiple techs that do. We have a trainee that has been working on one of our CMM's on an off shift (we actually have 3 training right now, but this one in particular...). Last night, he sends an email stating that he was just sitting there running a program on a part, and the "screen went blank, then black, then back to home, with PC-DMIS closed". I'm thinking " OK, We had a software crash". Just turn off the machine, and reboot the desktop and turn the machine back on in a minute or so. then open DMIS, and it should work, right? He goes to open a program from the server, and the data in the command screen is missing. He restarts the computer multiple times, and no change.
This morning, my lead trainer, myself and one of our trainees each logged onto that CMM (we have 3), and could not reproduce the condition he talked about. All of our files came up with the data in tact, so we all assumed that he must not have restarted the machine, and only restarted the desktop. Since none of us could reproduce the condition, we waited until he came in on the off shift to ask. He opened up a program from the server on that same CMM and what he came up with looked like the left side image. We moved him to a different CMM and pulled up the same program, and it came up like it should have, in the right side of the image. I've never seen anything like this happen before.
Does anyone have ANY idea what could have happened, before I go put in a support ticket with Hexagon and have a long, drawn-out process of trying to get them to help figure this out?
Admin Privileges are paramount for PCDMIS to operate without crazy windows interaction issues such as this. Hexagon has produced a list of registry keys and directories that EVERY user that logs into that device should have admin rights to. I've attached it. If you don't want to deal with IT for each person who logs into the machine the other option is to establish a common windows login for all to use (some IT dept's won't allow this).
Maintaining a library of "validated" measurement methods is super important. We set all our routines within windows to "Read Only" to make sure they remain unaltered.
Admin Privileges are paramount for PCDMIS to operate without crazy windows interaction issues such as this. Hexagon has produced a list of registry keys and directories that EVERY user that logs into that device should have admin rights to. I've attached it. If you don't want to deal with IT for each person who logs into the machine the other option is to establish a common windows login for all to use (some IT dept's won't allow this).
Maintaining a library of "validated" measurement methods is super important. We set all our routines within windows to "Read Only" to make sure they remain unaltered.