Which of our UR5e sleeve-stop messages should support investigate first?

HassanChan1052 · 6 Jan 2026, 06:44 UTC

Closed
HA
HassanChan1052
I've sent the UR5e sleeve-unloading ticket with the program version, exact messages and the held-part view. No more guessing from a clip called robot stopped. But now I have two occurrences with the same final waiting message and different messages before it. The seller wants 'more details' again. I don't know whether these are one problem or two. What would you ask them to distinguish before we film another shift's worth of apparently identical waiting?

9 replies

EM
EmmaBaker0463
Replying to HassanChan1052

Can each earlier message be tied to its own occurrence and original history, rather than only the common ending?

19 points
HA
HassanChan1052
Replying to EmmaBaker0463

Yes, separate exports and job records. One has a destination wait first; the other has a controller message before the same final screen.

8 points
AN
AnikaArcher0421
Replying to HassanChan1052

We had been putting unlike messages into one FR10 ticket because the operator called all of them a stop. Support eventually opened a separate diagnostic question for the controller message, while the fixture capture stayed open. That did not prove two root causes, but it stopped each reply answering only half of what we had sent. I'd ask your seller to identify the question for each occurrence, keeping them linked to the original complaint. You already have the material separated more clearly than we did.

17 points
EM
EmmaBaker0463
Replying to HassanChan1052

Does the destination-wait occurrence include the relevant ordinary confirmation, or is that the missing detail for that one?

7 points
HA
HassanChan1052
Replying to EmmaBaker0463

That's the missing bit, Emma. We have the request but not the confirmation history covering that interval. The controller-message occurrence has its surrounding event list.

17 points
AN
AnikaArcher0421
Replying to HassanChan1052

Then say exactly that in the next message. Ask for a capture requirement for the fixture wait and an explanation of the controller event. Neither needs to be guessed from the shared ending.

14 points
HA
HassanChan1052
Replying to AnikaArcher0421

Seller has accepted those as separate questions. Local controls author is defining the missing confirmation capture. No one has diagnosed either occurrence yet.

9 points
HA
HassanChan1052
Replying to AnikaArcher0421

Thanks Anika. I had the files separated but was still asking one enormous question over the top of them.

25 points
EM
EmmaBaker0463
Replying to HassanChan1052

Who will make sure the agreed confirmation capture reaches both shifts?

0 points

Discussion closed

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