Manual CP-8031 CP-8050 ENGREG

Communication Protocols
13.19 ÖBB X25
Wiring for connection CI-8551 (X1, X2) ↔ "PAD"

The external "PAD" can also be connected to the X1, X2 interface of the CI-8551 module with an "open ended"
patch cable. For interface X1 or X2 "RS-232" must be selected.
Connector X1, X2 (CI-8551)
Pin RS-232 Signal Push-in terminal 8-pole

8 RXD (I)
7 DCD (I)
6 GND
5 n.c.
4 DTR (O)
3 CTS (I)
2 TXD (O)
1 RTS (O)
SICAM A8000 Series, CP-8031, CP-8050, Manual 1901

DC8-026-2, Edition 03.2022
13.19 ÖBB X25
Necessary accessories
Meaning Order number

DATUS-PAD 5810/20E www.datus.com
DATUS-PAD
Note: 5810/20E
The PAD is factory provided by the ÖBB.
RS PRO RJ-Adapter, 25-pole Sub-D plug, RJ45 socket https://at.rs-

connector, Adapter, 39mm online.com/web/p/rj-
adapter-
kupplungen-und-
RS Order nr. 370-5196
verlangerungen/
3705196/
13.19.5.1 Data transmission X25-interface
X25-interface
• The X25-interface is supplied via the external "PAD".
• The CP-8050 is connected to the "PAD" via a serial RS-232 interface.
• The X25 interface is defined in the ESTW Supplement 7 agreement. The X25 interface must be compat-
ible with the DATEX-P network of Austrian Post (according to ÖNORM A2625 edition 1984).
• The parameterization of the externally connected "PAD's" must be carried out offline using a suitable
terminal emulation program in accordance with ÖBB requirements.
• Data transmission on the X25-interface (PAD ↔ RZÜ) according to X.25 HDLC Lap B (DIN 66221, ISO
3309).
1902 SICAM A8000 Series, CP-8031, CP-8050, Manual

DC8-026-2, Edition 03.2022
13.19 ÖBB X25
PAD Designation Order number

DATUS-PAD 5810/20E www.datus.com
The PAD from Datus has two asynchronous interfaces DATUS-PAD

as basic equipment. In addition, slots with additional 5810/20E
interfaces can be built into the PAD.
Connection type of the X25 interface

The protocol element in CP-8050 only supports a fixed leased line via X25 packet data networks (= "Permanent
Virtual Circuit").
X25 connection type OX25I1
– Point-to-point connection via own routed connections
– Dedicated connection via packet data networks "Permanent Virtual Circuit" X
– Dial-up connection via packet data networks "Virtual Call"
The connection setup for the fixed leased line via the X25 network of the ÖBB must be carried out by the
externally connected "PAD".
Initialization of the X25 interface

The life cycle message is sent cyclically by the CP-8050 and the remote station and is used to monitor the
interface.
If the remote station does not receive a valid life cycle messages within the double cycle time for moni-
toring messages (life cycle), the interface is reported as failed.
After the interface fails, the transmission of the life cycle messages is stopped for at least 3 life cycle periods.
Then the own message number is set to 0.
When the first life cycle message is received from the remote site, the message number of the remote site is
adopted.
Function Note
0 • X.25 connection not established
1 • X.25 connection established, has not • The X.25 connection establishment is controlled by
yet received two life cycle frames in the "PAD".
the specified period.
2 • Life cycle frames are received cycli- • Interface fault is reset after receipt of 2 Life cycle
cally within the specified period. frames with consecutive telegram numbers.
• General interrogation has not yet • NO data transmission as long as no GI has been trig-
been initiated. gered!
3 • Life cycle frames are received cycli- • After an going interface fault, a GI is waited for, then
cally within the specified period. the interface is released again (message sent).
• General interrogation has been initi-
ated but has not yet been completed.

DC8-026-2, Edition 03.2022
13.19 ÖBB X25
4 • Life cycle frames are received cycli- • GI messages are sent.

cally within the specified period.
• Spontaneous messages are transmitted during a
• General interrogation has been initi- running GI.
ated but has not yet been completed.
5 • Cyclical sending and receiving of life
cycle frames.
6 • Interface in operation. • Messages are transmitted spontaneously when there
is a change.

DC8-026-2, Edition 03.2022
13.19 ÖBB X25
Establishing a connection after startup of the CP-8050 without recommissioning condition
TL.Nr. ... Message number

DC8-026-2, Edition 03.2022
13.19 ÖBB X25
(1) ... Command receipt

(2) ... ACK-General interrogation (Bit 3 of the control location 1 is 1)
(3) ... ACK-General interrogation (Bit 2 of the control location 1 is 1)
(4) ... Interface in operation.
Acknowledgment of messages on the X25 interface

Messages of the main groups 0-127 are sent without acknowledgment. Commands (messages of the main
group 128-255) must be acknowledged with an acknowledgment message.
Retries
No retries are carried out for sent messages.
Command messages
The protocol firmware OX25I1 does not support command messages in the transmit direction.
General Interrogation
The protocol firmware stores the signal box data in send direction in an internal process image.
The following data is transmitted when a general interrogation command is received from the remote station:
• Command-Acknowledgement
• Acknowledgment for general interrogation command
• all signal box data (from the PRE internal process image)
• GI-End Message
The protocol firmware OX25I1 does not send a general interrogation command to the remote station.
13.19.5.2 Function for the Support of Redundant Communication Routes
This function is currently not supported!
13.19.6 Parameter and Setting
Parameter Name Description Settings

[PRE] Interface parameter
Note: Some parameters may not be displayed until the interface is selected.
Interface “Virtual serial interface“ (CP-8050 Permitted range = COM1 to COMxx
internal). Default setting = not used
The "virtual serial interface" is
assigned on the BSE to a serial
interface plug.
13.1.4.5 Selection of a serial inter-
face for communication protocols
Baud Rate The protocol firmware supports Permitted range = 50, 75, 100,
selected baud rates in range 50 Bd 134.5, 150, 200, 300, 600, 1050,
to 115200 Bd. 1200, 1800, 2000, 2400, 4800,
9600, 19200, 38400, 56000,
57600, 64000, 115200
Standard setting = 19200

DC8-026-2, Edition 03.2022
13.19 ÖBB X25

Parity Parity bit for data byte on the bit Permitted range =
transmission layer of the RS-232
interface between CP-8050 ↔ PAD.
• no Parity
• even Parity
• odd Parity
Default setting = no parity
Stop bits Stop bits for data byte on the bit Permitted range = 1, 1.5, 2 Bit
transmission layer of the RS-232 Standard setting = 1 Bit
interface between CP-8050 ↔ PAD.
[PRE] Station definition | Own Stellenbezeichnung
Station and facility iden- The station and system identifier Permitted range =
tification are defined by 4 characters. The
first 3 characters represent the
• max. 4 ASCII characters
station identifier, the 4th character • permitted ASCII signs:
represents the system identifier. 0-9; A-Z; a-z
Example: PEN1 Default setting =
→ station identifier = PEN
→ facility identification = 1
Control center Unique identifier of the control
Permitted range = 0 to 255
point. Standard setting = 255
[PRE] Station definition | Stellenbezeichnung of the remote station
Station and facility iden- The station and system identifier Permitted range =
tification are defined by 4 characters. The
first 3 characters represent the
• max. 4 ASCII characters
station identifier, the 4th character • permitted ASCII signs:
represents the system identifier. 0-9; A-Z; a-z
Example: HBF1 Default setting =
→ station identifier = HBF1
→ facility identification = 1
[PRE] OX25 | Communication functions | Initialization
Startup delay When restarting the CP-8050 Permitted range = 0 to 255 s
device, the X25 protocol on the Standard setting = 15
line is only activated after a delay.
During the startup delay, the
process image on the PRE is
updated.
[PRE] OX25 | Communication functions | Time settings
Cycle time for monitoring Cycle time for life cycle telegram. Permitted range = 2 to 127 s
messages (life cycle) The life cycle message is sent cycli- Default setting = 2 s
cally by the CP-8050 and the
remote station and is used to
monitor the interface.
If the remote station does not
receive a valid life cycle messages
within the double cycle time for
monitoring messages, the interface
is reported as failed.
Pause time (tp) Before a message transmission, a Permitted range = 0 to 32767 ms
parameter-settable pause time "tp" 0 = no pause time
is maintained before the transmis- Standard setting = 10
sion level is switched on with RTS.

DC8-026-2, Edition 03.2022
13.19 ÖBB X25

[PRE] OX25 | Time settings | Monitoring times
Idle monitoring time After transmission disturbances or Permitted range = 0 to 32767 Bit
message interruption the idle state Standard setting = 22 Bit
is monitored. After expiry of the
monitoring time the receiver is
resynchronized.
Character Monitoring Time Message gap monitoring Maximum Permitted range = 0 to 32767 Bit
pause between successive bytes of Standard setting = 22 Bit
a message Idle monitoring time is
started after detection of message
interruption.
Timeout transmission The signal box information of the Permitted range = 2 to 20 s
signal box data different main groups is transferred Default setting = 5 s
internally to the PRE with <TI: =
33> "32 bit bit pattern with time
stamp CP56Time2a". If a main
group consists of more than 32 bit
data (4 bytes), then all data must
be transferred to the PRE within the
timeout.
[PRE] OX25 | General interrogation
Timeout for GI end infor- The end of GI message is trans- Permitted range = 0 to 255 s
mation mitted to the remote station after Default setting = 5 s
the configured timeout. The
timeout is started on receipt of a GI
command from the remote station
(main group = 255).
[PRE] Data base management
Settings for the data base management on BSE (per PRE) - see 13.1.4.13 Data Management on the BSE for
[PRE] Advanced parameters | Options
CRC-Polynom The CRC (2 bytes for message Permitted range =
backup) of the ÖBB X25 protocol
can be inverted for transmission
• CCITT-CRC inversion and cross-
over
and the byte order can be
exchanged if necessary. • normal CCITT-CRC
Default: CCITT-CRC inversion and

cross-over
[PRE] Advanced parameters | Software test points
… The software test points may only Permitted range = yes, no
be used under the guidance of Default setting = no
experts for error detection! Once
the fault isolation is completed,
software checkpoints must always
be turned off.

DC8-026-2, Edition 03.2022
13.19 ÖBB X25
NOTE
i On the basic system element in the topology for OX25I1 you have to enter following.
• QID-ST = End-End
• Uhr-Sync = disabled
• GI = do not send
• Data flow direction = both directions
• Data flow direction = automatic and selective
• Service function messages = disabled
13.19.7 Message Conversion
Data in transmit direction are transferred from the basic system element to the protocol element in CP-8050
internal IEC 60870-5-101/104 (without 101/104 blocking) format. The conversion of the data formats IEC
60870-5-101/104 ↔ ÖBB X25 is performed by the protocol element. The transmission of data to the X-25
interface is controlled by the protocol element.
User data in receive direction (ÖBB X25 → CP-8050) are not supported. Control functions like e.g. general
interrogation are processed direct on the protocol element and not converted to IEC 60870-5-101/104!
The conversion of the CP-8050 internal IEC 60870-5-101/104 message format → ÖBB X25 data format and the
conversion of the address information are called message conversion.
The parameterization of the conversion from IEC 60870-5-101/104 → ÖBB X25 (address and message format)
is to be done with SICAM Device Manager with function “Signals” or SICAM TOOLBOX II, OPM II using “SIP
Message Address Conversion”.
Supported processing types for message conversion:
Data Direction Processing type OX25I1

Signal box data Transmit direction firmware/Trans_RCC_arguments ✓
13.19.7.1 Message Conversion in Transmit Direction (CP-8050 → ÖBB X25)
Message Conversion in Transmit Direction CP-8050 → ÖBB X25

DC8-026-2, Edition 03.2022
13.19 ÖBB X25
CP-8050: IEC 60870-5-101/104 → ÖBB X25

TI Designation Message Format
<TI:=33> Bit string of 32 bit Signal box data
with time tag CP56Time2a
• <Main group 01> ... RCC-arguments (Track switch, DKW, EKW)
• <Main group 10> ... RCC-arguments (start information)
• <Main group 16> ... RCC-arguments (Main signal)
• <Main group 18> ... RCC-arguments (Protection signal)
• <Main group 31> ... RCC-arguments (Isolated track)
• <Main group 32> ... RCC-arguments (Isolated track)
• <Main group 33> ... RCC-arguments (Freimelde Abschnitt)
• <Main group 44> ... RCC-arguments (Agreement)
• <Main group 100> ... RCC-arguments (RZÜ-Fahrstraße)
- • <Main group 124> ... General interrogation command
acknowledgement 365
• <Main group 126> ... Life cycle message 366
• <Main group 127> ... Command acknowledgment 365
Signal box data

The parameterization of the address and message conversion for signal box data in transmit direction is to be
done with the SICAM Device Manager with the function “Signals” or the SICAM TOOLBOX II, OPM II.
Processing: firmware/Trans_RCC_arguments
Parameters
TI .. Type Identification Supported Type Identifications:
• <TI:=33> ... Bit sting of 32 Bit with time tag CP56Time2a

Name Name of the signal
104 address CP-8050 internal IEC 60870-5-101/104 message address
(CASDU1, CASDU2, IOA1, IOA2, IOA3)
365 The general interrogation command is processed direct on the protocol element and not converted towards basic system element
The GI-Data are transmitted by the protocol element out of the PRE-internal process image to the remote station. The messages
"General interrogation command acknowledgment" and "command acknowledgment" are generated directly on the protocol
element and transmitted to the remote station.
366 The life cycle message is generated direct at the protocol element and transmitted to the remote station.

DC8-026-2, Edition 03.2022
13.19 ÖBB X25
Parameters
OX25_Main_group ÖBB X25 address “Main group” for signal box data according to ÖBB
X-25 protocol specification.
• 01 = Track switch, DKW, EKW

• 10 = Start message
• 16 = Main signal
• 18 = Protection signal
• 31 = Isolated track
• 32 = Isolated track
• 33 = Freimelde Abschnitt
• 44 = Agreement
• 100 = RZÜ Fahrstraße
OX25_Element ÖBB X25 element address for signal box data according to ÖBB X-25
protocol specification.
• 0 to 65535
OX25_Message identifier Identification whether the X25 signal box data are transmitted
CP-8050 internally with one or with two messages in the format
<TI:=33> bit pattern of 32 bits (= 4 bytes).
• 1/1 … Part “1 of 1” for signal box data (signal box data 4 Byte)
OX25_IV_NT_Bit Conversion of the IEC 60870-5-101/104 “NT-/IV-Bit” to “Z-Bit” of the
ÖBB X25 protocol. Predefined control words of the main groups
contain a “Z-Bit” (Z=1… state not actual).
NT- or IV-Bit =1: With “NT/IV=1”, all “Z-Bit‘s” and the status of the
control word are set according to the parameterization.
• Z=1, Data=0
• Z=1, Data from message
Message Conversion
The table describes the evaluated elements of the IEC 60870-5-101/104 message during message conversion.
Elements of the message
TI .. Type Identification • TI 33 .. Bit sting of 32 Bit with time tag CP56Time2a
CASDU, IOA .. Message address Parameter-settable
QDS .. Quality descriptor
BL .. blocked not evaluated
SB .. substituted not evaluated
NT .. not topical Conversion to ÖBB X25 “Z-Bit” and data settable with
OX25_IV_NT_Bit.
IV .. invalid Conversion to ÖBB X25 “Z-Bit” and data settable with
OX25_IV_NT_Bit.
OV .. overflow not evaluated
Cause of transmission
03 .. spontaneous not evaluated
xx .. other COTs not evaluated
T .. Test not evaluated
Information

DC8-026-2, Edition 03.2022
13.19 ÖBB X25
Elements of the message

BSI .. binary displayed additional informa- • Bit string (32 bit)
tion … is converted to ÖBB X25 signal box data.
Time tag
CP56Time2a .. Date + Time not evaluated
... not listed elements of the IEC 60870-5-101/104 message are not rated / not supported!
13.19.7.2 Message Conversion in Receive Direction (CP-8050 ← ÖBB X25)
Message Conversion in Receive Direction CP-8050 ← ÖBB X25:

CP-8050: IEC 60870-5-101/104 ← ÖBB X25
TI Designation Message Format
- <Main group 126> ... Life cycle message367
- <Main group 255> ... General interrogation command 368
367 The life cycle message is processed direct at the protocol element and not converted towards the basic system element.
368 The general interrogation command is processed direct on the protocol element and not converted towards basic system element
The GI-Data are transmitted by the protocol element out of the PRE-internal process image to the remote station.

DC8-026-2, Edition 03.2022
13.20 HSR
13.20 HSR
13.20.1 Introduction
HSR (High Availability Seamless Redundancy) is a redundancy protocol for the lossless, redundant transmission
of data over Ethernet networks in ring structure.
Like PRP, HSR (High Availability Seamless Redundancy Protocol) is specified in IEC 62439-3. Both protocols
provide redundancy without switching time.
The principle function can be found in the definition of PRP. PRP sends the same message over 2 separate
networks. In contrast, the message is duplicated in HSR in the 2 directions of the ring. The receiver receives it
accordingly over 2 ways in the ring, takes the 1st. message and rejects the 2nd (see PRP).
While NO messages are forwarded in the terminal at PRP, a switch function is built into the HSR node. There-
fore, the HSR node forwards messages in the ring that are not addressed to it.
In order to avoid circling messages in the ring, corresponding mechanisms are defined in HSR. The connection
of SAN (Single Attached Node) devices is only possible with HSR using a REDBOX.
PRP and HSR systems can be redundantly coupled with 2 REDBOXES.
Each device in the network is connected via 2 Ethernet interfaces. The messages are transmitted on both inter-
faces and transmitted simultaneously in both directions in the ring. Thus 2 identical messages arrive at the
target within a time frame (in a error-free state). The first is passed to the application and the second is
discarded.
The ring is monitored by cyclic HSR management telegrams (cycle time 1 second). An open ring is signaled by
a warning.
CP-8050 uses the "duplicate discard" mode in HSR, that means that duplicates are discarded and not passed to
the TCP/IP stack.
NOTE
i • HSR can only be used with the CI-852x module.
• Only 1 redundancy protocol can be used per ring.
• 2 HSR rings are possible for each CI-852x module.
• 2 redundancy protocols for Ethernet networks are possible for each CI-852x module (here 2x HSR or
1x HSR with RSTP, PRP or Line Mode).
• The choice, which 2 of the 5 interfaces on the module are used for the HSR ring, is arbitrary.
• For HSR, the parameter System | Hardware | Module properties | Type = HSR must be
set in the SICAM Device Manager for the used LAN port group in the module properties of the CI-852x
module.
• In a HSR ring, a maximum of 512 unique source MAC addresses are allowed.
• 2 rings on the same CI-852x module must not be connected! (also not via switch, REDBOX, ...)
• On the same CI-852x module, devices from one ring are not visible in the other ring.

DC8-026-2, Edition 03.2022
13.20 HSR
Schematic configuration with 1 HSR ring
Schematic configuration with 2 HSR rings

DC8-026-2, Edition 03.2022
13.20 HSR
Schematic configuration Description

1 redundancy protocol for Ethernet network (1 ring)
• Only 1 type for Ethernet redundancy protocol is supported

on both ports of a LAN port group.
2 redundancy protocols for Ethernet networks (2 rings)
• Any Ethernet redundancy protocol can be selected for each

LAN port group.
• The Ethernet networks of the different LAN port groups of a
CI-852x module must not be connected.
2 redundancy protocols for Ethernet networks (1 ring + PRP)

LAN port group.

DC8-026-2, Edition 03.2022
13.20 HSR

2 redundancy protocols for Ethernet networks (1 ring + Line
Mode)

LAN port group.

LAN port group.
Note:
3 rings are shown in this picture - any Ethernet redundancy
protocol can be selected for each LAN port group.

LAN port group.
Note:

DC8-026-2, Edition 03.2022
13.20 HSR
13.20.2 Use Cases
HSR configuration with electrically connected devices
HSR configuration with electrically/optically connected devices
Recommended converter see: 13.20.3 Optical converters (media converters)

DC8-026-2, Edition 03.2022
13.20 HSR
NOTE
i For the above configuration, using CI-8522 in place of CI-8520 can reduce the dependency on external
optical media converters as CI-8522 has dedicated optical interface support.
13.20.3 Optical converters (media converters)
The use of converters and fiber-optic cables can significantly increase the distance between the base device
and I/O-rows and between the individual I/O-rows. Depending on the type of cable and converter used,
different cable lengths can be achieved.
The following optical converters can be used for network redundancy protocols:
Converter RSTP PRP HSR Line-Mode
Ruggedcom RMC ✓ * * ✓
Siemens SCALANCE X101-1 ✓ * * ✓
Siemens SCALANCE X101-1LD ✓ * * ✓
Phönix FL MC 2000E LC ✓ ✓ ✓ ✓
* ... Converter can only be used if the parameter "MTU-size" is set to 1494 bytes for all devices in the
communication network. (some devices do not support this parameter)
NOTE
i • Only converters that support a transmission speed of 100 Mbit/s can be used.
• For HSR and PRP, the converter used must compulsorily support the "oversized frames" (1528 bytes)
function!
• Switch (with learning function) can not be used as a media converter in an HSR ring.
(For this, any kind of switch and switch redundancy function in the switch should be deactivated,
which is usually not possible.)

DC8-026-2, Edition 03.2022
13.20 HSR
Siemens Ruggedcom RMC
MLFB: • LC socket for opt. connector
• 6GK6001-0AC01-0FA0
• 6GK6001-0AC02-0FA0
• 6GK6001-0AC03-0FA0
• Dimensions (WxHxD) 58 x 109 x 94

• Ambient temperature (operation): -40 °C ... 85 °C
• MLFB: 6GK6001-0AC01-0FA0
– Nominal voltage: VDC 24
– Voltage range: VDC 18 ... 36
• MLFB: 6GK6001-0AC02-0FA0
• MLFB: 6GK6001-0AC03-0FA0
– Nominal voltage: HI
– Voltage range: VDC 88-300 or VAC 85-264
• Fiber optic cable with LC connector
– max. length: 2 km
– Multimode
– Wavelength: 1300 nm
– 1x 100TX to 1x 100FX

DC8-026-2, Edition 03.2022
13.20 HSR
• 6GK6001-0AC01-0EA0
• 6GK6001-0AC02-0EA0
• 6GK6001-0AC03-0EA0

• MLFB: 6GK6001-0AC01-0EA0
• MLFB: 6GK6001-0AC02-0EA0
• MLFB: 6GK6001-0AC03-0EA0
– Singlemode
– 100TX to 1x 100FX

DC8-026-2, Edition 03.2022
13.20 HSR
MLFB: • MTRJ socket for opt. connector
• 6GK6001-0AC01-0DA0
• 6GK6001-0AC02-0DA0
• 6GK6001-0AC03-0DA0

• MLFB: 6GK6001-0AC01-0DA0
• MLFB: 6GK6001-0AC02-0DA0
• MLFB: 6GK6001-0AC03-0DA0
• LWL with MTRJ-connector
– Multimode
– 1x 100TX to 1x 100FX

DC8-026-2, Edition 03.2022
13.20 HSR
Siemens SCALANCE
Type: X101-1 • ST socket for opt. connector

MLFB: (ST/BFOC … straight tip/bayonet fiber optic connector)
• 6GK5101-1BB00-2AA3

• Nominal voltage: VDC 24
• Voltage range: VDC 18 ... 32
• Current consumption: 120 mA
• Fiber optic cable with ST connector
– max. length: 4 km at
– cross-section: 62,5/125 μm
– Multimode
– cross-section: 50/125 μm
– Multimode

DC8-026-2, Edition 03.2022
13.20 HSR
Type: X101-1LD • ST socket for opt. connector

MLFB:
• 6GK5101-1BC00-2AA3

• Nominal voltage: VDC 24
• Current consumption: 120 mA
• Fiber optic cable with ST connector
– Singlemode

DC8-026-2, Edition 03.2022
13.20 HSR
Phoenix FO Converter
Type: FL MC 2000E LC • LC socket for opt. connector

Order number:
• 2891056

• Nominal voltage: VDC 24 or 48
• Current consumption: 110 mA (VDC 24)
– Attenuation: 0,7 dB/km
– max. length: 3.3 km at

DC8-026-2, Edition 03.2022
13.21 RSTP
13.21 RSTP
RSTP (Rapid Spanning Tree Protocol) is a standardized network protocol for redundancy control of backup links
in network with fast enabling/disabling of backup links. The Rapid Spanning Tree Protocol (RSTP) is used in the
event of an error to reorganize the network structure. That means, after a network path fails, RSTP redirects
the data to a different path. The RSTP protocol is used for disabling redundant backup links in local network
and if necessary to enable backup links in case of failure of a link.
The maximum number of switches in a network will be calculated on the basis of the RSTP timer for "max age":
max. number of switches = max age - 1. That means, in a ring topology up to 39 devices can be connected.
The RSTP-Protocol is defined in the standard IEEE 802.1D, Edition 2004.
NOTE
i • RSTP can only be used with a CI-852x module.
• Only 1 redundancy protocol can be used per ring.
• 2 RSTP rings are possible for each CI-852x module.
• 2 redundancy protocols for Ethernet networks are possible for each CI-852x module (here 2x RSTP or
1x RSTP with HSR, PRP or Line Mode).
• The choice, which 2 of the 5 interfaces on the module are used for the RSTP-ring, is arbitrary.
• For RSTP, the parameter System | Hardware | Module properties | Type = RSTP must
be set in the SICAM Device Manager for the used LAN port group in the module properties of the
CI-852x module.
• In a RSTP-ring, a maximum of 512 unique source MAC addresses are allowed.
• 2 rings on the same CI-852x module must not be connected! (also not via switch, REDBOX, ...)
• On the same CI-852x module, devices from one ring are not visible in the other ring.
Schematic configuration with 1 RSTP ring

DC8-026-2, Edition 03.2022
13.21 RSTP

1 redundancy protocol for Ethernet network (1 ring)


LAN port group.
2 redundancy protocols for Ethernet networks (1 ring + PRP)

LAN port group.

DC8-026-2, Edition 03.2022
13.21 RSTP

2 redundancy protocols for Ethernet networks (1 ring + Line
Mode)

LAN port group.

LAN port group.
Note:

LAN port group.
Note:

DC8-026-2, Edition 03.2022
13.21 RSTP
13.21.2 Use Cases
Example 1: RSTP Configuration with Electrically Connected Devices
Example 2: 1 RSTP Ring with 2 RS900 as Root Bridge(s)
Example 3: 2 RSTP Rings with 2 RS900 as Root Bridge(s)

Default configuration for redundancy (the CP-8050 is doubled above).

DC8-026-2, Edition 03.2022
13.21 RSTP
Example 4: 1 RSTP Ring without RS900 Switch

(Cost-effective variant without switch; CP-8050 = "Root Bridge")
Example 5: 1 RSTP Ring with 2 RS900 as Root Bridge(s) incl. RS900 as Edge Port
(that means that a non-RSTP enabled device, for example a CP-8000, is connected to a RS900 )

DC8-026-2, Edition 03.2022
13.21 RSTP
Example 6: 1 RSTP Ring with 2 RS900 as Root Bridge(s) incl. RS900 as Edge Port
(that means that a non-RSTP enabled device, for example a CP-8000, is connected to a RS900 )

DC8-026-2, Edition 03.2022
13.21 RSTP
Example 7: RSTP with 2 Active CP-8050 and 2 RSTP Rings with Redundant Switch
Example 8: Combination of Line Mode with 2 Active CP-8050 and 1 RSTP Ring with Redundant Switch

DC8-026-2, Edition 03.2022
13.21 RSTP
NOTE
i For all the above mentioned use cases and involving long distance communication (more than 100 m),
Siemens recommends to use CI-8522 in place of CI-8520.
13.21.3 Parameter and Setting
With CP-8050, the parameters for RSTP must be set with the SICAM Device Manager as follows:
• System | Hardware
[DM_System_Hardware_GER, 1, en_US]
• Select communication module for Ethernet interface
• Module properties
[DM_System_Hardware_CI-852x_Moduleigenschaften_GER, 1, en_US]
• Parameters for port group RSTP

DC8-026-2, Edition 03.2022
13.21 RSTP
Parameter settings for RSTP networks
Parameter Name Settings

RSTP priority The priority defines the position of the bridge in the network.
The lower the value, the higher the priority. The bridge with the
highest priority is the root bridge.
Siemens recommends setting the priority of the root bridge to 0.
Siemens recommends setting the priority of the replacement
root bridge, which should be located right next to the root
bridge, to 4096. The replacement root bridge should replace the
root bridge in case of a failure.
Siemens recommends setting the priority of all other devices and
bridges to 32 768.
0 to 61 440, in increments of 4096
Standard setting = 32 768
RSTP maximum age The parameter MaxAge is preset to 20. This setting is specified as
the standard setting in the IEEE Std 802.1DTM - 2004 standard
and can be increased up to 40. The basic function of this param-
eter is that messages with a higher or the same age are
discarded. The aging itself is determined by the number of
switches passed through.
The MaxAge parameter must be defined in such a way that all
switches, taking this definition into account, must be able to
reach the root switch, even in the event of line interruptions or a
device failure.
6 to 40
RSTP hello time This time determines at what intervals the HelloTime telegrams
are transmitted.
1 or 2 s
Default setting = 2 s
RSTP forward delay The forwarding delay time is the maximum number of seconds
that a port waits until a new topology is distributed in the RSTP
network and until the status is changed from learning and
listening to forwarding .
4 to 30 s
Default setting = 15 s

DC8-026-2, Edition 03.2022
13.21 RSTP

RSTP Transmit hold counter Transmit Hold Count is a meter that applies to all ports of the
bridge. It limits the number of RSTP telegrams per port trans-
mitted in sequence and without delay. When this telegram is
transmitted, only one more telegram per second is transmitted.
For a highly meshed system, a Transmit Hold Count that is set
low will result in a significant slowing of the reconfiguration
when the root switch fails.
Siemens recommends not changing the Transmit Hold Count
setting.
1 to 10
RSTP Path Cost X* (Port 1) With RSTP, each device chooses a preferred route to the root
RSTP Path Cost X* (Port 2) bridge. This is the path with the lowest path costs. The path
costs indicate the quality of a line. Each connection between 2
devices/switches have certain path costs. The path costs of the
selected ports for the RSTP ring can be different for both ports.
The path costs to the root bridge are exchanged between neigh-
boring devices - the own path costs RSTP Path Cost X* are
added to the path costs. The higher the value, the worse the line.
A device preferably chooses the route with the lowest path costs
to the root bridge, the other is only taken if this fails!
With the parameter "RSTP Path Cost" it is possible to configure
preferred routes in the RSTP ring.
In IEEE Std 802.1D™ - 2004 this value is determined depending
on the speed. For example, path costs of 200 000 are defined for
100 Mbit.
Siemens recommends not to change this setting.
0 to 200 000 000
Standard setting = 200 000
Example 1: Example 2:
Here the CP-8050 will take the Here the CP-8050 will take the
left path because the path costs right path because the path
to the root bridge (SIP5 with costs to the root bridge (SIP5
priority 4096) are 400 000. The with priority 4096) are 202
other route would have higher 000. The other route would
costs and is therefore only have higher costs and is there-
taken if the preferred route fore only taken if the preferred
fails. route fails.

DC8-026-2, Edition 03.2022
13.21 RSTP
Parameter settings for networks (Common)

Parameter name 802.1x suppli- SICAM A8000 CP-8031/CP-8050 supports IEEE 802.1X as suppli-
cant cant with EAP_TLS (EAP mode). It is not possible to use suppli-
cant and authenticator functionality on the same port. 802.1x
functionality only supports RSA certificates.
(For details see SICAM A8000 Series Administrator Security
Manual)
TCP minimum expected acknowl- Depending on the transmission medium for LAN /WAN/GPRS/
edgment time UMTS/LTE; ... the parameter TCP minimum expected
acknowledgment time must be set accordingly if necessary.
LAN/WAN >=250 ms. GPRS/UMTS/LTE >=1000 ms.
0 ms to 3000 s
Default setting = 250 ms
Maximum transmission unit Ethernet MTU (Maximum Transmission Unit).
68 to 9000 Bytes
Default setting = 1500 byte

DC8-026-2, Edition 03.2022
13.22 PRP
13.22 PRP
PRP (Parallel Redundancy Protocol) is a redundancy protocol for Ethernet networks which is specified in the
norm IEC 62439-3. In comparison to conventional redundancy procedures, for example, RSTP (Rapid Spanning
Tree Protocol, IEEE 802.1D-2004), PRP offers a switchover without interruptions what avoids a dead time in
the event of a fault, and thus the highest availability.
Previous redundancy methods are based on mechanisms where the power-system components (switches and
bridges) agree with each other and find the best communication path for normal operation.
In the event of a fault, for example, in a cable, an optical fiber, or in case of a switch failure, the interruption is
detected and alternative paths are found in the network and connected. No communication can take place
during this switching procedure. Depending on the size and on the configuration of the Ethernet network, this
state can last for 10 ms up to around 1 s. A protocol extension in the end device is not necessary in this case
because the protocol is implemented in the switches.
PRP adopts a different approach.
The redundancy procedure is generated in the end device itself. The procedure is simple: The redundant end
device has 2 Ethernet interfaces with the same address (DAN, Double Attached Node). Then, the same indica-
tion is sent twice, with PRP (parallel) via 2 separated networks. Both indications are unambiguously identified
with a sequence number.
The receiver takes the information that arrives first, stores the ID of the information in a duplicate filter using
the source address and the sequence number of the information. Thereby, the receiver recognizes the 2nd
redundant information and discards it.
[Ethernet_Redundanz_PRP, 1, --_--]
If the 1st indication is missing, the 2nd indication with the same information arrives via the other network.
This redundancy avoids a switchover of the network and is therefore a redundancy without interruption. The
end device does not forward any indication to the other network.
Since this procedure is realized in the Ethernet layer (same MAC address), it is transparent and can be used by
all Ethernet informative data protocols (IEC 61850, DNP, other TCP/IP based protocols).
Topology, performance, and latency may be different for both networks, but latencies may vary only to a
certain extent.
In addition, it is possible to use one of the 2 networks for the transmission of not redundant indications. To do
so, connect a SAN (Single Attached Node) device to a network. In this way, a PRP end device can communicate
with a SAN end device (in a not redundant way). If you wish to connect a SAN end device in a redundant way
to a PRP system, use a REDBOX (redundancy box). This REDBOX provides PRP functionality externally as an

DC8-026-2, Edition 03.2022
13.22 PRP
inline device. However, the PRP procedure also presents a disadvantage: You are buying the increased redun-
dancy function at the cost of a duplicate network (2x switches, cables).
There are 2 versions of PRP: PRP-0 and the successor PRP-1. Siemens implements PRP-1.
Supported Standard Description
IEC 62439-3 Edition 2.0 Industrial communication networks - High availability automation networks
(2012-07) - Part 3: Parallel Redundancy Protocol (PRP) and High-availability Seamless
Redundancy (HSR)
In a PRP structure all data are transmitted at the same time via 2 independent networks (LAN A and LAN B).
Topology, performance and latency can be different in both networks, but latency may only differ within a
certain range.
CP-8050 uses the "duplicate discard" mode in PRP, that means that duplicates are discarded and not passed to
the TCP/IP stack.
For the CI-852x module, the lower numbered Ethernet port is the LAN A port (for example: X1 = LAN A, X2 =
LAN B).
NOTE
i Both networks must not be connected, as otherwise an Ethernet double addressing takes place and this can
lead to malfunctions!
The advantage of PRP over other protocols is, that in the case of a communication failure within one network,
there is a bumpless switch over and hence no loss of data. Disadvantage of PRP is the operation of 2 inde-
pendent networks.
Depending on the connection PRP distinguishes the following device types:
• Dual Attached Nodes (DAN)

Devices which are connected with both networks. There is a separate interface for each network connec-
tion.
• Single Attached Nodes (SAN) Devices which are connected with just one network.
• Virtual Double Attached Nodes (VDAN)

VDANs are devices with just one interface, but which are connected with both networks via a redundancy
box (RedBox).

DC8-026-2, Edition 03.2022
13.22 PRP
NOTE
i • PRP can only be used with a CI-852x module.
• Only 1 redundancy protocol can be used per LAN port group.
• 2 separated PRP networks are possible for each CI-852x module.
• 2 redundancy protocols for Ethernet networks are possible for each CI-852x module (here 2x PRP or 1x
PRP with HSR, PRP or Line Mode).
• The choice, which 2 of the 5 interfaces on the module are used for the PRP network, is arbitrary
• For PRP, the parameter System | Hardware | Module properties | Type = PRP must be
set in the SICAM Device Manager for the used LAN port group in the module properties of the CI-852x
module.
• In a PRP network, a maximum of 512 unique source MAC addresses are allowed.
• The networks of the 2 LAN port groups on the same CI-852x module must not be connected!
(also not via switch, REDBOX, ...)
• On the same CI-852x module, devices from one ring/network are not visible in the other ring/network.
• PRP is monitored every second with a message. A failure of the monitoring is signaled by a warning.
• For the CI-852x module, the lower numbered Ethernet port is the LAN A port (for example: X1 = LAN
A, X2 = LAN B)
Schematic configuration with 1 RSTP ring

1 redundancy protocol for Ethernet network (1 x PRP)

2 redundancy protocols for Ethernet networks (PRP + PRP)


DC8-026-2, Edition 03.2022
13.22 PRP

2 redundancy protocols for Ethernet networks (Ring + PRP)

LAN port group.
2 redundancy protocols for Ethernet networks (PRP + Line

Mode)

LAN port group.

DC8-026-2, Edition 03.2022
13.22 PRP

3 redundancy protocols for Ethernet networks (PRP + 2 Rings)

LAN port group.
4 redundancy protocols for Ethernet networks (2 x PRP + 2

Rings)

LAN port group.

DC8-026-2, Edition 03.2022
13.22 PRP
13.22.2 Application example

DC8-026-2, Edition 03.2022
13.23 Line Mode
13.23 Line Mode
13.23.1 Line Mode
Line Mode is a Siemens-specific network redundancy protocol used in redundancy configurations at the
Ethernet level.
The line mode serves as a "redundant cable connection" to one or two switches.
The CI-852x module for CP-8050 has 2 electrical Ethernet interfaces that can be used in line mode. In line
mode, the CP-8050 can communicate via 2 Ethernet cables, but not at the same time. The 2nd channel always
serves as a reserve. This results in the network structure shown in following Figure, which shows the connec-
tion of the two connections to different switch ports.
The two physical connections are monitored. Therefore, when a connection is interrupted, a corresponding
message can always be generated and submitted.
Since the method is implemented in the Ethernet layer, it is transparent and usable for all Ethernet user data
protocols (IEC 61850, DNP, other TCP/IP-based protocols).
In line mode, the integrated switch for the Ethernet ports is controlled so that only 1 port is always switched to
"forwarding".
Line Mode:
• The data link layer (Layer-2) is always set up for both ports.
• The Ethernet packet forwarding is only performed on the port set to "Forwarding". The other port is set to
"Blocking".
• The basic system element firmware of the CP-8050 controls the operation of each port for the Ethernet
packet distribution:
– deactivated (= "Blocking")
– activated (= "Forwarding")
(By default Port-0 is set to "Forwarding" and Port-1 to "Blocking")
If the Ethernet connection ("Link Down") of the port set to "Forwarding" fails, the protocol element immedi-
ately sets the failed port to "Blocking" and the other port to "Forwarding".

DC8-026-2, Edition 03.2022
13.23 Line Mode
After enabling (= switching on "Forwarding") a port, special Ethernet packets are sent out, so that the switches
in the network quickly learn the "new ways" for the reachability of the MAC address of the activated ports.
In addition, a RARP (reverse ARP) is sent with its own IP address.
This method is Siemens specific and the Ethernet packets used are transmitted with Ethertype = 0x8827.
Channel Switching in Line Mode

When the active compound, the one which transmits the data between the device and the external switch, is
interrupted, the interruption is detected and reported. Simultaneously, with the detection of the interruption,
a switchover to the second channel (another port) is performed, so that the data traffic is continued almost
uninterrupted. The interrupt message is then transmitted over the reserve channel.
Port-0 is the Ethernet port on the CI-852x module with the lower interface number (e.g.: X1)
Port-1 is the Ethernet port on the CI-852x module with the higher interface number (e.g.: X3)
Failure of the External Switch

If both connections are connected to ports in different switches, the failure of an external switch does not lead
to a connection interruption to a control center. In this case, all devices that had actively established a connec-
tion via the failed switch, will switch to their second connection, which is connected to another switch and the
operation can be continued.
The external switches themselves are usually connected via a ring structure, so that they realize their own
redundancy with each other.
Switch Over Time

The switching time to the second connection in the event of a connection failure is approx. 1 ms.

DC8-026-2, Edition 03.2022
13.23 Line Mode
This applies to the Line Mode operating mode if both ports of the CI-852x module are connected to external
switches.
Interface RJ45
For Ethernet connections with RJ45, which are operated in line mode, both interfaces are not operational at
the same time. The connection is established automatically when the connection to a switch/partner is
detected. The second port remains inactive until the connection of the active port is lost. Then the connection
is automatically resumed on the second port. The respective non-active channel is monitored with regard to
the link status.
13.23.2 Use Cases
Example 1: Combination Line Mode with RSTP Mode on 2 Redundant Switches

DC8-026-2, Edition 03.2022
13.23 Line Mode
Example 2: Combination Line Mode with RSTP Mode on 1 Switch
Example 3: Combination of Line Mode with 2 Active CP-8050 and 1 RSTP Ring with Redundant Switch

DC8-026-2, Edition 03.2022
13.23 Line Mode
NOTE
i For all the above mentioned use cases and involving long distance communication (more than 100 m),
Siemens recommends to use CI-8522 in place of CI-8520.
13.23.3 Configuration information
• Line Mode can only be used with a CI-852x Ethernet Interface module
• For each CI-852x Ethernet Interface module only one Line Mode is permitted
• For each CI-852x Ethernet Interface module, only one redundancy protocol is possible for Ethernet
networks (here only Line Mode).
• The choice, which 2 of the 5 interfaces on the module are used for the Line Mode, is arbitrary
• The Line Mode must be activated for the used CI-852x Ethernet interfaces.
The relevant parameter can be found under [BSE] System settings | Network settings |
Interface | Mode = Line Mode.

DC8-026-2, Edition 03.2022
13.24 VLAN
13.24 VLAN
Virtual Local Area Networks (VLANs) are logical networks that are implemented on a physical LAN.
In this way, several logically separated networks can be operated for different areas on one physical network.
The technical basis for VLANs is described in the IEEE 802.1Q standard.
To be able to screen and if necessary prioritize the data traffic of a virtual LAN against the other network
parties, the data packets must have a corresponding identification. For this, the MAC-Frames are expanded
with an additional feature (a “tag”). The corresponding procedure is therefore also called Frame Tagging.
The Tagging is realized with an additional field in the MAC-Frame. In this field, two items of information essen-
tial for the virtual LAN are contained:
• VLAN-ID
The virtual LAN is identified with an unambiguous number. This ID determines the association of a data
packet to a logical (virtual) LAN. With this 12-bit value, up to 4094 different VLAN's can be defined (the
VLAN-IDs “0” and “4095” are reserved or not allowed).
• Priority
The priority of a VLAN-identified data packet is flagged with a 3-bit value. Thereby “0” stands for the
lowest priority, the “7” for highest priority. Data packets without VLAN Tag are handled with the priority
“0”.
13.24.2 Sample Applications
One application is that several logical VLANs are 'transmitted' to a CP-8050 over a single physical connection.
In the switch, the individual VLANs are then "switched through" to different physical switch ports.
[dw_use_case_vlan_1, 1, --_--]
The switch is a "VLAN aware switch" which processes the VLAN information (VLAN tag) in the Ethernet header.
Another application example is the integration of the CP-8050 in a physical ring, where different "logical rings"
are implemented via VLANs.

DC8-026-2, Edition 03.2022
13.24 VLAN
[dw_use_case_vlan_2, 1, --_--]
13.24.3 Configuration
On the CP8050, VLANs can be added to any simple Ethernet interface and to Ethernet switching groups. The
HSR and PRP switching groups are not supported in the first version.
The configuration is done in the Device Manager under System | Communication | LAN interfaces
| VLAN interfaces
The following parameters can be set for a VLAN:
• Port group
This parameter can be used to select the Ethernet interface or the switching group to which a VLAN is to
be added
• VLAN ID
This parameter can be used to specify the ID that is to be assigned to the VLAN. The valid range of values
is [1 ... 4094]
• VLAN Priority
This parameter can be used to specify the 3-bit priority value for VLAN packets that are sent via this VLAN.
The valid range of values is [0 ... 7]

DC8-026-2, Edition 03.2022
13.24 VLAN
Example
[sc_VLAN_config_1, 1, en_US]
The configured VLANs can then be used just like the physical interfaces for configuration of the LAN inter-
faces:
[sc_VLAN_config_2, 1, en_US]

DC8-026-2, Edition 03.2022
13.25 SNMP
13.25 SNMP
SNMP (Simple Network Management Protocol) is a network protocol used to monitor or control network
components (e.g. Router, Switches, Server or Automation units (SPS, RTUs …)) from a central station. The
protocol controls the communication between the monitored devices (SNMP Agents) and the monitoring
station (SNMP Manager).
Due to the integration of an SNMPv3 Agent in SICAM A8000 CP-8050 it is possible to read out SNMP Variables
(stored in the MIB = Management Information Base) via network with a standard network management soft-
ware (SNMP Manager). The information and data transmitted with SNMP are displayed according to their
functionality in the SNMP Manager in some kind of tree structure.
CP-8031/CP-8050 supports the security models USM (User-based Security Model) and TSM (Transport Security
Model) via TLS. USM and TSM are not supported at the same time, both must be selected via parameters. TSM
is supported from CPCI85 FW version 4.70 upwards.
[dw_A8000_snmp_config_8050, 1, --_--]
The SNMP protocol (Agent) is integrated in the firmware of the master module.
SNMP variables retrievable via:
• Standard SNMP network management software
• SCADA system with integrated SNMP manager.
• SICAM SCC
13.25.2 Functions
Function SNMP
SNMP
SNMPv2 –
SNMPv3 ✓
• SNMP queries from SNMP Manager are only supported according to SNMPv3 ✓
• Traps are transmitted to up to 5 SNMP managers in accordance with SNMPv3 ✓
SNMP Agent:
• Support of max. 4 Users ✓

DC8-026-2, Edition 03.2022
13.25 SNMP
Function SNMP
Supported Ports USM:

Port 161: SNMP, Incoming, UDP ✓
Port 162: SNMP Trap, Outgoing, UDP ✓
Supported Ports TSM:

PORT 10161: SNMP, Incoming, TCP ✓
PORT 10162: SNMP Trap, Outgoing, TCP ✓
SNMP-functions
GET (to request a management data record) ✓
GETNEXT (to request the subsequent data record; to pass through tables) ✓
GETBULK (to request several data records at once; e.g. several rows of a table) 369 –
RESPONSE (answer to GET, GETNEXT, GETBULK) ✓
TRAP (spontaneous data from SNMP Agent to SNMP Manager) 370 ✓
Supported MIBs
sicamRTUs ✓
MIB-2 (RFC1213) ✓
Ethernet-MIB (RFC3635) ✓
Host-Resources-MIB (RFC2790) ✓
USM-MIB (RFC2574) ✓
VACM-MIB (RFC2575) ✓
DGPI-MIB (Siemens Energy Management Digital Grid Product Inventory MIB) ✓
Supported SNMP variables MCPU (rough overview)

Plant name ✓
Firmware Revision ✓
Uptime ✓
Port status ✓
central error table ✓
TRAP “History” (Reading back of the last sent TRAPs)
• max. Number of saved traps: 50 ✓
Asset Management (Inventory data of Siemens Energy Management Digital Grid devices and soft- ✓
ware products)
Supported SNMP-Variables CCPU, PRE, PE ✓
SNMPv3 “Security Level”

authPriv (Communication with authentication and encryption) ✓
SNMPv3 - USM “auth Protocol” (Protocol for authentication "User name, Password")
MD5 (Message Digest Algorithm 5) ✓
SHA, SHA1, SHA2 (Secure Hash Algorithm) ✓
369 available from SNMPv2

370 Traps are transmitted with Security Level = "authPriv" with username = "Trap" and the configured passwords for authentication and
encryption

DC8-026-2, Edition 03.2022
13.25 SNMP
Function SNMP
SNMPv3 - USM “Privacy Protocol” (Protocol for encryption)

DES (Data Encryption Standard) ✓
AES (Advanced Encryption Standard) ✓
SNMPv3 - TSM "Certificate Signatur algorithmus"

SHA1 ✓
SHA256 ✓
Security: Encrypted storage of passwords

Security: Encrypted storage of passwords ✓
13.25.3 Configuration with SICAM Device Manager
General settings for USM and TSM

The pages for configuration can be found under HOME | Communication | Server services | Simple Network
Management Protocol (SNMP) - Common
[sc_Selection, 1, en_US]
• User configuration:
– A maximum of 4 users is possible
– A user is only active if the parameter User enabled is set to yes.
– If the parameter Write enabled is set to yes, the user can also execute "SET" commands.

DC8-026-2, Edition 03.2022
13.25 SNMP
• Trap configuration:
– A maximum of 5 users is possible
– Trap only becomes active when a server is defined
– To delete a trap server, you have to delete it from the Trap server configuration.
• The firewall does not have to be configured, it is done automatically.
• If necessary, complete the Access list configuration.
[sc_Accesslist, 1, en_US]
A maximum of 2 addresses can be added, if more than 2 addresses are needed, they can be released via
the firewall.
If the access list is empty, anyone can make an SNMP request.
If there is an entry, SNMP requests can only be made from the IP addresses on this list.
USM configuration
• In the Simple Network Management Protocol (SNMP) – Common area, select the security model USM
[sc_SecurityModel, 1, en_US]
• In the USM Crypto settings area, add new crypto settings and define them.
[sc_AddCrypto, 1, en_US]
• Select the desired LAN interface under SNMP Agent Configuration.
[sc_AgentConfig, 1, en_US]

DC8-026-2, Edition 03.2022
13.25 SNMP
• Add the user(s) under User Configuration. A maximum of 4 users can be configured.
In the User enabled column, you can enable or disable the user.
In the figure below, only the users testuser1 and testuser2 can send requests.
In the Writing enabled column, you define whether the user has read access (GET) as well as write
access (SET).
In the following picture, user testuser1 can select SET and GET, testuser2 can only select GET crypto
settings.
[sc_UserConfig, 1, en_US]
Traps
• To activate traps, you have to add a trap server in the Simple Network Management Protocol (SNMP) –
Traps area. Maximum 5 users are possible
Configure LAN interface and Crypto settings.
[sc_Traps, 1, en_US]
TSM configuration
NOTE
i The SAN (Subject Alternative Name) from the certificate of the remote station must be set as Security
name (IP, DNS oder email).

DC8-026-2, Edition 03.2022
13.25 SNMP
• In the Simple Network Management Protocol (SNMP) – Common area, select the security model TSM
[sc_ChooseCerts, 1, en_US]
• Import in SICAM WEB under HOME | Certificates | Certificates and Keys the local certificate.
[sc_localCert, 1, en_US]
• Import in SICAM WEB under HOME | Certificates | Certificates authorities the CA certificate (Certifica-
tion Authority).
[sc_CA, 1, en_US]
• Return to the SICAM Device Manager and select in the Simple Network Management Protocol (SNMP)
– Common area, security model TSM
• Select the wanted TSM Certificate and TSM Certificate Authority.
[sc_ChooseCerts, 1, en_US]

DC8-026-2, Edition 03.2022
13.25 SNMP
• The SNMP Agent Configuration is identically with USM.
• User Configuration
[sc_userConfig TSM, 1, en_US]
13.25.4 Configuration with the SICAM TOOLBOX II
NOTE
i SICAM TOOLBOX II supports only the configuration of USM (User-based Security Model). Use the SICAM
Device Manager for the configuration of TSM (Transport Security Model).
Configuration of an interface for SNMP

The selection and configuration of the interface, on which the SNMP-Manager is connected, takes place under
[BSE] System settings | Network settings | Interface . Choose a LAN interface (E.G. LAN 1)
under Interface , choose the hardware interface on which the SNMP Manager will be connected (e.g. CP-
X3) and enter IP address and Subnet Mask of this interface.
Enable SNMP
SNMP is enabled for the system under [BSE] System settings | Network settings | Services
| SNMP | SNMP Agent . Afterwards enter the IP address of the PC/Laptop with the SNMP Manager under
SNMP Access IP address 1 .
Crypto settings for SNMP V3 User

In CP-8050 4 SNMP users are available to which different crypto settings can be assigned. These settings can
be made under [BSE] System settings | Network settings | Services | SNMP | Crypto
settings .

DC8-026-2, Edition 03.2022
13.25 SNMP
Configuration of a SNMP V3 User

The configuration of a SNMP V3 users is made under [BSE] System settings | Network settings |
Services | SNMP | User | User configuration . Specify a name, assign a crypto setting to this
user name and release it.
Generate and display firewall

Choose in OPM the system element (M:CP-8050/CPCI85), open the popup menu and click on Generate Fire-
wall.

DC8-026-2, Edition 03.2022
13.25 SNMP
Open the firewall under [BSE] System settings | Security | Firewall (Whitelist). Check if
Port 161; SNMP is set.
Load changes to the target system

Now you can load the SNMP configuration into the target system (Target system | SICAM 1703 | Load
parameter ). After a Restart the SNMP-Manager can communicate via SNMP with CP-8050.
Enable SNMP traps

To use the Trap-function you have to enable the desired traps under [BSE] System settings |
Network settings | Services | SNMP | Traps .

DC8-026-2, Edition 03.2022
13.25 SNMP
NOTE
i In the SNMP Manager, the user must be configured with the user name "Trap" and the passwords of the
Traps/Crypto settings.
Configure SNMP traps

The IP address and interface, to which the traps shall be sent (e.g. PC with SNMP-Manager), must be set under
[BSE] System settings | Network settings | Services | SNMP | Traps | Trapserver
configuration .
Generate and display firewall for traps

Choose in OPM the system element (M:CP-8050/CPCI85), open the popup menu and click on Generate Fire-
wall.

DC8-026-2, Edition 03.2022
13.25 SNMP
Open the firewall under [BSE] System settings | Security | Firewall (Whitelist). Check if
Port 162; SNMP Trap is set.
NOTE
i From then on the traps will be sent spontaneously from CP-8050 to the SNMP manager.
TRAP-History
For selected SNMP traps, a limited number of changes can be read out via the SNMP variable "TRAP history".
The 50 most recently sent traps are entered in an SNMP table and can be read out with GET/GETBULK
GETNEXT (see SNMP Variables).
NOTE
i Note: The TRAP history is deleted on reset or restart!
13.25.5 SNMP MIBs – Management Information Base
A MIB (management information base) describes the information, which can be retrieved or modified via a
network management protocol (e.g. SNMP). These informations are named "Managed Objects". These are
description files, in which the single values are listed in table form. A MIB is specific for each component.

DC8-026-2, Edition 03.2022
13.25 SNMP
13.25.5.1 Download of the MIB-Files

The MIB files can be downloaded from the SIOS Portal (Siemens Industry Online Support) https://
support.industry.siemens.com :
• Search for SICAM RTUS MIB in the SIOS Portal
• Click in the list of results on SICAM RTUs SNMP MIB File (Download)
After the download you get the file SICAMRTUs_SNMP_MIB_V06.00.00.zip.
• Save this file to the computer where the MIB Browser is installed (for example, C:/Siemens) and unpack
the MIB files.
13.25.5.2 Import the MIB files in the MIB Browser

The import of the MIB files into your MIB browser must be done in the following sequence:
• Import of SIEMENS-SMI.mib
• Import of sicamRTUs.mib
• Import of digitalGridProductInventory.mib
• Import of digitalGridSecurityMonitoring.mib
• Import of emergencyUser.mib
• Import of RFC1213-MIB.mib (optional)
• Import of RFC3635_mib.mib (Ethernet-MIB, optional)
• Import of RFC2790_mib.mib (Host-Resources-MIB, optional)

Beside a standard MIB browsers you can load the MIB files also with the control center system SICAM SCC and
250 SCALA.
13.25.5.3 MIB: MIB-2 (RFC1213)

By means of this standard MIB, basic data of a CP-8050 system can be read out. The corresponding object ID is
called:
Path: iso.org.dod.internet.management.MIB-2.system.sysDescr (1.3.6.1.2.1.1.1)

DC8-026-2, Edition 03.2022
13.25 SNMP
Following objects are in this Object ID:

Objects Description / Example
Vendor Siemens AG
ProductFamily SICAM A8000
ProductName CP-8050
OrderNumber 6MF28..... (MLFB number)
HwVersion HW version of the device
FwVersion FW version of the device (e.g.: FW: 01.PB)
SwVersion SW version of the device
ProductSerialNumber (e.g.: SN: GC8-050--_88_BF1702....)
13.25.5.4 sicamRTUs
Path: iso.org.dod.internet.private.enterprises.siemens.sicamRTUs (1.3.6.1.4.1.22638.7)

DC8-026-2, Edition 03.2022
13.25 SNMP
13.25.5.5 MIB: dgpiMIB

(Digital Grid Product Inventory)

DC8-026-2, Edition 03.2022
13.25 SNMP
This private MIB implements the "Enterprise Asset Management (EAM)" domain model for all products of EM
DG PRO.
Path: iso.org.dod.internet.private.enterprises.siemens.siemensCommon.dgpiMIB (1.3.6.1.4.1.22638.11.1)
Object group 1: dgpiProdIdentity

This collection contains the supplier name ("Siemens AG") and some customer-related information at product
level, such as asset UUID (inventory number), customer name, product location, and geo-location. These
customer-related objects can only be read via SNMP. That is, they must be configured by the customer in other
ways (e.g., product-specific engineering tool, Web UI, etc.)
With the SICAM TOOLBOX II, this data can be entered with the following parameter: [BSE] System
settings | Device settings
Sub-Object group Objects Description
- dgpiVendorName Siemens AG
dgpiAssetUuid
dgpiCustomerName
dgpiLocationName
dgpiGeoPositionLatitude
dgpiGeoPositionLongi-
tude
dgpiGeoPositionAltitude
Object group 2: dgpiProdComp

This collection contains the product & component table (dgpiProductComponentsTable), which is the
most important object of the MIB. The product and its components are represented by lines in this table. The
first line is always occupied by the product, the following lines by the components. The order of the compo-
nents in the rows of this table is not mandatory.

DC8-026-2, Edition 03.2022
13.25 SNMP

dgpiProductComponent- dgpiProdCompIndex Index of the table line
sTable dgpiProdCompContai- Identifies the containment hierarchy of the product and
nedIn its components. It's zero in the product line because the
product is at the top of the hierarchy.
In the component rows, it corresponds to the value of
the object dgpiProdCompIndex of the product line (if
the component is directly from the product) or its
"parent" component row (if the component is contained
in a "parent" component).
dgpiProdCompClass identifies the class of the product or component of this
line
e.g.: hwProduct
dgpiProdCompName contains the name of the product or component
e.g.: SICAM A8000 CP-8050
dgpiProdCompDescrip- contains a brief description of the product or component
tion
dgpiProdCompOrder- contains the MLFB number of the product or component
Number e.g.: 6MF28050AA00
dgpiProdCompSerial- contains the serial number of the product or component
Number e.g.: BF1612034390
dgpiProdCompVersion contains the version number of the FW, HW, SW or the
configuration
dgpiProdCompHwSlot contains the number or name of the slot where the hard-
ware component is located
dgpiProdCompManu- contains the date of manufacture of the HW product or
factDate component
dgpiProdCompConfi- contains the last modification date and the last modifica-
gLastChange tion time of the updatable component
- dgpiProductCompTable- contains the date and time of the last change of each
LastChange dgpiProductComponentsTable object.
The change includes creation, removal and modification
of table rows.
This is in contrast to the dgpiProdCompLastChange
Change object, which refers to changing of rows, that
represent certain component classes.
Object group 3: dgpiNotifications

This group defines a notification (SNMPv2 trap, SNMPv3 indication). This notification can be enabled/disabled
in the Sicam Device Manager with the parameter Communication | Server Services | Simple Network
Management Protocol (SNMP) - Traps | DGPI traps enabled.

- dgpiNotificationsEna- enables/disables the sending of this notification
bled
dgpiNotificationProd-
CompChanged
Object group 4: dgpiConformance

This group contains compliance instructions. It defines that the implementation of the product identity and
product & component group objects is mandatory. The implementation of the objects of the notification

DC8-026-2, Edition 03.2022
13.25 SNMP
group is optional. The latter takes into account that not all SNMP agent implementations are prepared for
sending SNMP traps or indications.
dgpiCompliances dgpiCompliances
dgpiGroups dgpiProductIdenti-
tyGroup
dgpiProdCompGroup
dgpiNotifObjectsGroup
dgpiNotifNotifica-
tionsGroup
13.25.5.6 MIB: dgsmMIB

(Digital Grid Security Monitoring)
Path: iso.org.dod.internet.private.enterprises.siemens.siemensCommon.dgsmMIB (1.3.6.1.4.1.22638.11.2)
[dw_SNMP_MIB_Structure_dgsmMIB, 1, --_--]
Object group 1: dgsmNotifications

This group defines a notification (SNMPv2 trap, SNMPv3 indication). This notification can be enabled/disabled
in the Sicam Device Manager with the parameter Communication | Server Services | Simple Network
Management Protocol (SNMP) - Traps | DGPI traps enabled.
- dgsmNotificationsEna- enables/disables the sending of this notification
bled
dgsmLogAuditNotifica-
tion

DC8-026-2, Edition 03.2022
13.25 SNMP
Object group 2: dgsmLogAuditHist

This collection contains the product and component table (dgsmLogAuditHistTable), which is the most impor-
tant object of the MIB. The product and its components are represented by lines in this table. The first line is
always filled with the product, the following lines with the components. The order of the components in the
rows of this table is not mandatory.
dgsmLogAuditHistTable dgsmLogAudit Index of the table line
dgsmLogAuditNotifSe- sets the severity of the logaudit notification. The
verity enumeration contains two values: alert(1), warning(4)
dgsmLogAuditNotifVer- contains the version information of the logaudit notifica-
sion tion
dgsmLogAuditNotifTi- contains the date and time when the logaudit notifica-
meStamp tion was initiated
dgsmLogAuditNotifHost- contains the name of the host that issued the logaudit
Name notification
dgsmLogAuditNotifApp- contains the name of the application that issued the
Name logaudit message
dgsmLogAuditNo- contains the message identifier of the logaudit notifica-
tifMsgId tion
dgsmLogAuditNotifMes- contains the message body of the logaudit notification
sage
dgsmLogAuditNumEn- contains the number of entries (rows) of the dgsmLo-
tries gAuditHistTable
dgsmLogAuditEldes- contains the index to the entry of the dgsmLogAuditHist-
tEntry Table that stores the oldest LogAudit notification
dgsmLogAuditLates- contains the index to the entry of the dgsmLogAuditHist-
tEntry Table in which the latest LogAudit notification is stored
Object group 3: dgsmConformance

This group contains compliance instructions. It defines that the implementation of the product identity and
product & component group objects is mandatory. The implementation of the objects of the notification
group is optional. The latter takes into account that not all SNMP agent implementations are prepared for
sending SNMP traps or indications.
dgsmCompliances dgsmCompliances
dgsmGroups dgsmProductIdenti-
tyGroup
dgsmProdCompGroup
dgsmNotifObjectsGroup
dgsmNotifNotifica-
tionsGroup
13.25.6 SNMP Variables
13.25.6.1 Introduction
The current state of the supported SNMP variables can be read out by the SNMP manager with the SNMP serv-
ices GET / GETNEXT / GETBULK. CP-8050 supports the query of SNMP variables from different SNMP managers
with different IP addresses. The SNMP response is sent back to the SNMP manager from which the SNMP
request (GET / GETNEXT / GETBULK) was received.

DC8-026-2, Edition 03.2022
13.25 SNMP
SNMP variables of the following MIB files are supported:
• MIB-2 (RFC1213)
• sicamRTUs
• Ethernet-MIB (RFC3635)
• Host-Resources-MIB (RFC2790)
• USM-MIB (RFC2574)
• VACM-MIB (RFC2575)
• DGPI-MIB (Siemens Energy Management Digital Grid Product Inventory MIB)
13.25.6.2 SNMP Variables for MIB: sicamRTUs
General Information
GET NEXT / Response
TRAP
GETBULK / Response
<sicamRTUs.MIB>
GET / Response
SNMP address object identi- Data
fier (OID) Object description type
1.3.6.1.4.1.22638.7.1 SICAM RTUs – General Information ✓ ✓
1.3.6.1.4.1.22638.7.1.1 SICAM RTUs – General Information - device- ✓ ✓
specific
1.3.6.1.4.1.22638.7.1.1.1 Plant name 371 Text ✓ ✓
1.3.6.1.4.1.22638.7.1.1.2 Plant ID Text ✓ ✓
1.3.6.1.4.1.22638.7.1.1.3 System-technical region number Integer ✓ ✓
1.3.6.1.4.1.22638.7.1.1.4 System-technical component number Integer ✓ ✓
1.3.6.1.4.1.22638.7.1.2 SICAM RTUs – Firmware revision ✓ ✓
1.3.6.1.4.1.22638.7.1.2.1.1.2 Firmware instance Text ✓ ✓
1.3.6.1.4.1.22638.7.1.2.1.1.3 System element name Text ✓ ✓
1.3.6.1.4.1.22638.7.1.2.1.1.4 Firmware-Revision Text ✓ ✓
1.3.6.1.4.1.22638.7.1.2.1.1.5 System element description Text ✓ ✓
1.3.6.1.4.1.22638.7.1.2.1.1.6 System element address Text ✓ ✓
1.3.6.1.4.1.22638.7.1.2.1.1.7 Hardware number Text ✓ ✓
1.3.6.1.4.1.22638.7.1.2.1.1.8 Firmware number Text ✓ ✓
1.3.6.1.4.1.22638.7.10 SICAM RTUs – diagnostic information ✓ ✓
1.3.6.1.4.1.22638.7.10.1 SICAM RTUs – diagnostic information – central ✓ ✓
error table
1.3.6.1.4.1.22638.7.10.1.1 Sum diagnosis table | Fault 1 “Class internal” Text ✓ ✓
1.3.6.1.4.1.22638.7.10.1.2 Sum diagnosis table | Fault 2 “Class external” Text ✓ ✓
1.3.6.1.4.1.22638.7.10.1.3 Sum diagnosis table | Fault 3 “Class communication” Text ✓ ✓
1.3.6.1.4.1.22638.7.10.1.4 Sum diagnosis table | Fault 4 “Class test” Text ✓ ✓
1.3.6.1.4.1.22638.7.10.1.5 Sum diagnosis table | Fault 5 “Class warning” Text ✓ ✓
1.3.6.1.4.1.22638.7.10.1.6 Sum diagnosis table | Fault 6 “Class module failure” Text ✓ ✓
1.3.6.1.4.1.22638.7.10.1.7 Sum diagnosis table | Fault 7 “Class failure” Text ✓ ✓
1.3.6.1.4.1.22638.7.10.1.8 Sum diagnosis table | Fault 8 “Class startup” Text ✓ ✓
1.3.6.1.4.1.22638.7.10.1.9 Sum diagnosis table | Fault 9 “Class parameter” Text ✓ ✓
371 The shown value equals the parameter on M: AU common settings | Plant.

DC8-026-2, Edition 03.2022
13.25 SNMP
GET NEXT / Response
TRAP
GETBULK / Response
<sicamRTUs.MIB>
GET / Response
1.3.6.1.4.1.22638.7.10.1.10 Sum diagnosis table | Fault 10 “Class configuration” Text ✓ ✓
1.3.6.1.4.1.22638.7.11 SICAM RTUs – History ✓ ✓
1.3.6.1.4.1.22638.7.11.1 SICAM RTUs – History – TRAP-History ✓
NOTE
i All SNMP variables of the sicamRTUs.MIB can only be read via SNMP but not changed. SNMP variables can
not be read or changed with the SICAM TOOLBOX II. The central error table in SICAM RTUs is referred to as
the sum diagnostic table.
Example: SNMP GET for OID: 1.3.6.1.4.1.22638.7.10.1.1 Sum diagnosis table | Fault 1 „Class internal“
Example for firmware revision interrogation table (retrieved with ManageEngine MIB browser):

DC8-026-2, Edition 03.2022
13.25 SNMP
Traps
The following diagnostic information are sent spontaneously as SNMP Traps to the SNMP Manager:
GET NEXT / Response
TRAP
GETBULK / Response
<sicamRTUs.MIB>
GET / Response
1.3.6.1.4.1.22638.7.10.10 SICAM RTUs Traps
(formerly sum diagnosis traps)
1.3.6.1.4.1.22638.7.10.10.1 SICAM RTUs Event = Diagnostic Events ✓
1.3.6.1.4.1.22638.7.10.10.2 Diagnostics Error Group: Error 1 - 10 Integer ✓
(These correspond to the error classes in the central
error table, see above)
1.3.6.1.4.1.22638.7.10.10.3 Diagnostic Condition: 0 = going, 1 = coming Integer ✓
1.3.6.1.4.1.22638.7.10.10.4 Diagnostic Date: Time when the trap occurred Date + ✓
Time
NOTE
i All SNMP variables of the sicamRTUs.MIB can only be read via SNMP but not changed.
SNMP variables can not be read or changed with the SICAM TOOLBOX II.
The following state information are sent spontaneously as SNMP Traps to the SNMP Manager:

DC8-026-2, Edition 03.2022
13.25 SNMP
GET NEXT / Response
TRAP
GETBULK / Response
<sicamRTUs.MIB>
GET / Response
1.3.6.1.6.3.1.1.5.1 ColdStart trap ✓
1.3.6.1.6.3.1.1.5.3 linkDown trap ✓
1.3.6.1.6.3.1.1.5.4 linkUp trap ✓
NOTE
Example: SNMP „TRAPs“
Example: SNMP „TRAP Details“
Traps History
The following status information "TRAP History" can be requested by the SNMP Manager:

DC8-026-2, Edition 03.2022
13.25 SNMP
GET NEXT / Response
TRAP
GETBULK / Response
<sicamRTUs.MIB>
GET / Response
1.3.6.1.4.1.22638.7.11.1 SNMP table with the last 50 traps sent ✓
NOTE
The following traps are entered in the TRAP history:
GET NEXT / Response
TRAP
GETBULK / Response
<sicamRTUs.MIB>
GET / Response
1.3.6.1.6.3.1.1.5.1 ColdStart trap ✓
1.3.6.1.6.3.1.1.5.3 linkDown trap ✓
1.3.6.1.6.3.1.1.5.4 linkUp trap ✓
1.3.6.1.4.1.22638.7.10.1.1 Sum diagnosis table | Fault 1 “Class internal” ✓
1.3.6.1.4.1.22638.7.10.1.2 Sum diagnosis table | Fault 2 “Class external” ✓
1.3.6.1.4.1.22638.7.10.1.3 Sum diagnosis table | Fault 3 “Class communication” ✓
1.3.6.1.4.1.22638.7.10.1.4 Sum diagnosis table | Fault 4 “Class test” ✓
1.3.6.1.4.1.22638.7.10.1.5 Sum diagnosis table | Fault 5 “Class warning” ✓
1.3.6.1.4.1.22638.7.10.1.6 Sum diagnosis table | Fault 6 “Class module failure” ✓
1.3.6.1.4.1.22638.7.10.1.7 Sum diagnosis table | Fault 7 “Class failure” ✓
1.3.6.1.4.1.22638.7.10.1.8 Sum diagnosis table | Fault 8 “Class startup” ✓
1.3.6.1.4.1.22638.7.10.1.9 Sum diagnosis table | Fault 8 “Class parameter” ✓
1.3.6.1.4.1.22638.7.10.1.10 Sum diagnosis table | Fault 8 “Class configuration” ✓
NOTE
Example: Interrogation of the SNMP "TRAP History"

DC8-026-2, Edition 03.2022
13.25 SNMP
Example: SNMP “TRAP History“ table
13.25.6.3 SNMP variables for MIB: dgpiMIB
Object group 1: dgpiProdIdentity

This collection contains the supplier name ("Siemens AG") and some customer-related information at the
product level, such as asset UUID (inventory number), customer name, product location, and geo-location.
These customer-related objects can only be read via SNMP. That is, they must be configured by the customer
in other ways (e.g., product-specific engineering tool, Web UI, etc.)
With the SICAM TOOLBOX II, this data can be entered with the following parameter:

DC8-026-2, Edition 03.2022
13.25 SNMP
Sub-Object group Objects Description / SICAM TOOLBOX II Parameter

- dgpiVendorName fix: "Siemens AG"
dgpiAssetUuid is generated by the device itself
dgpiCustomerName [BSE] System settings | Device settings |
Customer
dgpiLocationName [BSE] System settings | Device settings |
Device name
dgpiGeoPositionLatitude [BSE] System settings | Device settings |
Geographical position | Latidude
dgpiGeoPositionLongi- [BSE] System settings | Device settings |
tude Geographical position | Longitude
dgpiGeoPositionAltitude [BSE] System settings | Device settings |
Geographical position | Altitude
Object group 2: dgpiProdComp

This collection contains the product & component table (dgpiProductComponentsTable), which is the
most important object of the MIB. The product and its components are represented by lines in this table. The
first line is always occupied by the product, the following lines by the components. The order of the compo-
nents in the rows of this table is not mandatory.

DC8-026-2, Edition 03.2022
13.25 SNMP

dgpiProductComponent- dgpiProdCompIndex Index of the table line
sTable dgpiProdCompContai- Identifies the containment hierarchy of the product and
nedIn its components. It's zero in the product line because the
product is at the top of the hierarchy.
In the component rows, it corresponds to the value of
the object dgpiProdCompIndex of the product line (if
the component is directly from the product) or its
"parent" component row (if the component is contained
in a "parent" component).
dgpiProdCompClass identifies the class of the product or component of this
line
e.g.: hwProduct
dgpiProdCompName contains the name of the product or component
e.g.: SICAM A8000 CP-8050
dgpiProdCompDescrip- contains a brief description of the product or component
tion
dgpiProdCompOrder- contains the MLFB number of the product or component
Number e.g.: 6MF28050AA00
dgpiProdCompSerial- contains the serial number of the product or component
Number e.g.: BF1612034390
dgpiProdCompVersion contains the version number of the FW, HW, SW or the
configuration
dgpiProdCompHwSlot contains the number or name of the slot where the hard-
ware component is located
dgpiProdCompManu- contains the date of manufacture of the HW product or
factDate component
dgpiProdCompConfi- contains the last modification date and the last modifica-
gLastChange tion time of the updatable component
- dgpiProductCompTable- contains the date and time of the last change of each
LastChange dgpiProductComponentsTable object.
The change includes creation, removal and modification
of table rows.
This is in contrast to the dgpiProdCompLastChange
Change object, which refers to changing of rows, that
represent certain component classes.
Object group 3: dgpiNotifications

This group defines a notification (SNMPv2 trap) that will be sent when the dgprProductComponentsTable
has changed.
- dgpiNotificationsEna- enables/disables the sending of this notification
bled

DC8-026-2, Edition 03.2022
13.26 ARP
13.26 ARP
The "ARP" Address Resolution Protocol assigns a MAC address to a given IP address and stores this mapping in
the ARP tables of the participating computers.
After Link Up (Start-up or connect cable), the basic system element transmits 3 time Gratuitous ARP messages
in single second interval (ARP request broadcast) in which the own IP address is entered as the source and
destination IP address. This means that the Ethernet interface notifies its current (possibly new) MAC address
without being asked and the ARP / MAC tables in the connected network devices are updated immediately.
Also, HW issues in the network that lead to link up / link down can be detected by the increased occurrence of
gratuitous ARPs.

DC8-026-2, Edition 03.2022
14 Licenses
14.1 Introduction 1978

14.2 SICAM A8000 Extended Processing (EPCI85) 1979
14.3 SICAM A8000 IEC104 Firewall (FWI4) 1980
14.4 SICAM A8000 Redundancy 1981
14.5 SICAM A8000 SIAPP Container 1982
14.6 SICAM A8000 Extended SICAM WEB 1984
14.7 SICAM A8000 Licensed Protocol 1985
14.8 Installation of a License 1986
14.9 Automation License Manager 1987

DC8-026-2, Edition 03.2022
Licenses
14.1 Introduction
14.1 Introduction
By installing licenses, the functionality can be extended.
The following licenses are available:
• SICAM A8000 Extended Processing
• SICAM A8000 IEC104 Firewall
• SICAM A8000 Redundancy
• SICAM A8000 SIAPP Container
• SICAM A8000 Extended SICAM WEB
• SICAM A8000 Licensed Protocol

Each license can only be used on one system. It is bound to the parameter set of the respective device. The
licenses are delivered on USB sticks as standard, but can also be obtained via OSD download. Order informa-
tion see section A.2 SICAM A8000 Licences
License Management requires the Automation License Manager (ALM).
The transfer of the licenses into the parameter set of a CP-8031/CP-8050 device takes place via the import
function of your engineering tool (SICAM Device Manager as of V3.01 or SICAM TOOLBOX II as of 6.03)
NOTE
i • Licensed features can be used up to 21 days without a valid license. Then you need a valid license to
continue using the feature.
Exception: The function package Extended SICAM WEB requires a valid license from the beginning
• Licenses can no longer be returned if they have been imported into a device.
• A replacement of spare parts is possible because the license is bound to the parameter set.

DC8-026-2, Edition 03.2022
Licenses
14.2 SICAM A8000 Extended Processing (EPCI85)
14.2 SICAM A8000 Extended Processing (EPCI85)

Extended processing/communication firmware for CP-8050. A separate license is required for each EPCI85
used.
Functions
• On an EPCI85 up to 4 protocols can be executed
• Up to 4 EPCI85 per CP-8050 system can be used
• 1 additional PLC (logic) resource per EPCI85
• Coupling of a SICAM A8000 rack (1 rack per license; maximum of 4 licenses per device)
• With global redundancy, a second license is required for Device B
Requirements
• CPCI85 Central Processing/Communication Rev. 3.10 or higher
• SICAM Device Manager V3.01 or higher
• SICAM TOOLBOX II V6.03 or higher
• For permanent operation a license is required
Comparison CPCI85 - EPCI85
Central processing and Extended processing

communication (CPCI85) and communication
(EPCI85)
Max. installable EPCI85 4 -
Max. installable protocols 8 4
Max. installable I/O master firmware files 16 0
Max. number of stations for all protocols 400 200
Max. number of data points 400 000 400 000
Max. size of the „retained“ logic memory (CAEx plus 32768 Byte 12732 Byte
or CFC)
Max. number of „retained“ input messages (CAEx plus 255 127
or CFC)
Maximum racks that can be equipped with up to 16 - 1
rack I/O firmware files each
Ordering Information
Medium Designation MLFB

USB Stick CP-8050 Extended Processing 6MF2750-0EP00
OSD Download SICAM A8000 Extended Processing 6MF2750-2EP00
DL

DC8-026-2, Edition 03.2022
Licenses
14.3 SICAM A8000 IEC104 Firewall (FWI4)
14.3 SICAM A8000 IEC104 Firewall (FWI4)

IEC 60870-5-104 Application Layer Firewall with stand-alone TCP/IP stack (stack separation).
When using FWI4 on the local ports of the master modules (CP-8050 and CP-8031) one speaks of an "applica-
tion layer firewall". When used with CI-8520 or CI-8522, it is a "hardware based application layer firewall".
Functions
• unencrypted IEC 60870-5-104 central/substation
• Routing of the data of the network interface takes place only on layer 7 (stack separation)
• IEC 60870-5-104 Edition 2.0 (see CP-8050 Manual, Chapter IEC 60870-5-104/Interoperability)
• up to 100 remote stations
• 104 redundancy according IEC 60870-5-104 Edition 2.0
• Data throughput limit
• Whitelistfilter
• No other network services are possible on this interface
• With global redundancy, a second license is required for Device B
Requirements

USB Stick CP-8050 IEC104 Firewall 6MF2750-0FW40
OSD Download SICAM A8000 IEC104 Firewall DL 6MF2750-2FW40

DC8-026-2, Edition 03.2022
Licenses
14.4 SICAM A8000 Redundancy
14.4 SICAM A8000 Redundancy

Functions
• Device redundancy with PLC synchronization via the Ethernet Based I/O bus incl. singular I/Os (via
encrypted I/O bus)
• Device redundancy with PLC synchronization via routed IP network
• Integrated system voter function
• Global and protocol-selective voting
• Soft or hardware voting to select the active device
Requirements
• Latest versions of I/O and protocol firmware files (V04.00)

USB Stick CP-8050 Redundancy 6MF2750-0RE00
(contains 2 licenses; device A and
B)
OSD Download SICAM A8000 Redundancy DL 6MF2750-2RE00
(contains 2 licenses; device A and
B)

DC8-026-2, Edition 03.2022
Licenses
14.5 SICAM A8000 SIAPP Container
14.5.1 Introduction
SICAM Applications (SIAPPs) are third-party applications using the runtime environment of CP-8031/CP-8050
platform. SIAPPs can be created using SIAPP Software Development Kit (SDK) based on Docker.
Examples for applications:
• Web based HMI APP (customer specific web server, using RTU data)
• Server APP LDAP, Radius, Syslog, FTP within a secure environment

Customer specific APP: user defined communication protocols and data point conversions
SICAM CP-8031/CP-8050 provides container technology:
• SIAPPs run on a SICAM CP-8031/CP-8050 in a protected SICAM Application Runtime (SIAR) environment
• Separation of SIAPP and RTU functions
• Access to process data of RTU via EDGE DATA API
• Up to 3 SIARs containing 1 – 3 SIAPPs are supported
• Up to 3 SIAPPs are supported in total

A license for each SICAM application runtime is necessary.
For more information on parameters and engineering refer to the SICAM Device Manager Manual.

USB Stick CP-8050 SIAPP Container 6MF2750-0LX00
OSD Download SICAM A8000 SIAPP Container DL 6MF2750-2LX00
14.5.2 Edge data API
The Edge data API provides access to the RTU engineered data in read/write direction. The API supports some
data formats as well as data point quality and time information.
The following IEC60870 data types are supported and mapped by the Edge Data API:
IEC60870 Data Type EDGE Data Type extra information
TI=30, Single-point information Unsigned Integer 32 Bit
TI=31, Double-point information Unsigned Integer 32 Bit
TI=32, Transformer tap position Signed Integer 32 Bit
TI=33, 32 Bit Bit string Unsigned Integer 32 Bit
TI=34, Measured value 15 Bit + Short floating point 32 Bit
sign, normalized
TI=35, Measured value 15 Bit + Signed Integer 32 Bit
sign, scaled
TI=36, Measured value short Short floating point 32 Bit
floating point
TI=37, Integrated total 31 Bit + sign Signed Integer 32 Bit
TI=45, Single command Unsigned Integer 32 Bit Only ACTIVATION and EXECUTE are
supported
TI=46 Double command Unsigned Integer 32 Bit Only ACTIVATION and EXECUTE are
supported

DC8-026-2, Edition 03.2022
Licenses
IEC60870 Data Type EDGE Data Type extra information

TI=47 Step-by-step command Unsigned Integer 32 Bit Only ACTIVATION and EXECUTE are
supported
TI=48, Setpoint value, standard Short floating point 32 Bit Only ACTIVATION and EXECUTE are
supported
TI=49, Setpoint value, normalized Signed Integer 32 Bit Only ACTIVATION and EXECUTE are
supported
TI=50, Setpoint value, short Short floating point 32 Bit Only ACTIVATION and EXECUTE are
floating point supported
TI=51, 32 Bit Bit string Unsigned Integer 32 Bit

DC8-026-2, Edition 03.2022
Licenses
14.6 SICAM A8000 Extended SICAM WEB
14.6 SICAM A8000 Extended SICAM WEB

Extended SICAM WEB Firmware for CP-8050.
Functions
• Import of signal names from other devices for monitoing & simulation
• Simulation of unavailable devices (test phase)
• Representation of measured values as a graph
Requirements
• SICAM TOOLBOX II V7.01 or higher
• A valid license was installed (no test operation possible)
Configuration
Enable the function "Import CSV"

After loading the license into the device, this function must still be activated.
• Open in SICAM Device Manager HOME | Communication | Server Services
• In sectionWeb Server (Web)you find the function Extended SICAM WEB features (License required).
• Select enable to activate the function.
[sc_SDM_Ext_SIC_WEB_enable, 1, en_US]

OSD Download SICAM A8000 Extended SICAM WEB 6MF2750-2WE00
DL

DC8-026-2, Edition 03.2022
Licenses
14.7 SICAM A8000 Licensed Protocol
14.7 SICAM A8000 Licensed Protocol

Functions
Required for the use of the following protocols:
• SAT SK-1703 End-End (Standard-/SSI-Formats)
• Siemens SINAUT 8 FW Master
• Siemens SINAUT 8 FW Slave
Requirements

OSD Download SICAM A8000 Licensed Protocol 6MF2750-2PR00

DC8-026-2, Edition 03.2022
Licenses
14.8 Installation of a License
14.8 Installation of a License

In order to use the license, the following steps are necessary:
• Transfer of the license to the engineering PC with the Automation License Manager
• Import and activate the license with the engineering tool
14.8.1 Transfer of the license to the engineering PC with the Automation License
Manager
To transfer the license from the USB stick to the engineering PC, you must plug the USB stick into a free USB
port of your engineering PC.
The USB stick is immediately recognized and displayed by the Automation License Manager.
In the directory tree on the left, select the USB stick that contains the licenses. The list of available licenses is
displayed on the right side of the Automation License Manager.
• Select the appropriate license
• Open the context menu (right mouse button). Select the entry Transfer…
• Select a local hard disk in the following dialog
• Click OK, to transfer the license to your hard drive
• Close the Automation License Manager
NOTE
i The installation of the licenses is also possible with Drag & Drop or Copy & Paste, see also almreadme.rtf
The license can also be transferred to a license server.
14.8.2 Import and activate the license
After transferring the license, it must still be imported into the Engineering Tool (SICAM Device Manager,
SICAM TOOLBOX II) and then activated.
Proceed as follows with the SICAM Device Manager:
• Open the device for which the license was purchased
• Click Configuration and Licenses

(The license page will only be opened when the project is saved)
• Click the icon for importing the license in the Automation License Manager
• Click on the license and confirm the selection
• In the Licensable Functions table, open the list box in the License Key / License Number column and
select the license to activate it
Proceed as follows with the SICAM TOOLBOX II:
• In the system technique of the OPM II, select the device (component) for which the license was
purchased
• Open the context menu and select License...
• In the License window click on Import license...
• In the Licensable Functions table, open the list box in the License Key / License Number column and
select the license to activate it

DC8-026-2, Edition 03.2022
Licenses
14.9 Automation License Manager
14.9 Automation License Manager

Important information about installation and use of the Automation License Manager can be found in
almreadme.rtf and in almapp_b.pdf (Programming and Operating Manual, available in English only) after
SICAM Device Manager installation at:
C:/Program Files/Siemens/Automation License Manager or C:/Program Files/Siemens/Automation License
Manager/manual
NOTE
i The file ReadMe_OSS of the SICAM Device Manager is also located in the installation directory.
Note that a restart is required after each (new) installation of the Automation License Manager.
After the restart, the ALM service is running. Open services.mscto check the running ALM service.

DC8-026-2, Edition 03.2022
DC8-026-2, Edition 03.2022
15 Sample Applications
15.1 Application Overview 1990

15.2 Expansion Stages 1992
15.3 Ring Configurations 1995
15.4 Line Configurations 2006
15.5 Configurations with SICAM A8000 Rack I/Os 2010
15.6 Migration of SICAM AK/AK3 I/O modules into the SICAM A8000 rack solution 2014
15.7 Initial Commissioning 2017

DC8-026-2, Edition 03.2022
Sample Applications
15.1 Application Overview

Due to the modular architecture, SICAM CP-8050 can be used in a variety of ways:
• Front End, Gateway
• Process control applications, automation applications
• Station Control Device, Sub-Node
• Telecontrol substation
[dw_CP-8050_Application_Overview, 1, en_US]
15.1.1 Front End, Gateway
Due to the large number of different interfaces (up to 32) and the protocols that can be used on them (up to
24), SICAM CP-8050 is ideally suited for use as a front end for a process control system.
All telecontrol substations - regardless of the manufacturer and via which protocol - are coupled to SICAM
CP-8050. In the front end, the signal processing and adaptation takes place for the respective control system.
From the perspective of the control system, there is no difference which protocol and which system behavior
the substation actually has.

DC8-026-2, Edition 03.2022
Sample Applications
15.1.2 Process control applications, automation applications
Open- and closed-loop control application programs are created by means of CAEx plus or CFC according to
IEC 61131-3, a standard that is generally accepted and recognized in the market.
Through this and due to the modularity, SICAM CP-8050 is suitable for many applications: from smaller auto-
mation applications up to complex process control applications. Naturally, all applications can also be
combined.
15.1.3 Station Control Device, Sub-Node
The functionality of a station control device can be simply regarded as a combination of the functionality of a
front end (interfacing of diverse bay devices, protective devices, processing of the data for the power system
control) and the functionality of process control applications (open- and closed loop control application
programs), and is therefore perfectly suited for this application. In addition, further telecontrol peripherals can
also be installed in the station control device, through which telecontrol station and station control device are
united in one device.
15.1.4 Telecontrol substation
For telecontrol applications, modular, versatile I/O modules are available for process data coupling.
SICAM CP-8050 supports centrally and decentrally installed I/O modules especially through the use of remote
I/O rows. Flexible communication functions also permit redundant communication and communication over
stand-by transmission lines.
Naturally, arbitrary open- and closed-loop control application programs can be realized in SICAM CP-8050 with
CAEx plus and CFC, through which, at the same time and to the same degree, SICAM CP-8050 can become a
remote terminal unit and an automation unit in one.

DC8-026-2, Edition 03.2022
Sample Applications
15.2 Expansion Stages
15.2.1 Basic Configurations
Master Module with Power Supply (Minimum Configuration)

Usage for simple data nodes. Selection of power supply according power consumption. Due to redundancy
reasons a second power supply module can be used.
Designation MLFB
CP-8050 Master Module 6MF28050AA00
PS-8620 Power supply DC 24 V to 60 V, 12 W 6MF28620AA00
PS-8642 Power supply DC 100 V to 240 V or VAC 45 W 6MF28642AA00
Master Module with Power Supply and Communication Module(s)

Usage for simple data nodes. Selection of power supply according power consumption. Up to 2 communica-
tion modules, each with 5 interfaces, are possible.

DC8-026-2, Edition 03.2022
Sample Applications
Designation MLFB
CI-8520 Ethernet Extension Module 6MF28520AA00
CI-8522 Network Interface Fiber Optic Extension Module 6MF28522AA00
Master Module with Power Supply and I/O Modules

Usage as automation system with local I/O modules. Selection of power supply according power consumption
of the system. Due to redundancy reasons a second power supply module can be used.
Designation MLFB
SICAM I/O Module See chapter [OptUnresol-
vedLink]SICAM I/O
modules[/OptUnresolved-
Link]

DC8-026-2, Edition 03.2022
Sample Applications
15.2.2 Maximum Configuration
CP-8050 with 15 I/O-Rows in Ring Configuration
[CP-8050_config_max, 1, --_--]

DC8-026-2, Edition 03.2022
Sample Applications
15.3 Ring Configurations
15.3.1 Ring configurations with electrically connected I/O rows
Example 1: Base device with I/O modules + 15 electrically connected I/O remote rows
If the base device and the I/O row(s) are electrically connected, the cable may not exceed 100 m in length.
This also applies to the connection between the I/O rows.
[CP-8050_config_Ring_el_remote_io_v1, 1, en_US]

DC8-026-2, Edition 03.2022
Sample Applications
Example 2: Base device with I/O modules + 15 electrically connected I/O remote rows + „Ethernet-Repeater“
An "Ethernet Repeater" can be used to extend the max. cable length between the base device and the I/O rows
or between the I/O rows. Each "Ethernet repeater" can extend the route by 100 m. The I/O Remote Modules
CI-8530 or CI-8532 can be used as “Ethernet Repeater“.
The I/O# of the “Ethernet Repeater“ in the ring configuration must be set to 0.
NOTE
i Configuration:
• Up to 20 CI-8530/CI-8532 can be used in a ring/line configuration as an I/O Remote module or

"Ethernet Repeater".
Maximum 15 out of these can be used as I/O Remote module.
• No I/O-Modules may be connected to the "Ethernet Repeaters".
• Ethernet I/O ring and Ethernet I/O line may not be connected to other Ethernet networks.
Refer to 12.3.4 SICAM I/O Remote Modules for LED display status on the Ethernet Repeaters.

DC8-026-2, Edition 03.2022
Sample Applications
15.3.2 Ring configurations with optically connected I/O rows
Example 1: Basic device with I/O modules; optical connection to the I/O rows; electronic connection between the
I/O rows
[CP-8050_config_Ring_opt_remote_io_v1, 1, en_US]
*) Converter see chapter: 15.3.3 Optical Converter (Media Converter) for I/O rows

DC8-026-2, Edition 03.2022
Sample Applications
Example 2: Basic device with I/O modules; optical and electrical connection to the I/O rows and between the I/O
rows
[dw_CP-8050_config_Ring_opt_remote_io_v3, 2, en_US]
*) Converter see chapter: 15.3.3 Optical Converter (Media Converter) for I/O rows

DC8-026-2, Edition 03.2022
Sample Applications
NOTE
i • If the CI-8531/CI-8533 is used as an I/O remote module and one of the connections is an electrical SFP
transceiver, no optical converter is required between the CP-8050 and CI-8531/CI-8533.
• If the CI-8531/CI-8533 is used as an I/O remote module and both connections are optical SFP trans-
ceivers, then an optical converter is required between the CP-8050 and CI-8531/CI-8533.
15.3.3 Optical Converter (Media Converter) for I/O rows
The use of converters and fiber-optic cables can significantly increase the distance between the base device
and I/O-rows and between the individual I/O-rows. Depending on the type of cable and converter used,
different cable lengths can be achieved.
NOTE
i • Only converters that support a transmission speed of 100 Mbit/s can be used.
• CI-8531/CI-8533 acts as a media converter with 1 electrical SFP and 1 optical SFP
• A maximum of 20 devices with Ethernet connection may be used in the I/O Line (ring/line configura-
tion)
Examples:
– 15 I/O-rows = 15 x CI-8530/CI-8532 + 4 optical converters = 19 (optical converters are always
required in pairs)
– 15 I/O-rows = 15 x CI-8530/CI-8532 + 5 x CI-8530/CI-8532 with switch position “I/O#=0“ = 20
– Example: 15 I/O-rows = 15 x CI-853x + 2 x CI-8531/33 = 17
• The converters must support the cut-through-process (Cut-Through-Forwarding/Cut-Through-

Switching).
Cut-through delay time (latency time): 6-8 μs (micro seconds)
• Ethernet I/O Ring and Ethernet I/O line may not be connected to other Ethernet networks.

DC8-026-2, Edition 03.2022
Sample Applications
Siemens Ruggedcom RMC
• 6GK6001-0AC01-0FA0
• 6GK6001-0AC02-0FA0
• 6GK6001-0AC03-0FA0

• MLFB: 6GK6001-0AC01-0FA0
• MLFB: 6GK6001-0AC02-0FA0
• MLFB: 6GK6001-0AC03-0FA0
– Multimode
– 1x 100TX to 1x 100FX

DC8-026-2, Edition 03.2022

Manual CP-8031 CP-8050 ENGREG

Uploaded by

Copyright:

Available Formats

Manual CP-8031 CP-8050 ENGREG

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Manual CP-8031 CP-8050 ENGREG

Uploaded by

Copyright:

Available Formats

Communication Protocols

13.19 ÖBB X25

Wiring for connection CI-8551 (X1, X2) ↔ "PAD"

Connector X1, X2 (CI-8551)

Pin RS-232 Signal Push-in terminal 8-pole

SICAM A8000 Series, CP-8031, CP-8050, Manual 1901

Meaning Order number

RS PRO RJ-Adapter, 25-pole Sub-D plug, RJ45 socket https://at.rs-

13.19.5.1 Data transmission X25-interface

• The X25-interface is supplied via the external "PAD".

• The CP-8050 is connected to the "PAD" via a serial RS-232 interface.

1902 SICAM A8000 Series, CP-8031, CP-8050, Manual

PAD Designation Order number

The PAD from Datus has two asynchronous interfaces DATUS-PAD

Connection type of the X25 interface

Initialization of the X25 interface

SICAM A8000 Series, CP-8031, CP-8050, Manual 1903

4 • Life cycle frames are received cycli- • GI messages are sent.

1904 SICAM A8000 Series, CP-8031, CP-8050, Manual

Establishing a connection after startup of the CP-8050 without recommissioning condition

TL.Nr. ... Message number

SICAM A8000 Series, CP-8031, CP-8050, Manual 1905

(1) ... Command receipt

Acknowledgment of messages on the X25 interface

• Acknowledgment for general interrogation command

13.19.5.2 Function for the Support of Redundant Communication Routes

This function is currently not supported!

13.19.6 Parameter and Setting

Parameter Name Description Settings

1906 SICAM A8000 Series, CP-8031, CP-8050, Manual

Parameter Name Description Settings

SICAM A8000 Series, CP-8031, CP-8050, Manual 1907

Parameter Name Description Settings

Default: CCITT-CRC inversion and

1908 SICAM A8000 Series, CP-8031, CP-8050, Manual

• Data flow direction = both directions

• Data flow direction = automatic and selective

• Service function messages = disabled

13.19.7 Message Conversion

Supported processing types for message conversion:

Data Direction Processing type OX25I1

13.19.7.1 Message Conversion in Transmit Direction (CP-8050 → ÖBB X25)

Message Conversion in Transmit Direction CP-8050 → ÖBB X25

SICAM A8000 Series, CP-8031, CP-8050, Manual 1909

CP-8050: IEC 60870-5-101/104 → ÖBB X25

Signal box data

• <TI:=33> ... Bit sting of 32 Bit with time tag CP56Time2a

1910 SICAM A8000 Series, CP-8031, CP-8050, Manual

• 01 = Track switch, DKW, EKW

SICAM A8000 Series, CP-8031, CP-8050, Manual 1911

Elements of the message

13.19.7.2 Message Conversion in Receive Direction (CP-8050 ← ÖBB X25)

Message Conversion in Receive Direction CP-8050 ← ÖBB X25:

1912 SICAM A8000 Series, CP-8031, CP-8050, Manual

i • HSR can only be used with the CI-852x module.

• Only 1 redundancy protocol can be used per ring.

• 2 HSR rings are possible for each CI-852x module.

SICAM A8000 Series, CP-8031, CP-8050, Manual 1913