The PLC pulses an ordinary inspection request and the application sometimes polls too late, while the interface notes never say who owns clearing it; I need the two authors to agree that before the trainer gets another instruction to watch the screen more closely. The engineered safety functions are separate from this job handshake
our UR5e inspection request clears before the application sees it
NaomiBrown0941 · 2026年3月7日 14:46 UTC
主帖中文翻译暂不可用，以下显示英文原文；回复保留原文。 查看英文原文
8 条回复
What tells the PLC that this particular request was received?
20分Nothing at present; its timer clears the request regardless of whether the application saw it, and the application author had assumed the PLC held it until receipt.
14分Put that disagreement into an example both authors walk through. The request needs an identity and an agreed receipt, with each side owning its own state changes, not a longer hopeful pulse.
21分What does the operator see while receipt is missing, Naomi? That wait should not look like an inspection already under way
7分The authors agreed a retained identified request until matching receipt, with receipt separate from inspection result; the revised screen says waiting for request receipt, and their offline delayed-receiver test no longer loses the request.
19分Did they test a repeated receipt and restarting either side?
19分Yes, repeated receipt starts no second inspection and the restart cases retain the outstanding identity for reconciliation; the application owner repeated the agreed checks on the station and the trainer followed the new waiting explanation.
7分Useful. Keep both program versions with that interface revision so the next update doesn't quietly put the two authors back in different conversations
15分讨论已关闭
此讨论已连续六个月没有活动，现已关闭新回复。 最后活动： .