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

Our UR5e request disappears without an agreed clear rule

ElenaBennett0775 · 2026年6月22日 00:52 UTC

回复讨论
EL
ElenaBennett0775
PLC request is brief. Our fixture-inspection app misses it sometimes. Nobody owns the clearing rules. Ordinary job interface only; safety is separate.

8 条回复

JO
JonasBrooks0807

Does either side know whether acknowledgement means received or finished? I'd settle that before pulse length.

17
EL
ElenaBennett0775

The application calls it received. The PLC notes don't define it beyond acknowledgement.

20
KA
KaiBaker0454

Write the normal exchange in plain language with one writer per signal. Request held until an agreed response, acceptance separate from completion, and explicit clearing conditions. The notes should describe both sides of the same conversation.

18
RA
RaviBennett0737

I'd bring whoever supports each side into that discussion. We can make a tidy table in one room and still leave the relief technician with two incompatible drawings when the application changes.

6
JO
JonasBrooks0807

Kai, include an interrupted exchange too. A clean first cycle doesn't explain a retained acknowledgement after restart.

14
KA
KaiBaker0454

Yes. I said normal exchange as a starting point, not the whole specification. Startup, timeout and retained states need their own decisions, including when work is uncertain and must not be automatically repeated.

17
EL
ElenaBennett0775

Both maintainers will review it. We still haven't agreed acknowledgement meaning or restart behaviour.

14
RA
RaviBennett0737

Then those are the two questions for the meeting, not just approve the interface. A named review is useful, but your operators still need the agreed waiting and escalation states before this is handed over.

14

参与讨论

欢迎来到 Application Robot

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

忘记密码?

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