System functions of PXC4/5/7 devices on BACnet/IP

System functions

PXC4.E16-2
PXC4.E16S-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
PXG3.W100-2/W200-2 web interfaces per IP segment

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
(local only, not for upload to the system due to limitations of the MS/TP network)

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.

  • Recommended number of devices for time synchronization in a PXC5/7: Up to 250 (on the same IP segment)
  • Time synchronization interval: 150 minutes (default)
  • Time synchronization interval value range: 1 to >1000 minutes

Life check
Supervision

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.

  • Recommended number of devices for life check: Max. 250 (on the same IP segment and/or in the MS/TP subnet connected to this PXC5/7 device)
  • Life check time interval: 5 minutes

Integration
of Modbus devices

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.

  • Polling time: 5 seconds to 5 minutes (5 minutes default).

Integration
Adding alarming, trending, scheduling to Modbus devices

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
Common setpoint and room operating mode (common schedulers)

Group manager objects for HVAC allow to set:

  • common setpoints
  • common room operating mode (based on group scheduler and/or calendar)

for a group of DXR room controllers.

  • Recommended number of group manager objects per PXC5/7 device: Max. 50
  • Recommended number of group members per group manager: Max. 250

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).