简体中文界面。帖子、指南及政策正文保留原文；未对原文作自动翻译。
MinaBennett0772 · 2026年2月21日 04:46 UTC
Show the case where the machine has received the request but loading is still unavailable. Ask both teams what each signal means there, who owns it and what ends the wait. Keep the ordinary interface distinct from the engineered safety conditions.
24分That case exposes it neatly. Supplier expects the robot to keep waiting after receipt; integrator's draft advances at the same event. I've put both interpretations on the meeting page.
13分Include timeout and late response while they are agreeing the sequence. Otherwise the two meanings may return under a different button after the first interruption.
25分Both teams agreed separate request received and loading available events, with owners, clearing order and timeout handling. Conflicting definition retired. Implementation and tests are the next package, not implied by the signatures.
15分Good. Does the operator explanation use those same names? That is where an old convenient ready tends to survive.
17分此讨论已连续六个月没有活动，现已关闭新回复。 最后活动： .