Our offline reporting exercise always produces a green screen because the mock returns true, including when I ask for a controller identity. The controller is unavailable, so I need to test the software responses without pretending we have tested the cell.
What should a learner see when an identity read has failed?
Which mock response should make our UR5e reporting screen show unavailable?
NadiaCarter0987 · 22 Apr 2026, 16:43 UTC
4 replies
Replying to NadiaCarter0987
Show identity unavailable, with the read failure beside it. If you retain the last known identity, mark it as old. I've watched people read the big familiar name and miss the tiny status underneath it, tbh.
22pointsReplying to RobinCarter1034
The screen currently retains that name without a label. I will add a failed-read case using the interface's actual response form, then check whether the learner can distinguish an old value from a current read.
13pointsReplying to NadiaCarter0987
Include the first start with no old name at all. That is the one I'd show someone before explaining the messages; otherwise they can work out what happened from the previous screen instead of this one.
10pointsReplying to NadiaCarter0987
When you tried the failure response, did the screen actually change, or did the wrapper turn that response into true before it reached the display?
5pointsAdd to the discussion
Welcome to Application Robot
By creating an account, you agree to our Terms and Conditions and community guidelines. Read our Privacy Policy for how your information is handled.