PROFIBUS DP DRIVER en
PROFIBUS DP DRIVER en
System requirements 2
Configuring 3
SIMATIC
Blocks 4
PCS 7 Process Control System
PROFIBUS DP driver blocks 5
Signal defaults
Example of alarm
configuration 6
Programming and Operating Manual
08/2021
A5E51115892-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.
1 Introduction ........................................................................................................................................... 7
1.1 Environment........................................................................................................................ 7
1.1.1 Hardware............................................................................................................................. 7
1.1.2 Software.............................................................................................................................. 8
1.2 Overview of blocks............................................................................................................... 9
2 System requirements........................................................................................................................... 11
2.1 Hardware........................................................................................................................... 11
2.2 Software............................................................................................................................ 11
3 Configuring .......................................................................................................................................... 13
3.1 Configuration of the SIPROTEC device in DIGSI ................................................................... 13
3.2 Hardware configuration in HW Config ................................................................................. 13
3.2.1 Integrating the GSD file ...................................................................................................... 13
3.2.2 Insertion of DP slave in the DP master system ..................................................................... 14
3.2.3 Insertion of input and output modules ............................................................................... 16
3.2.4 Assignment of symbolic names for inputs and outputs ....................................................... 19
3.3 Insertion and interconnection of the driver blocks in CFC.................................................... 20
3.3.1 Insertion in a cyclic interrupt OB......................................................................................... 20
3.3.2 Configuration of the input and output addresses ................................................................ 20
3.3.3 Connection to the technological block................................................................................ 23
3.3.4 Signal configuration ........................................................................................................... 23
4 Blocks................................................................................................................................................... 25
4.1 General functionalities ....................................................................................................... 25
4.1.1 Mapping ............................................................................................................................ 25
4.1.1.1 Parameter changes in the mapping .................................................................................... 28
4.1.1.2 ALRM_MAP ........................................................................................................................ 28
4.1.1.3 CMD_MAP ......................................................................................................................... 30
4.1.1.4 MEAS_MAP ........................................................................................................................ 31
4.1.1.5 BSTR_MAP ......................................................................................................................... 31
4.1.1.6 DIAG_MAP ......................................................................................................................... 31
4.1.2 Device status in the faceplate............................................................................................. 32
4.1.3 Factors for analog values.................................................................................................... 33
4.1.4 Transmission of alarms....................................................................................................... 34
4.1.5 Transfer and adjustment of time stamps............................................................................. 35
4.1.6 System functions used ....................................................................................................... 35
4.2 7SJ6X_FEEDER - FB 2580.................................................................................................... 36
4.2.1 7SJ6X_FEEDER ................................................................................................................... 36
4.2.2 GSD file.............................................................................................................................. 36
4.2.3 Interfaces_7SJ6X ............................................................................................................... 36
4.2.4 Conversion of the energy pulses......................................................................................... 37
4.2.5 I/O list................................................................................................................................ 37
4.2.5.1 Inputs................................................................................................................................ 37
4.2.5.2 Outputs ............................................................................................................................. 49
4.3 7SAX_LINE - FB 2581 ......................................................................................................... 50
4.3.1 7SAX_LINE......................................................................................................................... 50
4.3.2 GSD file.............................................................................................................................. 50
4.3.3 Interfaces_7SAX................................................................................................................. 51
4.3.4 I/O list................................................................................................................................ 51
4.3.4.1 Inputs................................................................................................................................ 51
4.3.4.2 Outputs ............................................................................................................................. 59
4.4 7SDX_LINE - FB 2582 ......................................................................................................... 60
4.4.1 7SDX_LINE......................................................................................................................... 60
4.4.2 GSD file.............................................................................................................................. 60
4.4.3 Interfaces_7SDX ................................................................................................................ 61
4.4.4 I/O list................................................................................................................................ 61
4.4.4.1 Inputs................................................................................................................................ 61
4.4.4.2 Outputs ............................................................................................................................. 69
4.5 7SJK80_FEEDER - FB 2583.................................................................................................. 70
4.5.1 7SJK80_FEEDER ................................................................................................................. 70
4.5.2 GSD file.............................................................................................................................. 70
4.5.3 Interfaces_7SJK80 ............................................................................................................. 71
4.5.4 Conversion of the energy pulses......................................................................................... 71
4.5.5 I/O list................................................................................................................................ 72
4.5.5.1 Inputs................................................................................................................................ 72
4.5.5.2 Outputs ............................................................................................................................. 87
4.6 7UM62_FEEDER - FB 2584.................................................................................................. 88
4.6.1 7UM62_FEEDER ................................................................................................................. 88
4.6.2 GSD file.............................................................................................................................. 88
4.6.3 Interfaces_7UM62 ............................................................................................................. 89
4.6.4 Conversion of the energy pulses......................................................................................... 89
4.6.5 I/O list................................................................................................................................ 90
4.6.5.1 Inputs................................................................................................................................ 90
4.6.5.2 Outputs ........................................................................................................................... 105
4.7 7UT612_TRAFO - FB 2585 ................................................................................................ 106
4.7.1 7UT612_TRAFO ............................................................................................................... 106
4.7.2 GSD file............................................................................................................................ 106
4.7.3 Interfaces_7UT612 .......................................................................................................... 107
4.7.4 Conversion of the energy pulses....................................................................................... 107
4.7.5 I/O list.............................................................................................................................. 108
4.7.5.1 Inputs.............................................................................................................................. 108
4.7.5.2 Outputs ........................................................................................................................... 116
4.8 7VE6X_SYNC - FB 2586 .................................................................................................... 116
4.8.1 7VE6X_SYNC ................................................................................................................... 116
4.8.2 GSD file............................................................................................................................ 117
4.8.3 Interfaces_7VE6X............................................................................................................. 117
4.8.4 I/O list.............................................................................................................................. 117
4.8.4.1 Inputs.............................................................................................................................. 117
4.8.4.2 Outputs ........................................................................................................................... 131
4.9 7UT6X_TRAFO - FB 2587 .................................................................................................. 132
4.9.1 7UT6X_TRAFO ................................................................................................................. 132
The PROFIBUS DP driver blocks for PowerControl form the interface between SIPROTEC
protection devices with a PROFIBUS connection 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 is to be used in conjunction with the PCL documentation and requires knowledge
of this documentation.
1.1 Environment
1.1.1 Hardware
The PROFIBUS driver blocks operate together with the technological blocks of the PCL in the
SIMATIC PCS 7 automation system (e.g., S7-400). They access the data of the devices connected
to PROFIBUS via the process input image of the CPU and write commands via the process output
image of the CPU. A redundant PROFIBUS configuration using an S7-400H system and Y-link is
also possible.
The figure below shows the hardware configuration of a singular and a redundant configuration:
PCS 7 ES PCS 7 ES
PCS 7 OS PCS 7 OS
SIPROTEC SIPROTEC
Clients Clients
Digsi Digsi
Power Control
Library (PCL)
S7-400H
S7-400
PROFIBUS DP
Driver Blocks
SIPROTEC Y-Link
Devices
PROFIBUS DP PROFIBUS DP
1.1.2 Software
The PROFIBUS DP driver blocks for PowerControl are configured in the user program of the
automation system with the help of 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 connection of
a driver block to multiple technological blocks is not possible.
In addition, every driver block is developed specifically for a PROFIBUS DP mapping. The DIGSI
software must be used to assign parameters for this mapping in the SIPROTEC device.
The screenshot below shows a CFC with a driver block and a technological block:
Note
To use the PROFIBUS driver blocks, the following values need to be configured correctly:
• "FACTOR_E" input of the PC_FEEDER is set to 1 (No calculations)
• UN_kV, IN_A should be configured as per the used IED
The table below shows all available PROFIBUS DP driver blocks with their respective PROFIBUS
mappings and matching technological blocks:
Siprotec devices:
Other devices:
2.2 Software
The PROFIBUS DP driver blocks have been released for the following PCS 7 versions:
• PCS 7 Version 9.1
The following GSD file is used to connect the SIPROTEC devices via an optical connection:
As soon as the GSD file is integrated in HW Config, the DP slave "SIPROTEC4 DP-Modul_HWRev4"
or "SIPROTEC4 DP-Fibre" appears in the hardware catalog under the following path:
"PROFIBUS DP / Additional Field Devices / General /SIPROTEC".
To update the information in the hardware catalog, select the menu command Options >
Update Catalog.
The table below shows the modules required for the individual devices:
SIPROTEC de‐ PROFIBUS DP map‐ Number of input Number of out‐ Modules in HW Config
vice ping bytes put bytes
7SJ6X 3.5 100 8 4x "Input – 16 bytes"
(slot 1-4)
1x "Input – 4 bytes"
(slot 5)
1x "Input – 16 words"
(slot 6)
1x "Output – 8 bytes"
(slot 7)
7SA522, 7SA6 3.2 100 6 4x "Input – 16 bytes"
(slot 1-4)
1x "Input – 4 bytes"
(slot 5)
1x "Input – 16 words"
(slot 6)
1x "Output – 6 bytes"
(slot 7)
7SD5, 7SD610 3.2 82 6 3x "Input – 16 bytes"
(slot 1-3)
1x "Input – 2 bytes"
(slot 4)
1x "Input – 16 words"
(slot 5)
1x "Output – 6 bytes"
(slot 6)
7SJ80, 7SK80 3.2 100 8 4x "Input – 16 bytes"
(slot 1-4)
1x "Input – 4 bytes"
(slot 5)
1x "Input – 16 words"
(slot 6)
1x "Output – 8 bytes"
(slot 7)
7UM62 3.4 100 8 4x "Input – 16 bytes"
(slot 1-4)
1x "Input – 4 bytes"
(slot 5)
1x "Input – 16 words"
(slot 6)
1x "Output – 8 bytes"
(slot 7)
SIPROTEC de‐ PROFIBUS DP map‐ Number of input Number of out‐ Modules in HW Config
vice ping bytes put bytes
7UT612 3.2 92 4 3x "Input – 16 bytes"
(slot 1-3)
1x "Input – 12 bytes"
(slot 4)
1x "Input – 16 words"
(slot 5)
1x "Output – 4 bytes"
(slot 6)
7VE61, 7VE63 3.3 76 16 2x "Input – 16 bytes"
(slot 1-2)
1x "Input – 12 bytes"
(slot 3)
1x "Input – 16 words"
(slot 4)
1x "Output – 16 bytes"
(slot 5)
7UT613, 3.2 100 6 6x "Input – 16 bytes"
7UT633, (slot 1-6)
7UT635 1x "Input – 4 bytes"
(slot 7)
1x "Output – 6 bytes"
(slot 8)
6MD662-664 3.1 100 14 2x "Input – 16 bytes"
(slot 1-2)
1x "Input – 14 bytes"
(slot 3)
1x "Input – 16 words"
(slot 4)
1x "Output – 14 bytes"
(slot 5)
The block reads and writes not only the interconnected bit, but also the entire area occupied by
the device in the image of the process data. The interconnection of "VALUE_I" and "VALUE_O" is
used only for addressing the assigned area in the process image.
If you have identified the addresses with names (symbols), you can make the interconnections
with the CFC function "Interconnection to Address...".
When the CFC is compiled with the setting "Generate module drivers", CFC writes the addresses
of the interconnected process data to the block and connects the "EN", "RACKF", "SUBN1ERR",
and "SUBN2ERR" inputs to an automatically generated "OB_DIAG1" block, which monitors the
assigned device on PROFIBUS.
The "PCS 7 Basis Library V80" setting is required for generating module drivers when compiling
with CFC.
The PCS 7 library used can be set under "Module driver settings".
An incorrect interconnection of the "VALUE_I" input or "VALUE_O" output produces a warning
when compiling in CFC and an indication of an error when generating drivers.
NOTICE
Incorrect addressing in the process image
If CFCs that have been compiled with a warning related to driver generation are downloaded
to a CPU, this may lead to incorrect addressing in the process image.
Note
The compilation in CFC with activated "Generate module drivers" function is controlled by
special XML files for the PROFIBUS driver blocks.
After their installation, the XML files are located in the PCS 7 system under:
"C:\Program Files\SIEMENS\STEP7\S7DATA\driver"
PROFIBUS DB
driver block
PCL block
Note
To use the PROFIBUS driver blocks, the following values need to be configured correctly:
• "FACTOR_E" input of the PC_FEEDER is set to 1 (No calculations)
• UN_kV, IN_A should be configured as per the used IED
4.1.1 Mapping
All data exchanged between SIPROTEC and PCS 7 are included in data packets that are cyclically
transferred via the PROFIBUS.
These cyclic data packets are described in the standard mapping. Various standard mappings can
be configured in each SIPROTEC device.
The driver blocks support only one standard mapping in each case, which must be set in the
device.
Within each mapping, it is possible to configure additional signals in free areas of the mapping
with the help of DIGSI.
Mapping is performed in the driver block identical to the mapping at the SIPROTEC end. The data
of the PROFIBUS data packets are assigned to the elements in the block with this mapping. This
mapping is made using various structure inputs on the block drivers.
There is one input for each data type:
Within the structure inputs, there is a "ByteOffs" parameter and a "BitOffs" parameter for each
signal.
These parameters in the mapping structures describe the position of a data point in the
PROFIBUS data packet. "ByteOffs" designates the byte number in the packet, and "BitOffs" the bit
number.
The smallest possible value for an offset is "0". The value range for "BitOffs" is "0" to "7".
The "BitOffs" parameter only exists in the structures for mapping of binary values.
The value "-1" means that the corresponding element is not initialized when it is passed to the
"PC_FEEDER" block. In this case, the quality code (ST) of the element contains the value "0",
which means "not defined".
For all data points specified in the respective standard mapping, "Byte Offs" and "BitOffs" are
already pre-assigned with the appropriate values.
Example: "Offset 6 / 5" in the mapping description corresponds to "ByteOffset=6", "BitOffset=5".
Note
In DIGSI, the bit position is not specified with a bit number from "0" to "7", but instead with a mask
in hexadecimal notation.
Example: "BitOffset 5" corresponds to mask "20(hex)".
Notation in DIGSI: 2 0
20(hex)
Binary: 0010 0000
Bit number BitOffs: 7654 3210
When activating the mapping structures "ALRM_MAP", "CMD_MAP" and "DIAG_MAP" any
existing formal configuration errors are detected. The block displays an error in the data of these
mapping structures in the outputs "ERR_MAPA", "ERR_MAPC" and "ERR_MAPD". The OR logic
operation of these configuration error displays is signaled as alarm to WinCC.
4.1.1.2 ALRM_MAP
The "ALRM_MAP" structure maps alarms and signals of PROFIBUS to the "Rcv_Data" structure for
the technological block.
An element exists 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.
This means all alarms that can be freely assigned or modified are named "EVIDX_SY". The X
stands for the alarm group and the Y for the corresponding signal.
This naming convention makes it easier to assign the signal at the driver block to the
corresponding alarm text at the technological block.
The following objects are included:
• Protection device pick-ups (".._Str")
• Protection device trips (".._Op")
• General alarms
• Condition code 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_ON", "QX_OFF")*
*Only for driver blocks with connection to the "PC_FEEDER"/"PC_FEEDER_2CB" technological
object
Double messages (e.g., feedback of switches) in SIPROTEC occupy two bits in the data
packet on PROFIBUS. The "ALRM_MAP" structure therefore has two elements for mapping
of one bit each.
Two offset values are specified for the signal in the description of the standard mapping 3-5: "Q0
OFF: 0 / 0" and "Q0 ON: 0 / 1".
The corresponding elements in "ALRM_MAP" are "Q0_ON" and "Q0_OFF". They are assigned to
the signals in the PROFIBUS data packet with the following parameter assignment:
4.1.1.3 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.
The "CMD_MAP" structure therefore has two elements for mapping of one bit each. You can
assign the offset values of a bit with "-1" and thereby disable them.
The following commands can be configured:
• Q0 (power switch)*
• Q1 (disconnector)*
• Q2 (additional switch)*
• Q8 (grounding switch)*
• Q9 (additional switch)*
• Freely-configurable switches ("CmdX_ON", "CmdX_OFF")
*Only for driver blocks with connection to the "PC_FEEDER" technological object
4.1.1.4 MEAS_MAP
The "MEAS_MAP" structure maps measured values for the technological block. They are
transmitted as data words or double words.
The "BitOffs" parameter is omitted because it must always be zero.
The following data points are contained:
• 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")
4.1.1.5 BSTR_MAP
The "BSTR_MAP" structure maps counter values for the technological block. They are transmitted
as data words or double words. The "BitOffs" parameter is omitted because it must always be
zero.
The following data points are contained:
• Energy counter ("WpForward", "WqForward"…)
• Operating cycles ("SwCount")
• Operating hours ("OpTm")
• Freely-configurable counter values of the Integer data type ("INT_spX")
• Freely-configurable counter values of the Double Integer data type ("DINT_spX")
4.1.1.6 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. A status signal ("ByteOffset
= -1") that is not configured is replaced in the S7 block with the value in good state or normal
state.
The following status signals can be configured:
• "DEV_RDY" : Device ready, startup complete
• "TEST" : Test mode is active
• "PROTECT" : At least one protection function is in effect
• "DAT_VAL" : The DP Interface transmits valid device data.
The device status is displayed by means of four indicators in standard view in the faceplate:
Protection
This field only shows a valid value if "DATA_VAL = 1" and "DEV_RDY = 1". Otherwise "N/A" is
displayed.
Switch permission
The switch control follows the Loc variable:
"Loc = 1" -> Local
"Loc = 0" -> Remote
Measured values are transmitted in the PROFIBUS data packet as an integer value with 16 bits.
In the SIPROTEC device and in the technological blocks, measured values have the "REAL" data
type. For this reason, the measured values must be adapted using divisors before and after their
transfer via PROFIBUS.
In doing so, the measured values in the driver block are divided by the same value they are
multiplied by in SIPROTEC.
The following divisors can be configured in the driver blocks:
The technological blocks of the PCL contain Message Event IDs for alarm generation.
The alarm type and the texts of the alarms are defined in the technological blocks.
The alarms that are sent to WinCC are assigned to the technological blocks in WinCC.
The Alarm_8P call occurs in the driver block with the Message Event ID of the technological
object.
Snd_Data
No alarm _8P call
Reading out
MSG_EVID is generated
MSG_EVIDx from the
here and
Snd_data structure MSG_EVIDx alarm texts are
defined here
The PROFIBUS data packets exchanged between the SIPROTEC device and the driver block, use
a handshake method to transfer alarms from the alarm buffer of the SIPROTEC device.
The driver block sends the message with time stamp from the SIPROTEC device to WinCC.
A message is not deleted from the buffer of SIPROTEC until it could be passed to WinCC. If the
SIPROTEC device is operated without WinCC connected, the message buffer in the SIPROTEC
device may overflow.
The use of the message buffer also enables transmission of a fast signal change with the time
stamp of SIPROTEC to WinCC.
If signals are transmitted without the message buffer, the driver block acquires these signals
cyclically with a cycle time of at least 0.5 seconds, even if the driver block is called in shorter
cycles.
If a signal change is detected at the driver block, it sends the associated alarm of an "ALARM_8P"
block with its own current time of day to WinCC. Fast signal changes within a cycle may be lost
with this procedure. The technological blocks of the PCL contain Message Event IDs for alarm
generation.
The PowerControl Profibus driver blocks use time stamps for the alarms and messages of the
SIPROTEC device. These time stamps are generated directly in the protection device and
transferred via Profibus. Using the ALARM_8P block, the time stamps are then transferred to the
OS and are also displayed in WinCC Alarm Logging.
By default, the automation system in a PCS 7 system is set in such a way that the internal system
time corresponds to the UTC time zone. In contrast, the SIPROTEC devices are usually
configured with the local time zone, so the display shows the correct time on location. Even if
time synchronization via Profibus is configured, the local time is transferred.
To avoid discrepancies between the time stamps of the automation system and of the SIPROTEC
devices in the OS, the driver blocks adjust the time stamps from the protection devices to the UTC
time. A system register of the automation system which contains the difference between UTC
and the local time zone is used for this purpose. This difference is then calculated with the time
stamp of the protection device.
If the SIPROTEC device does not make a time stamp available for a message, the time of the
automation system is used (UTC time).
The adjustment of the time stamp can be disabled by setting the "UTC" input to "1". This is
necessary, for example, if the SIPROTEC devices are configured to UTC time.
The PROFIBUS DP driver blocks use the following system blocks of PCS 7:
• ALARM_8P (SFB35)
• RD_SINFO (SFC6)
• READ_CLK (SFC1)
• TIME_TCK (SFC64)
• RDSYSST (SFC51)
4.2.1 7SJ6X_FEEDER
The block serves as driver block for the transmission of data packets between a SIPROTEC device
and PCS 7 and forms an interface to the technology block PC_FEEDER.
It supports standard mapping 3.5 and transfers messages from the incoming data packets to
WinCC.
More detailed information on the functionality of the driver blocks is available under General
functionalities (Page 25).
See also
GSD file (Page 36)
The following GSD file is used to connect the SIPROTEC devices via an optical connection:
4.2.3 Interfaces_7SJ6X
The "7SJ6X_FEEDER" block uses the following data structures (UDTs) as interface to the FB
"PC_FEEDER":
• UDT FEEDER_RCV
• UDT FEEDER_SND
The block performs an internal calculation of the energy values from the number of energy
pulses transmitted by the device, where the values of the UN_kV and IN_A parameters must be
specified via the corresponding input parameters of the block.
The calculation is carried out using the following formula:
The calculated energy values are output in the following structure elements of the block I/O
Rcv_Data:
Designation Description
WpForward Output active energy
WqForward Output reactive energy
WpReverse Received active energy
WqReverse Received reactive energy
4.2.5.1 Inputs
4.2.5.2 Outputs
4.3.1 7SAX_LINE
The block serves as driver block for the transmission of data packets between a SIPROTEC device
and PCS 7 and forms an interface to the technology block PC_LINE.
It supports standard mapping 3.2 and transfers messages from the incoming data packets to
WinCC.
More detailed information on the functionality of the driver blocks is available under General
functionalities (Page 25).
The following GSD file is used to connect the SIPROTEC devices via an optical connection:
4.3.3 Interfaces_7SAX
The "7SAX_LINE" block uses the following data structures (UDTs) as interface to the FB "PC_LINE":
• UDT LINE_RCV
• UDT LINE_SND
4.3.4.1 Inputs
4.3.4.2 Outputs
4.4.1 7SDX_LINE
The block serves as driver block for the transmission of data packets between a SIPROTEC device
and PCS 7 and forms an interface to the technology block PC_LINE.
It supports standard mapping 3.2 and transfers messages from the incoming data packets to
WinCC.
More detailed information on the functionality of the driver blocks is available under General
functionalities (Page 25).
The following GSD file is used to connect the SIPROTEC devices via an optical connection:
4.4.3 Interfaces_7SDX
The "7SDX_LINE" block uses the following data structures (UDTs) as interface to the FB "PC_LINE":
• UDT LINE_RCV
• UDT LINE_SND
4.4.4.1 Inputs
4.4.4.2 Outputs
4.5.1 7SJK80_FEEDER
The block serves as driver block for the transmission of data packets between a SIPROTEC device
and PCS 7 and forms an interface to the technology block PC_FEEDER.
It supports standard mapping 3.2 and transfers messages from the incoming data packets to
WinCC.
More detailed information on the functionality of the driver blocks is available under General
functionalities (Page 25).
The following GSD file is used to connect the SIPROTEC devices via an optical connection:
4.5.3 Interfaces_7SJK80
The "7SJK80_FEEDER" block uses the following data structures (UDTs) as interface to the FB
"PC_FEEDER":
• UDT FEEDER_RCV
• UDT FEEDER_SND
The block performs an internal calculation of the energy values from the number of energy
pulses transmitted by the device, where the values of the UN_kV and IN_A parameters must be
specified via the corresponding input parameters of the block.
The calculation is carried out using the following formula:
The calculated energy values are output in the following structure elements of the block I/O
Rcv_Data:
Designation Description
WpForward Output active energy
WqForward Output reactive energy
WpReverse Received active energy
WqReverse Received reactive energy
4.5.5.1 Inputs
4.5.5.2 Outputs
4.6.1 7UM62_FEEDER
The block serves as driver block for the transmission of data packets between a SIPROTEC device
and PCS 7 and forms an interface to the technology block PC_FEEDER.
It supports standard mapping 3.4 and transfers messages from the incoming data packets to
WinCC.
More detailed information on the functionality of the driver blocks is available under General
functionalities (Page 25).
The following GSD file is used to connect the SIPROTEC devices via an optical connection:
4.6.3 Interfaces_7UM62
The "7UM62_FEEDER" block uses the following data structures (UDTs) as interface to the FB
"PC_FEEDER":
• UDT FEEDER_RCV
• UDT FEEDER_SND
The block performs an internal calculation of the energy values from the number of energy
pulses transmitted by the device, where the values of the UN_kV and IN_A parameters must be
specified via the corresponding input parameters of the block.
The calculation is carried out using the following formula:
The calculated energy values are output in the following structure elements of the block I/O
Rcv_Data:
Designation Description
WpForward Output active energy
WqForward Output reactive energy
WpReverse Received active energy
WqReverse Received reactive energy
4.6.5.1 Inputs
4.6.5.2 Outputs
4.7.1 7UT612_TRAFO
The block serves as driver block for the transmission of data packets between a SIPROTEC device
and PCS 7 and forms an interface to the technology block PC_TRAFO.
It supports standard mapping 3.2 and transfers messages from the incoming data packets to
WinCC.
More detailed information on the functionality of the driver blocks is available under General
functionalities (Page 25).
The following GSD file is used to connect the SIPROTEC devices via an optical connection:
4.7.3 Interfaces_7UT612
The "7UT612_TRAFO" block uses the following data structures (UDTs) as interface to the FB
"PC_TRAFO":
• UDT TRAFO_RCV
• UDT TRAFO_SND
The block performs an internal calculation of the energy values from the number of energy
pulses transmitted by the device, where the values of the UN_kV and IN_A parameters must be
specified via the corresponding input parameters of the block.
The calculation is carried out using the following formula:
The calculated energy values are output in the following structure elements of the block I/O
Rcv_Data:
Designation Description
WpForward Output active energy
WqForward Output reactive energy
WpReverse Received active energy
WqReverse Received reactive energy
4.7.5.1 Inputs
4.7.5.2 Outputs
4.8.1 7VE6X_SYNC
The block serves as driver block for the transmission of data packets between a SIPROTEC device
and PCS 7 and forms an interface to the technology block PC_SYNC.
It supports standard mapping 3.3 and transfers messages from the incoming data packets to
WinCC.
More detailed information on the functionality of the driver blocks is available under General
functionalities (Page 25).
The following GSD file is used to connect the SIPROTEC devices via an optical connection:
4.8.3 Interfaces_7VE6X
The "7VE6X_SYNC" block uses the following data structures (UDTs) as interface to the FB
"PC_SYNC":
• UDT SYNC_RCV
• UDT SYNC_SND
4.8.4.1 Inputs
4.8.4.2 Outputs
4.9.1 7UT6X_TRAFO
The block serves as driver block for the transmission of data packets between a SIPROTEC device
and PCS 7 and forms an interface to the technology block PC_TRAFO.
It supports standard mapping 3.2 and transfers messages from the incoming data packets to
WinCC.
More detailed information on the functionality of the driver blocks is available under General
functionalities (Page 25).
The following GSD file is used to connect the SIPROTEC devices via an optical connection:
4.9.3 Interfaces_7UT6X
The "7UT6X_TRAFO" block uses the following data structures (UDTs) as interface to the FB
"PC_TRAFO":
• UDT TRAFO_RCV
• UDT TRAFO_SND
The block performs an internal calculation of the energy values from the number of energy
pulses transmitted by the device, where the values of the UN_kV and IN_A parameters must be
specified via the corresponding input parameters of the block.
The calculation is carried out using the following formula:
The calculated energy values are output in the following structure elements of the block I/O
Rcv_Data:
Designation Description
WpForward Output active energy
WqForward Output reactive energy
WpReverse Received active energy
WqReverse Received reactive energy
4.9.5.1 Inputs
4.9.5.2 Outputs
4.10.1 6MD66X_FEEDER
The block serves as driver block for the transmission of data packets between a SIPROTEC device
and PCS 7 and forms an interface to the technology block PC_FEEDER.
It supports standard mapping 3.1 and transfers messages from the incoming data packets to
WinCC.
More detailed information on the functionality of the driver blocks is available under General
functionalities (Page 25).
The following GSD file is used to connect the SIPROTEC devices via an optical connection:
4.10.3 Interfaces_6MD66X
The "6MD66X_FEEDER" block uses the following data structures (UDTs) as interface to the FB
"PC_FEEDER":
• UDT FEEDER_RCV
• UDT FEEDER_SND
The block performs an internal calculation of the energy values from the number of energy
pulses transmitted by the device, where the values of the UN_kV and IN_A parameters must be
specified via the corresponding input parameters of the block.
The calculation is carried out using the following formula:
The calculated energy values are output in the following structure elements of the block I/O
Rcv_Data:
Designation Description
WpForward Output active energy
WqForward Output reactive energy
WpReverse Received active energy
WqReverse Received reactive energy
4.10.5.1 Inputs
4.10.5.2 Outputs
4.11.1 Introduction
The block serves as driver block for the transmission of data packets between a SIPROTEC device
and PCS 7 and forms an interface to the technology block PC_FEEDER.
It supports standard mapping 3.2 and transfers messages from the incoming data packets to
WinCC.
More detailed information on the functionality of the driver blocks is available under General
functionalities (Page 25).
The following GSD file is used to connect the SIPROTEC devices via an optical connection:
4.11.3 Interfaces_7SAX
The "7SAX_FEEDER" block uses the following data structures (UDTs) as interface to the FB
"PC_FEEDER":
• UDT FEEDER_RCV
• UDT FEEDER_SND
4.11.4.1 Inputs
4.11.4.2 Outputs
4.12.1 Introduction
The SENTRON_FEEDER block allows you to connect a SENTRON 3WL/3VL device via PROFIBUS DP
to the Power Control Library, PCL. The PC_FEEDER block is used as a technological object.
Note
The "Circuit Breakers with Communication Capabilities Sentron 3WL and Sentron 3VL
Profibus" system manual provides the basis for using the Profibus driver block. This
manual describes the integration of the device in HW Config. Cyclic data exchange is used
as the communication type.
4.12.2 Interfaces_SENTRON
The "SENTRON_FEEDER" block uses the following data structures (UDTs) as interface to the FB
"PC_FEEDER":
• UDT FEEDER_RCV
• UDT FEEDER_SND
Note
The message classes and texts in the table above are not configured at the PC_FEEDER
block. They must be adapted at the respective instance.
4.12.6 Commands
The commands of the three basic types are the same and cannot be changed. 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.
4.12.8 Configuration
The following section describes how to configure a Sentron VL/WL circuit breaker in PCS 7 Power
Control.
4.12.8.1 HW Config
The following steps must be performed in HW Config:
View in HW Config:
Note
If the mapping is changed during the operation of the AS, the modified mapping has to be
activated in CFC online mode with a positive edge at the "NEW_MAP" block input.
View in CFC:
• Optional: Custom faceplate - feedback status of the free user output: If a display is to be
created for the status of the free user output, the WinCC tag ".Pos_CMD_sp1" can be used. If
the free user output is set (".Pos_CMD_sp1 = 1), Text2 is displayed or Text2 is displayed if the
input is not set (".Pos_CMD_sp1 = 0).
4.12.9.1 Inputs
4.12.9.2 Outputs
7VE6X 3.3
Mapping input Tag Description Data type Bytes Offset
MEAS_MAP U1 U1 FLOAT 18*
MEAS_MAP U2 U2 FLOAT 20*
MEAS_MAP F1 F1 FLOAT 22*
MEAS_MAP F2 F2 FLOAT 24*
MEAS_MAP DU DU FLOAT 26*
MEAS_MAP DF DF FLOAT 28*
MEAS_MAP DANG DANG FLOAT 30*
MEAS_MAP REAL_sp1 Spare real 1 FLOAT
MEAS_MAP REAL_sp2 Spare real 2 FLOAT
MEAS_MAP REAL_sp3 Spare real 3 FLOAT
MEAS_MAP REAL_sp4 Spare real 4 FLOAT
DIAG_MAP DEV_RDY Device OK INT 2 0
DIAG_MAP TEST BOOL
DIAG_MAP PROTECT BOOL 2 1
DIAG_MAP DAT_VAL BOOL 2 7
BSTR_MAP INT_sp1 Spare INT 1 INT
BSTR_MAP INT_sp2 Spare INT 2 INT
BSTR_MAP INT_sp3 Spare INT 3 INT
BSTR_MAP INT_sp4 Spare INT 4 INT
BSTR_MAP INT_sp5 Spare INT 5 INT
BSTR_MAP INT_sp6 Spare INT 6 INT
BSTR_MAP SwCount Switch count Q0 DINT
BSTR_MAP OpTm Operating hours DINT
BSTR_MAP DINT_sp1 BS32 value 8 (spare) DINT
BSTR_MAP DINT_sp2 BS32 value 8 (spare) DINT
BSTR_MAP DINT_sp3 BS32 value 8 (spare) DINT
BSTR_MAP DINT_sp4 BS32 value 8 (spare) DINT
BSTR_MAP DINT_sp5 BS32 value 8 (spare) DINT
BSTR_MAP DINT_sp6 BS32 value 8 (spare) DINT
ALRM_MAP EVID1_S1 Relay General TRIP BOOLMsg 2 6
ALRM_MAP EVID1_S2 Relay pickup BOOLMsg 2 5
7VE6X 3.3
Mapping input Tag Description Data type Bytes Offset
ALRM_MAP EVID1_S3 External trip 1 TRIP BOOLMsg
ALRM_MAP EVID1_S4 External trip 1 picked up BOOLMsg
ALRM_MAP EVID1_S5 External trip 2 TRIP BOOLMsg
ALRM_MAP EVID1_S6 External trip 2 picked up BOOLMsg
ALRM_MAP EVID1_S7 External trip 3 TRIP BOOLMsg
ALRM_MAP EVID1_S8 External trip 3 picked up BOOLMsg
ALRM_MAP EVID2_S1 External trip 4 TRIP BOOLMsg
ALRM_MAP EVID2_S2 External trip 4 picked up BOOLMsg
ALRM_MAP EVID2_S3 Frequency 1 < TRIP BOOLMsg
ALRM_MAP EVID2_S4 Frequency 1 < picked up BOOLMsg
ALRM_MAP EVID2_S5 Frequency 2 < TRIP BOOLMsg
ALRM_MAP EVID2_S6 Frequency 2 < picked up BOOLMsg
ALRM_MAP EVID2_S7 Frequency 3 < TRIP BOOLMsg
ALRM_MAP EVID2_S8 Frequency 3 < picked up BOOLMsg
ALRM_MAP EVID3_S1 Frequency 4 < TRIP BOOLMsg
ALRM_MAP EVID3_S2 Frequency 4< picked up BOOLMsg
ALRM_MAP EVID3_S3 Breaker failure picked up BOOLMsg
ALRM_MAP EVID3_S4 Breaker failure TRIP T1 BOOLMsg
ALRM_MAP EVID3_S5 Breaker failure TRIP T2 BOOLMsg
ALRM_MAP Loc Local operation BOOLMsg
ALRM_MAP Error Error summary alarm BOOLMsg 2 3
ALRM_MAP Warning Alarm summary event BOOLMsg 2 4
BOOL_MAP P1_MEAS Voltage difference OK BOOLMsg 9 3
ALRM_MAP P2_MEAS Point 1 measurement in progress BOOLMsg 7 0
ALRM_MAP P3_MEAS Point 2 measurement in progress BOOLMsg 7 1
ALRM_MAP P4_MEAS Point 3 measurement in progress BOOLMsg 7 2
ALRM_MAP P5_MEAS Point 4 measurement in progress BOOLMsg 7 3
ALRM_MAP P6_MEAS Point 5 measurement in progress BOOLMsg 7 4
ALRM_MAP P7_MEAS Point 6 measurement in progress BOOLMsg 7 5
ALRM_MAP P8_MEAS Point 7 measurement in progress BOOLMsg 7 6
ALRM_MAP P1_CL_EN Point 8 measurement in progress BOOLMsg 7 7
BOOL_MAP P2_CL_EN Frequency difference OK BOOLMsg 9 4
BOOL_MAP P3_CL_EN Angle difference OK BOOLMsg 9 5
ALRM_MAP P4_CL_EN Point 1 close enable BOOLMsg 13 0
ALRM_MAP P5_CL_EN Point 2 close enable BOOLMsg 13 2
ALRM_MAP P6_CL_EN Point 3 close enable BOOLMsg 13 4
ALRM_MAP P7_CL_EN Point 4 close enable BOOLMsg 13 6
ALRM_MAP P8_CL_EN Point 5 close enable BOOLMsg 14 0
ALRM_MAP P6_CL_EN Point 6 close enable BOOLMsg 14 2
ALRM_MAP P7_CL_EN Point 7 close enable BOOLMsg 14 4
ALRM_MAP P8_CL_EN Point 8 close enable BOOLMsg 14 6
ALRM_MAP PARSET_A Parameter set A active BOOLMsg 1 4
7VE6X 3.3
Mapping input Tag Description Data type Bytes Offset
ALRM_MAP PARSET_B Parameter set B active BOOLMsg 1 5
ALRM_MAP PARSET_C Parameter set C active BOOLMsg 1 6
ALRM_MAP PARSET_D Parameter set D active BOOLMsg 1 7
ALRM_MAP EVID9_S5 Spare alarm 1 BOOLMsg
ALRM_MAP EVID9_S6 Spare alarm 2 BOOLMsg
ALRM_MAP EVID9_S7 Spare alarm 3 BOOLMsg
ALRM_MAP EVID9_S8 Spare alarm 4 BOOLMsg
ALRM_MAP EVID10_S1 Spare alarm 5 BOOLMsg
ALRM_MAP EVID10_S2 Spare alarm 6 BOOLMsg
ALRM_MAP EVID10_S3 Spare alarm 7 BOOLMsg
ALRM_MAP EVID10_S4 Spare alarm 8 BOOLMsg
ALRM_MAP EVID10_S5 Spare alarm 9 BOOLMsg
ALRM_MAP EVID10_S6 Spare alarm 10 BOOLMsg
ALRM_MAP EVID10_S7 Spare alarm 11 BOOLMsg
ALRM_MAP EVID10_S8 Spare alarm 12 BOOLMsg
ALRM_MAP Spa1_ON Spare command 1 On BOOLMsg
ALRM_MAP Spa1_OFF Spare command 1 Off BOOLMsg
ALRM_MAP Spa2_ON Spare command 2 On BOOLMsg
ALRM_MAP Spa2_OFF Spare command 2 Off BOOLMsg
ALRM_MAP Spa3_ON Spare command 3 On BOOLMsg
ALRM_MAP Spa3_OFF Spare command 3 Off BOOLMsg
ALRM_MAP Spa4_ON Spare command 4 On BOOLMsg
ALRM_MAP Spa4_OFF Spare command 4 Off BOOLMsg
ALRM_MAP Spa5_ON Spare command 5 On BOOLMsg
ALRM_MAP Spa5_OFF Spare command 5 Off BOOLMsg
ALRM_MAP Spa6_ON Spare command 6 On BOOLMsg
ALRM_MAP Spa6_OFF Spare command 6 Off BOOLMsg
ALRM_MAP Spa7_ON Spare command 7 On BOOLMsg
ALRM_MAP Spa7_OFF Spare command 7 Off BOOLMsg
ALRM_MAP Spa8_ON Spare command 8 On BOOLMsg
ALRM_MAP Spa8_OFF Spare command 8 Off BOOLMsg
CMD_MAP Cmd1 Cmd1_ON Cmd
CMD_MAP Cmd1_OFF
CMD_MAP Cmd2 Cmd2_ON Cmd
CMD_MAP Cmd2_OFF
CMD_MAP Cmd3 Cmd3_ON Cmd
CMD_MAP Cmd3_OFF
CMD_MAP Cmd4 Cmd4_ON Cmd
CMD_MAP Cmd4_OFF
CMD_MAP Cmd5 Cmd5_ON Cmd
CMD_MAP Cmd5_OFF
CMD_MAP Cmd6 Cmd6_ON Cmd
7VE6X 3.3
Mapping input Tag Description Data type Bytes Offset
CMD_MAP Cmd6_OFF
CMD_MAP Cmd7 Cmd7_ON Cmd
CMD_MAP Cmd7_OFF
CMD_MAP Cmd8 Cmd8_ON Cmd
CMD_MAP Cmd8_OFF
BOOL_MAP U2_DOWN U2_DOWN 15 0
BOOL_MAP U2_UP P1_U2_UP 15 1
BOOL_MAP F2_DOWN P1_F2_DOWN 15 2
BOOL_MAP F2_UP P1_F2_UP 15 3
6.1 DIGSI
1. You connect the signal of the protection device trip to the system bus in DIGSI.
To do so, write an "X" in the respective line in the "System Interface" column.
3. Select the check box "Select message in fault record" in the "Select in fault record" tab.
4. Download the configuration to the device (e.g., from the DIGSI Manager).
3. To apply the new parameters, select test mode in the CFC editor and set the "NEW_MAP" input
to "1".
The block resets the input back to "0" immediately afterward.
4. If necessary, the message text can be adapted at the technology block PC_FEEDER. In the
example, this would be the alarm text of the first signal of the MSG_EV_ID 4.
Note
Alarms simulated in test mode are not visible in the event list of the SIPROTEC.
1. Open the device in DIGSI with the "Direct" setting (e.g., using the "RS 232" port on the front).
2. Select "Test" > "Generate Indications" in the tree structure.
If a signal change is simulated here, the device changes to test mode after input prompt for
the password.
The default password is "000000" (without quotation marks).
3. You can now test the alarm in the faceplate of the technological object in WinCC.
The time stamp of the alarm originates directly in the SIPROTEC device.