Which receiver condition should accompany our FR10 spacer stop?

OliverBarnes0537 · 28 Mar 2026, 03:50 UTC

Reply to discussion
OL
OliverBarnes0537
Our FR10 spacer-loading ticket has been open 34 days. Video shows a seated receiving tray and a waiting job. Support asks for more, but nobody has identified which receiver condition they cannot see.

14 replies

EL
ElenaBaker0514
Replying to OliverBarnes0537

What does the operator screen call that wait? Need the exact wording, not just robot stopped.

9 points
OL
OliverBarnes0537
Replying to ElenaBaker0514

Receiver not available. Our integrator says that message covers more than one condition, so I have asked for the actual installed branch behind it.

16 points
EL
ElenaBrown0949
Replying to OliverBarnes0537

Then ask support and the integrator to name the required history together. You should not have to guess which of those conditions their next email means.

9 points
OL
OliverBarnes0537
Replying to ElenaBrown0949

They identified receiver latch confirmation. The retained trace shows it dropping before the wait. Our phone view cannot show whether the latch is properly engaged.

10 points
CA
CallumAdams0099
Replying to OliverBarnes0537

Give maintenance the latch assembly identity with that interval. A tray looking seated from above is not much help with the engagement underneath.

0 points
LI
LinAdams0096
Replying to CallumAdams0099

Callum, yes, and let the job author explain the response too; a real loss of confirmation may be exactly why the job waits, rather than the program needing a way around it.

24 points
EL
ElenaBaker0514
Replying to OliverBarnes0537

Does the covering operator know to call maintenance for that condition?

15 points
EL
ElenaBrown0949
Replying to CallumAdams0099

Oliver, did maintenance find anything in the latch? Or is the captured change still unexplained?

7 points
OL
OliverBarnes0537
Replying to ElenaBrown0949

Excessive play in the latch assembly, confirmed against its service information. Maintenance has arranged the specified repair. Elena Baker, cover knows the hold-and-call route; the screen wording is being made more specific.

0 points
CA
CallumAdams0099
Replying to OliverBarnes0537

Worth keeping the removed assembly identified until the repair check is done. The next shift should not find it in the usable-spares box.

16 points
LI
LinAdams0096
Replying to OliverBarnes0537

And include the ordinary tray exchange in that check, Oliver, because a receiver left untouched for the entire demonstration does not tell your covering operator much about the next changeover.

21 points
EL
ElenaBrown0949
Replying to OliverBarnes0537

Has the repaired latch been tried with the trays that gave the recorded stops? I mean the identified trays, not merely another tray of the same colour.

5 points
OL
OliverBarnes0537
Replying to ElenaBrown0949

Maintenance and the integrator completed the agreed return check with those trays and normal exchanges. Latch confirmation remained stable. The installed message now names that wait, and cover followed the revised response in the handover exercise. We closed the captured fault with support.

10 points
EL
ElenaBaker0514
Replying to OliverBarnes0537

Useful outcome. Is the more specific message also in the operator's printed fault list?

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