My FR10 spacer video needs the wait behind the stop

DanielBennett0739 · 22 Aug 2026, 05:50 UTC

Reply to discussion
DA
DanielBennett0739
I know to ask support which observation is missing rather than simply send another film. This FR10 tray-loading package handles aluminium spacer blocks and stops intermittently. The unnamed Alibaba seller has had my ticket eighteen days. What would narrow this particular video into something their technician can act on?

11 replies

EL
ElenaBrown0949
Replying to DanielBennett0739

Start with the exact message and active sequence step for that occurrence, plus the fitted tray, spacer and program references. Tell them what the film actually shows. A visible pause is not necessarily a controller fault, even if the ticket currently calls it one.

2 points
SO
SofiaBaker0456
Replying to DanielBennett0739

Can the video show whether the spacer is still held or already in the tray?

5 points
JA
JamieBrown0904
Replying to ElenaBrown0949

And is the displayed wait readable? I would want the wording before deciding which extra record to ask for, otherwise we may tell Daniel to collect the wrong interface state.

17 points
DA
DanielBennett0739
Replying to JamieBrown0904

Spacer is already in the tray. I can read waiting for tray clear, but the film starts there and doesn't show what immediately preceded it. I've sent that limit with the installed references.

0 points
MI
MiaBaker0470
Replying to DanielBennett0739

Ask who owns tray clear and what it means in this program. The operator may think it means empty while the application means ready to exchange, and neither interpretation should be guessed from those three words.

0 points
EL
ElenaBrown0949
Replying to MiaBaker0470

Mia is right. I would ask the reviewer to identify the requested condition and the observed feedback separately, including the supported way to record them during an ordinary occurrence.

7 points
DA
DanielBennett0739
Replying to ElenaBrown0949

Technician reviewed the program reference and says that label is used for two different waits. They have asked for the active subroutine as well as the ordinary feedback record; the current clip doesn't identify it.

-2 points
SO
SofiaBaker0456
Replying to DanielBennett0739

That explains why the wording alone could not narrow it. Keep both waits in the request.

17 points
JA
JamieBrown0904
Replying to DanielBennett0739

Could the maintainer clarify the two messages for future captures? Not claiming that fixes the stopping condition, but a distinct message could stop the next shift having the same argument over which wait they saw.

-2 points
DA
DanielBennett0739
Replying to JamieBrown0904

They have proposed distinct messages and assigned the capture to our shift lead. Nothing changed in the installed program yet. The ticket is now about an unidentified wait, not a confirmed arm fault.

15 points
MI
MiaBaker0470
Replying to DanielBennett0739

Keep the capture instructions accessible at the station, with the support contact and current ticket reference. Otherwise the person who sees the next pause can do everything right and still send it into a fresh, disconnected enquiry.

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