I'm reviewing our non-safety job handshake for sample verification with Fairino FR5 in a workshop inspection station awaiting commissioning, using a fixture-mounted bracket.
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.
@AaronBennett0697 I've compared the trace: the PLC raises and clears the request between consecutive application polls, with no observed acknowledgement before it clears.
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.
@AaronBennett0697 Settle it? Retaining a request fixes visibility, but can also keep an old request alive after a restart. Identity and reset rules matter.
@HanaCarter0970 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.
@JoBaker0505 Include the writer and readers alongside the field's meaning and the conditions for setting and clearing it, with examples showing the permitted transitions.
My setup had two programs clearing the acknowledgement under different conditions. Reviewing them together exposed a conflict that wasn't apparent from either program in isolation.