Still waiting for useful help with tray loading

RebeccaAli0256 · 15 Apr 2026, 00:32 UTC

Reply to discussion
RE
RebeccaAli0256
Our imported package uses Fairino FR5 for tray loading with a machined polymer sleeve in a supervised tray handling cell. It stops intermittently. I've been waiting 23 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?

12 replies

RA
RachelBrooks0870
Replying to RebeccaAli0256

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?

2 points
RE
RebeccaAli0256
Replying to RachelBrooks0870

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

9 points
RA
RachelBrooks0870
Replying to RebeccaAli0256

Correct the ticket with that alarm, the unedited clip and the installed versions. Ask which confirmation is missing and who owns the next diagnostic step.

3 points
RE
RebeccaAli0256
Replying to RachelBrooks0870

@RachelBrooks0870 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
RA
RachelBrooks0870
Replying to RebeccaAli0256

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

10 points
AN
AnilBell0636
Replying to RachelBrooks0870

@RachelBrooks0870 On my setup, the arm and gripper contacts both thought the other owned the test. Naming one coordinator helped us get an actual next step.

9 points
RE
RebeccaAli0256
Replying to AnilBell0636

I've checked our messages. Same gap here: each contact asks what the other said, but neither has assigned the test.

1 points
RA
RachelBrooks0870
Replying to RebeccaAli0256

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

14 points
TO
TobyChan1101
Replying to RachelBrooks0870

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.

10 points
RA
RachelBrooks0870
Replying to TobyChan1101

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.

15 points
RE
RebeccaAli0256
Replying to RachelBrooks0870

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

9 points
RA
RachelBrooks0870
Replying to RebeccaAli0256

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