Our application misses the PLC's brief job request. No ownership or clearing rule written down. Where do I start? This is the ordinary interface, separate from safety.
Who should clear our UR5e inspection request?
EllaAli0207 · 2026年3月9日 22:50 UTC
主帖中文翻译暂不可用，以下显示英文原文；回复保留原文。 查看英文原文
10 条回复
DA
回复 EllaAli0207
Have the PLC and application authors define the request identity, matching receipt and which side clears its own state; a pulse widened by guesswork still does not tell either side that the request was received.
8分回复 DanLoop
Both authors agree the pulse was an assumption. PLC expected fast polling; application expected a retained request.
12分回复 EllaAli0207
Try a delayed receiver in an offline interface test first. It should recover the same pending request, not need another button press to create work.
20分They have defined retained request and matching receipt. Delayed receiver test now accepts the original request once.
6分DA
回复 EllaAli0207
Also test duplicate receipt and restart while the request is outstanding, with the saved identity retained rather than treating startup as a reason to submit another inspection.
8分回复 EllaAli0207
Who will explain the wait to the operator, Ella, so request received does not become inspection complete in the handover?
14分Trainer and application author. Draft now distinguishes waiting for receipt, inspection pending and completed result.
14分回复 DanLoop
Did the restart and duplicate cases pass with the final agreed interface revision?
8分Yes. Offline and installed checks completed with the owners. No missed request or duplicate inspection in those cases. Trainer accepted the wording.
16分DA
回复 EllaAli0207
Keep that interface revision with both program versions and the tested cases, so the next maintainer knows which combination was actually checked.
9分讨论已关闭
此讨论已连续六个月没有活动，现已关闭新回复。 最后活动： .