1, Yes, that is the problem i dont know how to find (Im sure that PLC is taking write access when sending System IO, so that could be it, but i dont understand why its stucked)
2, At the screenshot is shown Autohoming routine (used in Initialization) and robot R2 is curently in home position and waiting at instruction WaitUntil R1=In Home (So not waiting at WaitSyncTask, its one instruction below)
- Robots always starts and end in home position and dont have enough space, so WaitSyncTask is necessary but before it they always wait for signal Do_HomePos from second robot
3, StopMove\AllMoveTasks cannot be used, because one of the robot could reach position to enable enterance, but second one not (and there he would be stoped in random position which could be unrecoverable here)
4, Isleep is used twice for: (1, when trap routines continue after stop with start normaly. 2, when trap routine is canceled via UNDO handler by StartAtMain). MotorsOnStart cannot be used because of machine safety around robots (We need to trigger MotorsOnState at first and then after singal check separately Start) Most of the time Event routines works fine (i have Warning message to log every time they were executed) but here is the point when one of the robot became stucked at the begining of SystemStart event routine with "remote write access" notification
Program is a bit complicated because of using standard structure for whole machine (overall 5xABB) and we need to solve every error/problem in automatic mode so there should not be necessary for operator to switch robot manualy (exclude collision, all of the problems could be solved by Initialization)