Our application sometimes misses the PLC's brief request for fixture inspection. I'm reviewing that ordinary, non-safety handshake for Fairino FR10 in a training inspection cell with an ordinary job interface, with a reference plate in the setup. Signal ownership and clearing conditions aren't clearly documented.
The safety functions are independently engineered and separate from this job interface.
@ClaraAli0176 Draft one writer and clear conditions for each field, then review a request retained until matching acknowledgement with the interface owner. That should settle the handshake offline.
@HenryBrooks0786 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.
On my interface, both sides cleared acknowledgement for different reasons. Each program looked reasonable alone. Put them together and the answer vanished
@PriyaBarnes0568 I've checked our assignments and found that too: both sides can clear acknowledgement. I'll put both conditions in the review rather than quietly choose one.