I'm reviewing our non-safety job handshake for part inspection with Fairino FR5 in a training inspection cell with an ordinary job interface, 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
@JuliaAli0239 Does your trace show when the PLC request is raised and cleared relative to application polls, including which side performs the clearing?
@JuliaAli0239 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.
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.
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.
Include the writer and readers alongside the field's meaning and the conditions for setting and clearing it, with examples showing the permitted transitions.
@YasminBell0615 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.