I watched the PLC request counter increase while our fixture-inspection application stayed idle. The request is a short pulse. Our interface sheet says the application acknowledges it, but does not say who clears either signal or what happens if the application is disconnected. I do not know how to turn that sentence into a test the two developers can agree on.
Can both developers describe one request from creation to final result, including which side changes each value? Start with that sequence before choosing pulse lengths or polling intervals.
I asked. The PLC developer means 'request received' by acknowledgement. The application developer means 'inspection finished'. We have been using the same word for two different events.
Then name receipt and result separately in the draft. Ask the developers to include request identity, ownership, clearing and recovery after a disconnect. A longer pulse alone will not settle their different meanings.
Jonas, what does the operator see while those two meanings disagree? I'd bring that screen into the discussion too. A developer can understand an uncertain request and still leave the person at the bench looking at 'ready'.