1975 Modes "blocked" and "test/blocked" impact electrical outputs only, not data

Created: 25 Apr 2025
Status: Approval (Future Improvement)Show the workflow
Part: Part 7-4 (2020; Edition 2.1)
Links: None
Page: 454
Clause: Annex A
Paragraph: Table A.1, Table A.2

Issue

There is ambiguity whether modes "blocked" and "test/blocked" block electrical outputs only (relays, analogue outputs e.g.) or whether these modes additionally block the output of data.

Proposal

Clarify whether the output of data is impacted by the modes "blocked" and "test/blocked".

Marking of "q.test" = "true" by LN instances the modes of which are "test" or "test/blocked" is not under question here.

Clarity could be achieved by a statement in Annex A.

Discussion	Created
Approval (Future Improvement) changed state to "Future Improvement"	26 Aug 26
Discussion (red) follwing the discussions within WG10 incl. TF 10-3, I propose to change the state to 'Approval (Future Improvement)'	28 Jul 26
Discussion (red) Good to see that from the wording of the standard "All communication services work and get updated values." the expected behaviour is described: no blocking of data. But, although this texts exists since many years, there is still ambiguity in the community how to understand it. Could an additional statement like "The update of output data is not blocked." be added to both mode "blocked" and mode "test/blocked"?	07 Jul 26
Discussion (red) The definition in Table A.1 clearly states: "All communication services work and get updated values." Therefore it is expected that these mode "do not block" the update of the data. Propose to set to N/A.	07 Jul 26
Discussion (red) Change to "discussion"	02 May 25
Accepted It is stated that wired (electrical) outputs to process (switchgear) are considered. The intention is to model a test plug, what is often used testing (e.g. test of in protection settings and functions). Data that are used to communicate information to other functions in different IEDs are not considered.	02 May 25