简体中文界面。帖子、指南及政策正文保留原文;未对原文作自动翻译。

our fr5 dashboard finds an idle status inside a failed read

BenAli0196 · 2026年3月7日 05:39 UTC

回复讨论
BE
BenAli0196
The FR5 screen changes from busy to idle when this diagnostic read fails. New SDK response has several fields; our wrapper still picks a position from the old format. I've retained the failing reply.

15 条回复

RA
RachelArcher0435
回复 BenAli0196

Compare the wrapper's chosen field with the installed SDK's documented result. Check success before extracting a valid status; a diagnostic or error value can look quite plausible after being fed into your application's status labels.

7
BE
BenAli0196

That's what happened. The old position now supplies a diagnostic value, and our local label table turns it into idle. Developer has the version and both successful and failed responses.

0
OM
OmarAbbott0056
回复 BenAli0196

Does the report save that invented idle too?

20
BE
BenAli0196

Yes. Display and report both receive the wrapper's converted value. I've added the report row to the reproduction; it isn't only a misleading screen colour.

3
HA
HanaAdams0100
回复 BenAli0196

What will the operator see instead when there isn't a valid current reading?

13
RA
RachelArcher0435

Use an explicit unavailable result from the adapter and keep any previous reading separate with its observation time. Do not pass a made-up ordinary status downstream and expect each screen or export to recognise the trick.

13
DI
DineshBrown0908

Hana, would you remove the previous reading altogether? I'm not sure whether keeping it helps the operator or leaves another tempting number on the screen.

23
HA
HanaAdams0100

I'd ask the operator what they use it for, Dinesh, but I wouldn't leave it in the current-status position and hope a little timestamp explains the difference

21
BE
BenAli0196

Operator uses the last reading when reporting a stop. We've kept it in a separate previous-reading section, with current reading unavailable above. They could explain both on the revised test screen.

-1
OM
OmarAbbott0056
回复 BenAli0196

Has the parser fix passed, not just the wording?

4
BE
BenAli0196

Retained successful states parse correctly. Failed, incomplete and unexpected response shapes return unavailable. The same cases reach display and report without an ordinary status being invented. Installed workstation check remains.

6
RA
RachelArcher0435
回复 BenAli0196

Include first startup without any previous reading, and a good read followed by failure. Those are different screen histories even though both end without current data.

-1
DI
DineshBrown0908
回复 BenAli0196

Did the workstation comparison settle it, Ben?

18
BE
BenAli0196

Yes. Maintainer checked the identified installed package with both startup cases and the retained response set. Current and previous status stay distinct, and the report records failed reads as unavailable. Operator handover accepted.

12
HA
HanaAdams0100
回复 BenAli0196

Thanks for keeping the previous reading useful without dressing it up as the current one; that is the bit I would want the cover operator shown too

12

参与讨论

欢迎来到 Application Robot

所有人都可以阅读论坛。登录或注册后即可发起讨论、回复或上传照片。

忘记密码?

注册账号即表示你同意我们的 使用条款 社区准则。请阅读我们的 隐私政策 ,了解我们如何处理你的信息。