Extra FR10 logs have turned my availability display into a waiting screen

CallumArcher0360 · 31 Jul 2026, 19:45 UTC

Reply to discussion
CA
CallumArcher0360
My read-only FR10 maintenance display stalls with detailed logging into a busy folder; fixture block at the station, controls separate, and I suspect synchronous writes but have not ruled out slow communication. What is the cheapest useful comparison?

9 replies

GA
GabrielAdams0105
Replying to CallumArcher0360

I've seen an old inspection number survive a failed update, so first decide what stalled means here. Is the screen repainting an old sample, or does the whole interface stop responding? Either way, time read completion and log completion separately.

4 points
PR
PriyaBaker0481
Replying to CallumArcher0360

Use a short controlled comparison with optional detail reduced. Same read settings. Record errors too. A smoother screen by itself won't prove the communication path is healthy.

11 points
GA
GabrielAdams0105
Replying to PriyaBaker0481

Priya, I'd keep enough timing detail to see where the wait moved. Turning off all evidence is tempting, but then we're back to judging a read-only tool by whether it feels cheerful.

6 points
CA
CallumArcher0360
Replying to GabrielAdams0105

The interface stops responding; I have no separate read and write timings yet, so the folder connection is an observation, not a diagnosis.

-8 points
PR
PriyaBaker0481
Replying to GabrielAdams0105

Agreed, Gabriel. Optional detail reduced, not every diagnostic removed. Brief timing counters can be collected without feeding the same file on every event.

8 points
CA
CallumArcher0360
Replying to PriyaBaker0481

I have asked the maintainer for those two timings and a reduced-detail comparison; no change to cell controls or sampling interval.

22 points
GA
GabrielAdams0105
Replying to CallumArcher0360

Ask them to show the sample age during the stall investigation as well. A frozen display should not leave someone thinking the last available reading was just obtained. That remains useful even if the folder turns out innocent.

6 points
PR
PriyaBaker0481
Replying to CallumArcher0360

And tell the maintainer what you need preserved. A quick logging workaround can quietly remove the failure record you wanted in the first place.

6 points
CA
CallumArcher0360
Replying to PriyaBaker0481

The request now specifies failed reads and sample age alongside timing; I still need the comparison before blaming file writing.

8 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.