Our imported UR5e fixture-loading package pauses intermittently. I've sent the seller a video and got 'more information please' back. The picture shows where it stopped, but not the message at the time. Or the job version. What should I pull together so we can get beyond this fairly useless exchange?
We got nowhere until we sent one stop with its actual message and matching log. My first video was basically a tour of a machine that had already stopped. Start there, and include which job and tool setup were running.
Operator had a photo I hadn't seen. Application says waiting for nest empty. I've sent that with the job version and asked controls for the input trace from the same occurrence.
Operator says it was empty. The photo doesn't show inside, so I can't back that up from the image. Trace has the occupied input on. Local maintenance is looking at the nest and sensor setup.
Ask them to look at what the sensor sees around an empty nest too. On ours a loose label was enough to keep a presence signal on. That took a ridiculous amount of emailing to discover.
One nest. Maintenance found its target bracket displaced; the input stayed on when empty. They've corrected and checked it. The matched event is explained, with the trial still being watched for other stops.
Send that back on the existing ticket. And put the nest identifier in the local fault note, so the next person doesn't start with 'the robot has stopped' all over again.