Our UR5e acknowledgement sits between two reused coupon-job labels

NathanBennett0721 · 30 Jun 2026, 05:38 UTC

Reply to discussion
NA
NathanBennett0721
I cannot assign this acknowledgement to an inspection attempt. Python restarted and reused the label, while its timestamps disagree with the PLC and controller. We have a timeout in the record, but not a defensible combined sequence. What can I reconstruct without pretending the closest timestamp proves ownership?

1 reply

HA
HassanBennett0704
Replying to NathanBennett0721

Keep each source's original order and clock information, then look for shared event or attempt identifiers and independently established anchors. If those cannot distinguish the two attempts, retain both possible histories and the unassigned acknowledgement. The physical coupon's review owner needs that uncertainty, not a convenient guessed timeline.

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