I'm reviewing our non-safety job handshake for part inspection with Fairino FR10 in a PLC-coordinated fixture inspection cell, 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.
@ChenAli0181 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.
You're right; my conclusion skipped necessary cases. Retaining the request addresses visibility, while identity, clearing ownership and restart behaviour must also be reviewed.
@ChenAli0181 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.