KEPCO SUPERtrol II User guide

990375 05/05/17
Document Revision: 2.A
Web Congurator Template
Revision: 61
APPLICABILITY & EFFECTIVITY
Explains hardware specications, setup instructions and usage.
The instructions are effective for the above as of August 2016.
Multi-Protocol Communication Card (COM CARD)
Start-up Guide
For Interfacing KEP Products: SUPERtrol_II, SUPERtrol_I,
LEVELtrol_II, ES762-ST2
To Building Automation Systems:
BACnet MS/TP, BACnet/IP, Modbus TCP/IP, Metasys N2,
EtherNet/IP, DF1 and LonWorks

KEP Multi-Protocol Communication Card Option Start-up Guide
Page 2
Technical Support
Support Contact Information:
Kessler-Ellis Products
10 Industrial Way East Eatontown,
NJ 07724
Customer Service:
(800) 631 – 2165
(732) 935 – 1320
Email: [email protected]
Website: www.KEP.com

KEP Multi-Protocol Communication Card Option Start-up Guide
Page 3
Quick Start Guide
1. Record the information about the unit. (Section 3.1)
2. Set the device’s Modbus RTU serial settings (i.e. baud rate, parity, stop bits) and Modbus
Node-ID for the device connected to the COM CARD. (Section 3.3)
3. Metasys N2 or Modbus TCP/IP: Set the Node-ID. (Section 3.3.2)
4. Connect COM CARD 4 pin RS-485 port to the Field Protocol cabling, (Section 4.2) for LonWorks
port (Section 4.3)
5. Use a browser to access the embedded tool, which is referred to in this manual as the Web
Congurator, to select the device that will be attached to COM CARD and set the Modbus
Node-ID. Once the device is selected, the COM CARD Automatically builds and loads the
Conguration. (Section 5)
6. BACnet/IP or Modbus TCP/IP (Option 3): Use a browser to access the COM CARD Web
Congurator to change the IP Address. No changes to the conguration are necessary. (Section
5.4)
7. LonWorks (Option 4): The COM CARD must be commissioned on the LonWorks Network. This
needs to be done by the LonWorks administrator using a LonWorks Commissioning tool.
(Section 8)

KEP Multi-Protocol Communication Card Option Start-up Guide
Page 4
TABLE OF CONTENTS
1 CERTIFICATIONS ....................................................................................................................................................... 6
1.1 BTL Mark – BACnet Testing Laboratory .............................................................................................................. 6
1.2 LonMark Certication ............................................................................................................................................ 6
2 INTRODUCTION ......................................................................................................................................................... 7
2.1 COM CARD Gateway ......................................................................................................................................... 7
3 SETUP FOR COM CARD ........................................................................................................................................... 8
3.1 Record Identication Data .................................................................................................................................... 8
3.2 Point Count Capacity and Registers per Device .................................................................................................. 8
3.3 Conguring Device Communications ................................................................................................................... 9
3.3.1 Input COM Settings for all Devices with an Inserted COM CARD ..................................................................... 9
3.3.2 Set Modbus Node-ID for the Device ................................................................................................................... 9
4 INTERFACING COM CARD TO DEVICE ................................................................................................................. 10
4.1 Connection Ports ................................................................................................................................................ 10
4.2 BACnet MS/TP or Metasys N2 (Option 3): Wiring Field Port to RS-485 Network .......................................11
5 USE COM CARD WEB CONFIGURATOR TO SETUP THE GATEWAY ................................................................. 12
5.1 Connect the PC to COM CARD via the Ethernet Port ........................................................................................ 12
5.2 Connecting to COM CARD Web Congurator ..................................................................................................... 13
5.3 Selecting Proles for Device Connected to COM CARD .................................................................................... 13
5.4 BACnet/IP and Modbus TCP/IP: Setting IP Address for Field Network ............................................................... 15
5.5 Select Field Protocol ........................................................................................................................................... 17
5.5.1 BACnet/IP Conguration ................................................................................................................................. 17
5.5.2 BACnet MS/TP Conguration ........................................................................................................................... 18
5.5.3 Metasys N2, Modbus TCP and EtherNet/IP Conguration .............................................................................. 19
5.5.4 DF1 Conguration ........................................................................................................................................... 19
6 BACNET MS/TP AND BACNET/IP: SETTING NODE_OFFSET TO ASSIGN SPECIFIC DEVICE INSTANCES . 20
7 HOW TO START THE INSTALLATION OVER: CLEARING PROFILES .................................................................. 21
8 LONWORKS (Option 4): COMMISSIONING COM CARD ON A LONWORKS NETWORK ................................ 22
8.1 Commissioning COM CARD on a LonWorks Network ........................................................................................ 22
8.1.1 Instructions to Download XIF File from COM CARD Using Browser ................................................................ 22
9 BACNET EXPLORER ............................................................................................................................................... 24
Appendix A. Troubleshooting .................................................................................................................................... 25
Appendix A.1. Lost or Incorrect IP Address ............................................................................................................... 25
Appendix A.2. Viewing Diagnostic information ........................................................................................................... 26
Appendix A.3. Check Wiring and Settings ................................................................................................................. 27
Appendix A.4. LED Diagnostics for Communications Between COM CARD and Device ......................................... 28
Appendix A.5. Take Diagnostic Capture With the FieldServer Toolbox ...................................................................... 29
Appendix A.6. Update Firmware ................................................................................................................................. 32
Appendix A.8. Reading Data Arrays ........................................................................................................................... 33
Appendix B. Vendor Information - KEP ..................................................................................................................... 34
Appendix B.2. SUPERtrol_I Modbus RTU Mappings to BACnet, Metasys N2, EtherNet/IP, DF1,Modbus TCP/IP and
LonWorks ......................................................................................................................................................................... 36
Appendix B.3. LEVELtrol_II Modbus RTU Mappings to BACnet, Metasys N2, EtherNet/IP, DF1, Modbus TCP/IP and
LonWorks ......................................................................................................................................................................... 37
Appendix B.4. ES762-ST2 Modbus RTU Mappings to BACnet, Metasys N2, EtherNet/IP, DF1, Modbus TCP/IP and
LonWorks ...................................................................................................................................................................... 38
Appendix C. Reference ............................................................................................................................................... 40
Appendix C.1. Specications ....................................................................................................................................... 40
Appendix D. Limited 2 Year Warranty ........................................................................................................................ 41

KEP Multi-Protocol Communication Card Option Start-up Guide
Page 5
NOTES

KEP Multi-Protocol Communication Card Option Start-up Guide
Page 6
1 CERTIFICATIONS
1.1 BTL Mark – BACnet Testing Laboratory
1.2 LonMark Certication
The BTL Mark on the COM CARD is a symbol that indicates that a product has
passed a series of rigorous tests conducted by an independent laboratory which
veries 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 International is the recognized authority for certication, education,
and promotion of interoperability standards for the benet of manufacturers,
integrators and end users. LonMark International has developed extensive
product certication standards and tests to provide the integrator and user with
condence that products from multiple manufacturers utilizing LonMark de-
vices work together.

KEP Multi-Protocol Communication Card Option Start-up Guide
Page 7
2 INTRODUCTION
2.1 PCOM CARD
The COM CARD option is an internal, high performance Building Automation multi-protocol gate-
way that is precongured to automatically communicate between KEP’s products (hereafter called
“device”) connected to the COM CARD and automatically congures them for BACnet®1MS/TP, BAC-
net/IP, Metasys®2N2 by JCI, Modbus TCP/IP, EtherNet/IP, DF1 or LonWorks®3.
It is not necessary to download any conguration les to support the required applications.
The COM CARD is pre-loaded with tested Proles/Congurations for the supported devices.
1BACnet is a registered trademark of ASHRAE
2Metasys is a registered trademark of Johnson Controls Inc.
3LonWorks is a registered trademark of Echelon Corporation

KEP Multi-Protocol Communication Card Option Start-up Guide
Page 8
3 SETUP FOR COM CARD
3.1 Record Identication Data
3.2 Point Count Capacity and Registers per Device
Each unit 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.
Record Your Model Number Below: Example: ST2 O 1 3 BAC/IP P
MODEL NO. __________________________________________________________________
• Option 3 units have the following 2 ports: Ethernet + RS-485
• Option 4 units have the following 2 ports: LonWorks + Ethernet
The total number of Registers presented by the device attached to the COM CARD cannot
exceed:
Model Protocols Supported
Option 3 (Specify Protocol) BACnet IP, BACnet MS/TP, Modbus TCP/IP, Meyasys
N2, AB DF1, AB Ethernet/IP
Option 4 (LonWorks) LonWorks
COM CARD Option Part Numbers
Part number Total Registers
Option 3 1,500
Option 4 1,500
Figure 2: Supported Point Count Capacity
Devices Registers Per Device
SUPERtrol_II 116
SUPERtrol_I 64
LEVELtrol_II 40
ES762-ST2 126
Figure 3: Registers per Device

KEP Multi-Protocol Communication Card Option Start-up Guide
Page 9
3.3 Conguring Device Communications
3.3.1 Input COM Settings for all Devices with an Inserted COM CARD
3.3.2 Set Modbus Node-ID for the Device
• Set Modbus Node-ID for the device the COM CARD is plugged into. The Modbus Node-ID needs to
be uniquely assigned between 1 and 255.
oThe Modbus Node-ID that is assigned for the device needs to be documented
 The Modbus Node-ID assigned is used for designating the Device Instance for BAC-
net/IP and BACnet MS/TP (Section 6)
• The Metasys N2 and Modbus TCP/IP eld protocol Node-IDs are automatically set to be the
same value as the Node-ID of the Modbus RTU device.
•Set the serial device that the COM CARD is plugged into to have the same Baud Rate,
Data Bits, Stop Bits, and Parity settings as the COM CARD.
•Figure 4 species the device serial port settings required to communicate with the COM CARD.
Port Setting Device
Protocol Modbus RTU
Baud Rate 9600
Parity None
Data Bits 8
Stop Bits 1
Figure 4: COM Settings

Quad Digital Input
(ES762 only) RS-485
Ethernet
RS-232
KEP Multi-Protocol Communication Card Option Start-up Guide
Page 10
4 INTERFACING COM CARD TO DEVICE
4.1 Connection Ports

BMS RS-485 Wiring Flow Computer COM Card
Pin # Pin
Assignment
RS-485 + Pin 4 RS-485 +
RS-485 – Pin 3 RS-485 –
End Of Line Termination Pin 2 Terminating Resistor
- Pin 1 RS-485 GND
KEP Multi-Protocol Communication Card Option Start-up Guide
Page 11
4.2 BACnet MS/TP or Metasys N2 (Option 3): Wiring Field Port to RS-485 Network
Figure 6: Connection from COM CARD to RS-485 Field Network
• Connect the BACnet MS/TP or Metasys N2 RS-485 network wires to the 4-pin RS-485 connector on
COM CARD Terminal Block as shown below in Figure 6.
o The RS-485 GND (Pin 1) is not typically connected
•See Section 5.4 for information on connecting to BACnet/IP network.
• If the COM CARD is the last device on the BACnet MS/TP or Metasys N2 trunk, then the End-
Of-Line Terminating resistor (180 Ω) needs to be activated by placing a jumper from terminal pin
2 to terminal pin 3 on the multidrop cable end station.

KEP Multi-Protocol Communication Card Option Start-up Guide
Page 12
5 USE COM CARD WEB CONFIGURATOR TO SETUP THE GATEWAY
5.1 Connect the PC to COM CARD via the Ethernet Port
• Connect a CAT5 Ethernet cable (Straight through or Cross-Over) between the local PC and
COM CARD Ethernet Port.
• The Default IP Address of COM CARD is 192.168.1.24, Subnet Mask is 255.255.255.0. If the PC
and COM CARD 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 or later:
Go to > >
> >
Right-click on Local Area Connection > Properties
Highlight >
• For Windows XP and Windows 7, use the following IP Address:
• Click twice.

KEP Multi-Protocol Communication Card Option Start-up Guide
Page 13
5.2 Connecting to COM CARD Web Congurator
• After setting a local PC on the same subnet as the COM CARD (Section 5.1), open a web
browser on the PC and enter the IP Address of the COM CARD; the default address is
192.168.1.24.
NOTE: If the IP Address of the COM CARD has been changed by previous conguration, the assigned
IP Address can be discovered using the FS Toolbox utility. See Appendix A.1 for instructions.
5.3 Selecting Proles for Device Connected to COM CARD
Figure 9: Web Congurator Showing no Active Proles
• In the Web Congurator, the Active Proles section is shown on the lower left side of the screen.
• The Active Proles section lists the currently active device proles, including previous Web
Congurator additions. This list will be empty for new installations, or after clearing all con-
gurations. (Figure 9)
• To add an active prole to support a device, click the ADD button under Active Proles. This will
present a drop-down box underneath the Current Prole column that lists all the available proles.
(Figure 10)
• For every device that is added, assign a unique Modbus Node-ID. This specication must match the
device’s network settings.

KEP Multi-Protocol Communication Card Option Start-up Guide
Page 14
Figure 10: Web Congurator Showing Available Proles for Selection
Figure 11: Web Congurator Showing Active Prole Additions
• Once the Prole for the device has been selected from the drop-down list, enter the value of the de-
vice’s Modbus Node-ID which was assigned in Section 3.3.2.
• Then press the “Submit” button to add the Prole of the device to be congured.
• Completed additions will be listed under “Active Proles” as shown in Figure 11.

KEP Multi-Protocol Communication Card Option Start-up Guide
Page 15
5.4 BACnet/IP and Modbus TCP/IP: Setting IP Address for Field Network
• After setting a local PC to the same subnet as the COM CARD (Section 5.1), open a web
browser on the PC and enter the IP Address of the COM CARD; the default address is
192.168.1.24.
• The Web Congurator is displayed as the landing page. (Figure 12)
•To access the Web GUI, click on the “Diagnostics & Debugging” button in the bottom right side
of the page.
Figure 12: Web Congurator Screen with Active Proles

KEP Multi-Protocol Communication Card Option Start-up Guide
Page 16
Figure 13: Changing IP Address via Web GUI
• From the Web GUI landing page, click on “Setup” to expand the navigation tree and then select
“Network Settings” to access the IP Settings menu. (Figure 13)
• Modify the IP Address (N1 IP Address eld) of the COM CARD Ethernet port.
• If necessary, change the Netmask (N1 Netmask eld).
• Type in a new Subnet Mask.
• If necessary, change the IP Gateway (Default Gateway eld).
• Type in a new IP Gateway.
NOTE: If the COM CARD is connected to a router, the IP Gateway of the COM CARD should be set to
the IP Address of that router.
• Reset COM CARD.
• Unplug Ethernet cable from PC and connect it to the network hub or router.
• Record the IP Address assigned to the COM CARD for future reference.

KEP Multi-Protocol Communication Card Option Start-up Guide
Page 17
5.5 Select Field Protocol
5.5.1 BACnet/IP Conguration
Figure 14: Web Congurator Showing BACnet/IP Conguration
For Option 3 – Use the Protocol Selector by typing in the corresponding number next to the desired
protocol:
o BACnet/IP 1
o BACnet MS/TP 2
o Metasys N2 3
o Modbus TCP/IP 4
o EtherNet/IP 5
o DF1 6
Then click “System Restart” to bring up options to congure the desired protocol.
For Option 4 – There are no device details to be entered for this protocol combination.
• Enter the appropriate details for BACnet/IP:

KEP Multi-Protocol Communication Card Option Start-up Guide
Page 18
5.5.2 BACnet MS/TP Conguration
• Enter the appropriate details for BACnet MS/TP:
Figure 15: Web Congurator Showing BACnet MS/TP Conguration

KEP Multi-Protocol Communication Card Option Start-up Guide
Page 19
5.5.3 Metasys N2, Modbus TCP and EtherNet/IP Conguration
5.5.4 DF1 Conguration
Figure 16: Web Congurator Showing Metasys N2 Conguration
Figure 17: Web Congurator Showing DF1 Conguration
• There are no Web Congurator Parameters for Metasys N2, Modbus TCP/IP or EtherNet/IP:
• Enter the appropriate details for DF1:

KEP Multi-Protocol Communication Card Option Start-up Guide
Page 20
6 BACNET MS/TP AND BACNET/IP: SETTING NODE_OFFSET TO ASSIGN SPECIFIC
DEVICE INSTANCES
Figure 18: Active Proles with Node-ID
• After setting a local PC to be on the same subnet as the COM CARD (Section 5.1), open a web
browser on the PC and enter the IP Address of the COM CARD; the default address is
192.168.1.24.
o If the IP Address of the COM CARD has been changed by previous conguration, the
assigned IP Address must be gathered from the network administrator. o
The Web Congurator is displayed as the landing page. (Section 5.5)
• The Node_Offset eld shows the current value (default = 50,000).
o The values allowed for a BACnet Device Instance can range from 1 to 4,194,303.
• To assign a specic Device Instance (or range); change the Node_Offset value as needed using the
calculation below:
Device Instance (desired) = Node_Offset + Modbus Node_ID
For example, if the desired Device Instance for the device is 1,001 and the device has a Modbus
Node-ID of 1 then:
1,001 = Node_Offset + 1
1,000 = Node_Offset
• Enter the decided upon Node_Offset and click “Submit”.