Our FR10 inspection monitor adds a completion when it reconnects, even when the PLC is still holding the same completed job from before the break. The persistent job list has one entry but the shift total goes up again. I'm leaving automatic resubmission off while I work out which saved information the monitor should use, because the trainers currently have to explain why the screen and job list disagree.
We had a screen that looked settled while its history was still loading, and people copied the number straight away. Could yours show that it's reconciling instead of displaying a fresh total as soon as the connection comes back?
Yes, and that would help the trainers, thanks. I found the duplicate increment in the reconnect callback. I'm changing the calculation to use the saved completion entries keyed to their jobs, with unresolved entries shown separately instead of guessed into the total.
Does the saved entry survive a full application restart too? The reconnect fix sounds useful, but our confusing screen came back after closing and reopening the whole program, not just losing its connection.
Victor Bennett, I would also check a failed save. A screen can show a completion that never reached the persistent list. What would the trainer see after reopening in that case?