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?
Two FR10 inspection attempts share the same local job label
ReeceCarter0993 · 2025年8月15日 08:25 UTC
主帖中文翻译暂不可用，以下显示英文原文；回复保留原文。 查看英文原文
7 条回复
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分The PLC export has a request counter, but our application log does not record it (only the reused label).
4分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分Check the raw response captures if you kept them. The counter might be there even though the summary logger dropped it.
13分Mina, no raw captures remain; Theo, startup entries separate the local attempts, but neither gives us the missing counter.
22分Then leave that acknowledgement unassigned. Guessing now gives someone a very convincing wrong example to use later.
17分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分讨论已关闭
此讨论已连续六个月没有活动，现已关闭新回复。 最后活动： .