Issue
Clarification is required regarding whether Cross Controller Groups can be used in Security Expert systems that use the standard Download Server, or only in systems that use the Enterprise Download Server (EDS). Additional questions were raised regarding cross-controller functionality for alarm transmission, fire door control, and communication between controllers.
Product Line
EcoStruxure Security Expert
Environment
- Security Expert
- Security Expert standard Download Server
- Security Expert Enterprise Download Server (EDS)
- Security Expert version 4.3.393.3 and later
Cause
Changes introduced in Security Expert version 4.3.393.18 modified how controller relationships are managed, resulting in different Cross Controller Group requirements for EDS and non-EDS deployments.
Resolution
Cross Controller Groups can be used without EDS. Beginning with Security Expert version 4.3.393.18, Cross Controller Groups are mandatory when using EDS and optional when not using EDS.
For Security Expert versions 4.3.393.3 through versions earlier than 4.3.393.18, Cross Controller Groups needed to be created for both EDS and non-EDS sites.
Cross Controller Group functionality can be used to reduce communication and .dat file size in non-EDS systems by grouping controllers, for example creating one Cross Controller Group per building. This limits .dat files to include only controllers within the same group. However, communication between controllers in different groups is blocked.
The commands described in AN 180 Security Expert - Cross Controller Operations - Integration Guide (LocalIP = *,#) are only required in specific network configurations where NAT or port forwarding is used and controllers must communicate directly with each other. When controllers and the Security Expert server can reach each other through normal IP routing, the commands outlined in AN 180 Security Expert - Cross Controller Operations - Integration Guide are not required.
For fire door control, a controller-level design using dedicated relay outputs connected directly to inputs on each SP-C controller is recommended to avoid dependence on network communication between controllers. Where a cross-controller solution is required, maintaining separate local door groups per controller is preferred over creating large door groups spanning multiple controllers.
