Start with the installed main routine and follow its calls. Get the integrator to identify the versions as they go. Screenshots can illustrate that list, but they are a poor substitute for it.
Our FR10 handover screenshots skip the routine that decides the result
Evan_Blair · 11 Dec 2025, 07:00 UTC
18 replies
Start with one ordinary bracket passing through, too; a perfect call list can still leave the next person wondering which insert belongs on the bench
19 pointsThat's the annoying bit, Anika. The notes say 'standard nest' and stores has two inserts. I'll bring both to the walkthrough, not choose the shinier one.
14 pointsWho is the handover intended to support: someone teaching the established exercise, or someone modifying it? The first person needs clear limits and help routes; the second also needs enough detail to assess the consequences of a change.
-4 pointsJo, can that call list show where the ordinary PLC handshake enters? A routine can look stuck when it's waiting for a signal nobody put in the notes.
8 pointsYes. Put the signal meaning and source beside each wait, plus the expected response and timeout behaviour. Keep the ordinary sequence separate from the safety functions and their documentation.
14 pointsPavel, teaching the established exercise first. Any modifications go back for review. The integrator identified the current insert as B and found the result-selection routine missing from our export as well as the notes.
11 pointsThen keep the old insert out of that lesson's kit, with its own identity intact; hiding it behind a better sentence is optimistic
3 pointsEvan, does the installed routine match the screenshots anywhere, or are you rebuilding the whole guide from a different version?
13 pointsMain routine matches. The screenshots stop before the result-selection call, so they weren't enough even when taken. We're getting the missing dependencies into the handover rather than rewriting the working program.
21 pointsAaron's signal point is worth doing during that walkthrough. Ask the integrator to explain a normal rejected sample too, not only the easy green result.
7 pointsAnd where should a tutor stop when the actual station differs from the guide? A clear contact and escalation step is more useful than expecting them to diagnose an unfamiliar dependency during a lesson.
13 pointsWe've named the equipment coordinator for that, with the station held if the fixture or version doesn't match. The integrator's walk-through covered an accepted bracket and a normal reject. Both use the newly listed routine.
13 pointsThanks for checking the reject, Evan. Who will keep the guide aligned after the next reviewed change?
11 pointsAnd give the relief tutor the guide before explaining it. The original author is a very effective missing page.
5 pointsAnika, yes. A read-through with the author answering every hesitation only tests how well the author remembers the station.
6 pointsEquipment coordinator owns the controlled copy, Aaron. A relief tutor read it and couldn't work out which screen showed the selected bracket family. We've added that view and are checking the revised page.
12 pointsDoes that page show how the selected family is checked against insert B, rather than merely showing where the selection appears?
4 pointsDiscussion closed
This discussion is closed to new replies after six months without activity. Last activity: .