AERCO ProtoNode FPC-N34 & FPC-N35 User Manual
CHAPTER 2 – BACnet/LonWorks Setup
Page
12
of
108
AERCO International, Inc.
•
100 Oritani Dr.
•
Blauvelt, NY 10913
OMM-0107_0B
03/07/2017
Ph.: 800-526-0288
GF-150
2.3 Configuring Device Communications
2.3.1
Set Modbus COM setting on all of the Devices connected to the ProtoNode
•
All of the Serial devices connected to ProtoNode
MUST have the same Baud Rate,
Data Bits, Stop Bits, and Parity settings.
•
The Figure below specifies the device serial port settings required to communicate with
the ProtoNode.
Serial Port Setting
Device
Protocol
Modbus RTU
Baud Rate
9600
Parity
None
Data Bits
8
Stop Bits
1
Figure 2-4: Modbus RTU COM Settings
2.3.2
Set Modbus RTU Node-ID for each of the Devices attached to the ProtoNode
•
Set Modbus Node-ID for each of the devices attached to ProtoNode. The Modbus
Node-ID’s need to be uniquely assigned between 1 and 255.
o
The Modbus Node-ID that is assigned for each device needs to be
documented.
The Modbus Node-ID’s assigned are used for designating the Device
Instance for BACnet/IP and BACnet MS/TP (
Section 2.5.2
•
The Metasys N2 and Modbus TCP/IP Node-ID will be set to same value as the Node-ID
of the Modbus RTU device.
2.4 Selecting the Desired Field Protocol and Enabling Auto-Discovery
2.4.1
Selecting Desired Field Protocol
•
ProtoNode FPC-N34 units use the “S” bank of DIP switches (S0 – S2) to select the
Field Protocol.
o
See the table in the Figure below for the switch settings to select BACnet MS/TP,
BACnet/IP, Modbus TCP/IP, or Metasys N2.
o
The OFF position is when the DIP switches are set closest to the outside of the
box.
