ProtoCessor FieldServer SATEC ProtoNode FPC-N34 User guide

Document Revision: 1
Web Configurator
Template Revision: 13
ProtoNode FPC-N34 and ProtoNode FPC-N35
Startup Guide
For Interfacing Satec Products: BFM136 and EM133
To Building Automation Systems:
BACnet MS/TP, BACnet/IP, Modbus/TCP, 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 May 2014

Satec’s ProtoNode Startup Guide Page 2 of 41
ProtoCessor 1991 Tarob Court Milpitas, California 95035 USA Web: www.protocessor.com
Email: support@protocessor.com
Technical Support:
Thank you for purchasing the ProtoNode for BFM136 and EM133.
Please call Satec for Technical support of the ProtoNode product.
FieldServer does not provide direct support. If Satec needs to escalate the concern, they will contact FieldServer
for assistance.
Support Contact Information:
10 Milltown Court
Union
NJ 07083
Satec Service:
1-888-OK-SATEC (908-657-2832)
Office: (908) 686-9510
Mobile: (908) 337-8058
Email: bchristian@oksatec.com
Website: www.satec-global.com

Satec’s ProtoNode Startup Guide Page 3 of 41
ProtoCessor 1991 Tarob Court Milpitas, California 95035 USA Web: www.protocessor.com
Email: support@protocessor.com
A Quick Start guide
1. Record the information about the unit. (Section 2.1)
2. Set the device’s Modbus RTU serial settings (i.e. baud rate, parity, stop bits) and Modbus Node-ID’s for
each of the devices that will be connected to ProtoNode FPC-N34 or FPC-N35. (Section 2.2)
3. ProtoNode FPC-N34 units: Select the Field Protocol (BACnet MS/TP, BACnet/IP, Modbus/TCP or Metasys
N2) on the S Bank Dip Switches. (Section 2.3)
4. BACnet MS/TP (FPC-N34): Set the MAC Address on DIP Switch Bank A. (Section 2.4.1)
5. BACnet MS/TP or BACnet IP (FPC-N34): Set the BACnet Device Instance. (Section 2.4.2)
6. Metasys N2 or Modbus TCP (FPC-N34): Set the Node-ID. (See Section 2.4.3)
7. 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)
8. Connect FPC-N34 ProtoNode’s 3 pin RS-485 port to the Field Protocol cabling,
or connect FPC-N35 ProtoNode’s 2 pin LonWorks port to the Field Protocol cabling. (Section 3.1)
9. 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)
10. Connect Power to ProtoNode’s 6 pin connector. (Section 3.5)
11. Use a browser to access the ProtoNode’s embedded tool, which is referred to in this manual as the Web
Configurator, to 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 4)
12. BACnet/IP or Modbus/TCP (FPC-N34): Use a browser to access the ProtoNode’s Web Configurator to
change the IP address. No changes to the configuration are necessary. (Section 4.4)
13. 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 5)

Satec’s ProtoNode Startup Guide Page 4 of 41
ProtoCessor 1991 Tarob Court Milpitas, California 95035 USA Web: www.protocessor.com
Email: support@protocessor.com
Certifications
BTL MARK –BACNET TESTING LABORATORY
LONMARK CERTIFICATION
The BTL Mark on ProtoNode FPC-N34 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.
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.

Satec’s ProtoNode Startup Guide Page 5 of 41
ProtoCessor 1991 Tarob Court Milpitas, California 95035 USA Web: www.protocessor.com
Email: support@protocessor.com
TABLE OF CONTENTS
1Introduction ................................................................................................................................................... 7
1.1 ProtoNode Gateway ......................................................................................................................................7
1.2 Satec’s Devices and Point Count Available ....................................................................................................7
2BACnet/LonWorks Setup for ProtoCessor ProtoNode FPC-N34/FPC-N35 ....................................................... 8
2.1 Record Identification Data .............................................................................................................................8
2.2 Configuring Device Communications.............................................................................................................8
2.2.1 Set Modbus COM setting on all of the devices connected to the ProtoNode ..........................................8
2.2.2 Set Modbus RTU Node-ID for each of the devices attached to the ProtoNode........................................8
2.3 Selecting the Desired Field Protocol..............................................................................................................9
2.4 Setting the MAC Address, Device Instance and Baud Rate .........................................................................10
2.4.1 BACnet MS/TP (FPC-N34): Setting the MAC Address BACnet Network..................................................10
2.4.2 BACnet MS/TP and BACnet/IP (FPC-N34): Setting the Device Instance (Node-ID).................................11
2.4.3 Metasys N2 or Modbus/TCP (FPC-N34): Setting the Node-ID................................................................11
2.4.4 BACnet MS/TP (FPC-N34): Setting the Baud Rate..................................................................................12
3Interfacing ProtoNode to Devices ................................................................................................................ 13
3.1 ProtoNode FPC-N34 and FPC-N35 Showing Connection Ports....................................................................13
3.2 Device Connections to ProtoNode...............................................................................................................14
3.2.1 Biasing the Modbus RS-485 Network.....................................................................................................15
3.2.2 End of Line Termination Switch for the Modbus RS-485 port on the ProtoNode...................................16
3.3 BACnet MS/TP or Metasys N2 (FPC-N34): Wiring Field Port to RS-485 Network........................................17
3.4 LonWorks (FPC-N35): Wiring Field Port to LonWorks Network ..................................................................17
3.5 Connecting Power to ProtoNode.................................................................................................................18
4Use ProtoNode’s Web Configurator to Select Device Profiles....................................................................... 19
4.1 Connect the PC to ProtoNode via the Ethernet Port ...................................................................................19
4.2 Connecting to ProtoNode’s Web Configurator............................................................................................20
4.2.1 Selecting Profiles for Devices Connected to ProtoNode.........................................................................20
4.3 BACnet MS/TP and BACnet/IP: Setting Node_Offset to Assign Specific Device Instances .........................22
4.4 Accessing the FST Web GUI from the Web Configurator ............................................................................23
4.5 BACnet/IP and Modbus TCP: Setting IP Address for Field Network ............................................................24
5LonWorks (FPC-N35): Commissioning ProtoNode on a lonworks Network................................................... 25
5.1 Commissioning ProtoNode FPC-N35 on a LonWorks Network ...................................................................25
5.1.1 Instructions to Upload XIF File from ProtoNode FPC-N35 Using FieldServer GUI Web Server ...............25
6CAS BACnet Explorer for Validating ProtoNode in the Field ......................................................................... 27
6.1 Downloading the CAS Explorer and Requesting an Activation Key .............................................................27
6.2 CAS BACnet Setup........................................................................................................................................28
6.2.1 CAS BACnet MS/TP Setup.......................................................................................................................28
6.2.2 CAS BACnet BACnet/IP Setup .................................................................................................................28
Appendix A. Troubleshooting .............................................................................................................................. 29
Appendix A.1. Check Wiring and Settings................................................................................................................29
Appendix A.2. Take Diagnostic Capture With the FieldServer Utilities ...................................................................29
Appendix A.3. If there is more than 1 ProtoNode on the same BACnet/IP network, change Network Number ....32
Appendix A.4. LED Diagnostics for Modbus RTU Communications Between ProtoNode and Devices ...................32
Appendix B. Vendor Information - Satec.............................................................................................................. 33
Appendix B.1. BFM136 Modbus RTU Mappings to BACnet MS/TP, BACnet/IP, Metasys N2 and LonWorks..........33
Appendix B.2. EM133 Modbus RTU Mappings to BACnet MS/TP, BACnet/IP, Metasys N2 and LonWorks............34
Appendix C. MAC Address DIP Switch Settings .................................................................................................... 37
Appendix C.1. MAC Address DIP Switch Settings ....................................................................................................37
Appendix D. Reference ........................................................................................................................................ 40
Appendix D.1. Specifications ...................................................................................................................................40
Appendix D.1.1. Compliance with UL Regulations............................................................................................40

Satec’s ProtoNode Startup Guide Page 6 of 41
ProtoCessor 1991 Tarob Court Milpitas, California 95035 USA Web: www.protocessor.com
Email: support@protocessor.com
Appendix E. Limited 2 Year Warranty .................................................................................................................. 41
LIST OF FIGURES
Figure 1: Modbus Registers ...........................................................................................................................................7
Figure 2: ProtoCessor Part Numbers .............................................................................................................................8
Figure 3: Modbus RTU COM Settings ............................................................................................................................8
Figure 4: S Bank DIP Switches ........................................................................................................................................9
Figure 5: MAC Address DIP Switches ...........................................................................................................................10
Figure 6: Baud Rate DIP Switches ................................................................................................................................12
Figure 7: Baud Rate......................................................................................................................................................12
Figure 8: ProtoNode BACnet FPC-N34 (upper) and ProtoNode FPC-N35 (lower) .......................................................13
Figure 9: Power and RS-485 Connections....................................................................................................................14
Figure 10: Modbus RS-485 Biasing Switch on the ProtoNode N34 (left) and ProtoNode N35 (right).........................15
Figure 11: Modbus RS-485 End-Of-Line Termination Switch on the ProtoNode N34 (left) and .................................16
Figure 12: Connection from ProtoNode to RS-485 Field Network ..............................................................................17
Figure 13: RS-485 EOL Switch ......................................................................................................................................17
Figure 14: LonWorks Terminal.....................................................................................................................................17
Figure 15: Required current draw for the ProtoNode ................................................................................................18
Figure 16: Power Connections.....................................................................................................................................18
Figure 17: Ethernet Port Location................................................................................................................................19
Figure 18: Web Configurator Showing no Active Profiles............................................................................................20
Figure 19: Web Configurator Showing Available Profiles for Selection.......................................................................21
Figure 20: Web Configurator Showing an Active Profile Addition...............................................................................21
Figure 20: Web Configurator screen with Active Profiles............................................................................................23
Figure 21: Changing IP Address via FST Web GUI ........................................................................................................24
Figure 23: LonWorks Service Pin Location...................................................................................................................25
Figure 24: Sample of Fserver.XIF File Being Generated...............................................................................................26
Figure 25: Downloading the CAS Explorer ...................................................................................................................27
Figure 26: Requesting CAS Activation Key ...................................................................................................................27
Figure 27: Ethernet Port Location................................................................................................................................29
Figure 28: Web Configurator showing setting the network number for BACnet/IP ...................................................32
Figure 29: Diagnostic LEDs...........................................................................................................................................32
Figure 30: Specifications..............................................................................................................................................40

Satec’s ProtoNode Startup Guide Page 7 of 41
ProtoCessor 1991 Tarob Court Milpitas, California 95035 USA Web: www.protocessor.com
Email: support@protocessor.com
1INTRODUCTION
1.1 ProtoNode Gateway
ProtoNode is an external, high performance Building Automation multi-protocol gateway that is preconfigured to
automatically communicate between Satec’s products (hereafter called “device”) connected to the ProtoNode and
automatically configures them for BACnet®
1
MS/TP, BACnet/IP, Metasys®
2
N2 by JCI, Modbus TCP or LonWorks®
3
.
It is not necessary to download any configuration files to support the required applications.
1.2 Satec’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 or Metasys N2.
The total number of devices attached to ProtoNode FPC-N35 cannot exceed 1000 Modbus registers
for LonWorks.
Devices
Point Count
BFM136
61
EM133
89
Figure 1: Modbus Registers
1
BACnet is a registered trademark of ASHRAE
2
Metasys is a registered trademark of Johnson Controls Inc.
3 LonWorks is a registered trademark of Echelon Corporation

Satec’s ProtoNode Startup Guide Page 8 of 41
ProtoCessor 1991 Tarob Court Milpitas, California 95035 USA Web: www.protocessor.com
Email: support@protocessor.com
2BACNET/LONWORKS SETUP FOR PROTOCESSOR PROTONODE FPC-N34/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-0995
ProtoNode FPC-N35
FPC-N35-102-401-0996
Figure 2: 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
2.2 Configuring Device Communications
2.2.1 Set Modbus COM setting on all of the devices connected to the ProtoNode
All of the Serial devices connected to ProtoNode MUST have the same Baud Rate, Data Bits, Stop Bits,
and Parity settings.
Figure 3 specifies the device serial port settings required to communicate with the ProtoNode.
Serial Port Setting
Device
Protocol
Modbus RTU
Baud Rate
9600
Parity
None
Data Bits
8
Stop Bits
1
Figure 3: 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.
oThe Modbus Node-ID that is assigned for each device needs to be documented.
oThe Modbus Node-ID’s assigned are used for designating the Device Instance for BACnet/IP and
BACnet MS/TP (See section 0)
oThe Metasys N2 and Modbus/TCP Node-ID will be set to same value as the Node-ID of the
Modbus RTU device.

Satec’s ProtoNode Startup Guide Page 9 of 41
ProtoCessor 1991 Tarob Court Milpitas, California 95035 USA Web: www.protocessor.com
Email: support@protocessor.com
2.3 Selecting the Desired Field Protocol
ProtoNode FPC-N34 units use the “S” bank of DIP switches (S0 – S3) to select the Field Protocol.
oSee the table in figure 4 for the switch settings to select BACnet MS/TP, BACnet/IP, Modbus/TCP,
or Metasys N2.
oThe 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 – S3) to select a Field Protocol.
oOn ProtoNode FPC-N35 units, these switches are disabled; the Field Protocol is always LonWorks.
ProtoNode FPC-N34
S Bank DIP Switches
Profile
S0
S1
S2
S3
BACnet IP
Off
Off
Off
Off
BACnet MSTP
On
Off
Off
Off
Metasys N2
Off
On
Off
Off
Modbus TCP
On
On
Off
Off
S0 S1 S2 S3
S0 –S3 DIP Switches
S Bank DIP Switch Location
BACnet MS/TP, BACnet/IP, Modbus/TCP, and Metasys N2 Settings
for ProtoNode FPC-N34 (BACnet)
Figure 4: S Bank DIP Switches

Satec’s ProtoNode Startup Guide Page 10 of 41
ProtoCessor 1991 Tarob Court Milpitas, California 95035 USA Web: www.protocessor.com
Email: support@protocessor.com
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 address of the ProtoNode to a value between 1 to 127 (Master MAC
address); this is so that the BMS Front End can find ProtoNode via BACnet auto discovery.
Note: Never set a BACnet MS/TP MAC Address of the ProtoNode to a value from 128 to 255.
Addresses from 128 to 255 are Slave Addresses and can not be discovered by BMS Front Ends that
support Auto-Discovery of BACnet MS/TP devices.
Set “A” bank DIP switches A0 –A7 to assign a MAC Address to the ProtoNode for BACnet MS/TP.
Please refer to Appendix C for the complete range of MAC Addresses and DIP switch settings.
When using Metasys N2 and Modbus/TCP, the A Bank of DIP switches are disabled and not used.
They should be set to OFF.
NOTE: When setting DIP Switches, please ensure that power to the board is OFF.
Figure 5: MAC Address DIP Switches

Satec’s ProtoNode Startup Guide Page 11 of 41
ProtoCessor 1991 Tarob Court Milpitas, California 95035 USA Web: www.protocessor.com
Email: support@protocessor.com
2.4.2 BACnet MS/TP and BACnet/IP (FPC-N34): Setting the Device Instance (Node -ID)
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. (Section 2.4.2.1)
For example:
oNode_Offset value (default) = 50,000
oDevice 1 has a Modbus Node-ID of 1
oDevice 2 has a Modbus Node-ID of 22
oDevice 3 has a Modbus Node-ID of 33
oGiven that: Device Instance = Node_Offset + Node_ID
oDevice Instance, Device 1 = 50,000 + 1 = 50,001
oDevice Instance, Device 2 = 50,000 + 22 = 50,022
oDevice 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,000 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 4.3
oThis step cannot be performed until after the unit is connected and powered.
2.4.3 Metasys N2 or Modbus/TCP (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 Node_ID’s for the field protocols.
Metasys N2 and Modbus/TCP Node-ID Addressing: Metasys N2 and Modbus/TCP Node-ID’s range
from 1-255.

Satec’s ProtoNode Startup Guide Page 12 of 41
ProtoCessor 1991 Tarob Court Milpitas, California 95035 USA Web: www.protocessor.com
Email: support@protocessor.com
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
2.4.4.1 Baud Rate DIP Switch Selection
Baud
B0
B1
B2
B3
9600
On
On
On
Off
19200
Off
Off
Off
On
38400
On
On
Off
On
57600
Off
Off
On
On
76800
On
Off
On
On
Figure 7: Baud Rate
Figure 6: Baud Rate DIP Switches

Satec’s ProtoNode Startup Guide Page 13 of 41
ProtoCessor 1991 Tarob Court Milpitas, California 95035 USA Web: www.protocessor.com
Email: support@protocessor.com
3INTERFACING PROTONODE TO DEVICES
3.1 ProtoNode FPC-N34 and FPC-N35 Showing Connection Ports
Figure 8: ProtoNode BACnet FPC-N34 (upper) and ProtoNode FPC-N35 (lower)

Satec’s ProtoNode Startup Guide Page 14 of 41
ProtoCessor 1991 Tarob Court Milpitas, California 95035 USA Web: www.protocessor.com
Email: support@protocessor.com
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.
oThe 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 assignment
Pin RS-485 +
Pin 1
RS-485 +
Pin RS-485 -
Pin 2
RS-485 -
Pin GND
Pin 3
RS-485 GND
Power In (+)
Pin 4
V +
Power In (-)
Pin 5
V -
Frame Ground
Pin 6
FRAME GND
Figure 9: Power and RS-485 Connections

Satec’s ProtoNode Startup Guide Page 15 of 41
ProtoCessor 1991 Tarob Court Milpitas, California 95035 USA Web: www.protocessor.com
Email: support@protocessor.com
3.2.1 Biasing the Modbus RS-485 Network
An RS-485 network with more than one device needs to have biasing to ensure proper communication.
The biasing needs to be done on one device.
The ProtoNode has 530 Ohm resistors that can be used to set the biasing. The ProtoNode’s default
positions from the factory for the Biasing jumpers are OFF.
The OFF position is when the 2 RED biasing jumpers straddle the 4 pins closest to the outside of the
board of the ProtoNode. See Figure 10.
Only turn biasing ON:
oIF the BMS cannot see more than one device connected to the ProtoNode
oAND you have checked all the settings (Modbus COM settings, wiring, and DIP switches).
RS-485 Bias Switch
Figure 10: Modbus RS-485 Biasing Switch on the ProtoNode N34 (left) and ProtoNode N35 (right)

Satec’s ProtoNode Startup Guide Page 16 of 41
ProtoCessor 1991 Tarob Court Milpitas, California 95035 USA Web: www.protocessor.com
Email: support@protocessor.com
3.2.2 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.
On short cabling runs the EOL switch does not to need to be turned ON. The default setting for this Blue
EOL switch is OFF.
If the ProtoNode is placed at one of the ends of the trunk, you turn the Blue RS-485 End-of- Line
Terminating switch to ON position.
Always leave the single Red Jumper in the A position (default factory setting).
Modbus RS-485 EOL Switch
Leave in A Position
Figure 11: Modbus RS-485 End-Of-Line Termination Switch on the ProtoNode N34 (left) and
ProtoNode N35 (right)

Satec’s ProtoNode Startup Guide Page 17 of 41
ProtoCessor 1991 Tarob Court Milpitas, California 95035 USA Web: www.protocessor.com
Email: support@protocessor.com
3.3 BACnet MS/TP or Metasys N2 (FPC-N34): Wiring Field Port to RS-485 Network
Connect the BACnet MS/TP or Metasys N2 RS-485 network wires to the 3-pin RS-485 connector on
ProtoNode FPC-N34 as shown below in Figure 12.
oThe RS-485 GND (Pin 3) is not typically connected.
See Section 4.3 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 (See Figure 13). It is disabled by default.
3.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.
BMS RS-485
Wiring
ProtoNode
Pin #
Pin
Assignment
RS-485 +
Pin 1
RS-485 +
RS-485 -
Pin 2
RS-485 -
-
Pin 3
RS-485 GND
Figure 12: Connection from ProtoNode to RS-485 Field Network
Figure 13: RS-485 EOL Switch
Figure 14: LonWorks Terminal
End-of-Line Switch
G
-
+

Satec’s ProtoNode Startup Guide Page 18 of 41
ProtoCessor 1991 Tarob Court Milpitas, California 95035 USA Web: www.protocessor.com
Email: support@protocessor.com
3.5 Connecting Power to ProtoNode.
Apply power to ProtoNode. Ensure that the power supply used complies with the specifications provided in
Appendix D.1. Ensure that the cable is grounded using the “Frame-GND” terminal. ProtoNode accepts
either 9-30VDC or 12-24 VAC.
Power Requirement for ProtoNode at 9V through 30 VDC or 12-24 VAC
Current 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
100mA
90mA
FPC –N35 (Maximum)
250mA
130mA
100mA
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 15: Required current draw for the ProtoNode
Power to
ProtoNode
ProtoNode
Pin #
Pin
Assignment
Power In (+)
Pin 4
V +
Power In (-)
Pin 5
V -
Frame Ground
Pin 6
FRAME GND
Figure 16: Power Connections

Satec’s ProtoNode Startup Guide Page 19 of 41
ProtoCessor 1991 Tarob Court Milpitas, California 95035 USA Web: www.protocessor.com
Email: support@protocessor.com
4USE PROTONODE’S WEB CONFIGURATOR TO SELECT DEVICE PROFILES
4.1 Connect the PC to ProtoNode via the Ethernet Port
Connect a standard CAT5 Ethernet cable (Straight through or Cross-Over) between the PC and
ProtoNode
The Default IP Address of ProtoNode is 192.168.1.24, Subnet Mask is 255.255.255.0. If the PC and
ProtoNode are on different IP Networks, assign a static IP Address to the PC on the 192.168.1.xxx
network
Go to > >
Right-click on Local Area Connection > Properties
Highlight >
Select: Use the following IP address
Click twice
Figure 17: Ethernet Port Location
Ethernet
Port

Satec’s ProtoNode Startup Guide Page 20 of 41
ProtoCessor 1991 Tarob Court Milpitas, California 95035 USA Web: www.protocessor.com
Email: support@protocessor.com
4.2 Connecting to ProtoNode’s Web Configurator
After setting your PC to be on the same subnet as the ProtoNode (Section 4.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.
4.2.1 Selecting Profiles for Devices Connected to ProtoNode
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; see Figure 21.
To add an active profile to support a device, click the ADD button under Active Profiles. This will present a
drop-down box underneath the Current Profile column that lists all the available profiles. See Figure 19.
oFor FPC-N34 units, profiles for supported devices will be offered in the drop-down box only for
the Field protocol option selected with the S bank of DIP switches in Section 2.3.
oFor FPC-N35 units, profiles for supported devices will be offered in the drop-down box for the
Field protocol LonWorks.
For every device that is added, you need to specify the Node-ID assigned to the particular device.
This specification must match the device’s network settings.
Figure 18: Web Configurator Showing no Active Profiles
This manual suits for next models
1
Table of contents
Other ProtoCessor Gateway manuals