another stopped-arm video, still no diagnosis

ThomasAbbott0016 · 2025年4月24日 14:04 UTC

已关闭

主帖中文翻译暂不可用,以下显示英文原文;回复保留原文。 查看英文原文

TH
ThomasAbbott0016
Our UR5e spacer unload paused again. I filmed it, then realised the screen was behind me. Seller support through Alibaba wants more detail. Which existing records should I send before chasing another occurrence?

19 条回复

LE
LeahBarnes0582

Start with the exact application step and any saved controller messages for that occurrence, identifying the source of each record.

11分
TH
ThomasAbbott0016

Application log says waiting unload permission. Operator notes no visible controller message. The video just shows the arm holding position, which now seems a fairly obvious limitation.

8分
LE
LeahBarnes0582

What provides unload permission in this package?

14分
TH
ThomasAbbott0016

I do not know. The supplied job diagram has an arrow with that name, no signal source. Asked the seller to explain it.

10分
LE
LeahBarnes0582

Include the application version with that question so they can identify the installed logic rather than answer from a different release.

8分
HA
HarishChen1185

We had 'permission' calculated from three conditions. The screen showed only the combined result. Once we could see which condition was missing, the ticket got much shorter.

9分
TH
ThomasAbbott0016

Seller says ours also combines conditions from the machine interface. They sent the list. None of those values is in the log I originally supplied.

5分
LE
LeahBarnes0582

Ask which existing diagnostic view can capture those values together at the wait, including any indication of how recently they were updated.

22分
FI
FionaAllen0325

Who wrote that application? Get the question to them. You can spend a month teaching the sales contact to relay each sentence while the person who knows the logic sits somewhere else.

-3分
TH
ThomasAbbott0016

The seller has named their application engineer now. Direct technical contact arranged through the ticket. I should have pushed for that earlier.

9分
PR
PriyaBennett0742

Are the machine and application records on the same clock? I would state any uncertainty before combining them into one timeline.

2分
LE
LeahBarnes0582

Do you know that, Thomas?

25分
TH
ThomasAbbott0016

No. I am sending the separate originals and pointing that out. There are local sequence numbers, but I do not know whether they refer to the same operation.

12分
LE
LeahBarnes0582

Then retain those numbers as recorded and ask the engineer how they relate; matching similar-looking values by hand could create a misleading sequence.

20分
HA
HarishChen1185

Did they give you a capture method for the combined conditions yet? That sounds like the bit still missing from the next useful report.

4分
TH
ThomasAbbott0016

Yes. Maintenance used it on the next occurrence and sent the result. One permission input was stale in the application view. Engineer is comparing that with the machine-side record.

10分
FI
FionaAllen0325

Make sure the shift covering tonight has the ticket link and knows who is investigating. Otherwise somebody will see 'waiting permission' and start this whole support conversation again from their phone.

17分
TH
ThomasAbbott0016

Handover updated. The engineer has enough to investigate now, but we have no repair yet. I will post the result when we have one.

1分
LE
LeahBarnes0582

Please include how the proposed repair is checked against the original occurrence; that will help readers understand whether it addresses the same wait.

22分

讨论已关闭

此讨论已连续六个月没有活动,现已关闭新回复。 最后活动: .