ProtoNode FPC-N34 and FPC-N35 · 2016. 1. 5. · BACnet MS/TP or BACnet/IP: Assigning Specific Device Instances • With the default Node_Offset value of 50,000 the Device Instances

Installation and Service Instructions for Contractors

6720

8184

52 (2

015/1

0) U

S

3.4

ProtoNode FPC-N34 and FPC-N35FOR BUDERUS SSB BOILERS

6720818452 (2015/10) US ProtoNode

2 |

Contents

1 Key to symbols and safety instructions . . . . . . . . . . . . . . 31.1 Key to symbols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3

2 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42.1 ProtoNode Gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4

3 BACnet/LonWorks setup for protocessor ProtoNode FPC-N34/FPC-N35 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53.1 Record Identification Data . . . . . . . . . . . . . . . . . . . . . . . . .53.2 Point Count Capacity and Registers per Controller . . . . . .53.3 Configuring Controller Communications. . . . . . . . . . . . . . .53.3.1 Set Modbus COM setting on all of the Controllers

connected to the ProtoNode. . . . . . . . . . . . . . . . . . . . . . . .53.3.2 Set Modbus RTU Node-ID for each of the Controllers

attached to the ProtoNode . . . . . . . . . . . . . . . . . . . . . . . . .53.4 Selecting the Desired Field Protocol and Enabling

Auto-Discovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .53.4.1 Selecting Desired Field Protocol . . . . . . . . . . . . . . . . . . .53.4.2 Enabling Auto-Discovery . . . . . . . . . . . . . . . . . . . . . . . . .53.5 BMS (Building Management System) Network Settings:

MAC Address, Device Instance and Baud Rate. . . . . . . . .63.5.1 BACnet MS/TP (FPC-N34): Setting the MAC Address

for BMS (Building Management System) Network . . . . . .63.5.2 BACnet MS/TP and BACnet/IP (FPC-N34): Setting the

Device Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .63.5.3 Metasys N2 or Modbus TCP/IP (FPC-N34): Setting the

Node-ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .63.5.4 BACnet MS/TP (FPC-N34): Setting the Baud Rate for

BMS (Building Management System) Network . . . . . . . . .6

4 Interfacing ProtoNode to controllers . . . . . . . . . . . . . . . . 74.1 Showing internal board. . . . . . . . . . . . . . . . . . . . . . . . . . . .74.2 Controller Connections to ProtoNode. . . . . . . . . . . . . . . . .94.2.1 Biasing the Modbus RS-485 Device Network . . . . . . . . . .94.2.2 End of Line Termination Switch for the Modbus RS-485

Device Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .94.3 BACnet MS/TP or Metasys N2 (FPC-N34): Wiring Field

Port to RS-485 BMS (Building Management System) Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10

4.4 LonWorks (FPC-N35): Wiring Field Port to LonWorks Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10

4.5 Power-Up ProtoNode . . . . . . . . . . . . . . . . . . . . . . . . . . .10

5 Power-Up ProtoNode . . . . . . . . . . . . . . . . . . . . . . . . . .115.1 Auto-Discovery: After Completion – Turn Off to Save

Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11

6 BACnet/IP or Modbus TCP/IP: change the ProtoNode IP address 126.1 Instructions to Download XIF File from ProtoNode

FPC-N35 Using Browser . . . . . . . . . . . . . . . . . . . . . . . . .126.2 BACnet/IP and Modbus TCP/IP: Setting IP Address for

Field Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14

7 BACnet MS/TP and BACnet/IP: setting node_offset to assign specific device instances . . . . . . . . . . . . . . . . . . . . . . .16

8 How to start the installation over: clearing profiles . . . . . . .17

9 LonWorks (FPC-N35): commissioning ProtoNode on a LonWorks network . . . . . . . . . . . . . . . . . . . . . . . . . . .179.1 Commissioning ProtoNode FPC-N35 on a LonWorks

Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .179.2 Instructions to Upload XIF File from ProtoNode

FPC-N35 Using Browser . . . . . . . . . . . . . . . . . . . . . . . . .17

10 CAS BACnet explorer for validating ProtoNode in the field . .1810.1 Downloading the CAS Explorer and Requesting an

Activation Key. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1810.2 CAS BACnet Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1910.2.1 CAS BACnet MS/ST Setup . . . . . . . . . . . . . . . . . . . . . . .1910.2.2 CAS BACnet BACnet/IP Setup. . . . . . . . . . . . . . . . . . . . .19

11 Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1911.1 Viewing Diagnostic information . . . . . . . . . . . . . . . . . . . .1911.2 Appendix A.2. Check Wiring and Settings . . . . . . . . . . . .2011.3 Appendix A.3. Take Diagnostic Capture With the

FieldServer Toolbox . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2011.4 Appendix A.4. BACnet: Setting Network_Number for

more than one ProtoNode on Subnet. . . . . . . . . . . . . . . .2211.5 Appendix A.4. LED Diagnostics for Modbus RTU

Communications Between ProtoNode and Controllers . .2311.6 Appendix A.5. Passwords. . . . . . . . . . . . . . . . . . . . . . . . .23

12 Appendix B . Vendor Information – Fontecal_Bosch . . . . . . .2412.1 Appendix B.1 SSB Modbus RTU Mappings to BACnet

MS/TP, BACnet/IP, Metasys N2 and LonWorks . . . . . . . .24

13 Appendix C . “A” Bank DIP Switch Settings . . . . . . . . . . . .2713.1 Appendix C.1 “A” Bank DIP Switch Settings . . . . . . . . . .27

14 Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3014.1 Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3014.1.1 Compliance with UL Regulations . . . . . . . . . . . . . . . . . . .30

15 Limited 2 Year Warranty . . . . . . . . . . . . . . . . . . . . . . . .30

16 Certifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30

ProtoNode 6720818452 (2015/10) US

Key to symbols and safety instructions | 3

1 Key to symbols and safety instructions

1 .1 Key to symbolsWarnings

aaWarnings in this document are identified by a warning triangle printed against a grey background.Keywords at the start of a warning indicate the type and seriousness of the ensuing risk if measures to prevent the risk are not taken.

The following keywords are defined and can be used in this document:• DANGER indicates a hazardous situation which, if not avoided, will

result in death or serious injury.• WARNING indicates a hazardous situation which, if not avoided,

could result in death or serious injury.• CAUTION indicates a hazardous situation which, if not avoided,

could result in minor to moderate injury.• NOTICE is used to address practices not related to personal injury.

Important information

amThis symbol indicates important information where there is no risk to people or property.

6720818452 (2015/10) US ProtoNode

4 | Introduction

2 Introduction

2 .1 ProtoNode GatewayProtoNode is an external, high performance Building Automation multi-protocol gateway that is preconfigured to Auto-Discover any of the Bosch’s products (hereafter called “controller”) connected to the ProtoNode and automatically configures them for BACnet® MS/TP, BACnet/IP (*), Metasys® (**) N2 by JCI, Modbus TCP/IP or LonWorks® (***) .

(*) BACnet is a registered trademark of ASHRAE(**) Metasys is a registered trademark of Johnson Controls Inc.(***) LonWorks is a registered trademark of Echelon Corporation

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.

Fig. 1 ProtoNode Connectivity Layout Diagram

RS-485 Field Protocol

One or multipleEthernet Field

Protocols

One or multipleSerial Devices

Controller “A”

Controller “B”

Controller “C”

Controller “D”

Aut

o-D

isco

very

ProtoNode 6720818452 (2015/10) US

BACnet/LonWorks setup for protocessor ProtoNode FPC-N34/FPC-N35 | 5

3 BACnet/LonWorks setup for protocessor ProtoNode FPC-N34/FPC-N35

3 .1 Record Identification DataEach ProtoNode has a unique part number located on the side or the back of the unit. This number should be recorded, as it may be required for technical support. The numbers are as follows:

Model Part NumberProtoNode N34, Level 1 FPC-N34-1042ProtoNode N35, Level 1 FPC-N35-1043

Tab. 1 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

3 .2 Point Count Capacity and Registers per ControllerThe total number of Modbus Registers presented by all of the controllers attached to the ProtoNode cannot exceed:

Part number Total RegistersFPC-N34-1042, Level 1 1,500FPC-N35-1043, Level 1 1,500

Tab. 2 Supported Point Count Capacity

Controllers Registers Per ControllerSSB 143

Tab. 3 Modbus Registers per Controller

3 .3 Configuring Controller Communications3 .3 .1 Set Modbus COM setting on all of the Controllers connected

to the ProtoNode

• All of the Serial controllers connected to ProtoNode MUST have the same Baud Rate, Data Bits, Stop Bits, and Parity settings.

• Tab. 4 specifies the controller serial port settings required to communicate with the ProtoNode.

Serial Port Setting ControllerProtocol Modbus RTU

Baud Rate 9600Parity None

Data Bits 8Stop Bits 1

Tab. 4 Modbus RTU COM Settings

3 .3 .2 Set Modbus RTU Node-ID for each of the Controllers attached to the ProtoNode

► Set Modbus Node-ID for each of the controllers 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 controller needs to be

documented. - The Modbus Node-ID’s assigned are used for designating the

Controller Instance for BACnet/IP and BACnet MS/TP (Section 3.5.2)

► The Metasys N2 and Modbus TCP/IP Node-ID will be set to same value as the Node-ID of the Modbus RTU controller.

3 .4 Selecting the Desired Field Protocol and Enabling Auto-Discovery

3 .4 .1 Selecting Desired Field Protocol ► ProtoNode FPC-N34 units use the “S” bank of DIP switches (S0 – S2) to select the Field Protocol.

• See the Tab. 5 for the switch settings to select BACnet MS/TP, BACnet/IP, Modbus TCP/IP, or Metasys N2.

• The OFF position is when the 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.

• On ProtoNode FPC-N35 units, these switches are disabled; the Field Protocol is always LonWorks.

Fig. 2 S0 – S3 DIP Switches & S Bank DIP Switch Location

ProtoNode FPC-N34 S Bank DIP SwitchesProfile S0 S1 S2

BACnet/IP Off Off OffBACnet MS/TP On Off Off

Metasys N2 Off On OffModbus TCP/IP On On Off

Tab. 5 BACnet MS/TP, BACnet/IP, Modbus TCP/IP, and Metasys N2 Settings for ProtoNode FPC-N34 (BACnet)

3 .4 .2 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 Tab. 6 for the 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.

S3 DIP Switch Auto-Discovery Mode S3Auto-Discovery ON – Build New Configuration On

Auto-Discover OFF – Save Current Configuration OffTab. 6 S3 DIP Switch setting for Auto Discovering Devices

S0 S1 S2 S3

6720818452 (2015/10) US ProtoNode

6 | BACnet/LonWorks setup for protocessor ProtoNode FPC-N34/FPC-N35

3 .5 BMS (Building Management System) Network Settings: MAC Address, Device Instance and Baud Rate

3 .5 .1 BACnet MS/TP (FPC-N34): Setting the MAC Address for BMS (Building Management System) 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 (Building Management System) Front End can find the ProtoNode, via BACnet auto discovery.

amNever 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 (Building Management System) Front Ends that support auto discovery of BACnet MS/TP devices.

Fig. 3 A0 – A7 DIP Switches

• 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.

amWhen setting DIP Switches, please ensure that power to the board is OFF.

3 .5 .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 6.2).

• The BACnet Device Instance can range from 1 to 4,194,303.• To assign specific Device Instance values, change the Node_Offset

value. (Section 7)

For example: - Node_Offset value (default) = 50,000 - Controller 1 has a Modbus Node-ID of 1 - Controller 2 has a Modbus Node-ID of 22 - Controller 3 has a Modbus Node-ID of 33 - Given that: Controller Instance = Node_Offset + Modbus

Node_ID - Controller Instance, Controller 1 = 50,000 + 1 = 50,001 - Controller Instance, Controller 2 = 50,000 + 22 = 50,022 - Controller Instance, Controller 3 = 50,000 + 33 = 50,033

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.

• For changing the Node_Offset value are provided in Section 6.2• This step cannot be performed until after the unit is connected and

powered.

3 .5 .3 Metasys N2 or Modbus TCP/IP (FPC-N34): Setting the Node-ID

• The Modbus RTU Node-ID’s assigned to the controllers attached to the ProtoNode in Section 6.2 will be the Metasy N2 or Modbus TCP/IP Node_ID’s to 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.

3 .5 .4 BACnet MS/TP (FPC-N34): Setting the Baud Rate for BMS (Building Management System) Network

• “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).

Fig. 4 BMS (Building Management System) Baud Rate DIP Switches

Baud Rate DIP Switch Selection

Baud B0 B1 B2 B39600 On On On Off

19200 Off Off Off On38400* On On Off On57600 Off Off On On76800 On Off On On

* Factory default setting = 38,400Tab. 7 BMS (Building Management System) Baud Rate

A0 A1 A2 A3 A4 A5 A6 A7

B0 B1 B2 B3

ProtoNode 6720818452 (2015/10) US

Interfacing ProtoNode to controllers | 7

4 Interfacing ProtoNode to controllers

4 .1 Showing internal board

Fig. 5 ProtoNode FPC-N34

Run

Config Error

Node Offline

Heart Beat

“A” bank

“B” bank

“S” bank

RS-485 Bias jumper

SPL

RUNERR

RX

TX

PWRJumper DO NOT MOVE

PWR LED

Additional DIP switches(A1 & A2 enabled, other are disabled)

End of LineTerminal switch

RS-485+ - GND

LED: RS-485 Field RX/TX

RS-485 termination

jumper

Power 9-30 VDC12-24 VAC

RS-485+ - GND

Ethernet Port

LED

sLE

Ds

6720818452 (2015/10) US ProtoNode

8 | Interfacing ProtoNode to controllers

Fig. 6 ProtoNode FPC-N35

RunConfig Error

Node OfflineHeart Beat

“A” bank

“B” bank

“S” bank

RS-485 Bias jumper

SPL

RUN

ERRRX

TXPWR

Jumper - DO NOT MOVE

PWR LED

Additional DIP switches(A1 & A2 enabled, other are disabled)

LonWorks TX LEDLonWorks RXLED

RS-485+ - GND

LonWorksConnector

LonWorksLED

LonWorksService Pin

RS-485 termination

jumper

Power 9-30 VDC12-24 VAC

LED

sLE

Ds

Ethernet Port

ProtoNode 6720818452 (2015/10) US

Interfacing ProtoNode to controllers | 9

4 .2 Controller Connections to ProtoNodeProtoNode 6 Pin Phoenix connector for RS-485 Controllers• 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.

- 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).

Device Pins ProtoNode Pin # Pin assignmentPin RS-485 + Pin 1 RS-485 +Pin RS-485 - Pin 2 RS-485 -

Pin GND Pin 3 RS-485 GNDPower In (+) Pin 4 V +Power In (-) Pin 5 V -

Frame Ground Pin 6 FRAME GNDTab. 8 Power and RS-485 Connections

Fig. 7 RS-485 Connections

4 .2 .1 Biasing the Modbus RS-485 Device 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 Fig. 8/9).

• Only turn biasing ON: - IF the BMS (Building Management System) cannot see more

than one device connected to the ProtoNode . - AND you have checked all the settings (Modbus COM

settings, wiring, and DIP switches) .• 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.

Fig. 8 Modbus RS-485 Biasing Switch on the ProtoNode N34

Fig. 9 Modbus RS-485 Biasing Switch on the ProtoNode N35

4 .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) .

Fig. 10 Modbus RS-485 End-Of-Line Termination Switch on the ProtoNode N34

RS-485 + RS-485 -

RS-485 Bias jumper

RS-485 Bias jumper

Modbus RS-485 EOL Switch

Leave in A Position

6720818452 (2015/10) US ProtoNode

10 | Interfacing ProtoNode to controllers

Fig. 11 Modbus RS-485 End-Of-Line Termination Switch on the ProtoNode N35

4 .3 BACnet MS/TP or Metasys N2 (FPC-N34): Wiring Field Port to RS-485 BMS (Building Management System) Network

• Connect the BACnet MS/TP or Metasys N2 RS-485 network wires to the 3-pin RS-485 connector on ProtoNode FPC-N34 as shown below in Tab.9/Fig.12. - The RS-485 GND (Pin 3) is not typically connected.

• See Section 7 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 (Fig. 13). - 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 ProtoNode Pin # Pin AssignmentRS-485 + Pin 1 RS-485 +RS-485 - Pin 2 RS-485 -

- Pin 3 RS-485 GNDTab. 9 Connection from ProtoNode to RS-485 Field Network

Fig. 12 Connection from ProtoNode to RS-485 Field Network

Fig. 13 RS-485 BMS (Building Management System) Network EOL Switch

4 .4 LonWorks (FPC-N35): Wiring Field Port to LonWorks Network

• Connect ProtoNode to the field network with the LonWorks terminal using a twisted pair non-shielded cable. LonWorks has no polarity.

Fig. 14 LonWorks Terminal

4 .5 Power-Up ProtoNodeApply power to ProtoNode as show below in Tab. 11/Fig. 15. Ensure that the power supply used complies with the specifications provided in Section 14.1.• ProtoNode accepts either 9-30VDC or 12-24 VAC on pins 4 and 5.• Frame GND should be connected .

Power Requirement for ProtoNode External GatewayCurrent Draw Type

ProtoNode Family 12VDC/VAC 24VDC/VAC 30VDC

FPC – N34 (Typical) 170mA 100mA 80mA

FPC – N34 (Maximum) 240mA 140mA 100mA

FPC – N35 (Typical) 210mA 130mA 90mA

FPC – N35 (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.Tab. 10 Required current draw for the ProtoNode

Modbus RS-485 EOL Switch

Leave in A Position

RS-485 + RS-485 -

+ - G

End-of-Line Switch

ProtoNode 6720818452 (2015/10) US

Power-Up ProtoNode | 11

Power to ProtoNode ProtoNode Pin AssignmentPower In (+) Pin 4 V +Power In (-) Pin 5 V -

Frame Ground Pin 6 FRAME GNDTab. 11 Power Connections

Fig. 15 Power Connections

5 Power-Up ProtoNode

5 .1 Auto-Discovery: After Completion – Turn Off to Save Configuration

The S3 DIP Switch for Enabling Auto-Discovery should have been set in section 3.3.2 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 3 minutes to complete the discovery of all of the RS-485 devices attached to the ProtoNode.

• 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 FPC-N34 and FPC-N35S3 DIP Switch Auto-Discovery Mode S3

Auto-Discovery ON – Build New Configuration OnAuto-Discover OFF – Save Current Configuration Off

Tab. 12 S3 DIP Switch setting for Auto Discovering Devices

V + V - FRAME GND

6720818452 (2015/10) US ProtoNode

12 | BACnet/IP or Modbus TCP/IP: change the ProtoNode IP address

6 BACnet/IP or Modbus TCP/IP: change the ProtoNode IP address

6 .1 Instructions to Download XIF File from ProtoNode FPC-N35 Using Browser

► 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

FOR WINDOWS XP:

► Go to START and open Control Panel

Fig. 16 Start

Fig. 17 Control Panel

► Go to Network Connections

Fig. 18 Network Connections

► Right-click on Local Area Connection > Properties

Fig. 19 Local Area Connection

► Highlight Internet Protocol TCP/IP > Properties

Fig. 20 Local Area Connection Properties

ProtoNode 6720818452 (2015/10) US

BACnet/IP or Modbus TCP/IP: change the ProtoNode IP address | 13

FOR WINDOWS 7:

► Go to START and open Control Panel

Fig. 21 Start

Fig. 22 Control Panel

► Go to Network Connections

Fig. 23 Network Connections

► Right-click on Local Area Connection > Properties ► Highlight: Internet Protocol Version 4 (TCP/IPv4) > Properties

Fig. 24 Local Area Connection

FOR WINDOWS XP & WINDOWS 7

► Select: Use the following IP address

Fig. 25 Internet Protocol TCP/IP Properties

► Click OK twice

Fig. 26 Ok

6720818452 (2015/10) US ProtoNode

14 | BACnet/IP or Modbus TCP/IP: change the ProtoNode IP address

6 .2 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 6.2), 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. (Fig. 27) ► To access the FST Web GUI, click on the “Diagnostics & Debugging” button in the bottom right side of the page.

Fig. 27 Web Configurator screen with Active Profiles

amBelow the Active Profiles heading you should see profiles listed for connected devices. If no profiles are present, then the wiring, baud rate, and DIP switch settings must be checked, because there is a problem with device communications. All the active profiles must show the correct Node-ID’s before proceeding.

ProtoNode 6720818452 (2015/10) US

BACnet/IP or Modbus TCP/IP: change the ProtoNode IP address | 15

Fig. 28 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. (Fig. 28)

► 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

amIf 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 .

6720818452 (2015/10) US ProtoNode

16 | BACnet MS/TP and BACnet/IP: setting node_offset to assign specific device instances

7 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 6), 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. (Fig. 29)• 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.

- Given that: Node_Offset + Modbus Node_ID = Device InstanceFor example:

- Controller 1 has a Modbus Node-ID of 1 - Controller 2 has a Modbus Node-ID of 22 - Controller 3 has a Modbus Node-ID of 33 - Desired Controller Instance for 1st device = 1,001 - The Node_Offset value will be applied to all devices. - Controller 1 Instance will then be = 1,000 + Modbus Node_ID = 1,000 + 1 = 1,001 - Controller 2 Instance will then be = 1,000 + Modbus Node_ID = 1,000 + 22 = 1,022 - Controller 3 Instance will then be = 1,000 + Modbus Node_ID = 1,000 + 33 = 1,033

Fig. 29 Web Configurator screen

ProtoNode 6720818452 (2015/10) US

How to start the installation over: clearing profiles | 17

8 How to start the installation over: clearing profiles

• After setting your PC to be on the same subnet as the ProtoNode (Section 6), 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.

9 LonWorks (FPC-N35): commissioning ProtoNode on a LonWorks network

Commissioning may only be performed by the LonWorks administrator .

9 .1 Commissioning ProtoNode FPC-N35 on a LonWorks 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 9.2 to generate XIF

Fig. 30 LonWorks Service Pin Location

9 .2 Instructions to Upload XIF File from ProtoNode FPC-N35 Using Browser

• Connect the PC to ProtoNode via the Ethernet Port• 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

Fig. 31 Sample of Fserver.XIF File Being Generated

6720818452 (2015/10) US ProtoNode

18 | CAS BACnet explorer for validating ProtoNode in the field

10 CAS BACnet explorer for validating ProtoNode in the fieldSierra Monitor Corporation 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 (Building Management System) Integrator on site. A Serial or USB to RS-485 converter is needed to test BACnet MS/TP.

10 .1 Downloading the CAS Explorer and Requesting an Activation KeyTo request the complementary BACnet CAS key, go to http://app.chipkin.com/activation/twoweek/ and fill in all the information. Enter Vendor Code “Fontecal2BACnet”. Once completed, the email address that was submitted will be registered.

Fig. 32 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”.

Fig. 33 Requesting CAS Activation Key

ProtoNode 6720818452 (2015/10) US

Troubleshooting | 19

10 .2 CAS BACnet SetupThese are the instructions to set CAS Explorer up for the first time on BACnet MS/ST and BACnet/IP.

10 .2 .1 CAS BACnet MS/ST 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:

- Click on settings - Check the BACnet MS/TP box and uncheck the BACnet/IP and

BACnet Ethernet boxes - Set the BACnet MS/TP MAC address to 0 - Set the BACnet MS/TP Baud Rate to 38400 - Click Ok - On the bottom right-hand corner, make sure that the BACnet MS/

TP box is green - Click on discover - Check all 4 boxes - Click Send

10 .2 .2 CAS BACnet BACnet/IP Setup• See Section 6 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:• Click on settings• Check the BACnet/IP box and uncheck the BACnet MS/TP and

BACnet Ethernet boxes• In the “Select a Network Device” box, select the network card of the

PC by clicking on it• Click Ok• On the bottom right-hand corner, make sure that the BACnet/IP box

is green• Click on discover• Check all 4 boxes• Click Send

11 Troubleshooting

11 .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.

Fig. 34 Error messages screen

6720818452 (2015/10) US ProtoNode


11 .2 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 RTU and you need to check the following things: - Visual observations of LEDs on ProtoNode. (Section 11.5) - Check baud rate, parity, data bits, stop bits - Check Modbus RTU device address - Verify wiring - Verify all the Modbus RTU devices that were discovered in FST

Web Configurator. (Section 6.2)• Field COM problems:

- Visual observations of LEDs on ProtoNode. (Section 11.5) - Visual dipswitch settings (using correct baud rate and device

instance) - Verify IP address setting - Verify wiring

• If the problem still exists, a Diagnostic Capture needs to be taken and sent to Sierra Monitor Corporation. (Appendix A.3)

11 .3 Appendix A .3 . Take Diagnostic Capture With the FieldServer Toolbox

• 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 Corporation 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.

ProtoNode 6720818452 (2015/10) US

CAS BACnet explorer for validating ProtoNode in the field | 21

► Disable any wireless Ethernet adapters on the PC/Laptop ► Disable firewall and virus protection software if possible ► Connect a standard cat5 Ethernet cable between the PC and ProtoNode ► Double click on the FS Toolbox Utility

STEP 1: TAKE A LOG ► Click on the diagnose icon of the desired device

Fig. 35 FS Toolbox

► Select full Diagnostic

Fig. 36 FS Toolbox - Device Diagnostics

► If desired, the default capture period can be changed. ► Click on Start Diagnostic

Fig. 37 FS Toolbox - Start Diagnostic

6720818452 (2015/10) US ProtoNode


► Wait for Capture period to finish. Diagnostic Test Complete window will appear.

STEP 2: SEND LOG ► Once the Diagnostic test is complete, a .zip file will be saved on the PC.

Fig. 38 FS Toolbox - Send Log

► Choose open to launch explorer and have it point directly at the correct folder. Send the Diagnostic zip file to support@sierramonitor .com

Fig. 39 Diagnostic zip file

11 .4 Appendix A .4 . BACnet: Setting Network_Number for more than one ProtoNode on SubnetFor 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.

Fig. 40 Web Configurator showing setting the network number for BACnet

ProtoNode 6720818452 (2015/10) US

CAS BACnet explorer for validating ProtoNode in the field | 23

11 .5 Appendix A .4 . LED Diagnostics for Modbus RTU Communications Between ProtoNode and ControllersPlease see Fig. 41 below for ProtoNode FPC-N34 and FPC-N35 LED Locations.

Fig. 41 Diagnostic LEDs

11 .6 Appendix A .5 . PasswordsAccess to the ProtoNode can be restricted by enabling a password. There are 2 access levels defined by 2 account names: Admin and User.

• The Admin account has unrestricted access to the ProtoNode. • The User account can view any ProtoNode information, but cannot make any changes or restart the ProtoNode.The password needs to be a minimum of eight characters and is case sensitive.

If you forgot your password, click cancel on the password authentication popup window, and e-mail the Password recovery token to [email protected] to receive a temporary password from the Sierra Monitor support team. You can now access the ProtoNode to set a new password.

Tag DescriptionSPL The SPL LED will light if the ProtoNode is off line.

RUN The RUN LED will start flashing 20 seconds after power indicating normal operation.

ERR

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.

RX The RX LED will flash when a message is received on the host port.

TX The TX LED will flash when a message is sent on the host port.

PWR This is the power light and should show steady green at all times when ProtoNode is powered.

6720818452 (2015/10) US ProtoNode

24 | Appendix B . Vendor Information – Fontecal_Bosch

12 Appendix B . Vendor Information – Fontecal_Bosch

12 .1 Appendix B .1 SSB Modbus RTU Mappings to BACnet MS/TP, BACnet/IP, Metasys N2 and LonWorks

Point NameBACnet Object Type

BACnet Object

IDN2 Data

TypeN2 Point Address Lon Name Lon SNVT

Unit Selection AV 1 AO 1 nvoUnitSel_XXX SNVT_count_fControl Register AV 2 AO 2 nvoCtrlReg_XXX SNVT_count_fState AI 3 AI 3 nvoState_XXX SNVT_count_fStatus AI 4 AI 4 nvoStatus_XXX SNVT_count_fError Code AI 5 AI 5 nvoErrCode_XXX SNVT_count_fCH Pump AI 6 AI 6 nvoCHPmp_XXX SNVT_count_fDHW Pump AI 7 AI 7 nvoDHWPmp_XXX SNVT_count_fGeneral Pump AI 8 AI 8 nvoGenPmp_XXX SNVT_count_fSupply Temperature AI 9 AI 9 nvoSupTmp_XXX SNVT_temp_pReturn Temperature AI 10 AI 10 nvoRetTmp_XXX SNVT_temp_pDHW Temperature AI 11 AI 11 nvoDHWTmp_XXX SNVT_temp_pFlue Gas Temperature AI 12 AI 12 nvoFlGasTmp_XXX SNVT_temp_pSystem (Heat Exchanger) Temperature AI 13 AI 13 nvoSysTmp_XXX SNVT_temp_pOutside Temperature AI 14 AI 14 nvoOutTmp_XXX SNVT_temp_pFiring Rate AI 15 AI 15 nvoFirRate_XXX SNVT_lev_percentFlame (Ionization) Current AI 16 AI 16 nvoFlmCrnt_XXX SNVT_count_fWater Pressure AI 17 AI 17 nvoWtrPrs_XXX SNVT_count_fSuccessful Ignition Counter AI 18 AI 18 nvoSucIgnCnt_XXX SNVT_count_fFailed Ignition Counter AI 19 AI 19 nvoFldIgnCnt_XXX SNVT_count_fFlame Failure Counter AI 20 AI 20 nvoFlmFlCnt_XXX SNVT_count_fBurn Hours CH AI 21 AI 21 nvoBrnHrCH_XXX SNVT_time_hourBurn Hours DHW AI 22 AI 22 nvoBrnHrDHW_XXX SNVT_time_hour1st Lockout In History AI 23 AI 23 nvo1LkotHst_XXX SNVT_count_f2nd Lockout In History AI 24 AI 24 nvo2LkotHst_XXX SNVT_count_f3rd Lockout In History AI 25 AI 25 nvo3LkotHst_XXX SNVT_count_f4th Lockout In History AI 26 AI 26 nvo4LkotHst_XXX SNVT_count_f5th Lockout In History AI 27 AI 27 nvo5LkotHst_XXX SNVT_count_f6th Lockout In History AI 28 AI 28 nvo6LkotHst_XXX SNVT_count_f7th Lockout In History AI 29 AI 29 nvo7LkotHst_XXX SNVT_count_f8th Lockout In History AI 30 AI 30 nvo8LkotHst_XXX SNVT_count_f9th Lockout In History AI 31 AI 31 nvo9LkotHst_XXX SNVT_count_f10th Lockout In History AI 32 AI 32 nvo10LkotHst_XXX SNVT_count_f11th Lockout In History AI 33 AI 33 nvo11LkotHst_XXX SNVT_count_f12th Lockout In History AI 34 AI 34 nvo12LkotHst_XXX SNVT_count_f13th Lockout In History AI 35 AI 35 nvo13LkotHst_XXX SNVT_count_f14th Lockout In History AI 36 AI 36 nvo14LkotHst_XXX SNVT_count_f15th Lockout In History AI 37 AI 37 nvo15LkotHst_XXX SNVT_count_f16th Lockout In History AI 38 AI 38 nvo16LkotHst_XXX SNVT_count_fTime After 1st Lockout AI 39 AI 39 nvoTmAf1Lkot_XXX SNVT_time_hourTime After 2nd Lockout AI 40 AI 40 nvoTmAf2Lkot_XXX SNVT_time_hourTime After 3rd Lockout AI 41 AI 41 nvoTmAf3Lkot_XXX SNVT_time_hourTime After 4th Lockout AI 42 AI 42 nvoTmAf4Lkot_XXX SNVT_time_hourTime After 5th Lockout AI 43 AI 43 nvoTmAf5Lkot_XXX SNVT_time_hourTime After 6th Lockout AI 44 AI 44 nvoTmAf6Lkot_XXX SNVT_time_hourTime After 7th Lockout AI 45 AI 45 nvoTmAf7Lkot_XXX SNVT_time_hourTime After 8th Lockout AI 46 AI 46 nvoTmAf8Lkot_XXX SNVT_time_hourTime After 9th Lockout AI 47 AI 47 nvoTmAf9Lkot_XXX SNVT_time_hourTime After 10th Lockout AI 48 AI 48 nvoTmA10Lkot_XXX SNVT_time_hourTime After 11th Lockout AI 49 AI 49 nvoTmA11Lkot_XXX SNVT_time_hourTime After 12th Lockout AI 50 AI 50 nvoTmA12Lkot_XXX SNVT_time_hourTime After 13th Lockout AI 51 AI 51 nvoTmA13Lkot_XXX SNVT_time_hourTime After 14th Lockout AI 52 AI 52 nvoTmA14Lkot_XXX SNVT_time_hourTime After 15th Lockout AI 53 AI 53 nvoTmA15Lkot_XXX SNVT_time_hourTab. 13 Level 2 parameters

ProtoNode 6720818452 (2015/10) US

Appendix B . Vendor Information – Fontecal_Bosch | 25


BACnet Object

IDN2 Data


Time After 16th Lockout AI 54 AI 54 nvoTmA16Lkot_XXX SNVT_time_hour1st Blocking In History AI 55 AI 55 nvo1BlkInHst_XXX SNVT_count_f2nd Blocking In History AI 56 AI 56 nvo2BlkInHst_XXX SNVT_count_f3rd Blocking In History AI 57 AI 57 nvo3BlkInHst_XXX SNVT_count_f4th Blocking In History AI 58 AI 58 nvo4BlkInHst_XXX SNVT_count_f5th Blocking In History AI 59 AI 59 nvo5BlkInHst_XXX SNVT_count_f6th Blocking In History AI 60 AI 60 nvo6BlkInHst_XXX SNVT_count_f7th Blocking In History AI 61 AI 61 nvo7BlkInHst_XXX SNVT_count_f8th Blocking In History AI 62 AI 62 nvo8BlkInHst_XXX SNVT_count_f9th Blocking In History AI 63 AI 63 nvo9BlkInHst_XXX SNVT_count_f10th Blocking In History AI 64 AI 64 nvo10BlkHst_XXX SNVT_count_f11th Blocking In History AI 65 AI 65 nvo11BlkHst_XXX SNVT_count_f12th Blocking In History AI 66 AI 66 nvo12BlkHst_XXX SNVT_count_f13th Blocking In History AI 67 AI 67 nvo13BlkHst_XXX SNVT_count_f14th Blocking In History AI 68 AI 68 nvo14BlkHst_XXX SNVT_count_f15th Blocking In History AI 69 AI 69 nvo15BlkHst_XXX SNVT_count_f16th Blocking In History AI 70 AI 70 nvo16BlkHst_XXX SNVT_count_fTime After 1st Blocking AI 71 AI 71 nvoTmAf1Blk_XXX SNVT_time_hourTime After 2nd Blocking AI 72 AI 72 nvoTmAf2Blk_XXX SNVT_time_hourTime After 3rd Blocking AI 73 AI 73 nvoTmAf3Blk_XXX SNVT_time_hourTime After 4th Blocking AI 74 AI 74 nvoTmAf4Blk_XXX SNVT_time_hourTime After 5th Blocking AI 75 AI 75 nvoTmAf5Blk_XXX SNVT_time_hourTime After 6th Blocking AI 76 AI 76 nvoTmAf6Blk_XXX SNVT_time_hourTime After 7th Blocking AI 77 AI 77 nvoTmAf7Blk_XXX SNVT_time_hourTime After 8th Blocking AI 78 AI 78 nvoTmAf8Blk_XXX SNVT_time_hourTime After 9th Blocking AI 79 AI 79 nvoTmAf9Blk_XXX SNVT_time_hourTime After 10th Blocking AI 80 AI 80 nvoTmAf10Blk_XXX SNVT_time_hourTime After 11th Blocking AI 81 AI 81 nvoTmAf11Blk_XXX SNVT_time_hourTime After 12th Blocking AI 82 AI 82 nvoTmAf12Blk_XXX SNVT_time_hourTime After 13th Blocking AI 83 AI 83 nvoTmAf13Blk_XXX SNVT_time_hourTime After 14th Blocking AI 84 AI 84 nvoTmAf14Blk_XXX SNVT_time_hourTime After 15th Blocking AI 85 AI 85 nvoTmAf15Blk_XXX SNVT_time_hourTime After 16th Blocking AI 86 AI 86 nvoTmAf16Blk_XXX SNVT_time_hourDependent 01 State AI 87 AI 87 nvoD01State_XXX SNVT_count_fDependent 01 Error Code AI 88 AI 88 nvoD01ErrCd_XXX SNVT_count_fDependent 01 Firing Rate AI 89 AI 89 nvoD01FirRt_XXX SNVT_lev_percentDependent 02 State AI 90 AI 90 nvoD02State_XXX SNVT_count_fDependent 02 Error Code AI 91 AI 91 nvoD02ErrCd_XXX SNVT_count_fDependent 02 Firing Rate AI 92 AI 92 nvoD02FirRt_XXX SNVT_lev_percentDependent 03 State AI 93 AI 93 nvoD03State_XXX SNVT_count_fDependent 03 Error Code AI 94 AI 94 nvoD03ErrCd_XXX SNVT_count_fDependent 03 Firing Rate AI 95 AI 95 nvoD03FirRt_XXX SNVT_lev_percentDependent 04 State AI 96 AI 96 nvoD04State_XXX SNVT_count_fDependent 04 Error Code AI 97 AI 97 nvoD04ErrCd_XXX SNVT_count_fDependent 04 Firing Rate AI 98 AI 98 nvoD04FirRt_XXX SNVT_lev_percentDependent 05 State AI 99 AI 99 nvoD05State_XXX SNVT_count_fDependent 05 Error Code AI 100 AI 100 nvoD05ErrCd_XXX SNVT_count_fDependent 05 Firing Rate AI 101 AI 101 nvoD05FirRt_XXX SNVT_lev_percentDependent 06 State AI 102 AI 102 nvoD06State_XXX SNVT_count_fDependent 06 Error Code AI 103 AI 103 nvoD06ErrCd_XXX SNVT_count_fDependent 06 Firing Rate AI 104 AI 104 nvoD06FirRt_XXX SNVT_lev_percentDependent 07 State AI 105 AI 105 nvoD07State_XXX SNVT_count_fDependent 07 Error Code AI 106 AI 106 nvoD07ErrCd_XXX SNVT_count_fDependent 07 Firing Rate AI 107 AI 107 nvoD07FirRt_XXX SNVT_lev_percentDependent 08 State AI 108 AI 108 nvoD08State_XXX SNVT_count_fDependent 08 Error Code AI 109 AI 109 nvoD08ErrCd_XXX SNVT_count_fDependent 08 Firing Rate AI 110 AI 110 nvoD08FirRt_XXX SNVT_lev_percentTab. 13 Level 2 parameters

6720818452 (2015/10) US ProtoNode



BACnet Object

IDN2 Data


Dependent 09 State AI 111 AI 111 nvoD09State_XXX SNVT_count_fDependent 09 Error Code AI 112 AI 112 nvoD09ErrCd_XXX SNVT_count_fDependent 09 Firing Rate AI 113 AI 113 nvoD09FirRt_XXX SNVT_lev_percentDependent 10 State AI 114 AI 114 nvoD10State_XXX SNVT_count_fDependent 10 Error Code AI 115 AI 115 nvoD10ErrCd_XXX SNVT_count_fDependent 10 Firing Rate AI 116 AI 116 nvoD10FirRt_XXX SNVT_lev_percentDependent 11 State AI 117 AI 117 nvoD11State_XXX SNVT_count_fDependent 11 Error Code AI 118 AI 118 nvoD11ErrCd_XXX SNVT_count_fDependent 11 Firing Rate AI 119 AI 119 nvoD11FirRt_XXX SNVT_lev_percentDependent 12 State AI 120 AI 120 nvoD12State_XXX SNVT_count_fDependent 12 Error Code AI 121 AI 121 nvoD12ErrCd_XXX SNVT_count_fDependent 12 Firing Rate AI 122 AI 122 nvoD12FirRt_XXX SNVT_lev_percentDependent 13 State AI 123 AI 123 nvoD13State_XXX SNVT_count_fDependent 13 Error Code AI 124 AI 124 nvoD13ErrCd_XXX SNVT_count_fDependent 13 Firing Rate AI 125 AI 125 nvoD13FirRt_XXX SNVT_lev_percentDependent 14 State AI 126 AI 126 nvoD14State_XXX SNVT_count_fDependent 14 Error Code AI 127 AI 127 nvoD14ErrCd_XXX SNVT_count_fDependent 14 Firing Rate AI 128 AI 128 nvoD14FirRt_XXX SNVT_lev_percentDependent 15 State AI 129 AI 129 nvoD15State_XXX SNVT_count_fDependent 15 Error Code AI 130 AI 130 nvoD15ErrCd_XXX SNVT_count_fDependent 15 Firing Rate AI 131 AI 131 nvoD15FirRt_XXX SNVT_lev_percentCH Mode AV 132 AO 132 nvi/nvoCHMode_XXX SNVT_count_fDHW Mode AV 133 AO 133 nvi/nvoDHWMode_XXX SNVT_count_fCH Setpoint AV 134 AO 134 nvi/nvoCHSP_XXX SNVT_count_fDHW Setpoint AV 135 AO 135 nvi/nvoDHWSP_XXX SNVT_count_fReset Curve Boiler Design AV 136 AO 136 nvi/nvoReCrBlDsn_XXX SNVT_count_fReset Curve Boiler Mild Weather AV 137 AO 137 nvi/nvoReCrBMlWt_XXX SNVT_count_fReset Curve Outdoor Mild Weather AV 138 AO 138 nvi/nvoReCrOMlWt_XXX SNVT_count_fReset Curve Outdoor Design AV 139 AO 139 nvi/nvoReCrOtDsn_XXX SNVT_count_fWarm Weather Shutdown AV 140 AO 140 nvi/nvoWrmWtShdn_XXX SNVT_count_fReset Curve Boiler Maximum AV 141 AO 141 nvi/nvoReCrBlMax_XXX SNVT_count_fReset Curve Boiler Minimum AV 142 AO 142 nvi/nvoReCrBlMin_XXX SNVT_count_fNight Setback AV 143 AO 143 nvi/nvoNghtStbck_XXX SNVT_count_fTab. 13 Level 2 parameters

ProtoNode 6720818452 (2015/10) US

Appendix C . “A” Bank DIP Switch Settings | 27

Address A0 A1 A2 A3 A4 A5 A6 A71 On Off Off Off Off Off Off Off2 Off On Off Off Off Off Off Off3 On On Off Off Off Off Off Off4 Off Off On Off Off Off Off Off5 On Off On Off Off Off Off Off6 Off On On Off Off Off Off Off7 On On On Off Off Off Off Off8 Off Off Off On Off Off Off Off9 On Off Off On Off Off Off Off

10 Off On Off On Off Off Off Off11 On On Off On Off Off Off Off12 Off Off On On Off Off Off Off13 On Off On On Off Off Off Off14 Off On On On Off Off Off Off15 On On On On Off Off Off Off16 Off Off Off Off On Off Off Off17 On Off Off Off On Off Off Off18 Off On Off Off On Off Off Off19 On On Off Off On Off Off Off20 Off Off On Off On Off Off Off21 On Off On Off On Off Off Off22 Off On On Off On Off Off Off23 On On On Off On Off Off Off24 Off Off Off On On Off Off Off25 On Off Off On On Off Off Off26 Off On Off On On Off Off Off27 On On Off On On Off Off Off28 Off Off On On On Off Off Off29 On Off On On On Off Off Off30 Off On On On On Off Off Off31 On On On On On Off Off Off32 Off Off Off Off Off On Off Off33 On Off Off Off Off On Off Off34 Off On Off Off Off On Off Off35 On On Off Off Off On Off Off36 Off Off On Off Off On Off Off37 On Off On Off Off On Off Off38 Off On On Off Off On Off Off39 On On On Off Off On Off Off40 Off Off Off On Off On Off Off41 On Off Off On Off On Off Off42 Off On Off On Off On Off Off43 On On Off On Off On Off Off44 Off Off On On Off On Off Off45 On Off On On Off On Off Off46 Off On On On Off On Off Off47 On On On On Off On Off Off48 Off Off Off Off On On Off Off49 On Off Off Off On On Off Off50 Off On Off Off On On Off Off51 On On Off Off On On Off Off52 Off Off On Off On On Off Off53 On Off On Off On On Off Off54 Off On On Off On On Off Off

Tab. 14 Level 2 parameters

Address A0 A1 A2 A3 A4 A5 A6 A755 On On On Off On On Off Off56 Off Off Off On On On Off Off57 On Off Off On On On Off Off58 Off On Off On On On Off Off59 On On Off On On On Off Off60 Off Off On On On On Off Off61 On Off On On On On Off Off62 Off On On On On On Off Off63 On On On On On On Off Off64 Off Off Off Off Off Off On Off65 On Off Off Off Off Off On Off66 Off On Off Off Off Off On Off67 On On Off Off Off Off On Off68 Off Off On Off Off Off On Off69 On Off On Off Off Off On Off70 Off On On Off Off Off On Off71 On On On Off Off Off On Off72 Off Off Off On Off Off On Off73 On Off Off On Off Off On Off74 Off On Off On Off Off On Off75 On On Off On Off Off On Off76 Off Off On On Off Off On Off77 On Off On On Off Off On Off78 Off On On On Off Off On Off79 On On On On Off Off On Off80 Off Off Off Off On Off On Off81 On Off Off Off On Off On Off82 Off On Off Off On Off On Off83 On On Off Off On Off On Off84 Off Off On Off On Off On Off85 On Off On Off On Off On Off86 Off On On Off On Off On Off87 On On On Off On Off On Off88 Off Off Off On On Off On Off89 On Off Off On On Off On Off90 Off On Off On On Off On Off91 On On Off On On Off On Off92 Off Off On On On Off On Off93 On Off On On On Off On Off94 Off On On On On Off On Off95 On On On On On Off On Off96 Off Off Off Off Off On On Off97 On Off Off Off Off On On Off98 Off On Off Off Off On On Off99 On On Off Off Off On On Off

100 Off Off On Off Off On On Off101 On Off On Off Off On On Off102 Off On On Off Off On On Off103 On On On Off Off On On Off104 Off Off Off On Off On On Off105 On Off Off On Off On On Off106 Off On Off On Off On On Off107 On On Off On Off On On Off108 Off Off On On Off On On Off


13 Appendix C . “A” Bank DIP Switch Settings

13 .1 Appendix C .1 “A” Bank DIP Switch Settings

6720818452 (2015/10) US ProtoNode


Address A0 A1 A2 A3 A4 A5 A6 A7109 On Off On On Off On On Off110 Off On On On Off On On Off111 On On On On Off On On Off112 Off Off Off Off On On On Off113 On Off Off Off On On On Off114 Off On Off Off On On On Off115 On On Off Off On On On Off116 Off Off On Off On On On Off117 On Off On Off On On On Off118 Off On On Off On On On Off119 On On On Off On On On Off120 Off Off Off On On On On Off121 On Off Off On On On On Off122 Off On Off On On On On Off123 On On Off On On On On Off124 Off Off On On On On On Off125 On Off On On On On On Off126 Off On On On On On On Off127 On On On On On On On Off128 Off Off Off Off Off Off Off On129 On Off Off Off Off Off Off On130 Off On Off Off Off Off Off On131 On On Off Off Off Off Off On132 Off Off On Off Off Off Off On133 On Off On Off Off Off Off On134 Off On On Off Off Off Off On135 On On On Off Off Off Off On136 Off Off Off On Off Off Off On137 On Off Off On Off Off Off On138 Off On Off On Off Off Off On139 On On Off On Off Off Off On140 Off Off On On Off Off Off On141 On Off On On Off Off Off On142 Off On On On Off Off Off On143 On On On On Off Off Off On144 Off Off Off Off On Off Off On145 On Off Off Off On Off Off On146 Off On Off Off On Off Off On147 On On Off Off On Off Off On148 Off Off On Off On Off Off On149 On Off On Off On Off Off On150 Off On On Off On Off Off On151 On On On Off On Off Off On152 Off Off Off On On Off Off On153 On Off Off On On Off Off On154 Off On Off On On Off Off On155 On On Off On On Off Off On156 Off Off On On On Off Off On157 On Off On On On Off Off On158 Off On On On On Off Off On159 On On On On On Off Off On160 Off Off Off Off Off On Off On161 On Off Off Off Off On Off On162 Off On Off Off Off On Off On163 On On Off Off Off On Off On164 Off Off On Off Off On Off On165 On Off On Off Off On Off On166 Off On On Off Off On Off On167 On On On Off Off On Off On


Address A0 A1 A2 A3 A4 A5 A6 A7168 Off Off Off On Off On Off On169 On Off Off On Off On Off On170 Off On Off On Off On Off On171 On On Off On Off On Off On172 Off Off On On Off On Off On173 On Off On On Off On Off On174 Off On On On Off On Off On175 On On On On Off On Off On176 Off Off Off Off On On Off On177 On Off Off Off On On Off On178 Off On Off Off On On Off On179 On On Off Off On On Off On180 Off Off On Off On On Off On181 On Off On Off On On Off On182 Off On On Off On On Off On183 On On On Off On On Off On184 Off Off Off On On On Off On185 On Off Off On On On Off On186 Off On Off On On On Off On187 On On Off On On On Off On188 Off Off On On On On Off On189 On Off On On On On Off On190 Off On On On On On Off On191 On On On On On On Off On192 Off Off Off Off Off Off On On193 On Off Off Off Off Off On On194 Off On Off Off Off Off On On195 On On Off Off Off Off On On196 Off Off On Off Off Off On On197 On Off On Off Off Off On On198 Off On On Off Off Off On On199 On On On Off Off Off On On200 Off Off Off On Off Off On On201 On Off Off On Off Off On On202 Off On Off On Off Off On On203 On On Off On Off Off On On204 Off Off On On Off Off On On205 On Off On On Off Off On On206 Off On On On Off Off On On207 On On On On Off Off On On208 Off Off Off Off On Off On On209 On Off Off Off On Off On On210 Off On Off Off On Off On On211 On On Off Off On Off On On212 Off Off On Off On Off On On213 On Off On Off On Off On On214 Off On On Off On Off On On215 On On On Off On Off On On216 Off Off Off On On Off On On217 On Off Off On On Off On On218 Off On Off On On Off On On219 On On Off On On Off On On220 Off Off On On On Off On On221 On Off On On On Off On On222 Off On On On On Off On On223 On On On On On Off On On224 Off Off Off Off Off On On On225 On Off Off Off Off On On On226 Off On Off Off Off On On On


ProtoNode 6720818452 (2015/10) US

Appendix B . Vendor Information – Fontecal_Bosch | 29

Address A0 A1 A2 A3 A4 A5 A6 A7227 On On Off Off Off On On On228 Off Off On Off Off On On On229 On Off On Off Off On On On230 Off On On Off Off On On On231 On On On Off Off On On On232 Off Off Off On Off On On On233 On Off Off On Off On On On234 Off On Off On Off On On On235 On On Off On Off On On On236 Off Off On On Off On On On237 On Off On On Off On On On238 Off On On On Off On On On239 On On On On Off On On On240 Off Off Off Off On On On On241 On Off Off Off On On On On242 Off On Off Off On On On On243 On On Off Off On On On On244 Off Off On Off On On On On245 On Off On Off On On On On246 Off On On Off On On On On247 On On On Off On On On On248 Off Off Off On On On On On249 On Off Off On On On On On250 Off On Off On On On On On251 On On Off On On On On On252 Off Off On On On On On On253 On Off On On On On On On254 Off On On On On On On On255 On On On On On On On On


6720818452 (2015/10) US ProtoNode

30 | Reference

14 Reference

14 .1 Specifications

Electrical Connections

ProtoNode FPC-N34One 6-pin Phoenix connector with: RS-485 port (+ / - / gnd) Power port (+ / - / Frame-gnd) One 3-pin Phoenix connector with: S-485 port (+ / - / gnd) One Ethernet 10/100 BaseT port

ProtoNode FPC-N35One 6-pin Phoenix connector with:RS-485 port (+ / - / gnd) Power port (+ / - / Frame-gnd) One Ethernet 10/100 BaseT port One FTT-10 LonWorks port

Approvals:

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; RoHS Compliant; CSA 205 Approved

Power Requirements Multi-mode power adapter: 9-30VDC or 12 - 24VAC

Physical Dimensions 11.5 cm L x 8.3 cm W x 4.1 cm H (4.5 x 3.2 x 1.6 in.)

Weight: 0.2 kg (0.4 lbs)Operating

Temperature: -40°C to 75°C (-40°F to167°F)

Surge Suppression

EN61000-4-2 ESD EN61000-4-3 EMC EN61000-4-4 EFT

Humidity: 5 - 90% RH (non-condensing)(Specifications subject to change without notice)

14 .1 .1 Compliance with UL RegulationsFor 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.

15 Limited 2 Year WarrantySierra 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.

16 Certifications

BTL MARK – BACNET TESTING LABORATORY LThe 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

3.4

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.

ProtoNode 6720818452 (2015/10) US

| 31

Notes

United States and Canada

Bosch Thermotechnology Corp.50 Wentworth AvenueLondonderry, NH 03053Tel. 603-552-1100Fax 603-965-7581www.boschheatingandcooling.comU.S.A.

Bosch Thermotechnology Corp. reserves the right to make changes without notice due to continuing engineering and technological advances.

6720

8184

52 (2

015/1

0) U

S - R

ev.1

- (12

/2015

)

Documents

ProtoNode FPC-N34 and FPC-N35 · 2016. 1. 5. · BACnet MS/TP or BACnet/IP: Assigning Specific Device Instances • With the default Node_Offset value of 50,000 the Device Instances