What is another FR5 housing pickup nudge actually compensating for?

DineshBell0647 · 24 Aug 2026, 23:37 UTC

Reply to discussion
DI
DineshBell0647
Our FR5 housing grip looks less square while pickup edits accumulate; I want the saved changes and tray-change condition included in inspection, not another reassuring look at a stationary tray.

8 replies

SA
SarahCarter1024
Replying to DineshBell0647

Can you show the housing before contact and after closure? Less square while held does not tell us whether the part arrived that way or turned in the grip.

16 points
CH
ChloeBaker0483
Replying to DineshBell0647

Preserve the affected housings too, if identified. Fresh samples might not carry the feature that made those pickups troublesome.

6 points
DI
DineshBell0647
Replying to SarahCarter1024

The retained examples lean before contact; I had been looking mainly at the lifted view. Maintenance is comparing their seating with the ordinary housings under the inspection procedure.

20 points
EM
EmmaArcher0376
Replying to DineshBell0647

That redirects the enquiry, but doesn't finish it. A raised incoming feature, a mismatched pocket and dirt beneath an insert can all leave a part leaning before pickup. What did the comparison actually find?

12 points
SA
SarahCarter1024
Replying to EmmaArcher0376

Emma's right. Don't rename arm drift as tray fault before the inspection comes back.

24 points
DI
DineshBell0647
Replying to EmmaArcher0376

Quality found excess material on the underside of the affected incoming housings; the specified examples seat normally in the inspected pocket. The affected group is held. Saved pickup edits still need review before release of the job.

-4 points
CH
ChloeBaker0483
Replying to DineshBell0647

Does incoming inspection now have that underside feature in its check? Otherwise the same group can return in a different tray.

18 points
EM
EmmaArcher0376
Replying to DineshBell0647

And retain the limits of the finding. Those identified housings explain the observed leaning examples, not necessarily every edit in the program's history. The reviewer should be able to leave older unexplained changes unresolved rather than invent a single story for all of them.

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.