RaviAdams0128 · 25 Jul 2025, 19:04 UTC
Start with the message and program position for the same pause. We had two stops that looked identical from across the room but waited on different stations. The phone video made them look like one fault.
24 pointsFound two messages in the history: tray not confirmed and waiting downstream clear. My video has no visible clock, so I cannot match it confidently to either.
20 pointsThen say that in the ticket. Use a later occurrence with a known time and matching screens rather than giving the old video a message it might never have had.
19 pointsCaptured a later tray-not-confirmed occurrence with the operator's note, tray identity and controller event list. Sent it separately; downstream-clear issue remains another open example.
20 pointsHas the technician named the actual tray confirmation being awaited? That would give maintenance a more useful starting point than treating the whole tray as one suspicious object.
7 pointsRavi, does the tray-not-confirmed one happen straight after a tray swap or partway through an unchanged tray?
4 pointsThe captured case was after a swap. Technician has identified the latch confirmation and requested its trace. Older notes lack enough detail to say every occurrence followed a swap.
16 pointsUseful distinction. When you have that trace, I'd be interested whether the signal is absent or present but not reaching the sequence. Those send you to different places.
7 pointsThis discussion is closed to new replies after six months without activity. Last activity: .