Which part of our FR10 logging path is delaying the trend screen?

AmyChen1163 · 17 Jun 2026, 10:11 UTC

Reply to discussion
AM
AmyChen1163
I enabled more detailed logs and our read-only trend display now pauses while the folder is busy. The cell controls are separate. What should we measure before deciding the file writes are to blame?

6 replies

FE
FelixAli0197
Replying to AmyChen1163

We once chased a supposed connection problem from a screen that was simply behind. I'd ask the developer for separate receive, write and display timings. Folder activity and a stationary screen are observations, not a completed diagnosis.

18 points
AM
AmyChen1163
Replying to FelixAli0197

Our developer says writing and display refresh share a callback. That explains a possible path, but we haven't measured how long each step takes.

7 points
AN
AnilAli0201
Replying to AmyChen1163

Are replies still arriving during the pause, with their receive times retained?

19 points
FE
FelixAli0197
Replying to AnilAli0201

Anil's question is worth answering before changing the design. I'd also establish what the trend must preserve, so a proposed faster display doesn't quietly throw away the samples the diagnostic record needs.

8 points
AM
AmyChen1163
Replying to AnilAli0201

Receive timestamps are available, but we haven't aligned them with one display pause yet. We do need gaps made visible if recording loses samples.

22 points
FE
FelixAli0197
Replying to AmyChen1163

Have the maintainer own that comparison and the recording requirement together. A screen that looks lively while its useful history disappears would be a poor trade, even if it stops this particular complaint.

10 points

Add to the discussion

Welcome to Application Robot

Everyone can read the forum. Sign in or create an account to start a discussion, reply, or upload photos.

Forgot your password?

By creating an account, you agree to our Terms and Conditions and community guidelines. Read our Privacy Policy for how your information is handled.