UR5e sleeve-stop clip after the receiving tray was already removed

BrunoAllen0278 · 16 Feb 2026, 22:33 UTC

Closed
BR
BrunoAllen0278
Our UR5e sleeve-unloading report has a clear video and an unclear explanation. Seller wants the tray state before the stop. We filmed after the receiving tray was removed. What can we still recover?

16 replies

LU
LucaChan1048
Replying to BrunoAllen0278

Did anybody save the event history before removing it?

7 points
BR
BrunoAllen0278
Replying to LucaChan1048

Not manually. Maintainer says the recorder may still have it. Video definitely shows the changed scene, not the original tray position.

9 points
RU
RuthBlair
Replying to BrunoAllen0278

Keep the video. Label what changed, rather than throwing away the only view you have.

14 points
DA
DanielChan1087
Replying to BrunoAllen0278

Ask the package author which receiving condition the unloading step waits for, then have the maintainer find that condition around the occurrence. Tray removed afterwards is useful context, but it doesn't tell you whether it was seated correctly when the wait began.

19 points
PR
PriyaBarnes0568
Replying to BrunoAllen0278

And identify the tray that was there, not today's replacement.

22 points
CO
Colin_Blair
Replying to LucaChan1048

We used to have wonderful fault clips ending with a hand pointing at the screen, while the useful message had disappeared before filming began; the recorder eventually saved us that performance, but only once someone checked which events it actually retained.

3 points
MA
Marcus_Blair
Replying to Colin_Blair

Who checked yours, Colin: the installer or your maintainer?

12 points
DA
DanielCarter1000
Replying to PriyaBarnes0568

Keep the tray reference with the job identity. Our records once retained the attempt while the monitor invented a new run label after reconnect. The information was there, but the names made it easy to attach it to the wrong work.

6 points
JA
JasperBennett0725
Replying to Colin_Blair

Check the exported interval itself, including its lead-in. A successfully created file is not evidence that the needed events survived in the recorder.

22 points
BR
BrunoAllen0278
Replying to JasperBennett0725

Maintainer recovered the original attempt and identified tray. Trace shows seated confirmation disappearing before the wait. It includes the earlier normal transition too. Author has accepted that interval for investigation.

10 points
TH
ThomasAbbott0016
Replying to BrunoAllen0278

Our fixture looked home from the front while a rear contact wasn't made. Worth giving maintenance the intended seating detail, not only the signal name.

2 points
TH
TheoAli0236
Replying to ThomasAbbott0016

Compare that detail with the actual tray and confirmation hardware from this occurrence, because a lost signal can come from the physical seat or its sensing path and the trace alone doesn't choose between them.

22 points
RE
ReeceBrooks0819
Replying to TheoAli0236

Give the maintenance work a place in the production plan too. Otherwise everyone agrees to inspect it and the shift still expects another unexplained adjustment to keep the job going.

22 points
BR
BrunoAllen0278
Replying to TheoAli0236

Inspection found damage to the receiving latch catch. Tray could look nearly home without reaching its intended seat. Fixture designer is specifying the replacement; this job remains held, with cover arranged for the maintainer.

20 points
LU
LucaChan1048
Replying to BrunoAllen0278

Has the replacement arrived yet?

15 points
BR
BrunoAllen0278
Replying to LucaChan1048

No. Identified and requested, not received. We have the captured condition and a physical finding now, but no repair or return result to report.

6 points

Discussion closed

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