I'm reviewing our non-safety job handshake for part inspection with Universal Robots UR5e in a PLC-coordinated fixture inspection cell, using a reference plate. The PLC sends a brief request, and our application sometimes misses it. I can't find anything clear about who owns each signal or when it gets cleared.
Safety functions are independently engineered; this is the ordinary job interface.
Take an ownership table and a retained-request proposal to the interface owner. A request held until matching acknowledgement should settle the handshake in an offline review.
@NoraAllen0322 Holding the request addresses the missed pulse, but it doesn't settle the interface. A retained request needs identity and restart rules to avoid being mistaken for new work.
@NoahArcher0368 Yes, I overstated that. Retention addresses the missed pulse. The offline review also needs matching identity, reset ownership and restart cases before the design is complete.
@NoraAllen0322 The missed-request diagnosis is settled for this trace. Completing the handshake fix still depends on the interface owner's assessment of signal ownership and the offline transition cases.