简体中文界面。帖子、指南及政策正文保留原文；未对原文作自动翻译。
RosaBrown0901 · 2026年2月9日 18:01 UTC
Ask their technical contact to name the condition behind that wait message. Our screen once carried the wrong recipe label, which made a real receiver wait sound like a different problem. The words alone sent us in circles.
25分Does the job think the destination is empty, Rosa, or only the person looking at it?
6分I'd also ask who clears a completed destination in the normal changeover. We had somebody removing finished parts while the application was still waiting for the agreed exchange confirmation. Empty tray, busy computer.
14分Harish, possible, but don't turn the loader into the suspect before Rosa knows which condition is missing. A half-written changeover sequence can leave them doing exactly what the instruction says.
1分Get the preceding states retained with the stop. Our newer capture finally includes that interval; the original short export missed it entirely.
23分Can the operator read the destination identity from their normal position? A screen label that only the programmer recognises will not help much.
17分Lin: job says occupied, although that pocket is physically empty. Harish: the instruction includes exchange confirmation, and the loader followed it. Support has now named the retained destination-status field they want with the job identity.
0分Then compare which destination that exchange confirmation cleared. It might be correctly recorded against a different tray job. I would not ask the operator to repeat it blindly while the ownership is unclear.
19分Rebecca, agreed. Rosa's answer makes the distinction important. I was describing our case, not accusing her loader of skipping something.
-7分Nina, destination names were abbreviated and too similar. The retained trace also shows exchange clearing the previous tray job, while the active job keeps its occupied state. Programmer is checking that mismatch.
10分That sounds painfully familiar in the wording, although the job-state mismatch is your own finding. Keep both in the correction: clearer names won't fix which job receives the confirmation.
12分Will the revised screen let the loader see the active job before confirming the exchange, Rosa? I'd want that answer from someone using it, not just someone who wrote it.
20分Revision ties exchange confirmation to the active destination identity and rejects the old job's confirmation. Offline tests cover both cases. The clearer names passed a walkthrough with our loader, who spotted the mismatched example unaided.
7分Has that correction reached the installed station, or is it still the tested revision waiting to go in?
18分Installed and checked with the integrator. Two normal tray exchanges completed, and the mismatched-job test held for review instead of clearing another destination. This ticket is closed. Thanks for asking about the condition behind the message, Farah.
9分此讨论已连续六个月没有活动，现已关闭新回复。 最后活动： .