Our UR5e housing stop clip leaves the operator message out

RosaCarter0988 · 2026年4月3日 13:27 UTC

已关闭

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

RO
RosaCarter0988
Our UR5e housing-unloading ticket is 31 days old. I supplied the tray and job identities with the video, but the screen is out of frame. The operator calls every pause a stop, including tray exchanges. I need to distinguish the reported occurrences before asking support to diagnose them as one fault.

10 条回复

DA
DanielCarter1000

Have the job author identify the message at each reported occurrence, with the tray exchange context kept alongside it. I would not assume the same fault merely because the housing is stationary in every clip.

12分
RO
RosaCarter0988

Our integrator matched the retained intervals. All three clips show the ordinary wait for confirmation after a receiving-tray exchange, not an alarm. The current operator view only says waiting, so that distinction wasn't visible to cover.

16分
IS
IsaacBell0694

Then the ticket needs that finding stated against those three occurrences. It does not justify dismissing another stop which nobody has matched. Is the intended tray-exchange response actually in the handover?

8分
RO
RosaCarter0988

No. The demonstrator supplied that part during training. Our sheet describes changing the tray but omits the agreed confirmation step. I mean the ordinary job confirmation, not a safety reset.

5分
DA
DanielCarter1000

Ask the integrator and shift lead to put the visible condition and intended response together for cover. Don't just rename waiting to something the program author understands and assume the instruction is finished.

7分
IS
IsaacBell0694

Also retain the reported occurrences as training findings rather than deleting them from the service history. Somebody may ask later why a month-long fault ticket closed without a replaced part.

11分
RO
RosaCarter0988

Revised screen names receiving-tray confirmation. Integrator and shift lead checked the instruction against the installed job. The covering operator's exercise is arranged, with no demonstrator quietly completing that step.

16分
DA
DanielCarter1000

Did cover recognise why the wait remained after changing the tray, without being told where to look?

23分
RO
RosaCarter0988

Yes. Cover completed the normal exchange and its agreed confirmation, and recognised the wait in the interrupted example. We closed the three matched reports with support as an incomplete handover and unclear message. Different future occurrences will still get their own evidence.

13分
IS
IsaacBell0694

That is a useful closure: named occurrences, an actual explanation and a checked handover change. No need to invent a hardware repair to make the ticket sound more substantial.

15分

讨论已关闭

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