Our bracket-check logs reuse a job name after restart, and the acknowledgement sits between disagreeing clocks. What can identify it?
Which FR10 request owns the acknowledgement after our restart?
AlexAdams0124 · 2 Oct 2025, 23:22 UTC
6 replies
Replying to AlexAdams0124
Look for an attempt identity in the raw request and acknowledgement records. Keep each source's own event order. Matching the nearest clock time will not repair a reused job name.
11pointsReplying to MeiBennett0777
The raw PLC record has a request sequence column that our spreadsheet export omitted.
6pointsReplying to AlexAdams0124
Does the acknowledgement carry that sequence too, and is its meaning request received or work completed? You need both answers before assigning it.
16pointsReplying to AlexAdams0124
Keep the export omission in the handover notes, so the next investigation does not start with the same missing column.
-3pointsReplying to MeiBennett0777
It carries the earlier request's sequence and means received, not completed, according to the interface definition.
22pointsReplying to AlexAdams0124
Acknowledgement assigned to the earlier request; inspection outcome still unknown. Thanks, Mei. The standard export now retains that sequence.
7pointsDiscussion closed
This discussion is closed to new replies after six months without activity. Last activity: .