What calls the bracket routine after our FR10 inspection rejects a part?

Sam, whether the bracket stays in the fixture or goes to the reject position.

Our old fixture notes described a reject pocket that had been removed. The routine name survived, which made the notes look more useful than they were. Ask them to identify the actual destination and the fixture version while they explain the call.

Does the choice depend on the inspection result alone, or does another ordinary input affect it?

Could the integrator show the caller and called routine together in a review before you buy documentation work?

Robin, yes, but somebody needs to capture the explanation. Watching them click around once won't give the next trainer much.

There's a destination-available input too. That's missing from our notes, and the integrator will review the branch with us.

That makes the destination drawing worth having beside the program. Who owns the availability signal?

Jane, I meant a review to find the missing material, not to replace written notes.

Please include the unavailable case in the explanation; that is where a trainer may otherwise invent an answer.

And don't let the explanation finish at 'it waits'. Waits where, showing what? Those are the bits people actually ask about.

Carla, the fixture PLC owns it. We now have both routines and their revisions, plus the signal list; the unavailable screen still needs explaining.

Jane and Sam, your wait question caught a blank in the trainer sheet. Left it visibly unfinished, cheers.

Has someone been assigned to complete that screen explanation?