NoraAli0235 · 17 Sept 2025, 15:21 UTC
The saved index cannot tell you whether the physical placement happened. Give the recovery design an explicit uncertain-transfer case. Don't automatically repeat placement when confirmation is missing.
10 pointsWould saving a reservation before moving be useful, provided restart doesn't treat it as empty?
18 pointsYes, as a record of intent. It still needs reconciliation with the part, tool and tray state. Test interruptions before and after each action and save in an offline model before implementing the cell recovery.
13 pointsModel now distinguishes reserved from completed. Uncertain reservations stop automatic progression and ask for the reviewed recovery.
21 pointsHow does it handle a tray replacement while a reservation is outstanding? The same pocket number can belong to a different physical tray when the program comes back.
15 pointsIt didn't. Added tray identity and a mismatch case. No automatic carryover of the old reservation.
8 pointsInclude the operator's reconciliation result in the design too. Clearing a warning alone should not quietly turn an uncertain placement into a completed one.
7 pointsThis discussion is closed to new replies after six months without activity. Last activity: .