A spacer in the nest and an unchanged pocket counter

Anders_Briggs · 15 Apr 2026, 10:58 UTC

Reply to discussion
AN
Anders_Briggs
My UR5e tray sequence can place a spacer and stop before saving the advance, leaving restart eager to repeat it. The counter is certain; the physical transfer isn't. I need a better recovery model.

4 replies

FE
FelixBaker0458
Replying to Anders_Briggs

Separate the source, held spacer and destination states, tied to the identified trays and transfer attempt. An uncertain placement needs reconciliation before any repeat or advance. Have the integrator define what evidence and responsible person resolve it.

13 points
AN
Anders_Briggs
Replying to FelixBaker0458

Draft now holds uncertain placement instead of offering repeat. We track the two trays and the spacer attempt separately. The awkward example is a tray exchange while the application was stopped.

12 points
FE
FelixBaker0458
Replying to Anders_Briggs

Include a definitely completed transfer and a definitely unstarted one too. Does reopening after a saved reconciliation preserve that decision? A recovery screen should not create the same uncertainty on every startup.

7 points
AN
Anders_Briggs
Replying to FelixBaker0458

Offline cases now keep those distinctions across reopening, including the exchanged-tray mismatch. The operator walkthrough still needs doing. At least the counter no longer gets the casting vote.

17 points

Add to the discussion

Welcome to Application Robot

Everyone can read the forum. Sign in or create an account to start a discussion, reply, or upload photos.

Forgot your password?

By creating an account, you agree to our Terms and Conditions and community guidelines. Read our Privacy Policy for how your information is handled.