CleaverBrooks ProtoNode Startup Manual
Cloud Enabled
ProtoNode Gateway
Startup Guide
750-426
03/2018
TO: Owners, Operators and/or Maintenance Personnel
This operating manual presents information that will help to properly operate and care for the equipment. Study its contents carefully. The unit will provide good service and continued operation if proper operating and maintenance instructions are followed. No attempt should be made to operate the unit until the principles of operation and all of the
components are thoroughly understood.
It is the responsibility of the owner to provide training and advice in all aspects of safety not only to his or her personnel,
but to any contractors' personnel who will be servicing, repairing, or operating the equipment.
Cleaver-Brooks equipment is designed and engineered to give long life and excellent service on the job. The electrical
and mechanical devices supplied as part of the unit were chosen because of their known ability to perform; however,
proper operating techniques and maintenance procedures must be followed at all times.
It is solely the operator’s responsibility to properly operate and maintain the equipment. No amount of written instructions
can replace intelligent thinking and reasoning and this manual is not intended to relieve the operating personnel of the
responsibility for proper operation. On the other hand, a thorough understanding of this manual is required before attempting to operate, maintain, service, or repair this equipment.
The operation of this equipment by the owner and any operating personnel must comply with all requirements or regulations of the insurance company and/or other authority having jurisdiction. In the event of any conflict or inconsistency
between such requirements and the warnings or instructions contained herein, please contact Cleaver-Brooks before proceeding.
ProtoNode Gateway Cloud Enabled
RER (BACnet, N2, Modbus, Ethernet/IP)
and
LER (LonWorks)
for interfacing Cleaver-Brooks products:
Falcon Hydronic, Falcon Steam, CB780, CB120, HSC, LCS, PCS, HAWK 1000, HAWK 2000, HAWK
4000, HAWK 4500, HAWK 5000, HAWK Master, HAWK ADAC, HAWK ICS, Shark100, Shark200,
UDC2500, HSC Pump Interface, HSC Boiler Interface, CB780, CB783, FARC, HAWK 4000 V2, ADAC
1000
to Building Energy Management Systems:
BACnet MS/TP, BACnet/IP, Modbus TCP/IP, Modbus RTU, Metasys N2, Ethernet/IP and LonWorks
750-426
03/2018
ProtoNode Gateway
Technical Support:
Thank you for purchasing the ProtoNode for Cleaver-Brooks products. For the latest edition of this
Startup Guide, go to: http://www.cleaverbrooks.com/protonode
For ProtoNode Gateway technical support, please contact your Cleaver-Brooks authorized service
representative. C-B representative contact information is available at www.cleaverbrooks.com/Finda-Rep/Index.aspx
Sierra Monitor Corporation does not provide direct support. Should circumstances require, CleaverBrooks will contact Sierra Monitor Corporation on your behalf.
Support Contact Information:
Cleaver-Brooks
221 Law Street
Thomasville, GA 31792
Customer Service:
(229) 227-2614
(800) 250-5883 / (229) 226-3024
Website: www.CleaverBrooks.com
2 750-426
ProtoNode Gateway
Quick Start Reference
Below is a basic sequence of steps required to configure and register a ProtoNode. It is recommended to
become familiar with the manual in its entirety before beginning the registration process.
If using the ProtoNode for cloud-based data monitoring only (without protocol translation), steps 4, 5, 6, 8,
and 13 below may be skipped.
1. First determine the configuration method (Auto-Discovery or Web Configurator) for devices to be connected
to the ProtoNode (Section 1.2).
2. Record the ProtoNode part number in case needed for technical support (Section 2.1).
3. Set the device's COM settings and Node-ID for each of the devices that are to connect to the ProtoNode
RER or LER (Section 2.3).
4. RER: Select the field protocol on the S Bank DIP Switches (Section 2.4).
5. BACnet MS/TP (RER): Set the MAC Address on the A Bank DIP Switches (Section 2.5.1).
6. BACnet MS/TP, Modbus RTU (RER): Set the baud rate of the field protocol on the B Bank DIP Switches
(Section 2.5.2).
7. Connect ProtoNode 6 pin RS-485 connector to the RS-485 network that is connected to each of the C-B
serial devices (Section 3.2).
8. Connect ProtoNode RER's 3 pin RS-485 port to the field protocol cabling, (Section 3.3) or connect the
ProtoNode LER's 2 pin LonWorks port to the field protocol cabling (Section 3.4).
9. Connect power to the ProtoNode 6 pin connector (Section 3.6).
10. Optional, for Falcon controls only - Enable the ProtoNode “Auto-Discovery” mode on S Bank DIP Switches
(Section 2.4.1). When power is applied it will take about 3 minutes for all the devices to be discovered
and the configuration file to be built. Once Auto-Discovery is complete turn OFF the S3 DIP switch to save
the configuration settings (Section 3.5).
11. Web Configurator Devices: Use a web browser to access the ProtoNode Web Configurator page; select the
profiles of the devices attached to the ProtoNode and input the Node-ID from each device. Once devices
are selected, the ProtoNode automatically builds and loads the appropriate configuration (Section 4).
12. BACnet/IP, Modbus TCP/IP, or cloud (RER): Use a web browser to access the ProtoNode Web Configurator
page to change the IP Address. No changes to the configuration are necessary (Section 4.4).
13. LonWorks (LER): The ProtoNode must be commissioned on the LonWorks Network. This needs to be done
by the LonWorks administrator using a LonWorks commissioning tool (Section 7).
14. Complete the registration process for the FieldPoP device cloud (Section 8).
BEFORE BEGINNING
In order to complete the ProtoNode registration and setup process, the following are required:
• A laptop computer for Internet access
• Ethernet cable
• IP address(es) to identify the ProtoNode and connected devices on plant network (NOTE - all devices
connected via Ethernet to the ProtoNode will need an IP address on the same subnet)
• Email address for site/end user contact that will be the Enterprise Customer Admin for the site
The startup technician must be registered on the FieldPoP site as an OEM Manager.
750-426 3
ProtoNode Gateway
Certifications
BACNET TESTING LABORATORY
The BTL Mark on ProtoNode RER is a symbol that indicates that a product
has passed a series of rigorous tests conducted by an independent laboratory
which verifies that the product correctly implements the BACnet features
claimed in the listing. The mark is a symbol of a high-quality BACnet product.
Go to http://www.BACnetInternational.net/btl/ for more information about the
BACnet Testing Laboratory. For the Protocol Implementation Conformance
(PIC) statement go to:
http://www.sierramonitor.com/assets/blt933677195ae326eb/PDS_BACnet_PIC_Statement.pdf
LONMARK
LonMark International is the recognized authority for certification, education,
and promotion of interoperability standards for the benefit of manufacturers,
integrators and end users. LonMark International has developed extensive
product certification standards and tests to provide the integrator and user
with confidence that products from multiple manufacturers utilizing LonMark
devices work together. Sierra Monitor Corporation has more LonMark Certified
gateways than any other gateway manufacturer, including the ProtoCessor,
ProtoCarrier and ProtoNode for OEM applications and the full featured, configurable gateways.
4 750-426
ProtoNode Gateway
TABLE OF CONTENTS
1 Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
1.1 ProtoNode Gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
1.2 Methods of Configuration - Cleaver-Brooks' Devices . . . . . . . . . . . . . . . . . . . . . . . . . . 9
2 Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
2.1 Record Identification Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
2.2 Point Count Capacity and Registers per Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
2.3 Configuring Device Communications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
2.3.1 Input COM Settings on all Serial Devices Connected to the ProtoNode . . . . . . . 11
2.3.2 Set Modbus Node-ID for each Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
2.3.3 Set Ethernet IP address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
2.4 Selecting the Desired Field Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
2.4.1 Enabling Auto-Discovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
2.5 BMS Network Settings: MAC Address, Device Instance and Baud Rate. . . . . . . . . . . . 13
2.5.1 BACnet MS/TP (RER): Setting the MAC Address BACnet Network . . . . . . . . . . 13
2.5.2 BACnet (RER): Calculating the Default Device Instance . . . . . . . . . . . . . . . . . 13
2.5.3 BACnet MS/TP (RER): Setting the Baud Rate for BMS Network . . . . . . . . . . . . 14
3 Interfacing ProtoNode to Devices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
3.1 ProtoNode RER and LER Showing Connection Ports. . . . . . . . . . . . . . . . . . . . . . . . . 15
3.2 Device Connections to ProtoNode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
3.2.1 Biasing the Modbus RS-485 Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
3.2.2 End of Line Termination Switch for the Modbus RS-485 Device Network . . . . . . 17
3.3 BACnet MS/TP or Metasys N2 (RER): Wiring Field Port to RS-485 Network . . . . . . . . 18
3.4 LonWorks (LER): Wiring Field Port to LonWorks Terminal . . . . . . . . . . . . . . . . . . . . . 18
3.5 Auto-Discovery. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
3.6 Power up ProtoNode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
4 Web Configurator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
4.1 Connect the PC to ProtoNode via the Ethernet
4.2 Connecting to ProtoNode’s Web Configurator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
4.3 Selecting Profiles for Devices Connected to ProtoNode . . . . . . . . . . . . . . . . . . . . . . . . .24
4.4 BACnet/IP and Modbus TCP/IP: Setting IP Address for Field Network . . . . . . . . . . . . 26
5 BACnet MS/TP and BACnet/IP: Setting Node_Offset to Assign Specific Device
6 How to Start the Installation over: Clearing Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
7 Commissioning ProtoNode on a LonWorks Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
7.1 Downloading an XIF File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
8 SMC Cloud User Setup, Registration and Login . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
8.1 User Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
8.2 Registration Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
8.3 Login . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Port
. . . . . . . . . . . . . . . . . . . . . . . . . . .21
Instances
.28
750-426 5
ProtoNode Gateway
Appendix A. Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .38
A.1. Lost or Incorrect IP Address. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .38
A.2. Viewing Diagnostic information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .39
A.3. Check Wiring and Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .40
A.4. LED Diagnostics for Communications Between ProtoNode and
A.5. Take Diagnostic Capture with the FieldServer Toolbox. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .42
A.6. Mounting
A.7. Update Firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .44
A.8. BACnet: Setting Network_Number for more than one ProtoNode on
A.9. Securing ProtoNode with Passwords. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .45
Appendix B. Data Point Mappings for Cleaver-brooks Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . .46
B.1. Falcon Hydronic. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .46
B.2. Falcon Steam . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .48
B.3. CB780 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .50
B.4. CB120 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .52
B.5. HSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .54
B.6. LCS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .61
B.7. PCS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .62
B.8. Hawk 1000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .63
B.9. Hawk 2000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .68
B.10. Hawk 4000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .70
B.11. Hawk 5000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .75
B.12. Hawk Master. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .81
B.13. ADAC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .85
B.14. Hawk ICS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .91
B.15. Shark 100 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .94
B.16. Shark 200 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .95
B.17. UDC 2500 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .96
B.18. PIM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .97
B.19. BIM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .98
B.20. CB780 / 783 FARC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .99
B.21. Hawk 4000 V.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .103
B.22. ADAC 1000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .110
B.23. Hawk 4500 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .116
ProtoNode
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .43
Devices
Subnet
. . . . . . . . . . . . . . . . . . . .41
. . . . . . . . . . . . . . . . .44
Appendix C. “A” Bank DIP Switch Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .125
Appendix D. Interfacing Protonode Gateway to Boiler Networks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .128
D.1. Boiler Network Wiring Connections to ProtoNode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .128
D.2. ClearFire Boiler Modbus Network. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .128
D.3. Falcon System Display Modbus Gateway Connection (COM2) Wiring to the ProtoNode . . . . . . .129
D.4. CB780E Modbus connections to ProtoNode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .130
D.5. CB120E Modbus connections to ProtoNode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .130
D.6. HSC Modbus connections to ProtoNode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .130
Appendix E. Specifications \ UL Compliance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .131
E.1. Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .131
E.1.1. Compliance with UL Regulations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .131
Appendix F. Limited 2 Year Warranty . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .132
6 750-426
ProtoNode Gateway
LIST OF FIGURES
Method of configuration for the devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
ProtoNode Part Numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Supported Point Count Capacity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Modbus Registers per Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
COM Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
S Bank DIP Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
MAC Address DIP Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Baud Rate DIP Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
ProtoNode Connection Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
RS-485 and Power Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
RS-485 Bias Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
RS-485 EOL Termination Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Connection from ProtoNode to RS-485 Field Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18
RS-485 BMS Network EOL Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
LonWorks Terminal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18
S3 DIP Switch setting for Auto Discovering Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Required current draw for the ProtoNode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Power Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Ethernet Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Web App Splash Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Login Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Web App Landing Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Configuration Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Web Configurator Showing no Active Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Web Configurator showing available profiles for selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Web Configurator Showing Active Profile Additions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Web Configurator Screen with Active Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Changing IP Address via FS-GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Web Configurator Node Offset Field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Active Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
LonWorks Service Pin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Generating an XIF File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Welcome to FieldPoP Email . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Setting User Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Web App Landing Page - FieldPoP Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Registration Information Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
SMC Cloud Connection Problems Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
SMC Cloud Registration Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Device Registered for SMC Cloud . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
SMC Cloud Login Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
SMC Cloud Landing Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Ethernet port location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .38
Error messages screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .39
Ethernet Port Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
DIN Rail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Web Configurator - Network Number Field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
FS-GUI Passwords Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Password Recovery Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
750-426 7
ProtoNode Gateway
1. INTRODUCTION
1.1 ProtoNode Gateway
ProtoNode is an external, high performance Building Automation multi-protocol gateway that is configured to automatically communicate between any of Cleaver-Brooks' products (hereafter called
“device”) to various building automation protocols. These protocols include BACnet® MS/TP, BACnet/IP, Metasys® N2 by JCI, Modbus TCP/IP, Modbus RTU, Ethernet/IP and LonWorks®.
It is not necessary to download any configuration files to support the required applications. The ProtoNode is pre-loaded with tested Profiles/Configurations for the supported devices.
We use 2 methods to dynamically configure the ProtoNode to support the devices with the selected
protocol.
Auto-Discovery: Supported RS-485 devices can be automatically detected and identified for addition
to the ProtoNode's configuration. (Section 1.2)
Web Configurator: Ethernet devices connected to the ProtoNode can not be Auto-Discovered. To add
Ethernet devices to the gateway, profiles must be selected in the ProtoNode's Web Configurator. The
Web Configurator shows all the stored profiles/devices on the ProtoNode. It will also show all the RS485 devices that were previously discovered. After selecting the device, the Modbus Node-ID and,
only for Ethernet Devices, the IP Address must also be entered. Once all the devices are selected and
saved, the ProtoNode automatically builds and downloads the configuration for the desired protocol.
ProtoNode Applications
1
BACnet is a registered trademark of ASHRAE
2
Metasys is a registered trademark of Johnson Controls Inc.
3
LonWorks is a registered trademark of Echelon Corporation
8 750-426
ProtoNode Gateway
1.2 Methods of Configuration - Cleaver-Brooks' Devices
The ProtoNode offers two methods of configuration:
• Auto-Discovery for RS-485 devices listed below in Figure 1.
• Web Configurator for Ethernet devices and RS-485 devices that cannot be identified by Auto-Discovery
A list of C-B products for use with the ProtoNode, together with their respective means of configuration, is shown in the table below.
Devices Type of Communication Type of Configuration
Falcon Hydronic RS-485 Auto-Discovery/Web Configurator
Falcon Steam RS-485 Auto-Discovery/Web Configurator
CB780 RS-485 Web Configurator
CB120 RS-485 Web Configurator
HSC Admin RS-485 Auto-Discovery/Web Configurator
HSC BIM RS-485 Web Configurator
HSC PIM RS-485 Web Configurator
LCS RS-485 Web Configurator
PCS RS-485 Web Configurator
HAWK 1000 Ethernet Web Configurator
HAWK 2000 Ethernet Web Configurator
HAWK 4000 Ethernet Web Configurator
HAWK 4500 Ethernet Web Configurator
HAWK 5000 Ethernet Web Configurator
HAWK Master Ethernet Web Configurator
HAWK ADAC Ethernet Web Configurator
HAWK ICS Ethernet Web Configurator
Shark 100 Ethernet Web Configurator
Shark 200 Ethernet Web Configurator
UDC2500 Ethernet Web Configurator
HSC Pump Interface (PIM) Ethernet Web Configurator
HSC Boiler Interface (BIM) Ethernet Web Configurator
CB780 CB783 FARC Ethernet Web Configurator
HAWK 4000 V2 Ethernet Web Configurator
ADAC 1000 Ethernet Web Configurator
FIGURE 1 - Method of configuration for the devices
750-426 9
ProtoNode Gateway
2. PROTONODE SETUP
2.1 Record Identification Data
Each ProtoNode has a unique part number located on the underside of the unit. This number should
be recorded, as it may be required for technical support. The numbers are as follows:
Model Part Number Description
ProtoNode RER 833-06022-000 BACnet, N2, Modbus, Ethernet/IP
ProtoNode LER 833-06029-000 LonWorks
FIGURE 2 - ProtoNode Part Numbers
• RER units have the following 3 ports: RS-485 + Ethernet + RS-485
• LER units have the following 3 ports: LonWorks + Ethernet + RS-485
2.2 Point Count Capacity and Registers per Device
The total number of Modbus registers presented by all of the devices attached to the ProtoNode
cannot exceed:
Model Total Registers
ProtoNode RER 10,000
ProtoNode LER 5,000
FIGURE 3 - Supported Point Count Capacity
DEVICE REGISTERS PER DEVICE
Falcon_Hydronic 92
Falcon_Steam 62
CB780 93
CB120 94
HSC 318
LCS 59
PCS 57
HAWK_1000 278
HAWK_2000 75
HAWK_4000 293
HAWK_5000 278
HAWK_Master 200
HAWK_ADAC 275
HAWK_ICS 146
Shark100 41
Shark200 50
UDC2500 42
HSC_Pump_Interface 47
HSC_Boiler_Interface 40
CB780_CB783_FARC 178
Hawk_4000_V2 378
ADAC_1000 338
FIGURE 4 - Modbus Registers per Device
10 750-426
ProtoNode Gateway
2.3 Configuring Device Communications
2.3.1 Input COM Setting s on all Seria l De vice s C onnect ed to the Pro to Node
All of the connected serial devices MUST have the same Baud Rate, Data Bits, Stop Bits, and Parity settings as the ProtoNode.
Figure 5 specifies the device serial port settings required to communicate with the ProtoNode.
Port Setting Falcon Steam & Hydronic
Protocol Modbus RTU Modbus RTU
Baud Rate 38400 9600
Parity None None
Data Bits 8 8
Stop Bits 1 1
FIGURE 5 - COM Settings
2.3.2 Set Modbus Node-ID for each device attached to the ProtoNode
Other Serial Devices
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. The Modbus Node-ID that is assigned for each device
needs to be documented. The Modbus Node-IDs 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 Field Protocol Node-IDs are automatically set to the same
value as the Node-ID of the device.
2.3.3 Set IP Address for each Ethernet Device Connected to the ProtoNode
Ensure devices are set to Modbus TCP/IP to communicate with the ProtoNode.
• The device needs to be on the same IP subnet as the ProtoNode and the configuration PC.
• Record the following device information to start the setup:
IP Address
IP port
Node-ID
NOTE: This information is required for Section 4.
2.4 Selecting the Desired Field Protocol
NOTE: If using the ProtoNode only for cloud-based data monitoring, Sections 2.4 and 2.5 may be
skipped.
• ProtoNode RER units use the “S” bank of DIP switches (S0 - S2) to select the Field Protocol.
See Figure 6 for the DIP switch settings.
The OFF position is when the DIP switches are set closest to the outside of the box.
• ProtoNode LER units do not use the “S” bank DIP switches to select a Field Protocol. On ProtoNode LER
units, these DIP switches are disabled; the Field Protocol is always LonWorks.
750-426 11
ProtoNode Gateway
ProtoNode RER S Bank DIP Switches
Profile S0 S1 S2
BACnet IP Off Off Off
BACnet MSTP On Off Off
Metasys N2 Off On Off
Modbus TCP & Modbus RTU On On Off
Ethernet/IP Off Off On
BACnet MS/TP (single node) On Off On
S Bank DIP Switches
S3 DIP Switch Auto-Discovery Mode S3
Auto-Discovery ON - Build New Configuration On
Auto-Discover OFF - Save Current Configuration Off
NOTE: When setting DIP switches, ensure that power to the board is OFF.
FIGURE 6 - S Bank DIP Switches
2.4.1 Enabling Auto-Discovery
The S3 DIP switch is used to both enable Auto-Discovery of known devices attached to the ProtoNode, and to save the recently discovered configuration.
See the table in Figure 6 for the DIP switch setting to enable Auto-Discovery.
If the ProtoNode is being installed for the first time, set S3 to the ON position to enable Auto-Discovery.
The ON position is when the DIP switches are set closest to the inside of the box.
12 750-426
ProtoNode Gateway
2.5 BMS Network Settings: MAC Address, Device Instance and Baud Rate
2.5.1 BACnet MS/TP (RER): Setting the MAC Address for BMS Network
Only 1 MAC address is set for the ProtoNode regardless of how many devices are connected.
Set the BACnet MS/TP MAC addresses of the ProtoNode to a value between 1 to 127 (MAC Master
Addresses); this is so that the BMS Front End can find the ProtoNode via BACnet auto discovery.
Note: Never set a BACnet MS/TP MAC Address from 128 to 255. Addresses from 128 to 255 are
Slave Addresses and can not be discovered by BMS Front Ends that support auto discovery of BACnet MS/TP devices.
Set “A” bank DIP switches A0 - A7 to assign a MAC Address to the ProtoNode for BACnet MS/TP.
Please refer to Appendix C for the complete range of MAC Addresses and DIP switch settings.
NOTE: When using Metasys N2 and Modbus TCP/IP, the A Bank of DIP switches are disabled
and not used. They should be set to OFF.
FIGURE 7 - MAC Address DIP Switches
NOTE: When setting DIP Switches, please ensure that power to the board is OFF.
2.5.2 BACnet (RER): Calculating the Default Device Instance
The Device Instance value is automatically generated using the following formula:
BACnet Device Instance = (Device Node ID) + (Default Node Offset)
NOTE: The default Node Offset is 50,000.
For example, if Device A has a Node ID of 1 and Device B has a Node ID of 2, then:
BACnet Device Instance A = (1) + (50000) = 50001
BACnet Device Instance B = (2) + (50000) = 50002
NOTE: The Node ID is set in Section 2.3.2.
To reach a specific BACnet Device Instance result, refer to Section 5.
750-426 13
ProtoNode Gateway
2.5.3 BACnet MS/TP: Setting the Baud Rate for BMS Network
DIP switches B0 – B3 can be used to set the field baud rate of the ProtoNode to match the baud
rate required by the BMS for BACnet MS/TP.
The ProtoNode baud rate for Metasys N2 is set for 9600. DIP switches B0 – B3 are disabled for
Metasys N2 on ProtoNode RER.
DIP switches B0 – B3 are disabled on ProtoNode LER (LonWorks).
Table 1: Baud Rate DIP Switch Selection
Baud B0 B1 B2 B3
9600 On On On Off
19200 Off Off Off On
38400* On On Off On
57600 Off Off On On
76800 On Off On On
Baud Rate DIP Switches
*Factory default
FIGURE 8 - Baud Rate DIP Switches
NOTE: When setting DIP switches, ensure that power to the board is OFF.
14 750-426
3. INTERFACING PROTONODE TO DEVICES
3.1 ProtoNode Connection Ports
ProtoNode Gateway
RER
FIGURE 9 - ProtoNode
LER
Connection Ports
750-426 15
ProtoNode Gateway
3.2 Device Connections to ProtoNode
ProtoNode 6 Pin Phoenix connector for RS-485 Devices
The 6 pin Phoenix connector is the same for ProtoNode RER (BACnet) and LER (LonWorks).
Pins 1 through 3 are for Modbus RS-485 devices. The RS-485 GND (Pin 3) is not typically connected.
Pins 4 through 6 are for power. Do not connect power (wait until Section 3.6).
Device Pins ProtoNode Pin # Pin assignment
Pin RS-485 + Pin 1 RS-485 +
Pin RS-485 - Pin 2 RS-485 -
Pin GND Pin 3 RS-485 GND
Power In (+) Pin 4 V +
Power In (-) Pin 5 V -
Frame Ground Pin 6 FRAME GND
FIGURE 10 - RS-485 and Power Connections
3.2.1 Biasing the Modbus RS-485 Network
An RS-485 network with more than one device needs to have biasing to ensure proper communication. The biasing only needs to be done on one device.
The ProtoNode has 510 Ohm resistors that can be used to set the biasing. The ProtoNode's default
positions from the factory for the biasing jumpers are OFF.
The OFF position is when the 2 RED biasing jumpers straddle the 4 pins closest to the outside of the
board of the ProtoNode. See Figure 11.
Only turn biasing ON:
• IF the BMS cannot see more than one device connected to the ProtoNode
• AND all the settings (Modbus COM settings, wiring, and DIP switches) have been checked.
To turn biasing ON, move the 2 RED biasing jumpers to straddle the 4 pins closest to the inside of
the board of the ProtoNode.
16 750-426
ProtoNode Gateway
(off)
FIGURE 11 - RS-485 Bias Switch
3.2.2 End of Line Termination Switch for the Modbus RS-485 Device Network
On long RS-485 cabling runs, the RS-485 trunk must be properly terminated at each end.
The ProtoNode has an End Of Line (EOL) blue jumper. The default setting for this Blue EOL switch is
OFF with the jumper straddling the pins closest to the inside of the board of the ProtoNode.
On short cabling runs the EOL switch does not to need to be turned ON.
If the ProtoNode is placed at one of the ends of the trunk, set the blue EOL jumper to the ON position straddling the pins closest to the outside of the board of the ProtoNode.
Always leave the single Red Jumper in the A position (default factory setting).
RER
FIGURE 12 - RS-485 EOL Termination Switch
LER
750-426 17
ProtoNode Gateway
3.3 BACnet MS/TP or Metasys N2 (RER): Wiring Field Port to RS-485 Network
Connect the BACnet MS/TP or Metasys N2 RS-485 network wires to the 3-pin RS-485 connector on ProtoNode RER as shown below.
• Use standard grounding principles for RS-485 GND.
See Section 4.4 for information on connecting to BACnet/IP network.
If the ProtoNode is the last device on the BACnet MS/TP or Metasys N2 trunk, then the End-Of-Line
Termination Switch needs to be enabled (Figure 14).
• The default setting from the factory is OFF (switch position = right side).
• To enable the EOL Termination, turn the EOL switch ON (switch position = left side).
BMS RS-485
Wiring
RS-485 + Pin 1 RS-485 +
RS-485 - Pin 2 RS-485 -
- Pin 3 RS-485 GND
ProtoNode
Pin #
Pin
Assignment
FIGURE 13 - Connection from ProtoNode to RS-485 Field Network
End-of-Line Switch
FIGURE 14 - RS-485 BMS Network EOL Switch
3.4 LonWorks (LER): Wiring LonWorks Devices to the LonWorks Terminal
Wire the LonWorks device network to the ProtoNode LonWorks Terminal.
• Use approved cable per the FT-10 installation guidelines
• LonWorks has no polarity.
FIGURE 15 - LonWorks Terminal
18 750-426
ProtoNode Gateway
3.5 Auto-Discovery: After Completion - Turn Off to Save Configuration
NOTE: If Modbus TCP/IP was selected for the field/BMS protocol, skip this section. Auto-Discovery
is NOT used for Modbus TCP/IP.
The S3 DIP Switch for Enabling Auto-Discovery should have been set in Section 2.4.1 before applying power to the ProtoNode. Do not Enable Auto-Discovery when the unit is powered.
When power is applied to a ProtoNode that is set to enable Auto-Discovery, it will take about 3 minutes to complete the discovery of all of the RS-485 devices attached to the ProtoNode.
• The “TX” LED will flash during Auto-Discovery
• Once Auto-Discovery is complete, the “TX” and “RX” LEDs should flash rapidly, indicating good communication between discovered devices
• Once the ProtoNode has discovered all of the RS-485 devices, set the S3 DIP switch to the OFF position
to save the current configuration.
ProtoNode RER and LER
S3 DIP Switch Auto-Discovery Mode S3
Auto-Discovery ON - Build New Configuration On
Auto-Discover OFF - Save Current Configuration Off
FIGURE 16 - S3 DIP Switch setting for Auto Discovering Devices
3.6 Power-Up ProtoNode
Check power requirements in the table below:
Power Requirement for ProtoNode at 9V through 30 VDC or 12-24 VAC
Current Draw Type
ProtoNode Family 12VDC/VAC 24VDC/VAC 30VDC
RER (Typical) 170mA 100mA 80mA
RER (Maximum) 240mA 140mA 100mA
LER (Typical) 210mA 130mA 90mA
LER (Maximum) 250mA 170mA 110mA
Note: These values are 'nominal' and a safety margin should be added to the power supply of the host system. A safety margin of 25% is recommended.
FIGURE 17 - Required current draw for the ProtoNode
Apply power to ProtoNode as shown below in Figure 18. Ensure that the power supply used complies
with the specifications provided in Appendix E.1.
• ProtoNode accepts either 9-30VDC or 12-24 VAC on pins 4 and 5.
• Frame GND should be connected.
750-426 19
ProtoNode Gateway
Power to
ProtoNode
Power In (+) Pin 4 V +
Power In (-) Pin 5 V -
Frame Ground Pin 6 FRAME GND
ProtoNode
Pin #
Pin
Assignment
FIGURE 18 - Power Connections
20 750-426
ProtoNode Gateway
4. WEB CONFIGURATOR
Use Protonode's Web Configurator to set up the gateway.
4.1 Connect the PC to ProtoNode via the Ethernet Port
Ethernet
port
FIGURE 19 - Ethernet Port
• Connect a standard CAT5 Ethernet cable (Straight through or Cross-Over) between the PC and ProtoNode.
• The Default IP Address of ProtoNode is 192.168.1.24, Subnet Mask is 255.255.255.0. If the PC and
ProtoNode are on different IP Networks, assign a static IP Address to the PC on the 192.168.1.xxx network.
• For Windows 10:
Right click on > > >
>
Right-click on Local Area Connection > Properties
Highlight >
Use the following IP Address:
Click twice.
750-426 21
ProtoNode Gateway
4.2 Connecting to ProtoNode's Web Configurator
After setting a local PC on the same subnet as the ProtoNode (Section 4.1), open a web browser on
the PC and enter the IP Address of the ProtoNode; the default address is 192.168.1.24.
NOTE: If the IP Address of the ProtoNode has been changed by previous configuration, the
assigned IP Address can be discovered using the FS Toolbox utility. See Appendix A.1 for instructions.
• Once at the Web App splash page, click the <Login> button.
FIGURE 20 - Web App Splash Page
• Enter the previously set up or default user name and password.
NOTE: The default user name is “admin”. The default password is “admin”.
FIGURE 21 - Login Window
22 750-426
• From the Web App landing page (Figure 22), click the Configure tab.
FIGURE 22 - Web App Landing Page
• Then click the <Profiles Configuration> button to go to the Web Configurator page.
ProtoNode Gateway
FIGURE 23 - Configuration Page
NOTE: The FieldPoP™ tab (see Figure 23) allows users to connect to the SMC Cloud,
Sierra Monitor's device cloud solution for IIoT. The SMC Cloud enables secure remote connection to
field devices through a FieldServer and its local applications for configuration, management, maintenance. For more information about the SMC Cloud, refer to the SMC Cloud Start-up Guide.
NOTE: For Web App instructions to the System View, Historian and Event Logger functions, see the
SMC Cloud Start-up Guide.
750-426 23
ProtoNode Gateway
4.3 Selecting Profiles for Devices Connected to ProtoNode
In the Web Configurator, the Active Profiles section is shown on the lower left side of the screen.
The Active Profiles section lists the currently active device profiles, including previous Web Configurator additions and any devices identified by Auto-Discovery configuration methods. This list will be
empty for new installations, or after clearing all configurations.
FIGURE 24 - Web Configurator Showing no Active Profiles
To add an active profile to support a device, click the <Add> button under Active Profiles. This will
present a drop-down box underneath the Current Profile column that lists all the available profiles.
For every device that is added, assign a unique Modbus Node-ID. This specification must match the
device's network settings.
NOTE: If multiple devices are connected to the ProtoNode, set the BACnet Virtual Server Nodes
field to “Yes”; otherwise leave the field on the default “No” setting.
Once the Profile for the device has been selected from the drop-down list, enter the value of the
device's Node-ID which was assigned in Section 2.3.2
24 750-426
ProtoNode Gateway
FIGURE 25 - Web Configurator
• Then press the <Submit> button to add the profile to the list of devices to be configured.
• Repeat this process until all the devices have been added.
• Completed additions will be listed under Active Profiles as shown in Figure 26.
• After adding profiles press <System Restart>
FIGURE 26 - Web Configurator Showing Active Profile Additions
showing available profiles for selection
NOTE: If the device is connected via EtherNet/IP, the “IP_Addr” under the Parameters heading
must be gathered from settings on the device. This corresponds to the device IP Address (Section
2.3.3).
750-426 25
ProtoNode Gateway
4.4 BACnet/IP and Modbus TCP/IP: Setting IP Address for Field Network
After setting a local PC to the same subnet as the ProtoNode (Section 5.1), open a web browser on
the PC and enter the IP Address of the ProtoNode; the default address is 192.168.1.24.
The Web Configurator is displayed as the landing page (Figure 27).
To access the FieldServer Graphic User Interface (FS-GUI), click on the “Diagnostics & Debugging”
button in the bottom right corner of the page.
FIGURE 27 - Web Configurator Screen with Active Profiles
26 750-426
ProtoNode Gateway
From the FS-GUI landing page, click on “Setup” to expand the navigation tree and then select “Network
Settings” to access the IP Settings menu.
FIGURE 28 - Changing IP Address via FS-GUI
Modify the IP Address (N1 IP Address field) of the ProtoNode Ethernet port.
If necessary, change the Netmask (N1 Netmask field).
If necessary, change the IP Gateway (Default Gateway field).
DHCP Client State should remain disabled; Domain Name Server 1 and 2 should be left at their current values.
NOTE: If the ProtoNode is connected to a managed switch/router, the IP Gateway of the ProtoNode
should be set to the IP Address of that managed switch/router.
Click the “System Restart” button at the bottom of the page to apply changes and restart the ProtoNode.
Unplug Ethernet cable from PC and connect it to the network switch or router.
Record the IP Address assigned to the ProtoNode for future reference.
NOTE: The FieldPoP™ button (see Figure 28) allows users to connect to the SMC
Cloud, Sierra Monitor's device cloud solution for IIoT. The SMC Cloud enables secure remote connection to field devices through a FieldServer and its local applications for configuration, management, maintenance. For more information about the SMC Cloud, refer to the SMC Cloud Start-up
Guide.
750-426 27
ProtoNode Gateway
5. BACNET MS/TP AND BACNET/IP: SETTING NODE OFFSET TO ASSIGN SPECIFIC
DEVICE INSTANCES
After setting a local PC to the same subnet as the ProtoNode (Section 4.1), open a web browser on
the PC and enter the IP Address of the ProtoNode; the default address is 192.168.1.24.
• If the IP Address of the ProtoNode has been changed by previous configuration, the assigned IP Address
will need to be obtained from the network administrator.
• The Web Configurator will be displayed as the landing page.
Node_Offset field will be presented displaying the current value (default = 50,000). The values
allowed for a BACnet Device Instance can range from 1 to 4,194,303.
• To assign a specific Device Instance (or range); change the Node_Offset value as needed using the calculation below:
Device Instance (desired) = Node_Offset + Modbus Node_ID
For example, if the desired Device Instance for the device 1 is 50,001 and the following is true:
Device 1 has a Modbus Node-ID of 1
Device 2 has a Modbus Node-ID of 22
Device 3 has a Modbus Node-ID of 33
Then plug the device 1's information into the formula to find the desired Node_Offset:
50,001 = Node_Offset + 1
50,000 = Node_Offset
Once the Node_Offset value is input, it will be applied to all devices as shown below:
Device 1 Instance will then be = 1,000 + Node_ID = 1,000 + 1 = 1,001
Device 2 Instance will then be = 1,000 + Node_ID = 1,000 + 22 = 1,022
Device 3 Instance will then be = 1,000 + Node_ID = 1,000 + 33 = 1,033
Click “Submit” once the desired value is entered.
FIGURE 29 - Web Configurator Node Offset Field
FIGURE 30 - Active Profiles
28 750-426
Loading...