System functions of PXC4/5/7 devices on BACnet/IP
System functions | PXC4.E16-2 | PXC5.E003 | PXC5.E24 | PXC7.E400S | PXC7.E400M | PXC7.E400L | |
|---|---|---|---|---|---|---|---|
|
BACnet profile (Rev. 1.16) | B-BC | B-BC | B-BC | B-BC | B-BC | B-BC | |
AMEV profile (BACnet 2017) | AS-A / AS-B | AS-A / AS-B | AS-B | AS-B | AS-B | AS-B | |
KBOB profile (BACnet 2017) | AS-CH 1) | AS-CH 1) | AS-CH 1) | AS-CH 1) | AS-CH 1) | AS-CH 1) | |
Time manager RTC (Real Time Clock) or NTP (Network Time Protocol) | Yes | Yes | Yes | Yes | Yes | Yes | |
BBMD (Broadcast Management Device) | Yes | Yes | Yes | Yes | Yes | Yes | |
Device monitoring: Life check of other BACnet devices | No | Yes | Yes | Yes | Yes | Yes | |
Web interface (via IP network, local WLAN access point, and cloud) | Yes | Yes | Yes | Yes | Yes | Yes | |
Number of alarms | 100 | 1,500 2) | 1,200 2) | 1,000 2) | 2,000 2) | 5,000 2) | |
Number of trend blocks 3) | 40 | 200 | 200 | 600 | 600 | 600 | |
Number of trend entries | 20,000 | 200,000 | 200,000 | 500,000 | 500,000 | 500,000 | |
Number of schedulers | 5 | 20 | 20 | 50 | 50 | 50 | |
Schedulers: Number of switching points per day | 20 | 20 | 20 | 20 | 20 | 20 | |
Number of calendars | 5 | 20 | 20 | 50 | 50 | 50 | |
Number of BACnet objects | PXC4.E16-2: 400 PXC4.E16S-2: 250 | 1,500 | 1,200 | 1,000 | 2,000 | 5,000 | |
Web interface - Local operation | Yes | Yes | Yes | Yes | Yes | Yes | |
Web interface - System-wide operation (for assigned devices) | No | Yes | Yes | Yes | Yes | Yes | |
Building X cloud connectivity | Yes 4) | Yes | Yes | Yes | Yes | Yes | |
Number of data points time series (active data points per device) | PXC4.E16-2: 130 PXC4.E16S-2: 70 | 400 | 400 | 400 | 700 | 1400 | |
|
1) AS-CH pending 2) No alarm limitation check in ABT Site. 3) Number of total trend blocks include the offline created and the dynamically created trend log objects. 4) PXC4 has only limited Building X cloud connectivity. PXC4-2 has extended Building X cloud connectivity. |
Number of devices per network range (on BACnet/IP)
Number of devices per network range | Recommended and tested limits 1) |
|---|---|
|
Number of devices per BACnet Internetwork | Up to 1500 1) |
Number of IP segments per BACnet Internetwork | Up to 10 1) |
Number of devices per ABT Site project | 500 |
Number of PXC4/5/7 and DXR devices per IP segment in mixed combinations | Up to 250 2) |
Number of PXC4/5/7 and DXR devices via integrated IP switch (Daisy chain) | Up to 20 in any combination |
Number of MS/TP networks per BACnet Internetwork | Up to 50 |
Number of PXM30.E/40.E/50.E touch panels or | Up to 10 |
Number of PXM30-1/40-1/50-1 touch panels per IP segment | Up to 30 |
PXM30/40/50 and PXG3.W100-2/W200-2: Max. number of assigned devices BACnet/IP devices MS/TP devices |
50 10 |
Max. number of assigned devices for web interface operation on PXC5.E003, PXC5.E24, and PXC7.E400.. BACnet/IP devices MS/TP devices |
50 10 |
Number of assigned devices for supervisory functions (time sync, life check etc.) per PXC5.E003/PXC5.E24/PXC7.E400x | 500 |
Number of Desigo CC management platforms | 1 |
|
1) These figures are based on system communication between the various units for typical systems. For additional information and details, e.g. on topology or communication, see: Application guide for BACnet networks in building automation and control, A6V11159798. 2) When the system only exists of one segment, the number of PXC 4/5/7 and DXR devices can be increased to 500. For details, see Application guide for BACnet networks in building automation and control, A6V11159798. |
System functions of PXC4-2 devices on BACnet MS/TP
System functions | PXC4.M16-2, PXC4.M16S-2 |
|---|---|
|
BACnet profile (Rev. 1.16) | B-BC |
Time manager RTC (Real Time Clock) | Yes |
Web interface (via local WLAN access point) | Yes |
Number of alarms | 100 |
Number of trend blocks | 40 |
Number of trend entries | 20,000 |
Number of schedulers | 5 |
Schedulers: Number of switching points per day | 20 |
Number of calendars | 5 |
Number of BACnet objects | PXC4.M16-2: 400 PXC4.M16S-2: 250 |
Building X cloud connectivity
Enable a secure direct connectivity between the PXC devices to the cloud, leveraging the Building X platform functionalities.
For details, see Buildings X Operations Manager User Guide, A6V11881696 and Building X Energy Manager User Guide, A6V12503191.
System and supervisory controller functions on PXC5/PXC7 devices
|
Full flexibility | PXC5/7 devices are freely programmable and is a flexible system with supervisory controllers to control, monitor, and supervise technical plants in all building types and to cover all the functionalities required to efficiently operate user centric buildings. |
Time sync | A PXC5/7 automation station can be configured as a time manager for other PXC4/5/7 and DXR devices and as well for third-party devices (if they allow this functionality). (Devices on BACnet IP, BACnet/SC, and BACnet MS/TP) A time manager is a dedicated device that defines and distributes the common time for the assigned devices. A common system time is important for synchronized actions (e.g. schedulers or trended data). Time distribution itself is a standardized BACnet service. The time source of the time manager is either NTP (Network Time Protocol) or built in RTC on the device. The time manager can be configured on each device.
|
Life check | A life check device is a dedicated PXC5/7 device that checks the reachability of other BACnet devices and generates an alarm if assigned devices cannot be reached. The devices to be supervised by the PXC5/7 device must be added to the life check list. The table contains the device instance number for PXC4/5/7 and DXR devices. Only the device instance number is available for third-party devices.
|
|
Integration | The PXC5/7 device integrates Modbus TCP and RTU devices and maps Modbus data points (register) to BACnet I/O objects. Mechanism: PXC5/7 receive the Modbus data via polling. The update time of the values depends on baud rate, number of engineered data points, and traffic on the Modbus network.
|
Integration | The PXC5/7 device can add system functionality (alarming, trending, scheduling) to third-party Modbus devices (either Modbus TCP and/or Modbus RTU) System functionality can be added via the CFC program to the BACnet input/output objects mapped from the different Modbus devices.
|
Grouping function | Group manager objects for HVAC allow to set:
for a group of DXR room controllers.
Place the members on the same IP segment as the group manager. Assign the group members to a group manager object. The group assignment can be changed online as well (e.g. via Desigo CC).
|
|
Grouping function | Group manager objects “supply chain” can:
for a group of DXR room controllers.
Place the members on the same IP segment as the group manager. Enter the group members to the list in the group manager object.
|
BACnet MS/TP devices | The PXC5/7 device routes BACnet messages from connected BACnet MS/TP devices to and from BACnet/IP devices (without engineering data points on the PXC5/7 device). The B-BC functionality is available between BACnet/IP networks and BACnet MS/TP devices. Be careful not to overload the BACnet MS/TP network which has a lower performance. In addition, refer to the additional limits of number of MS/TP devices per trunk.
|
BACnet MS/TP devices | In addition to the routing functionality for BACnet MS/TP devices described above, PXC5/7 devices can add system functionality (alarming, trending, scheduling) to third-party BACnet MS/TP devices, e.g. to thermostats or air handling unit controllers. The PXC5/7 device adds additional functionality as defined in the CFC program to the DXR/PXC4/third-party devices on BACnet MS/TP via the BACnet IO connection. |
|
Web interface for assigned devices | The PXC5/7 device provides generic operation via the embedded web interface on the assigned devices without additional engineering or mapping. All BACnet input/output/value objects, scheduler/calendar, local alarms/events are listed in the Generic view. Add the devices to the list of assigned devices. The table contains device instance numbers and device names of PXC4/5/7 and DXR devices. Only the device instance numbers are available for third-party devices.
|
BBMD | On medium to large projects, the IP networks are structured into different IP segments via IP routers. The IP routers limit the network traffic by blocking BACnet broadcast messages. The PXC5/7 device can serve as BBMD (BACnet Broadcast Management Device). The main purpose of BBMDs is to redistribute the broadcast messages that BACnet/IP requires for discovery of BACnet/IP devices on IP networks interconnected via IP routers. For details on how to structure the network, see Application Guide for BACnet Networks in Building Automation, A6V11159798. |
Central functions for lighting and blinds | The group manager objects for light and blinds for a group of DXR room automation stations are placed in a DXR2.E18 automation station with app type “Central functions”. DXR2 room automation stations with central functions can be used for the HVAC grouping functions and, if required, also for the grouping function “Seasonal compensation” for HVAC. In this use case, the PXC5/7 device hosts the scheduler/calendar for different groups of room automation stations engineered in the central function DXR automation station. For details on how to structure the network, see Application Guide for BACnet Networks in Building Automation, A6V11159798.
|
Remark: PXC4 on IP also supports some of the above-mentioned functionality but PXC4 focuses on controlling plants including the necessary system functionality. Comply with the system limits listed in the tables of this document.