I'm reviewing our non-safety job handshake for fixture inspection with Fairino FR10 in a training inspection cell with an ordinary job interface, using a sample housing.
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.
@NaomiAllen0332 I've compared the trace: the PLC raises and clears the request between consecutive application polls, with no observed acknowledgement before it clears.
@ZaraArcher0395 Take an ownership table and a retained-request proposal to the interface owner. A request held until matching acknowledgement should settle the handshake in an offline review.
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.
@NaomiBrown0941 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.
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.