the FR5 sleeve pause needs a matched event report
KaiBrooks0802 · 2 Sept 2025, 04:37 UTC
13 replies
One of our tickets improved when we tied the video to the exact message and sequence step. Put this station's equipment and fixture references at the top, then ask support which input trace they need for that occurrence.
14pointsOur technician has the station and program references, but the video starts after the message clears; I have asked for a fresh matched capture and told support the old clip's limitation
18pointsCan the message be recovered from the existing event history? Worth asking the technician before waiting for another stop, though it would still need linking to the video time.
4pointsEvent history has several waits and I cannot link one confidently to that clip, so I have sent them as separate records with that uncertainty stated
9pointsThen let support say which wait needs more detail. A list of old events can help them ask a narrower question, without pretending one of them is definitely the filmed stop.
12pointsWho is collecting the evidence when this happens on a different shift? We lost useful messages because everyone thought the person who opened the ticket would be there to photograph them.
17pointsBoth shift technicians now have the capture note, Chen, and support has requested the receiving-tray confirmation state with the active step and message
6pointsHas a new occurrence been captured with those details yet? Curious whether it points to the same wait as the older event list.
13pointsNot yet, Jamie; we have the collection plan but no new matched event to compare
15pointsKeep the request open as awaiting evidence. I would also ask controls what contributes to receiving-tray confirmation, so the technician knows which physical area the eventual message refers to.
18pointsDoes the removable tray have its own identification?
10pointsYes, Caleb, tray T8 is identified separately; controls says confirmation includes tray presence and the selected setup, and both values are now on the requested trace
20pointsUseful to have both. Keep the operator's own description beside the trace too, since they may notice a tray-change problem that the screen compresses into one unhelpful word.
5pointsDiscussion closed
This discussion is closed to new replies after six months without activity. Last activity: .