The complete export and dependency list, tied to the installed revision.
简体中文界面。帖子、指南及政策正文保留原文;未对原文作自动翻译。
An FR10 inspection handover without the called routines
AlexBell0646 · 2025年8月21日 12:14 UTC
12 条回复
Requested. They sent a folder called final, but its main routine name differs from our screenshots.
7分Ask which installed version it matches. Final isn't a revision identifier.
9分Get 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.
7分Our maintainer found a local routine rename. Integrator is comparing the export with the installed set.
15分They've matched the renamed routine. Camera recipe and ordinary PLC signal list are still missing.
21分Keep the handover open for those. Matching the routine name was only one gap.
22分Ask 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.
12分Recipe found on the integrator's laptop. Transfer and access arrangement agreed, not yet checked from our maintenance account.
13分And 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.
1分Fixture F3, Sam. Drawing and installed label agree. Maintenance-account verification remains outstanding. Thanks Anika for asking about access.
4分Have 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.
23分讨论已关闭
此讨论已连续六个月没有活动,现已关闭新回复。 最后活动: .