Siemens PXC4.E16-2

Compatibility

BACnet/IP integration, build check required

The manufacturer documents BACnet/IP and the inspected Edge source contains a BACnet client. This guide applies only to Edge builds containing that client; a minimum released Edge version and physical controller pairing have not been verified.

Exact PXC4.E16-2 S55375-C150 with a commissioned BACnet/IP application. PXC4.E16S-2 has different field-integration limits. The supplied guide has no fixed object instances or Modbus register template. Edge build availability and physical pairing are not verified; this path requires a build containing its BACnet client. BACnet/SC is outside the proposed connection.

Connect it with

• 
  Gateway ZGW-20
  From €899 ex VAT Configure Gateway

Models

Specifications

The full E16-2 has 12 universal I/O and 4 relay outputs. Its point budget separates physical I/O from integrated field data: up to 50 onboard plus TXM points and up to 40 integration points, for 90 combined. The apparent 250 M-Bus device address capacity does not create 250 freely usable measurement points.¹

Exact hardware

PXC4.E16-2, S55375-C150; not PXC4.E16S-2 S55375-C152¹

Supply and installation

AC or DC 24 V; DIN-rail or screw mounting; plug-in screw terminals¹

Physical I/O

16 onboard: 12 UIO and 4 relays. Up to 50 onboard plus TXM points.¹

Integrated measurements

Up to 40 total M-Bus, Modbus TCP and Modbus RTU data points; up to 90 combined I/O and integration points¹

Serial field network

One configured RS-485 network for Modbus RTU or M-Bus level converters. M-Bus needs a level converter; device count is constrained by point and object capacity.¹

KNX PL-Link

Up to 64 devices on the full E16-2. These do not count as integration points, but BACnet object limits still apply.¹

BACnet and engineering

BACnet/IP or BACnet/SC; B-BC Rev 1.20. SC node only, not hub. ABT Site engineers and commissions the application.¹

Networking

Two-port Ethernet switch and WLAN for engineering/commissioning; this guide uses the commissioned wired BACnet/IP network¹

Installation envelope

Front parts in DIN cut-out: IP30; terminals: IP20. Operating ambient -5 to +45 °C or +50 °C depending on mounting orientation; follow the datasheet mounting table. Humidity 5–95%, non-condensing.¹

Interface

Documented measurements and integration boundaries for PXC4.E16-2.

• Measured temperatures or other local inputs exposed by the commissioned application.
• Meter readings integrated over Modbus or M-Bus and mapped by the engineer to BACnet objects.
• Object name, description, type, instance, engineering unit and source refresh interval.
• Controller-side reliability or quality information used to distinguish a source failure from a valid reading.

Setup

1. Check the exact controller

   Confirm PXC4.E16-2 S55375-C150 and record firmware and ABT Site project version. Obtain authorised access and the project backup. The E16S-2 has no listed M-Bus/Modbus integration capacity; a visually similar controller is not enough to establish this route.

2. Trace the source of each measurement

   Identify whether each requested point comes from onboard I/O, TXM, Modbus or M-Bus. For field meters retain their original map, scale and update interval. Siemens documents mapping integrated Modbus data to BACnet I/O objects; the mapping is application-specific, not a fixed controller register table.

3. Identify the commissioned object

   Use the controller web interface’s Object view to find the point by name, description or type and inspect its properties. Record the BACnet device and object identifiers with the unit and source. Check quality or reliability in the controller before copying the identity into another system.

4. Check the network and Edge build

   Confirm that the approved network uses BACnet/IP and that the installed Edge build contains its BACnet client. Source inspection does not establish the minimum released version. Do not connect this path directly to BACnet/SC or assume an MS/TP serial client. Retain the existing BMS security design.

5. Compare one read before adding more

   Discover the intended BACnet device, select the approved measurement object and read Present_Value. Compare against Object view and the source instrument at the same time. Confirm the unit, sign and engineering scale; then add only the agreed list. Preserve the map for checks after application updates.

Common questions

Can it collect 250 M-Bus meters?

The datasheet lists addressing capacity of up to 250 meters via level converters, but also limits the full controller to 40 integration data points and applies BACnet object limits. Size the actual points needed from every meter; 250 addresses is not 250 unrestricted meter integrations.¹

Is PXC4.E16S-2 equivalent for metering integration?

No. The type-summary table gives the S variant zero M-Bus/Modbus integration points, zero KNX PL-Link devices and zero configurable RS-485 field networks. Use the exact order code when selecting a controller for existing field meters.¹

Does a downstream Modbus register become the same-numbered BACnet object?

No. Siemens maps integrated data into BACnet I/O objects in the engineered application. Use the project’s object list and property view to identify the measurement; do not convert a register address into an object instance by arithmetic.^2, 3

Does this require Building X?

The specification documents a local embedded web interface and BACnet/IP alongside Building X connectivity. This guide uses the commissioned local interface, not a cloud connection. Obtain ABT Site engineering access and applicable project entitlements from the system owner; no free engineering-tool licence is implied.¹