The FR10 screenshots name the coupon routine but not its revision or the called checks. I have asked the integrator for the matching program set. How should I tie those files to the fixture assumptions in the handover?
our coupon handover shows a routine without identifying its dependencies
PavelBaker0440 · 20 Feb 2026, 15:25 UTC
2 replies
Replying to PavelBaker0440
Use one checked inventory linking program revisions, called routines, fixture identity and expected ordinary PLC confirmations.
9pointsReplying to SofiaBrown0891
Integrator supplied the inventory but one called routine is still absent from the export. I've returned that specific gap. No point calling it a complete handover because the top-level screenshot matches.
-2pointsDiscussion closed
This discussion is closed to new replies after six months without activity. Last activity: .