Cannot tell support which UR5e stop my screenshot belongs to

GabrielAbbott0018 · 14 Jan 2026, 23:08 UTC

Closed
GA
GabrielAbbott0018
My UR5e unloading clip and screenshot aren't from the same stop. Should I send them together at all?

18 replies

RE
RebeccaChan1126
Replying to GabrielAbbott0018

Send them as separate occurrences if both are useful. Say what's missing from each. A tidy-looking package assembled from two stops can persuade support they're seeing a sequence that never happened.

17 points
GA
GabrielAbbott0018
Replying to RebeccaChan1126

Understood. Clip has the block waiting; screenshot has the message. Neither proves they happened together.

11 points
CA
CallumBrooks0795
Replying to GabrielAbbott0018

Is there a saved event history covering the filmed stop, with enough information to identify it? That is the first place I would look for the missing connection, before asking you for more footage.

13 points
GA
GabrielAbbott0018
Replying to CallumBrooks0795

There is an export, but its clock is offset from the phone. I haven't matched them.

21 points
RE
RebeccaChan1126
Replying to GabrielAbbott0018

Any distinctive event visible in both? Not just roughly the same time. If somebody corrects the clock by guessing until the desired message lines up, you're back where you started.

5 points
LI
LinBrooks0792
Replying to GabrielAbbott0018

I had two people film a stop once and neither showed the screen the other person thought they were covering. Very thorough coverage of one stationary part. Worth deciding what the next recording must include before everybody reaches for a phone.

3 points
AN
AnikaBell0682
Replying to GabrielAbbott0018

Who can recover the application history without disturbing the stopped job?

4 points
GA
GabrielAbbott0018
Replying to AnikaBell0682

Our controls contact has the saved export. Clip shows a tray-change acknowledgement also present there.

4 points
CA
CallumBrooks0795
Replying to GabrielAbbott0018

Have that contact verify the match and retain the original times with the explanation. The offset may be explainable, but I would not rewrite the raw history to make it prettier.

-2 points
LI
LinBrooks0792
Replying to CallumBrooks0795

Callum, yes. We kept the originals after our filming muddle; someone else needed to see what was actually absent, rather than trust our improved version of events.

6 points
GA
GabrielAbbott0018
Replying to CallumBrooks0795

Controls matched the tray acknowledgement and following events. Filmed stop says destination unavailable in the application history.

17 points
RE
RebeccaChan1126
Replying to GabrielAbbott0018

That's useful. Does your separate screenshot say something different, or is it the same wording from another occurrence? Keep its identity separate either way.

5 points
GA
GabrielAbbott0018
Replying to RebeccaChan1126

Different wording: tray exhausted. That screenshot is staying separate. I'm asking what destination unavailable means here.

7 points
AN
AnikaBell0682
Replying to GabrielAbbott0018

Good question for the application owner, not a guess from the stationary block.

10 points
LI
LinBrooks0792
Replying to GabrielAbbott0018

Has the seller actually received the matched version now, Gabriel? I'd put the difference in the first line, because they may still be answering the old combined report.

3 points
GA
GabrielAbbott0018
Replying to LinBrooks0792

Sent it with separate occurrence IDs. Asked them to retire the combined attachment from the ticket.

10 points
GA
GabrielAbbott0018
Replying to GabrielAbbott0018

Seller acknowledged the split and forwarded the filmed occurrence to their application contact. No diagnosis back yet.

16 points
RE
RebeccaChan1126
Replying to GabrielAbbott0018

Leave the other occurrence open in your list too. You might eventually find one cause behind both, but at least nobody now has to explain a fictional sequence made from your two recordings.

22 points

Discussion closed

This discussion is closed to new replies after six months without activity. Last activity: .