Our application sometimes misses the PLC's brief request for sample verification.
I'm reviewing that ordinary, non-safety handshake for Fairino FR10 in a training inspection cell with an ordinary job interface, with a fixture-mounted bracket in the setup.
Signal ownership and clearing conditions aren't clearly documented.
The safety functions are independently engineered and separate from this job interface.
@TobyBrooks0840 I've compared the trace: the PLC raises and clears the request between consecutive application polls, with no observed acknowledgement before it clears.
@MinaArcher0424 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.
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.
@TobyBrooks0840 Should I record readers as well as the single writer? Our existing phrase used by PLC doesn't distinguish setting, reading or clearing a field.