I have an FR5 bracket acceptance timeout and an acknowledgement with the same job label. Python restarted between them. The PLC clock is different again (not by a constant amount in my merged sheet). I need to untangle this before assigning a result to the bracket.
the same job label appears on both sides of our restart
VictorChen1142 · 2026年2月3日 12:40 UTC
主帖中文翻译暂不可用，以下显示英文原文；回复保留原文。 查看英文原文
8 条回复
Start with separate runs. Does the Python file mark its restart?
20分Yes, it has a startup header. The job label starts again below that header. My merged sheet hid the header because it has no job field.
20分I'd ditch the merged sheet for now. Not the files, just that view. It's making an invented continuous run look very official, which is exactly how we ended up arguing about the wrong branch on a tray problem.
6分Keep the startup header visible when you rebuild it. The blank job field still carries meaning.
-1分I have separated the two Python runs. The first includes the timeout. The acknowledgement appears only in the second export, but I cannot tell whether the PLC event was carried over.
11分Does the PLC export have an event counter or another ordering clue? I'm asking about an existing field, not suggesting you can recover the old sequence by adding one now.
11分There is an event counter. It places the acknowledgement before the restart marker recorded by the PLC, so my merge put an older acknowledgement beside the reused label. I have removed that match. The bracket still needs its acceptance decision checked.
17分That is a useful correction. Did you find a result belonging to the later attempt itself?
12分讨论已关闭
此讨论已连续六个月没有活动，现已关闭新回复。 最后活动： .