Two FR10 inspection attempts share the same local job label

ReeceCarter0993 · 15 Aug 2025, 08:25 UTC

Closed
RE
ReeceCarter0993
I cannot assign one acknowledgement to an inspection attempt because the app reused its job label after restarting and the PLC and laptop clocks disagree; is there another reliable link I should look for in the existing exports?

7 replies

TH
TheoArcher0410
Replying to ReeceCarter0993

Look for request sequence values or other identifiers that appear in both exports. I wouldn't start by lining up the nearest times. We once made two unrelated events look connected by correcting one clock against the very event we were trying to identify.

16 points
RE
ReeceCarter0993
Replying to TheoArcher0410

The PLC export has a request counter, but our application log does not record it (only the reused label).

4 points
TH
TheoArcher0410
Replying to ReeceCarter0993

Any connection or startup entries around those attempts? They may let you split the application file into runs, even if they don't identify the acknowledgement on their own.

21 points
MI
MinaBennett0772
Replying to ReeceCarter0993

Check the raw response captures if you kept them. The counter might be there even though the summary logger dropped it.

13 points
RE
ReeceCarter0993
Replying to MinaBennett0772

Mina, no raw captures remain; Theo, startup entries separate the local attempts, but neither gives us the missing counter.

22 points
MI
MinaBennett0772
Replying to ReeceCarter0993

Then leave that acknowledgement unassigned. Guessing now gives someone a very convincing wrong example to use later.

17 points
TH
TheoArcher0410
Replying to ReeceCarter0993

For the next capture, have the maintainer record the agreed request identity in each participating log and note restarts explicitly. Keep your current exports unchanged. They show why that addition is needed, even without a neat answer to this occurrence.

16 points

Discussion closed

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