Our FR10 fixture-check monitor counts a completion again on reconnect although the indication was already high. How should I match it to its original attempt without clearing it or resending work?
Which coupon attempt owns the FR10 completion retained through disconnection?
CarlaArcher0401 · 2026年7月2日 19:55 UTC
主帖中文翻译暂不可用，以下显示英文原文；回复保留原文。 查看英文原文
12 条回复
Check the retained identity and result beside the processing history that survives restart. The first high state after reconnect is an observation of retained data, not proof that a new job just completed.
18分回复 LucyBell0654
The retained record has a unique attempt identity and coupon link. Our saved detail row already contains that result once, but the displayed total increments when the monitor sees high after connecting.
18分Then fix the total's source rather than disturb the PLC state to make the screen's arithmetic behave
21分Does the total mean completed attempts or accepted coupons? The same stored result can support a technical completion count without establishing the coupon's current quality disposition.
4分Replay the saved records first. Can the expected total be rebuilt without a live connection?
25分Anna, this screen explicitly reports completed attempts; quality dispositions are elsewhere. Zara, the replay rebuilds the expected total from distinct durable attempt rows. We have stopped incrementing a separate number just because the retained bit is high.
2分Include a completion first discovered after disconnection too. Reconnect must not add a duplicate, but it still needs to record genuinely new identified results that arrived while the monitor was absent.
14分And reopening should derive the same result, not restore yesterday's separate counter from another file
23分回复 LucyBell0654
Both pass in the replay: repeated retained result stays one row, and a newly discovered identified completion adds one row and one completed attempt. Reopening rebuilds the same total. The old standalone counter is no longer read.
8分Have those tests used the actual retained-record format from your documented interface? A convenient fake identity would test the counter while leaving the real input path unexamined.
25分Yes, saved records from the installed interface, then the maintainer repeated the reconnect comparison through the normal monitor. Counts match the durable rows after reopening. Thanks Anna; the screen label remains completed attempts, not accepted coupons.
12分Keep that distinction and the newly discovered-result test in the handover. The fix now accounts for both replayed history and work first observed after reconnect, without changing the job's physical state.
22分