ProtoNode FPC-N34 and ProtoNode FPC-N35 Startup Guide For Interfacing Harsco Industrial Patterson-Kelley Products: ENVI Control Systems, Love Controller and Nuro To Building Automation Systems: BACnet MS/TP, BACnet/IP, Modbus TCP/IP, Metasys N2 and LonWorks APPLICABILITY & EFFECTIVITY Explains ProtoNode FPC-N34 and FPC-N35 hardware and how to install it. The instructions are effective for the above as of April 2015 Document Revision: 12 Hybrid-RS485 Template Revision: 29 Harsco Patterson Kelley’s ProtoNode Startup Guide Technical Support: Thank you for purchasing the ProtoNode for Harsco Industrial Patterson-Kelley. Please call Harsco Industrial Patterson-Kelley for Technical support of the ProtoNode product. SMC does not provide direct support. If Harsco Industrial Patterson-Kelley needs to escalate the concern, they will contact Sierra Monitor Corporation for assistance. Support Contact Information: HIP-K Water Heaters, General Inquiries 155 Burson Street East Stroudsburg, Pennsylvania 18301 Harsco Industrial Patterson-Kelley Service: 570-476-7261 Email: [email protected] Website: http://harscopk.com/ Page 2 of 54 Harsco Patterson Kelley’s ProtoNode Startup Guide A Quick Start Guide 1. Methods of Configuration: (Section 1.2) Auto-Discovery: See Figure 1 for table of RS-485 devices supporting Auto-Discovery. Web Configurator: For RS-485 devices that cannot be Auto-Discovered, use browser to connect to ProtoNode’s Web Configurator utility. 2. Record the information about the unit. (Section 2.1) 3. Set the device’s Modbus RTU serial settings (i.e. baud rate, parity, stop bits) and Modbus NodeID’s for each of the devices that will be connected to the ProtoNode. (Section 2.2) 4. ProtoNode FPC-N34 units: Select the Field Protocol (BACnet MS/TP, BACnet/IP, Modbus TCP/IP or Metasys N2) on the S Bank Dip Switches. (Section 2.3.1) 5. Auto-Discovery Configurations: Enable the ProtoNode “Auto-Discovery” mode on DIP Switch S3. (Section 2.3.2) 6. BACnet MS/TP (FPC-N34): Set the MAC Address on DIP Switch Bank A. (Section 2.4.1) 7. BACnet MS/TP or BACnet IP (FPC-N34): Set the BACnet Device Instance. (Section 2.4.2) 8. Metasys N2 or Modbus TCP/IP (FPC-N34): Set the Node-ID. (Section 2.4.3) 9. BACnet MS/TP (FPC-N34): Set the BAUD rate of the BACnet MS/TP Field Protocol on DIP Switch Bank B. (Section 2.4.4) 10. Connect ProtoNode FPC-N34’s 3 pin RS-485 port to the Field Protocol cabling, or connect ProtoNode FPC-N35’s 2 pin LonWorks port to the Field Protocol cabling. (Section 3.1) 11. Connect ProtoNode’s 6 pin RS-485 connector to the Modbus RS-485 network that is connected to each of the devices. (Section 3.2) 12. Connect Power to ProtoNode’s 6 pin connector. (Section 3.3) 13. When power is applied it will take about 10 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 4) 14. Web Configurator Configurations: Use a browser to access the ProtoNode’s Web Configurator, then select the devices that will be attached to ProtoNode and set the current Modbus Node-ID for each these products. Once the devices are selected, the ProtoNode Automatically builds and loads the Configuration for the devices. (Section 5) 15. BACnet/IP or Modbus TCP/IP (FPC-N34): Use a browser to access the ProtoNode’s Web Configurator to change the IP address. (Section 6) 16. Reset Configurations: If you need to start over from the beginning of the installation process, you can clear all Auto-Discovered and/or Web Configurator configurations. (Section 7) 17. LonWorks (FPC-N35): The ProtoNode must be commissioned on the LonWorks Network. This needs to be done by the LonWorks administrator using a LonWorks Commissioning tool. (Section 8) Page 3 of 54 Harsco Patterson Kelley’s ProtoNode Startup Guide Certifications BTL MARK – 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. Click here for BACnet PIC Statement. LONMARK CERTIFICATION 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. FieldServer Technologies 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. Page 4 of 54 Harsco Patterson Kelley’s ProtoNode Startup Guide TABLE OF CONTENTS 1 Introduction .......................................................................................................................................... 8 1.1 ProtoNode Gateway ....................................................................................................................... 8 1.2 Methods of Configuration – Harsco Industrial Patterson-Kelley’s Devices .................................... 9 1.3 Harsco Industrial Patterson-Kelley’s Devices and Point Count Available ...................................... 9 2 BACnet/LonWorks Setup for ProtoCessor ProtoNode FPC-N34/FPC-N35 .................................. 10 2.1 Record Identification Data ............................................................................................................ 10 2.2 Configuring Device Communications ........................................................................................... 11 2.2.1 Set Modbus COM setting on all of the devices connected to the ProtoNode ......................... 11 2.2.2 Set Modbus RTU Node-ID for each of the devices attached to the ProtoNode ..................... 11 2.3 Selecting the Desired Field Protocol and Enabling Auto-Discovery............................................. 12 2.3.1 Selecting Desired Field Protocol ............................................................................................. 12 2.3.2 Enabling Auto-Discovery ......................................................................................................... 13 2.4 Setting the MAC Address, Device Instance and Baud Rate ........................................................ 14 2.4.1 BACnet MS/TP (FPC-N34): Setting the MAC Address BACnet Network ............................... 14 2.4.2 BACnet MS/TP and BACnet/IP (FPC-N34): Setting the Device Instance .............................. 15 2.4.3 Metasys N2 or Modbus TCP/IP (FPC-N34): Setting the Node-ID .......................................... 15 2.4.4 BACnet MS/TP (FPC-N34): Setting the Baud Rate ................................................................ 16 3 Interfacing ProtoNode to Devices .................................................................................................... 17 3.1 ProtoNode FPC-N34 and FPC-N35 Showing Connection Ports .................................................. 17 3.2 Device Connections to ProtoNode ............................................................................................... 18 3.2.1 Connecting NURO Modbus RTU Boilers to the ProtoNode’s RS-485 .................................... 18 3.2.2 Connecting LOVE Modbus RTU Boilers to the ProtoNode’s RS-485 ..................................... 18 3.2.3 Connecting ENVI Modbus RTU Boilers to the ProtoNode’s RS-485 ...................................... 18 3.2.4 Biasing the Modbus RS-485 Network ..................................................................................... 19 3.2.5 End of Line Termination Switch for the Modbus RS-485 port on the ProtoNode ................... 20 3.3 BACnet MS/TP or Metasys N2 (FPC-N34): Wiring Field Port to RS-485 Network ...................... 21 3.4 LonWorks (FPC-N35): Wiring Field Port to LonWorks Network ................................................... 21 3.5 Power-Up ProtoNode.................................................................................................................... 22 4 Auto-Discovery: Saving RS-485 device configurations................................................................. 23 4.1 Auto-Discovery with DIP Switch Method: After Completion – Turn Off to Save Configuration .... 23 5 Use ProtoNode’s Web Configurator to Select Device Profiles ..................................................... 24 5.1 Connect the PC to ProtoNode via the Ethernet Port .................................................................... 24 5.2 Connecting to ProtoNode’s Web Configurator ............................................................................. 25 5.2.1 Changing Device COM Settings ............................................................................................. 25 5.2.2 Auto-Discovery with the Web-Configurator ............................................................................. 26 5.2.3 Selecting Profiles for Devices Connected to ProtoNode – Must Use Web Configurator to Configure ENVI’s................................................................................................................................ 27 5.3 BACnet/IP and Modbus TCP/IP: Setting IP Address for Field Network ....................................... 29 6 BACnet MS/TP and BACnet/IP: Setting Node_Offset to Assign Specific Device Instances ..... 31 7 How to Start the Installation Over: Clearing Profiles ..................................................................... 32 8 LonWorks (FPC-N35): Commissioning ProtoNode on a lonworks Network ............................... 33 8.1 Commissioning ProtoNode FPC-N35 on a LonWorks Network ................................................... 33 8.1.1 Instructions to Download XIF File from ProtoNode FPC-N35 Using Browser ........................ 33 9 CAS BACnet Explorer for Validating ProtoNode in the Field ........................................................ 35 9.1 Downloading the CAS Explorer and Requesting an Activation Key ............................................. 35 9.2 CAS BACnet Setup....................................................................................................................... 36 9.2.1 CAS BACnet MS/TP Setup ..................................................................................................... 36 9.2.2 CAS BACnet BACnet/IP Setup ............................................................................................... 36 Appendix A. Troubleshooting .................................................................................................................. 37 Appendix A.1. Viewing Diagnostic information ........................................................................................ 37 Page 5 of 54 Harsco Patterson Kelley’s ProtoNode Startup Guide Appendix A.2. Check Wiring and Settings............................................................................................... 38 Appendix A.3. Take Diagnostic Capture With the FieldServer Utilities ................................................... 38 Appendix A.4. BACnet: Setting Network_Number for more than one ProtoNode on Subnet ................. 41 Appendix A.5. LED Diagnostics for Modbus RTU Communications Between ProtoNode and Devices 42 Appendix B. Vendor Information - Harsco Industrial Patterson-Kelley .............................................. 43 Appendix B.1. ENVI Modbus RTU Mappings to BACnet MS/TP, BACnet/IP, Metasys N2 and LonWorks ................................................................................................................................................................. 43 Appendix B.2. Love Modbus RTU Mappings to BACnet MS/TP, BACnet/IP, Metasys N2 and LonWorks ................................................................................................................................................................. 46 Appendix B.3. Nuro Modbus RTU Mappings to BACnet MS/TP, BACnet/IP, Metasys N2 and LonWorks ................................................................................................................................................................. 48 Appendix C. “A” Bank DIP Switch Settings ........................................................................................... 50 Appendix C.1. “A” Bank DIP Switch Settings .......................................................................................... 50 Appendix D. Reference ............................................................................................................................. 53 Appendix D.1. Specifications ................................................................................................................... 53 Appendix D.1.1. Compliance with UL Regulations ........................................................................... 53 Appendix E. Limited 2 Year Warranty ..................................................................................................... 54 Page 6 of 54 Harsco Patterson Kelley’s ProtoNode Startup Guide LIST OF FIGURES Figure 1: Method of configuration for the devices ......................................................................................... 9 Figure 2: Modbus Registers .......................................................................................................................... 9 Figure 3: ProtoCessor Part Numbers .......................................................................................................... 10 Figure 4: Modbus RTU COM Settings ........................................................................................................ 11 Figure 5: S Bank DIP Switches ................................................................................................................... 12 Figure 6: MAC Address DIP Switches ........................................................................................................ 14 Figure 7: Baud Rate DIP Switches ............................................................................................................. 16 Figure 8: Baud Rate .................................................................................................................................... 16 Figure 9: ProtoNode FPC-N34 (upper) and ProtoNode FPC-N35 (lower) ................................................. 17 Figure 10: Wiring diagram for Modbus RTU RS-485 connections to the ProtoNode’s RS-485 port .......... 18 Figure 11: Modbus RS-485 Biasing set to ON position FPC-N34 (left) and FPC-N35 (right) .................... 19 Figure 12: Modbus RS-485 End-Of-Line Termination on the FPC-N34 (left) and FPC-N35 (right) ........... 20 Figure 13: Connection from ProtoNode to RS-485 Field Protocol .............................................................. 21 Figure 14: RS-485 EOL Switch ................................................................................................................... 21 Figure 15: LonWorks Terminal .................................................................................................................... 21 Figure 16: Required current draw for the ProtoNode .................................................................................. 22 Figure 17: Power Connections .................................................................................................................... 22 Figure 18: S3 DIP Switch setting for Auto Discovering Devices ................................................................. 23 Figure 19: Web Configurator Showing no Active Profiles ........................................................................... 25 Figure 20: Discovering devices ................................................................................................................... 26 Figure 21: Web Configurator Showing Available Profiles for Selection ...................................................... 27 Figure 22: Web Configurator Showing Node-ID ......................................................................................... 28 Figure 23: Web Configurator Showing an Active Profile Addition............................................................... 28 Figure 24: Web Configurator screen with Active Profiles ........................................................................... 29 Figure 25: Changing IP Address via FST Web GUI ................................................................................... 30 Figure 26: Web Configurator screen ........................................................................................................... 31 Figure 27: Web Configurator screen ........................................................................................................... 32 Figure 28: LonWorks Service Pin Location ................................................................................................. 33 Figure 29: Sample of Fserver.XIF File ........................................................................................................ 34 Figure 30: Downloading the CAS Explorer ................................................................................................. 35 Figure 31: Requesting CAS Activation Key ................................................................................................ 35 Figure 32: Error messages screen .............................................................................................................. 37 Figure 33: Ethernet Port Location ............................................................................................................... 38 Figure 34: Web Configurator showing setting the network number for BACnet ......................................... 41 Figure 35: Diagnostic LEDs ........................................................................................................................ 42 Figure 36: Specifications ............................................................................................................................. 53 Page 7 of 54 Harsco Patterson Kelley’s ProtoNode Startup Guide 1 INTRODUCTION 1.1 ProtoNode Gateway ProtoNode is an external, high performance Building Automation multi-protocol gateway that is preconfigured to automatically communicate between any of Harsco Industrial Patterson-Kellley’s products (hereafter called “device”) to various building automation protocols. These protocols include 1 2 3 BACnet® MS/TP, BACnet/IP, Metasys® N2 by JCI, Modbus TCP/IP, and LonWorks® . It is not necessary to download any configuration files to support the required applications. ProtoNode is pre-loaded with tested Profiles/Configurations for the supported devices. The We use 2 methods to dynamically configure the ProtoNode to support the devices with the selected protocol. 1 2 4 Auto-Discovery: Supported RS-485 devices can be automatically detected and identified for addition to the ProtoNode’s configuration. (Section 1.2) Web Configurator: For RS-485 devices that are not supported by Auto-Discovery, use a browser to connect to the ProtoNode’s Web Configurator utility. Select the device(s) from a dropdown list of known profiles and assign a Modbus Node-ID. Then the ProtoNode automatically builds the configuration to support the device(s) with the desired protocol. BACnet is a registered trademark of ASHRAE Metasys is a registered trademark of Johnson Controls Inc. LonWorks is a registered trademark of Echelon Corporation Page 8 of 54 Harsco Patterson Kelley’s ProtoNode Startup Guide Methods of Configuration – Harsco Industrial Patterson-Kelley’s Devices 1.2 The ProtoNode offers two methods of configuration: Auto-Discovery for RS-485 devices listed below in Figure 1. Web Configurator for RS-485 devices that cannot be identified by Auto-Discovery. Devices Type of Communication Type of Configuration ENVI RS-485 Web Configurator Love RS-485 Auto-Discover Nuro RS-485 Auto-Discover Figure 1: Method of configuration for the devices 1.3 Harsco Industrial Patterson-Kelley’s Devices and Point Count Available The total number of devices attached to ProtoNode FPC-N34 cannot exceed 1500 Modbus registers for BACnet MS/TP, BACnet/IP, Modbus TCP/IP or Metasys N2. The total number of devices attached to ProtoNode FPC-N35 cannot exceed 1000 Modbus registers for LonWorks. Devices Point Count ENVI 53 LOVE 40 NURO 31 Figure 2: Modbus Registers Page 9 of 54 Harsco Patterson Kelley’s ProtoNode Startup Guide 2 BACNET/LONWORKS SETUP FOR PROTOCESSOR PROTONODE FPCN34/FPC-N35 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 ProtoNode FPC-N34 FPC-N34-0710 ProtoNode FPC-N35 FPC-N35-103-401-0771 Figure 3: ProtoCessor Part Numbers FPC-N34 units have the following 3 ports: RS-485 + Ethernet + RS-485 FPC-N35 units have the following 3 ports: LonWorks + Ethernet + RS-485 Page 10 of 54 Harsco Patterson Kelley’s ProtoNode Startup Guide 2.2 Configuring Device Communications 2.2.1 Set Modbus COM setting on all of the devices connected to the ProtoNode All of the devices connected to ProtoNode MUST have the same Baud Rate, Data Bits, Stop Bits, and Parity settings. Figure 4 specifies the device serial port settings required to communicate with the ProtoNode. Set the Modbus COM settings on the devices now. When mixing devices, the selected baud rates are required to match the slowest device (ENVI=9600). When there are no ENVI units present, the baud rate could be set faster (LOVE end NURO support 19200 and 38400). o The ProtoNode’s default settings are 9600 / None / 8 /1 o Ability to change the ProtoNode’s Device COM settings are offered later in Section 5.2.1 The Selected device COM settings need to be documented. Serial Port Setting ENVI LOVE NURO Protocol Modbus RTU Modbus RTU Modbus RTU Baud Rate 9600 9600, 19.2k, 38.4k 9600, 19.2k, 38.4k Parity None None None Data Bits 8 8 8 Stop Bits 1 1 1 Figure 4: Modbus RTU COM Settings 2.2.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. o The Modbus Node-ID’s assigned are used for designating the Device Instance for BACnet/IP and BACnet MS/TP (Section 2.4.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. Page 11 of 54 Harsco Patterson Kelley’s ProtoNode Startup Guide 2.3 Selecting the Desired Field Protocol and Enabling Auto -Discovery 2.3.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 Figure 4 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. ProtoNode FPC-N35 units do not use the “S” bank DIP switches (S0 – S2) to select a Field Protocol. o On ProtoNode FPC-N35 units, these switches are disabled; the Field Protocol is always LonWorks. S0 S1 S2 S3 S0 – S3 DIP Switches S Bank DIP Switch Location ProtoNode FPC-N34 Profile BACnet/IP BACnet MS/TP Metasys N2 Modbus TCP/IP S Bank DIP Switches S0 S1 S2 Off Off Off On Off Off Off On Off On On Off BACnet MS/TP, BACnet/IP, Modbus TCP/IP, and Metasys N2 Settings for ProtoNode FPC-N34 (BACnet) ProtoNode FPC-N34 and FPC-N35 S3 DIP Switch Auto-Discovery Mode Auto-Discovery ON – Build New Configuration Auto-Discover OFF – Save Current Configuration Figure 5: S Bank DIP Switches Page 12 of 54 S3 On Off Harsco Patterson Kelley’s ProtoNode Startup Guide 2.3.2 Enabling Auto-Discovery There are two methods to activate Auto-Discovery: The first is by using the DIP switches (as described below) and the second method is by using the Web-Configurator (see Section 5.2.2) If using the Web-Configurator method, leave the S3 DIP switch in the OFF position. 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. o See the table in Figure 1 for RS-485 devices that are supported by Auto-Discovery. o See the table in Figure 5 for the DIP switch setting to enable Auto-Discovery. o If the ProtoNode is being installed for the first time, set S3 to the ON position to enable Auto-Discovery. o The ON position is when the DIP switches are set closest to the inside of the box for the DIP switch setting to enable Auto Discovery. Page 13 of 54 Harsco Patterson Kelley’s ProtoNode Startup Guide 2.4 Setting the MAC Address, Device Instance and Baud Rate 2.4.1 BACnet MS/TP (FPC-N34): Setting the MAC Address BACnet Network Only 1 MAC address is set for ProtoNode regardless of how many devices are connected to ProtoNode. 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.1 for the complete range of MAC Addresses and DIP switch settings. Figure 6: MAC Address DIP Switches NOTE: When setting DIP Switches, please ensure that power to the board is OFF. Page 14 of 54 Harsco Patterson Kelley’s ProtoNode Startup Guide 2.4.2 BACnet MS/TP and BACnet/IP (FPC-N34): Setting the Device Instance The BACnet Device Instances will be calculated by adding the Node_Offset (default value is 50,000) to the device’s Modbus Node ID (that was assigned in Section 2.2). The BACnet Device Instance can range from 1 to 4,194,303. To assign specific Device Instance values, change the Node_Offset value. 2.4.2.1) (Section For example: o o Node_Offset value (default) = 50,000 Device 1 has a Modbus Node-ID of 1 o Device 2 has a Modbus Node-ID of 22 o Device 3 has a Modbus Node-ID of 33 o Given that: Device Instance = Node_Offset + Modbus Node_ID o Device Instance, Device 1 = 50,000 + 1 = 50,001 o Device Instance, Device 2 = 50,000 + 22 = 50,022 o Device Instance, Device 3 = 50,000 + 33 = 50,033 2.4.2.1 BACnet MS/TP or BACnet/IP: Assigning Specific Device Instances With the default Node_Offset value of 50,000 the Device Instances values generated will be within the range of 50,001 to 50,127. 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. Methods for changing the Node_Offset value are provided in Section 6 o This step cannot be performed until after the unit is connected and powered. 2.4.3 Metasys N2 or Modbus TCP/IP (FPC-N34): Setting the Node-ID The Modbus RTU Node-ID’s assigned to the devices attached to the ProtoNode in Section 2.2 will be the Metasy N2 and Modbus TCP/IP Node_ID’s for the field protocols. Metasys N2 and Modbus TCP/IP Node-ID Addressing: Metasys N2 and Modbus TCP/IP Node-ID’s range from 1-255. Page 15 of 54 Harsco Patterson Kelley’s ProtoNode Startup Guide 2.4.4 BACnet MS/TP (FPC-N34): Setting the Baud Rate “B” bank DIP switches B0 – B3 can be used to set the Field baud rate of the ProtoNode to match the baud rate required by the Building Management System for BACnet MS/TP. The baud rate on ProtoNode for Metasys N2 is set for 9600. “B” bank DIP switches B0 – B3 are disabled for Metasys N2 on ProtoNode FPC-N34. “B” bank DIP switches B0 – B3 are disabled on ProtoNode FPC-N35 (FPC-N35 LonWorks). B0 B1 B2 B3 Figure 7: Baud Rate DIP Switches 2.4.4.1 Baud Rate DIP Switch Selection Baud 9600 19200 38400 57600 76800 B0 On Off On Off On B1 On Off On Off Off B2 On Off Off On On Figure 8: Baud Rate Page 16 of 54 B3 Off On On On On Harsco Patterson Kelley’s ProtoNode Startup Guide 3 INTERFACING PROTONODE TO DEVICES 3.1 ProtoNode FPC-N34 and FPC-N35 Showing Connection Ports Figure 9: ProtoNode FPC-N34 (upper) and ProtoNode FPC-N35 (lower) Page 17 of 54 Harsco Patterson Kelley’s ProtoNode Startup Guide 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 FPC-N34 (BACnet) and FPC-N35 (LonWorks). Pins 1 through 3 are for Modbus RS-485 devices. o 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.5). 3.2.1 Connecting NURO Modbus RTU Boilers to the ProtoNode’s RS -485 Connect NURO’s Modbus COM A to ProtoNode’s pin 1 labeled Tx/+ on the Phoenix 6 pin connector. Connect NURO’s Modbus COM B to ProtoNode’s pin 2 labeled Rx/- on the Phoenix 6 pin connector. Do not connect Ground between NURO and the ProtoNode’s RS-485 Ground. 3.2.2 Connecting LOVE Modbus RTU Boilers to the ProtoNode’s RS -485 Connect LOVE’s Modbus DATA+ to ProtoNode’s pin 1 labeled Tx/+ on the Phoenix 6 pin connector. Connect LOVE’s Modbus DATA- to ProtoNode’s pin 2 labeled Rx/- on the Phoenix 6 pin connector. Do not connect Ground between LOVE and the ProtoNode’s RS-485 Ground. 3.2.3 Connecting ENVI Modbus RTU Boilers to the ProtoNode’s RS -485 Connect ENVI’s Modbus COM 1A (RS-485+) to ProtoNode’s pin 1 labeled B+ (RS-485+) on the Phoenix 6 pin connector. Connect ENVI’s Modbus COM 1B (RS-485-) to ProtoNode’s pin 2 labeled A- (RS-485-) on the Phoenix 6 pin connector. Do not connect Ground between ENVI and the ProtoNode’s RS-485 Ground. Figure 10: Wiring diagram for Modbus RTU RS-485 connections to the ProtoNode’s RS-485 port Page 18 of 54 Harsco Patterson Kelley’s ProtoNode Startup Guide 3.2.4 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. None of the ENVI’s support biasing. The ProtoNode is required to bias the RS-485 network. 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 ON. The biasing MUST always be left set to the ON position. The ON position is when the 2 RED biasing jumpers straddle the 4 pins closest to the inside of the board of the ProtoNode. See Figure 11. RS-485 Bias Switch Figure 11: Modbus RS-485 Biasing set to ON position FPC-N34 (left) and FPC-N35 (right) Page 19 of 54 Harsco Patterson Kelley’s ProtoNode Startup Guide 3.2.5 End of Line Termination Switch for the Modbus RS-485 port on the ProtoNode 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. o 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). Modbus RS-485 EOL Switch Leave in A Position Figure 12: Modbus RS-485 End-Of-Line Termination on the FPC-N34 (left) and FPC-N35 (right) Page 20 of 54 Harsco Patterson Kelley’s ProtoNode Startup Guide 3.3 BACnet MS/TP or Metasys N2 (FPC-N34): W iring Field Port to RS-485 Network Note: See Section 5.3 for information on connecting to a BACnet/IP or Modbus TCP/IP network. Connect the RS-485 network wires for BACnet MS/TP or Metasys N2 to the 3-pin RS-485 connector on ProtoNode FPC-N34 as shown below in Figure 13. o The RS-485 GND (Pin 3) is not typically connected. 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). o To enable the EOL Termination, turn the EOL switch ON (switch position = left side). Pin Assignment RS-485 + RS-485 RS-485 GND - ProtoNode Pin # Pin 1 Pin 2 Pin 3 G BMS RS-485 Wiring RS-485 + RS-485 - + o Figure 13: Connection from ProtoNode to RS-485 Field Protocol End-of-Line Switch Figure 14: RS-485 EOL Switch 3.4 LonW orks (FPC-N35): Wiring Field Port to LonW orks Network Connect ProtoNode to the field network with the LonWorks terminal using a twisted pair nonshielded cable. LonWorks has no polarity. Figure 15: LonWorks Terminal Page 21 of 54 Harsco Patterson Kelley’s ProtoNode Startup Guide 3.5 Power-Up ProtoNode Apply power to ProtoNode as show below in Figure 17. complies with the specifications provided in Appendix D.1. Ensure that the power supply used ProtoNode accepts either 9-30VDC or 12-24 VAC on pins 4 and 5. Frame GND on pin 6 should be connected. Power Requirement for ProtoNode External Gateway Current Draw Type ProtoNode Family 12VDC/VAC 24VDC/VAC 30VDC FPC – N34, N36, N38 (Typical) 170mA 100mA 80mA FPC – N34, N36, N38 (Maximum) 240mA 140mA 100mA FPC – N35, N37, N39 (Typical) 210mA 130mA 90mA FPC – N35, N37, N39 (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 16: Required current draw for the ProtoNode Power to ProtoNode ProtoNode Pin Pin # Assignment Power In (+) Power In (-) Frame Ground Pin 4 Pin 5 Pin 6 V+ VFRAME GND Figure 17: Power Connections Page 22 of 54 Harsco Patterson Kelley’s ProtoNode Startup Guide 4 AUTO-DISCOVERY: SAVING RS-485 DEVICE CONFIGURATIONS There are some RS-485 devices that cannot be recognized by Auto-Discovery; see Section 1.2 for a list of devices. Devices that cannot be configured by Auto-Discovery are setup by using the Web Configurator (Section 5). There are two ways to run Auto-Discovery: Use the S3 DIP switch to enable Auto-Discovery and save the configuration (Section 2.3.2 + 4.1) Use the Web-Configurator’s interface to run Auto-Discovery (Section 5.1 + 5.2). If using the Web-Configurator’s interface, skip Section 4.1 below and go to Section 5.1. Auto-Discovery with DIP Switch Method: After Completion – Turn Off to Save Configuration 4.1 The S3 DIP Switch for Enabling Auto-Discovery should have been set in section 2.3.2 before applying power to the ProtoNode. Do not Enable Auto-Discovery via S3 DIP switch when the unit is powered. When power is applied to a ProtoNode that is set to Enable Auto-Discovery, it will take about 10 minutes to complete the discovery of all of the RS-485 devices attached to the ProtoNode. The “TX” LED will flash during Auto-Discovery. The “TX LED will stop flashing when completed. Once the ProtoNode has discovered all of the RS-485 devices, turn OFF the power supplied to the ProtoNode and set the S3 DIP switch to the OFF position to save the current configuration. Then turn the power to the ProtoNode back ON. The stored configuration will be loaded. ProtoNode FPC-N34 and FPC-N35 S3 DIP Switch Auto-Discovery Mode Auto-Discovery ON – Build New Configuration Auto-Discover OFF – Save Current Configuration S3 On Off Figure 18: S3 DIP Switch setting for Auto Discovering Devices Page 23 of 54 Harsco Patterson Kelley’s ProtoNode Startup Guide 5 USE PROTONODE’S WEB CONFIGURATOR TO SELECT DEVICE PROFILES 5.1 Connect the PC to ProtoNode via the Ethernet Port Connect a Cat 5 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. Go to Right-click on Local Area Connection > Properties Highlight Select: Use the following IP address > Click > > twice Page 24 of 54 Harsco Patterson Kelley’s ProtoNode Startup Guide Connecting to ProtoNode’s Web Configurator 5.2 After setting your PC to be on the same subnet as the ProtoNode (Section 5.1), open a web browser on your 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, you will need to get the assigned IP address from the network administrator. 5.2.1 Changing Device COM Settings When you open the Web Configurator, you will see the Device COM settings section as the first 4 fields of the screen. See Figure 20. o mod_baud_rate o mod_parity o mod_data_bits o mod_stop_bits Each field specifies the accepted range of values. After entering a new Device COM setting value, click the “Submit” button to save the change. After completing all Device COM setting changes, click “System Restart” to apply the saved changes. Figure 19: Web Configurator Showing no Active Profiles Page 25 of 54 Harsco Patterson Kelley’s ProtoNode Startup Guide 5.2.2 Auto-Discovery with the Web-Configurator Note: To run Auto-Discovery with the Web-Configurator, the S3 DIP switch must be in the OFF position when power is provided to the ProtoNode. When you open the Web Configurator, you will see the “Discovery Mode” button at the bottom of the screen. The dark green color of the indicator in the Discovery Mode button indicates it is not active. Click on the “Discovery Mode” button. A dialog box will be presented to confirm restart. When the ProtoNode restarts it will begin Auto-Discovery. The bright green color of the indicator in the Discovery Mode button indicates it is active (searching). It will take about 10 minutes to complete the discovery of all to the RS-485 devices attached to the ProtoNode. See Figure 20. The “TX” LED will flash during Auto-Discovery. The “TX” LED will stop flashing when completed. After the discovery completes, click on the “Discovery Mode” button to save the configuration and restart. A dialog box will be presented to “disable discovery and restart the device”. Figure 20: Discovering devices Page 26 of 54 Harsco Patterson Kelley’s ProtoNode Startup Guide 5.2.3 Selecting Profiles for Devices Connected to ProtoNode – Must Use Web Configurator to Configure ENVI’s When you open the Web Configurator, you will see the Active Profiles section 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 19) To add an active profile to support a device, click the ADD button under Active Profiles. His will present a drop-down box underneath the Current Profile column that lists all the available profiles. (Figure 21) For every device that is added, you need to specify the Modbus Node-ID assigned to the particular device. This specification must match the device’s network settings. Figure 21: Web Configurator Showing Available Profiles for Selection Page 27 of 54 Harsco Patterson Kelley’s ProtoNode Startup Guide Figure 22: Web Configurator Showing Node-ID Once the Profile for the device has been selected from the drop-down list, enter the value of the device’s Modbus Node-ID which was assigned in Section 2.2.2. See Figure 22. 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 show in Figure 23. Figure 23: Web Configurator Showing an Active Profile Addition Page 28 of 54 Harsco Patterson Kelley’s ProtoNode Startup Guide 5.3 BACnet/IP and Modbus TCP/IP: Setting IP Address for Field Network After setting your PC to be on the same subnet as the ProtoNode (Section 5.1), open a web browser on your PC and enter the IP address of the ProtoNode; the default address is 192.168.1.24. The Web Configurator will be displayed as your landing page. (Figure 24) To access the FST Web GUI, click on the “Diagnostics & Debugging” button in the bottom right side of the page. Figure 24: Web Configurator screen with Active Profiles Page 29 of 54 Harsco Patterson Kelley’s ProtoNode Startup Guide Figure 25: Changing IP Address via FST Web GUI From the FST Web GUI’s landing page, click on “Setup” to expand the navigation tree and then select “Network Settings” to access the IP Settings menu. (Figure 25). Modify the IP address (N1 IP address field) of the ProtoNode Ethernet port. If necessary, change the Netmask (N1 Netmask field). Type in a new Subnet Mask If necessary, change the IP Gateway (Default Gateway field) Type in a new IP Gateway Note: If the ProtoNode is connected to a router, the IP Gateway of the ProtoNode should be set to the IP address of the router that it is connected to. Reset ProtoNode Unplug Ethernet cable from PC and connect it to the network hub or router Record the IP address assigned to the ProtoNode for future reference. Page 30 of 54 Harsco Patterson Kelley’s ProtoNode Startup Guide 6 BACNET MS/TP AND BACNET/IP: SETTING NODE_OFFSET TO ASSIGN SPECIFIC DEVICE INSTANCES After setting your PC to be on the same subnet as the ProtoNode (Section 5.1), open a web browser on your 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, you will need to get the assigned IP address from the network administrator. The Web Configurator will be displayed as your landing page. (Figure 26) Node_Offset field will be presented displaying the current value (default = 50,000). Change the value of Node_Offset to establish the desired Device Instance values, and click SUBMIT. o Given that: Node_Offset + Modbus Node_ID = Device Instance o Then: Node_Offset (required) = Device Instance (desired) – Modbus Node_ID For example: o Device 1 has a Modbus Node-ID of 1 o Device 2 has a Modbus Node-ID of 22 o Device 3 has a Modbus Node-ID of 33 o Desired Device Instance for 1 device = 1,001 o Node_Offset (required) = 1,001 – (Modbus Node_ID) = 1,001 – 1 = 1,000 o The Node_Offset value will be applied to all devices. o Device 1 Instance will then be = 1,000 + Modbus Node_ID = 1,000 + 1 = 1,001 o Device 2 Instance will then be = 1,000 + Modbus Node_ID = 1,000 + 22 = 1,022 o Device 3 Instance will then be = 1,000 + Modbus Node_ID = 1,000 + 33 = 1,033 st Figure 26: Web Configurator screen Page 31 of 54 Harsco Patterson Kelley’s ProtoNode Startup Guide 7 HOW TO START THE INSTALLATION OVER: CLEARING PROFILES After setting your PC to be on the same subnet as the ProtoNode (section 5.1), open a web browser on your 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, you will need to get the assigned IP address from the network administrator. The Web Configurator will be displayed as your landing page. At the bottom-left of the page, click the “Clear Profiles and Restart” button. Once restart is complete, all the past profiles that were discovered and or added via the Web configurator will be delete. The unit is now ready to be reinstalled. Figure 27: Web Configurator screen Page 32 of 54 Harsco Patterson Kelley’s ProtoNode Startup Guide 8 LONWORKS (FPC-N35): COMMISSIONING PROTONODE ON A LONWORKS NETWORK Commissioning may only be performed by the LonWorks administrator. 8.1 Commissioning ProtoNode FPC-N35 on a LonW orks Network The User will be prompted by the LonWorks Administrator to hit the Service Pin on the ProtoNode FPC-N35 at the correct step of the Commissioning process which is different for each LonWorks Network Management Tool. If an XIF file is required, see steps in Section 8.1.1 to generate XIF Figure 28: LonWorks Service Pin Location 8.1.1 Instructions to Download XIF File from ProtoNode FPC-N35 Using Browser Connect a 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 XP: Go to > > Right-click on Local Area Connection > Properties Highlight > For Windows 7: Go to > > > > Right-click on Local Area Connection > Properties Highlight > Page 33 of 54 Harsco Patterson Kelley’s ProtoNode Startup Guide For Windows XP and Windows 7, select: Use the following IP address Click Open a web browser and go to the following address: IP address of ProtoCessor/fserver.xif Example: 192.168.1.24/fserver.xif If the web browser prompts you to save file, save the file onto the PC. If the web browser displays the xif file as a web page, save the file on your PC as fserver.xif twice Figure 29: Sample of Fserver.XIF File Page 34 of 54 Harsco Patterson Kelley’s ProtoNode Startup Guide 9 CAS BACNET EXPLORER FOR VALIDATING PROTONODE IN THE FIELD ProtoCessor has arranged a complementary 2 week fully functional copy of CAS BACnet Explorer (through Chipkin Automation) that can be used to validate BACnet MS/TP and/or BACnet/IP communications of ProtoNode in the field without having to have the BMS Integrator on site. A Serial or USB to RS-485 converter is needed to test BACnet MS/TP. 9.1 Downloading the CAS Explorer and Requesting an Activation Key To request the complementary BACnet CAS key, go to http://app.chipkin.com/activation/twoweek/ and fill in all the information. Enter Vendor Code “Harsco12”. Once completed, the email address that was submitted will be registered. Figure 30: Downloading the CAS Explorer Go to the following web site, download and install the CAS BACnet Explorer to your PC: http://www.chipkin.com/technical-resources/cas-bacnet-explorer/ Open CAS BACnet Explorer; in the CAS Activation form, enter the email address that was registered and click on “Request a key”. The CAS key will then be emailed to the registered address. Cut/paste key from email into the Product key field and click “Activate”. Figure 31: Requesting CAS Activation Key Page 35 of 54 Harsco Patterson Kelley’s ProtoNode Startup Guide 9.2 CAS BACnet Setup These are the instructions to set CAS Explorer up for the first time on BACnet MS/ST and BACnet/IP. 9.2.1 9.2.2 CAS BACnet MS/TP Setup Using the Serial or USB to RS-485 converter, connect it to your PC and the 3 Pin BACnet MS/TP connector on ProtoNode FPC-N34. In CAS Explorer, do the following: o Click on settings o Check the BACnet MS/TP box and uncheck the BACnet/IP and BACnet Ethernet boxes o Set the BACnet MS/TP MAC address to 0 o Set the BACnet MS/TP Baud Rate to 38400 o Click Ok o On the bottom right-hand corner, make sure that the BACnet MS/TP box is green o Click on discover o Check all 4 boxes o Click Send CAS BACnet BACnet/IP Setup See Section 5.3 to set the IP address and subnet of the PC that will be running the CAS Explorer. Connect a straight through or cross Ethernet cable from the PC to ProtoNode. In CAS Explorer, do the following: o Click on settings o Check the BACnet/IP box and uncheck the BACnet MS/TP and BACnet Ethernet boxes o In the “Select a Network Device” box, select the network card of the PC by clicking on it o Click Ok o On the bottom right-hand corner, make sure that the BACnet/IP box is green o Click on discover o Check all 4 boxes o Click Send Page 36 of 54 Harsco Patterson Kelley’s ProtoNode Startup Guide Appendix A. Troubleshooting Appendix A.1. Viewing Diagnostic information Type the IP address of the ProtoNode into your web browser or use the FieldServer Toolbox to connect to the ProtoNode. Click on Diagnostics and Debugging Button, then click on view, and then on connections. If there are any errors showing on the Connection page, please refer to Appendix A.2 for the relevant wiring and settings. Figure 32: Error messages screen Page 37 of 54 Harsco Patterson Kelley’s ProtoNode Startup Guide Appendix A.2. Check Wiring and Settings No COMS on Modbus RTU side. If Tx/Rx are not flashing rapidly then there is a COM issue on the Modbus side and you need to check the following things: o Visual observations of LEDs on ProtoNode. (Appendix A.5) o Check baud rate, parity, data bits, stop bits o Check Modbus device address o Verify wiring o Verify all the Modbus RTU devices that were discovered in FST Web Configurator. (Section 5.2) Field COM problems: o Visual observations of LEDs on ProtoNode. (Appendix A.5) o Visual dipswitch settings (using correct baud rate and device instance) o Verify IP address setting o Verify wiring If the problem still exists, a Diagnostic Capture needs to be taken and sent to Sierra Monitor Corporation. (Appendix A.3) Appendix A.3. Take Diagnostic Capture With the FieldServer Utilities Once the Diagnostic Capture is complete, email it to [email protected]. The Diagnostic Capture will allow us to rapidly diagnose the problem. Ensure that FieldServer Toolbox is Loaded on the PC that is currently being used, or download FieldServer-Toolbox.zip on the Sierra Monitor webpage, under Customer Care: Resource Center, Software Downloads: http://www.sierramonitor.com/customer-care/resource-center?filters=software-downloads Extract the executable file and complete the installation. Ethernet Port Figure 33: Ethernet Port Location Disable any wireless Ethernet adapters on the PC/Laptop. Disable firewall and virus protection software if possible. Connect a standard Cat 5 Ethernet cable between the PC and ProtoNode. Double click on the FS Toolbox Utility. Page 38 of 54 Harsco Patterson Kelley’s ProtoNode Startup Guide Step 1: Take a Log o Click on the diagnose icon o Select full Diagnostic o If desired, the default capture period can be changed. o Click on Start Diagnostic of the desired device. Page 39 of 54 Harsco Patterson Kelley’s ProtoNode Startup Guide o Wait for Capture period to finish. Diagnostic Test Complete window will appear. Step 2: Send Log o Once the Diagnostic test is complete, a .zip file will be saved on the PC. o Choose open to launch explorer and have it point directly at the correct folder. Send the Diagnostic zip file to [email protected] Page 40 of 54 Harsco Patterson Kelley’s ProtoNode Startup Guide Appendix A.4. BACnet: Setting Network_Number for more than one ProtoNode on Subnet For both BACnet MS/TP and BACnet/IP, if more than one ProtoNode is connected to the same subnet, they must be assigned unique Network_Number values. On the main Web Configuration screen, update the Network Number with the “network_nr” field and click submit. The default value is 50. . Figure 34: Web Configurator showing setting the network number for BACnet Page 41 of 54 Harsco Patterson Kelley’s ProtoNode Startup Guide Appendix A.5. LED Diagnostics for Modbus RTU Communications Between ProtoNode and Devices Please see the diagram below for ProtoNode FPC-N34 and FPC-N35 LED Locations. Diagnostic LEDs Tag SPL RUN ERR RX TX PWR Description Used to monitor Node offline The RUN LED will start flashing 20 seconds after power indicating normal operation. The SYS ERR LED will go on solid 15 seconds after power up. It will turn off after 5 seconds. A steady red light will indicate there is a system error on ProtoNode. If this occurs, immediately report the related “system error” shown in the error screen of the GUI interface to FieldServer Technologies for evaluation. The RX LED will flash when a message is received on the host port. The TX LED will flash when a message is sent on the host port. This is the power light and should show steady green at all times when ProtoNode is powered. Figure 35: Diagnostic LEDs Page 42 of 54 Harsco Patterson Kelley’s ProtoNode Startup Guide Appendix B. Vendor Information - Harsco Industrial Patterson-Kelley Appendix B.1. ENVI Modbus RTU Mappings to BACnet MS/TP, BACnet/IP, Metasys N2 and LonWorks Point Name State (See Note 1) Supply Temp Return Temp DHW Temp Header Temp Firing Rate Flue Gas Temp HX Temp Outside Temp Flame Signal (See Note 2) CH Setpoint (Read/Write) DHW Setpoint (Read/Write) Boiler Operation (Read/Write) (See Note 3) High Outdoor Air Temp (Read/Write) Min Outdoor Air Setpoint (Read/Write) Low Outdoor Air Temp (Read/Write) Max Outdoor Air Setpoint (Read/Write) Outdoor Air Shutdown Temp (Read/Write) Night Setback (Read/Write) Error Code (See Note 4) Analog In Analog Out Ignitions Burner High Hours BACnet Object Type AI AI AI AI AI AI AI AI AI AI AV AV AV 1 2 3 4 5 6 7 8 9 10 11 12 13 AI AI AI AI AI AI AI AI AI AI AO AO AO 1 2 3 4 5 6 7 8 9 10 11 12 13 nvoState_XXX nvoSupplyTmp_XXX nvoReturnTmp_XXX nvoDHWTmp_XXX nvoHeaderTmp_XXX nvoFiringRat_XXX nvoFluGasTmp_XXX nvoHXTmp_XXX nvoOutsidTmp_XXX nvoFlameSig_XXX nvi/nvoCHSP_XXX nvi/nvoDHWSP_XXX nvi/nvoBlrOpera_XXX State Supply Temp Return Temp DHW Temp Header Temp Firing Rate Flue Gas Temp HX Temp Outside Temp Flame Signal CH Setpoint DHW Setpoint Boiler Operation AV 14 AO 14 nvi/nvoHiOATmp_XXX High Outdoor Air Temp AV 15 AO 15 nvi/nvoMinOASP_XXX Min Outdoor Air Setpoint AV 16 AO 16 nvi/nvoLoOATmp_XXX Low Outdoor Air Temp AV 17 AO 17 nvi/nvoMaxOASP_XXX Max Outdoor Air Setpoint AV 18 AO 18 nvi/nvoOAShtdnTp_XXX Outdoor Air Shutdown Temp AV AI AI AI AI AI 19 20 21 22 23 24 AO AI AI AI AI AI 19 20 21 22 23 24 nvi/nvoNightStbk_XXX nvoErrorCode_XXX nvoAnalogIn_XXX nvoAnalogOut_XXX nvoIgnitions_XXX nvoBrnrHiHrs_XXX Night Setback Error Code Analog In Analog Out Ignitions Burner High Hours BACnet Object ID N2 Data Type N2 Point Address Page 43 of 54 Lon Name Lon SNVT Harsco Patterson Kelley’s ProtoNode Startup Guide Burner Medium Hours Burner Low Hours Water Level Low Gas Pressure Air Pressure Blocked Flue CH Pump DHW Pump Air Damper High Gas Pressure ET Error Number (See Note 4) ET Supply Temp ET Return Temp ET DHW Temp ET Flue Gas Temp ET HX Temp ET Outside Temp Boiler State Frost Protection DHW Mode CH Mode ET Month ET Day ET Year ET Hours ET Minutes ET Day Count High ET Day Count Low ET Run Hours AI AI BI BI BI BI BI BI BI BI AI AI AI AI AI AI AI AI BI BI BI AI AI AI AI AI AI AI AI 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 AI AI DI DI DI DI DI DI DI DI AI AI AI AI AI AI AI AI DI DI DI AI AI AI AI AI AI AI AI 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 nvoBrnrMdHrs_XXX nvoBrnrLoHrs_XXX nvoWaterLvl_XXX nvoLoGasPrs_XXX nvoAirPrs_XXX nvoBlckdFlue_XXX nvoCHPump_XXX nvoDHWPump_XXX nvoAirDamper_XXX nvoHiGasPrs_XXX nvoETErrNum_XXX nvoETSupTmp_XXX nvoETRetTmp_XXX nvoETDHWTmp_XXX nvoETFluGsTp_XXX nvoETHXTmp_XXX nvoETOtsdTmp_XXX nvoBlrState_XXX nvoFrstPrtct_XXX nvoDHWMode_XXX nvoCHMode_XXX nvoETMonth_XXX nvoETDay_XXX nvoETYear_XXX nvoETHrs_XXX nvoETMinutes_XXX nvoETDyCntHi_XXX nvoETDyCntLo_XXX nvoETRunHrs_XXX Burner Medium Hours Burner Low Hours Water Level Low Gas Pressure Air Pressure Blocked Flue CH Pump DHW Pump Air Damper High Gas Pressure ET Error Number ET Supply Temp ET Return Temp ET DHW Temp ET Flue Gas Temp ET HX Temp ET Outside Temp Boiler State Frost Protection DHW Mode CH Mode ET Month ET Day ET Year ET Hours ET Minutes ET Day Count High ET Day Count Low ET Run Hours NOTES: 1) “State” Codes: 1=resetting; 2=standby, waiting for demand; 3=relay circuit check; 4=relay circuit check; 5=pre-purging; 6=pre-purging; 7=pre-ignition with gas valve closed; 8=ignition with gas valve open; 9=burning; 10=post purging; 11=post purging; 12=post pumping for CH; 13=pumping for CH; 14=post pumping for DHW; 15=pumping for DHW; 16=error handling (locking); 17=error handling (blocking); 18=restarting burner control; 19=error handling; 20=error handling; 21=error handling Page 44 of 54 Harsco Patterson Kelley’s ProtoNode Startup Guide 2) “Flame Signal” Codes: 0=no flame; 128=flame 3) “Boiler Operation” Codes: 0=boiler off & pump off; 1=boiler on & pump auto control; 2=boiler off & pump constantly on; 3=boiler on & pump constantly on 4) “Error Code” Codes: 1=ignition failure; 4=max ∆T exceeded; 5=internal error gas valve relay; 6=internal error safety relay; 7=rapid rise outlet temperature; 8=fan wrong speed; 10=internal error E2PROM signal; 11=UV sensor defect; 12=internal error E2PROM error; 15=rapid rise inlet temperature; 16=internal error 16; 17=rapid rise HX temperature; 18=high limit; 20=late flame; 21=early flame; 24=flame failure; 25=air switch not open; 26=air switch not close; 30=low water level (ENVI versions 01BD, BD71, and 49A7) or internal error 30 (ENVI versions 6999 and 79F2); 31=low gas pressure (ENVI versions 01BD, BD71, and 49A7) or internal error 31 (ENVI versions 6999 and 79F2); 32=high gas pressure (ENVI versions 01BD, BD71, and 49A7) or internal error 32 (ENVI versions 6999 and 79F2); 35=internal error 35 (ENVI versions 01BD, BD71, and 49A7) or high flue temperature (ENVI versions 6999 and 79F2); 36=internal error 36 (ENVI versions 01BD, BD71, and 49A7) or false flame (ENVI versions 6999 and 79F2); 37=internal error 37 (ENVI versions 01BD, BD71, and 49A7) or low water level (ENVI versions 6999 and 79F2); 38=high flue temperature (ENVI versions 01BD, BD71, and 49A7) or low gas pressure (ENVI versions 6999 and 79F2); 39=false flame (ENVI versions 01BD, BD71, and 49A7) or blocked flue (ENVI versions 6999 and 79F2); 40=blocked flue (ENVI versions 01BD, BD71, and 49A7) or high inlet temperature (ENVI versions 6999 and 79F2); 41=high inlet temperature (ENVI versions 01BD, BD71, and 49A7) or reverse flow in/out (ENVI versions 6999 and 79F2); 42=reverse flow in/out (ENVI versions 01BD, BD71, and 49A7) or N/A (ENVI versions 6999 and 79F2); 43=N/A (ENVI versions 01BD, BD71, and 49A7) or no ground 60 hertz error (ENVI versions 6999 and 79F2); 44=no ground 60 hertz error (ENVI versions 01BD, BD71, and 49A7) or line neutral reverse (ENVI versions 6999 and 79F2); 45=line neutral reverse (ENVI versions 01BD, BD71, and 49A7) or line frequency error (ENVI versions 6999 and 79F2); 46=line frequency error (ENVI versions 01BD, BD71, and 49A7) or faulty ground (ENVI versions 6999 and 79F2); 47=faulty ground (ENVI versions 01BD, BD71, and 49A7) or internal error 47 (ENVI versions 6999 and 79F2); 48=internal error 47 (ENVI versions 01BD, BD71, and 49A7) or wrong boiler type (ENVI versions 6999 and 79F2); 49=wrong boiler type (ENVI versions 01BD, BD71, and 49A7) or rapid rise HX error (ENVI versions 6999 and 79F2); 50=rapid rise HX error (ENVI versions 01BD, BD71, and 49A7) or N/A (ENVI versions 6999 and 79F2); 51=N/A (ENVI versions 01BD, BD71, and 49A7) or outlet temperature sensor open (ENVI versions 6999 and 79F2); 52=outlet temperature sensor open (ENVI versions 01BD, BD71, and 49A7) or inlet temperature sensor open (ENVI versions 6999 and 79F2); 53=inlet temperature sensor open (ENVI versions 01BD, BD71, and 49A7) or N/A (ENVI versions 6999 and 79F2); 55=N/A (ENVI versions 01BD, BD71, and 49A7) or DHW temperature sensor open (ENVI versions 6999 and 79F2); 56=DHW temperature sensor open (ENVI versions 01BD, BD71, and 49A7) or HX temperature sensor open (ENVI versions 6999 and 79F2); 57=HX temperature sensor open (ENVI versions 01BD, BD71, and 49A7) or flue temperature sensor open (ENVI versions 6999 and 79F2); 58=flue temperature sensor open (ENVI versions 01BD, BD71, and 49A7) or N/A (ENVI versions 6999 and 79F2); 59=N/A (ENVI versions 01BD, BD71, and 49A7) or outlet temperature sensor short (ENVI versions 6999 and 79F2); 60=outlet temperature sensor short (ENVI versions 01BD, BD71, and 49A7) or inlet temperature sensor short (ENVI versions 6999 and 79F2); 61=inlet temperature sensor short (ENVI versions 01BD, BD71, and 49A7) or N/A (ENVI versions 6999 and 79F2); 63=N/A (ENVI versions 01BD, BD71, and 49A7) or DHW temperature sensor short (ENVI versions 6999 and 79F2); 64=DHW temperature sensor short (ENVI versions 01BD, BD71, and 49A7) or HX temperature sensor short (ENVI versions 6999 and 79F2); 65=HX temperature sensor short (ENVI versions 01BD, BD71, and 49A7) or flue temperature sensor short (ENVI versions 6999 and 79F2); 66=flue temperature sensor short (ENVI versions 01BD, BD71, and 49A7) or internal error 66 (ENVI versions 6999 and 79F2); 67=internal error 66 (ENVI versions 01BD, BD71, and 49A7) or high gas pressure (ENVI versions 6999 and 79F2); 68=IF communication failure; 69=header sensor open; 70=header sensor short; 71=rapid rise error Page 45 of 54 Harsco Patterson Kelley’s ProtoNode Startup Guide Appendix B.2. Love Modbus RTU Mappings to BACnet MS/TP, BACnet/IP, Metasys N2 and LonWorks Point Name Process Value (See Note 1) Setpoint (Read/Write) Upper-Limit of Temp Range Lower-Limit of Temp Range Control Method (Read/Write) (See Note 2) PB Proportional Band (Read/Write) Ti Integral Time (Read/Write) Td Derivative Time (Read/Write) Output Value (Read/Write) Upper-Limit Regulation (Read/Write) Lower-Limit Regulation (Read/Write) Analog Decimal Setting (Read/Write) PID Parameter Selection (Read/Write) SV Value (Read/Write) Alarm 1 Type (Read/Write) (See Note 3) Alarm 2 Type (Read/Write) (See Note 3) Alarm 3 Type (Read/Write) (See Note 3) Upper-Limit Alarm 1 (Read/Write) Lower-Limit Alarm 1 (Read/Write) Upper-Limit Alarm 2 (Read/Write) Lower-Limit Alarm 2 (Read/Write) Upper-Limit Alarm 3 (Read/Write) Lower-Limit Alarm 3 (Read/Write) Setting Lock Status (Read/Write) (See Note 4) BACnet Object Type AI AV AI AI AV BACnet Object ID 1 2 3 4 5 N2 Data Type AI AO AI AI AO N2 Point Address 1 2 3 4 5 nvoProcVal_XXX nvi/nvoSetpoint_XXX nvoUpLmTpRng_XXX nvoLoLmTpRng_XXX nvi/nvoCtrlMethd_XXX SNVT_count_inc_f SNVT_count_inc_f SNVT_count_inc_f SNVT_count_inc_f SNVT_count_inc_f AV AV AV AV AV 6 7 8 9 10 AO AO AO AO AO 6 7 8 9 10 nvi/nvoPB_PrpBnd_XXX nvi/nvoTiIntegTm_XXX nvi/nvoTdDerTime_XXX nvi/nvoOutputVal_XXX nvi/nvoUpLimReg_XXX SNVT_count_inc_f SNVT_count_inc_f SNVT_count_inc_f SNVT_lev_percent SNVT_count_inc_f AV 11 AO 11 nvi/nvoLoLimReg_XXX SNVT_count_inc_f AV 12 AO 12 nvi/nvoAnaDecSet_XXX SNVT_count_inc_f AV 13 AO 13 nvi/nvoPIDPrmSel_XXX SNVT_count_inc_f AV AV 14 15 AO AO 14 15 nvi/nvoSVValue_XXX nvi/nvoAlm1Type_XXX SNVT_count_inc_f SNVT_count_inc_f AV 16 AO 16 nvi/nvoAlm2Type_XXX SNVT_count_inc_f AV 17 AO 17 nvi/nvoAlm3Type_XXX SNVT_count_inc_f AV AV AV AV AV AV AV 18 19 20 21 22 23 24 AO AO AO AO AO AO AO 18 19 20 21 22 23 24 nvi/nvoUpLimAlm1_XXX nvi/nvoLoLimAlm1_XXX nvi/nvoUpLimAlm2_XXX nvi/nvoLoLimAlm2_XXX nvi/nvoUpLimAlm3_XXX nvi/nvoLoLimAlm3_XXX nvi/nvoSetLkStat_XXX SNVT_count_inc_f SNVT_count_inc_f SNVT_count_inc_f SNVT_count_inc_f SNVT_count_inc_f SNVT_count_inc_f SNVT_count_inc_f Page 46 of 54 Lon Name Lon SNVT Harsco Patterson Kelley’s ProtoNode Startup Guide Communication Write-in Selection (See Note 5) Temp Unit Display Selection (Read/Write) (See Note 6) Control RUN/STOP Setting (Read/Write) (See Note 7) STOP Setting for PID (Read/Write) (See Note 8) Temp STOP for PID (Read/Write) (See Note 9) PV Unstable Re-initialize PV Value for Error 0002H Input Sensor Did Not Connect PV Value for error 0003H Input Signal Error PV Value for Error 0004H Over Input Range ADC Fail PV Value for Error 0006H EEPROM Read/Write error AI 25 AI 25 nvoComWrinSl_XXX SNVT_count_inc_f BV 26 DO 26 nvi/nvoTmpUnit_XXX SNVT_switch BV 27 DO 27 nvi/nvoCtrRnStSt_XXX SNVT_switch BV 28 DO 28 nvi/nvoStpSetPID_XXX SNVT_switch BV 29 DO 29 nvi/nvoTmpStpPID_XXX SNVT_switch AI AI AI AI AI AI AI AI AI AI AI 30 31 32 33 34 35 36 37 38 39 40 AI AI AI AI AI AI AI AI AI AI AI 30 31 32 33 34 35 36 37 38 39 40 nvoPV_Unstbl_XXX nvoRe_init_XXX nvoPVValEr2H_XXX nvoInSnNoCnc_XXX nvoPVValEr3H_XXX nvoInSigErr_XXX nvoPVValEr4H_XXX nvoOvrInRng_XXX nvoADC_Fail_XXX nvoPVValEr6H_XXX nvoEEPROMErr_XXX SNVT_count_inc_f SNVT_count_inc_f SNVT_count_inc_f SNVT_count_inc_f SNVT_count_inc_f SNVT_count_inc_f SNVT_count_inc_f SNVT_count_inc_f SNVT_count_inc_f SNVT_count_inc_f SNVT_count_inc_f NOTES: 1) “Process Value” Codes: XXX.X=actual value; 8002H=initial process; 8003H=temperature sensor is not connected; 8004H=temperature sensor input error; 8006H=Cannot get temperature value. ADC input error; 8007H=Memory read/write error. 2) “Control Mode” Codes: 0=PID; 1=On/Off; 2=manual tuning; 3=PID program control 3) “Alarm Types” Codes: 0=alarm function disabled; 1=deviation upper- and lower-limit; 2=deviation upper-limit; 3=deviation lower-limit; 4=reverse deviation upper- and lower-limit; 5=absolute value upper- and lower-limit; 6=absolute value upper-limit; 7=absolute value lower-limit; 8=deviation upper- and lower-limit with standby sequence; 9=deviation upper-limit with standby sequence; 10=deviation lower-limit with standby sequence; 11=hysteresis upper-limit alarm output; 12=hysteresis lower-limit alarm output; and 13=CT alarm output 4) “Setting Lock Status” Codes: 0=normal; 1=all setting lock; 11=lock others than SV value 5) “Communication Write In” Codes: 0=disabled; 1=enabled 6) “Temperature Unit Display Selection” Codes: 0=⁰F; 1=⁰C 7) “Control RUN/STOP Setting” Codes: 0=STOP; 1=RUN 8) “STOP setting for PID program control” Codes: 0=RUN; 1=STOP 9) “Temporary STOP for PID program control” Codes: 0=RUN; 1=temporary STOP Page 47 of 54 Harsco Patterson Kelley’s ProtoNode Startup Guide Appendix B.3. Nuro Modbus RTU Mappings to BACnet MS/TP, BACnet/IP, Metasys N2 and LonWorks Point Name Supply Temperature Return Temperature Stack Temperature DHW Temperature Header Temperature HX Temperature ODA Temperature Filtered Extra Field Temperature Wireless Temperature Analog Input Analog Output Burner Control Digital I/O (See Note 1) Burner Control Digital I/O 2 (See Note 2) CH Mode Active Setpoint DHW Mode Active Setpoint Demand Source (See Note 3) Active Demand Status (See Note 4) Boiler State (See Note 5) Flame Signal Fan Speed Firing Rate Error Code Error Type (See Note 6) Burner Control Cycle Count Burner Control Run Hours CH Boiler Control (Read/Write) BMS CH Setpoint (Read/Write) BMS CH Demand (Read/Write) DHW Boiler Control (Read/Write) BACnet Object Type AI AI AI AI AI AI AI AI AI AI AI AI BACnet Object ID 1 2 3 4 5 6 7 8 9 10 11 12 N2 Data Type AI AI AI AI AI AI AI AI AI AI AI AI N2 Point Address 1 2 3 4 5 6 7 8 9 10 11 12 nvoSupplyTmp_XXX nvoReturnTmp_XXX nvoStackTmp_XXX nvoDHWTmp_XXX nvoHeaderTmp_XXX nvoHXTmp_XXX nvoODATmpFlt_XXX nvoExtFldTmp_XXX nvoWirlssTmp_XXX nvoAnaInput_XXX nvoAnaOutput_XXX nvoBrnCtDgIO_XXX SNVT_temp_p SNVT_temp_p SNVT_temp_p SNVT_temp_p SNVT_temp_p SNVT_temp_p SNVT_temp_p SNVT_temp_p SNVT_temp_p SNVT_count_f SNVT_count_f SNVT_count_f AI 13 AI 13 nvoBrCtDgIO2_XXX SNVT_count_f AI AI AI AI 14 15 16 17 AI AI AI AI 14 15 16 17 nvoCHMdActSP_XXX nvoDHWMdAcSP_XXX nvoDmdSrc_XXX nvoActDmdSt_XXX SNVT_temp_p SNVT_temp_p SNVT_count_f SNVT_count_f AI AI AI AI AI AI AI AI BV AV BV BV 18 19 20 21 22 23 24 25 26 27 28 29 AI AI AI AI AI AI AI AI DO AO DO DO 18 19 20 21 22 23 24 25 26 27 28 29 nvoBlrState_XXX nvoFlameSig_XXX nvoFanSpeed_XXX nvoFirRate_XXX nvoErrCode_XXX nvoErrType_XXX nvoBrCtrCyCt_XXX nvoBrCtrRnHr_XXX nvi/nvoCHBlrCtrl_XXX nvi/nvoBMSCHSP_XXX nvi/nvoBMSCHDmd_XXX nvi/nvoDHWBlCtrl_XXX SNVT_count_f SNVT_count_f SNVT_count_f SNVT_lev_percent SNVT_count_f SNVT_count_f SNVT_count_f SNVT_time_hour SNVT_switch SNVT_temp_p SNVT_switch SNVT_switch Page 48 of 54 Lon Name Lon SNVT Harsco Patterson Kelley’s ProtoNode Startup Guide BMS DHW Setpoint (Read/Write) BMS DHW Tank Setpoint (Read/Write) AV AV 30 31 AO AO 30 31 nvi/nvoBMSDHWSP_XXX nvi/nvoBMDHWTkSP_XXX SNVT_temp_p SNVT_temp_p NOTES: 1) “Burner Control Digital I/O” Codes: Bit Map:15=safety relay, 14=night setback input, 13=enable, 12=undefined, 11=undefined, 10=limit control circuit, 9=damper end switch input, 8=interlock control circuit, 7=alarm relay on, 6=undefined, 5=gas valve open, 4=external ignition on, 3=Relay D on, 2=Relay C on, 1=Relay B on, 0=Relay A on 2) “Burner Control Digital I/O 2” Codes: Bit Map:15-8= undefined, 7=auxiliary input 2, 6=high gas pressure, 5=high temperature limit, 4=low water cutoff, 3=auxiliary input 1, 2=start interlock 2, 1=start interlock 1, 0=air switch 3) “Demand Source” Codes: 0=none; 1=CHl; 2=DHW; 3=freze protection; 4=manual; 5=CH & DHW; 6=DHW & CH 4) “Active Demand Status” Codes: 0=normal; 1=system pump pre-pump; 2=system pump post-pump; 3=CH pump pre-pump; 4=CH pump post-pump; 5=tank pump pre-pump; 6=tank pump post-pump; 7=DHW pump pre-pump; 8=DHW pump post-pump; 9=waiting anti-cycle; 10=mod back max temp; 11=low fire hold; 12=limit time to high fire; 13=limit accelerate; 14=limit decelerate; 15=waiting for mode demand; 16=waiting for boiler to start; 17=CH pump running; 18=system pump running; 19=DHW pump running; 20=tank pump running 5) “Boiler State” Codes: 0=waiting for communication; 1=standby; 2=lockout; 3=hold; 4=waiting for air switch close; 5=waiting for air switch open; 6=opening damper; 7=waiting for damper to open; 8=pre-purge; 9=post purge; 10=run; 11=mod back delta temp; 12=mod back max temp; 13=mod back stack temp; 14=pre-ignition; 15=ignition; 16=mod back delta temp exceeded; 17=mod back max temp exceeded; 18=mod back stack temp exceeded; 19=rate modified by air switch; 20=rate modified by outlet temperature; 21=rate modified by delta limit; 22=rate modified by stack limit; 23=starting; 24=fan only; 25=stopping 6) “Error Type” Codes: 0=no error; 1=lockout; 2=boiler hold; 3=mode hold; 4=alert caused alarm Page 49 of 54 Harsco Patterson Kelley’s ProtoNode Startup Guide Appendix C. “A” Bank DIP Switch Settings Appendix C.1. “A” Bank DIP Switch Settings Address A0 A1 A2 A3 A4 A5 A6 A7 Address A0 A1 A2 A3 A4 A5 A6 A7 1 On Off Off Off Off Off Off Off 46 Off On On On Off On Off Off 2 Off On Off Off Off Off Off Off 47 On On On On Off On Off Off 3 On On Off Off Off Off Off Off 48 Off Off Off Off On On Off Off 4 Off Off On Off Off Off Off Off 49 On Off Off Off On On Off Off 5 On Off On Off Off Off Off Off 50 Off On Off Off On On Off Off 6 Off On On Off Off Off Off Off 51 On On Off Off On On Off Off 7 On On On Off Off Off Off Off 52 Off Off On Off On On Off Off 8 Off Off Off On Off Off Off Off 53 On Off On Off On On Off Off 9 On Off Off On Off Off Off Off 54 Off On On Off On On Off Off 10 Off On Off On Off Off Off Off 55 On On On Off On On Off Off 11 On On Off On Off Off Off Off 56 Off Off Off On On On Off Off 12 Off Off On On Off Off Off Off 57 On Off Off On On On Off Off 13 On Off On On Off Off Off Off 58 Off On Off On On On Off Off 14 Off On On On Off Off Off Off 59 On On Off On On On Off Off 15 On On On On Off Off Off Off 60 Off Off On On On On Off Off 16 Off Off Off Off On Off Off Off 61 On Off On On On On Off Off 17 On Off Off Off On Off Off Off 62 Off On On On On On Off Off 18 Off On Off Off On Off Off Off 63 On On On On On On Off Off 19 On On Off Off On Off Off Off 64 Off Off Off Off Off Off On Off 20 Off Off On Off On Off Off Off 65 On Off Off Off Off Off On Off 21 On Off On Off On Off Off Off 66 Off On Off Off Off Off On Off 22 Off On On Off On Off Off Off 67 On On Off Off Off Off On Off 23 On On On Off On Off Off Off 68 Off Off On Off Off Off On Off 24 Off Off Off On On Off Off Off 69 On Off On Off Off Off On Off 25 On Off Off On On Off Off Off 70 Off On On Off Off Off On Off 26 Off On Off On On Off Off Off 71 On On On Off Off Off On Off 27 On On Off On On Off Off Off 72 Off Off Off On Off Off On Off 28 Off Off On On On Off Off Off 73 On Off Off On Off Off On Off 29 On Off On On On Off Off Off 74 Off On Off On Off Off On Off 30 Off On On On On Off Off Off 75 On On Off On Off Off On Off 31 On On On On On Off Off Off 76 Off Off On On Off Off On Off 32 Off Off Off Off Off On Off Off 77 On Off On On Off Off On Off 33 On Off Off Off Off On Off Off 78 Off On On On Off Off On Off 34 Off On Off Off Off On Off Off 79 On On On On Off Off On Off 35 On On Off Off Off On Off Off 80 Off Off Off Off On Off On Off 36 Off Off On Off Off On Off Off 81 On Off Off Off On Off On Off 37 On Off On Off Off On Off Off 82 Off On Off Off On Off On Off 38 Off On On Off Off On Off Off 83 On On Off Off On Off On Off 39 On On On Off Off On Off Off 84 Off Off On Off On Off On Off 40 Off Off Off On Off On Off Off 85 On Off On Off On Off On Off 41 On Off Off On Off On Off Off 86 Off On On Off On Off On Off 42 Off On Off On Off On Off Off 87 On On On Off On Off On Off 43 On On Off On Off On Off Off 88 Off Off Off On On Off On Off 44 Off Off On On Off On Off Off 89 On Off Off On On Off On Off 45 On Off On On Off On Off Off 90 Off On Off On On Off On Off Page 50 of 54 Harsco Patterson Kelley’s ProtoNode Startup Guide Address A0 A1 A2 A3 A4 A5 A6 A7 Address A0 A1 A2 A3 A4 A5 A6 A7 91 On On Off On On Off On Off 139 On On Off On Off Off Off On 92 Off Off On On On Off On Off 140 Off Off On On Off Off Off On 93 On Off On On On Off On Off 141 On Off On On Off Off Off On 94 Off On On On On Off On Off 142 Off On On On Off Off Off On 95 On On On On On Off On Off 143 On On On On Off Off Off On 96 Off Off Off Off Off On On Off 144 Off Off Off Off On Off Off On 97 On Off Off Off Off On On Off 145 On Off Off Off On Off Off On 98 Off On Off Off Off On On Off 146 Off On Off Off On Off Off On 99 On On Off Off Off On On Off 147 On On Off Off On Off Off On 100 Off Off On Off Off On On Off 148 Off Off On Off On Off Off On 101 On Off On Off Off On On Off 149 On Off On Off On Off Off On 102 Off On On Off Off On On Off 150 Off On On Off On Off Off On 103 On On On Off Off On On Off 151 On On On Off On Off Off On 104 Off Off Off On Off On On Off 152 Off Off Off On On Off Off On 105 On Off Off On Off On On Off 153 On Off Off On On Off Off On 106 Off On Off On Off On On Off 154 Off On Off On On Off Off On 107 On On Off On Off On On Off 155 On On Off On On Off Off On 108 Off Off On On Off On On Off 156 Off Off On On On Off Off On 109 On Off On On Off On On Off 157 On Off On On On Off Off On 110 Off On On On Off On On Off 158 Off On On On On Off Off On 111 On On On On Off On On Off 159 On On On On On Off Off On 112 Off Off Off Off On On On Off 160 Off Off Off Off Off On Off On 113 On Off Off Off On On On Off 161 On Off Off Off Off On Off On 114 Off On Off Off On On On Off 162 Off On Off Off Off On Off On 115 On On Off Off On On On Off 163 On On Off Off Off On Off On 116 Off Off On Off On On On Off 164 Off Off On Off Off On Off On 117 On Off On Off On On On Off 165 On Off On Off Off On Off On 118 Off On On Off On On On Off 166 Off On On Off Off On Off On 119 On On On Off On On On Off 167 On On On Off Off On Off On 120 Off Off Off On On On On Off 168 Off Off Off On Off On Off On 121 On Off Off On On On On Off 169 On Off Off On Off On Off On 122 Off On Off On On On On Off 170 Off On Off On Off On Off On 123 On On Off On On On On Off 171 On On Off On Off On Off On 124 Off Off On On On On On Off 172 Off Off On On Off On Off On 125 On Off On On On On On Off 173 On Off On On Off On Off On 126 Off On On On On On On Off 174 Off On On On Off On Off On 127 On On On On On On On Off 175 On On On On Off On Off On 128 Off Off Off Off Off Off Off On 176 Off Off Off Off On On Off On 129 On Off Off Off Off Off Off On 177 On Off Off Off On On Off On 130 Off On Off Off Off Off Off On 178 Off On Off Off On On Off On 131 On On Off Off Off Off Off On 179 On On Off Off On On Off On 132 Off Off On Off Off Off Off On 180 Off Off On Off On On Off On 133 On Off On Off Off Off Off On 181 On Off On Off On On Off On 134 Off On On Off Off Off Off On 182 Off On On Off On On Off On 135 On On On Off Off Off Off On 183 On On On Off On On Off On 136 Off Off Off On Off Off Off On 184 Off Off Off On On On Off On 137 On Off Off On Off Off Off On 185 On Off Off On On On Off On 138 Off On Off On Off Off Off On 186 Off On Off On On On Off On Page 51 of 54 Harsco Patterson Kelley’s ProtoNode Startup Guide Address A0 A1 A2 A3 A4 A5 A6 A7 Address A0 A1 A2 A3 A4 A5 A6 A7 187 On On Off On On On Off On 235 On On Off On Off On On On 188 Off Off On On On On Off On 236 Off Off On On Off On On On 189 On Off On On On On Off On 237 On Off On On Off On On On 190 Off On On On On On Off On 238 Off On On On Off On On On 191 On On On On On On Off On 239 On On On On Off On On On 192 Off Off Off Off Off Off On On 240 Off Off Off Off On On On On 193 On Off Off Off Off Off On On 241 On Off Off Off On On On On 194 Off On Off Off Off Off On On 242 Off On Off Off On On On On 195 On On Off Off Off Off On On 243 On On Off Off On On On On 196 Off Off On Off Off Off On On 244 Off Off On Off On On On On 197 On Off On Off Off Off On On 245 On Off On Off On On On On 198 Off On On Off Off Off On On 246 Off On On Off On On On On 199 On On On Off Off Off On On 247 On On On Off On On On On 200 Off Off Off On Off Off On On 248 Off Off Off On On On On On 201 On Off Off On Off Off On On 249 On Off Off On On On On On 202 Off On Off On Off Off On On 250 Off On Off On On On On On 203 On On Off On Off Off On On 251 On On Off On On On On On 204 Off Off On On Off Off On On 252 Off Off On On On On On On 205 On Off On On Off Off On On 253 On Off On On On On On On 206 Off On On On Off Off On On 254 Off On On On On On On On 255 On On On On On On On On 207 On On On On Off Off On On 208 Off Off Off Off On Off On On 209 On Off Off Off On Off On On 210 Off On Off Off On Off On On 211 On On Off Off On Off On On 212 Off Off On Off On Off On On 213 On Off On Off On Off On On 214 Off On On Off On Off On On 215 On On On Off On Off On On 216 Off Off Off On On Off On On 217 On Off Off On On Off On On 218 Off On Off On On Off On On 219 On On Off On On Off On On 220 Off Off On On On Off On On 221 On Off On On On Off On On 222 Off On On On On Off On On 223 On On On On On Off On On 224 Off Off Off Off Off On On On 225 On Off Off Off Off On On On 226 Off On Off Off Off On On On 227 On On Off Off Off On On On 228 Off Off On Off Off On On On 229 On Off On Off Off On On On 230 Off On On Off Off On On On 231 On On On Off Off On On On 232 Off Off Off On Off On On On 233 On Off Off On Off On On On 234 Off On Off On Off On On On Page 52 of 54 Harsco Patterson Kelley’s ProtoNode Startup Guide Appendix D. Reference Appendix D.1. Specifications ProtoNode FPC-N34 Electrical Connections Approvals: ProtoNode FPC-N35 One 6-pin Phoenix connector with: One 6-pin Phoenix connector with: RS-485 port (+ / - / gnd) RS-485 port (+ / - / gnd) Power port (+ / - / Frame-gnd) Power port (+ / - / Frame-gnd) One 3-pin Phoenix connector with: One Ethernet 10/100BaseT port RS-485 port (+ / - / gnd) One FTT-10 LonWorks port One Ethernet 10/100BaseT port CE Certified; TUV approved to UL 916, EN 60950-1, EN 50491-3 and CSA C22-2 standards; FCC Class A Part 15; DNP3 Conformance Tested; OPC Self-tested for Compliance; RoHS Compliant; CSA 205 Approved BTL Marked LonMark Certified Power Multi-mode power adapter: 9-30VDC or 12 - 24VAC Requirements Physical 11.5 cm L x 8.3 cm W x 4.1 cm H (4.5 x 3.2 x 1.6 in.) Dimensions Weight: 0.2 kg (0.4 lbs) Operating -40°C to 75°C (-40°F to167°F) Temperature: Surge EN61000-4-2 ESD EN61000-4-3 EMC EN61000-4-4 EFT Suppression Humidity: 5 - 90% RH (non-condensing) (Specifications subject to change without notice) Figure 36: Specifications Appendix D.1.1. Compliance with UL Regulations For UL compliance, the following instructions must be met when operating ProtoNode. The units shall be powered by listed LPS or Class 2 power supply suited to the expected operating temperature range. The interconnecting power connector and power cable shall: Comply with local electrical code. Be suited to the expected operating temperature range. Meet the current and voltage rating for ProtoNode/Net Furthermore, the interconnecting power cable shall: Be of length not exceeding 3.05m (118.3”) Be constructed of materials rated VW-1 or FT-1 or better If the unit is to be installed in an operating environment with a temperature above 65 °C, it should be installed in a Restricted Access Area requiring a key or a special tool to gain access This device must not be connected to a LAN segment with outdoor wiring. Page 53 of 54 Harsco Patterson Kelley’s ProtoNode Startup Guide Appendix E. Limited 2 Year Warranty Sierra Monitor Corporation warrants its products to be free from defects in workmanship or material under normal use and service for two years after date of shipment. Sierra Monitor Corporation will repair or replace any equipment found to be defective during the warranty period. Final determination of the nature and responsibility for defective or damaged equipment will be made by Sierra Monitor Corporation personnel. All warranties hereunder are contingent upon proper use in the application for which the product was intended and do not cover products which have been modified or repaired without Sierra Monitor Corporation’s approval or which have been subjected to accident, improper maintenance, installation or application, or on which original identification marks have been removed or altered. This Limited Warranty also will not apply to interconnecting cables or wires, consumables or to any damage resulting from battery leakage. In all cases Sierra Monitor Corporation’s responsibility and liability under this warranty shall be limited to the cost of the equipment. The purchaser must obtain shipping instructions for the prepaid return of any item under this warranty provision and compliance with such instruction shall be a condition of this warranty. Except for the express warranty stated above, Sierra Monitor Corporation disclaims all warranties with regard to the products sold hereunder including all implied warranties of merchantability and fitness and the express warranties stated herein are in lieu of all obligations or liabilities on the part of Sierra Monitor Corporation for damages including, but not limited to, consequential damages arising out of/or in connection with the use or performance of the product. Page 54 of 54
© Copyright 2024