Data Sheet for Product

Siemens Industry, Inc. Page 3 of 7
Modbus 500 Driver on the PXC Series Platform
Functionality
Notes on System Architecture
The Modbus 500 Driver in RTU Master Mode (Figure 2), with Firmware 3. x , supports
the following:
● BACnet MS/TP or BACnet/IP ALN on Firmware 3.
x .
If the driver is on a BACnet MS/TP network, you can use a standard field panel
with Firmware Revision 3.1 or later as a router to connect to an Insight
workstation. Do not use an Integration Driver as the router.
● Three physical FLNs (FLN 1 through FLN 3) on PXC Modular hardware, which
can be used for connecting and addressing either Modbus RTU or P1 devices on
RS-485 FLNs.
● Up to two physical FLNs (FLN 1 through FLN 2) on PXC-36 hardware, depending
on the ALN chosen, which can be used for connecting and addressing either
Modbus RTU or P1 devices on RS-485 FLNs.
● With Firmware 3.5 and later, one physical FLN (1) on the BACnet/IP PXC-24 and
PXC-16 hardware can be used for connecting and addressing Modbus RTU or P1
devices on RS-485 FLNs. In addition, the Ethernet port can be used for Modbus
TCP or Modbus RTU over IP.
● Up to 247 device addresses per FLN.
● TX-I/O Modules.
● Maximum of 8,000 APOGEE points per driver.
● Maximum of 500 Modbus points per driver.
Figure 3: System Architecture—Modbus RTU Master, Modbus TCP Client, and Modbus RTU over Ethernet
on Firmware Revision 2.x.