How can I tell which FR10 attempt received this acknowledgement?

JaneChan1119 · 8 Jul 2025, 12:29 UTC

Closed
JA
JaneChan1119
I'm investigating a bracket acceptance timeout. The application restarted and reused the label Check-1. PLC and controller clocks differ from the laptop. One acknowledgement could belong to either attempt. What should I reconstruct before calling the retry successful?

11 replies

GR
GraceBennett0755
Replying to JaneChan1119

Preserve each log's original order and timestamp source, then mark the restart boundaries. Look for identifiers carried between systems before aligning times; wall-clock proximity is not enough to choose between two attempts with the same label.

9 points
JA
JaneChan1119
Replying to GraceBennett0755

Application has a new process start entry before the second Check-1. The acknowledgement records that name but no attempt reference. PLC retains a counter, which we are checking against the trace.

12 points
DI
DineshCarter0995
Replying to JaneChan1119

Check what advances the counter before using it. It could count accepted requests, finished inspections or something else, and those are different boundaries around a timeout.

15 points
AI
AishaBarnes0605
Replying to JaneChan1119

Do the clocks have recorded offsets for the incident? Today's offset may not describe the log you are investigating, especially if a clock was corrected in between.

8 points
JA
JaneChan1119
Replying to AishaBarnes0605

No offset record from the incident. IT found a clock correction after it. We will not shift the old events by today's difference. Counter meaning is also undocumented so far.

10 points
GR
GraceBennett0755
Replying to JaneChan1119

Keep those uncertainties in the incident account. You may be able to bound an event between two known steps without assigning it an exact cross-system time, provided the linking evidence is explicit.

7 points
MI
MiaBennett0731
Replying to JaneChan1119

What does the screen currently tell the operator about that bracket? The log detective work can take ages, but I wouldn't leave a cheerful accepted label sitting there meanwhile.

19 points
JA
JaneChan1119
Replying to MiaBennett0731

It says accepted because the old code used the acknowledgement to finish the current row. Quality has held that bracket while controls investigates. The screen wording is being corrected.

7 points
AI
AishaBarnes0605
Replying to JaneChan1119

Acknowledged what? Receipt of a request and an accepted part are quite different. Check that meaning as well as which attempt it belongs to.

18 points
JA
JaneChan1119
Replying to AishaBarnes0605

Receipt only, according to controls. We had two mistakes: unknown attempt ownership and the wrong meaning assigned to the reply. Existing row remains under review; future interface changes are separate work.

6 points
DI
DineshCarter0995
Replying to JaneChan1119

Include both mistakes in the offline tests. A unique identifier will help with ownership, but it will not stop receipt being mistaken for a passing inspection.

22 points

Discussion closed

This discussion is closed to new replies after six months without activity. Last activity: .