Our aluminium-spacer unloading ticket is 19 days old. I am keeping the filmed event separate from possible earlier history, as in my housing-stop question. Here the missing detail is the active step. What would let support match this bench occurrence to the supplied sequence?
Get the installed program and fixture identity into the ticket now. Ask the supplied sequence owner which occurrence details they need; an unreadable step should not make you reverse-engineer their whole program.
Installed export identified. Fixture label matches the current tooling record. The retained event list gives a wait message, but the phone clip does not show the corresponding input states.
Ask them to map that wait to the relevant conditions in this revision. Do not turn a message naming a confirmation into a diagnosis of the sensor providing it.
Support identified a receiving-fixture confirmation in the supplied routine. Actual state at the occurrence remains unknown. They have requested the contributing state history with the next identifiable occurrence.
Have your controls person establish what can be retained and how it links to the event time before the next stop. Otherwise the same request returns with a different filename.
Controls has agreed the capture method and clock reference. No new occurrence captured yet. Thanks Thomas; the ticket now asks a specific question about that wait, not whether the arm generally works.