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

UR5e housing wait with an unreadable destination identity

HazelAllen0310 · 2026年3月21日 10:14 UTC

回复讨论
HA
HazelAllen0310
We have the lead-in and job export for our UR5e housing stop now. The destination is hidden by the tray wall in the video, and the export uses a pocket number without the tray identity. Our eleven-day seller ticket needs that gap explained, not another confident guess about where the housing went.

13 条回复

EM
EmmaBaker0463

Does another retained record identify which destination tray was fitted for that occurrence?

0
HA
HazelAllen0310

The shift sheet names the tray family, not the individual tray or insert. It doesn't settle which of the two arrangements was present.

24
NA
NathanChen1156

Tell support that limit explicitly. Ask the author to include the destination identity in a new capture, linked to the physical arrangement and the job that selected it.

12
NA
NaomiBrown0941

Can the covering operator identify those two arrangements from the normal loading position?

15
HA
HazelAllen0310

Only by a small mark at the rear. The loader usually recognises them from where they are stored, which isn't a reliable handover.

17
LU
LucaChen1135

Then the job needs a visible arrangement identity as well as a better export; otherwise you'll record a selection nobody can confidently match to the tray.

23
NA
NathanChen1156

Luca's point is separate from inferring the old stop. Fix future identification without rewriting the uncertain history.

24
HA
HazelAllen0310

Agreed. We're adding a visible identity to each approved arrangement and having the author expose the selected one. The old occurrence remains uncertain.

0
EM
EmmaBaker0463

Has the maintainer confirmed the next capture includes the events before the wait, rather than only the selected arrangement at the end?

4
HA
HazelAllen0310

Yes. It retains the request, receipt and destination condition leading into that step, with one occurrence reference.

1
NA
NaomiBrown0941

I'd have the covering operator try the identification and export together, so the two improvements actually meet at handover

5
LU
LucaChen1135

And leave the new wait unexplained until it occurs with that capture; an improved recorder is preparation, not a diagnosis.

15
HA
HazelAllen0310

The handover walkthrough is arranged. No new matched stop yet, so support still has the original export with its destination uncertainty clearly stated.

14

参与讨论

欢迎来到 Application Robot

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

忘记密码?

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