Getting past 'please send details' for Universal Robots UR5e (fixture loading)

RaviAbbott0041 · 21 Jul 2026, 19:24 UTC

Reply to discussion
RA
RaviAbbott0041
We bought an imported handling package from an unnamed seller through the Alibaba marketplace. It uses Universal Robots UR5e for fixture loading with a rigid plastic housing in a compact prototype production area and stops intermittently. My support report has been open for 48 days. The seller requested more information after receiving my phone video, and I need to understand what would narrow the fault down.

16 replies

CA
CarlaBarnes0575
Replying to RaviAbbott0041

@RaviAbbott0041 Have you captured the exact alarm before restarting? Also, does the stop happen before release, during it, or after it?

19 points
RA
RaviAbbott0041
Replying to CarlaBarnes0575

@CarlaBarnes0575 Captured it: missing process confirmation. The unedited video shows a wait before release. I'd described it as a dropped part, which didn't help.

7 points
CA
CarlaBarnes0575
Replying to RaviAbbott0041

Send a corrected description supported by the exact alarm, full recording and installed version details. Ask support to identify the expected confirmation and assign responsibility for the next diagnostic action

15 points
RA
RaviAbbott0041
Replying to CarlaBarnes0575

@CarlaBarnes0575 Worth leaving my original description visible? It's wrong, but deleting it might make the replies look odd.

10 points
CA
CarlaBarnes0575
Replying to RaviAbbott0041

Keep it with a clear correction. Explain that the full clip shows a pre-release wait; that tells support why the investigation needs to change direction

16 points
LO
LouisAli0224
Replying to CarlaBarnes0575

@CarlaBarnes0575 My own support case stalled because the robot and gripper contacts each expected the other to arrange the test. A named coordinator clarified who would organise the next action.

3 points
RA
RaviAbbott0041
Replying to LouisAli0224

@LouisAli0224 Our correspondence shows a similar coordination gap. Both contacts refer me back to the other's response, and I can't find an assigned owner for the test.

-1 points
CA
CarlaBarnes0575
Replying to RaviAbbott0041

@RaviAbbott0041 That missing confirmation points to the gripper, so its contact should take the diagnostic lead

19 points
AN
AnikaAbbott0073
Replying to CarlaBarnes0575

@CarlaBarnes0575 You're jumping from a missing signal to a failed component. It could be the interface or sequence. The alarm doesn't assign ownership by itself.

9 points
CA
CarlaBarnes0575
Replying to AnikaAbbott0073

You're right; I assigned the cause too early. Ask the package seller to coordinate tracing that confirmation across the interface, with both contacts involved as needed

14 points
LE
LeahAllen0321
Replying to CarlaBarnes0575

When you say the seller should coordinate this, do you mean Alibaba or the business that supplied the package through the marketplace?

7 points
CA
CarlaBarnes0575
Replying to LeahAllen0321

The unnamed seller who supplied your package. Alibaba is the marketplace; your technical request here is to the seller and their support contacts

17 points
RA
RaviAbbott0041
Replying to CarlaBarnes0575

@CarlaBarnes0575 Would you send every log I've? There are lots, and I don't know which ones cover the stop.

-1 points
CA
CarlaBarnes0575
Replying to RaviAbbott0041

Ask which diagnostic files they need and provide the ones you can tie to the event. Include collection context; unrelated bulk can hide the useful bit

25 points
RA
RaviAbbott0041
Replying to CarlaBarnes0575

@CarlaBarnes0575 I've got a usable next request now: the corrected alarm and clip, version details, and a named diagnostic owner. That settles how I'll approach support; the actual fault is still to be diagnosed.

1 points
CA
CarlaBarnes0575
Replying to RaviAbbott0041

Your next request is now tied to the event you captured. It's clear that this is progress in the support process, with diagnosis still outstanding

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