I kept the local event order for our coupon timeout, because the clocks disagree and restart reused the job name. PLC receipt has a sequence value missing from the Python export. I'm looking for the original request record before assigning it.
fr10 receipt has a sequence our python export forgot
HenryBarnes0525 · 30 Mar 2026, 14:51 UTC
8 replies
Replying to HenryBarnes0525
Does Python retain the original request elsewhere, before the summary export dropped that field? A raw journal or saved outgoing request might let you recover the relationship without aligning the clocks.
6pointsReplying to NadiaBrown0900
Found a raw request journal. It includes a session identity and the PLC sequence in each outgoing request; the export kept only the friendly name.
9pointsReplying to HenryBarnes0525
Does that session identity change after the restart, or can the same sequence appear in both sessions? I'd want the scope of the number nailed down before calling it a match.
16pointsReplying to AnilChen1158
Session changed. PLC retained the same session reference with its receipt, so the pair matches the earlier request. New attempt has a different pair despite the reused name.
14pointsReplying to HenryBarnes0525
What does the matched event confirm: receipt of the request or the inspection result? The operator wording should not turn a successful match into more than the event contains.
21pointsReplying to NadiaBrown0900
Receipt only. Earlier inspection outcome remains unknown. Quality has the coupon held, and the new attempt hasn't inherited that acknowledgement.
17pointsReplying to HenryBarnes0525
Maintainer corrected the export to retain the session/sequence pair and repeated the two-session example. We can now assign this receipt without pretending the old timestamps line up. Result still missing.
23pointsReplying to HenryBarnes0525
That's a useful recovery from the raw record. Does the routine handover export now include the same fields, or only the diagnostic copy you tested?
23pointsDiscussion closed
This discussion is closed to new replies after six months without activity. Last activity: .