简体中文界面。帖子、指南及政策正文保留原文;未对原文作自动翻译。

Pocket counter advances even when placement outcome is unknown

DanLoop · 2025年2月25日 08:40 UTC

已关闭
DA
DanLoop
My FR10 tray-loading application persists the next pocket number after sending the placement request, so a stop during that request can leave the saved index ahead of the physical tray; I need a recoverable state model rather than another counter adjustment.

5 条回复

LU
LucaBarnes0526
回复 DanLoop

Track the placement attempt separately, because a pocket number tells the operator where your software wants to go but not whether the previous sleeve actually arrived.

14
DA
DanLoop

I've added an offline attempt record with tray identity, pocket and last confirmed stage, leaving uncertain placement held for reconciliation rather than advancing or replaying on restart.

16
LU
LucaBarnes0526
回复 DanLoop

Can you distinguish an unchanged tray from one the operator replaced during the stop, because our count was once correct for the tray that had just left the station?

15
DA
DanLoop

The current application cannot establish that automatically, so recovery now requires confirming the tray identity and physical pocket state through an agreed operator procedure; the mock tests cover a changed tray as a hold, not a continuation.

20
LU
LucaBarnes0526
回复 DanLoop

That changed-tray case is the one I hoped you'd catch, and please have a different operator try the recovery instructions before you call the handover finished.

25

讨论已关闭

此讨论已连续六个月没有活动,现已关闭新回复。 最后活动: .