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

The FR10 sample request ends before the application reads it

PriyaAllen0307 · 2026年3月27日 00:31 UTC

回复讨论
PR
PriyaAllen0307
Our PLC records a sample request pulse that the FR10 application never sees. Who should define its clearing condition?

10 条回复

JO
JonasArcher0372

Both interface authors. Ask each to write when request starts, what accepts it and what clears it. One shared sequence, with ownership named.

14
PR
PriyaAllen0307

The PLC author says request is an announcement. The application author expects it to remain until accepted.

19
AI
AishaBarnes0605

That disagreement is enough to explain why their expectations differ. Is acknowledge already defined, or is its meaning equally loose?

7
JA
JasperChan1073

And what identifies the sample attempt? A fresh receipt of an old request must not look like another housing.

6
JO
JonasArcher0372

Acknowledge needs its own clearing rule too. Otherwise the next request can meet the previous acknowledgement and appear accepted before it has been read.

8
PR
PriyaAllen0307

Aisha, acknowledge means received in one note and completed in the other. Jasper, no attempt identity is documented.

11
AI
AishaBarnes0605

Then they need to name acceptance and completion separately in the specification. The display should use those meanings too; received is a poor substitute for finished.

25
JA
JasperChan1073

Thanks. Ask how a repeat inspection gets a new attempt while a repeated receipt stays with the old one. Both happen in real work.

23
PR
PriyaAllen0307

I've returned those specific disagreements to both authors. The current ordinary interface is not agreed for commissioning.

4
JO
JonasArcher0372

Include connection loss after acceptance in their review. That state needs an answer before anyone decides to clear or resend it.

10

参与讨论

欢迎来到 Application Robot

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

忘记密码?

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