My UR5e housing-loading ticket needs the event behind the phone video

BrunoBennett0713 · 20 Aug 2026, 08:37 UTC

Reply to discussion
BR
BrunoBennett0713
Our imported UR5e housing loader stops intermittently. The Alibaba seller asked for more information after my phone video, and the report has been open twelve days. I want one identifiable occurrence with enough context for technical review, not a diagnosis inferred from a paused arm.

5 replies

MA
MayaArcher0388
Replying to BrunoBennett0713

Which parts of the occurrence can you actually link now: readable message, active step, installed revision, housing state and preceding action, or does the clip begin after everyone has already gathered around the pause?

14 points
BR
BrunoBennett0713
Replying to MayaArcher0388

It begins after the pause, with no readable message. I have the job revision but no secure event-history match. I've sent that limitation and asked the technical reviewer which supported records to capture next.

10 points
MA
MayaArcher0388
Replying to BrunoBennett0713

Has a new occurrence been captured under that request, with a named shift contact to retain it rather than whichever person happens to have a phone?

10 points
BR
BrunoBennett0713
Replying to MayaArcher0388

Yes. Shift lead retained a matched message and history interval with the physical view. It identifies a receiving-fixture wait; support is reviewing the ordinary confirmation path, with no cause assigned to the old clip.

15 points
MA
MayaArcher0388
Replying to BrunoBennett0713

Keep that new event's fixture identity beside the installed job, so the reviewer can trace the actual confirmation source rather than treat the wait label as its own explanation.

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