Compare the actual waiting condition and its source history with the display's update time; a last-known tray value should not be treated as a current confirmation
Cannot tell support whether our UR5e sleeve tray was actually ready
AishaAli0257 · 10 Dec 2025, 13:18 UTC
19 replies
I'd ask the programmer what the screen does when updates stop. If it leaves the old green symbol unchanged, that is a display problem worth fixing even before support explains this particular wait.
-2 pointsIt keeps the symbol and doesn't show an age. The recorded controller message is waiting for tray-ready. We still need the matching PLC history to see what that condition was doing during the filmed wait.
15 pointsDoes the tray-ready definition refer to the fitted sleeve tray, Aisha, or is support reading a generic signal description that might omit part of the actual condition?
14 pointsGive the operator an honest stale indication in the proposed screen change, not a blank symbol that leaves them wondering whether the tray disappeared. I'd have a relief operator review the wording too.
2 pointsVictor, would you keep the old value visible with its time, or only say the current value is unavailable? I lean toward both, but a tiny busy screen can become harder to read if every old fact stays equally prominent.
11 pointsCurrent availability first, old observation secondary and clearly dated if it helps the task. I wouldn't preserve an unexplained green icon merely to avoid changing the layout.
14 pointsNaomi, controls has confirmed the fitted tray's mapping and supplied the history. The required input was absent during the identified wait. That establishes the wait condition, not yet why the input was absent.
17 pointsSend support that mapping and matched occurrence together, with the old display behaviour explained; it should stop the green symbol being used to contradict the actual input history
-4 pointsAnd include the tray and sensing arrangement in the technical review, since an absent input does not by itself tell us whether the physical tray was correctly presented
7 pointsDid the relief-operator review happen, Victor? Or rather, Aisha, has your team tried the wording with someone who wasn't involved in finding the stale symbol? I don't mean Victor's workplace.
19 pointsAisha's team has that answer. My suggestion was about the review, not a claim that anyone has already carried it out.
2 pointsKeep the recorded input and physical observation separate in that review too, so the new screen does not teach that an absent tray-ready condition always means an empty tray
6 pointsLuca, wording review is pending. Support has requested an installer check of the fitted tray-ready arrangement. We haven't ordered a sensor or changed the tray from the input value alone.
2 pointsWill the installer have the intended mounting detail and tray identity, rather than just the signal name? That would make the requested check more concrete.
23 pointsYes, both supplied. Separately, the relief operator understood 'current value unavailable' but initially read the smaller green history icon as current anyway. Programmer is changing that presentation before another review.
8 pointsThank you for trying it. That is exactly the sort of thing a developer who knows the timestamps can miss; I would keep the old observation readable without giving it the same visual treatment as a live state.
19 pointsRevised display passed the wording review and the saved stale-update test. The installer check is still outstanding, so the original sleeve wait remains unresolved. At least its screenshot now stops arguing with its history.
16 pointsGive the covering shift that distinction in the handover: display correction done, cause of the sleeve wait still under investigation. Otherwise the improved screen may be mistaken for closure of the whole ticket.
10 pointsDiscussion closed
This discussion is closed to new replies after six months without activity. Last activity: .