I want to replace ready with events both suppliers can explain. Machine supplier uses it for request received; integrator uses it for loading area available. Those don't happen at the same point. This is our ordinary job interface, separate from the engineered safety functions.
What should ready mean in our UR5e spacer-loading interface?
LucaCarter0961 · 2026年2月18日 11:36 UTC
主帖中文翻译暂不可用，以下显示英文原文；回复保留原文。 查看英文原文
7 条回复
Can they name the two events separately and show the case where a request has been received while the area remains occupied? That ought to expose the difference faster than another argument about one word.
24分They walked that case. Machine can acknowledge receipt while the previous part is still present, so the current diagram's single ready arrow is wrong. We have separate receipt and availability entries now.
9分What does the operator see while the request is received but the area is still occupied?
21分Draft screen says request received, waiting for loading area. Author still needs to define what clears availability after use and how the same request is identified after a restart.
13分Has that clearing rule been agreed yet? The two labels help, but the next request should not inherit availability from the previous exchange merely because nobody withdrew it.
24分Agreed now, with retained request identity and explicit unknown states after interruption. Offline sequence checks passed. The operator understood the two waits in the walkthrough; installed interface verification remains open. Thanks, Harish, the occupied-area example ended the word game.
6分Can the support contact identify that request from the operator's view now?
21分讨论已关闭
此讨论已连续六个月没有活动，现已关闭新回复。 最后活动： .