I'm reconstructing a failed sample verification attempt on Fairino FR10 in a workshop cell with separate controller logs, using a reference plate.
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.
Can your application log identify where the process restarted? That would distinguish the reused labels within one source, even with mismatched clocks elsewhere.
Keep source order, label the sessions and leave that acknowledgement unassigned. Comparing the timestamps alongside them should establish the combined order.
You're right to challenge that. The timestamps can suggest matches, not prove them. Keep source order intact and label cross-system links uncertain unless there's supporting evidence.
I had a clock adjustment make a merged incident view look plausible on my setup. The original per-source order was what let us correct the interpretation.
Use monotonic time for durations within a running process. It doesn't supply a shared clock across machines or restarts; keep session identity and wall-clock reference alongside it.