Network Topologies - Kaco blueplanet 87.0 TL3 M1 WM OD IIF0 Manual

Hide thumbs Also See for KACO blueplanet 87.0 TL3 M1 WM OD IIF0:
Table of Contents

Advertisement

8 | Start-up
8.3

Network topologies

Plant segmentation
Service
Max. 100m
SEGMENT 1
5
Segment
2)
Controller
Network
6
Segment Switch
7
8
(RSTP)
Ethernet
SC
BP1
Ring
SC
BP2
Topology
SC
BP3
9
max. 100m
max. 100 nodes/segment
SC
SC
Legend:
SC: ARGUS
DC
RS485
Fig. 42: Segmentation of a plant
1 Gateway VPN 3G/4G router
2 Main network switch
3 FO - switch (fibre optic)
4 Slicebox (for fibre optic data transfer)
5 Segment Controller
This figure shows a potential alternative for multiple segments. Depending on the local conditions, a different positioning
of the components may also be preferable (e.g. position Segment Controller at a central location and connect in
the segment switch via glass fibre cable).
Located directly after the Gateway VPN-Router, is the main network switch via which the segment con-
troller is connected in. With the corresponding system size (distance from main network switch to the seg-
ment controller >100 m), it may also be necessary to connect in segments that are further away via a glass fibre
connection.
Within a segment, it is possible to link KACO devices to one another as part of an Ethernet daisy-chain by way of an inte-
grated switch, whereby the Segment Controller is connected at the first element in the chain. For this purposes of an ex-
ample, this topology is shown in segment 2. A Segment Controller can manage up to 100 nodes. A node in this
sense is any data source that is monitored by the Segment Controller. (Example: 45 pairs consisting of inverter and
string combiner (90 nodes) + 10 reserve nodes for other substation/segment data sources)
If additional failure safety is desirable, the KACO devices can also be arranged in a ring via a correspondingly configured
Network Segment Switch (that supports the Rapid Spanning Tree Protocol "RSTP"). This switch is then also coupled
to the Segment Controller. For this purposes of an example, this configuration is shown in segments 1 and M.
As can be seen in the figure, a string combiner is assigned to each KACO device. In terms of communication, these
are connected to the device directly via an RS485 cable (green cable). To this end, MODBUS RTU is used as a communica-
tion protocol. The monitoring of the string combiner is also carried out via the Segment Controller, whereby
the KACO device undertakes the role of a MODBUS gateway. The string combiner must be coupled using a KACO
blueplanet ARGUS.
The only 3rd party string combiner device currently available, which can also be addressed in this manner via the
Segment Controller, comes from "Kernel Sistemi".
Page 36
User
HTTP(S)
10
Plant
1)
Controller
2
Main network switch
SEGMENT 2
Segment
2)
Controller
HTTP(S)
FTP
MODBUS/RTU
Ethernet
SC
BP1
BPm
SC
SC
BP2
BPk
SC
Topology
SC
BP3
BPj
SC
max. 100m
SC
typ. 10MW/segment
BP: blueplanet 125
RSTP: Rapid Spanning Tree
Inverter
String Combiner
Manual
HTTP(S)
Internet
XMPP
1
Gateway
VPN 3G/4G Router
3
Fiber
FO Switch
Splicebox
SEGMENT M
MQTT
MODBUS/TCP
BPk
SC
Line
BPj
SC
BPi
SC
SC
MQTT: Messge Queuing
Protocol
Telemetry Transport
6 Network segment switch
7 Inverter device
8 String combiner
9 Connection cable and protocol
- DC / Modbus RTU / RS485
10 Plant Controller
KACO blueplanet 110 TL3 KACO blueplanet 125 TL3 US
Cloud
meteocontrol Portal
WEB-
Database-
App-
Server
Server
Server
4
Splicebox
FO Switch
Segment
2)
Controller
Network
Segment Switch
(RSTP)
Ethernet
SC
BP1
BPk
Ring
SC
BP2
BPj
Topology
SC
BP3
BPi
max. 100m
SC
SC
1): meteocontrol blue'Log XC
2): meteocontrol blue'Log XM
SC
SC
SC

Hide quick links:

Advertisement

Table of Contents
loading

Table of Contents