SICAM P85x 7KG85 CM US
SICAM P85x 7KG85 CM US
SICAM P85x 7KG85 CM US
Table of Contents
User Information 1
SICAM Communication 2
Power Monitoring Device
and Power Quality Device
Connection with SICAM PQS 3
Glossary
SICAM P850/P855 7KG85X
Communication Index
V3.10
Manual
E50417-C1040-C482-A9
NOTE
i For your own safety, observe the warnings and safety instructions contained in this document, if available.
Target Audience
This manual is intended for all engineers configuring, parameterizing, and operating a SICAM P850/P855
device.
Scope
This manual is valid for the Class S Power Quality Instrument and Power Monitoring Device SICAM P850/P855.
Standards
This product is UL-certified to Standard UL 61010-1, third edition, based on the Technical data.
(UL File No.: E228586)
Additional Support
For questions about the system, contact your Siemens sales partner.
Training Courses
Inquiries regarding individual training courses should be addressed to our Training Center:
Siemens AG
Siemens Power Academy TD Phone: +49 911 9582 7100
Humboldtstraße 59 E-mail: [email protected]
90459 Nuremberg Internet: www.siemens.com/poweracademy
Germany
Notes on Safety
This document is not a complete index of all safety measures required for operation of the equipment (module
or device). However, it comprises important information that must be followed for personal safety, as well as
to avoid material damage. Information is highlighted and illustrated as follows according to the degree of
danger:
! DANGER
DANGER means that death or severe injury will result if the measures specified are not taken.
² Comply with all instructions, in order to avoid death or severe injuries.
! WARNING
WARNING means that death or severe injury may result if the measures specified are not taken.
² Comply with all instructions, in order to avoid death or severe injuries.
! CAUTION
CAUTION means that medium-severe or slight injuries can occur if the specified measures are not taken.
² Comply with all instructions, in order to avoid moderate or minor injuries.
NOTICE
NOTICE means that property damage can result if the measures specified are not taken.
² Comply with all instructions, in order to avoid property damage.
NOTE
i Important information about the product, product handling or a certain section of the documentation
which must be given attention.
OpenSSL
This product includes software developed by the OpenSSL Project for use in OpenSSL Toolkit (http://
www.openssl.org/).
This product includes software written by Tim Hudson ([email protected]).
This product includes cryptographic software written by Eric Young ([email protected]).
Preface.......................................................................................................................................................... 3
1 User Information.......................................................................................................................................... 9
1.1 General User Information.................................................................................................. 10
1.2 Contents of This System Manual........................................................................................11
2 Communication.......................................................................................................................................... 13
2.1 Communication Interfaces................................................................................................ 14
2.1.1 Communication via Ethernet Interface......................................................................... 14
2.1.1.1 TCP/IP Protocol Stack.............................................................................................. 14
2.1.1.2 IP Address.............................................................................................................. 14
2.1.1.3 Ethernet Interface Description................................................................................ 16
2.1.2 Communication via RS485 Interface.............................................................................16
2.2 Modbus............................................................................................................................ 18
2.2.1 Modbus Functions for Modbus TCP Server and Modbus RTU Slave................................ 18
2.2.2 Exception Responses for Modbus TCP Server and Modbus RTU Slave.............................18
2.2.3 Properties and Parameterization of the Modbus TCP Server.......................................... 19
2.2.4 Modbus RTU Slave....................................................................................................... 20
2.2.5 Numbering of Modbus Registers.................................................................................. 21
2.2.5.1 Modbus Specifications........................................................................................... 21
2.2.5.2 Mapping Documentation of the SICAM Devices...................................................... 21
2.2.6 Data Types.................................................................................................................. 22
2.2.6.1 Data Type - Measured Value (Read)........................................................................ 22
2.2.6.2 Data Type - Date/Time (Read and Write)..................................................................23
2.2.6.3 Data Type - Indications (Read)................................................................................ 24
2.2.6.4 Data Type - Controllable Indications (Read and Write)............................................. 25
2.2.6.5 Data Type - Counter (Read).....................................................................................26
2.2.7 Data in the Modbus Registers (Data Mapping).............................................................. 27
2.2.7.1 Registers 0001 to 0048: Device Identification (Read Only)...................................... 28
2.2.7.2 Registers 0065 to 0068: Date and Time (Read and Write)........................................ 28
2.2.7.3 Registers 0077 to 0088: Version Information (Read Only)....................................... 29
2.2.7.4 Registers 0101 and 0102: Device Status Indication (Read Only)...............................29
2.2.7.5 Registers 0111 and 0112: Measurand Limit Violation Indications (Read Only)..........29
2.2.7.6 Register 0113: Group Indications (Read Only)......................................................... 30
2.2.7.7 Register 0114: Power Quality Events (Read Only)....................................................30
2.2.7.8 Register 0131: Status of the Binary Outputs (Read Only)......................................... 31
2.2.7.9 Register 0141: Indications of the Communication (Read and Write).........................31
2.2.7.10 Register 0151: Load Profiles (Write Only)................................................................ 31
2.2.7.11 Register 0152: Load Profiles (Read Only).................................................................32
2.2.7.12 Register 0153: Synchronization of Load Profile Measuring Period (Read and Write)..32
2.2.7.13 Register 0154: Tariffs (Read and Write)................................................................... 32
2.2.7.14 Registers 0201 to 0322, and 6401 to 6406: Measured Values (Read Only).............. 32
2.2.7.15 Registers 0323 to 0358: Flicker (Read Only)............................................................34
2.2.7.16 Registers 0392 to 0399: Date/Time for Last Period PQ Aggregation (Read Only).......35
Glossary.................................................................................................................................................... 101
Index.........................................................................................................................................................103
Communication
To communicate with the systems control and other process automation equipment, SICAM P850/P855
features an Ethernet interface, and if included in the device module, an RS485 interface.
Ethernet supports the device parameterization, the transmission of measured data, metered values, load
profiles and indications/events, and time synchronization with NTP. Depending on the device model and
parameterization, the communication protocols HTTPS, Modbus TCP and/or IEC 61850 are used.
The RS485 interface supports the transmission of the measured data, metered values, indications, and time
synchronization. Depending on the device model, the Modbus RTU or IEC 60870-5-103 communication proto-
cols can be used for communication.
• DHCP (Dynamic Host Configuration Protocol) to assign the network configuration (IP address etc.) to
clients in an Ethernet network with DHCP server
• Data transfer to SICAM PQS for fault record and power quality analysis
• TCP/IP IPv4
• HTTPS
2.1.1.2 IP Address
To enable the device to communicate within the Ethernet network, you have to establish a network configura-
tion consisting of IP address, subnet mask and standard gateway.
The device is delivered with a default IP address that can be restored at any time by pressing the F4 softkey.
Each device also has a unique MAC address.
The default IP address and the default subnet mask are imprinted on the side panel:
[dw_location_key-F4_IP-addr_P85x, 1, en_US]
NOTE
i If the device is directly connected to a PC (without Ethernet switch), the PC will need a longer period to be
able to detect the connection and therefore to receive the ARP telegram. In this case it may not be detected
when PC and device have the same IP address.
If no DHCP server is available, disconnect the device from the network and start it using the default IP address
and subsequently assign a permanent IP address.
[le_Q100_3D_oben_ok_03, 1, --_--]
• Protocol: IEEE802.3
• Connection: 100Base-T (RJ45), pinout according to DIN EN 50173, automatic patch/crossover cable
recognition
• Connecting cable: 100 Ω to 150 Ω STP, CAT5 (shielded twisted-pair cable), max. 100 m if well installed
Devices equipped with an RS485 interface can communicate serially with peripheral devices using the Modbus
RTU or IEC 60870-5-103 bus protocol. The serial interface supports the following actions:
• Time synchronization
The connection is a 9-pin D-sub connector plug.
Data of the RS485 Interface when Using the Modbus RTU Protocol (Default Settings)
The RS485 interface comes with the following parameters set by the manufacturer:
• Device address: 1
• Parity: even
Data of the RS485 Interface when Using the IEC 60870-5-103 Protocol (Default Settings)
The RS485 interface comes with the following parameters set by the manufacturer:
• Device address: 1
• Transmit energy: no
[dw_P85x_behind, 1, en_US]
NOTE
i The pinout of the D-sub connector plug is described in Device Manual SICAM P850/P855.
2.2 Modbus
When communicating via Ethernet, the Modbus TCP protocol is used; communication via RS485 relies on the
Modbus RTU protocol. The following Modbus specifications with a detailed explanation of the Modbus
protocol are provided at http://www.modbus.org:
2.2.1 Modbus Functions for Modbus TCP Server and Modbus RTU Slave
NOTE
i The Modbus functions are the same for Modbus TCP (Ethernet) and Modbus RTU (serial).
The Modbus TCP server of SICAM P850/P855 supports the following Modbus functions:
2.2.2 Exception Responses for Modbus TCP Server and Modbus RTU Slave
NOTE
i The exception responses for Modbus TCP (Ethernet) and Modbus RTU (serial) are the same.
The Modbus server performs a series of consistency checks of the Modbus client requests, and if errors (for
example request to read a nonexistent register) are detected, it generates Modbus exception codes which are
signaled to the Modbus client in exception response messages.
The messages contain the following codes:
• The Modbus client uses a function that is not supported by the Modbus server of the SICAM P850/P855.
The supported Modbus functions are listed in 2.2.1 Modbus Functions for Modbus TCP Server and
Modbus RTU Slave.
• An attempt is made to read out or write to a nonexistent Modbus register (see 2.2.7 Data in the Modbus
Registers (Data Mapping), Modbus mapping for valid registers).
• An attempt is made to read out or write to too many registers. A Modbus message enables reading out
125 holding registers and writing to 123 holding registers maximum.
• The Modbus client tries to write to a register in the Modbus server for which only read access is allowed
according to the Modbus mapping (see 2.2.7 Data in the Modbus Registers (Data Mapping)).
• The redundancy client addresses a register that does not allow access to partial data. The register has a
complex data structure and is distributed across several registers. The register can be read or written only
as a whole.
• The Modbus client tries to write to the Modbus server for which the access rights are set to "read only".
• Error during the time format conversion in the Modbus server because a faulty date/time format was
received via Modbus, for example month format > 12.
• Use of IP addresses for addressing individual components connected to the bus (bus nodes)
• The Modbus TCP protocol has the TCP port number 502 reserved on the server side. It is possible to use a
parameterized port number.
• All data types in the Modbus TCP messages which are larger than 1 byte are stored in the Big-Endian
format, that is the most significant byte (MSB) is stored at the lowest register address and is transmitted
first.
• Communication sequence:
– The client sends a request to the server to start a data transmission from the server to the client.
– If the requested data are not available, the server sends an error feedback indication to the client.
• The Modbus TCP data packet has a maximum size of 260 bytes:
– 253 bytes max. for data and
– 7 bytes for the Modbus TCP header
Parameterization
The following parameters can be set for the Modbus TCP bus protocol (see also Device Manual SICAM P850/
P855):
Number of Connections
Up to four TCP connections are possible:
• With user port number: A total of 4 connections via standard port 502 and the user port
• Client-server protocol
• The individual data bytes in the messages are transmitted asynchronously with 11 bits:
– 1 start bit
– 8 data bits
– 1 parity bit and 1 stop bit or
– No parity bit and 2 stop bits
• Single messages are separated by bus silent intervals of at least 3.5 character times and end with a CRC
code for error detection.
Register Number
The register number characterizes a Modbus register using a 5-digit or 6-digit decimal number where the digit
with the highest value defines the register type:
• 3 – input register
• 4 – holding register
Counting of the register number starts at 1 for each register type, for example, for the 5-digit display:
Register Address
All address data in Modbus messages refer to the value 0. Therefore, register number and register address are
related as follows:
• Coil 127 is addressed as 126 (007Ehex) in a Modbus message to query or describe the coil status register.
• 40108 is addressed as 107 (006Bhex) in a Modbus message to query or describe the holding register.
Only holding registers are used for SICAM P850/P855. All measured values, indications, metered values etc.
are stored in these holding registers.
NOTE
i The Modbus data types for Modbus TCP (Ethernet) and Modbus RTU (serial) are the same.
The following data types are used for storing variables in the Modbus registers.
• Measured value
• Date/time
• Indication
• Controllable indication
• Counter
• String
NOTE
i The following convention applies when storing variables consisting of more complex data types to the
Modbus holding register (that is variables which are larger than a holding register, for example 32-bit
measured values):
The register with the lowest address contains the most significant byte (MSB), the register with the highest
address contains the least significant byte (LSB).
[dw_MeasuredValue, 1, en_US]
Value Range
The 32-bit floating-point format has the value range: ±(10-38 to 10+38).
0 < Exponent < 255: Resulting value = (-1)<sign> * 2 (<exponent> - 127) * 1, <mantissa>
• Hexadecimal: ±FF FF FF
• Decimal: ±16777216
32-bit floating-point numbers are accurate to about 7 decimal digits. An accuracy of 4 decimal digits
(0.2 measuring error) is required for measuring alternating current quantities.
[dw_DataTime, 2, en_US]
Date/Time Status
10H set: Daylight saving time active
20H set: Date/time error: equivalent to FAIL bit, see Device Manual SICAM P850/P855, Time Synchronization.
NOTE
i For the time synchronization via Ethernet, Siemens recommends the use of NTP.
[dw_Indications, 2, en_US]
Where:
Value Bit V
The value bit indicates whether an indication is ON (=1) or OFF (=0).
• Processing internal device commands (for example resetting the energy counters)
The holding register is used for read and write access in this context.
[dw_ControllableIndications_Read, 1, en_US]
Where:
[dw_ControllableIndications_Write, 1, en_US]
This data format enables up to 8 commands to be transmitted via the holding register for which the ON/OFF
bits are set to either 0/1 or to 1/0. If these bits are set to 0/0 or 1/1, no evaluation will be performed.
General
With the Counter data type, units of energy are transmitted as counter pulses.
To calculate the primary value, the conversion factor 'Energy per counter pulse' is output as the Measured
Value data type in addition to the counter pulses (see 2.2.6.1 Data Type - Measured Value (Read)). The
primary value is calculated as follows:
The following information is sent to each counter using the Modbus protocol:
• Separate status indications for invalid and overflow for each counter
• Energy per counter pulse in floating-point format for measured values (see 2.2.7.28 Registers 3801 to
3990: Tariff Counters (Read Only))
Counter Pulses
32-bit integers with sign allow a maximum of ±2 147 483 647 counter pulses before the counter overflows.
The Counter data type is structured as follows:
[dw_CounterPulses, 1, en_US]
Bit S (Sign)
Reserved for negative metered values.
Quality Information
The two following quality bits are stored for each counter in separate holding registers:
• Overflow OV: The internal counter pulse exceeds 31 bits. The Overflow bit is reset once the counter has
been reset.
• Invalid IV: The counter value is invalid due to a reset/device start. The bit is deleted 1 min after the device
start.
[dw_CounterQuality, 1, en_US]
NOTE
i The data for Modbus TCP (Ethernet) and Modbus RTU (serial) in the Modbus registers are the same.
The indications, measured values, etc. are stored in Holding registers. The following register groups exist.
They are described in the following sections:
• Register 0153: Synchronization of load profile measuring period (read and write)
• Registers 0201 to 0322, and 6401 to 6406: Measured values (read only), without 0281 to 0292
• Registers 0392 to 0395: Date/Time for last period PQ aggregation (fixed period = 10 s) (read only)
• Registers 0396 to 0399: Date/Time for last period PQ aggregation for frequency (configurable) (read
only)
• Registers 0401 to 0510, and 16001 to 16006: PQ aggregation values – average values (read only)
• Registers 0531 to 0640, and 16007 to 16012: PQ aggregation values – minimum values (read only)
• Registers 0651 to 0760, and 16013 to 16018: PQ aggregation values – maximum values (read only)
• Registers 1801 to 2080: PQ aggregation for average harmonic voltage values (read only)
• Registers 2201 to 2480: PQ aggregation for max. harmonic voltage values (read only)
• Registers 2601 to 2880: PQ aggregation for average harmonic current values (read only)
• Registers 3001 to 3280: PQ aggregation for max. harmonic current values (read only)
2.2.7.2 Registers 0065 to 0068: Date and Time (Read and Write)
The date and time can be transmitted in 64-bit format or in 32-bit format.
64-bit Format
The 4 registers 0065 to 0068 (time and date) are transmitted in one message.
32-bit Format
The registers are transmitted in 2 messages. The 1st message contains the registers 0067 and 0068 (date), the
2nd message contains the registers 0065 and 0066 (time).
The time synchronization only takes effect when the time has been completely transmitted.
2.2.7.4 Registers 0101 and 0102: Device Status Indication (Read Only)
These registers are write-protected. A write attempt will be rejected with exception code 02
(ILLEGAL_DATA_ADDRESS).
Data type: Indication
2.2.7.5 Registers 0111 and 0112: Measurand Limit Violation Indications (Read Only)
These registers are write-protected. A write attempt will be rejected with exception code 02
(ILLEGAL_DATA_ADDRESS).
Data type: Indication
NOTE
i If a voltage, frequency, or voltage unbalance event happened and ended, the relevant bit of this register
will be set to "1" and will be kept until it is reset by using relevant bits in register 141.
0141/24 to Reserved =0
0141/26
0141/28 Reset PQ Voltage Event 0 → 1: Resets voltage events, such as dips, swells,
and interrupts
0141/210 Reset PQ Frequency Event 0 → 1: Resets frequency events, such as overfre-
quency and underfrequency events
0141/212 Reset PQ VoltUnbal Event 0 → 1: Resets voltage unbalance events
0141/214 Reset Energy 0 → 1: Resets the energy counters
2.2.7.12 Register 0153: Synchronization of Load Profile Measuring Period (Read and Write)
Data type: Controllable indications
2.2.7.14 Registers 0201 to 0322, and 6401 to 6406: Measured Values (Read Only)
These registers are write-protected. A write attempt will be rejected with exception code 02
(ILLEGAL_DATA_ADDRESS).
Data type: Measured value
Table 2-18 Registers 0201 to 0322, and 6401 to 6406: Measured Values
NOTE
i It depends on the connection type (ph-ph or ph-n) which measured values are available. Phase-to-phase
quantities are available in 3-wire networks; phase-to-ground quantities are available with all other connec-
tion types. See SICAM P850/P855 Device Manual, section “Measurands Depending on the Connection
Type”.
2.2.7.16 Registers 0392 to 0399: Date/Time for Last Period PQ Aggregation (Read Only)
NOTE
These registers are write-protected. A write attempt will be rejected with exception code 02
(ILLEGAL_DATA_ADDRESS).
Table 2-20 Registers 0392 to 0395: Date/Time for Last Period PQ Aggregation
Registers 0396 to 0399: Date/Time for Last Period PQ Aggregation for Frequency
Date type: Date/time
Table 2-21 Registers 0396 to 0399: Date/Time for Last Period PQ Aggregation for Frequency
2.2.7.17 Registers 0401 to 0510, and 16001 to 16006: PQ Aggregation Values – Average Values (Read Only)
NOTE
These registers are write-protected. A write attempt will be rejected with exception code 02
(ILLEGAL_DATA_ADDRESS).
The data are calculated within the parameterized time (for example 1 min, 10 min, etc.).
Data type: Measured value
Table 2-22 Registers 0401 to 0510, and 16001 to 16006: PQ Aggregation Values – Average Values
2.2.7.18 Registers 0531 to 0640, and 16007 to 16012: PQ Aggregation Values – Minimum Values (Read Only)
NOTE
These registers are write-protected. A write attempt will be rejected with exception code 02
(ILLEGAL_DATA_ADDRESS).
The data are calculated within the parameterized time (for example 1 min, 10 min, etc.).
Data type: Measured value
Table 2-23 Registers 0531 to 0640, and 16007 to 16012: PQ Aggregation Values – Minimum Values
2.2.7.19 Registers 0651 to 0760, and 16013 to 16018: PQ Aggregation Values – Maximum Values (Read Only)
NOTE
These registers are write-protected. A write attempt will be rejected with exception code 02
(ILLEGAL_DATA_ADDRESS).
The data are calculated within the parameterized time (for example 1 min, 10 min, etc.).
Data type: Measured value
Table 2-24 Registers 0651 to 0760, and 16013 to 16018: PQ Aggregation Values – Maximum Values
2.2.7.23 Registers 1801 to 2080: PQ Aggregation for Harmonics (Average Values) – Voltage Values (Read Only)
NOTE
These registers are write-protected. A write attempt will be rejected with exception code 02
(ILLEGAL_DATA_ADDRESS).
The data are calculated within the parameterized time (for example 1 min, 10 min, etc.).
Network types: Harmonic ph-n is available if 4-wire is used, and harmonic ph-ph is available if 3-wire is used.
Data type: Measured value
Table 2-30 Registers 1801 to 2080: PQ Aggregation for Harmonics (Average Values) – Voltage Values
2.2.7.24 Registers 2201 to 2480: PQ Aggregation for Harmonics (Maximum Values) – Voltage Values (Read Only)
NOTE
These registers are write-protected. A write attempt will be rejected with exception code 02
(ILLEGAL_DATA_ADDRESS).
The data are calculated within the parameterized time (for example 1 min, 10 min, etc.).
Data type: Measured value
Table 2-31 Registers 2201 to 2498: PQ Aggregation for Harmonics (Maximum Values) – Voltage Values
2.2.7.25 Registers 2601 to 2880: PQ Aggregration for Harmonics (Average Values) – Current Values (Read Only)
NOTE
These registers are write-protected. A write attempt will be rejected with exception code 02
(ILLEGAL_DATA_ADDRESS).
The data are calculated within the parameterized time (for example 1 min, 10 min, etc.).
Data type: Measured value
Table 2-32 Registers 2601 to 2880: PQ Aggregration for Harmonics (Average Values) – Current Values
2.2.7.26 Registers 3001 to 3280: PQ Aggregation for Harmonics (Maximum Values) – Current Values (Read Only)
NOTE
These registers are write-protected. A write attempt will be rejected with exception code 02
(ILLEGAL_DATA_ADDRESS).
The data are calculated within the parameterized time (for example 1 min, 10 min, etc.).
Data type: Measured value
Table 2-33 Registers 3001 to 3280: PQ Aggregation for Harmonics (Maximum Values) – Current Values
2.2.7.30 Registers 4873 to 4984: Energy Freeze Float64 Values (Read Only)
Data type: Measured value (64-bit floating-point format)
2.2.7.36 Registers 5901 to 5997: Latest 10 Voltage Unbalance Events (Read Only)
These registers are write-protected. A write attempt will be rejected with exception code 02
(ILLEGAL_DATA_ADDRESS).
Data type: Measured value + Date/time
The following table shows the information for the latest voltage unbalance event (5901 to 5907). The infor-
mation of the other 9 voltage unbalance events (5911 to 5997) is in the same structure.
Table 2-44 Registers 5901 to 5907: The Latest Voltage Unbalance Event
2.2.7.39 Registers 6101 to 6158: Load Profile – Measured Values (Read Only)
These registers are write-protected. A write attempt will be rejected with exception code 02
(ILLEGAL_DATA_ADDRESS).
Data type: Measured value
2.2.7.41 Registers 8701 to 8756: Energy Freeze Float32 Values (Read Only)
Data type: Measured value (32-bit floating-point format)
The diagnostics for Modbus TCP and Modbus RTU allows analyzing the parameters and communication as well
as resetting the diagnostics counters. For more information, see the SICAM P850/P855 device manual, Config-
uration of the Device.
[sc_Modbus_TCP_diagnosis, 1, en_US]
• Port number:
Standard port 502 and configured user port
• Maximum connections:
For user port number 502: 4 connections via the standard port 502
For other user port numbers: A total of 4 connections via standard port 502 and the user port
• Used connections:
Number of connections that are actually used
• Connection overflows:
Counter of the attempts to establish more connections than allowed;
Number of allowed connection attempts:
For user port number 502: ≥ 4 connection attempts via standard port 502
For other user port numbers: ≥ 3 connection attempts via standard port 502 and/or ≥ 3 connection
attempts via user port
Parameter of Connections
• Server port:
Server port number of the current connection in the respective column; if 0 is displayed, the connection
is inactive or down
• Client IP:Port:
Last or current IP address and port number of the client
• Received bytes:
Total number of bytes received by the TCP port
• Sent bytes:
Total number of bytes sent to the TCP port
• Good messages:
Total number of messages received that were detected as valid Modbus messages
• Exception responses:
Counters of the transmitted exception response messages (see 2.2.2 Exception Responses for Modbus
TCP Server and Modbus RTU Slave)
[sc_Diagnose_Modbus_RTU, 1, en_US]
Parameter
The following parameters are displayed with Modbus RTU:
• Device address:
Default setting: 1
• Baud rate:
Default setting: 19 200 bit/s
• Parity:
Default setting: Even
• Access rights:
Default setting: Full
Serial Interface
• Received bytes:
Total number of bytes received by the RS485 interface
• Sent bytes:
Total number of bytes sent to the RS485 interface
• Framing errors:
Number of detected frame errors (invalid stop bit, for example if the baud rate is wrong)
• Parity errors:
Number of detected parity errors (wrong parity)
Serial Server
• Good messages:
Total number of messages received that were detected as valid Modbus messages
• CRC errors:
Total number of messages received in which CRC errors were detected
• Exception responses:
Counters of the transmitted exception response messages
• Broadcast messages:
Total number of the broadcast messages received with the server address 0
NOTE
i For information on ASDU 205, see: http://siemens.siprotec.com; pdf document: Additional information for
users of the IEC 60870-5-103.
Explanations to the 100 % corresponds to Values: Alternating voltages and Alternating Currents
All 100 % values correspond to the associated selected nominal operating values (AC 1 A or AC 5 A for currents
and AC 110 V, AC 190 V, AC 400 V or AC 690 V (max. 600 V for UL) for voltages Vph-ph).
The following special cases apply to the frequency and the active power factors:
Explanations to the "100 % corresponds to" Values: Active Power Factor cos φ
The active power factor cos φ has a sign:
Information Number
Function Type
Compatibility
Data Unit
Position
# Value Measured Quantity 100% Corresponds to
1 Va Voltage (A-N) Vph-N (nom.) 130 148 Yes 9 4
2 Vb Voltage (B-N) Vph-N (nom.) 130 148 Yes 9 5
3 Vc Voltage (C-N) Vph-N (nom.) 130 148 Yes 9 6
4 Vab Voltage (A-B) Vph-ph (nom.) 130 151 No 9 1
5 Vbc Voltage (B-C) Vph-ph (nom.) 130 151 No 9 2
6 Vca Voltage (C-A) Vph-ph (nom.) 130 151 No 9 3
7 Vavg Average Voltage Vph-N (nom.) 130 151 No 9 4
8 VN Neutral-point Vph-N (nom.) 130 150 No 9 7
displacement voltage
9 Ia Current (A) I(nom.) 130 148 Yes 9 1
10 Ib Current (B) I(nom.) 130 148 Yes 9 2
11 Ic Current (C) I(nom.) 130 148 Yes 9 3
12 Iavg Average Current I(nom.) 130 151 No 9 9
13 IN Neutral-point current I(nom.) 130 151 No 9 10
14 Pa Active power (A) I(nom.) * Vph-N (nom.) 130 150 No 9 1
15 Pb Active power (B) I(nom.) * Vph-N (nom.) 130 152 No 9 1
16 Pc Active power (C) I(nom.) * Vph-N (nom.) 130 152 No 9 2
17 P Active power 3 * I(nom.) * Vph-N (nom.) 130 148 Yes 9 7
18 Qa Reactive power (A) I(nom.) * Vph-N (nom.) 130 150 No 9 2
Information Number
Function Type
Compatibility
Data Unit
Position
# Value Measured Quantity 100% Corresponds to
19 Qb Reactive power (B) I(nom.) * Vph-N (nom.) 130 152 No 9 3
20 Qc Reactive power (C) I(nom.) * Vph-N (nom.) 130 152 No 9 4
21 Q Reactive power 3 * I(nom.) * Vph-N (nom.) 130 148 Yes 9 8
22 Sa Apparent power (A) I(nom.) * Vph-N (nom.) 130 150 No 9 3
23 Sb Apparent power (B) I(nom.) * Vph-N (nom.) 130 152 No 9 5
24 Sc Apparent power (C) I(nom.) * Vph-N (nom.) 130 152 No 9 6
25 S Apparent power 3 * I(nom.) * Vph-N (nom.) 130 151 Yes 9 5
26 cos φ (a) Active power factor 1 130 150 No 9 4
cos φ (A)
27 cos φ (b) Active power factor 1 130 152 No 9 7
cos φ (B)
28 cos φ (c) Active power factor 1 130 152 No 9 8
cos φ (C)
29 cos φ Active power factor 1 130 151 No 9 6
cos φ
30 PFa Power factor (A) 1 130 150 No 9 5
31 PFb Power factor (B) 1 130 152 No 9 9
32 PFc Power factor (C) 1 130 152 No 9 10
33 PF Power factor 1 130 151 No 9 7
34 φa Phase angle (A) 180° 130 150 No 9 6
35 φb Phase angle (B) 180° 130 152 No 9 11
36 φc Phase angle (C) 180° 130 152 No 9 12
37 φ Phase angle 180° 130 151 No 9 8
38 f Power frequency 5 Hz deviation 130 148 Yes 9 9
39 U2 Unbalanced voltage 100 % 130 151 No 9 11
40 Iunbal Unbalanced current 100 % 130 151 No 9 12
41 THDS Va Subgroup total 100 % 130 153 No 9 1
harmonic distortion,
voltage (a)
42 THDS Vb Subgroup total 100 % 130 153 No 9 2
harmonic distortion,
voltage (b)
43 THDS Vc Subgroup total 100 % 130 153 No 9 3
harmonic distortion,
voltage (c)
44 THDS Ia Subgroup total 100 % 130 154 No 9 1
harmonic distortion,
current (a)
45 THDS Ib Subgroup total 100% 130 154 No 9 2
harmonic distortion,
current (b)
Information Number
Function Type
Compatibility
Data Unit
Position
# Value Measured Quantity 100% Corresponds to
46 THDS Ic Subgroup total 100% 130 154 No 9 3
harmonic distortion,
current (c)
47 to H_Va_1 to Odd harmonic (1 to 100% 130 170 No 9 1 to
66 H_Va_39 39), voltage (a-N) 20
67 to H_Vb_1 to Odd harmonic (1 to 100% 130 171 No 9 1 to
86 H_Vb_39 39), voltage (b-N) 20
87 to H_Vc_1 to Odd harmonic (1 to 100% 130 172 No 9 1 to
106 H_Vc_39 39), voltage (c-N) 20
107 H_Va_2 to Even harmonic (2 to 100% 130 173 No 9 1 to
to H_Va_40 40), voltage (a-N) 20
126
127 H_Vb_2 to Even harmonic (2 to 100% 130 174 No 9 1 to
to H_Vb_40 40), voltage (b-N) 20
146
147 H_Vc_2 to Even harmonic (2 to 100% 130 175 No 9 1 to
to H_Vc_40 40), voltage (c-N) 20
166
167 H_Ia_1 to Harmonic (1, 2, 3 to 100% 130 176 No 9 1 to
to H_Ia_21 21), current (a) 21
187
188 H_Ib_1 to Harmonic (1, 2, 3 to 100% 130 177 No 9 1 to
to H_Ib_21 21), current (b) 21
208
209 H_Ic_1 to Harmonic (1, 2, 3 to 100% 130 178 No 9 1 to
to H_Ic_21 21), current (c) 21
229
230 H_Ia_22 to Harmonic (22, 23, 24 100% 130 179 No 9 1 to
to H_Ia_40 to 40), current (a) 19
248
249 H_Ib_22 to Harmonic (22, 23, 24 100% 130 180 No 9 1 to
to H_Ib_40 to 40), current (b) 19
267
268 H_Ic_22 to Harmonic (22, 23, 24 100% 130 181 No 9 1 to
to H_Ic_40 to 40), current (c) 19
286
Compatible Measurands II
Voltage (Vbc)
Voltage (Vca)
Average Voltage (Vavg)
Apparent Power (S)
Active Power Factor cos φ
Power Factor (PF)
Phase Angle (φ)
Average Current (I)
Neutral-Point Current (In)
Voltage unbalance (U2)
Current unbalance (Iunbal)
...
21st harmonic (Ia)
Network Type
1-phase 3-wire 3-phase 4-wire 3-phase
Network Balanced Unbalanced Unbalanced Balanced Unbalanced
3I 2I
Compatible Measurands II X3 X4 X4 X4 X X
Private Measurands X - - - - X
1-phase additional
Private Measurands - X X X X X
3-phase, 1. additional
Private Measurands - - - - - X
3-phase, 2. additional
Private Measurands X5 - - - X5 X
3-phase, 3. additional
Private Measurands X6 X6 X X X6 X
3-phase, 4. additional
Private Measurands X - - - X X
3-phase, 5. additional
Private Measurands - - - - - X
3-phase, 6. additional
Private Measurands - - - - - X
3-phase, 7. additional
Private Measurands X - - - X X
3-phase, 8. additional
Private Measurands - - - - - X
3-phase, 9. additional
Private Measurands - - - - - X
3-phase, 10. additional
Private Measurands X X X X X X
3-phase, 11. additional
Private Measurands - - X X - X
3-phase, 12. additional
Private Measurands - - X X - X
3-phase, 13. additional
Private Measurands X X X X X X
3-phase, 14. additional
Private Measurands - - X X - X
3-phase, 15. additional
3 The values for 3N as well as phases b and c in the “Compatible Measurands II” telegram which are not available for this network type
are indicated as invalid.
4 For 3-wire network configuration following quantities of measurand II are not valid: Van, Vbn, Vcn. Therefore, the relevant meas-
urand invalid bit in “Compatible Measurand II” - ASDU 9 will be set.
5 Measured values for Vb-N and Vc-N may be not available for some connection types and will be marked with invalid in data unit.
6 Measured values for Ib and Ic may be not available for some connection types and will be marked with invalid in data unit.
Network Type
1-phase 3-wire 3-phase 4-wire 3-phase
Network Balanced Unbalanced Unbalanced Balanced Unbalanced
3I 2I
Private Measurands - - X X - X
3-phase, 16. additional
Private Measurands X5 - - - X5 X
3-phase, 17. additional
Private Measurands - X X X - -
3-phase, 18. additional
All telegrams are transferred sequentially. The IEC 60870-5-103 slave sends the next following telegram in the
order shown in Table 2-57 and the measurands telegram.
When the last measurands telegram has been sent, transmission of the "Compatible Measurands II" telegram is
started again.
The IEC 60870-5-103 Master can retrieve either only one telegram, a part of the telegram or all telegrams
supported by the device.
On every class 2 request from the IEC 60870-5-103 master, the current measured values are transmitted. It is
the task of the communication master to compare the values of the current and previous request if necessary.
The following table contains all available commands and events as well as the information of the modules:
General Interrogation
Information Number
Function Type
Compatibility
Data Unit
Type of Informa-
# Designation Description tion
1 Indication 1 from Assign to binary Event 135 32 No 1 Yes
Remote output 1 or 2
2 Indication 1 from Assign to binary Command 135 32 No 20 -
Remote output 1 or 2
3 Indication 2 from Assign to binary Event 135 33 No 1 Yes
Remote output 1 or 2
4 Indication 2 from Assign to binary Command 135 33 No 20 -
Remote output 1 or 2
5 BO1 Binary output 1 Event 135 34 No 1 Yes
6 BO2 Binary output 2 Event 135 35 No 1 Yes
7 Limit Violation 1 Limiting value 1 Event 135 49 No 1 Yes
8 Limit Violation 2 Limiting value 2 Event 135 50 No 1 Yes
9 Limit Violation 3 Limiting value 3 Event 135 51 No 1 Yes
10 Limit Violation 4 Limiting value 4 Event 135 52 No 1 Yes
11 Limit Violation 5 Limiting value 5 Event 135 53 No 1 Yes
12 Limit Violation 6 Limiting value 6 Event 135 54 No 1 Yes
13 Limit Violation 7 Limiting value 7 Event 135 55 No 1 Yes
14 Limit Violation 8 Limiting value 8 Event 135 56 No 1 Yes
General Interrogation
Information Number
Function Type
Compatibility
Data Unit
Type of Informa-
# Designation Description tion
15 Limit Violation 9 Limiting value 9 Event 135 57 No 1 Yes
16 Limit Violation 10 Limiting value 10 Event 135 58 No 1 Yes
17 Limit Violation 11 Limiting value 11 Event 135 59 No 1 Yes
18 Limit Violation 12 Limiting value 12 Event 135 60 No 1 Yes
19 Limit Violation 13 Limiting value 13 Event 135 61 No 1 Yes
20 Limit Violation 14 Limiting value 14 Event 135 62 No 1 Yes
21 Limit Violation 15 Limiting value 15 Event 135 63 No 1 Yes
22 Limit Violation 16 Limiting value 16 Event 135 64 No 1 Yes
23 Battery fault Battery fault Event 135 65 No 1 Yes
24 Device OK Device OK Event 135 66 No 1 Yes
25 Reset Energy Reset energy Event 135 67 No 1 Yes
26 Reset Energy Reset energy Command 135 67 No 20 -
27 Time Synchroniza- Time synchroniza- Event 135 68 No 1 Yes
tion Error tion error
28 Settings Load Parameter load Event 135 69 No 1 Yes
29 SD card error SD card status Event 135 70 No 1 Yes
30 Direction Rotation Direction of rotation Event 135 82 No 1 Yes
31 GI1 Group indication 1 Event 135 83 No 1 Yes
32 GI2 Group indication 2 Event 135 84 No 1 Yes
33 GI3 Group indication 3 Event 135 85 No 1 Yes
34 GI4 Group indication 4 Event 135 86 No 1 Yes
Metering values (for example kWh) are not defined in the IEC standard and there are no compatible data units
available which are suitable for the transmission of metered values. The private data unit 205 has been
defined for the transmission of metered values using Class 1 data format.
Only one metering value per data unit is transmitted. There exists a cyclic interval for transmitting the coun-
ters which is set fixed to 1 min in SICAM P850/P855.
Compati- bility
Function Type
Data Unit
# Value Unit
1 WPa_exp Wh 133 51 No 205
2 WPb_exp Wh 133 52 No 205
3 WPc_exp Wh 133 53 No 205
4 WP_exp Wh 133 54 No 205
Information Number
Compati- bility
Function Type
Data Unit
# Value Unit
5 WPa_imp Wh 133 55 No 205
6 WPb_imp Wh 133 56 No 205
7 WPc_imp Wh 133 57 No 205
8 WP_imp Wh 133 58 No 205
9 WQa_ind varh 133 59 No 205
10 WQb_ind varh 133 60 No 205
11 WQc_ind varh 133 61 No 205
12 WQ_ind varh 133 62 No 205
13 WQa_cap varh 133 63 No 205
14 WQb_cap varh 133 64 No 205
15 WQc_cap varh 133 65 No 205
16 WQ_cap varh 133 66 No 205
17 WSa VAh 133 67 No 205
18 WSb VAh 133 68 No 205
19 WSc VAh 133 69 No 205
20 WS VAh 133 70 No 205
The diagnostics for IEC 60870-5-103 enables analyzing the parameters and the communication and resetting
the diagnostics counters. For more information, see the SICAM P850/P855 device manual, Configuration of
the Device.
Parameters
The following parameters are displayed with IEC 60870-5-103:
• Device address:
Default setting: 1
• Baud rate:
Default setting: 9600 bit/s
• Transmit energy: No
Serial Interface
The following parameters are displayed for the serial interface:
• Frame length error: Total numbers of incoming frame exceeded buffer size (invalid stop bit, for example
if the baud rate is wrong)
Serial Server
The following parameters are displayed for the serial server:
• Broadcast messages: Total numbers of received broadcast telegrams with server address zero
• Transmission error: Total numbers of error returned from target transmit routine
• FCB error: Total numbers of received invalid frame count bit (FCB)
3.1 General 80
3.2 Licensing SICAM PQS 81
3.3 Downloading IID/CID Files 82
3.4 Settings in SICAM PQS 84
3.5 Viewing Measured Values in Value Viewer 97
3.6 Graphic Display in PQ Analyzer 98
3.1 General
The data acquired by SICAM P850/P855 are stored in the internal memory of the device. The measured values,
for example mean values, and the trend records are available in the PGDIF data format. The fault records are
saved in the COMTRADE data format. This data can be transferred to SICAM PQS using the IEC 61850 Ed.2
protocol.
The SICAM PQS software, version V8.03 and higher, allows importing the data into the SICAM PQS archive.
Once the data has been transferred into the SICAM PQS archive, it can be used for further evaluations such as
reporting, export, etc.
SICAM PQ Analyzer or SIGRA allows displaying the data in graphical or numerical form and analyzing them. For
example, evaluations of the records and reports can be performed according to the EN 50160 standard or
other grid codes.
The following diagram shows the sequence of the parameterization and the analysis:
[dw_workflow-P85x-settings-for-SICAM_PQS, 1, en_US]
NOTE
[sc_SICAM_PQS_Feature_Enabler, 1, en_US]
Enter all license keys for your application and click Install.
Licenses
On the configuration computer:
• PQS Notification
[sc_configure_comm_IEC61850_P85x, 1, en_US]
NOTE
3.4.1 Configuration
[sc_SICAM_PQS_UI-Configuration, 1, en_US]
[sc_01_PQS_Config, 1, en_US]
• Select the project and add its system from the context menu.
Your own PC will be automatically inserted as the first system and as the full server.
[sc_SICAM_PQS_System_insert, 1, en_US]
• In the navigation window right-click SICAM PAS PQS → Computer name (in the example
e312n-002010) → Application → Archive.
[sc_02_PQS_Archive_create, 1, en_US]
[sc_03_Archive_path, 1, en_US]
• Click OK.
NOTE
i The archive is needed to store measurements recorded by SICAM P850/P855 which enables SICAM PQ
Analyzer to present them.
• In the navigation window right-click SICAM PAS PQS → Computer name (in the example:
e312n-002010) → Application → IEC 61850 Client.
[sc_04_IEC61850_Client, 1, en_US]
• If necessary, change the name of the IEC 61850 client in the General Parameters window.
• In the navigation window right-click SICAM PAS PQS → Computer name (in the example:
e312n-002010) → IEC 61850 Client → Interface.
[sc_06_Interface, 1, en_US]
[sc_07_Setting_Interface, 1, en_US]
• In the navigation window right-click SICAM PAS PQS → Computer name (in the example:
e312n-002010) → IEC 61850 Client → Interface (in the example: interface designation 3P4W) →
Import....
[sc_08_Import_in_interface, 1, en_US]
• In the folder select the file previously downloaded from device and then click Open.
[sc_importing_CID_file, 1, en_US]
• Select the desired element in the next window (in the example: SICAMP_00001) by checking the Select
column.
[sc_select_elements_P85x, 1, en_US]
• Click OK.
• If you wish a fault record transmission (COMTRADE files), select Yes in the list box under Fault record
transmission → Activation on device start.
• To transfer PQDIF data of the measured values or trend records, select Yes in the list box under PQDIF
data transmission → Transfer PQDIF data.
NOTE
i The fault records can be displayed in PQ Analyzer. Additionally, fault records can be forwarded via PQS
Automatic Export and PQS Notification and displayed by SICAM Diamond.
[sc_SICAM_PQS_UI-Operation, 1, en_US]
[sc_11_System_update, 1, en_US]
NOTE
i After the update has been completed successfully, the entries in the navigation window are displayed with
a blue icon.
• In the navigation window right-click your Computer name and subsequently Start all.
[sc_12_Start, 1, en_US]
[sc_13_current_status, 1, en_US]
[sc_14_Start_Value_Viewer, 1, en_US]
After starting the Value Viewer, the up-to-date measured values are displayed in a table.
[sc_15_View_in_Value_Viewer, 1, en_US]
NOTE
i You receive detailed information about the PQ Analyzer in the manual of the PQ Analyzer.
[sc_16_PQ-Analyzer_opend, 1, en_US]
• Select the fault record you want to display graphically and click Open.
[sc_17_GUI_COMTRADE-Data, 1, en_US]
[sc_graphic_display, 1, en_US]
AC
Alternating Current
ARP
Address Resolution Protocol: Network protocol
Big-Endian format
The most significant byte is stored first, that is at the memory location with the lowest address.
Broadcast message
Message in the network where data packets are transmitted to all devices on the network from one point
COMTRADE
COMmon format for TRAnsient Data Exchange
DHCP
Dynamic Host Configuration Protocol enables the network configuration to be assigned to the devices by a
DHCP server
Ethernet
Cable-based data network technology for local data networks
Holding register
Area for representing data in Modbus communication
IP
Internet Protocol
IP address
Addresses in computer networks based on the Internet protocol
Limit violation
A value exceeding or falling under a parameterized limiting value
MBAP
Modbus Application Protocol
MBAP Header
Header of a Modbus TCP message consisting of these 4 parts: Transaction identifier (2 bytes), protocol identi-
fier (2 bytes), length (2 bytes), unit identifier (1 byte)
Modbus
The Modbus protocol is a communication protocol based on a client-server architecture.
NaN
Not a Number means invalid: Result of an invalid computing operation
NTP
Network Time Protocol: Standard for synchronizing clocks in computer systems using packet-based communi-
cation networks
RJ45
Connector type
RS485
Interface standard for digital, wire-based, differential, serial data transmission
SNMP
Simple Network Management Protocol: Serves for monitoring and controlling network elements of a central
station
STP
Shielded twisted pair is the cable for 100Base-T (Ethernet).
Subnet mask
Bit mask in the network protocol that defines how many IP addresses the computer network encompasses.
Together with the IP address of a device, the subnet mask defines which IP addresses the device searches in its
own network.
TCP/IP
Transmission Control Protocol/Internet Protocol: Family of network protocols
C N
Communication 10 Numbering of Modbus Registers 21
Communication Interfaces 14
Communication via Ethernet Interface 14
Communication via RS485 Interface 16
Connection to SICAM PQS 10 P
Connection with SICAM PQS 79
PQ Analyzer 98
D
S
Data in the Modbus Registers 27
Data Mapping 27 Settings in SICAM PQS 84
Data Types 22
Default IP Address 15
T
M
Mapping Documentation 21
Modbus 18
Modbus Functions 18
Modbus RTU Slave 20
Modbus RTU Slave Diagnosis 61
Modbus Specifications 21
Modbus TCP Diagnosis 59
Modbus TCP Server 19