UR5e housing wait with an unreadable destination identity

HazelAllen0310 · 21 Mar 2026, 10:14 UTC

Reply to discussion
HA
HazelAllen0310
We have the lead-in and job export for our UR5e housing stop now. The destination is hidden by the tray wall in the video, and the export uses a pocket number without the tray identity. Our eleven-day seller ticket needs that gap explained, not another confident guess about where the housing went.

13 replies

EM
EmmaBaker0463
Replying to HazelAllen0310

Does another retained record identify which destination tray was fitted for that occurrence?

0 points
HA
HazelAllen0310
Replying to EmmaBaker0463

The shift sheet names the tray family, not the individual tray or insert. It doesn't settle which of the two arrangements was present.

24 points
NA
NathanChen1156
Replying to HazelAllen0310

Tell support that limit explicitly. Ask the author to include the destination identity in a new capture, linked to the physical arrangement and the job that selected it.

12 points
NA
NaomiBrown0941
Replying to HazelAllen0310

Can the covering operator identify those two arrangements from the normal loading position?

15 points
HA
HazelAllen0310
Replying to NaomiBrown0941

Only by a small mark at the rear. The loader usually recognises them from where they are stored, which isn't a reliable handover.

17 points
LU
LucaChen1135
Replying to HazelAllen0310

Then the job needs a visible arrangement identity as well as a better export; otherwise you'll record a selection nobody can confidently match to the tray.

23 points
NA
NathanChen1156
Replying to LucaChen1135

Luca's point is separate from inferring the old stop. Fix future identification without rewriting the uncertain history.

24 points
HA
HazelAllen0310
Replying to NathanChen1156

Agreed. We're adding a visible identity to each approved arrangement and having the author expose the selected one. The old occurrence remains uncertain.

0 points
EM
EmmaBaker0463
Replying to HazelAllen0310

Has the maintainer confirmed the next capture includes the events before the wait, rather than only the selected arrangement at the end?

4 points
HA
HazelAllen0310
Replying to EmmaBaker0463

Yes. It retains the request, receipt and destination condition leading into that step, with one occurrence reference.

1 points
NA
NaomiBrown0941
Replying to HazelAllen0310

I'd have the covering operator try the identification and export together, so the two improvements actually meet at handover

5 points
LU
LucaChen1135
Replying to HazelAllen0310

And leave the new wait unexplained until it occurs with that capture; an improved recorder is preparation, not a diagnosis.

15 points
HA
HazelAllen0310
Replying to LucaChen1135

The handover walkthrough is arranged. No new matched stop yet, so support still has the original export with its destination uncertainty clearly stated.

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