The FR10 handover shows a routine but not what it depends on

ChenAdams0094 · 6 May 2026, 15:13 UTC

Reply to discussion
CH
ChenAdams0094
Our sample-verification notes are pendant pictures without revisions. I can see the main routine, but not the called routines, fixture assumptions or ordinary PLC signals it expects. The original integrator is still available. What should I ask them to explain first?

4 replies

JA
JasperArcher0377
Replying to ChenAdams0094

Walk one normal job through with them and list every dependency encountered: program and called routines, fixture identity, expected ordinary signals, and where their definitions live. Then identify the installed revisions. Screenshots can illustrate that map, but they can't replace the missing relationships.

10 points
CH
ChenAdams0094
Replying to JasperArcher0377

We have arranged that walkthrough. I also asked for a waiting case because another support exchange left us unsure what the fixture step expected to confirm. I mean the ordinary job behaviour, not the separately assessed safety functions.

7 points
JA
JasperArcher0377
Replying to ChenAdams0094

Yes, and record who owns each explanation after the integrator leaves. A good description that nobody can update will get stale as soon as the fixture or routine changes. Have the maintainer follow the draft while the integrator can still answer questions.

12 points
DA
DavidCarter1041
Replying to JasperArcher0377

Keep unresolved dependencies visible in the draft rather than filling them from guesswork; a box saying which answer is missing is more useful than a confident but invented signal meaning.

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