Night-shift handover for our FR5 coupon inspection has one timeout and an acknowledgement nobody can place. Python restarted and reused the label. The three log clocks disagree. I'm reluctant to call either attempt complete.
Two attempts sharing one label
LouisBarnes0572 · 2026年9月4日 15:03 UTC
主帖中文翻译暂不可用，以下显示英文原文；回复保留原文。 查看英文原文
20 条回复
Leave completion unconfirmed for now. Does either attempt have a distinct sequence value?
21分Python only wrote the reused label. PLC trace includes a request counter. I'm looking for somewhere that counter reached the application log.
9分Check the raw response capture too, if you retained one.
15分Don't merge by displayed time yet; a local sequence can tell you more than three clocks disagreeing confidently.
5分Yes, keep each source in order before trying to align them.
13分Found a raw capture from before the restart. It contains the PLC counter beside the first label. Nothing equivalent after restart. At least the first request has an identity now.
21分What made you call the later entry a second attempt? I ask because our display once called reconnection a retry even though it had only read the existing PLC state. Very economical use of the word retry.
13分Distinguish intended work from transmitted work. An application retry entry does not establish that a second request reached the PLC. Preserve that uncertainty in the reconstruction until a corresponding transition or message can be identified.
11分Does the PLC counter advance after the restart?
22分No advance in the captured interval. And the application line says 'retry pending', not 'retry sent'. I shortened that too far in my opening.
20分Then a second executed attempt is not established by those records.
24分That removes one mystery cheaply. Still need to tie the acknowledgement to the first request, though.
20分The PLC trace has acknowledgement changing after that request counter appears. The application saw it later, following reconnect. I'll describe those as separate observations instead of two acknowledgements.
22分What will the incoming operator see on the job screen? The log explanation is improving, but they need to know whether that coupon's result is usable without becoming the fourth person interpreting three clocks.
22分An acknowledgement establishes only what the interface defines it to acknowledge. If it means request acceptance, it does not establish inspection completion or a passing result. That distinction should determine the displayed status.
12分What does your interface document say this acknowledgement means?
22分Request accepted. No result payload survived in our capture. The screen has been marked awaiting reconciliation by the controls lead; the coupon isn't being counted as inspected from this evidence.
14分Worth adding the request counter and application startup identity to future logs. Doesn't mend this record, but avoids the same guessing exercise.
17分Added both to the logging change request. Handover now says one confirmed accepted request, completion unknown, and no confirmed second request. That's less dramatic than my original version, fortunately.
5分That's a handover someone can use. Who covers the reconciliation if the controls lead is away when the next shift starts? The named contact needs a backup, especially for a state that blocks normal work.
20分