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

I cannot assign request clearing from our UR5e interface notes

JuliaChan1109 · 2026年2月18日 10:01 UTC

已关闭
JU
JuliaChan1109
PLC request ends before receipt is confirmed. Application sometimes misses it. Who should own clearing in the agreed interface?

9 条回复

LI
LiamChen1186

What event does the PLC author currently think permits clearing?

19
JU
JuliaChan1109

Elapsed pulse time. Application author expects the request to persist until it acknowledges the identified attempt.

13
PA
PavelChan1049

Have both authors agree the exchange as states and events. Who publishes the request, what confirms receipt, who clears each state, and what happens without receipt. Stretching the pulse doesn't settle their incompatible assumptions.

22
LI
LiamChen1186

Does that acknowledgement mean received or completed?

1
JU
JuliaChan1109

Received only. We separated receipt from inspection result and gave both the same retained attempt identity.

20
PA
PavelChan1049

Test delayed receipt, duplicate receipt and restart with an unfinished exchange. The operator also needs a clear difference between no answer and an actual rejected housing, because those are different problems to report.

9
JU
JuliaChan1109

Offline cases passed. Unknown receipt stays awaiting reconciliation; duplicate receipt does not create another inspection. Operator walkthrough distinguished the cases.

18
JU
JuliaChan1109

Installed interface checks completed with both authors. Request and receipt clearing now follow the agreed ownership. Handover revision issued.

5
LI
LiamChen1186

Can the covering operator find the attempt identity without opening an engineering screen?

8

讨论已关闭

此讨论已连续六个月没有活动,现已关闭新回复。 最后活动: .