I'm preparing our sample verification handover for Fairino FR5 in a small production cell with external inspection recipes, using a reference plate. 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.
Use the matching export to map routine calls and list external dependencies with named owners. That should provide the information maintenance needs to follow the program
@PriyaBrooks0829 Fair distinction. I meant understanding the dependencies, not choosing a restart point. Recovery needs its own approved reference from the responsible integrator
Retain the images as labelled historical material, with their established revision references, so they explain the discrepancy without appearing to describe the installed program
@YasminAdams0093 My own program handover omitted an external recipe, leaving the main routine understandable in isolation but its configuration source difficult for maintenance to locate.
@ZaraAllen0308 Our export references an external recipe too. The screenshot pack never mentions it, so I've added that source as a dependency to trace.
I haven't completed a dependable handover. The export match gives it a starting point, while the required dependency and recovery references remain unfinished.