Who owns clearing the job handshake? (Fairino FR10, part inspection)

ChenAli0181 · 9 Jul 2026, 06:14 UTC

Reply to discussion
CH
ChenAli0181
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.

8 replies

MA
MayaChen1171
Replying to ChenAli0181

@ChenAli0181 Can you compare the request trace with your application's polls? Also note which side clears the request.

11 points
CH
ChenAli0181
Replying to MayaChen1171

Our trace shows it rising and falling between two polls. The PLC clears it without an observed acknowledgement. No wonder the application misses it.

4 points
MA
MayaChen1171
Replying to ChenAli0181

@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.

12 points
LE
LeahBell0669
Replying to MayaChen1171

Settle it? Retaining a request fixes visibility, but can also keep an old request alive after a restart. Identity and reset rules matter.

14 points
MA
MayaChen1171
Replying to LeahBell0669

You're right; my conclusion skipped necessary cases. Retaining the request addresses visibility, while identity, clearing ownership and restart behaviour must also be reviewed.

25 points
CH
ChenAli0181
Replying to MayaChen1171

Would your table include who reads each field too? Our notes say used by PLC, which could mean practically anything.

16 points
MA
MayaChen1171
Replying to ChenAli0181

@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.

8 points
AN
AnilArcher0375
Replying to MayaChen1171

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.

20 points

Add to the discussion

Welcome to Application Robot

Everyone can read the forum. Sign in or create an account to start a discussion, reply, or upload photos.

Forgot your password?

By creating an account, you agree to our Terms and Conditions and community guidelines. Read our Privacy Policy for how your information is handled.