RaviBarnes0563 · 19 Jul 2025, 13:28 UTC
Pick one occurrence you can identify from the shift notes and event history. A complete example will help more than another unlabelled video of the arm waiting.
8 pointsI found an entry linked to the operator's tray-change note, with waiting unload fixture returned on the screen; the fixture was U4, which was missing from my first email.
9 pointsAsk the integrator which confirmation that message means. Then capture that state and the program step for the same occurrence, not a similar-looking pause from another shift.
17 pointsThey have named the return confirmation and asked maintenance to inspect its target, while the controls technician prepares the capture; no cause confirmed yet.
6 pointsHas anyone checked whether the message occurs only after U4 is exchanged? That pattern would be useful even before the target inspection gives an answer.
15 pointsAre there records from the other fixture as well, Ravi? Absence from the notes may mean nobody wrote it down, not that it never happened.
16 pointsThe recorded cases all name U4 after exchange, but the older notes omit fixture identity, Jamie, so I cannot say the other fixture has never done it.
18 pointsMaintenance found a damaged target mount on U4 and has repaired and checked it; we are arranging a supervised comparison after exchange, with fixture identity included in each record.
11 pointsLet support know both the repair and that the exchange comparison is still pending. They may want something specific captured before they close the ticket.
21 pointsThis discussion is closed to new replies after six months without activity. Last activity: .