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.
How do I measure where status processing gets stuck? (Fairino FR10)
LouisBaker0485 · 2026年8月10日 02:57 UTC
主帖中文翻译暂不可用，以下显示英文原文；回复保留原文。 查看英文原文
6 条回复
Try a controller-free replay of saved responses with a delayed log destination, measuring receipt separately from processing. Does the display still stall?
20分回复 LucyBell0654
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.
9分Try a separate writer with a bounded queue in that replay. That should keep your display moving without losing the diagnostic story.
25分回复 LucyBell0654
@LucyBell0654 A bounded queue fills. You can't promise the whole diagnostic story survives. What happens when storage stays blocked?
1分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.
24分回复 LucyBell0654
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.
0分