My UR5e monitoring laptop holds the last status on screen while a new log file opens, or at least that is the timing I keep seeing; the separate cell controls continue normally, and I want to distinguish a blocked display from a delayed response.
Time the stages separately. Request sent, response received, log write started and finished, display updated. A single timestamp beside the displayed value hides most of that journey.
The current timestamp is added after writing the file, so it cannot tell me when the response arrived; I will move the timing points before comparing causes.
What tells somebody the screen is stale while all this happens? I've seen an unchanged green box described as reassuring, right up until we discovered it hadn't heard anything for a while.
Beth, avoid sending those timing measurements through the same file writer you are measuring. Buffering a small diagnostic trace separately may be enough for the comparison, with any missing trace entries made visible.