JasperAdams0116 · 28 Jul 2026, 12:54 UTC
I'm working through an evidence gap on my own ticket. First check what your existing clip actually shows: sleeve position, active tray and the displayed message. Missing observations can be stated plainly instead of inferred from a pause.
15 pointsTray and sleeve visible. Display unreadable. Can't supply that occurrence's exact message from the clip.
10 pointsCan the operator record the message before normal recovery dismisses it? Our habit of clearing first has left that gap before, though capturing it must not interfere with required protective action.
17 pointsAnd do not attach a readable message from another stop as if it supplies this clip's missing evidence.
12 pointsKeep the fixture and tray references with the program revision. The same-looking sleeve can be running in another arrangement, and support needs to investigate the one in the clip rather than the arrangement somebody remembers commissioning.
11 pointsDaniel, agree, but label any revision that wasn't recorded at the event as retrospective information. Current installed details may help the enquiry; they aren't automatically proof of what was active during an older recording.
12 pointsAsk the technical contact which existing event export they need and for the supported procedure. I wouldn't choose diagnostic settings from this conversation. Your first useful bundle can identify the event and state what the video cannot establish.
18 pointsWho will assemble the bundle when you are not on that shift?
13 pointsAnd who reads it at the seller, because a shared sales inbox can acknowledge files without allocating any technical work?
-2 pointsInclude the last observed step before the pause, with ordinary wait conditions left as questions where they are unclear. A stopped motion doesn't by itself identify a robot fault (or establish that the receiving position was available).
10 pointsCan the same event time be found in the controller record, with any uncertainty between that clock and the phone stated?
15 pointsKeep event sequence as well as clock readings; don't align unrelated records merely because the displayed times look close.
7 pointsMaintenance will collect it with the shift. Requested export instructions and a technical owner; no answer yet.
8 pointsLucy, fair correction. I meant identify the event's configuration, not quietly use today's version as historical fact. Jasper can attach today's details too, provided he calls them that and keeps the uncertainty on the older clip.
9 pointsThat is already more useful than a new clip labelled same problem. I'd leave the original occurrence separate, then give any later capture its own identity so the technician can compare rather than inherit a composite event nobody witnessed.
12 pointsI've sent the original clip with its gaps listed. New capture plan agreed internally; no diagnosis or seller action yet.
8 pointsBy creating an account, you agree to our Terms and Conditions and community guidelines. Read our Privacy Policy for how your information is handled.