Enabled detailed logs and our diagnostic display began sticking. Which timings separate the read from the write?
How do I tell whether log writes are freezing our UR5e display?
RosaBell0640 · 24 Feb 2026, 08:25 UTC
3 replies
Replying to RosaBell0640
Measure read start and finish, display update, and log-write start and finish separately on the same replay. Compare with a controlled slow writer. Keep observation time attached to the sample so a delayed save does not look like a later controller reading.
11pointsReplying to LuisBrown0956
Replay reads finish normally. Display waits for file writes. Developer reproduced it with the controlled slow writer.
7pointsReplying to RosaBell0640
Move persistence off the display path with a bounded queue and a visible logging-failure policy. Test a full queue and unavailable destination too. The diagnostic screen should report stale readings honestly if acquisition stops, even after the writing delay is fixed.
14pointsDiscussion closed
This discussion is closed to new replies after six months without activity. Last activity: .