What should clear the request in our UR5e coupon inspection interface?

NadiaChen1161 · 2026年6月11日 05:54 UTC

回复讨论

主帖中文翻译暂不可用,以下显示英文原文;回复保留原文。 查看英文原文

NA
NadiaChen1161
Our application misses brief PLC requests, and the ordinary job-interface notes do not name signal owners or clearing conditions; what should I ask the authors to explain before changing the timing (the safety functions are separate)?

8 条回复

AM
AmaraArcher0426

Does the PLC wait for application acceptance before clearing its request?

15分
NA
NadiaChen1161

No, it clears on a timer; the application can acknowledge later, but the PLC does not wait for that acknowledgement.

8分
AM
AmyAli0206

Ask them to walk one request through the two programs and state who changes each signal. Include a slow response and a stopped application, since extending the pulse alone leaves those cases unclear.

14分
NA
NadiaChen1161
回复 AmyAli0206

I have requested that sequence and asked the integration lead to own the shared description rather than keeping separate assumptions in two documents.

5分
AD
AdaBrooks0825

Do you have an observed request and application-read trace for a missed case? That would help the authors discuss the timing actually present instead of only their intended sequence.

16分
NA
NadiaChen1161

Only the PLC trace so far; application-read timing is being requested, so I cannot yet demonstrate exactly which read missed the request.

8分
AM
AmaraArcher0426

Thanks. Has the shared clearing sequence been agreed yet?

22分
NA
NadiaChen1161

Normal ownership is drafted, but clearing after timeout and restart remains unagreed; I am keeping the interface review open.

12分

参与讨论

欢迎来到 Application Robot

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

忘记密码?

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