The exact message from that stop, if it's still available. Somebody calling it a collision is not the same thing as the controller reporting one
What actually stopped this sleeve-unloading job?
NathanChen1156 · 7 Apr 2025, 22:11 UTC
18 replies
The operator says there was no collision message. He used that term because the arm stopped near the tray. I have removed it from the ticket's confirmed facts.
23 pointsGood. Which program step was active? Even knowing whether it was waiting for something or executing a move would help
25 pointsThe saved screenshot shows a wait in the application. It is waiting for a tray-present condition, after the previous tray was removed.
20 pointsThen start at that condition. Ask who supplies it and what the application actually received at the time
22 pointsWe once chased a robot pause that was a sticky fixture confirmation. Was the replacement tray fully located when the operator took the video, or merely sitting somewhere in the loading area?
17 pointsHe believes it was located. The camera does not show the stops or latch, so I cannot verify that from the recording.
6 pointsKeep his observation, just label it as his observation. It may be right; the missing camera angle doesn't make it false
12 pointsOur relief shift was parking trays against the wrong stop after cleaning. Photograph the intended seated position for the report. It also gives whoever takes the next shift a useful reference.
-6 pointsAnd compare that with the actual locator arrangement. A photo from before a tooling change can be worse than no photo
21 pointsDon't go straight from this to blaming the operator. You're still missing the input history, and the tray could be seated with the signal absent.
10 pointsAgreed. We have a wait condition to investigate, not a culprit. The physical seating and reported input both need checking
15 pointsMaintenance found the current input name and traced it to the tray latch sensor. They will inspect that assembly during the planned stop. No input is being bypassed to get past the wait.
13 pointsHave they found anything yet? The sensor name at least gives the seller's controls person something specific to follow
10 pointsAlso ask whether the latch has more than one physical position that feels closed. Ours had enough play to fool your hand while the sensor still said no (not the operator's fault).
19 pointsMaintenance has found play in the latch bracket. It can feel seated before the sensor changes. They are checking the correct bracket position against the tooling documentation before repair.
16 pointsThe seller's controls contact now has the wait step, input name and bracket photographs. Repair and verification are pending. The original collision diagnosis had no basis in the records.
24 pointsThat's a much better ticket. Let the bracket check finish before closing it; finding a plausible fault isn't yet a clean run
6 pointsDiscussion closed
This discussion is closed to new replies after six months without activity. Last activity: .