| PXC4.E16S-2 PXC4.M16S-2 | PXC4.E16-2 PXC4.M16-2 | PXC5.E003 | PXC5.E24 | PXC7.E400S | PXC7.E400M | PXC7.E400L |
|---|---|---|---|---|---|---|---|
|
Data sheet A6V1xxxxxx | 4651312 4651900 | 4651312 4651900 | 1646020 | 3187283 | 2505052 | 2505052 | 2505052 |
Number of inputs / outputs onboard | 16 | 16 | 1 | 24 | 1 | 1 | 1 |
Maximum number of inputs / outputs onboard and TXM | 40 | 40 |
| 80 |
|
|
|
Maximum number of inputs / outputs via TXM |
|
|
| 80 | 100 | 200 | 400 |
Maximum number of integration data points |
| 40 | 500 | 80 | 100 | 200 | 400 |
Maximum number of all TXM-I/Os and integration data points 1) | 40 | 80 | 500 | 120 | 100 | 250 | 600 |
Maximum number of KNX PL-Link devices 1) |
| 64 | 64 | 64 | 64 | 64 | 64 |
Number of built-in hardware interfaces for M-bus devices according to EN 13757-2 | 1 | 1 | 1 | 1 | 1 | ||
Maximum number of simple M-bus loads à 1.5 mA (see row above) | 4 | 4 | 4 | 4 | 4 | ||
Maximum number of M-bus devices wired via level converters (RS485) | The maximum number of M-bus devices wired via level converters depends on available integration data points and the maximum of all TXM-I/Os and integration data points together (see above). Theoretically, per level converter 250 simple M-bus devices can be wired. | ||||||
Number of configurable field level networks per RS485 (either for Modbus RTU, BACnet MS/TP, or M-bus level converters with maximum of 250 M-bus devices each) | - | 1 2) | 2 | 2 | 1 | 2 | 4 |
Maximum number of BACnet MS/TP devices in a field level network 3) 4) |
|
| 2 x 60 | 2 x 60 | 1 x 60 | 2 x 60 | 4 x 60 |
BACnet/SC support | Node 5) | Node 5) | Node, Hub 6) | Node, Hub 6) | Node, Hub 6) | Node, Hub 6) | Node, Hub 6) |
Number of BACnet/SC devices supported as hub | - | - | Up to 100 3) | Up to 100 3) | Up to 100 3) | Up to 100 3) | Up to 100 3) |
|
1) KNX PL-Link data points do not count as integration points. For KNX PL-Link, only the limits on BACnet objects are considered. 2) Modbus RTU or M-bus only (no MS/TP). 3) 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. 4) Dependent on the behavior of the third-party MS/TP devices. 5) Ethernet types only. 6) Hubs with BACnet Secure Connect can also work as regular BACnet routers to non-BACnet/SC networks. |