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

UR5e status container reaches our display even when the request failed

ElenaAdams0166 · 2026年8月16日 03:29 UTC

回复讨论
EL
ElenaAdams0166
Our old status wrapper expects a value; replacement SDK returns a container. Failed UR5e reads now get normal labels. Where should validation happen?

4 条回复

TO
TobyAllen0318

At the adapter boundary, using the applicable response contract to distinguish request success from validated status data; test malformed replies and good-read-then-failure before the screen updates.

10
EL
ElenaAdams0166

Contract located for this environment. Maintainer has the failed container example and a good-then-failure test. No code correction completed yet.

24
LI
LiamBrooks0838

Also include a genuine valid status that is not favourable. The adapter should not turn every negative-looking reading into a communication failure. Preserve the distinction between unavailable data and an observed condition.

6
EL
ElenaAdams0166

Offline cases now pass after the repair, including valid negative status and stale previous data. Supported-environment comparison remains outstanding. The training display is not released yet.

11

参与讨论

欢迎来到 Application Robot

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

忘记密码?

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