CerberusPro configuration: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 9: | Line 9: | ||
[[Image:_sinteso_1_network_tree.png|left|thumb|300px]] Open network settings of a CerberusPro site. In this tutorial we discuss a basic configuration when a SIWENOID and a CerberusPro control unit are in the same network segment. | [[Image:_sinteso_1_network_tree.png|left|thumb|300px]] Open network settings of a CerberusPro site. In this tutorial we discuss a basic configuration when a SIWENOID and a CerberusPro control unit are in the same network segment. | ||
<br style="clear: both" /> | <br style="clear: both" /> | ||
[[Image:_sinteso_1_global_Bacnet_config.png|left|thumb| | [[Image:_sinteso_1_global_Bacnet_config.png|left|thumb|500px]] First check global BACnet configuration. These settings should be used for proper communication. | ||
<br style="clear: both" /> | <br style="clear: both" /> | ||
[[Image:_sinteso_1_Bacnet_client_config.png|left|thumb| | [[Image:_sinteso_1_Bacnet_client_config.png|left|thumb|500px]] BACnet device ID is the SIWENOID (as a BACnet client) address. This address has to be set in SIWENOID container definition. | ||
Revision as of 13:31, 11 December 2014
| Language: | English • magyar |
|---|
Previous chapter-> Project backup/restore / Next chapter-> Detectomat configuration
Configuring CerberusPro
CerberusPro (SIEMENS) control unit uses Bacnet protocol to communicate with Siwenoid. Communication settings can be done in FXS72xx editor of CerberusPro control unit.
Open network settings of a CerberusPro site. In this tutorial we discuss a basic configuration when a SIWENOID and a CerberusPro control unit are in the same network segment.
First check global BACnet configuration. These settings should be used for proper communication.
BACnet device ID is the SIWENOID (as a BACnet client) address. This address has to be set in SIWENOID container definition.