I cannot assign request clearing from our UR5e interface notes

JuliaChan1109 · 18 Feb 2026, 10:01 UTC

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

9 replies

LI
LiamChen1186
Replying to JuliaChan1109

What event does the PLC author currently think permits clearing?

19points
JU
JuliaChan1109
Replying to LiamChen1186

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

13points
PA
PavelChan1049
Replying to JuliaChan1109

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.

22points
LI
LiamChen1186
Replying to JuliaChan1109

Does that acknowledgement mean received or completed?

1points
JU
JuliaChan1109
Replying to LiamChen1186

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

20points
PA
PavelChan1049
Replying to JuliaChan1109

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.

9points
JU
JuliaChan1109
Replying to PavelChan1049

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

18points
JU
JuliaChan1109
Replying to JuliaChan1109

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

5points
LI
LiamChen1186
Replying to JuliaChan1109

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

8points

Discussion closed

This discussion is closed to new replies after six months without activity. Last activity: .