Our UR5e tray-unloading package stops with a housing held, and the seller asked for more information after my video. The ticket has gone round for weeks. I can collect software logs, but I do not want to label every pause a robot fault when the application may be waiting for something.
Start with the exact message and the step it stopped at. We once sent three impressive videos of an arm waiting for a tray sensor. Or rather, waiting for a signal the tray sensor was meant to provide. The wording mattered.
The screen says destination unavailable. It comes from our PLC interface, not a controller alarm. I have corrected the ticket and asked the PLC owner which conditions make that state true.
Good, now give them one occurrence with its matching logs and setup version. Don't bundle a message from one run with a video from another unless you've clearly said they're separate examples.
The matched trace shows the destination occupied input stayed on after the operator emptied the tray. I can report that mismatch, but it does not tell me whether the sensor or its target caused it.
Exactly. Let maintenance check the physical side under their procedure. Your useful contribution is showing what the input did beside what the operator reported seeing, without filling the gap with a diagnosis.
Photograph the relevant setup before parts are moved for inspection. Sensor, target and tray identity. A close-up of just the sensor can leave out the thing it was detecting.
Maintenance found a bent tray flag holding the occupied sensor active. They corrected the tray issue and checked the input. We added the tray photographs to the same event record for the seller.
Has it run since with the corrected tray? I'm glad you found something concrete, but the repair and the observed result should both go into the update.
The supervised checks passed with that tray. Other trays have not all been inspected, so I described this occurrence as explained and left the broader intermittent-stop investigation open.
That's a fair split. Get someone named against the remaining tray checks, otherwise the sensible caveat in your email becomes everybody's reason to wait for somebody else.