two attempts sharing a very unhelpful job label

AnikaBennett0769 · 12 Aug 2025, 00:27 UTC

Closed
AN
AnikaBennett0769
Our UR5e bracket verification log uses check-7 before and after a Python restart, and the PLC clock disagrees with the laptop. I've got an acknowledgement with two possible homes, neither especially convincing

10 replies

ZA
ZaraBaker0482
Replying to AnikaBennett0769

Can you see the application restart in the original log, and does either side retain a sequence number? Start there before shifting timestamps around. The same label on both attempts makes a sorted spreadsheet look more certain than it is.

20 points
AN
AnikaBennett0769
Replying to ZaraBaker0482

Restart is clear, sequence number isn't. Python starts numbering again at one, while the exported PLC trace only contains the job label and acknowledgement state

13 points
ZA
ZaraBaker0482
Replying to AnikaBennett0769

Ask controls whether the original capture contains more fields than the export. You might recover an attempt reference that was left out. Keep the original order within each log meanwhile, even though the clocks do not line up.

11 points
JU
JuliaAdams0152
Replying to AnikaBennett0769

Was that acknowledgement a new change, or was it already on when the trace started? I'd want to know that before giving it to either attempt.

0 points
VI
VictorChen1142
Replying to JuliaAdams0152

Julia's point matters for the report too. A state sampled at capture start needs a different description from a recorded transition. Otherwise the next person may read it as an event you actually saw.

11 points
AN
AnikaBennett0769
Replying to JuliaAdams0152

Already on in the first sample. I had drawn an arrow from it to the retry, which now looks a bit ambitious. Removing that arrow

2 points
VI
VictorChen1142
Replying to AnikaBennett0769

Keep the observation, though. It tells the reader what was present when capture began, even if its origin remains unknown. Put the missing earlier trace beside that limitation.

14 points
TH
ThomasAbbott0016
Replying to AnikaBennett0769

We once spent ages aligning clocks only to find a held bit in every row. Is there an older capture on the engineering laptop before anyone goes looking for clever timing tools?

12 points
ZA
ZaraBaker0482
Replying to ZaraBaker0482

Did controls find any earlier capture or extra identifier, Anika? I'm curious whether you managed to connect either attempt, or whether this remains a logging change for the next investigation.

19 points
AN
AnikaBennett0769
Replying to ZaraBaker0482

No earlier capture turned up. Controls is adding an attempt reference that survives application restarts; the old acknowledgement stays unassigned. Thanks Julia, that arrow would have become a very confident paragraph

3 points

Discussion closed

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