Which UR5e indication belongs with our housing-loading stop?

AmaraArcher0426 · 2025年12月29日 02:50 UTC

已关闭

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

AM
AmaraArcher0426
Support says tray not ready. Our later screenshot is green. Which evidence actually describes the captured stop?

20 条回复

IS
IsaacBell0694

What is the exact label beside the green indication, and when was that screenshot taken relative to the stop? A later ready state may describe a perfectly different condition.

12分
AM
AmaraArcher0426

Tray present. Taken after the operator replaced the tray, not during the stop.

17分
CA
CallumBell0621

Then label it as the later state. It should not be sent as proof that the tray was present during the stop.

18分
RE
ReeceAli0210

And ask what support means by ready. Present can be one input to a larger condition. You could have a readable green lamp and still be answering a question they did not ask, which is a wonderfully efficient way to spend another week exchanging screenshots.

9分
LI
LiamArcher0403

What does the actual waiting message say?

14分
AM
AmaraArcher0426

Await receiving tray ready. The clip does not show the individual input page.

14分
IS
IsaacBell0694

Ask support to name the source conditions behind that message for the fitted tray arrangement, then ask your technician whether the retained history covers them at that occurrence. The current page cannot supply their old values.

18分
CA
CallumBell0621

Does support have the actual tray and insert identity? My last ticket had two names for the same fitted part, which made the signal discussion harder than it needed to be.

4分
AM
AmaraArcher0426

They have the carrier name. The removable insert is missing from our ticket. I'll add its identity.

0分
RE
ReeceAli0210

Callum's point is useful. Amara, include the physical label and their drawing name together if those differ. Don't make the remote person recognise the insert from a wide shot of the arm.

8分
LI
LiamArcher0403

Can maintenance still retrieve the stop's earlier history?

12分
AM
AmaraArcher0426

Maintenance preserved the full available range. We don't yet know whether it records the needed source conditions.

13分
IS
IsaacBell0694

That is the question for support and controls now. Send the preserved occurrence with the exact fixture mapping; a longer file is useful only if someone can identify what in it answers the wait.

12分
CA
CallumBell0621

Keep the operator's expected next step too. That may expose a missing handover explanation even if the retained signals are insufficient to diagnose the occurrence.

12分
RE
ReeceAli0210

Callum, yes, but distinguish what the operator expected from what the system actually requested. I've seen an expectation copied into a sequence report and quietly become an observed event.

10分
AM
AmaraArcher0426

Operator expected unloading to continue after tray exchange. That is their account, not an event in the trace.

20分
LI
LiamArcher0403

Was that expectation in the handover sheet?

3分
AM
AmaraArcher0426

The sheet says continue after exchange. It does not explain the readiness decision or who confirms it.

18分
RE
ReeceAli0210

Then there are two useful questions: explain the captured wait if the evidence allows it, and explain the exchange to the next operator. Don't let an incomplete trace become a reason to leave the second one unanswered.

18分
AM
AmaraArcher0426

Both questions sent to the applications contact, with the insert identity. Thanks Reece. No stop cause established yet.

18分

讨论已关闭

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