Data Sheet for Product

Page 4 of 6 Siemens Industry, Inc.
Modbus 250 Driver on the PXC Series Platform
Functionality
● Up to 95 virtual FLNs (6 through 100) for mapping devices accessed through
Modbus RTU over Ethernet. Diagnostic Point 50 identifies which FLNs are used
for RTU communication (at and below the set value) and which FLNs are used for
TCP communication (above the set value).
● Up to 247 device addresses per FLN.
● TX-I/O Modules.
● Maximum of 8,000 APOGEE points per driver.
● Maximum of 250 Modbus points per driver.
Figure 4: System Architecture—Modbus RTU Master, Modbus TCP Client, and Modbus RTU over Ethernet
on Firmware Revision 3.x.
Notes on System Architecture
The Modbus 250 Driver as RTU Master, Modbus TCP Client, and Modbus RTU over
Ethernet on Firmware Revision 3.
x (Figure 4) 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 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 ALN chosen, can be used for connecting and addressing either Modbus RTU
or P1 devices on RS-485 FLNs.
● Up to 95 virtual FLNs (6 through 100) for mapping devices through an Ethernet
TCP/IP network.
● Up to 95 virtual FLNs (6 through 100) for mapping devices accessed through
Modbus RTU over Ethernet. Diagnostic Point 50 identifies which FLNs are used