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

BrunoChan1061 · 4 Aug 2026, 18:10 UTC

Reply to discussion
BR
BrunoChan1061
I'm preparing our sample verification handover for Fairino FR5 in a maintenance review of a commissioned inspection cell, using a fixture-mounted coupon. 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.

5 replies

LU
LucyChen1176
Replying to BrunoChan1061

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

9 points
BR
BrunoChan1061
Replying to LucyChen1176

@LucyChen1176 I've matched our installed revision to an export. Some screenshots belong to an older copy, though. That explains the names that weren't lining up.

11 points
LU
LucyChen1176
Replying to BrunoChan1061

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.

11 points
BR
BrunoChan1061
Replying to LucyChen1176

@LucyChen1176 I've matched our installed revision and identified the mixed screenshots. The dependency and recovery references still need completing before the handover is ready.

14 points
LU
LucyChen1176
Replying to BrunoChan1061

The revision work is useful progress. Those outstanding dependency and recovery references explain why the handover remains partial.

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