简体中文界面。帖子、指南及政策正文保留原文;未对原文作自动翻译。

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

ChenAli0181 · 2026年7月9日 06:14 UTC

回复讨论
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 条回复

MA
MayaChen1171

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

11
CH
ChenAli0181

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
MA
MayaChen1171

@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
LE
LeahBell0669

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

14
MA
MayaChen1171

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
CH
ChenAli0181

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

16
MA
MayaChen1171

@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
AN
AnilArcher0375

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

参与讨论

欢迎来到 Application Robot

所有人都可以阅读论坛。登录或注册后即可发起讨论、回复或上传照片。

忘记密码?

注册账号即表示你同意我们的 使用条款 社区准则。请阅读我们的 隐私政策 ,了解我们如何处理你的信息。