I unplugged the monitoring laptop from our UR5e inspection network during a completed job and reconnecting added another accepted housing. Nothing moved in the cell. The ordinary completion signal was still high.
I was going to ignore the first reading after connection. Thinking about it, that could hide a real result too. What should the app compare before deciding that reading represents another housing?
Was the first count saved before you disconnected? I ask because remembering the last displayed number and remembering which job was counted are different things in our little tracker.
Yes. Controls confirmed it resets. We need a run identity with it, not just the bare job number. They're reviewing what the PLC can retain and report reliably.
That caught ours in testing. We added a list of jobs and were delighted until a new run reused the numbers. It is worth testing a completed job that the app never saw, too; otherwise the duplicate fix can quietly throw away missing results.
Maintainer has both cases now, Alex. We removed my ignore-first-reading idea from the change request. Revised interface is still being worked out, so I haven't got a fixed count to report.