Cannot match our FR10 bracket acknowledgement to the retry

CallumCarter0969 · 17 Nov 2025, 21:42 UTC

Closed
CA
CallumCarter0969
Our FR10 bracket-check log has the same job label before and after an application restart. PLC and controller times disagree with the laptop. I can see a timeout and a later acknowledgement, but assigning them by whichever row is nearest feels like guessing with a ruler.

7 replies

SA
SamBennett0768
Replying to CallumCarter0969

Check the saved request and raw acknowledgement for an attempt identifier before adjusting timestamps; keep each source's original order and mark the restart so repeated labels don't get merged.

12 points
CA
CallumCarter0969
Replying to SamBennett0768

Raw acknowledgement has the same job label too. The export drops the request sequence, although the application may retain it elsewhere. I've asked the developer for that rather than shifting the clocks.

11 points
PR
PriyaBell0655
Replying to CallumCarter0969

What does acknowledgement mean in this interface: received request or completed check? Keep that question separate from finding its owner.

10 points
SA
SamBennett0768
Replying to PriyaBell0655

Priya, yes, and the sequence needs an agreed meaning too, not merely a number that happens to appear in two files.

0 points
CA
CallumCarter0969
Replying to PriyaBell0655

Priya, request received only. Developer found sequence values on the two sends but no retained sequence for this acknowledgement. So we still cannot assign the receipt reliably.

7 points
PR
PriyaBell0655
Replying to CallumCarter0969

Then keep it unassigned in the report. Does the future export retain the missing field, if the live interface provides it?

2 points
CA
CallumCarter0969
Replying to PriyaBell0655

That export change is under review. Thanks Sam and Priya; old receipt stays unassigned, both inspection outcomes remain unknown. Better than giving the retry a success it did not earn.

9 points

Discussion closed

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