Which UR5e indication belongs with our housing-loading stop?
AmaraArcher0426 · 29 Dec 2025, 02:50 UTC
20 replies
What is the exact label beside the green indication, and when was that screenshot taken relative to the stop? A later ready state may describe a perfectly different condition.
12pointsTray present. Taken after the operator replaced the tray, not during the stop.
17pointsThen label it as the later state. It should not be sent as proof that the tray was present during the stop.
18pointsAnd ask what support means by ready. Present can be one input to a larger condition. You could have a readable green lamp and still be answering a question they did not ask, which is a wonderfully efficient way to spend another week exchanging screenshots.
9pointsWhat does the actual waiting message say?
14pointsAwait receiving tray ready. The clip does not show the individual input page.
14pointsAsk support to name the source conditions behind that message for the fitted tray arrangement, then ask your technician whether the retained history covers them at that occurrence. The current page cannot supply their old values.
18pointsDoes support have the actual tray and insert identity? My last ticket had two names for the same fitted part, which made the signal discussion harder than it needed to be.
4pointsThey have the carrier name. The removable insert is missing from our ticket. I'll add its identity.
0pointsCallum's point is useful. Amara, include the physical label and their drawing name together if those differ. Don't make the remote person recognise the insert from a wide shot of the arm.
8pointsCan maintenance still retrieve the stop's earlier history?
12pointsMaintenance preserved the full available range. We don't yet know whether it records the needed source conditions.
13pointsThat is the question for support and controls now. Send the preserved occurrence with the exact fixture mapping; a longer file is useful only if someone can identify what in it answers the wait.
12pointsKeep the operator's expected next step too. That may expose a missing handover explanation even if the retained signals are insufficient to diagnose the occurrence.
12pointsCallum, yes, but distinguish what the operator expected from what the system actually requested. I've seen an expectation copied into a sequence report and quietly become an observed event.
10pointsOperator expected unloading to continue after tray exchange. That is their account, not an event in the trace.
20pointsWas that expectation in the handover sheet?
3pointsThe sheet says continue after exchange. It does not explain the readiness decision or who confirms it.
18pointsThen there are two useful questions: explain the captured wait if the evidence allows it, and explain the exchange to the next operator. Don't let an incomplete trace become a reason to leave the second one unanswered.
18pointsBoth questions sent to the applications contact, with the insert identity. Thanks Reece. No stop cause established yet.
18pointsDiscussion closed
This discussion is closed to new replies after six months without activity. Last activity: .