I can't assign this acknowledgement confidently. Our FR5 housing-check application restarted and reused the job label, then timed out. The PLC and Python clocks disagree, with a controller event list offering a third opinion.
I've kept the original files. Is there a sensible first comparison I can do without spending an afternoon moving timestamps until the story looks right?
Which FR5 attempt owns the acknowledgement after our laptop restarted?
LucaCarter0961 · 7 Oct 2025, 11:33 UTC
21 replies
Replying to CallumAli0186
Callum's planning example is familiar. I'd show the revised report to whoever normally queues the next batch and ask which entries they think are safe to schedule. You may find a second meaning of pending there.
15pointsDiscussion closed
This discussion is closed to new replies after six months without activity. Last activity: .