Define the interrupted stages before moving the save instruction. The design must distinguish a block still at source, held by the tool, placed, and not yet confirmed. One pocket number cannot describe all of those.
简体中文界面。帖子、指南及政策正文保留原文;未对原文作自动翻译。
FR10 saved pocket ahead of the block
Olivia_Blair · 2025年12月13日 06:21 UTC
18 条回复
Controls suggested saving after release instead. That leaves the opposite gap, doesn't it?
11分Yes. A stop after release but before the save can leave the stored position behind. The recovery design needs to handle uncertainty, not just move it to another line
20分Does startup show the saved number as a confirmed empty pocket?
17分It says next pocket. No uncertainty shown.
9分Who is expected to reconcile the interrupted transfer when the operator cannot establish where the block is, Olivia? That responsibility belongs in the design as well as the stored states.
2分Yasmin's wording point matters. I would have controls hold an uncertain transfer for the agreed reconciliation, with the last stored information identified as such. Reopening must not convert it into a fresh request.
20分And reconciliation is more than choosing a screen value. The physical recovery and access need assessment with the integrator before those choices become operator instructions
9分Designated maintenance lead, Pavel. Agreed method still outstanding. We're not handing this to production yet.
21分Can the software test a stop at both sides of release without moving hardware?
17分The developer can test the state logic with simulated observations and interruptions. That is useful coverage, but it will not establish how the real placement is confirmed or how physical recovery is carried out.
6分Offline cases now include both gaps. Also reopening with the block state unknown.
9分Cases written, or passed?
22分Olivia, include a repeated interruption during reconciliation in the discussion with the maintenance lead; people can be called away before an agreed recovery has finished.
25分Written when I posted. Passed now, with unknown remaining held after reopening. Physical method still under review.
15分Does the test also reopen after the second interruption Pavel describes? A hold that survives one restart may still be cleared accidentally by a later path.
4分Keep the operator trial separate from those software results. Someone unfamiliar with the fault should understand why the station is held, without being invited to guess the missing placement
7分What will it display if the tray identity is missing too?
13分讨论已关闭
此讨论已连续六个月没有活动,现已关闭新回复。 最后活动: .