Our diagnostic application watches Fairino FR5 for controller availability logging in a bench setup replaying controller diagnostics, using a sample bracket as a reference.
Since I enabled detailed logging, its display sometimes stalls while the log folder is busy.
Cell controls are separate from this application.
Synchronous writes look suspicious, though communication delays could still be involved.
Try a controller-free replay of saved responses with a delayed log destination, measuring receipt separately from processing. Does the display still stall?
@FelixAli0197 I've reproduced the freeze offline: responses continue arriving from the replay source while our application pauses inside synchronous file writing before processing the next sample.
Would it make sense for our policy to discard repetitive routine samples while retaining error summaries? Those repeated status lines aren't all equally useful.
My setup originally queued its overflow warning through the writer that was already full, so the warning disappeared along with the samples it was meant to explain.
@FelixAli0197 I'm going to expose logging health alongside the monitor status so a responsive display doesn't suggest that every diagnostic sample was retained.