In such a case I would create an AoA backup and take a closer look into the logbook file which is part of the AoA backup. If somebody made a change you will definitely find some hints within the logbook.
Did it change to something else, or is it empty? If someone has UI17 PNS_STROBE mapped to a digital input, and toggles true, it will wipe clear your "$shell_wrk.$cust_name" and your robot will just sit there doing nothing after you send it a start signal.
If it changed to something else, then I'd say someone is changing it.
Do you have a cold start autoexec program? It would be listed under SYSTEM > CONFIG
In such a case I would create an AoA backup and take a closer look into the logbook file which is part of the AoA backup. If somebody made a change you will definitely find some hints within the logbook.
Good idea, ill try that, thanks!
Did it change to something else, or is it empty? If someone has UI17 PNS_STROBE mapped to a digital input, and toggles true, it will wipe clear your "$shell_wrk.$cust_name" and your robot will just sit there doing nothing after you send it a start signal.
If it changed to something else, then I'd say someone is changing it.
It was changed to something. A non-existing program btw. However, the name is similar to existing programs, just a different number suffix.
Do you have a cold start autoexec program? It would be listed under SYSTEM > CONFIG
No cold start autoexec program, I just checked.
Did you ever get this resolved? I'm running into this now. Sometimes, on power up, the robot changes the OTHER program from 'MAINLINE' to 'PNS001', which doesn't exist on this system.
Nation, that can happen if you have the PNS UOP configured. I only configure UI's 1 thru 8 and UO's 1 thru 10. Hope that helps
That was it. Thanks for the help. Odd that the background logic that handles this doesn't just ignore those when set to other mode.
You need to be a member in order to leave a comment
