Our UR5e spacer-unloading job sometimes waits after the tray looks empty. I have the current job and tray identities; I am not assuming they match just because the labels look familiar. The seller through Alibaba has asked for more detail on the 24-day-old report. The phone clip starts at the wait, and nobody recorded which pocket was taken last. I want a capture that settles the ending of the tray sequence rather than another guess about the gripper.
Empty tray, UR5e job still waiting for another spacer
LeoAllen0275 · 2026年3月14日 00:41 UTC
主帖中文翻译暂不可用，以下显示英文原文；回复保留原文。 查看英文原文
16 条回复
回复 LeoAllen0275
Ask the author for the selected tray definition, expected pocket count and current step from the same occurrence. The ending may matter here, but the empty-looking tray alone does not explain what the job expects.
14分回复 LeoAllen0275
Is this every tray, Leo, or only the short orders? That difference would be useful even before the next trace arrives.
22分回复 ZaraBell0656
The operator may know how the tray was prepared without remembering its last pocket. Ask for the starting arrangement, including deliberately empty positions.
17分Only the short orders we can identify. They begin with part-filled trays. The operator follows a written fill order, but the job selection page only names the tray family, not the order ending.
14分回复 LeoAllen0275
Get the applicable definition from the author. Don't teach the operator to skip a wait until the application has an agreed meaning for those empty positions.
24分回复 LeoAllen0275
Has the customer-supplied fill order ever been included in the package handover? It could be correct packing practice and still be absent from the program assumptions.
14分回复 LeoAllen0275
What did the original demonstration use, Leo, a full tray or the same partial starting condition?
23分Callum's handover question needs an owner. This will keep returning if the trainer has one fill order and the job author has another.
19分回复 John_Briggs
John, full tray in the demonstration. Callum, our partial fill order was sent during planning but never added to the issued job notes. New capture shows the program waiting on the next position in its full-tray definition after the actual short order is exhausted.
8分回复 LeoAllen0275
So the short-order work was not represented in that definition. Has the author accepted that scope, or are they proposing full trays only?
14分回复 ZaraBell0656
Full trays only could be a valid restricted job, but the operator would need the restriction before loading. It cannot live solely in the support ticket.
1分Victor, agreed. Leo, ask for an explicit decision on the short orders and their finish, including interruption. Do not let a changed pocket total stand in for that whole decision.
23分The author and our lead agreed identified short-order definitions using the permitted fill order. The offline checks cover normal finish, an unexpected empty pocket and interruption. The screen now shows which order definition is selected.
10分回复 LeoAllen0275
Have those changes reached the station, or only the support demonstration?
17分Station checks completed with the integrator and shift lead. Full and agreed short orders finish correctly; unexpected gaps take the agreed recovery route. Trainer updated the fill-order notes. Thanks, Zara, asking which orders failed got us moving.
8分回复 LeoAllen0275
That explains the reported short-order wait. I would leave any older untraceable stop unassigned rather than let this answer absorb it.
6分讨论已关闭
此讨论已连续六个月没有活动，现已关闭新回复。 最后活动： .