CerberusPro configuration

From WikiSiwenoid
Jump to: navigation, search
Language: English  • magyar

Previous chapter-> Project backup/restore / Next chapter-> Satel configuration


Configuring CerberusPro in stand alone mode

CerberusPro (SIEMENS) control unit uses Bacnet protocol to communicate with Siwenoid. Communication settings can be done in FXS72xx editor of CerberusPro control unit.

Sinteso 1 network tree.png

Open network settings of a CerberusPro. In this tutorial we discuss a basic configuration when a SIWENOID and a CerberusPro control unit are in the same network segment.


Sinteso 1 global Bacnet config.png

First check global BACnet configuration. These settings should be used for proper communication.


Sinteso 1 Bacnet client config.png

BACnet device ID is the SIWENOID's (as a BACnet client) address. This address has to be set in SIWENOID container definition.


Sinteso 1 FC ethernet.png

Set the IP address of your control unit. This parameter should also be set in thee container definition of SIWENOID.


Sinteso 1 Ethernet subnet.png

Set the network mask of control unit ethernet interface. SIWENOID should be in the same network segment as the control unit.


Sinteso 1 Bacnet device object.png

This address field is the BACnet address of the CerberusPro control unit. This is important when you import a SibX file into SIWENOID.


Sinteso 1 Bacnet device object details.png

Usually you have to leave this field on default. (BBMD should be used when the control unit and SIWENOID are not in the same network segment.)


Assign.png

In order to make CerberusPro communicate with Siwenoid from a subnet(Control unit's subnet) to another subnet(Siwenoid's subnet) a GAP creation is necessery in 'Functions' submenu.


Route.jpeg

It is necessery to create a route inside the GAP (under overview tab) by setting up the Destination address (Pointing to Siwenoid's subnet, or IP of the Siwenoid client PC), Network mask and Gateway(CerberusPro's subnet router IP).


Configuring SIWENOID in stand alone mode

GD 015.png

Create a new container in SIWENOID. Select control unit type, and select protocol. There are different protocol for <MP5 and >MP5. Be sure to use the appropriate. Host address is the address of CerberusPro control unit. Subnet is the network mask of BACnet protocol. 47808 is the default BACnet port number. Local address can be used only if your computer has more than one ethernet interface. Normally it should be left empty. Local Device ID is the SIWENOID (as a BACnet client) BACnet ID. This should align the settings of CerberusPro FSX72xx editor parameters. If it is required, UDP port field can be filled when the Control unit and Siwenoid is not in the same subnet.


A SibX file can contain datapoints of more than one control unit. An import always fetch only one control unit at a time.

SINTESO0001.png

Use the popup menu on the container. Select "Update from metafile". Now set the id's of the control unit you want to import. Device ID must be equal the control unit address, and Device address must be equal the BACnet ID of control unit. If you have more than one control unit in a SibX then repeat these steps and set the id's of control units one by one.


Finally each control units and their datapoint will be included in the container.


Configuring CerberusPro in SAFEDLINK subnets

Bacnet.png


The settings of Siwenoid in case of a SAFEDLINK build. These examples are from a working system.

Safed2.png


Overview of the sub-net settings.

Subnet1 1.png


Overview of the first sub-net element.

Subnet1 2.png


Overview of the first sub-net element network settings.

Subnet2 2.png


Overview of the second sub-net element.

Safedlink2v2 2.png


Overview of the second sub-net element network settings.




1.ESZKO23Z.PNG


Overview of the first element


1.ESZKOZ DETAILS.PNG


Details of the first element



2.ESZKOZ.PNG


Overview of the second element


2.ESZKO22Z DETAILS.PNG


Details of the second element



Previous chapter-> Project backup/restore / Next chapter-> Satel configuration