Get both programmers to write the intended state sequence together, including who sets and clears each signal. Making the pulse longer might hide the symptom while leaving the two sides with different ideas about what acknowledgement means.
简体中文界面。帖子、指南及政策正文保留原文;未对原文作自动翻译。
our request disappears before the app sees it
RaviCarter0998 · 2025年3月3日 13:38 UTC
13 条回复
PLC author means 'request offered'. App author means 'request accepted'. Same bit name, different contract.
8分There's a useful starting point. Define the meaning of each transition as well as its owner, including what remains asserted until the other side confirms it. Names alone won't resolve that disagreement.
10分Does the handover documentation include what should happen when the PC restarts halfway through, because we inherited a cell where both programs seemed reasonable individually and neither expected to meet the other's old signals on startup?
17分Include that in the contract. Normal completion, timeout, reconnect and restart need defined outcomes, not an instruction for the operator to keep clearing bits until the screen looks ready again.
18分No restart definition exists. We're reviewing the job state diagram before changing either program.
8分Use the missed-request trace as one example for that review. It should explain the observed loss, and the revised design should specify how receipt is confirmed despite different polling schedules.
7分Our training bench had two writers clearing one status bit. Could you check the actual writers against the proposed ownership table, not only the comments?
18分Found an old cleanup routine clearing request too. Comments never mentioned it. Added to the review.
22分That sounds familiar; who will own the final interface document when both programmers leave, so maintenance has one place to look instead of choosing whichever comment seems newest?
23分Assign a joint acceptance test too. Each side passing its own test isn't enough if the tests assume different clearing rules. Exercise the complete job interface, including interrupted exchanges, in a controlled environment before deployment.
1分And make the operator recovery procedure match those tested states. Otherwise the software contract will be precise and the shift instructions will still say 'restart and try again', which reintroduces the uncertainty.
8分Controls lead owns the draft contract. Joint tests and recovery instructions pending; no live interface change yet.
7分讨论已关闭
此讨论已连续六个月没有活动,现已关闭新回复。 最后活动: .