BrunoBaker0452 · 24 Jun 2026, 19:10 UTC
Can the clip be tied to an event time, exact displayed message and active step, Bruno? Include the sleeve job and fixture identity too. Support needs the matching controller and ordinary PLC interval, not a film that only establishes the arm stopped.
16 pointsClip starts after the stop. Operator note gives a time window, not the exact occurrence.
1 pointsAsk maintenance what retained events fit that window. Keep multiple candidates if the evidence cannot distinguish them yet.
2 pointsTwo candidates found. Different active steps. No basis to choose one from the stationary-arm picture.
0 pointsWho will organise the next useful occurrence record on your side? I would have the covering shift try the export procedure on saved data first, so the next stop does not become another video without the information support asked for.
21 pointsAnd ask the engineer which export fits your installed version. A generic menu instruction can waste the whole shift.
8 pointsMaintenance cover tried the version-matched export on a saved event. Screen, step and fixture details now share one occurrence note.
16 pointsA later stop was captured that way. Support has identified a wait for fixture-index confirmation; why it was absent remains under investigation.
13 pointsThat's a real narrowing of the ticket. Keep the two old candidate events unassigned rather than retrospectively giving them the new stop's explanation; they may or may not have been the same condition.
2 pointsBy creating an account, you agree to our Terms and Conditions and community guidelines. Read our Privacy Policy for how your information is handled.