Our diagnostic application watches Fairino FR10 for controller availability logging in a bench setup replaying controller diagnostics, using a reference coupon 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?
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.
You're right about my preservation claim. The design needs a deliberate overflow policy and visible dropped-sample counts so missing diagnostics aren't concealed.
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.