Okay now its kind of making sense.
What we do is use cell to call what ever job that we need to run and then just loop in that required program until a job changeover is required. This means we may not return to cell.scr for days.
does PGNO_VALID need to be issues whenever we stop the robot and start it again, even if we don't go back to cell.
Also we noticed this only happen when we stop the robot enter the cell, and step through the program with the pendant.
We were thinking it had to do with moving the program pointer by using block selection. However it does the same thing if we just step through the program.
We also noticed that it does not matter if we are in ext/aut, T1, or T2 we get the same issue.
If we hold the enable APPL_RUN turns on the press the Start button its still on, if we let go of the Start button it stays on, however if we let go of the enable while still holding the start button
if goes off and the only way to get it to turn on again is to release both and then confirm messages (even if there are none) and press enable the start
So if in T1 we can cause the same issue but not correctly releasing the button and have to follow a set way to reset it
with that line of thought it is possible that the way the robot is being started in ext/aut could be my issue not anything with the robot itself.
There are 6 different timing charts in the manual . Two for automatic system start and then the rest for restart.
do i use that same start no matter what or use the automatic system start when we first load the job and need to call it from cell, then the restart sequence depending on how we stop the robot
Sorry for the long post
Also its 10 robots that do the same thing.