Our logs show a timeout during sample verification with Fairino FR5, but I can't assign an acknowledgement to the right attempt. We're in a commissioning station recording job events, using a machined bracket.
Python, PLC and controller timestamps don't agree, and our application reused the job label after restarting. I'm trying to reconstruct what we actually know.
Three logs, one timeout, no clear sequence (Fairino FR5, sample verification)
AmaraBrooks0861 · 2026年5月13日 09:55 UTC
主帖中文翻译暂不可用，以下显示英文原文；回复保留原文。 查看英文原文
18 条回复
Got a process-start entry? That could separate the reused labels without trusting another machine's clock.
20分@LiamBaker0490 I've found the process-start line, so our Python entries can be divided into two sessions. I still can't link the PLC acknowledgement to a specific attempt.
8分Keep source order, label the sessions and leave that acknowledgement unassigned. Comparing the timestamps alongside them should establish the combined order.
20分Those clocks disagree. Why would putting their timestamps beside the sessions establish an order across systems without an offset or matching exchange?
9分回复 AdaBrown0912
You're right; I went too far. Timestamps suggest matches. Keep source order and mark cross-system links uncertain unless evidence supports them.
6分I'll leave it unassigned. A tidy timeline would be nice, but the nearest timestamp would still be a guess.
3分My merged log fooled us after a machine clock adjustment. Keeping the original source order let us untangle our confidently wrong interpretation.
4分@TheoBrown0932 Can monotonic timestamps fix the clock issue across these systems, or are they only comparable within a process?
-1分Inside a running process. Machines and restarts don't automatically share that clock, so keep a session ID and wall-clock reference too.
16分@LiamBaker0490 I'm thinking of a stable job identifier plus a separate identifier per attempt. Is that the distinction our reused display label is missing?
11分Yes. Job for the work, attempt for each try. Record both with your event source and session.
24分Can your PLC exchange carry that identity? Python IDs won't label another system's records by magic.
17分回复 AdaBrown0912
I can't see a correlation field in our export. I'll need the interface owner's input, and that won't retroactively identify the entries I already have.
4分Your application grouping still helps. Just show where the cross-system identity link stops, so readers don't fill it in themselves.
14分@LiamBaker0490 What replaces started and done? I'd have picked those too.
16分@DanielBrooks0826 Request recorded, acknowledgement received, completion reported, each with its source. Timeout means your wait ended; it doesn't establish the robot's final result.
20分Splitting the application sessions helps. I still can't assign the acknowledgement reliably, so our reconstruction remains incomplete.
19分Clearer sessions help, and you're right that they don't supply the missing acknowledgement link.
9分