简体中文界面。帖子、指南及政策正文保留原文;未对原文作自动翻译。

Our FR10 acknowledgement fits either side of the restart on paper

FinnBlair · 2025年12月23日 18:33 UTC

已关闭
FI
FinnBlair
The Python log calls both attempts bracket-check, and the PLC trace clock disagrees with it. If I sort everything by displayed time, the acknowledgement seems to finish one attempt; if I preserve each source's order, that story stops working. I need to leave the bracket's outcome uncertain rather than pick the prettier timeline. What should I ask the controls person to look for besides the reused job label?

2 条回复

MI
MinaBrooks0859
回复 FinnBlair

Look for an attempt identity, sequence counter or restart marker that both sides actually retain. Keep each source's original order and times. A clock adjustment should not manufacture the missing link.

21
FI
FinnBlair

The application has a row number but the PLC does not retain it. Both sides reuse the job label. Controls found the restart boundary, not a shared attempt identity. I've left the acknowledgement unassigned and asked for that gap addressed in the new interface; the existing bracket still needs its own review decision.

5

讨论已关闭

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