简体中文界面。帖子、指南及政策正文保留原文;未对原文作自动翻译。

I cannot diagnose our UR5e sleeve-unloading stops from this clip

JaneAbbott0075 · 2026年7月26日 14:40 UTC

回复讨论
JA
JaneAbbott0075
I've had a support request open with our Alibaba seller for 12 days over intermittent UR5e sleeve-unloading stops. They asked for more information after my phone video. What should I collect so we can distinguish a sequence wait from something failing, rather than just film the stationary arm again?

14 条回复

GA
GabrielAbbott0018

Does your video show the message when the stop happens?

0
JA
JaneAbbott0075

It starts after the arm has stopped. I can see the sleeve, but the display isn't readable. I have no exact message for that occurrence.

10
TH
ThomasBarnes0538

Send the installed software and program references now. Ask support which event export they need, then match the next capture to its timestamp and active step.

10
TH
TheoAllen0323

What's the operator's account of the few seconds before your clip, Jane? Doesn't need to be a diagnosis. On shift I'd want their own description beside the files, especially if the stop followed a tray change or manual intervention.

15
JA
JaneAbbott0075

The operator says it happened during the normal unloading sequence, with no recent manual intervention they recall. I've added that as recollection and requested the export instructions. Configuration references have gone to support.

9
JA
JamieCarter0991

Keep normal sequence as context, not proof that every earlier stop was the same event.

23
GA
GabrielAbbott0018

Did support say which additional information was missing, beyond asking for details?

22
JA
JaneAbbott0075

They've now named the log export and asked for the active step and fixture state from the same occurrence. We haven't captured another stop yet, so those are still outstanding.

15
TH
TheoAllen0323

Give that request to the person who will actually be there, then agree who forwards the material. Otherwise it sits in your email while the shift sees another pause and assumes support already has enough video.

8
TH
ThomasBarnes0538

Preserve the physical observation as well as commanded fixture state. The command can be present while the condition it requests remains unconfirmed.

16
JA
JaneAbbott0075

We have a matched capture now. The screen identifies a waiting step, and support has asked our controls owner to compare its expected fixture feedback. That doesn't yet establish which part of the system is responsible.

1
JA
JamieCarter0991

Exactly. A named wait gives you a question to investigate, not a failed component to order.

7
JA
JaneAbbott0075

Thanks, Theo; the shift handoff meant the log and physical view arrived together this time. Controls is still preparing the comparison. I've left the older clip unclassified rather than giving it the new wait label.

17
GA
GabrielAbbott0018

Has the seller's ticket description been updated too? The first diagnosis can linger in its title.

6

参与讨论

欢迎来到 Application Robot

所有人都可以阅读论坛。登录或注册后即可发起讨论、回复或上传照片。

忘记密码?

注册账号即表示你同意我们的 使用条款 社区准则。请阅读我们的 隐私政策 ,了解我们如何处理你的信息。