OwenBrooks0834 · 16 Mar 2025, 17:49 UTC
Three afternoons aren't a diagnosis. What message or active step did each pause show?
24 pointsOnly 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 pointsGood. Start with the one you can actually identify.
16 pointsThat 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 pointsWas it?
11 pointsCheck 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 pointsTray 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 pointsMay have been. Ask support to confirm the wait condition before closing that occurrence.
11 pointsOur 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 pointsWorth checking. Otherwise you'll attach the wrong rack shortage to the right robot pause.
13 pointsI'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 pointsAny new occurrence with a readable message?
9 pointsOne 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 pointsSo after lunch has retired. Did they identify which fixture signal was absent?
13 pointsHave 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 pointsThey 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 pointsI 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 pointsThat's useful progress, even without a single grand cause for all four notes.
8 pointsThis discussion is closed to new replies after six months without activity. Last activity: .