Fixture assumptions shouldn't live only in someone's head (Fairino FR5)

RachelBell0696 · 19 May 2026, 10:00 UTC

Reply to discussion
RA
RachelBell0696
I'm preparing our inspection-cycle coordination handover for Fairino FR5 in a training inspection station preparing a handover, using a machined bracket. The notes are mostly pendant screenshots without revision details. They show the main routine but omit subprograms, fixture assumptions and expected ordinary PLC signals. I need a usable structure while the original integrator is still available.

3 replies

CA
CallumBennett0708
Replying to RachelBell0696

Can you match the installed revision to a controlled export first? That tells you which program the handover needs to describe.

7points
RA
RachelBell0696
Replying to CallumBennett0708

Our installed revision matches a controlled export, but I've identified screenshots from an older program copy. Their different routine names explain the mismatch in our notes.

13points
CA
CallumBennett0708
Replying to RachelBell0696

@RachelBell0696 Build a call map from that export and list external dependencies with their owners. That should give maintenance what it needs to follow the program.

7points

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.