Configuring Device Communications; 3.3.1 Input Com Settings On All Devices Connected To The Protonode; 3.3.2 Set Modbus Rtu Node-Id For Each Device Attached To The Protonode; Figure 4: Modbus Com Settings - SMC Sierra Monitor FieldServer ProtoNode FPC-N38 Startup Manual

For interfacing riello array boilers: 905, to building automation systems: bacnet ms/tp, bacnet/ip, modbus tcp/ip, metasys n2 and lonworks
Hide thumbs Also See for FieldServer ProtoNode FPC-N38:
Table of Contents

Advertisement

3.3

Configuring Device Communications

3.3.1 Input COM settings on all Devices connected to the ProtoNode

All of the connected serial devices MUST have the same Baud Rate, Data Bits, Stop Bits,
and Parity settings as the ProtoNode.
Figure 4
specifies the device serial port settings required to communicate with the ProtoNode.
Protocol
Baud Rate
Parity
Data Bits
Stop Bits

3.3.2 Set Modbus RTU Node-ID for each Device 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 6)
The Metasys N2 and Modbus TCP/IP Node-IDs are automatically set to be the same value
as the Node-ID of the Modbus RTU device.
Port Setting

Figure 4: Modbus COM Settings

Page 9 of 43
Riello ProtoNode Start-up Guide
Device
Modbus RTU
9600
None
8
2

Hide quick links:

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the FieldServer ProtoNode FPC-N38 and is the answer not in the manual?

Questions and answers

This manual is also suitable for:

Fieldserver protonode fpc-n39

Table of Contents

Save PDF