I'm reconstructing a failed sample verification attempt on Universal Robots UR5e in a small production cell with an inspection fixture, using a sample housing.
Our Python log, PLC trace and controller event list have disagreeing timestamps.
The application also reused its job label after a restart.
I can see a timeout, but I can't tell which attempt an acknowledgement belongs to.
Which acknowledgement belongs to my retry? (Universal Robots UR5e, sample verification)
JoBrooks0853 · 7 Aug 2026, 02:09 UTC
3 replies
Replying to JoBrooks0853
@JoBrooks0853 Got a process-start entry? That could separate the reused labels without trusting another machine's clock.
15pointsReplying to NoraChen1192
@NoraChen1192 Found it. I can split our Python log into two sessions. Still no attempt match for that PLC acknowledgement, though.
15pointsReplying to JoBrooks0853
Keep source order, label the sessions and leave that acknowledgement unassigned. Comparing the timestamps alongside them should establish the combined order.
15pointsAdd to the discussion
Welcome to Application Robot
By creating an account, you agree to our Terms and Conditions and community guidelines. Read our Privacy Policy for how your information is handled.