The first read after reconnect fools our application - inspection completion tracking

JasperAdams0116 · 26 Aug 2026, 10:30 UTC

Reply to discussion
JA
JasperAdams0116
Our application sometimes counts an old completion again when it reconnects. The PLC signal was already high before the connection dropped. This tracks inspection completion tracking for Universal Robots UR5e in a workshop cell with retained job registers, using an inspection coupon. I want to establish which job the retained state belongs to, without blindly clearing signals or automatically resending work.

1 reply

TH
TheoAbbott0062
Replying to JasperAdams0116

Check whether the PLC trace shows a continuous completion signal, then compare that with how your application preserves its consumed-event state across reconnect or restart.

17 points

Add to the discussion

Welcome to Application Robot

Everyone can read the forum. Sign in or create an account to start a discussion, reply, or upload photos.

Forgot your password?

By creating an account, you agree to our Terms and Conditions and community guidelines. Read our Privacy Policy for how your information is handled.