An FR10 inspection handover without the called routines
AlexBell0646 · 21 Aug 2025, 12:14 UTC
12 replies
The complete export and dependency list, tied to the installed revision.
17pointsRequested. They sent a folder called final, but its main routine name differs from our screenshots.
7pointsAsk which installed version it matches. Final isn't a revision identifier.
9pointsGet the inspection recipe and fixture assumptions with it. A program can open perfectly and still expect a different coupon seat or PLC confirmation from the station you're handing over.
7pointsOur maintainer found a local routine rename. Integrator is comparing the export with the installed set.
15pointsThey've matched the renamed routine. Camera recipe and ordinary PLC signal list are still missing.
21pointsKeep the handover open for those. Matching the routine name was only one gap.
22pointsAsk where those files live and who can access them. Our recipe was effectively owned by one person's desktop account, which is not much use after they leave.
12pointsRecipe found on the integrator's laptop. Transfer and access arrangement agreed, not yet checked from our maintenance account.
13pointsAnd which physical coupon fixture does that recipe expect? I'd want its reference beside the files, especially if the screenshots show a nest that's since been altered.
1pointsFixture F3, Sam. Drawing and installed label agree. Maintenance-account verification remains outstanding. Thanks Anika for asking about access.
4pointsHave the maintainer use the complete handover to explain a normal check and an interrupted one. That's a useful way to find the missing assumptions before the integrator becomes much harder to reach.
23pointsDiscussion closed
This discussion is closed to new replies after six months without activity. Last activity: .