What does support want besides another stopped UR5e video?
NoraAli0235 · 15 Jul 2025, 14:49 UTC
10 replies
Capture the full station message and program step, with one occurrence time and matching logs. Include what the operator saw immediately before the pause, not only the stationary pose.
7pointsMessage says waiting for nest ready. Log capture requested from maintenance. No sensor diagnosis yet.
21pointsWhich nest was fitted during that occurrence? If the package has interchangeable tooling, support needs the actual identity, not a generic picture of whatever happens to be installed when the email is written.
23pointsNest B, identified in the video. Maintenance has its revision with the matching trace.
19pointsAsk maintenance to compare the physical ready condition with the ordinary input during the same event. The label could be hiding a mapping issue as well as a real fixture condition.
15pointsAnd send that set to the seller with a specific question about the waiting step. Otherwise the next reply may simply ask for a longer video of the same nothing happening.
14pointsSent one linked occurrence. Asked which input the step expects and who checks the supplied mapping.
20pointsDid the seller answer those questions, Nora? I'd follow that response before gathering more footage without knowing what is missing from this set.
11pointsThey named the expected input. Integrator is comparing it with the installed mapping. Still unresolved.
21pointsWhen they report back, keep the nest identity in the explanation. Stores and maintenance may need to recognise the same setup later, especially if the mapping differs across interchangeable nests.
13pointsDiscussion closed
This discussion is closed to new replies after six months without activity. Last activity: .