What actually stopped this sleeve-unloading job?

NathanChen1156 · 7 Apr 2025, 22:11 UTC

Closed
NA
NathanChen1156
I have inherited a support ticket for an FR5 tray-unloading package bought through a seller on Alibaba. The ticket says collision fault. The supplied video shows a stationary arm and a sleeve still in the tray, with no visible message. I want to correct the report before anyone adjusts a collision setting. What should I ask the workshop to retrieve?

18 replies

TH
ThomasBrooks0799
Replying to NathanChen1156

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

12 points
NA
NathanChen1156
Replying to ThomasBrooks0799

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 points
TH
ThomasBrooks0799
Replying to NathanChen1156

Good. Which program step was active? Even knowing whether it was waiting for something or executing a move would help

25 points
NA
NathanChen1156
Replying to ThomasBrooks0799

The saved screenshot shows a wait in the application. It is waiting for a tray-present condition, after the previous tray was removed.

20 points
TH
ThomasBrooks0799
Replying to NathanChen1156

Then start at that condition. Ask who supplies it and what the application actually received at the time

22 points
WI
WillChan1096
Replying to NathanChen1156

We 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 points
NA
NathanChen1156
Replying to WillChan1096

He believes it was located. The camera does not show the stops or latch, so I cannot verify that from the recording.

6 points
TH
ThomasBrooks0799
Replying to NathanChen1156

Keep his observation, just label it as his observation. It may be right; the missing camera angle doesn't make it false

12 points
ZA
ZaraBennett0743
Replying to NathanChen1156

Our 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 points
TH
ThomasBrooks0799
Replying to ZaraBennett0743

And compare that with the actual locator arrangement. A photo from before a tooling change can be worse than no photo

21 points
AN
AnilAllen0288
Replying to ZaraBennett0743

Don'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 points
TH
ThomasBrooks0799
Replying to AnilAllen0288

Agreed. We have a wait condition to investigate, not a culprit. The physical seating and reported input both need checking

15 points
NA
NathanChen1156
Replying to ThomasBrooks0799

Maintenance 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 points
TH
ThomasBrooks0799
Replying to NathanChen1156

Have they found anything yet? The sensor name at least gives the seller's controls person something specific to follow

10 points
WI
WillChan1096
Replying to NathanChen1156

Also 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 points
NA
NathanChen1156
Replying to WillChan1096

Maintenance 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 points
NA
NathanChen1156
Replying to ThomasBrooks0799

The 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 points
TH
ThomasBrooks0799
Replying to NathanChen1156

That's a much better ticket. Let the bracket check finish before closing it; finding a plausible fault isn't yet a clean run

6 points

Discussion closed

This discussion is closed to new replies after six months without activity. Last activity: .