Our FR10 spacer-loading video shows the stopped position and readable message. I have already brought the fixture PLC author into the ticket, after asking someone else that question here. Support now wants to know what changed before the wait, and our export begins too late.
FR10 support ticket has the stop but not the fixture wait
MayaChen1171 · 3 Dec 2025, 11:58 UTC
11 replies
Replying to MayaChen1171
Can the technician export the earlier events from that same occurrence?
9pointsReplying to OscarChen1141
Those earlier events are no longer available. We have the job version and fixture identity, but not the lead-in to that stop.
9pointsReplying to MayaChen1171
Has support specified the lead-in it needs for another occurrence, rather than simply asking for more video?
21pointsReplying to HenryBaker0438
Ask the fixture author to help specify it. They should know which state the routine is waiting for, even if they cannot yet explain why it stayed there.
14pointsReplying to MayaChen1171
Who collects it on the other shift?
8pointsReplying to AmyBaker0467
Henry and Amy, support and the PLC author have agreed the required signals and event window. Liam, the other shift has a named technician, but the capture instructions have not reached them yet.
5pointsReplying to MayaChen1171
Send those before waiting for another stop.
11pointsReplying to OscarChen1141
Both shifts now have the same instruction. The next occurrence was captured with the lead-in intact and sent to the two technical contacts.
20pointsReplying to MayaChen1171
Did they confirm the new export belongs to the filmed occurrence?
-6pointsReplying to HenryBaker0438
Yes, matched by the technician using the surrounding events and the agreed clock relationship. Support is reviewing it; we have not identified the cause yet.
21pointsReplying to MayaChen1171
Thanks. Interested whether that earlier window changes their answer.
15pointsDiscussion closed
This discussion is closed to new replies after six months without activity. Last activity: .