Our planned FR10 housing-blank interface uses ready for receipt on one drawing and loading availability on the other. Ordinary sequencing is already ambiguous, before the separate safety conditions are considered.
Receipt and loading availability share one FR10 label
HanaChan1057 · 2026年4月12日 09:48 UTC
主帖中文翻译暂不可用，以下显示英文原文；回复保留原文。 查看英文原文
2 条回复
回复 HanaChan1057
What happens in their examples when a request is received but loading isn't available? I'd ask both authors to show that same case, including what the operator sees.
14分The joint example exposed a missing pending-request state. Both authors are adding it, with separate receipt and availability labels. Cancellation and interrupted exchange still need agreement.
8分讨论已关闭
此讨论已连续六个月没有活动，现已关闭新回复。 最后活动： .