Why does our FR5 handover stop where the inspection helper starts?

Integrator has identified the installed package. Two pictures are from an earlier helper revision. We're keeping them out of the current lesson while the matching set is assembled.

Put the expected fixture and ordinary PLC conditions beside the step that uses them. Another separate signal list won't help the tutor work out why this particular step is waiting.

And start with the tutor explaining one normal inspection back to the integrator. You'll hear the missing assumptions faster than by asking whether the new document looks complete.

Does the package identify the coupon and fixture setup expected for that lesson, Pavel? I mean the installed insert and inspection configuration as well as the routine names.

Anna, it identifies the insert but not the inspection configuration used in the pictures. Integrator is adding that link. Hazel, we've started putting each ordinary condition beside its wait.

Keep ordinary conditions distinct from the independently engineered safety functions. The tutor must not learn that changing an application flag is a recovery method.

Yes, Henry. Teach the meaning of the wait and the agreed call for help, not secret shortcuts to make it disappear.

First walkthrough failed in a useful way. Tutor thought received meant the coupon had passed. It only meant the application had retained the inspection request. The result arrives later.

Change the message as well as the lesson. A clear paragraph is fighting uphill if the screen still gives the tutor the wrong idea.

Can you show the exact current wording, Pavel? It would help distinguish an ambiguous caption from a missing explanation of the next step.

It says inspection accepted. Author is changing it to request received, awaiting result. The result state will be separate, including a missing or mismatched result.

That's much better. Have the tutor explain a normal delayed result too. Not every wait needs somebody to arrive with a laptop.

And a result for a different coupon, Pavel, so the lesson does not imply any arriving result finishes the current one.

Keep the coupon identity visible in both examples. It shouldn't require opening a hidden diagnostic page to see which result the message is talking about.

Hazel, agreed. That also gives the covering tutor something definite to report if the identities disagree.

Second walkthrough passed the normal wait, absent result and wrong-coupon examples without hints. Tutor found the named support route and the matching configuration from the package. Thank you, Yasmin, explaining it back exposed more than our checklist did.

Integrator completed the agreed station checks with the tutor. Current package and lesson issued together; old screenshots withdrawn from both teaching copies. We can finally hand this over without lending out the author as well.

A useful handover, and a useful record of what the first walkthrough got wrong. Keep that example for the next revision review.