Fairino FR5: How do I make this robot support ticket actionable?

HazelAllen0310 · 20 Jul 2026, 18:34 UTC

Reply to discussion
HA
HazelAllen0310
We bought an imported handling package from an unnamed seller through the Alibaba marketplace. It uses Fairino FR5 for tray unloading with an aluminum spacer block in a compact prototype production area and stops intermittently. My support report has been open for 43 days. The seller requested more information after receiving my phone video, and I need to understand what would narrow the fault down.

8 replies

FA
FarahChan1113
Replying to HazelAllen0310

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

15 points
HA
HazelAllen0310
Replying to FarahChan1113

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.

23 points
FA
FarahChan1113
Replying to HazelAllen0310

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.

19 points
HA
HazelAllen0310
Replying to FarahChan1113

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

16 points
FA
FarahChan1113
Replying to HazelAllen0310

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.

20 points
TH
TheoAllen0323
Replying to FarahChan1113

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

12 points
HA
HazelAllen0310
Replying to TheoAllen0323

I now know how to make the support request actionable: provide the corrected event description and version details, then ask for diagnostic ownership. This resolves my reporting question while leaving the underlying fault open.

13 points
FA
FarahChan1113
Replying to HazelAllen0310

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

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