I've sent the references. Video starts after the stop, with the pendant too small to read. Exact message missing from that occurrence.

I have a similar evidence gap in my own ticket. Does your clip at least identify the active fixture and show the spacer position clearly? Those could still be useful without pretending it contains the message.

Fixture visible, spacer partly hidden by the fingers. I've described that limitation in the attachment note. Support hasn't specified logs yet.

Who can describe what happened before the camera started? The operator may remember a tray change or a particular sequence step. I wouldn't call that proof of cause, but it gives support context that a stopped-arm film cannot.

Keep recollection separate from recorded evidence, especially if somebody has already reset the screen before remembering what it said.

Agreed, Elliot. I mean their own description, labelled as such. Better an honest recollection with limits than making the report look complete by assigning a message nobody recorded.

Ask the shift to record the next normal occurrence under the approved procedure. No deliberate stop provocation needed for a better report.

Shift lead has that request. Thanks, Leo; the operator could describe the preceding step, so I've added it as recollection rather than a logged event.

Do you have one ticket owner keeping these additions together? I'm finding that separate replies can leave the technical person reading an older attachment set.

One indexed event bundle would help, but don't discard earlier versions of the evidence when the interpretation changes.

I'm maintaining the attachment list. No new stop captured yet. Seller has acknowledged the extra references, but hasn't answered the export question.

Can your installer help identify the supported export for the installed version while the seller answers? That would be useful local assistance, provided they actually know this package and don't guess at a generic procedure.

Keep the supplier's unanswered request visible too. Local help doesn't mean the original report suddenly contains the missing event records.

Installer is checking what they can supply. I still have no matched message or log for the first stop, and I'm leaving its cause undecided.

Please post what export they identify. I'd be interested in the process of getting the right evidence, even if the actual cause turns out quite different from ours.