AVENAR Panel FPA 5 Special enUS 79594142347
AVENAR Panel FPA 5 Special enUS 79594142347
Ethernet
en Networking manual
AVENAR panel | FPA-5000 | FPA-1200 Table of contents | en 3
Table of contents
1 Safety 5
1.1 Organizational measures for PC running service clients 5
1.2 Explanations of safety symbols 6
1.3 Safety notices 6
2 Introduction 8
3 System overview 8
4 Topologies 10
4.1 CAN loop 15
4.2 Ethernet loop 16
4.3 Ethernet loop with OPC server 16
4.4 Ethernet loop with OPC server to redundant panel 17
4.5 Ethernet/CAN double loop 17
4.6 CAN loop with Ethernet segments 17
4.7 Ethernet backbone with sub-loops (Ethernet/CAN) 17
4.8 Connecting Ethernet loops 19
5 Ethernet network 21
5.1 Protocols 21
5.2 Network diameter 22
5.3 Cables used 24
5.4 Creating or modifying an Ethernet network 24
6 CAN network 26
6.1 Creating or modifying a CAN network 27
7 Ethernet and CAN networking pattern 27
7.1 Panel network over Ethernet 29
7.2 Panel network over CAN 29
7.3 Connect services to panel 30
7.4 Panel network over Ethernet with redundant panels 31
7.5 Panel network over CAN with redundant panels 31
7.6 Panel network over two Ethernet loops 32
7.7 Panel network over two Ethernet loops with redundant panels 32
7.8 Connect Ethernet and CAN network with redundant panels 32
7.9 Connect remote services to redundant panels 33
7.9.1 Redundant AVENAR panel 33
7.9.2 Redundant FPA 34
7.10 Connect life safety services to redundant panels 34
8 Remote Services 35
8.1 Remote Connect 35
8.2 Remote Alert 37
8.3 Remote Maintenance 38
8.4 Remote Portal 40
9 Smart Safety Link 42
9.1 One direct VAS interface 43
9.1.1 Praesideo and PAVIRO 43
9.1.2 PRAESENSA 44
9.2 Multiple direct VAS interfaces 45
9.3 VAS integrated in Ethernet panel network 46
10 Installation 47
10.1 Settings on media converter 47
Bosch Sicherheitssysteme GmbH Networking manual 2021-12 | 2 | F.01U.378.914
4 en | Table of contents AVENAR panel | FPA-5000 | FPA-1200
1 Safety
In this chapter you find organizational measures for PC running service clients for the Bosch
portfolio for fire products. You are obliged to comply with these contractual agreements.
You find also safety notices collected and sorted by topics. Later on, the safety notices are
placed before the related instruction.
7. Segregation of duties
Duties and areas of responsibility shall be segregated to reduce opportunities for
unauthorized or unintentional modification or misuse, i.e. different tasks shall be
assigned to different roles.
8. Monitoring
All access attempts to the PC running the service client must be monitored to recognize
unauthorized access to the PC and the internet.
Notice!
i Indicates a situation which, if not avoided, could result in damage to the equipment, to the
environment, or to data loss.
Warning!
Laser light
Do not look directly into the beam with the naked eye or with visual instruments of any kind
! (e.g. magnifying glass, microscope). Failure to observe this notice poses a danger to the eyes
at a distance of less than 100 mm. The light emerges at the visual terminals or at the end of
the fiber optic cables connected to these. CLASS 2M laser diode, wavelength 650 nm, output
< 2 mW, in accordance with IEC 60825-1.
Remote Services
Caution!
For access via the internet use only Bosch Remote Services.
!
Caution!
Remote Services require a secure IP connection. Bosch Remote Services or connection with
Private Secure Network is required.
! With Private Secure Network an IP network is provided, which is based on DSL with an
optional wireless access on the panel side (EffiLink). Remote Services for Private Secure
Network is only available in Germany with a service agreement with Bosch BT-IE.
Notice!
An exclusive Ethernet network is required in order to set up a central fire alarm network.
i The use of a fire alarm system in any other Ethernet network is at the own risk of the user.
Bosch disclaims any and all warranties and liabilities for this misapplication.
In case of non-exclusive Ethernet network reliable alarm transmission and IT-security cannot
be ensured.
Warning!
Ethernet security risks
! Do not connect PRAESENSA to FPA-5000/FPA-1200 using Smart Safety Link due to Ethernet
security risks.
Notice!
i VdS 2540
The voice alarm system must be flush with the fire panel in one single room. Otherwise the
requirements of VdS 2540 for data transmission paths are not fulfilled.
Panel network
Notice!
EN 54
i To ensure that the network is set up in compliance with EN 54, use only components that
have been approved for use in central fire alarm networks.
External RSTP switches and media converters in Ethernet networks must be installed in panel
housings. The installation outside of a panel housing is not compliant with EN 54.
Notice!
i TX cable length
All IP connections must be direct or via media converters approved by Bosch. The node to
node TX cable length must be less than 100 m.
Notice!
i VdS 2540
To meet the requirements of VdS 2540 for data transmission paths, use fiber optic cable for
Ethernet connections. For connections within a housing, you can use TX Ethernet cables.
Notice!
Notice!
Applicable topologies
i The functionality and panel-to-panel communication is limited by the panel type. Refer to the
panel specification for information on services, for number of connectable panels and for
number of connectable remote keypads.
2 Introduction
This document is aimed at readers with experience in planning and installing EN 54 compliant
fire alarm systems. In addition, you need networking knowledge.
This document describes a variety of fire alarm network topologies. The topologies are
described independently of the fire panel type.
For building up panel networks corresponding to the introduced topologies and connecting
services, you need the networking pattern described in this document.
The document provides an overview of the basic conditions, limit values, and general
procedures for panel network planning and installation.
Detailed descriptions of the installation of the individual components can found in the
respective installation guides.
You find a description of the user interface of the panel controller in the user guide included
with the device.
The user interface of the FSP-5000-RPS programming software is described in the online help.
3 System overview
Voice Alarm System
Networking over IP
OPC-Server
Networking
over CAN
Services
IP Stack
IP Protocols
CAN
Ethernet
In the network, the Ethernet interface and IP protocols are used for different services. The
Ethernet interface can be disabled completely or its use disabled only for networking over
TCP/IP. Disabling may be necessary for networking over CAN.
Enabling services
– networking over TCP/IP
In FSP-5000-RPS, enable panel-to-panel communication in the Ethernet network
– OPC servers
Add an OPC server to the FSP-5000-RPS configuration
– Voice Alarm System connection
Add a Voice Alarm System to the FSP-5000-RPS configuration and configure virtual
triggers.
– Remote Services (Remote Connect as prerequisite, Remote Maintenance and Remote
Alert)
Activate the relevant check box in FSP-5000-RPS
– Remote Services (Remote Connect as prerequisite, Remote Maintenance and Remote
Alert) for Private Secure Network
Add remote access to the FSP-5000-RPS configuration and set up the remote access in
FSP-5000-RPS.
Notice!
Unintentionally data transfer
i If the Ethernet interface of the panel controller is used only for communicating with an OPC
server or for Remote Services disable the panel communication over TCP/IP, in FSP-5000-
RPS. Otherwise fire data could be transferred over the Ethernet unintentionally.
To operate Ethernet or TCP/IP-based services, the Ethernet interfaces must be enabled and
the correct TCP/IP settings configured.
Network of panels and remote keypads
The table shows the options for networking panels/remote keypads depending on the network
topology and the panel type. Consider the limits determined by the network topology.
Possible Possible
Standalone
Max. 32 panels and remote keypads 1 panel and max. 3 remote keypads
Loop
If you extend an FPA-5000 network, Bosch recommends to extend the network with a panel of
the AVENAR panel series.
When exchanging a panel of the FPA series with a panel of the AVENAR panel series, then it is
sufficient to exchange the panel controller solely. Remind, that the panels of the AVENAR
panel series does not support address cards. In case of a plugged Ethernet switch, you can
continue the usage of it.
When exchanging a remote keypad of the FPA series by a remote keypad of the AVENAR panel
series, check if the line resistance is within the range specified for the remote keypad of the
AVENAR panel series.
Notice!
Firmware installation
Notice!
Firmware versions
i For a system containing exclusively AVENAR nodes, it is recommended to run the latest panel
firmware version 4.x.
For a system containing at least one FPA/FMR node, it is recommended to run the latest
panel firmware version 3.x.
Notice!
From January 1, 2022 to December 31, 2025, panel firmware version 3.x is in maintenance
mode. During this period, new versions will be released containing fixes for critical bugs and
critical security gaps. No new product features, LSN peripheral devices, GUI languages, and
i normative changes are planned to be added.
After December 31, 2025 running firmware V3.x on panels that are connected to an Ethernet
interface or network increases security risks. It is strongly recommended to perform a
security risk assessment. When security risks are identified, it is mandatory to upgrade to
AVENAR panel and run latest firmware V4.x.
Notice!
4 Topologies
This document describes a variety of fire alarm network topologies. The topologies are
described independently of the fire panel type.
Notice!
Applicable topologies
i The functionality and panel-to-panel communication is limited by the panel type. Refer to the
panel specification for information on services, for number of connectable panels and for
number of connectable remote keypads.
OPC-Server
a b
OPC-Server
OPC-Server
Cable Description
Device Description
Media converter
Limits in network
The number of panels and remote keypads that can be networked depends on the choice of
network topology.
Networked panels and remote keypads are known as nodes.
– The number of detection points in a network is limited to 32768.
– The number of detection points per panel operated in a network is limited to 2048.
– The number of nodes per system depends on the type of topology.
A node is either a panel controller or a remote keypad.
– The number of nodes in loop topology is limited to 32.
– With FSP-5000-RPS you can assign up to 3 configured remote keypads to one panel.
The cabling between nodes and the maximum permissible cable length is also determined by
the choice of topology.
Up to 32 panel controllers, remote keypads and OPC servers can be combined to form a
network.
Depending on the intended application, different panel controllers and remote keypads can be
divided into groups and defined as network nodes or local nodes. As a rule, within any given
group, only the status of control panels within the defined group can be displayed. The status
of all control panels can be displayed and/or processed from network nodes, irrespective of
the group to which the panels belong.
Physical node address
A panel or a remote keypad is identified in the network by a unique address, which is known
as the physical node address.
Notice!
Notice!
Notice!
EN 54
i To ensure that the network is set up in compliance with EN 54, use only components that
have been approved for use in central fire alarm networks.
External RSTP switches and media converters in Ethernet networks must be installed in panel
housings. The installation outside of a panel housing is not compliant with EN 54.
Notice!
Redundant panel - EN 54-2
For each panel, a maximum of 512 detection points can be connected according to EN 54-2. If
this number is exceeded, you have to design the panel redundantly.
i Also if a panel acts as an interface with a CAN sub-loop and more than 512 detection points
are connected in the sub-loop, then you have to design the panel redundantly. The RSTP
switch which connect 2 loops performs the redundancy.
For a standalone panel you can connect up to 4096 detection points, even though it is
designed redundantly. If the panel is included in a network, then you can connect a maximum
of 2048 detection points.
Notice!
Make sure that the physical node address assigned to the panel matches that in the
i programming software. The latter is responsible for setting the last number of the IP address
in the standard settings.
Activate RSTP as the redundancy protocol and adopt the default standard values.
Notice!
i Correct setting of the physical node address on the panel controllers and in the FSP-5000-
RPS programming software is a requirement for a run-capable network.
Notice!
i Use of the Ethernet redundancy must be activated separately in the panel controller.
– IP settings
– IP address 192.168.1.x
The last digit of the IP address in the standard settings is always identical to the
physical node address set on the panel controller.
– Network screen 255.255.255.0
– Gateway 192.168.1.254
– Multicast address 239.192.0.1
– Port number 25001 - 25008 (only the first port can be set, 8 consecutive ports are
always used)
– RSTP parameters (default settings)
– Bridge Priority 32768
– Hello Time 2
– Max. Age 20
– Forward Delay 15
Notice!
You can use the standard settings of the IP configuration with networks of up to 20 RSTP
i switches.
In the case of networks with more than 20 RSTP switches, additional settings are required
according to the topology. In-depth knowledge of networks is required for this.
OPC Ethernet
Server 100BaseTX
Notice!
EN 54
The connection of a building management system (e.g. BIS) via an Ethernet interface using an
i OPC server or an FSI server is EN54 compliant if the EN54 relevant functions are performed
by the fire panel solely. Any EN54 relevant control or administration (e.g. control of
notification appliances or administration of switch-off) by the building management system
requires an individual EN54 certification of the overall system by a certification body.
Notice!
OPC-Server
OPC-Server
Consider the settings for loops with more than 20 RSTP switches, see Settings for loops with
more than 20 RSTP switches, page 14.
Notice!
i This topology requires additional settings for all RSTP switches in the backbone. More in-
depth knowledge of networks is therefore required.
Notice!
If the panel acts as an interface with a CAN sub-loop, this panel must then also be designed
i redundantly according to EN 54‑2 if more than 512 detection points are connected in the sub-
loop.
This restriction does not apply in an Ethernet sub-loop, as the switches to connect the 2
loops perform the redundancy.
Additional settings
You must operate the central loop as the backbone. This central loop must be networked via
Ethernet.
Notice!
For all RSTP switches in the backbone, set a higher RSTP priority than in the sub-loops. This
i ensures that the RSTP root bridge will always remain in the backbone, even in the event of a
fault.
The RSTP switches to connect the loops are part of the backbone!
Use a RSTP priority of 16384 in the backbone.
Notice!
i The lower the set value, the higher the RSTP priority.
Switches for connecting the OPC server and the sub-loops must be programmed separately
Program the IP address and redundancy settings of the Ethernet switches, see Settings on
switch, page 49. For this topology, the fault outputs of the switch only have to be used if you
have designed the power supply for the switch redundantly or there is a switch-to-switch
connection, see Ethernet switch, page 59.
Make sure that the RSTP settings in the panel controllers, in FSP-5000-RPS and in the
Ethernet switch are identical.
Notice!
i Change the RSTP priority for the RSTP switches that connect the loops, as they belong to the
backbone.
OPC-Server
i This topology requires additional settings for all RSTP switches in the backbone. More in-
depth knowledge of networks is therefore required.
Additional settings
This topology is a special instance of the Ethernet backbone with sub-loops, see Ethernet
backbone with sub-loops (Ethernet/CAN). You must operate one of the two loops as the
backbone.
Notice!
For all panels and switches in the backbone, set a higher RSTP priority than in the sub-loops.
i This will ensure that the RSTP root bridge will always remain in the backbone, even in the
event of a fault.
The switches to connect the two loops are part of the backbone!
Use a RSTP priority of 16384 in the backbone.
Notice!
i The lower the set value, the higher the RSTP priority.
Switches for connecting the OPC server and the second loop must be programmed
separately
Program the IP address and redundancy settings of the Ethernet switch, see Settings on
switch, page 49. For this topology, the fault outputs of the switch only have to be used if you
have designed the power supply for the switch redundantly, see Ethernet switch, page 59.
Make sure that the RSTP settings in the panel controllers, in FSP-5000-RPS and in the
Ethernet switch are identical.
Change the RSTP priority for the switches for connecting the two loops, as they belong to the
backbone.
OPC server must be programmed separately
Program the IP address, network nodes, network group and RSN. See the corresponding
section in the Installation chapter of the Networking Guide.
The OPC server uses port 25000 as standard.
Make sure that the settings in the FSP-5000-RPS programming software and in the OPC server
are identical.
Parameters
– The OPC server may be connected via an Ethernet cable (copper) or fiber optic cable.
In these examples, loop a is the backbone. Loop b is the sub-loop.
OPC-Server
a b
OPC-Server
5 Ethernet network
In the network, the Ethernet network connections are monitored continuously. If a connection
has been severed, then the interruption is detected. Repaired connections are also detected.
The network diagnosis of the panel always shows you the MAC address of the hosts
connected via the network.
MAC addresses
For network connection each panel controller provides the following MAC addresses.
– MAC address for the host
– MAC address to identify the ETH1 port
– MAC address to identify the ETH2 port
Depending on panel controller type:
– MAC address to identify the ETH3 port
– MAC address to identify the ETH4 port
Rules for using 4 Ethernet ports
If your panel has 4 Ethernet ports, apply the following rules in the given order. Bosch supports
networks, which are built according to the following rules, only.
1. For panel networking you have to use ETH1 and ETH2. An external RSTP switch on ETH1
or ETH2 must only be used for panel networking.
2. For connecting an OPC, an FSM-5000-FSI, a Voice Alarm System, an UGM-2040 you have
to use ETH3. You may connect an external RSTP switch, which must not be used for panel
networking.
3. For Remote Services you have to use ETH4. If no connection to Remote Services is
required, then ETH4 can be used for connecting an OPC, an FSM-5000-FSI, a Voice Alarm
System, or an UGM-2040.
4. If there is no panel networking via ETH1 and ETH2, then each can be used for connecting
an OPC, an FSM-5000-FSI, a Voice Alarm System, or an UGM-2040.
5.1 Protocols
SNMP
SNMP is used to monitor and control network components. To this end, parameters of
network nodes can be read out or modified. For this you require the appropriate network
management software (e.g. Hirschmann HiVision).
Notice!
Consider, that the AVENAR panel series does not yet support the SNMP protocol.
LLDP
LLDP is a basic protocol standardized by the IEEE. It is used to share network information
between neighboring devices. This information is
– provided as part of the SNMP data
– displayed via the panel controller as part of the network diagnostic data
RSTP
RSTP is a network protocol standardized by the IEEE. RSTP ensures that there are no loops in
networks. Redundant paths are detected in the network, deactivated and activated when
necessary (failure of a connection).
The protocol is used for exactly this purpose in the network.
A change to the topology following the failure of a connection is automatically canceled once it
has been repaired.
2 connected panels form the smallest possible loop. The diameter of this network is equal to
2, as the internal RSTP switches are located between the end points.
CPU CPU
S 1 S 2
Ø=2=#
CPU
CPU
1
2
CPU
6
CPU
3 Ø=6=#
CPU
CPU 5
4
10 9
12 7
11 8
14 5
13 15 4 6
18 1
16 3
17 2
Ø = 18
# = 14
Figure 5.3: Network diameter of a backbone with sub-loops
The figure shows, for the diameter you have to find the longest path.
Notice!
i TX cable length
All IP connections must be direct or via media converters approved by Bosch. The node to
node TX cable length must be less than 100 m.
Notice!
i VdS 2540
To meet the requirements of VdS 2540 for data transmission paths, use fiber optic cable for
Ethernet connections. For connections within a housing, you can use TX Ethernet cables.
5. Configure the network settings for the individual control panels directly at the control
unit as per the printout.
6. Reset each of the control panels in the network in order to activate the network
configuration.
7. Connect your computer with the FSP-5000-RPS programming software to a control panel
in the network. Load this configuration to all other control panels across the network via
this control panel. Redundant panels use the main panel configuration.
8. Carry out a reset in order to reset the pending error messages. Rectify any errors.
Configure the network settings on the control panels first. This gives you the advantage that
you can program the other control panels in the network from one control panel.
Creating an Ethernet network (medium-sized and large projects)
This procedure is suitable for projects involving a number of tasks carried out concurrently by
several teams. As many tasks performed during installation and configuration involve
restarting the fire alarm control panel, the network is not started up in this procedure until a
later stage.
1. Plan out the network.
2. Produce a configuration of the network without peripherals with FSP-5000-RPS.
3. Print the network information out for safe keeping, or store the information on the
laptop.
4. Install the network cables and check individual sections or loops.
5. Install the panels and commission them as stand-alone panels.
6. Install the peripherals in the panels.
7. Configure each of the panels with FSP-5000-RPS.
8. Ensure that the individual panels are working correctly.
9. Commission the individual loops of the network one after the other, according to the
topology.
Start with the backbone.
– Produce a configuration for the backbone in FSP-5000-RPS. Import all of the
necessary panel configurations. Configure the network settings and print them out.
– Connect all panels to a network.
– Configure the network settings for the individual control panels directly at the panel
controller as per the printout.
– Reset each of the control panels in order to load the network configuration.
– Ping the neighboring panels in order to check the network.
– Commission the entire backbone and rectify any errors.
Commission the sub-loops as per the example of the backbone.
Add a panel to a network
1. Change the network configuration in FSP-5000-RPS.
2. Print the network information out for safe keeping, or store the information on the
laptop.
3. Install the control panel and network cables and connect them to the network.
4. Configure the network settings for the individual control panel directly at the control unit
as per the printout.
5. Reset the panel and adjoining panels in order to activate the network configuration.
Remove a panel from the network
1. Change the network configuration in FSP-5000-RPS.
2. Print the network information out for safe keeping, or store the information on the
laptop.
3. Configure the network settings for the adjoining control panels directly at the control unit
as per the printout.
4. Shut off the panel, and the power supply (mains and battery) before removing it from the
network.
5. Reset the adjoining panels in order to activate the network configuration.
6 CAN network
Loop topology
In loop topology, the CAN cable is always routed from a CAN1 terminal to a CAN2 terminal
[CAN1 ⇒ CAN2]. The cable length depends on the cable cross-section.
CAN connection
The CAN connection is a two-wire connection (CAN‑H and CAN‑L). Connect CAN‑H to CAN‑H
and connect CAN‑L to CAN‑L for a two-wire connection. A three-wire connection (CAN‑H,
CAN‑L and CAN‑GND) may be necessary in exceptional cases, e.g. with a high EMC load or a
significant difference in grounding potential. Connect CAN‑H to CAN‑H, CAN‑L to CAN‑L and
CAN‑GND to CAN‑GND for a three-wire connection. The shield wire of the CAN cable is only
connected to the metal housing of the panel on one side.
CAN2 H
CAN2 L
CAN1 H CAN2 G
CAN1 L
CAN1 G
CAN1 H CAN1 H
CAN1 L CAN1 L
CAN1 G CAN1 G
Notice!
i The distance between two nodes in loop topology can be determined by reading off the value
at two nodes in the diagram.
Figure 6.2: CAN network: Achievable cable length, depending on the number of nodes and the cable
resistance
N= number of nodes
Icon Description
Icon Description
CAN cable
Housing
Note: In order to simplify the overview of various networking
patterns, the figures in this chapter show always a small panel
housing for symbolizing a panel. This small housing does not
provide in all presented cases sufficient space to mount the
displayed switches, media converters and gateways. Use the
Safety Systems Designer to ensure, that you order the correct
amount and the correct size of housings to install the equipment.
AVENAR panel
FPA
Icon Description
Media converter
1 2
1 2 3 4 1 2 3 4
1 2 1 2
Figure 7.3: Left side: without panel network, Right side: with panel network
Only for more than two services connected to the panel, the Ethernet switch is required.
For ranges greater than 100 m the range extension with media converters is mandatory. For
ranges less than 100 m the media converters might not be required.
1 2 1 2
1 2
7.7 Panel network over two Ethernet loops with redundant panels
1 2 1 2
1 2 1 2 1 2 1 2
Figure 7.8: Connect Ethernet and CAN network with redundant panels
For ranges greater than 100 m the range extension with media converters is mandatory. For
ranges less than 100 m the media converters might not be required.
1 2 1 2 4 1 1 4
Figure 7.9: Left side: in Ethernet network Right side: in CAN network
For ranges greater than 100 m the range extension with media converters is mandatory. For
ranges less than 100 m the media converters might not be required.
Procedure
1. For connecting the Secure network gateway, connect it to the ETH4 port of the redundant
panel controller.
2. In the CAN network an Ethernet cable is required from the ETH1 to the ETH1 port of the
redundant panel controller. Configure the ETH1 settings in the FSP-5000-RPS Net
interface-Ethernet window:
– For Line Type select Link
– A line number greater than 0 in Connected to Line Number causes that the
connection is supervised.
3. For both, CAN network or Ethernet network, configure the ETH4 settings in the FSP-5000-
RPS Net interface-Ethernet window:
– Enter 0 in Connected to Line Number.
– Mark Use Port.
1 2 1 2 1 1 2
Figure 7.10: Left side: in Ethernet network Right side: in CAN network
For ranges greater than 100 m the range extension with media converters is mandatory. For
ranges less than 100 m the media converters might not be required.
Procedure in CAN network
1. For connecting the Secure network gateway, connect it to the ETH2 port of the redundant
panel controller.
2. In the CAN network an Ethernet cable is required from the ETH1 to the ETH1 port of the
redundant panel controller. Configure the ETH1 settings in the FSP-5000-RPS Net
interface-Ethernet window:
– For Line Type select Link
– A line number greater than 0 in Connected to Line Number causes that the
connection is supervised.
3. Configure the ETH2 settings in the FSP-5000-RPS Net interface-Ethernet window:
– Enter 0 in Connected to Line Number.
– Mark Use Port.
ETH1 2 3 4 ETH1 2 3 4
1 2 3 1 2 3
Figure 7.11: VAS and hierarchy panel interface to redundant AVENAR panel
8 Remote Services
The following services belong to Remote Services:
– Remote Connect
– Remote Alert
– Remote Maintenance
Prerequisite for Remote Alert and Remote Maintenance is Remote Connect.
Notice!
i While Remote Connect supports connection to a panel network via Ethernet or CAN, Remote
Alert and Remote Maintenance functionality is only supported when Ethernet networking
between panels is provided and configured for service usage.
Remote
Connect
Notice!
To prevent sending EN 54-2 relevant multicast traffic to the router, use the Ethernet switch (in
general MM, BPA-ESWEX-RSR20) approved with panel version 2.8. Activate IGMP snooping of
the Ethernet switch, see the corresponding section in the Installation chapter of the
Networking manual.
Notice!
The internet router (or the company network which provides internet access) as well as the
Secure network gateway must provide separated sub-networks. Panels of the panel network
may not be placed in the sub-network of the internet router. Also overlapping of the sub-
networks is not possible.
In case of overlapping sub-networks you have to separate the sub-networks by changing the
IP addresses on panel network side.
i Additionally you have to propagate the changes to the Secure network gateway. To do so,
launch the web interface via a web browser:
- Address: https://192.168.1.254
- User name: bosch
- Password: ipti83
Under Configuration -> Network (LAN) you can change the IP address. Consider, that the
Default gateway: address in the panel controller configuration must match the IP address of
the Secure network gateway.
Notice!
i In accordance with DIBt guidelines, remote resetting is not permitted via Remote Services to
restore the operational readiness of door control systems with motorized opening assistance.
The following topology shows a CAN network where a Secure network gateway is connected
to the network via Ethernet port.
CAN
Remote
Connect
Remote
Maintenance
Notice!
i Ethernet connections used only to transfer Remote Maintenance data may be realized as
Ethernet or fiber optic cables. Note the permitted maximum cable lengths.
Notice!
Remote
Maintenance
Caution!
Remote Services require a secure IP connection. Bosch Remote Services or connection with
Private Secure Network is required.
! With Private Secure Network an IP network is provided, which is based on DSL with an
optional wireless access on the panel side (EffiLink). Remote Services for Private Secure
Network is only available in Germany with a service agreement with Bosch BT-IE.
Notice!
Remote
Maintenance via
Private Secure
Network
Service
Center
Figure 8.5: Remote Maintenance for Private Secure Network
For Remote Maintenance, you must enter the server IP address and port of the Remote
Maintenance system server in the FSP-5000-RPS programming software.
Assign a unique Panel Network ID to the network.
Switch for connecting the CMS must be programmed separately
Program the IP address and redundancy settings of the switch, see Settings on switch, page
49. As the switch is installed in the immediate vicinity (without intermediate space), the
power supply does not have to be designed redundantly and the fault outputs are therefore
not used.
Make sure that the RSTP settings in the panel controllers, in FSP-5000-RPS and in Ethernet
switch are identical.
Notice!
To avoid reconfigurations or adjustments when using Remote Services, ensure that the
following requirements are met:
i - panel with firmware 2.19.7 or higher, all panels connected via Ethernet, Ethernet interfaces
enabled and standard Ethernet settings
- Remote Connect enabled in the FSP-5000-RPS panel configuration
- Secure network gateway for Remote Services available
- computer with FSP-5000-RPS 4.8 or higher installed and internet access
Notice!
Instructions
For using Remote Services you must be user of a Remote Portal account.
Step 1: Create a Remote Portal account
You can have multiple users under one Remote Portal account. Each Remote Portal account
has one unique Remote ID, which is meant to represent one company. If you cannot use an
existing Remote Portal account, you have to create one:
1. On https://remote.boschsecurity.com -> Sign Up enter your name, your company and
your email address and create a password. Observe the terms and conditions and select I
agree to the terms and conditions. Also observe the privacy statement and select I agree
to the privacy statement.
2. Click Register.
The Remote Portal promptly sends an email to the provided address containing an
activation link.
3. For activating the account click the activation link. On the Remote Portal click your user
name and select Account Settings. Here you find your Remote ID. You will need this
Remote ID at the panel controller later.
To give each of your technicians an own account you can create several users for the same
Remote ID:
You are logged in to the Remote Portal.
4 Select Users -> New Technician. Then enter the required data and confirm with Save.
Step 2: Connect Secure network gateway
For establishing Remote Services use a Secure network gateway.
1. Connect the WAN port of the Secure network gateway to the internet router or to the
company network which provides the internet access.
2. On the internet router or company network check the availability of the following
protocols and ports, to the Secure network gateway (required for connection to Remote
Services).
IPsec VPN UDP 500 and UDP 4500 for Remote Connect
3. Connect the LAN1 port of the Secure network gateway to the designated Ethernet port of
the panel controller using the supplied CAT5 RJ45 network cable. Observe the possible
topologies.
4. Connect the Secure network gateway to a 100 V - 230 V mains supply using the supplied
power supply.
WAN LED on (blue), when the connection to the internet has been established. VPN LED on
(blue) shortly after, which indicates that a VPN connection to the Remote Portal has been
established.
Each connected panel or panel network has one unique System ID.
Separating sub-networks (VPN LED off)
Connecting the Secure network gateway for Remote Services fails in case of overlapping sub-
networks (VPN LED off). The following example shows a Secure network gateway and a panel
controller in the same address range as the DSL router.
192.168.1.12
. 192.168.2.254 192.168.2.1
(via DHCP)
DSL router
A Secure network gateway detects overlapping sub-networks unambiguously: The Alarm LED
is blinking continuously.
Separating the sub-networks is done by changing the third octet of the IP address. You change
the IP addresses on panel network side. After changing the IP address you have to propagate
the changes to the Secure network gateway. To do so, launch the web interface via a web
browser:
- Address: https://192.168.1.254
- User name: bosch
- Password: ipti83
Under Configuration -> Network (LAN) you can change the IP address. Consider, that the
Default gateway: address in the panel controller configuration must match the IP address of
the Secure network gateway.
Step 3: Establish remote connection
1. At the panel use standard Ethernet settings.
2. Restart the panel.
3. For authentication select Configuration -> Network Services -> Change date / time, enter
the current date, and confirm your settings.
4. Select Configuration -> Network Services -> Remote Services, and enter the Remote ID.
You can check the status of the remote connection: Select Diagnostics -> Network Services ->
Remote Services at the panel controller.
Step 4: Assign license in the Remote Portal
To activate the usage of the Remote Services you have to assign a license in the Remote
Portal. One license is automatically supplied to your account with the first successful
connection.
Notice!
state with the VAS. In case of a fire condition, the fire panel can automatically start voice
announcements using virtual VAS triggers that are activated by rules which are configured in
FSP-5000-RPS. The fire panel generates a supervisory message when an evacuation event is
started from the VAS. A malfunction on the VAS will generate a fault message on the user
interface of the fire panel.
Through the graphical user interface of AVENAR panel the operator has the possibility to
silence the announcements of the fire panel. The operator can request a status overview of all
virtual triggers. Each virtual trigger can be marked with an unambiguous label containing the
location and message type. A clearly distinctive color is reflecting the condition of each virtual
trigger. An operator with L2 user rights can start and stop the voice announcement in the
selected virtual trigger manually.
PAVIRO or Praesideo can be connected to FPA and AVENAR panel.
Due to its networked topology PRAESENSA requires an interface with encrypted data
communication. Only use AVENAR panel running on panel controller firmware version 4.x to
connect with PRAESENSA.
Smart Safety Link over Ethernet was introduced in panel controller firmware version 2.11 and
FSP-5000-RPS version 4.3.
Warning!
Ethernet security risks
! Do not connect PRAESENSA to FPA-5000/FPA-1200 using Smart Safety Link due to Ethernet
security risks.
Notice!
Notice!
Notice!
i VdS 2540
The voice alarm system must be flush with the fire panel in one single room. Otherwise the
requirements of VdS 2540 for data transmission paths are not fulfilled.
Notice!
i If an MPC-xxxx-B panel controller shall be used for the direct connection to a Praesideo/
PAVIRO system a cross-over patch cable is required as neither Praesideo/PAVIRO nor the
MPC-xxxx-B supports Auto-MDI(X).
9.1.2 PRAESENSA
PRAESENSA is a networkable voice alarm system using an IP-network for audio and control.
Always connect AVENAR panel through a PRA-ES8P2S Ethernet switch, 8xPoE, 2xSFP to
PRAESENSA.
PRAESENSA
FPE-8000-PPC
FPE-2000-PPC
48 VDC
PRA-ES8P2S
Caution!
Ethernet security risks
Do not use Smart Safety Link to connect PRAESENSA to FPA-5000/FPA-1200. Only use
! AVENAR panel and AVENAR keypad 8000 in the complete network. For connecting
PRAESENSA to FPA-5000/FPA-1200 use relay contacts as specified in TI2363/2021. Otherwise
Ethernet security risks occur.
Notice!
PRAESENSA to AVENAR panel
- Use PRA-ES8P2S exclusively for Smart Safety Link. Besides the PRA-SCL System controller
do not connect other PRAESENSA equipment to the Ethernet ports of the Ethernet switch,
8xPoE, 2xSFP. Do not use the Ethernet switch, 8xPoE, 2xSFP for connection to a Building
Management System, Hierarchy panel, Secure Network Gateway for Remote Services, etc.
i - Use a panel containing only one panel controller to connect with PRAESENSA using Smart
Safety Link. Smart Safety Link to PRAESENSA is not yet compatible with panel controller
redundancy. The panels in the network that are not directly connected to PRAESENSA may
contain panel controller redundancy.
- Use CAN-Bus topology for the panel network. Do not use an Ethernet panel network.
- All AVENAR panel and all AVENAR keypad 8000 in the network must run with panel firmware
4.x.
Procedure
1. Mount the PRA-ES8P2S Ethernet switch in the PRAESENSA rack. Install PRA-SCL flush to
AVENAR panel, in one single room. Do not mount the PRA-ES8P2S Ethernet switch in the
AVENAR panel enclosure.
2. PRAESENSA must supply the power for PRA-ES8P2S.
3. Configure the PRA-ES8P2S Ethernet switch:
– only allow unicast communication between FPE-8000-PPC and PRAESENSA
Controller
– block all multicast communication
– disable RSTP
4. Check the mode of PRAESENSA, it must run in DHCP mode. Zeroconf mode is not
supported when using Smart Safety Link.
5. Connect the PRAESENSA Controller by a single Ethernet cable (RSTP disabled).
6. For the Smart Safety Link configuration of AVENAR panel, select Encrypted VAS over IP
in FSP-5000-RPS.
Praesideo | Praesideo |
PAVIRO PAVIRO
Praesideo |
PAVIRO
Figure 9.3: Multiple direct VAS interfaces
For each node, for which you want to deactivate panel networking over IP, perform the
following procedure in FSP-5000-RPS:
1. Select the node for deactivating panel networking.
2. Select Use Ethernet Settings.
3. Deselect Panel Networking over IP.
4. Click Apply .
Notice!
i VdS 2540
The voice alarm system must be flush with the fire panel in one single room. Otherwise the
requirements of VdS 2540 for data transmission paths are not fulfilled.
Notice!
i VdS 2540
To meet the requirements of VdS 2540 for data transmission paths, use fiber optic cable for
Ethernet connections. For connections within a housing, you can use TX Ethernet cables.
Praesideo |
PAVIRO
10 Installation
Checklist
Before starting with the installation of the network, please review all of the points set out
below.
– Ethernet and CAN
– The requisite line lengths of the Ethernet TX, Ethernet FX and CAN TX and CAN FX
cables are less than their maximum length.
– The entire peripherals and their cabling in the individual panels are planned.
– Network planning
– All IP addresses and network settings for the individual panels and additional
network components are planned and at your disposal.
– An overview of the additional components to be installed, such as Ethernet switches
and media converters, and their cabling with neighboring panels is at your disposal.
– An overview of the network topology to be installed is at your disposal.
– All network redundancy settings have been planned and are at your disposal.
Notice!
i The media converters are only supplied with power via power supply terminal 1.
The error LED on the media converter is therefore continuously lit. However, this does not
affect the functionality of the device.
Notice!
Use only the following cables for networking:
Ethernet cable
Ethernet patch cable, shielded, CAT5e or better.
Notice!
i Refer to the installation guides for the mounting kits for information on how to install a media
converter in the housing of a panel: FPM 5000 KMC (F.01U.266.845) FPM‑5000‑KES
(F.01U.266.844)
Notice!
i The maximum transmission section for multimode media converters via FX is 2000 m.
The maximum transmission section for single mode media converters via FX is 40 km.
Using the DIP switches, configure the media converter as shown in the following figure.
Notice!
i Only change the DIP switch settings on media converters when they are de-energized.
1
0
! (e.g. magnifying glass, microscope). Failure to observe this notice poses a danger to the eyes
at a distance of less than 100 mm. The light emerges at the visual terminals or at the end of
the fiber optic cables connected to these. CLASS 2M laser diode, wavelength 650 nm, output
< 2 mW, in accordance with IEC 60825-1.
Notice!
i Refer to: Installation guide for the Mounting kit for Ethernet switch FPM‑5000‑KES
(F.01U.260.523).
Notice!
Refer to the manufacturer's user guide for an exact description of the installation and
i configuration of the switches. Access data:
User: admin
Password: private
Use a browser to call up the configuration user interface for the switches.
You must perform the following settings in the switch:
– Assign IP address, page 49,
– Program redundancy settings, page 50.
Furthermore, optional settings e. g.:
– Programming the fault relay, page 50,
– Programming connection monitoring, page 51,
– Activating IGMP snooping, page 52.
Notice!
Please refer to the following manufacturer documents for an exact description of the
i installation and configuration of the switches:
Installation user guide
Web-based interface reference guide
Notice!
The settings in the individual menu items in the switch configuration take effect after clicking
i on Write.
The settings are only saved permanently, i.e. so that they are retained even after the device is
restarted, if under Basic Settings -> Load/Save in the Save field you select the item On the
device and click on the Save button.
Notice!
The settings in the individual menu items in the switch configuration take effect after clicking
i on Write.
The settings are only saved permanently, i.e. so that they are retained even after the device is
restarted, if under Basic Settings -> Load/Save in the Save field you select the item On the
device and click on the Save button.
i requirements is met:
There is a connection between 2 switches. This is possible in the case of a backbone with
sub-loops, for example.
The power supply to the switch is designed redundantly.
Notice!
Please refer to the following manufacturer documents for an exact description of the
i installation and configuration of the switches:
Installation user guide
Web-based interface reference guide
Notice!
i The settings in Device Status also apply to the fault LED of the switch.
Click on Write.
Notice!
The settings in the individual menu items in the switch configuration take effect after clicking
i on Write.
The settings are only saved permanently, i.e. so that they are retained even after the device is
restarted, if under Basic Settings -> Load/Save in the Save field you select the item On the
device and click on the Save button.
i You only need the setting for the connection monitoring if you are using the fault relay of the
switch.
If you want to use the fault relay to monitor the connections of the switch, then you must
specify in the switch configuration which ports of the switch should be monitored.
Activate the Forward Connection Error check box for the individual ports in the Basic
Settings -> Port Configuration menu.
Only connections for which Forward Connection Errors has been activated are monitored.
Click on Write.
Notice!
The settings in the individual menu items in the switch configuration take effect after clicking
i on Write.
The settings are only saved permanently, i.e. so that they are retained even after the device is
restarted, if under Basic Settings -> Load/Save in the Save field you select the item On the
device and click on the Save button.
In the QoS/Priorität -> Global menu, change the settings of the drop-down list field under
Trusted Mode to trustIpDscp.
Click on Write.
Notice!
The settings in the individual menu items in the switch configuration take effect after clicking
i on Write.
The settings are only saved permanently, i.e. so that they are retained even after the device is
restarted, if under Basic Settings -> Load/Save in the Save field you select the item On the
device and click on the Save button.
4 On mechanical rotary switches on the rear of the panel set the RSN with, and note it on
the sign below the rotary switches.
Configuration of the topology
The DIP switches for the configuration of different topologies are located on the rear.
4 Mark the selected setting on the sign near to the DIP switches.
Standalone Panel and Redundant Standalone Panel
CAN internal
Figure 10.1: DIP switch settings for standalone panel (top: AVENAR, bottom: FPA, left: regular, right: redundant)
001 001
CAN internal
Figure 10.2: DIP switch settings for remote keypad as redundant panel (AVENAR only)
Loop
L max
CAN1 CAN2 CAN1 CAN2 CAN1 CAN2 CAN1 CAN2 CAN1 CAN2
ETH1 ETH2 ETH1 ETH2 ETH1 ETH2 ETH1 ETH2 ETH1 ETH2
Figure 10.3: DIP switch settings for loop (top: AVENAR, bottom: FPA)
L max
CAN1 CAN2 CAN1 CAN2 CAN1 CAN2 CAN1 CAN2 CAN1 CAN2
CAN internal
ETH1 ETH2 ETH1 ETH2 ETH1 ETH2 ETH1 ETH2 ETH1 ETH2
Figure 10.4: DIP switch settings for loop with redundant panels (top: AVENAR, bottom: FPA)
L max
CAN1 CAN2 CAN1 CAN2 CAN1 CAN2 CAN1 CAN2 CAN1 CAN2
CAN internal
ETH1 ETH2 ETH1 ETH2 ETH1 ETH2 ETH1 ETH2 ETH1 ETH2
Figure 10.5: DIP switch settings for loop with remote keypad (AVENAR only)
11 Cabling
To create an EN 54-2-compliant system, connect the RSTP switches and the media converters
via the monitored power supply of the fire alarm control panel.
– For the power supply to the media converters and to the RSTP switches use the 24 V
output of either the BCM 0000 B or FPP-5000.
– If you have connected a redundant power supply or are creating a switch-to-switch
connection, then the fault outputs of the RSTP switch must be monitored via panel
inputs. For example, use the inputs on the panel controller or IOP 0008 A.
– In the case of the media converter, the Link Fault Pass-Through function must be
activated. Configuration is performed via the DIP switch of the media converter.
Notice!
Use only the following cables for networking:
Ethernet cable
Ethernet patch cable, shielded, CAT5e or better.
i Please note the minimum bending radii specified in the cable specification.
Fiber optic cable
Multi-mode: fiber optic Ethernet patch cable, duplex I‑VH2G 50/125μ or duplex I‑VH2G
62.5/125μ, SC plug.
Single mode: fiber optic Ethernet patch cable, duplex I-VH2E 9/125μ, SC plug.
Please note the minimum bending radii specified in the cable specification.
Notice!
i Note the direction of transmission of the FOC fibers when connecting the FX cabling of the
media converters.
BCM-0000-B
24V (2,8 A)
24V
MAIN POWER
MAIN POWER
BCM-0000-B
TROUBLE
BATTERY 1
TROUBLE
BATTERY 2
TROUBLE
Figure 11.1: Connection of media converter to power supply and to panel controller IN1/IN2
Icon Description
24 V power supply
Icon Description
Transmission of fault
Media converter
Notice!
The fault relay only has to be connected for applications where at least one of the following
i requirements is met:
There is a connection between 2 switches. This is possible in the case of a backbone with
sub-loops, for example.
The power supply to the switch is designed redundantly.
Connection of switches with reporting of faults to the inputs of the IOP module:
OUT1
OUT2
OUT3
OUT4
OUT5
OUT6
OUT7
OUT8
GND
GND
GND
GND
IOP 0008 A
GND
GND
GND
GND
IN1
IN2
IN3
IN4
IN5
IN6
IN7
IN8
BCM-0000-B IOP 0008 A
-
+
24V Input Input 24V (2,8 A)
MAIN POWER
MAIN POWER
BCM-0000-B
TROUBLE
BATTERY 1
TROUBLE
BATTERY 2
TROUBLE
Icon Description
24 V power supply
Transmission of fault
RSTP switch
IN1 IN2
BCM-0000-B
24V
-
+
24V (2,8 A)
MAIN POWER
MAIN POWER
BCM-0000-B
TROUBLE
BATTERY 1
TROUBLE
BATTERY 2
TROUBLE
Figure 11.3: Connection of switch to the power supply and to the panel controller
Icon Description
24 V power supply
Transmission of fault
RSTP switch
Notice!
Notice!
Note that the FPP‑5000 External power supply and the PSF 0002 A (PSS 0002 A) must be
i installed in the immediate vicinity (without intermediate space) of the remote keypad. It must
not be possible to touch the connecting cables between the components, as they are not
monitored for creeping short circuit and creeping open monitoring.
Notice!
i Use only media converters to connect a Remote keypad to an Ethernet panel network.
The use of switches is not permitted for the Remote keypad.
Notice!
i The functional earth of the Remote keypad must always be placed in position when
connecting the unit to an Ethernet panel network.
PSF 0002 A /
PSS 0002 A
MAIN POWER
MAIN POWER
TROUBLE
BCM-0000-B
BATTERY 1
TROUBLE
BATTER Y 2
TROUBLE
Icon Description
24 V power supply
Media converter
12 FSP-5000-RPS settings
You can program the entire network with the RPS programming software via the USB port,
network interface or the serial interface of a panel. To do this, you must have configured the
network settings on the panel and restarted these in order to commission the network.
Alternatively, you can also use the network interface of a switch that is connected to the
network.
FX OPC-Server
FX FX
6
7
ETH1 ETH2 ETH1 ETH2 ETH1 ETH2
8
CAN1 CAN2 CAN1 CAN2 CAN1 CAN2
3 5 1
2 1
OPC-Server
12.3 Switches
If you are using switches in your network, you must create these switches in the FSP-5000-
RPS programming software. You can assign up to 128 ports to each created switch. In order to
create your network, you can assign the connected line numbers to the individual ports.
Notice!
EN 54
The connection of a building management system (e.g. BIS) via an Ethernet interface using an
i OPC server or an FSI server is EN54 compliant if the EN54 relevant functions are performed
by the fire panel solely. Any EN54 relevant control or administration (e.g. control of
notification appliances or administration of switch-off) by the building management system
requires an individual EN54 certification of the overall system by a certification body.
Notice!
Notice!
i You must assign the UGM‑2040 server to each network node from which statuses should be
transmitted.
In order to connect a panel to the UGM‑2040, you must simulate the physical structure of the
network in RPS. This also includes the line numbers between the connecting panel controller
and the switches of the UGM‑2040.
UGM-2040
1 2’
2 1’
13 Appendix
13.1 Ethernet error messages
Please note that in the event of an error, the error message plus the group error is displayed
in each instance.
135.0.1.0 Network 1.0 General Network There is an incompatible version of the panel network
Trouble software. There are 2 different software versions
135.0.6.1 Network 2.1 Duplicate IP Address An IP address has been assigned twice.
135.0.6.2 Network 2.2 IP Settings The IP configuration of the reporting panel is different
to the RPS configuration
135.0.6.3 Network 2.3 Redundancy Settings The redundancy configuration (RSTP, RSTP parameter,
dual homing or nothing) of the reporting panel is
different to the RPS configuration.
135.0.7.1 Network 3.1 RSTP Fallback The reporting panel has switched from RSTP mode to
STP mode (compatibility mode). A STP device has
been connected to the network.
135.0.7.2 Network 3.2 RSTP Topology Change The RSTP network topology has changed. For
example, another RSTP device has been added to the
network. This message may also arise in the event of
an interruption to the line.
135.0.7.3 Network 3.3 RSTP Link Type An RSTP port of the reporting panel is not in the
Point2Point point-2-point status. Several RSTP devices have been
connected to an RSTP port, for example. Or another
RSTP device has been connected to the RSTP port via
a half-duplex line.
135.0.5.1 Network CAN 1 Trouble Data transmission to CAN bus 1 is restricted. Possible
connection 1.0 causes include: cable breaks, cable not connected,
cable interference.
135.0.5.2 Network CAN 2 Trouble Data transmission to CAN bus 2 is restricted. Possible
connection 2.0 causes include: cable breaks, cable not connected,
cable interference.
Index
A Remote Maintenance 38
Addressing for Private Secure Network 38
Physical node address 12 for Remote Portal 38
Remote Portal 38, 40
C
CAN interface 12, 52 Remote Services 35, 40
CAN network 8 Assign license 42
CAN topologies 10 Connect Secure network gateway 40
Create Remote Portal account 40
E Establish remote connection 41
Ethernet interface 52
License 42
Ethernet network 8
Reorder license 42
Ethernet topologies 10
Separating sub-networks 41
Ethernet, standard settings 13
RS232 interface 52
L RSN 12
Limits: Network 12 RSTP 21
LLDP 21 RSTP parameters 14
M S
MAC address 21 Secure network gateway 35, 40
Maximum limits 12 Services 8
N Standard settings, Ethernet 13
Network
T
Addressing 55 Topologies, CAN 10
Cable 26 Topologies, Ethernet 10
Limits 12
Network diameter 22
U
USB interface 52
Network: Cabling 26
Network: Panel controller 52 V
Networking Voice alarm system 43
Cable length 26
Loop topology 26
Networking over CAN 8
Networking over TCP/IP 8
O
OPC Server 8, 52
P
Panel controller
Networking 52
Parameters
RSTP 14
PAVIRO 8, 43
Physical node address 12
Praesideo 8, 43
R
Redundancy
Addressing 12
Remote Alert 37
Remote Connect 35
202112221820