How do I stop reconnect counting our bracket again?

AnikaBrown0943 · 2025年5月23日 00:42 UTC

已关闭

主帖中文翻译暂不可用,以下显示英文原文;回复保留原文。 查看英文原文

AN
AnikaBrown0943
Our FR5 monitor counts the retained completion on reconnect. Same job, extra accepted part. I want the job matched properly, without clearing the evidence or sending it again

11 条回复

LU
LucaBarnes0526

Compare the retained job reference with the saved result; have you got that reference on both sides?

6分
AN
AnikaBrown0943

PLC has it. Saved result has it too. Dashboard ignores it at startup

9分
LU
LucaBarnes0526

I'd take that exact pair to whoever owns the monitor, because it gives them a concrete duplicate to reproduce without touching the equipment

6分
OM
OmarBrooks0839

Also try a result that arrived while the monitor was away. Otherwise they'll fix this by ignoring the first reading and lose that one instead.

-1分
AN
AnikaBrown0943

That was their proposed fix. I've asked for both cases

18分
AN
AnikaBrown0943

They can replay both offline. Job numbers restart after maintenance though. That needs covering as well

16分
LU
LucaBarnes0526

Can the PLC identify which run that job number belongs to, so job one after maintenance doesn't collide with the old job one?

14分
VI
VictorBennett0707

I had a teaching example repeat work when the monitor reopened. We now make the students follow what was saved and what was merely seen on screen. Yours sounds like a useful case for that same paper walkthrough, especially at the maintenance reset.

13分
JO
JonasBarnes0546

What does the operator see while the software cannot match the result? A wrong total is bad, but a blank unexplained screen will probably earn another restart.

10分
LU
LucaBarnes0526

I'd like to hear that answer too; our quality totals get copied into a sheet, and the explanation often doesn't travel with the number

24分
AN
AnikaBrown0943

Controls is adding run identity. Unmatched results will show review required with a named contact. Offline duplicate case fixed; reset case still being checked

8分

讨论已关闭

此讨论已连续六个月没有活动,现已关闭新回复。 最后活动: .