MOD-6001
September 24, 2018
NEXUS
NX6100/PPC6000 SERIES
MODBUS RTU / TCPIP,
and BACNET/IP
COMMUNICATIONS
DESCRIPTION
The MODBUS interface is designed to c onnect Fireye's NX6100 or PPC6000 Nexus
Controllers to other devices using the 'MODBUS RTU' or 'MODBUS TCP' protocols, using
3 wire RS485. This bulletin shows connections and the available MODBUS memory map for these
controls only.
NX6100/PPC6000 series controllers may be connected to a MODBUS communications system to
enable data collection and limited control functions. The controllers are connected to the MOD-
BUS via the Isolated RS485 Communications terminals on the NX6100 or PPC6000. The MODBUS
function requires a daughter board to be fitted to each controller.
The protocol supported is MODBUS RTU and the data configuration supported is 8-bits, no parity,
1-stop bit. This is the simplest and most common data configuration because the MODBUS protocol
includes 'crc' to ensure data packet integrity.
A network of up to 14 Fireye Nexus NX6100 or PPC6000 controls can be linked toMODBUS.
Consideration needs to be given to the total number of registers to be communicated, refer to page 4
for further details.
MODBUS RTU can be accessed via two daughter boards for the NX6100 or PPC6000. The NXD-
BMB (MODBUS only) or NXDBVSD (MODBUS and variable speed drive) allow access to the
NX6100/PPC6000 through the isolated RS485 terminals. See Figure 1, Section 1.2. Also, refer to
the appropriate bulletin, NEX-6101 or PPC-6001.
The touch-screen NXTSD104 or NX6330 is required to use BACNET/IP because it provides the
Ethernet interface. The protocol is implemented by the firmware running on the touch-screen hard-
ware. BACNET/IP is the only form of the BACNET protocol available for the 6000 series.
1