Getting past 'please send details' for Fairino FR5

OmarAdams0143 · 2 Sept 2026, 03:08 UTC

Reply to discussion
OM
OmarAdams0143
Our imported package uses Fairino FR5 for fixture loading with a molded connector body in a small parts assembly workshop. It stops intermittently. I've been waiting 19 days since reporting it to the unnamed seller we bought from through Alibaba. I sent a phone video; they asked for more information. Fair, but what would actually help?

10 replies

RA
RachelAllen0348
Replying to OmarAdams0143

The alarm text and sequence position would help focus your report. Do you've the alarm as displayed before restart, and can you place the stop relative to release?

10 points
OM
OmarAdams0143
Replying to RachelAllen0348

I now have the alarm indicating a missing process confirmation. Reviewing the unedited video places the wait before release, so my original description of a dropped workpiece was inaccurate.

20 points
RA
RachelAllen0348
Replying to OmarAdams0143

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.

21 points
OM
OmarAdams0143
Replying to RachelAllen0348

Should I preserve the original report when I correct it? Removing that wording might make it difficult to understand why support's existing replies focused on a drop.

4 points
RA
RachelAllen0348
Replying to OmarAdams0143

Leave the original account readable and add the correction prominently. Explaining that the unedited recording shows a wait before release gives support a reason to revise its diagnostic focus.

8 points
FA
FarahBaker0504
Replying to RachelAllen0348

@RachelAllen0348 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.

17 points
OM
OmarAdams0143
Replying to FarahBaker0504

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.

17 points
RA
RachelAllen0348
Replying to OmarAdams0143

Given the missing confirmation, the gripper seems to be the source of the problem. I'd ask its support contact to lead the diagnosis.

8 points
OM
OmarAdams0143
Replying to RachelAllen0348

@RachelAllen0348 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.

3 points
RA
RachelAllen0348
Replying to OmarAdams0143

That answers the reporting problem without claiming a repair. The corrected symptom gives the next request a useful focus.

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