Which fixture state belongs with our UR5e loading-stop report?

LuisChan1130 · 17 Apr 2026, 04:21 UTC

Closed
LU
LuisChan1130
Thirty-nine-day ticket with our Alibaba seller. UR5e stops holding a housing above the fixture. Video starts after the stop.

19 replies

YA
YasminArcher0354
Replying to LuisChan1130

Ask the package author which condition the waiting step expects, against the installed job and fixture revision. Then maintenance can collect the preceding events around that input.

10points
LU
LuisChan1130
Replying to YasminArcher0354

They name fixture available. Our old export includes available but no source address.

21points
AD
AdaCarter0999
Replying to LuisChan1130

Does the author mean the same available as that export?

8points
ZA
ZaraBarnes0569
Replying to LuisChan1130

Check the mapping before another recording. A friendly column name can outlive the fixture it described. I would have maintenance trace it against the installed job, not assume the matching word is enough.

23points
LU
LuisChan1130
Replying to ZaraBarnes0569

Different input. Export setup came from the previous fixture. Maintainer has identified the installed mapping.

6points
HA
HanaBennett0709
Replying to LuisChan1130

Replace that export setup on the covering shift's laptop too.

11points
YA
YasminArcher0354
Replying to LuisChan1130

And keep the old occurrence labelled incomplete, Luis. The corrected mapping helps the next capture; it cannot tell you what the missing input was doing earlier.

16points
AD
AdaCarter0999
Replying to LuisChan1130

Can maintenance show the author a sample of the corrected export first?

6points
ZA
ZaraBarnes0569
Replying to AdaCarter0999

Ada, yes. Better to find another omission from an ordinary sample than after waiting for the next stop.

-3points
LU
LuisChan1130
Replying to AdaCarter0999

Sample sent and accepted by the author. Both shifts now have the same capture setup.

14points
HA
HanaBennett0709
Replying to LuisChan1130

Does it include the interval before the wait?

4points
LU
LuisChan1130
Replying to HanaBennett0709

Yes, including the loading request and selected fixture identity. Thanks for checking the shift copies.

7points
AD
AdaCarter0999
Replying to LuisChan1130

Has a new stop happened since?

24points
YA
YasminArcher0354
Replying to LuisChan1130

Luis, include what the physical fixture did in that lead-in if another stop occurs. A missing indication could reflect an actual unavailable fixture, not necessarily a sensor fault.

9points
ZA
ZaraBarnes0569
Replying to YasminArcher0354

Yasmin's point matters. I've seen a perfectly accurate input accused because the screen caption was more reassuring than the mechanism.

19points
LU
LuisChan1130
Replying to AdaCarter0999

New stop captured. Indication absent while the fixture appears clear. Mechanism inspection is next.

21points
AD
AdaCarter0999
Replying to LuisChan1130

Can the clip show the actual release position clearly?

13points
LU
LuisChan1130
Replying to AdaCarter0999

Not clearly enough. Maintainer is inspecting it with the fixture designer; I won't call it released from this angle.

6points
YA
YasminArcher0354
Replying to LuisChan1130

That's a useful limit. Send their finding with this captured occurrence when it's available, so support doesn't have to guess the physical state either.

23points

Discussion closed

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