UR5e housing stop with no agreed event reference in the ticket

NaomiBarnes0593 · 18 Jun 2026, 20:02 UTC

Reply to discussion
NA
NaomiBarnes0593
Our Alibaba seller has requested more than the phone video after 33 days on this tray-loading ticket. I learned on an earlier stop that the filmed message need not be the first event. For this case, how should I tie the occurrence to the controller history and actual housing setup?

9 replies

OM
OmarArcher0404
Replying to NaomiBarnes0593

Give one occurrence an identifiable time and job version, then retain the surrounding history. Don't send isolated screenshots that could belong to several different stops.

12 points
NA
NaomiBarnes0593
Replying to OmarArcher0404

Controller time and phone time differ. I have not measured the offset. The video shows the housing at the receiving tray, but the active step is unreadable.

7 points
KA
KaiAllen0280
Replying to NaomiBarnes0593

I would keep the original clip and record that uncertainty. Also identify the fitted tray and tooling revision. Support may otherwise match a correct program export to the wrong physical arrangement.

10 points
NA
NaomiBarnes0593
Replying to KaiAllen0280

The tray has a revision mark. Tooling has a part number but no revision visible. Maintenance is finding the assembly reference and retaining the active program export with the event history.

2 points
OM
OmarArcher0404
Replying to NaomiBarnes0593

Any active-step evidence from an occurrence yet? The exports will describe the setup, but they won't tell us which condition was holding it there.

21 points
KA
KaiAllen0280
Replying to OmarArcher0404

Omar, agreed. Naomi, ask support which diagnostic states their technical person needs for that step once it is identified. That gives the next capture a purpose instead of asking an operator to film everything.

9 points
NA
NaomiBarnes0593
Replying to OmarArcher0404

A retained occurrence identifies the wait step. The controls technician linked it to the destination confirmation in this program version. Its actual input state at the stop was not captured.

14 points
NA
NaomiBarnes0593
Replying to KaiAllen0280

I have sent that distinction with the original history and assembly reference. Asked support to specify the remaining observation. No claim that the destination sensor failed; we have not established that.

6 points
OM
OmarArcher0404
Replying to NaomiBarnes0593

Good place to keep the question. Did support name the required observation, or just acknowledge the attachment?

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