Empty tray, UR5e job still waiting for another spacer

LeoAllen0275 · 14 Mar 2026, 00:41 UTC

Reply to discussion
LE
LeoAllen0275
Our UR5e spacer-unloading job sometimes waits after the tray looks empty. I have the current job and tray identities; I am not assuming they match just because the labels look familiar. The seller through Alibaba has asked for more detail on the 24-day-old report. The phone clip starts at the wait, and nobody recorded which pocket was taken last. I want a capture that settles the ending of the tray sequence rather than another guess about the gripper.

16 replies

AD
AdaAbbott0042
Replying to LeoAllen0275

Ask the author for the selected tray definition, expected pocket count and current step from the same occurrence. The ending may matter here, but the empty-looking tray alone does not explain what the job expects.

14 points
ZA
ZaraBell0656
Replying to LeoAllen0275

Is this every tray, Leo, or only the short orders? That difference would be useful even before the next trace arrives.

22 points
VI
VictorBennett0707
Replying to ZaraBell0656

The operator may know how the tray was prepared without remembering its last pocket. Ask for the starting arrangement, including deliberately empty positions.

17 points
LE
LeoAllen0275
Replying to VictorBennett0707

Only the short orders we can identify. They begin with part-filled trays. The operator follows a written fill order, but the job selection page only names the tray family, not the order ending.

14 points
TH
ThomasBarnes0538
Replying to LeoAllen0275

Get the applicable definition from the author. Don't teach the operator to skip a wait until the application has an agreed meaning for those empty positions.

24 points
CA
CallumAdams0099
Replying to LeoAllen0275

Has the customer-supplied fill order ever been included in the package handover? It could be correct packing practice and still be absent from the program assumptions.

14 points
JO
John_Briggs
Replying to LeoAllen0275

What did the original demonstration use, Leo, a full tray or the same partial starting condition?

23 points
JA
JaneAllen0336
Replying to CallumAdams0099

Callum's handover question needs an owner. This will keep returning if the trainer has one fill order and the job author has another.

19 points
LE
LeoAllen0275
Replying to John_Briggs

John, full tray in the demonstration. Callum, our partial fill order was sent during planning but never added to the issued job notes. New capture shows the program waiting on the next position in its full-tray definition after the actual short order is exhausted.

8 points
ZA
ZaraBell0656
Replying to LeoAllen0275

So the short-order work was not represented in that definition. Has the author accepted that scope, or are they proposing full trays only?

14 points
VI
VictorBennett0707
Replying to ZaraBell0656

Full trays only could be a valid restricted job, but the operator would need the restriction before loading. It cannot live solely in the support ticket.

1 points
AD
AdaAbbott0042
Replying to VictorBennett0707

Victor, agreed. Leo, ask for an explicit decision on the short orders and their finish, including interruption. Do not let a changed pocket total stand in for that whole decision.

23 points
LE
LeoAllen0275
Replying to AdaAbbott0042

The author and our lead agreed identified short-order definitions using the permitted fill order. The offline checks cover normal finish, an unexpected empty pocket and interruption. The screen now shows which order definition is selected.

10 points
CA
CallumAdams0099
Replying to LeoAllen0275

Have those changes reached the station, or only the support demonstration?

17 points
LE
LeoAllen0275
Replying to CallumAdams0099

Station checks completed with the integrator and shift lead. Full and agreed short orders finish correctly; unexpected gaps take the agreed recovery route. Trainer updated the fill-order notes. Thanks, Zara, asking which orders failed got us moving.

8 points
JO
John_Briggs
Replying to LeoAllen0275

That explains the reported short-order wait. I would leave any older untraceable stop unassigned rather than let this answer absorb it.

6 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.