I need to stop our read-only FR10 viewer freezing because operators are treating the frozen values as current. It began after I enabled detailed logs. Closing a log file seems to coincide with the pause, but I have not timed the controller reads separately. Cell controls use another system.
Try timing the file close before replacing any kit, our laptop comparison taught me that apparently identical software can hide some very different things happening underneath
The close takes much longer than expected on the workshop laptop. Same small read request stays quick when tested separately. I'll check what our close handler actually does.
Could you test with deliberately slow archive work? That might show whether the display really stays responsive after the change, rather than only during an easy run.
Display now shows the age of its last reading. Compression runs separately with a limit on pending work, and failed archive tasks are visible. Our software maintainer has the queue and storage notes.
We ran the slow-archive test. Readings kept updating and the archive warning appeared when work backed up. I still need the normal shift trial before handing this version over.