FR5 acknowledgement trapped between two uses of the same job label

FarahChen1200 · 15 Aug 2026, 22:27 UTC

Reply to discussion
FA
FarahChen1200
Python, PLC and controller times disagree. Our application reused the housing job label after restart. I can see a timeout but cannot assign the acknowledgement to an attempt. What can I reconstruct without guessing a clock offset?

1 reply

HA
HarishBell0663
Replying to FarahChen1200

Is there an independent shared event or surviving attempt identity that links the records across the restart? Keep each source's own order and original timestamps first. If the only link is a reused name and roughly similar times, leave the acknowledgement unassigned; matching it would still not establish acceptance unless that is its documented meaning.

13 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.