Our FR10 unload wait appears after the fixture is changed

Fixture-change path says 'fixture ready missing'. Ordinary start proceeds. Same job version, and the fixture is the same one removed and refitted for the demonstration.

Nina, yes, but capture the actual ready condition too. Similar symptoms aren't enough to transplant your fix.

Adrian, who refits the fixture, and can they see the locating faces? On one of our checks it looked seated from the front while the rear contact told another story.

Our setter refits it. She inspected the intended contacts with maintenance and they found it seated correctly. The retained PLC history also shows the ordinary ready condition present during the wait.

Ask the package author which source that waiting branch reads. The screen label alone will not establish it.

Callum, agreed. I should have been clearer that ours is a comparison to request, not a diagnosis for Adrian.

Adrian, do the clip and PLC history cover the same changeover? Keep the identity and event window with the comparison.

Yes, same changeover, identified by our technician. Author compared the branches and found the changeover branch waits for an obsolete internal flag. The ordinary start uses the current fixture-ready condition.

Will they explain why that old flag remains there? The next maintainer needs to know what the replacement branch expects, not only which version to load.

And test the condition absent as well as present. Replacing a wait with unconditional progress would make the demonstration look fixed.

The author says that flag belonged to the earlier fixture handover sequence. Revised logic uses the current agreed condition. Their offline tests cover ordinary start, changeover with ready, and changeover without ready; the last remains waiting.

Useful. Has the revised version been checked through the installed interface with your technician, or only in that offline set?

Installed checks are now complete under our technician's supervision. Ready permits the intended sequence after changeover; without it the wait remains. The setter repeated the normal fixture exchange and unloading completed.

Thanks for reporting the actual finding. Different stale flag from our address problem, same reason to compare branches rather than throw new sensing parts at it.

We closed this ticket with the changed routine version and those test results. The handover now describes the current ready condition and the old flag's removal. No hardware order needed.