How should our FR5 inspection request stay visible until it is received?

DineshChen1169 · 18 Nov 2025, 21:16 UTC

Closed
DI
DineshChen1169
Our ordinary PLC request can vanish before the application polls it. The interface note names neither owner nor clearing condition. Safety functions are separate. How should the two authors agree this job handshake?

5 replies

NA
NathanBrooks0808
Replying to DineshChen1169

Who currently clears the request, and does the application return anything tied to the specific request it received? Start with the actual behaviour before choosing new names.

6 points
DI
DineshChen1169
Replying to NathanBrooks0808

PLC clears it on a timer. Application has a general connected flag, not an acknowledgement of that plate request. Neither author documented the gap.

17 points
NA
NathanBrooks0808
Replying to DineshChen1169

Can they agree retained request ownership and a request-specific acknowledgement, with receipt distinct from completion? The connected flag cannot explain whether this job was accepted.

25 points
DI
DineshChen1169
Replying to NathanBrooks0808

That is now the proposed sequence. They still need to agree timeout and restart behaviour. I've asked for the unanswered case in the operator walkthrough as well.

14 points
NA
NathanBrooks0808
Replying to DineshChen1169

What does the proposed screen tell the operator while that answer is missing? They should not have to guess whether another press creates another request.

25 points

Discussion closed

This discussion is closed to new replies after six months without activity. Last activity: .