our UR5e inspection request clears before the application sees it

NaomiBrown0941 · 7 Mar 2026, 14:46 UTC

Closed
NA
NaomiBrown0941
The PLC pulses an ordinary inspection request and the application sometimes polls too late, while the interface notes never say who owns clearing it; I need the two authors to agree that before the trainer gets another instruction to watch the screen more closely. The engineered safety functions are separate from this job handshake

8 replies

JO
JonasBrooks0807
Replying to NaomiBrown0941

What tells the PLC that this particular request was received?

20points
NA
NaomiBrown0941
Replying to JonasBrooks0807

Nothing at present; its timer clears the request regardless of whether the application saw it, and the application author had assumed the PLC held it until receipt.

14points
JA
JamieBrooks0817
Replying to NaomiBrown0941

Put that disagreement into an example both authors walk through. The request needs an identity and an agreed receipt, with each side owning its own state changes, not a longer hopeful pulse.

21points
BE
BethArcher0411
Replying to NaomiBrown0941

What does the operator see while receipt is missing, Naomi? That wait should not look like an inspection already under way

7points
NA
NaomiBrown0941
Replying to JamieBrooks0817

The authors agreed a retained identified request until matching receipt, with receipt separate from inspection result; the revised screen says waiting for request receipt, and their offline delayed-receiver test no longer loses the request.

19points
JO
JonasBrooks0807
Replying to NaomiBrown0941

Did they test a repeated receipt and restarting either side?

19points
NA
NaomiBrown0941
Replying to JonasBrooks0807

Yes, repeated receipt starts no second inspection and the restart cases retain the outstanding identity for reconciliation; the application owner repeated the agreed checks on the station and the trainer followed the new waiting explanation.

7points
BE
BethArcher0411
Replying to NaomiBrown0941

Useful. Keep both program versions with that interface revision so the next update doesn't quietly put the two authors back in different conversations

15points

Discussion closed

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