670   enable/disable LN via setting

Created: 03 Sep 2010

Status: In Force (green)

Part: Part 7-4 (2010; Edition 2)


Page: p22

Clause: 5.3 Common LN


Category: Issue for edition 3 of this part


Usually in conventional IEDs there is a setting to enable/disable its corresponding protection/control function.
In IEC 61850, the only way to do so is by using control service on LD/LN Mod via a client.
Why not provide the option of change LN Mod via settings? It's how it used to be, worked well, satified the utilitie's habit, and (I think)it's safer to enable/disable a function by setting rather than by control services over ethernet.


Discussion Created Status
09 Mar 11 In Force (green)
01 Feb 11 Ballot Period
Will be considered in edition 3. 28 Jan 11 Ballot Period
The idea is that SetMod ONLY contains the Mod default value when the IED is switched on, or the Mod value to be taken at a setting group switch. if the Mod is changed meantime, this is active immediately without influence to SetMod (i.e. Mod is 'stronger'), however just temporarily until a setting group change or an IED restart happens. 22 Nov 10 Discussion (red)
I support this idea. One question is open: is there a condition for instance modeling?: e.g. if the SetMod is modeled, the controllable Mod should be read-only to avoid a discrepancy.
Or another way would be to describe the mechanism like in the inheritance of the Beh. The stronger value is dominant (e.g. Off is stronger as Test).So you could switch off with command Mod=Off if the SetMod=Test.
19 Nov 10 Discussion (red)
Good idea. Add a setting SetMod:ENG to the common LN which defines the default value of Mod at startup and sets Mod in case its (SetMod's) active value is changed e.g. by a setting group change or a setting change. 16 Sep 10 Discussion (red)


Privacy | Contact | Disclaimer

Tissue DB v.