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

Can't tell support which UR5e wait our video shows

DanielChan1087 · 2025年8月14日 04:30 UTC

已关闭
DA
DanielChan1087
Our seller wants more evidence for a UR5e housing-unloading stop, and I was ready to send the same video again. Then I noticed our notes call one event waiting for tray and another program stopped, with no times to join them up. How should I rebuild this report without guessing which event belongs to the clip?

8 条回复

RA
RaviBarnes0563

Leave the old clip identified as unmatched and collect the exact displayed message, occurrence time and active step together for a new event, with the unit and application versions supplied separately.

11
DA
DanielChan1087

I've done the unit and version details. Operator remembers the clip was after a tray exchange, but can't say which message was showing. I won't put a confident caption on it.

8
RA
RaviBarnes0563

Ask for the tray identifier in that next capture as well, since an exchange may be relevant without establishing that the tray caused the stop.

10
DA
DanielChan1087

New event captured on tray H2. The message says it is waiting for tray confirmation, at the unload-start step. Sent that with the time and a photo showing the actual tray setup.

5
RA
RaviBarnes0563

That gives support a particular condition to investigate, although the old program-stopped note should remain separate until you can identify what it described.

7
EL
ElliotBell0683

Did the confirmation disappear at the exchange, Daniel, or was H2 already working before that wait showed up?

13
DA
DanielChan1087

First request after H2 was put in, Elliot. We haven't captured the confirmation changing, only its missing state during the wait. Controls is checking the detection and mapping before anyone calls the tray faulty.

1
RA
RaviBarnes0563

Has controls been able to distinguish a missing physical detection from the signal not reaching the application, using that same H2 setup?

23

讨论已关闭

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