Function mode handling - Arc protection - Bay control and measurement - Merging unit - Transformer protection - 2 winding - Feeder protection - Voltage regulation - Capacitor bank protection - Grid automation - Busbar differential protection (high impedance) - Line differential protection - Back-up protection - Motor protection - Busbar protection (voltage and frequency) - Interconnection protection - Generator protection - Power management/Load shedding - IEC 61850 Engineering Guide - REX615 Protection and control - Relion Protection and Control - PCL2 - IEC - ANSI

Parameter Setting is the primary tool for changing the function's operation mode. IEC 61850 defines the logical node's common behavior. Each logical device (LD) must contain standard data objects LLN0.Mod and LLN0.Beh which can be statusonly or controllable.

Due to security and limited visibility in the menu, several mapping rules apply to Mod data objects.

Mod data objects are mapped to existing Mod parameters which are visible in the menu.
If Mod is unmapped, the functionality is always “on”.
If the intention is to turn the function off, the behavior (Beh) data must be in the menu.
Status-only must be used for the FPN control model when the intention is not to write the data. It is possible to override the ABB direct-with-normalsecurity by status-only in control model (ctlModel).

There are some recommendations for the menu parameters.

Test mode = "LD0.LLN0.Mod" via Tests > IED test
Device state = "LD0.LLN0.Beh" via Monitoring > IED status > Self-supervision
Control mode = "CTRL.LLN0.Mod" via Configuration > Control > General
Operation = "Function block master Mod" via Settings > Settings > <Category> > <Function name>
<Function name> = Function block Beh via Monitoring > FB status

Mapping example 1

All FPN mode parameters are mapped to the existing ABB model. The global mode parameter of the logical device (LLN0.Mod) is mapped to the ABB-specific LD0.LLN0.Mod.

Table 1. Mapping example 1
FPN model					ABB model
LD	LN	DO	DA	Default	LD	LN	DO	DA
Prot					LD0
	LLN0					LLN0
		Mod					Mod
			stVal					stVal
			Oper.ctlVal					Oper.ctlVal
			ctlModel					ctlModel
		Beh					Beh
			stVal					stVal
	HIPTOC1					PHIPTOC1
		Mod					Mod
			stVal					stVal
			Oper.ctlVal					Oper.ctlVal
			ctlModel					ctlModel
		Beh					Beh
			stVal					stVal

Mapping example 2

The FPN model's global mode is set to the default value. The behavior indicates the IED's global test mode regardless of the mapping.

Table 2. Mapping example 2
FPN model					ABB model
LD	LN	DO	DA	Default	LD	LN	DO	DA
Prot					LD0
	LLN0					(NONE)
		Mod					(NONE)
			stVal	on				(NONE)
			Oper.ctlVal					(NONE)
			ctlModel	status- only				(NONE)
		Beh					(NONE)
			stVal					(NONE)
	HIPTOC1					PHIPTOC1
		Mod					Mod
			stVal					stVal
			Oper.ctlVal					Oper.ctlVal
			ctlModel					ctlModel
		Beh					Beh
			stVal					stVal

Mapping example 3

DARREC1 is moved logically under control functions and existing ABB data LD0.DARREC1.Mod.stVal is explicitly mapped to new Control.Q1RREC1.Mod.stVal.

When the IEC 61850 MMS client writes Control.LLN0.Mod.Oper.ctlVal value "off", DARREC1 is switched off.

According to data model inheritance, MMS data Control.Q1RREC1.Beh.stVal indicates "off".
Existing menu parameter “Monitoring\FB status\Control\DARREC1”, which is actually LD0.DARREC1.Beh.stVal, indicates "off".

Table 3. Mapping example 3
FPN model					ABB model
LD	LN	DO	DA	Default	LD	LN	DO	DA
Control					CTRL
	LLN0					LLN0
		Mod					Mod
			stVal					stVal
			Oper.ctlVal					Oper.ctlVal
			ctlModel					ctlModel
		Beh					Beh
			stVal					stVal
	Q1CSWI					CBCSWI1
		Mod					Mod
			stVal					stVal
			Oper.ctlVal					Oper.ctlVal
			ctlModel					ctlModel
		Beh					Beh
			stVal					stVal
					LD0
	Q1RREC1					DARREC1
		Mod					Mod
			stVal					stVal
			Oper.ctlVal					Oper.ctlVal
			ctlModel					ctlModel
		Beh					Beh
			stVal					stVal

Mapping example 4

DARREC1 is moved visually under control functions. Since the engineer has not mapped DARREC1.Mod.stVal, the function still belongs logically under LD0.LLN0.Mod.

Table 4. Mapping example 4
FPN model					ABB model
LD	LN	DO	DA	Default	LD	LN	DO	DA
Control					CTRL
	LLN0					LLN0
		Mod					Mod
			stVal					stVal
			Oper.ctlVal					Oper.ctlVal
			ctlModel					ctlModel
		Beh					Beh
			stVal					stVal
	Q1CSWI					CBCSWI1
		Mod					Mod
			stVal					stVal
			Oper.ctlVal					Oper.ctlVal
			ctlModel					ctlModel
		Beh					Beh
			stVal					stVal
					LD0
	Q1RREC1					DARREC
		Mod					(NONE)
			stVal	on				(NONE)
			Oper.ctlVal					(NONE)
			ctlModel					(NONE)
		Beh					Beh
			stVal					stVal

Mapping example 5

It is possible to have multiple logical devices. Global modes LLN0.Mod should typically be mapped to global test mode LD0.LLN0.Mod. However, it is also possible to map the Mode parameter to existing ABB data in a more demanding way.

In the example below, ABB Operation parameters of protection trip conditioning (LD0.TPRPPTR1/2.Mod) are allocated to different logical devices of the FPN project (LLN.Mod). If the user writes "Off" to Prot2.LLN0.Mod.Oper.ctlVal, the following happens:

Relay's DEFPTOC1 is turned off.
FPN model's Control.DEFTOC1.Beh indicates “off”.
In the relay's menu, LD0.DEFPTOC1.Beh indicates “off”.

Table 5. Mapping example 5
FPN model					ABB model
LD	LN	DO	DA	Default	LD	LN	DO	DA
Prot1					LD0
	LLN0					TRPPTRC1
		Mod					Mod
			stVal					stVal
			Oper.ctlVal					Oper.ctlVal
			ctlModel					ctlModel
		Beh					Beh
			stVal					stVal
	OCPTRC1
		Op					Op
			general					general
	OCPTOC1					PHIPTOC1
		Mod					Mod
			stVal					stVal
			Oper.ctlVal					Oper.ctlVal
			ctlModel					ctlModel
		Beh					Beh
			stVal					stVal
Prot2
	LLN0					TRPPTRC2
		Mod					Mod
			stVal					stVal
			Oper.ctlVal					Oper.ctlVal
			ctlModel					ctlModel
		Beh					Beh
			stVal					stVal
	DEFPTRC1
		Op					Op
			general					general
	DEFPTOC1					DEFHPTOC1
		Mod					Mod
			stVal					stVal
			Oper.ctlVal					Oper.ctlVal
			ctlModel					ctlModel
		Beh					Beh
			stVal					stVal