FR5 mode display borrowing a value from a failed reply

The captures already include the SDK version. The live wrapper does not use it to choose a parser; it guesses from the shape. A failed reply can satisfy that guess.

Then keep unsupported combinations visibly unsupported. Guessing is exactly what gave the failed response a respectable-looking mode in the first place

Could it show the last good value, clearly marked old?

We want that for diagnosis, Robin. But it must not occupy the current-mode field. The present design puts the last valid value and its time underneath an unavailable message.

I like the separate place. Does the unavailable wording say the read failed, rather than implying the controller itself has definitely stopped responding?

The display can distinguish a reported request failure, a timeout and a reply it cannot interpret, where the available evidence supports those distinctions. It should not manufacture a machine state from any of them.

Lin, yes, but don't put the whole parser diagnosis in the main status label. People need the immediate meaning first, with the reason available underneath

Would read unavailable be enough there, with the reason below?

That wording is a reasonable candidate for a walkthrough. The diagnostic detail can remain separate; I was describing the information to retain, not prescribing a long label.

The two explicit parsers now pass our saved success and reported-failure examples. The live configuration names its supported SDK version. We still need malformed containers and timeout cases before I would call the wrapper ready.

Include an old value that looks perfectly ordinary in the walkthrough. A ridiculous value won't tell you whether someone mistakes a stale reading for the current one.

Sofia, that is now in the example. We retained an ordinary last-good mode from before the failed read. The tutor has not tried the revised screen yet.

Can the tutor tell a saved capture from the live view too? You mentioned keeping both readable, and that is another place a valid old mode can look current

The saved view is labelled with its capture time and connection identity. I have added switching between that and the live view to the walkthrough. The current failure is not being hidden by a successful old capture.

Let us know which wording the tutor actually understood first.