Figure 1: System Architecture—Modbus 500 Driver in RTU Master Mode (Firmware 2.x). Notes on System Architecture The Modbus 500 Driver in RTU Master Mode (Figure 1) with Firmware 2.x, supports the following: ● 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. Siemens Industry, Inc.
Modbus 500 Driver on the PXC Series Platform Functionality ● ● ● ● ● ● 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 either Modbus RTU or P1 devices on RS-485 FLNs. Up to 247 device addresses per FLN. TX-I/O Modules.
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.
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 2.x (Figure 3) supports the following: ● 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.
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.
Modbus 500 Driver on the PXC Series Platform Keys to Success Keys to Success Ensure that all Modbus equipment to be integrated supports the Modbus RTU or TCP protocols. The Modbus ASCII protocol is not supported. Benefits Systems integration brings the powerful facility control capabilities of the APOGEE Automation System together with vendor system.
Modbus 500 Driver on the PXC Series Platform Ordering Information Accessories 538-670 Trunk Interface II, 115V 538-675 Trunk Interface II, 230V 538-755 Trunk/RS-422 Interface (115V Power) 538-760 Trunk/RS-422 Interface (230V Power) 536-004 RS-232 Cable License LSM-INT-MDBS500 License to enable the Modbus 500 Driver on PXC Modular or PXC36, BACnet/IP PXC-24 or PXC-16 hardware. LSM-ADAPT License to use the Adaptive Control added in FW 3.5.1/2.8.
