Data Sheet for Product

Siemens Industry, Inc. Page 5 of 7
Modbus 500 Driver on the PXC Series Platform
Functionality
Notes on System Architecture
The Modbus 500 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
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 500 Modbus points per driver.
NOTE:
The limit of 500 Modbus points per driver does not apply to I/O, addressing,
diagnostic, and P1 application points.
Functionality
The Modbus 500 Driver provides communication between the APOGEE® Automation
System and the vendor's Modbus system.
The Modbus 500 Driver can be loaded into PXC Modular or PXC-36 hardware. The
driver is a microprocessor-based, multi-tasking platform designed for multi-system
communication and control.
● When using a P2 ALN, the Modbus 500 Driver communicates with Insight
software, other APOGEE field panels and controllers, and the vendor's Modbus
system.
● When using a BACnet ALN, the Modbus 500 Driver communicates with Insight
workstation software, other APOGEE field panels and controllers, and the
vendor's Modbus system.
Through the Insight workstation, the Modbus points can be monitored and
commanded. The Modbus points integrated into the APOGEE Automation System can
be accessed by system applications, such as Powers Process Control Language
(PPCL), scheduling, trending, and alarming.
The Modbus 500 Driver will not affect, in any way, the operating sequence or safeties
as factory-programmed into the vendor's Modbus system.
NOTE:
BACnet Field Panel Web Server licenses LSM-FPWEB, LSM-FPWEBPL and LSM-
FPWEBPLHST are now retired. Launch Pad must be used instead and is available
for free download from Standard Apps/Partner Extranet.