Ask the package author which condition the waiting step expects, against the installed job and fixture revision. Then maintenance can collect the preceding events around that input.
Which fixture state belongs with our UR5e loading-stop report?
LuisChan1130 · 17 Apr 2026, 04:21 UTC
19 replies
They name fixture available. Our old export includes available but no source address.
21 pointsDoes the author mean the same available as that export?
8 pointsCheck the mapping before another recording. A friendly column name can outlive the fixture it described. I would have maintenance trace it against the installed job, not assume the matching word is enough.
23 pointsDifferent input. Export setup came from the previous fixture. Maintainer has identified the installed mapping.
6 pointsReplace that export setup on the covering shift's laptop too.
11 pointsAnd keep the old occurrence labelled incomplete, Luis. The corrected mapping helps the next capture; it cannot tell you what the missing input was doing earlier.
16 pointsCan maintenance show the author a sample of the corrected export first?
6 pointsAda, yes. Better to find another omission from an ordinary sample than after waiting for the next stop.
-3 pointsSample sent and accepted by the author. Both shifts now have the same capture setup.
14 pointsDoes it include the interval before the wait?
4 pointsYes, including the loading request and selected fixture identity. Thanks for checking the shift copies.
7 pointsHas a new stop happened since?
24 pointsLuis, include what the physical fixture did in that lead-in if another stop occurs. A missing indication could reflect an actual unavailable fixture, not necessarily a sensor fault.
9 pointsYasmin's point matters. I've seen a perfectly accurate input accused because the screen caption was more reassuring than the mechanism.
19 pointsNew stop captured. Indication absent while the fixture appears clear. Mechanism inspection is next.
21 pointsCan the clip show the actual release position clearly?
13 pointsNot clearly enough. Maintainer is inspecting it with the fixture designer; I won't call it released from this angle.
6 pointsThat's a useful limit. Send their finding with this captured occurrence when it's available, so support doesn't have to guess the physical state either.
23 pointsAdd to the discussion
Welcome to Application Robot
Everyone can read the forum. Sign in or create an account to start a discussion, reply, or upload photos.
By creating an account, you agree to our Terms and Conditions and community guidelines. Read our Privacy Policy for how your information is handled.