47-day UR5e unload ticket still has no defined evidence request

AmyAllen0293 · 17 Aug 2026, 00:46 UTC

Reply to discussion
AM
AmyAllen0293
Our Alibaba-bought UR5e package stops intermittently unloading aluminum spacer blocks. Seller wants more after a phone video. Ticket open 47 days. What would turn that into a specific diagnostic request?

9 replies

AN
AnnaBennett0764
Replying to AmyAllen0293

Ask what they cannot determine from the clip, and send the known occurrence time, active step and readable message if retained. Identify the actual fixture and program revision too. A stationary arm alone leaves too many possible reasons for the same-looking pause.

12 points
NI
NinaAbbott0066
Replying to AmyAllen0293

And ask who will assess the extra material. Sorry, I mean a technical owner who can name the next question, not another sales contact promising to forward it. Forty-seven days is a lot of forwarding.

13 points
AM
AmyAllen0293
Replying to AnnaBennett0764

Technical contact assigned. Clip begins after the stop; no readable message. Retained history has two possible events.

9 points
AN
AnnaBennett0764
Replying to AmyAllen0293

Keep the two candidates separate until you can link one to the filmed occurrence. Check each record's time source and the preceding action, not just similar-looking times. Support can tell you which observations would distinguish them on a later normal supervised run.

5 points
AM
AmyAllen0293
Replying to AnnaBennett0764

One candidate belongs to another program revision. Excluded it from this clip's evidence; the other remains unconfirmed.

10 points
NI
NinaAbbott0066
Replying to AmyAllen0293

That narrows the records, but it doesn't prove the remaining event is the one in the video. Has support accepted that uncertainty and given the shift a focused capture request?

8 points
AM
AmyAllen0293
Replying to NinaAbbott0066

Yes. They want the destination confirmation state with the next observed wait. Normal observation procedure only, no forced stop.

10 points
AM
AmyAllen0293
Replying to AmyAllen0293

New supervised occurrence captured. Displayed step waits for destination confirmation while the spacer remains held. Controls is reviewing the recorded input history with support.

16 points
AN
AnnaBennett0764
Replying to AmyAllen0293

That is a useful occurrence to investigate. It establishes the named wait and observed held block, not whether the destination device or its signal path is faulty. Keep the old unmatched clip separate from this new evidence.

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