Detailed logging made our FR5 trend screen freeze more often. The read-only application is separate from cell control; I want to measure the delay before buying a faster laptop to watch it freeze.
Our FR5 trend display waits for its own diagnostic log
SamAdams0159 · 2026年3月24日 23:51 UTC
主帖中文翻译暂不可用，以下显示英文原文；回复保留原文。 查看英文原文
7 条回复
回复 SamAdams0159
Split the timing around the read, processing, save and display update. Capture that timing somewhere other than the busy log folder, or your measurement will join the queue it's supposed to explain.
19分回复 AmyAdams0119
Saved-response replay reproduces the freeze. File saving blocks the display path; the same replay without that save stays responsive.
21分回复 SamAdams0159
Does the read itself ever stall in the connected capture?
8分Yes, separately. One captured read takes longer even when saving is quick. I have kept the two examples apart.
9分回复 SamAdams0159
Good, two observed delays rather than one grand diagnosis. Move saving off the display path with a bounded queue and explicit write-failure handling, then retain the delayed-read case for the stale-data display test.
12分回复 AmyAdams0119
The test build handles slow and failed storage without freezing the screen. Full-queue warning works too. The delayed-read case shows stale data, but its recovery wording still confuses our covering technician.
9分回复 SamAdams0159
What does the recovery message actually say?
11分讨论已关闭
此讨论已连续六个月没有活动，现已关闭新回复。 最后活动： .