I trimmed our FR5 support clip to make it easier to watch. Unfortunately I removed the tray exchange immediately before the spacer-unloading wait, which is the bit the seller is now asking about. The original is still on the phone, so this is recoverable embarrassment rather than lost evidence. What should I send beside it so their technical person can follow the job and fixture states, instead of guessing from an arm sitting still?
Done. The longer clip shows a tray exchange and the operator's confirmation before the wait. Our existing log starts afterwards, so I have labelled that gap instead of calling it a complete record.
Ask the author which underlying condition the wait needs, and what preceding events would distinguish the possible paths into it. Your clip may explain what the operator did while still leaving the controller's view of that action unknown.
Their applications contact says the exchange confirmation must reach the job with the new tray identity. They want both values in the capture, including when they changed. Our current export records only the identity at the end.
Have the maintainer check the proposed capture with a known offline sequence before relying on it. Also ask for the operator explanation of that wait; the missing history should not prevent the author explaining the intended behaviour.
The capture check passed after the maintainer added the missing change events. The author also corrected the handover: the screen now distinguishes a tray identified locally from an exchange accepted by the job. No new occurrence yet, so I still cannot explain the original wait.