Profinet Driver en

Security information 1
Introduction 2
System requirements 3
SIMATIC
Configuring 4
Process Control System PCS 7
PROFINET driver blocks SIPROTEC 5 5
Blocks
Programming and Operating Manual
08/2021
A5E51115894-AA
Legal information
Warning notice system
This manual contains notices you have to observe in order to ensure your personal safety, as well as to prevent damage
to property. The notices referring to your personal safety are highlighted in the manual by a safety alert symbol, notices
referring only to property damage have no safety alert symbol. These notices shown below are graded according to
the degree of danger.
DANGER
indicates that death or severe personal injury will result if proper precautions are not taken.
WARNING
indicates that death or severe personal injury may result if proper precautions are not taken.
CAUTION
indicates that minor personal injury can result if proper precautions are not taken.
NOTICE
indicates that property damage can result if proper precautions are not taken.
If more than one degree of danger is present, the warning notice representing the highest degree of danger will be
used. A notice warning of injury to persons with a safety alert symbol may also include a warning relating to property
damage.
Qualified Personnel
The product/system described in this documentation may be operated only by personnel qualified for the specific
task in accordance with the relevant documentation, in particular its warning notices and safety instructions.
Qualified personnel are those who, based on their training and experience, are capable of identifying risks and
avoiding potential hazards when working with these products/systems.
Proper use of Siemens products
Note the following:
WARNING
Siemens products may only be used for the applications described in the catalog and in the relevant technical
documentation. If products and components from other manufacturers are used, these must be recommended or
approved by Siemens. Proper transport, storage, installation, assembly, commissioning, operation and maintenance
are required to ensure that the products operate safely and without any problems. The permissible ambient
conditions must be complied with. The information in the relevant documentation must be observed.
Trademarks
All names identified by ® are registered trademarks of Siemens AG. The remaining trademarks in this publication may
be trademarks whose use by third parties for their own purposes could violate the rights of the owner.
Disclaimer of Liability
We have reviewed the contents of this publication to ensure consistency with the hardware and software described.
Since variance cannot be precluded entirely, we cannot guarantee full consistency. However, the information in this
publication is reviewed regularly and any necessary corrections are included in subsequent editions.
Siemens AG A5E51115894-AA Copyright © Siemens AG 2021.

Digital Industries Ⓟ 07/2021 Subject to change All rights reserved
Postfach 48 48
90026 NÜRNBERG
GERMANY
Table of contents
1 Security information.............................................................................................................................. 5
2 Introduction ........................................................................................................................................... 7
2.1 Environment........................................................................................................................ 7
2.1.1 Hardware............................................................................................................................. 7
2.1.2 Software.............................................................................................................................. 7
2.2 Overview of blocks............................................................................................................... 8
3 System requirements............................................................................................................................. 9
3.1 Hardware............................................................................................................................. 9
3.2 Software.............................................................................................................................. 9
4 Configuring .......................................................................................................................................... 11
4.1 Configuration in DIGSI 5 ..................................................................................................... 11
4.2 Hardware configuration in HW Config ................................................................................. 11
4.3 Installation and interconnection of the driver blocks in CFC ................................................ 13
4.4 Mapping example .............................................................................................................. 14
4.4.1 Diagnostics ........................................................................................................................ 15
4.4.2 Circuit breaker - interlock, switching command and feedback ............................................. 18
4.4.3 Device operating hours and switching cycles ...................................................................... 22
5 Blocks................................................................................................................................................... 27
5.1 General functionalities ....................................................................................................... 27
5.1.1 Inputs................................................................................................................................ 27
5.1.2 Outputs ............................................................................................................................. 28
5.1.3 Mapping ............................................................................................................................ 28
5.1.3.1 Parameter changes in the mapping .................................................................................... 29
5.1.3.2 CMD_MAP ......................................................................................................................... 30
5.1.3.3 MEAS_MAP ........................................................................................................................ 30
5.1.3.4 BSTR_MAP ......................................................................................................................... 30
5.1.3.5 DIAG_MAP ......................................................................................................................... 31
5.1.4 Commands ........................................................................................................................ 31
5.1.5 Troubleshooting................................................................................................................. 31
5.1.6 Diagnostic outputs............................................................................................................. 32
5.1.7 Divisor for measured values ............................................................................................... 32
5.1.8 Converting energy pulses................................................................................................... 33
5.1.9 System functions used ....................................................................................................... 33
5.1.10 Initialization following hardware change ............................................................................ 33
5.2 SIP5_FEEDER...................................................................................................................... 34
5.3 SIP5_Line........................................................................................................................... 34
5.4 SIP5_TRAFO ....................................................................................................................... 34
5.5 SIP5_SYNC ......................................................................................................................... 34
PROFINET driver blocks SIPROTEC 5

Programming and Operating Manual, 08/2021, A5E51115894-AA 3
Table of contents

4 Programming and Operating Manual, 08/2021, A5E51115894-AA
Security information 1
Siemens provides products and solutions with industrial security functions that support the
secure operation of plants, systems, machines and networks.
In order to protect plants, systems, machines and networks against cyber threats, it is necessary
to implement – and continuously maintain – a holistic, state-of-the-art industrial security
concept. Siemens’ products and solutions constitute one element of such a concept.
Customers are responsible for preventing unauthorized access to their plants, systems,
machines and networks. Such systems, machines and components should only be connected to
an enterprise network or the internet if and to the extent such a connection is necessary and only
when appropriate security measures (e.g. firewalls and/or network segmentation) are in place.
For additional information on industrial security measures that may be implemented, please
visit
https://www.siemens.com/industrialsecurity.
Siemens’ products and solutions undergo continuous development to make them more secure.
Siemens strongly recommends that product updates are applied as soon as they are available
and that the latest product versions are used. Use of product versions that are no longer
supported, and failure to apply the latest updates may increase customer’s exposure to cyber
threats.
To stay informed about product updates, subscribe to the Siemens Industrial Security RSS Feed
under
https://www.siemens.com/industrialsecurity.

Security information

Introduction 2
General information
The PROFINET driver blocks for PCS 7 PowerControl form the interface between SIPROTEC 5
protection devices with a PROFINET interface and the technological objects of the PowerControl
Library (PCL). The blocks can only be used in connection with the blocks of the PCL.
This manual must be used in conjunction with the PCL and DIGSI 5 manuals and requires
knowledge of this documentation.
2.1 Environment
2.1.1 Hardware
The PROFINET driver blocks operate together with the technological blocks of the PCL on the
PCS 7 controller (AS). They access the data of the devices connected to PROFINET via the process
image input of the CPU and write commands via the process image output of the CPU.
2.1.2 Software
The PROFINET driver blocks for PowerControl are configured in the user program of the
automation system using the CFC editor and connected to the blocks of the PCL. Special
structures that exchange all necessary data between the technological blocks and the driver
blocks are available for this connection.
A driver block can only be connected to the corresponding technological block. A driver block
cannot be connected to multiple technological blocks.
The data points of the driver block must be mapped in accordance with the respective SIPROTEC
device. The DIGSI 5 software must be used to assign parameters for this mapping in the
SIPROTEC 5 device. The mapping can be freely configured and is not predefined.
The screenshot below shows a CFC chart with a driver block and a technological block:

Introduction
2.2 Overview of blocks
Figure 2-1 Driver block (1) and technological block (2)
2.2 Overview of blocks

The table below shows all available PROFINET driver blocks with the corresponding
technological blocks:
Name FB No Technological block (PCL)

SIP5_FEEDER FB2592 PC_FEEDER, PC_FEEDER_2CB
SIP5_LINE FB2593 PC_LINE
SIP5_SYNC FB2594 PC_SYNC
SIP5_TRAFO FB2595 PC_TRAFO

System requirements 3
3.1 Hardware
PROFINET driver blocks can run on all automation systems released for PCS 7. The interface
integrated in the CPU or an external communications processor (CP) is used for PROFINET
communication.
3.2 Software
The PROFINET drivers were developed with GSDML-V*-SIEMENS-SIPROTEC5-*.XML and the
GSDML "GSDML-V2.32-Siemens-SIPROTEC5-20191012" is also supported and are only approved
in conjunction with these GSDMLs.
The PROFINET driver blocks have been released for the PCS 7 version 9.1.

System requirements
3.2 Software

Configuring 4
The following section shows the individual steps of configuring a SIPROTEC 5 - PN device driver
in PCS 7.
4.1 Configuration in DIGSI 5

Requirement
The SIPROTEC device must be fully configured using the DIGSI software prior to its integration in
PCS 7 PowerControl.
You can find more information on this subject in the DIGSI documentation.
Note the following in regard to communication with PowerControl:

• The PROFINET device name must be configured.
• The required control rights (remote / local) must be configured.
• All required alarms and diagnostics must be configured.
• All required measured values must be configured.
• All required statistical values and counter values must be configured.
• All necessary commands and feedback signals must be configured.
4.2 Hardware configuration in HW Config
To configure a SIPROTEC device in HW Config, it must be connected to the PROFINET IO system

from the "PROFINET IO -> Protection and PQ -> SIPROTEC 5 ..." library using drag-and-drop. The
matching GSDML file must be installed in advance.
The same device name that was set in DIGSI for the device must be assigned in the object
properties of SIPROTEC. This is a prerequisite for establishing a PROFINET connection between
the PROFINET controller and SIPROTEC.

Configuring
4.2 Hardware configuration in HW Config
Figure 4-1 Hardware configuration
The required modules can now be dragged onto the slots of the device. The order of the modules
does not matter.
You can select:
Name Type Number of signals Mapping on the driver block using

per module
Single messages Input data 16 or 32 ALRM_MAP, DIAG_MAP, BOOL_MAP
Double messages Input data 4 or 8 ALRM_MAP
Measured values Input data 6 or 12 MEAS_MAP, BSTR_MAP
Counter values Input data 4 BSTR_MAP
Double commands Output data 04 or 08 CMD_MAP
Single commands Not used
Actuating com‐ Not used
mands
Step commands Not used
These modules are used to exchange data between the CPU and the SIPROTEC. The signals are
mapped via the "communication assignment" in DIGSI and via the inputs "ALRM_MAP",
"DIAG_MAP", "MEAS_MAP", "CMD_MAP", and "BSTR_MAP" at the driver block. Section 4.4
(Page 14) explains the mapping using an example.
Section 7.1.5 in the SIPROTEC 5 Communication Protocols manual in the internet link (https://
support.industry.siemens.com/cs/ww/en/view/109742443) provides a very clear description of

Configuring
4.3 Installation and interconnection of the driver blocks in CFC
the assignment of I/O modules to SIPROTEC 5 data objects. This manual also provides detailed
information about the modules described and the data types used.
NOTICE
A module error will occur if more modules of a data type are configured in HW Config than
are required by the configuration in DIGSI.
4.3 Installation and interconnection of the driver blocks in CFC

The PN driver blocks can be dragged from the Power Control library into a CFC chart. They can
then be connected to their associated technological block, once the block has also been drawn
from the library into the chart. For this, the respective inputs and outputs "Rcv_Data" and
"Snd_Data" of the two blocks must be connected:
Figure 4-2 Interconnection in the CFC chart using the FEEDER example
The input "Start_In" of the driver block is connected to the first bit of the first input module of the
SIPROTEC 5 device (here EB10).
If the chart is compiled using the option "Generate module drivers", the inputs "Mod_Data" and
"RAC_DIAG" of the driver block are automatically connected by the driver wizard.

Configuring
4.4 Mapping example
Figure 4-3 Compile CFC with "Generate module drivers"
4.4 Mapping example

This section explains, by way of example, the mapping between a SIPROTEC configuration in
DIGSI 5 and a SIP5_FEEDER driver block. This is based on the configuration described in the
previous section. The examples are just suggestions on how the mapping could be structured.
Of course, it could be different, depending on the respective requirements.
The changes made by the mapping are demonstrated step by step on the corresponding
faceplate:

Configuring
4.4 Mapping example
Figure 4-4 Faceplate without mapping
4.4.1 Diagnostics
The diagnostics is mapped first. To do this, the "Communication assignment" must be opened in
DIGSI 5. In the example image (Figure 4-5 Mapping the diagnostics in DIGSI 5), the signals of the
sections "General" -> "State" and "Standby" are assigned to the single messages 1-6 (indicated by
the "PLC" type).
It is important to know that the mapping is performed using values rather than input and output
addresses. The values are assigned to logical addresses fully automatically in the background.
The values do not need to be consecutive, and can be freely selected within the limits of the
respective type. Make sure that enough modules of the respective type are configured in HW
Config.

Configuring
4.4 Mapping example
Figure 4-5 Mapping the diagnostics in DIGSI 5
"Health" -> "OK" has been assigned to the value 1 in the example image (Figure 4-5 Mapping the
diagnostics in DIGSI 5). This represents the first single message of the first module "Single
message 16" in HW Config (see Figure 4-1 Hardware configuration) in the section Hardware
configuration in HW Config (Page 11). With the current configuration consisting of 2 * "single
messages 16" and 1 * "single messages 32", the maximum value of 64 may be assigned to signals
of the "PLC" type in the communication assignment. For the changes to be accepted, the new
configuration must be loaded into the device.
The input DIAG_MAP is used for the mapping on the driver block (Figure 4-6 Mapping the
diagnostics on the driver block). In this structure, the values set in DIGSI can be assigned to the
corresponding signals. The respective maps CMD_MAP, ALRM_MAP, etc. are used for mapping
commands, alarms, etc. An unmapped signal has the value "-1" by default. It can be assigned
again at any time in order to remove a mapping.
If the mapping is made in the test mode of the CFC editor, the changes take effect immediately.
If the changes are made offline, the chart must be recompiled and reloaded.

Configuring
4.4 Mapping example
Figure 4-6 Mapping the diagnostics on the driver block
This completes the mapping of these 6 signals. The two "DIAG_MAP" elements "Dev_Rdy" and
"Dat_Val" must also be mapped. Otherwise, the block will report a device error. In this example,
both elements are mapped to "Device" -> "Life contact".
As soon as all "DIAG_MAP" elements are correctly mapped, the two indicators in the lower left
corner of the faceplate change their value from N/A to the values transferred by SIPROTEC. In this
example, the values are "Device OK" and "Protect On" (Figure 4-7 Faceplate with mapped device
and protection status).

Configuring
4.4 Mapping example
Figure 4-7 Faceplate with mapped device and protection status
4.4.2 Circuit breaker - interlock, switching command and feedback

In the next example, the circuit breaker "CB" (Figure 4-7 Faceplate with mapped device and
protection status) is made switchable via the faceplate. This requires the following steps to be
taken:
• Set switching authority to remote
• Map interlock
• Map switching command
• Map feedback of the switch position
For commands to be executed via the faceplate, the "switching authority" of SIPROTEC must be
set to "Remote". This setting can be made on the SIPROTEC itself via the operator terminal. To
map the interlock, "Circuit breaker 1" -> "Interlock" -> "> Rel. deactivation" and "> Rel. activation"
must be linked to a single message in the communication assignment in DIGSI:
Figure 4-8 Mapping interlocks in DIGSI

Configuring
4.4 Mapping example
The switching command is linked to double command 1 via "Circuit-breaker 1" -> "Control" ->
"Command with feedback". For this, a "double commands" module must be configured in HW
Config.
Figure 4-9 Mapping a switching command in DIGSI
The feedback of the switch position is linked to double message 2 via "Circuit breaker 1" ->
"Circuit breaker" -> "Position". For this, a "double messages" module must be configured in HW
Config.
Figure 4-10 Mapping the feedback of a circuit breaker in DIGSI
As shown in the previous example, the maps at the driver block must be adapted. The interlocks
and the switch position are mapped via "ALRM_MAP":
Figure 4-11 Mapping a switching command at the driver block png
Figure 4-12 Mapping interlocks at the driver block

Configuring
4.4 Mapping example
NOTICE
Unlike the other values in ALRM_MAP, double messages, such as feedback from switches,
are imported by a double message module instead of a single message module.
Depending on the driver block, the last 4 or 8 elements in ALRM_MAP are interpreted as
a double message. The other elements are interpreted as single messages.
The switching command is mapped via "CMD_MAP":
Figure 4-13 Mapping of the feedback of a circuit breaker at the driver module png
As a result of this mapping, the two interlock symbols "Op" and "Cls" turned green, and the circuit
breaker can now be actuated. The feedback of the current switch position is displayed correctly
by the "Open" indicator.

Configuring
4.4 Mapping example
Figure 4-14 Faceplate with controllable CB circuit breaker
The following table summarizes which signals must be mapped in order to control the circuit
breaker:
Path in DIGSI Map + element to be mapped

"Circuit breaker 1" -> "Interlock" -> "> Rel. deacti‐ "ALRM_MAP" -> "Q0_EnaCls"
vation"
"Circuit breaker 1" -> "Interlock" -> "> Rel. activa‐ "ALRM_MAP" -> "Q0_EnaOpn"
tion"
"Circuit breaker 1" -> "Control" -> "Command with "CMD_MAP" -> "Q0"
feedback"
"Circuit breaker 1" -> "Circuit breaker" -> "Position" "ALRM_MAP" -> "Q0"
"General" > "Key auth. Key/par" (not described in "ALRM_MAP" -> "LOC"
the example) (For displaying the key authority: "Remote" or "Lo‐
cal")

Configuring
4.4 Mapping example
4.4.3 Device operating hours and switching cycles

In this example, device operating hours and switching cycles are mapped. This requires a
workaround, because these two signals are of the "State of an integer measured value (INS)"
type and cannot be interconnected in the communication assignment of DIGSI 5 V7.80.
Figure 4-15 Signal for switching cycle in DIGSI 5
Figure 4-16 Signal for device operating hours in DIGSI 5
Therefore, both signals must be converted to an auxiliary signal of an interconnectable type

according to the function diagram. To do this, create two new signals in the communication
assignment by right-clicking on "Device" -> "Add new signal":
Figure 4-17 Adding a new signal
It would be intuitive to select the "Counter value (BCR)" type for the auxiliary signals, since the
two signals are mapped at the driver block via "BSTR_MAP". However, this is not possible because
this type is not available when creating new signals. Therefore, the "Measured value (MV)" type
is selected and the two signals, "Device operating hours_MV" and "Switch cycle counter_MV", are
created newly. These are also mapped directly to the values 3 and 4.

Configuring
4.4 Mapping example
Figure 4-18 Creating the "Device operating hours MV" signal
Figure 4-19 Newly created auxiliary signals
These newly created signals can now be described in a function diagram using the signals of the
"INS" type. This requires a "SPLIT_INS" block and a "BUILD_XMV" block in each case. The
interconnection is shown in Figure 4-20 (Function diagram for INS MV type conversion):

Configuring
4.4 Mapping example
Figure 4-20 Function diagram for INS MV type conversion
As in the previous example, the corresponding "Map" at the driver block must be adapted. The
two signals are mapped via "BSTR_MAP":
Figure 4-21 Mapping the device operating hours and switching cycles at the driver block
This mapping allows the two signals "OpHours" and "Switch count" to be displayed in the
faceplate.

Configuring
4.4 Mapping example
Figure 4-22 Faceplate with mapped device operating hours and switching cycles

Configuring
4.4 Mapping example

Blocks 5
5.1 General functionalities
5.1.1 Inputs
The inputs of the four driver blocks differ only slightly. All of them are therefore described in this
section. The description specifies whether a block is equipped with a specific input or not.
Input Type Description

Snd_Data STRUCT Interconnect with SnD_Data of the corresponding technological block -
PC_FEEDER, PC_LINE, PC_TRAFO, or PC_SYNC
Start_In ANY Interconnection with any bit or byte of an input module (section 4.3
(Page 13)).
SAM REAL Cycle time in seconds. It is assigned automatically.
Div_Cur DINT Current divisor (not SIP5_SYNC) (section 5.1.7 (Page 32))
Div_Vol DINT Voltage divisor (section 5.1.7 (Page 32))
Div_Pow DINT Power divisor (not SIP5_SYNC) (section 5.1.7 (Page 32))
Div_Freq DINT Frequency divisor (section 5.1.7 (Page 32))
Div_PF DINT cos φ divisor (not SIP5_SYNC) (section 5.1.7 (Page 32))
Div_Ang DINT Alpha angle divisor (SIP5_SYNC only) (section 5.1.7 (Page 32))
Div_Spa DINT Spare divisor (SIP5_SYNC only) (section 5.1.7 (Page 32))
Div_TAbs DINT Absolute temperature divisor (SIP5_TRAFO only) (section 5.1.7
(Page 32))
Div_TRel DINT Relative temperature divisor (SIP5_TRAFO only) (section 5.1.7 (Page 32))
EN_ROUND BOOL 1 = Rounds cos φ to two decimal places (not SIP5_SYNC)
CMD_LEN INT Commands are applied for at least CMD_LEN * 0.5 s. By default, CMD_LEN
= 3. (Section 5.1.4 (Page 31)).
Mod_Data STRUCT Contains address information of the configured SIPROTEC 5 modules. It is
interconnected automatically by the driver wizard (section 4.3 (Page 13)).
EN_MSG BOOL 1 = Unlock alarms
RAC_DIAG STRUCT Rack diagnostics of OB_DIAG. It is interconnected automatically by the
driver wizard (section 4.3 (Page 13)).
ALRM_MAP STRUCT Mapping - Alarms (section 5.1.3 (Page 28))
BSTR_MAP STRUCT Mapping - Counter values (section 5.1.3 (Page 28))
BOOL_MAP STRUCT Mapping - Bool (SIP5_SYNC only) (section 5.1.3 (Page 28))
CMD_MAP STRUCT Mapping - Commands (section 5.1.3 (Page 28))
DIAG_MAP STRUCT Mapping - Diagnostics (section 5.1.3 (Page 28))
MEAS_MAP STRUCT Mapping - Measured values (section 5.1.3 (Page 28))

Blocks
UN_kV REAL Rated voltage UN in kV. It is used to calculate the work based on count
pulses (section 5.1.8 (Page 33)).
IN_A REAL Rated current IN in A. It is used to calculate the work based on count pulses
(section 5.1.8 (Page 33)).
5.1.2 Outputs
The outputs of the four driver blocks differ only slightly. All of them are therefore described in this
section. The description specifies whether a block is equipped with a specific output or not.
Output Type Description

Rcv_Data STRUCT Interconnect with Rcv_Data of the corresponding technological
block - PC_FEEDER, PC_LINE, PC_TRAFO, or PC_SYNC
ERR_FB BOOL Error when calling RD_ SINFO (SFC6).
ERR_MAPA BOOL Incorrect mapping in "ALRM_MAP" (section 5.1.5 (Page 31)).
ERR_MAPB BOOL Incorrect mapping in "BSTR_MAP" (section 5.1.5 (Page 31)).
ERR_MAPBOOL BOOL Incorrect mapping in "BOOL_MAP" (section 5.1.5 (Page 31)). (Only
SIP5_SYNC)
ERR_MAPC BOOL Incorrect mapping in "CMD_MAP" (section 5.1.5 (Page 31)).
ERR_MAPD BOOL Incorrect mapping in "DIAG_MAP" (section 5.1.5 (Page 31)).
ERR_MAPM BOOL Incorrect mapping in "MEAS_MAP" (section 5.1.5 (Page 31)).
ERR_DEV BOOL 1 = Device error. It is set if one of the two diagnostic outputs "QVALID"
= 0 or "QDEVRDY" = 0.
QRACKF BOOL 1 = Rack error. It is determined by evaluating the structure input
"RAC_DIAG".
QDEVRDY BOOL 1 = Device ready. It is determined using the signal mapped by "DI‐
AG_MAP.Dev_Rdy".
QTEST STRUCT 1 = Test mode active. It is determined using the signal mapped by
"DIAG_MAP.Prot_Test".
QPROTECT STRUCT 1 = Protection function available. It is determined using the signal
mapped by "DIAG_MAP.Prot_On".
QVALID BOOL 1 = Valid device data. It is determined using the signal mapped by
"DIAG_MAP.Dat_Val".
5.1.3 Mapping
All data exchanged between SIPROTEC and PCS 7 is included in data packets that are cyclically
transferred via PROFINET. The mapping is used to determine which data this is and to which
address it is written.
The mapping in DIGSI 5 takes place via the "Communication assignment" mask (Figure 4-5
Mapping the diagnostics in DIGSI 5).
Mapping is performed in the driver block corresponding to the mapping at the SIPROTEC end.
This mapping is used to assign the data of the PROFINET data packets to the elements in the
block. This mapping is performed using various structure inputs on the block drivers:

Blocks
Name of structure I/O module (HW Config) Signal

ALRM_MAP Single message and double message Alarms and binary status displays
BOOL_MAP Single message Binary status displays
(SIP5_SYNC)
BSTR_MAP Counter values (exception: "OpTm" and Statistical values and counter val‐
"SwCount" are imported via measured ues
value modules)
CMD_MAP Double commands Commands
DIAG_MAP Single messages Status displays of the device
MEAS_MAP Measured values Measured values
Examples of mapping are described in section 4.4 (Page 14).

Section 7.1.5 in the SIPROTEC 5 Communication Protocols manual in the internet link (https://
support.industry.siemens.com/cs/ww/en/view/109742443) provides a very clear description of
the assignment of I/O modules to SIPROTEC 5 data objects.
5.1.3.1 Parameter changes in the mapping

Parameter changes of mapping structures become immediately active if they are made in the
test mode of the CFC editor. If the changes were made offline, the chart must be recompiled and
reloaded.
If a value is mapped in "ALRM_MAP", "BOOL_MAP", "BSTR_MAP", "CMD_MAP", or "DIAG_MAP",
and is set again to the default value "-1", the affected tags and outputs are automatically set to
0. The quality code is also set to "0x08: not connected" (does not apply to "DIAG_MAP").
The ALRM_MAP structure maps alarms and signals of SIPROTEC to the "Rcv_Data" structure of the
technological block. There is an element for each relevant signal in the technological block. The
sequence of the signals corresponds to the ALARM_8P groups or the message event IDs of the
alarms of the technological block.
The following objects are included, depending on the block:
• Protection device pick-ups (".._Str")
• Protection device trips (".._Op")
• General alarms
• Indicator bits of the parameter sets
• Remote/local control right ("Loc")
• Interlocking signals of the device ("QX_Ena...")
• User-definable alarms ("ALM_spX")
• Feedback of switches ("QX ")

Blocks
NOTICE
Double messages (e.g. feedback of switches) in SIPROTEC occupy two bits in the data
packet in PROFINET. Therefore, unlike the other values in ALRM_MAP, they are imported
by a double message module instead of a single message module. Depending on the
driver block, the last 4 or 8 elements in ALRM_MAP are interpreted as a double message.
The remaining elements are interpreted as a single message.
5.1.3.2 CMD_MAP
The CMD_MAP structure maps the commands of the technological blocks to the SIPROTEC
device. Similar to double messages, double commands occupy two bits in the SIPROTEC device.
All elements in CMD_MAP are interpreted as double command. PN driver blocks do not use single
command modules.
The following commands can be configured, depending on the block:
• Q0 (circuit breaker)
• Q1 (disconnector)
• Q2 (additional switch)
• Q8 (grounding switch)
• Q9 (additional switch)
• Freely configurable switches ("CmdX", "CmdX")
5.1.3.3 MEAS_MAP
The "MEAS_MAP" structure maps measured values to the technological block. They are imported
via measured value modules.
• Voltages ("U_X")
• Currents ("I_X")
• Frequency ("F")
• Power ("P","Q","S")
• Power factor cos phi ("PF")
• Other measured values Freely configurable measured values ("REAL_spx")
5.1.3.4 BSTR_MAP
The "BSTR_MAP" structure maps counter values to the technological block. With the exception
of "OpTm" and "SwCount", they are imported via counter value modules. "OpTm" and "SwCount"
are imported via measured value modules, since this requires a workaround (see section 4.4.3
(Page 22)).

Blocks

• Energy counter ("WpForward", "WqForward")
• Switching cycles ("SwCount")
• Operating hours ("OpTm")
• Freely configurable counter values of the double integer data type ("DINT_spX")
5.1.3.5 DIAG_MAP
The "DIAG_MAP" structure addresses status signals of the SIPROTEC device that are displayed in
block outputs (e.g., "QTEST") and used for status displays in WinCC.
The following status signals can be configured:
• Device status ("DEV_*")
• Status of protection and test function ("Prot_*")
• Valid device data ("Dat_Val")
5.1.4 Commands
Setting of the outputs is edge-triggered. The minimum duration of an edge is 0.5 s and can be
extended using the "CMD_LEN" input (duration = CMD_LEN x 0.5 s). Only one command can be
active at any given time to avoid unwanted states.
In the case of a rack or device error, all command outputs are set to 0.
5.1.5 Troubleshooting
The following configuration errors have been detected in the mapping structures "ALRM_MAP",
"BOOL_MAP", "BSTR_MAP", "CMD_MAP", "DIAG_MAP", and "MEAS_MAP":
• An element is assigned a higher value than is possible for the number of modules configured
in HW Config. (For example, 25 is assigned to an element in "MEAS_MAP", even though only
two "measured value 12" modules are configured)
• An element is assigned a higher value than the one intended by DIGSI for this type (e.g. PLC:
1 to 500, MV: 1 to 100)
In these cases, the block indicates an error at the corresponding output "ERR_MAPA",
"ERR_MAPBOOL", "ERR_MAPB", "ERR_MAPC", "ERR_MAPD", or "ERR_MAPM". The error is also
reported in the WinCC signaling system. The block continues to run as usual, and the quality
code of the incorrectly mapped element is set to "0x18: Incorrect configuration".
The other outputs for displaying errors are described in the following table:

ERR_FB BOOL Error when calling RD_ SINFO (SFC6).

Blocks
ERR_DEV BOOL 1 = Device error. It is set if one of the two diagnostic outputs
"QVALID" = 0 or "QDEVRDY" = 0.
QRACKF BOOL 1 = Rack error. It is determined by evaluating the structure
input "RAC_DIAG".
In the case of a rack or device error, the quality codes of all mapped signals (except diagnostics)
are set to "0x08: Not connected".
5.1.6 Diagnostic outputs

The driver blocks provide the following outputs for diagnostics:

QDEVRDY BOOL 1 = Device ready. It is determined using the signal mapped by
"DIAG_MAP.Dev_Rdy".
QTEST STRUCT 1 = Test mode active. It is determined using the signal map‐
ped by "DIAG_MAP.Prot_Test".
QPROTECT STRUCT 1 = Protection function available. It is determined using the
signal mapped by "DIAG_MAP.Prot_On".
QVALID BOOL 1 = Valid device data. It is determined using the signal map‐
ped by "DIAG_MAP.Dat_Val".
5.1.7 Divisor for measured values

"Div_*" inputs can be used to divide measured values and correct their size, if necessary. This
functionality is disabled by default because each "Div_*" input is preset to 1.
Input Measured Signals affected

value
Div_Cur Current I_A, I_B, I_C, I1_A, I1_B, I1_C, I2_A, I2_B, I2_C, I3_A, I3_B,
I3_C, IDIFFL1, IDIFFL2, IDIFFL3, IDIFF3I0, IRESTL1, IRESTL2,
IRESTL3, I30
Div_Vol Voltage U, U_A, U_B, U_C, U_AB, U_BC, U_CA, P1_U1, P1_U2, P2_U1,
…, P1_DU, …
Div_Pow Power P, Q, S (not SIP5_SYNC)
Div_Freq Frequency F, P1_F1, P1_F2, P2_F1, …, P1_DF, …
Div_PF cos phi PF
Div_Ang DINT P1_DANG, P2_DANG, …
Div_Spa - REAL_sp1, REAL_sp2, …
Div_TAbs Temperature THETA_L1, THETA_L2, THETA_L3
Div_TRel Temperature THETA

Blocks
5.1.8 Converting energy pulses

The blocks SIP5_FEEDER and SIP5_TRAFO internally calculate energy values from the number of
energy pulses transmitted by the SIPROTEC 5 device. In order for the energy values to be
calculated correctly, the respective elements must be mapped correctly in "BSTR_MAP", and
rated voltage/rated current must be specified at the block inputs UN_kV and IN_A.
The calculation is performed using the following formula:
Identifier Unit Data type Value Explanation

Wx kWh DINT Energy value
UN_kV kV REAL Input UN_kV – rated voltage
IN_A A REAL Input IN_A – rated current
Imp_h CONST 60000 Pulses per hour
Imp_r DINT Pulses transmitted by the device
The formula is used to calculate the following values:

• WpForward – output active energy
• WqForward – output reactive energy
• WpReverse – obtained active energy
• WqReverse – obtained reactive energy
5.1.9 System functions used

The PROFINET driver blocks use the following system blocks of PCS 7:
• ALARM_8P (SFB35)
• RD_SINFO (SFC6)
• READ_CLK (SFC1)
• TIME_TCK (SFC64)
5.1.10 Initialization following hardware change

If the configuration of the SIPROTEC 5 device in HW Config has been changed by adding/deleting
modules, it is sufficient to compile the changes (incl. "Generate module drivers") and load them
into the CFC editor for the changes to take effect. Driver blocks detect the change at the
"Mod_Data" input and reinitialize themselves. Of course, HW Config must also be compiled and
loaded beforehand.

Blocks
5.5 SIP5_SYNC
5.2 SIP5_FEEDER
The block serves as a driver block for the transmission of data packets between a SIPROTEC 5
device and PCS 7. It also forms an interface to the technological block PC_FEEDER.
Since the functions of the four driver blocks are very similar, they are described in general in
section 5.1 (Page 27).
5.3 SIP5_Line
device and PCS 7. It also forms an interface to the technological block PC_LINE.
5.4 SIP5_TRAFO
device and PCS 7. It also forms an interface to the technological block PC_TRAFO.
5.5 SIP5_SYNC
device and PCS 7. It also forms an interface to the technological block PC_SYNC.


Profinet Driver en

Uploaded by

Copyright:

Available Formats

Profinet Driver en

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Profinet Driver en

Uploaded by

Copyright:

Available Formats

Security information 1

Programming and Operating Manual

Siemens AG A5E51115894-AA Copyright © Siemens AG 2021.

PROFINET driver blocks SIPROTEC 5

PROFINET driver blocks SIPROTEC 5

PROFINET driver blocks SIPROTEC 5

PROFINET driver blocks SIPROTEC 5

PROFINET driver blocks SIPROTEC 5

Figure 2-1 Driver block (1) and technological block (2)

2.2 Overview of blocks

Name FB No Technological block (PCL)

PROFINET driver blocks SIPROTEC 5

PROFINET driver blocks SIPROTEC 5

PROFINET driver blocks SIPROTEC 5

4.1 Configuration in DIGSI 5

Note the following in regard to communication with PowerControl:

4.2 Hardware configuration in HW Config

To configure a SIPROTEC device in HW Config, it must be connected to the PROFINET IO system

PROFINET driver blocks SIPROTEC 5

Figure 4-1 Hardware configuration

Name Type Number of signals Mapping on the driver block using

PROFINET driver blocks SIPROTEC 5

4.3 Installation and interconnection of the driver blocks in CFC

PROFINET driver blocks SIPROTEC 5

Figure 4-3 Compile CFC with "Generate module drivers"

4.4 Mapping example

PROFINET driver blocks SIPROTEC 5

Figure 4-4 Faceplate without mapping

PROFINET driver blocks SIPROTEC 5

Figure 4-5 Mapping the diagnostics in DIGSI 5

PROFINET driver blocks SIPROTEC 5

Figure 4-6 Mapping the diagnostics on the driver block

PROFINET driver blocks SIPROTEC 5

Figure 4-7 Faceplate with mapped device and protection status

4.4.2 Circuit breaker - interlock, switching command and feedback

Figure 4-8 Mapping interlocks in DIGSI

PROFINET driver blocks SIPROTEC 5

Figure 4-9 Mapping a switching command in DIGSI

Figure 4-10 Mapping the feedback of a circuit breaker in DIGSI

Figure 4-11 Mapping a switching command at the driver block png

Figure 4-12 Mapping interlocks at the driver block

PROFINET driver blocks SIPROTEC 5

The switching command is mapped via "CMD_MAP":

PROFINET driver blocks SIPROTEC 5

Figure 4-14 Faceplate with controllable CB circuit breaker

Path in DIGSI Map + element to be mapped

PROFINET driver blocks SIPROTEC 5

4.4.3 Device operating hours and switching cycles

Figure 4-15 Signal for switching cycle in DIGSI 5

Figure 4-16 Signal for device operating hours in DIGSI 5

Therefore, both signals must be converted to an auxiliary signal of an interconnectable type

Figure 4-17 Adding a new signal

PROFINET driver blocks SIPROTEC 5

Figure 4-18 Creating the "Device operating hours MV" signal

Figure 4-19 Newly created auxiliary signals

PROFINET driver blocks SIPROTEC 5

Figure 4-20 Function diagram for INS MV type conversion

PROFINET driver blocks SIPROTEC 5

PROFINET driver blocks SIPROTEC 5