简体中文界面。帖子、指南及政策正文保留原文；未对原文作自动翻译。
OwenBrooks0834 · 2025年3月16日 17:49 UTC
Three afternoons aren't a diagnosis. What message or active step did each pause show?
24分Only one has a screen photo: waiting for downstream ready. The other two notes just say stopped. I have asked support to keep those separate for now.
0分Good. Start with the one you can actually identify.
16分That occurrence has a matching event export too. Sent it with program version and the screen photo. Support asks whether the downstream tray station was running.
5分Was it?
11分Check the downstream station's own record at the same time, allowing for any clock difference. It may have been running generally but unable to accept the next part. The distinction would help support identify what downstream ready actually means here.
16分Tray station was waiting for an empty rack on that occasion. Operator had left to fetch one. That's in its shift note, so the robot pause may have been expected.
4分May have been. Ask support to confirm the wait condition before closing that occurrence.
11分Our tray station log clock was seven minutes off the robot's, so match the sequence as well as the displayed time if you can
14分Worth checking. Otherwise you'll attach the wrong rack shortage to the right robot pause.
13分I'm interested in what the other two turn out to be, because our supposed afternoon fault was two unrelated waits that happened to share a lunch break.
18分Any new occurrence with a readable message?
9分One this week. Different step: waiting for fixture release. Support confirmed the earlier downstream pause was expected. We now have a separate ticket entry for the fixture wait, with its own timestamp and photo.
9分So after lunch has retired. Did they identify which fixture signal was absent?
13分Have maintenance capture the fixture's physical state alongside the available input display when it happens. Support can then compare what the fixture did with what the program saw, without treating either observation as the whole explanation.
22分They identified the release confirmation. Maintenance is investigating; we have not established whether the missing confirmation reflects delayed movement or a sensing problem. No settings changed on a guess.
15分I renamed our shift log entry to the actual wait step. Afternoon fault was sending everyone in circles. One pause explained, one still under investigation, two old notes still too vague to classify.
7分That's useful progress, even without a single grand cause for all four notes.
8分此讨论已连续六个月没有活动，现已关闭新回复。 最后活动： .