Micro control systems MCS-BMS-GATEWAY-see User manual

MCS Total
Solution
for all your
Control
Needs Energy Ecient and
RoHS Compliant
5580 Enterprise Pkwy.
Fort Myers, FL 33905
O󰀩ce: 239-694-0089
Fax: [phone]
www.mcscontrols.com
BMS COMMUNICATION
MCS-BMS-GATEWAY
For Interfacing MCS-MAGNUM to:
Building Automation Systems Protocols:
MCS, Modbus RTU, Modbus IP, Ethernet,
BACnet IP, BACnet MS/TP, N2, *LonWorks
Manual supports the following:
MCS-BMS-GATEWAY - see Chapter 4 & 5 for installation
MCS-BMS-GATEWAY-NL-see Chapter 4 & 5 for installation
MCS-BMS-GATEWAY-N54-see Chapter 6 for installation
MCS-MAGNUM
Rev. 3.5 May 24, 2022
Ethernet
Building
Management
System
MCS-Touch
Internet
Router
MCS-BMS-Gateway Models
RS485
• MCS-BMS-GATEWAY
with LonWorks
• MCS-BMS-GATEWAY-NL
(NO LonWorks)
• MCS-BMS-GATEWAY-N54
(NO LonWorks)
RS485
OR

2
The MCS Commitment is to provide practical solutions for the industries
needs and to be both a leader and partner in the e󰀨ective use of
microprocessor controls.
Micro Control Systems, Inc.
5580 Enterprise Parkway
Fort Myers, Florida 33905
PH:[phone] FAX:[phone]
www.mcscontrols.com
All information contained within this document is considered to be proprietary information of Micro Control Systems, Inc.
No information or data from this document shall be published, used, reproduced, transmitted, or disclosed to others outside your
organization without the prior expressed written consent of Micro Control Systems, Inc. This document and the information
contained herein shall be treated as proprietary. Reasonable provisions shall be provided to ensure that this information
remains proprietary by your employees, agents, and other personnel that may have access to this document.
Copyright ©2022
Date Author Description of Changes
4-12-16 DEW Restructured manual
4-14-16 DEW Changes made from Ray
7-8-16 DEW Merge MCS-BMS-GATEWAY VER 2.0
10-03-16 DEW Update drawings, revised back startup section
12-27-16 DEW Creating CSV Files
11-30-17 DEW Remove address 0 in dip switch settings
8-14-17 DEW Added Alarm BMS info
10-31-19 DEW Update photos to new style
11-19-19 DEW Add Modbus IP to RTU
1-29-2020 DEW Change baud rate for Metasys N2 to 9600
04-12-2021 DEW Changes made from startup guide
08-17-2021 DEW CREATE MANUAL FOR MCS-BMS-GATEWAY-NL
01-27-2022 DEW COMBINE 3 BMS-GATEWAYS INTO ONE MANUAL
04-14-2022 DEW Minor changes to photos, etc
05-24-2022 DEW Add complete section on N54 install, etc. PDF
Revision/Disclaimer Page
MCS-MAGNUM-BMS

3
Table of Contents
Chapter - 1. MCS-BMS-GATEWAYS .......................................................................................................5
1.1. MCS-BMS-GATEWAY (Model with LonTalk) ...............................................................................................5
1.1.1 LONTALK Protocol..............................................................................................................................5
1.2. MCS-BMS-GATEWAY-NL (Model NO LonTalk) ...........................................................................................5
1.3. MCS-BMS-GATEWAY-N54 (Model NO LonTalk) .........................................................................................5
Chapter - 2. NETWORK PROTOCOLS ..................................................................................................6
2.1. MCS-MAGNUM BMS PROTOCOLS............................................................................................................6
2.1.1 BACnet OVER IP PROTOCOL...........................................................................................................6
2.1.2 ETHERNET NETWORK PROTOCOL ................................................................................................6
2.1.3 MODBUS RTU PROTOCOL...............................................................................................................7
2.1.4 MODBUS TCP/IP PROTOCOL...........................................................................................................7
2.2. PROTOCOLS USING MCS-BMS-GATEWAY ..............................................................................................7
2.3. Protocols MCS controllers support: ..............................................................................................................8
2.4. MCS-MAGNUM USING RS-485 ..................................................................................................................9
2.5. Wiring Multiple MCS Controllers.................................................................................................................10
2.6. EXAMPLE NETWORK ...............................................................................................................................11
2.6.1 Standalone MCS-Magnum ...............................................................................................................11
2.6.2 MULTIPLE MCS-MAGNUM ENCLOSURES ....................................................................................12
2.7. MULTIPLE MCS-MAGNUM BMS RS485 WIRING DIAGRAM..................................................................13
Chapter - 3. MCS-BMS-GATEWAY & NL FIELDSERVER TOOLBOX ................................14
Chapter - 4. Setup-MCS-BMS-GATEWAY & GATEWAY-NL .......................................................17
4.1. Record Identication Data ..........................................................................................................................17
4.2. Conguring Device Communications .........................................................................................................17
4.2.1 Set COM settings on all Devices Connected to the MCS-BMS-GATEWAY .....................................17
4.2.2 Set IP Address for each MCS-MAGNUM connected to the MCS-BMS-GATEWAY .........................17
4.3. BMS Network Settings: ..............................................................................................................................18
4.3.1 BACnet MS/TP, N2 and Modbus IP to RTU......................................................................................18
Figure 5 Protocol Selection Switch Tables........................................................................................................18
4.3.2 BACnet MS/TP: Setting the MAC Address for BMS Network ...........................................................18
4.3.3 BACnet MS/TP and BACnet/IP: Setting the Device Instance ..........................................................19
4.3.4 Metasys N2: Setting the Node-ID .....................................................................................................19
4.3.5 BACnet MS/TP: Setting the Serial Baud Rate for BMS Network......................................................19
4.3.5.1. Baud Rate DIP Switch Selection ..........................................................................................20
Chapter - 5. Interfacing MCS-BMS-GATEWAY to Devices .........................................................21
5.1. MCS-BMS-GATEWAY Connection Ports....................................................................................................21
5.2. Wiring diagram for connecting the MCS-Magnum......................................................................................22
5.3. Device Connections to MCS-BMS-GATEWAY ...........................................................................................23
5.4. MCS-MAGNUM Address Settings ..............................................................................................................23
5.5. Biasing the RS-485 Device Network ..........................................................................................................25
5.6. End of Line Termination Switch for the Modbus RS-485 Device Network..................................................25
5.7. Power-Up MCS-BMS-GATEWAY ...............................................................................................................26
Chapter - 6. MCS-BMS-GATEWAY-N54 START-UP GUIDE ........................................................27
Chapter - 7. BMS SWITCH SETTINGS ...............................................................................................54
7.1. BMS Address DIP Switch Settings .............................................................................................................54
Chapter - 8. APPENDIX - INPUT / OUTPUT POINTS / STATES ..............................................60
8.1. Sensor Input Points ....................................................................................................................................60
8.2. Relay Output Points....................................................................................................................................61
8.3. ANALOG Output Points..............................................................................................................................62
8.4. Setpoints.....................................................................................................................................................62
8.5. Chiller/Compressor States..........................................................................................................................62
8.6. Other Points................................................................................................................................................63
8.7. Network inputs to MCS-MAGNUM .............................................................................................................66
8.8. MCS Capacity Control State Chart.............................................................................................................67

4
8.9. MCS Compressor Control State Chart .......................................................................................................67
Chapter - 9. ALARMS- UNIT/COMPRESSOR / MODBUS ...........................................................68
9.1. Unit Alarms .................................................................................................................................................68
9.2. Compressor Alarms ....................................................................................................................................69
9.3. MODBUS Alarms........................................................................................................................................71
Chapter - 10. CREATING CSV FILES USING MCS-CONFIG .......................................................76
9.4. How to Create CSV Files:...........................................................................................................................76

5
Chapter - 1. MCS-BMS-GATEWAYS
The MCS-BMS-GATEWAY is a microprocessor based communication device that provides protocol translation from
di󰀨erence protocols. Information that can be transmitted includes the status of control points, alarm information, digital
inputs, analog inputs or setpoints.
The MCS-BMS-GATEWAY protocol is eld selectable by setting jumper on the device.
Using MCS-CONFIG and the CONFIG le for the MCS-MAGNUM, you can automatically create the program that is re-
quired by the MCS-BMS-GATEWAY. Then using a web browser you can download the program into the unit.
The MCS-BMS-GATEWAY can receive changes from the network to enable or disable the Network Run/Stop indicator.
Adjustments can also be made to the Cooling Target (Setpoint #1) of a MCS-MAGNUM.
MCS is currently shipping 3 dierence MCS-BMS-GATEWAYS
MCS-BMS-GATEWAY USE CHAPTER 4 AND 5 FOR INSTALLATION
1.1. MCS-BMS-GATEWAY (Model with LonTalk)
Supports BACnet®1 MS/TP, Metasys®2 N2 by JCI, LonWorks®3 and
Modbus IP to RTU.
Communication Rate ......... 19,200 bps
1.1.1 LONTALK Protocol
When the MCS-BMS-GATEWAY is setup for LONTALK, it is capable
of being congured by Network Management Tools such as LonMaker. For binding (implicit mode), a Net-
work Management Tool is necessary to create the bindings.
It is possible to place a MCS-BMS-GATEWAY into a Network for explicit communications without using a Net-
work Management Tool, but this requires intimate knowledge of the network in question.
The external interface le (.XIF) for the MCS-BMS-GATEWAY can be uploaded from the MCS-BMS-GATE-
WAY for the particular application. The MCS-BMS-GATEWAY di󰀨ers from most other LonWorks devices in
that its XIF le is not xed due to varying applications.
MCS-BMS-GATEWAY-NL USE CHAPTER 4 AND 5 FOR INSTALLATION
1.2. MCS-BMS-GATEWAY-NL (Model NO LonTalk)
Supports BACnet®1 MS/TP, Metasys®2 N2 by JCI, and Modbus IP
to RTU.
Communication Rate ......... 19,200 bps
MCS-BMS-GATEWAY-N54 USE CHAPTER 6 FOR INSTALLATION
1.3. MCS-BMS-GATEWAY-N54 (Model NO LonTalk)
Supports BACnet®1 MS/TP, Metasys®2 N2 by JCI, and Modbus IP to RTU.
Communication Rate ......... 9600, 19200, 38400, 57600,76800, 115000
Features and Benets:
• Ethernet
• RS-485 & RS-232
• On-board diagnostics allow easy troubleshooting for both serial and Ethernet
communications.
• One MCS-BMS-GATEWAY-N54 connects multiple Serial and Ethernet devices.
• Supports up to 10,000 device points.
• Can support OEM proprietary protocols to building management systems.

6
Chapter - 2. NETWORK PROTOCOLS
2.1. MCS-MAGNUM BMS PROTOCOLS
The following Protocols are available with the Magnum. Changes can be made to the settings using the Keypad or
can be made using MCS-CONNECT SERVICE WINDOW.
1. BACnet IP
2. MCS PROTOCOL
3. MODBUS RTU PROTOCOL
4. ETHERNET PROTOCOL (this protocol is always active)
5. MODBUS IP (this protocol is always active)
2.1.1 BACnet OVER IP PROTOCOL
The BACnet DEVICE ID is a ve-digit number. The rst three digits are based on MCS’s BACnet Vendor ID 181, and the
last two are set by the BACnet/MS/TP address.
181 XX
↓↓
BACnet BACnet IP
Vendor181 Address
In case the end user would like to set up an ID other than 181-XX, there is an extended BACnet setting that can only be
set in MCS Cong.
The following changes can be made using the Keypad or can be made using MCS-CONNECT
SERVICE WINDOW.
The BACnet IP address can be veried and changed (with the proper authorization code) from the Keypad/LCD. The
following steps will display the BACnet IP Network address, and the the TCP/IP port:
Press the Menu key, select Serv Tools, and then press the Enter key.
Use arrow to BACnet Setting then press Enter.
Select address then press Enter. Change the address so it matches the last two digits of the device
ID then press Enter.
Use arrow to tab to the TCP/IP address.
Select address then press Enter. Change the address and port to match your device.
2.1.2 ETHERNET NETWORK PROTOCOL
The following steps will display the ETHERNET NETWORK settings:
If you are going to manually assign the IP Address, Subnet Mask, and Default Gateway.
Press the Menu key, select Serv Tools, and then press the Enter key.
Select Ethernet Network then press Enter.
Set “DYNAMIC IP” to NO.
Set the “IP Address”.
Set the “Subnet Mask”.
Set “Default Gateway”.
Reset Magnum for change to take e󰀨ect.
If you are going to let your network assign the IP Address, Subnet Mask, and Default Gateway:
Press the Menu key, select Serv Tools, and then press the Enter key.
Select Ethernet Network then press Enter.
Set “DYNAMIC IP” to YES.
Connect the MCS-Magnum to the network and power up the board.

7
2.1.3 MODBUS RTU PROTOCOL
The Modbus RTU address can be veried and changed (with the proper authorization code) from the keypad/LCD or
can be made using MCS-CONNECT SERVICE WINDOW..
The following steps will display the Modbus RTU Network address, and the Baud Rate:
Press the Menu key, select Serv Tools, and then press the Enter key.
Select RS485 Network then press Enter.
Select Protocol then press Enter. Change the protocol to Modbus RTU.
Select address then press Enter. Change the address then press Enter.
Select Baud then press Enter. Set the baud rate then press Enter.
Connect the communication wires to the TX RS485 three-position terminal located above the Ethernet
connector.
Reset Magnum for change to take e󰀨ect.
2.1.4 MODBUS TCP/IP PROTOCOL
This protocol is always active.
Make sure the MCS-Magnum network settings are set correctly.
If you are going to manually assign the IP Address, Subnet Mask, and Default Gateway.
Press the Menu key, select Serv Tools, and then press the Enter key.
Select Ethernet Network then press Enter.
Set “DYNAMIC IP” to NO.
Set the “IP Address”.
Set the “Subnet Mask”.
Set “Default Gateway”.
Reset Magnum for change to take e󰀨ect.
If you are going to let your network assign the IP Address, Subnet Mask, and Default Gateway:
Press the Menu key, select Serv Tools, and then press the Enter key.
Select Ethernet Network then press Enter.
Set “DYNAMIC IP” to YES.
Connect the MCS-Magnum to the network and power up the board.
2.2. PROTOCOLS USING MCS-BMS-GATEWAY
The MCS-BMS-GATEWAY is a microprocessor based communication device that provides translation from
BACnet IP to BACnet MS/TP, or Johnson Control N2.
Information that can be transmitted includes the status of control points, alarm information, digital inputs, ana-
log inputs or setpoints.
For more information on the MCS-BMS-GATEWAY please go to www.mcscontrols.com.
Network protocols are formatting rules that specify how data is sent and received between devices.
Protocols are necessary for devices to interact with each other.

8
2.3. Protocols MCS controllers support:
1. BACnet
2. MODBUS RTU
3. ETHERNET
4. MCS
5. JOHNSON N2
MCS Network Protocol Support
Magnum MicroMag
BACnet MCS BACnet RouterR2
Modbus IP In Development
MCS IP MCS-Ethernet
Modbus RTU  
MCS 485  
BACnet MS/IP MCS-BMS-Gateway 
Johnson N2 MCS-BMS-Gateway MCS-BMS-Gateway
=Built in Support
Required MCS-BMS GATEWAY
Over
Ethernet
Over
RS485

9
2.4. MCS-MAGNUM USING RS-485
Using the RS485, the MCS-Magnum can be connected to the BMS (Modbus RTU or MCS 485)
RS485
.
.
.
MCS-MAGNUM
MCS-MAGNUM
MCS-MAGNUM
Building
Management
System

10
2.5. Wiring Multiple MCS Controllers
Using the RS485, the network must be wired controller to controller
Star congurations not allowed
Up to 30 controllers can be wired togetherMCS-MAGNUM USING ETHERNET
04-14-2022
B

11
Using the Ethernet, the MCS-Magnum can be connected to:
BMS (BACnet IP or Modbus IP)
MCS-Touch (MCS-Connect)
PC (MCS-Connect)
Internet access through router (which allows connection via MCS-Connect from anywhere)
2.6. EXAMPLE NETWORK
2.6.1 Standalone MCS-Magnum
MCS-Touch
BMS (Johnson N2 or BACnet MS/TP)
Internet Access
Ethernet
Or
Or
Or
Ethernet
Building
Management
System
MCS-Touch
Internet
Router
MCS-BMS-Gateway-NL
RS485 or
LonWorks

12
2.6.2 MULTIPLE MCS-MAGNUM ENCLOSURES
Internet Access
BMS (BACnet IP or Modbus IP)

13
2.7. MULTIPLE MCS-MAGNUM BMS RS485 WIRING DIAGRAM
04-14-2022
C

14
Chapter - 3. MCS-BMS-GATEWAY & NL FIELDSERVER TOOLBOX
Revision: 2.A
The latest update to the user interface utility called FieldServer Toolbox has been introduced. This updated utility
is available on the web for all FieldServer Gateways and enables users to easily:
1. Search the local network for any connected FieldServers.
2. Select the FieldServer and launch either the current user-friendly browser-based interface to help set-up, cong-
ure and diagnose the FieldServer.
NOTE: The ProtoCast gateway is not supported by the FS Toolbox. For gateways updated with FieldSafe, diag-
nostic captures cannot be taken with the FieldServer Toolbox but has been integrated into the FS-GUI congura-
tion page.
The following information is viewable for connected FieldServers found by the FieldServer Toolbox:
DEVICES – Lists the device name.
IP ADDRESS – Shows the IP Address of the listed device.
MAC ADDRESS – Shows the MAC Address of the listed device.
FAVORITE – Click to mark this as a favorite device. The device information will show whether the device is found
or not.
CONNECTIVITY – The light shows the level of connectivity for the device. Green is full connectivity. Yellow is
limited connectivity. Blue is limited IP connectivity. And red is connectivity lost.
BUTTONS – These buttons allow multiple functions. The Connect button jumping straight into a device’s FS-GUI
or Web Conguration page via default Internet browser. The Heartbeat button allows taking diagnostics for the
device.
NOTE: For detailed descriptions on any of these items or additional information check the help menu.
Download the MCS-BMS-GATEWAY - FS Toolbox at:
https://mcscontrols.com/communications.html - “FieldServer Toolbox-1.08aC-Setup.exe
FieldServer Graphical User Interface (FS-GUI)
FieldServer Gateways come with the web-based FS-GUI making it easy to check the status, congure and diag-
nose your FieldServer. Information such as network settings, node information, map descriptors, and transfer of
les. The web browser interface can even be set up with your own logo and background if desired.
Each of the pages on the FS-GUI includes specic FieldServer information and features described below.
NOTE: Click the Help button at the bottom of any page to view the Keyboard Shortcut and General Navigation list.

15
Home
Allows the user to check the status of the FieldServer gateway, including the conguration code, version, memory,
gateway type and more. Under “Settings” the user has access to important network information.
NOTE: The “System Restart” button at the bottom of the page is used to restart the FieldServer gateway (only on
the Home page).
About
Allows the user to check current rmware of the FieldServer gateway plus version identication of the interface
and skin, plus con- tact information. Skin is either the default FieldServer template or it can be a specic template
specied by the OEM customer.
Setup
Select “File Transfer” to upload les to the FieldServer gateway including conguration les, rmware upgrades
and more. Select “Network Settings” to access and modify network connection.
View
Select “Connections” to view activity of devices connected to the FieldServer gateway ports.
Select “Data Arrays” to view the Data Arrays setup in the gateway and the user can click on the specic Data
Array for detailed information.
Select “Nodes” to view the Nodes setup in the gateway and the user can click on the specic node for Node
detailed information. On the Nodes details page tabs across the top allow access to settings, status, info stats and
error stats.

16
Select “Map Descriptors” to view the Map Descriptors setup in the gateway and clicking on the specic map
descriptor will access the Map Descriptors detail page. Again, tabs across the top of the page provide quick
access to settings, status, info stats, and error stats.
User Messages
Allows access to error messages, info messages and driver messages.
Diagnostics
Used to create diagnostics captures to assist technical support. Allows capture of Ethernet or Wi-Fi conne

17
Chapter - 4. Setup-MCS-BMS-GATEWAY & GATEWAY-NL
4.1. Record Identication Data
Each MCS-BMS-GATEWAY 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 Number
MCS-BMS-GATEWAY FPC-ED4 FPC-ED4
Figure 1: MCS-BMS-GATEWAY Part Numbers
• FPC-ED4 units have the following 3 ports: LonWorks + Ethernet + RS-485.
4.2. Conguring Device Communications
4.2.1 Set COM settings on all Devices Connected to the MCS-BMS-GATEWAY
• Set up all devices on the same subnet as the MCS-BMS-GATEWAY and the conguration PC.
• All of the connected serial devices MUST have the same Baud Rate, Data Bits, Stop Bits, and
Parity settings as the MCS-BMS-GATEWAY.
•
4.2.2 Set IP Address for each MCS-MAGNUM connected to the MCS-BMS-GATEWAY
The device needs to be on the same IP subnet as the MCS-BMS-GATEWAY and the conguration PC.
Record the following MCS-MAGNUM information to start the setup:
IP Address
MCS-MAGNUM BacNet Device ID
Set MCS-MAGNUM BacNet port to 47808 in MCS-CONFIG
• For Windows XP:
*Customer ProtoCarrier Startup Guide
Page 23 of 38
6 LONWORKS (FPC-C35): COMMISSIONING PROTOCARRIER ON A
LONWORKS NETWORK
Commissioning may only be performed by the LonWorks administrator.
6.1 Commissioning ProtoCarrier FPC-C35 on a LonWorks Network
The User will be prompted by the LonWorks Administrator to hit the Service Pin on the ProtoCarrier
FPC-C35 at the correct step of the Commissioning process which is different for each LonWorks
Network Management Tool.
xIf an XIF file is required, see steps in Section 6.1.1 to generate XIF.
6.1.1 Instructions to Download XIF File from ProtoCarrier FPC-C35 Using Browser
xConnect a CAT5 Ethernet cable (Straight through or Cross-Over) between the PC and
ProtoCarrier.
xThe Default IP Address of ProtoCarrier is 192.168.1.24, Subnet Mask is 255.255.255.0. If the PC
and ProtoCarrier are on different IP Networks, assign a static IP Address to the PC on the
192.168.1.xxx network.
xFor Windows XP:
Go to > >
Right-click on Local Area Connection > Properties
Highlight >
xFor Windows 7 or later:
Go to > >
> >
Right-click on Local Area Connection > Properties
Highlight >
Figure 17: LonWorks Service Pin Location

18
• For Windows XP and Windows 7, select: Use the following IP Address
4.3. BMS Network Settings:
• Selecting Stored Configurations, Setting the MAC Address, Device Instance, and Baud Rate
• Selecting Conguration Files for Devices: “S” Bank DIP Switches S0 – S3
The S bank of DIP switches (S0 - S3) are used to select and load a conguration le from a group of
pretested/preloaded conguration les which are stored in the MCS-BMS-GATEWAY FPC-ED4.
NOTE: S0 - S3 DIP Switches sets the Protocol: BACnet MS/TP, OR JOHNSON N2
NOTE: When setting DIP Switches, please ensure that power to the board is OFF.
4.3.1 BACnet MS/TP, N2 and Modbus IP to RTU
The following chart describes S0 - S3 DIP Switch conguration settings for MCS-BMS-GATEWAY to sup-
port BACnet® MS/TP, Metasys® N2 by JCI and Modbus IP to RTU.
Figure 5 Protocol Selection Switch Tables
4.3.2 BACnet MS/TP: Setting the MAC Address for BMS Network
Only 1 MAC address is set for MCS-BMS-GATEWAY regardless of how many devices are connected to MCS-
BMS-GATEWAY.
Set the BACnet MS/TP MAC addresses of the MCS-BMS-GATEWAY to a value between 1 to 127 (MAC Master
Addresses); this is so that the BMS Front End can nd the MCS-BMS-GATEWAY via BACnet auto discovery.
192 . 168 . 18 . 201
255 . 255 . 255 . 0
192 . 168 . 18 . 1
*Customer ProtoCarrier Startup Guide
Page 24 of 38
xFor Windows XP and Windows 7, select: Use the following IP Address
xClick twice
xOpen a web browser and go to the following address: [IP Address of ProtoCarrier]/fserver.xif
oExample: 192.168.1.24/fserver.xif
xIf the web browser prompts to save the file, save the file onto the PC. If the web browser displays
the xif file as a web page, save the file onto the local PC as fserver.xif
Figure 18: Sample of Fserver.XIF File Being Generated
S0 –S3 DIP
Switches S Bank DIP Switch Location
S0
S1
S2
S3
Off On
Figure 3: S Bank DIP Switches
Fig 3
Shows setting for
BACNet MS/TP
Dip switch S0 ‘ON’
as per the Figure 5
chart below
MCS-BMS-GATEWAY MCS-BMS-GATEWAY Bank DIP Switches
Prole – MCS-BMS-GATEWAY RER S0 S1 S2 S3
Bacnet MS/TP On O O O
N2 O On O O
Modbus IP to RTU On On O O

19
NOTE: Never set a BACnet MS/TP MAC Address from 128 to 255. Addresses from 128 to 255 are Slave
Addresses and can not be discovered by BMS Front Ends that support auto discovery of BACnet MS/TP
devices.
Set DIP switches A0 – A7 to assign MAC Address for BACnet MS/TP for the MCS-BMS-GATEWAY FPC-ED4.
Please refer to Appendix A.1 for the complete range of MAC Addresses and DIP switch settings.
NOTE: When using Metasys N2 and Modbus TCP/IP, the ‘A’ Bank of DIP
switches are disabled and not used. They should be set to OFF.
NOTE: When setting DIP Switches, please ensure that power to the boaris OFF.
4.3.3 BACnet MS/TP and BACnet/IP: Setting the Device Instance
• The ‘A’ Bank of DIP switches are used for two purposes:
• For BACnet MS/TP, they are used to set the BACnet MS/TP MAC address (Section 3.3.2)
• For both BACnet MS/TP and BACnet/IP, they are also used to determine the BACnet Device In-
stance values
• The BACnet Device Instance can range from 1 to 4,194,303.
• The BACnet device instances will be calculated by taking the Node O󰀨set (default is 18100)
found in Web Congurator and adding it to the value of the ‘A’ Bank DIP switches.
When more than one device is connected to the MCS-BMS-GATEWAY, the subsequent BACnet Device In-
stance values will be sequential from the rst/previous device.
For example:
• Given that Device Instance = Node_O󰀨set + A Bank DIP switch value = Default Node_O󰀨set
value = 18150 = ‘A’ Bank DIP switch value = 03 (as per Appendix A.10 DIP Switch Setting)
• Then the Device Instance values for the devices are: = Device 1 Instance = 18153 = Device 2
Instance = 18154
4.3.4 Metasys N2: Setting the Node-ID
• Set DIP switches A0 – A7 to assign a Node-ID for Metasys N2 to the MCS-BMS-GATEWAY.
• Node-ID’s range from 1-255.
• Refer to Appendix A.10 for the full range of addresses for setting Node ID.
4.3.5 BACnet MS/TP: Setting the Serial Baud Rate for BMS Network
DIP Switches B0 – B3 can be used to set the serial baud rate to match the baud rate required by the Building
Management System for BACnet MS/TP.
• The baud rate on MCS-BMS-GATEWAY for Metasys N2 is set for 9600. DIP Switches B0 – B3
are disabled for Metasys N2.
NOTE: When setting DIP Switches, please ensure that power to the board is OFF.
B0
B1
B2
B3
Off On
Figure 5: Baud Rate DIP Switches
Fig 5
Shows setting for
19200 Baud Rate
A0
A1
A2
A3
A4
A5
A6
A7
OffOn
Figure 4: MAC Address DIP Switches
Fig 4
Shows setting for 03 BMS Address
as found in A.1 appendix
in the rear of this manual

20
4.3.5.1. Baud Rate DIP Switch Selection
Baud B0 B1 B2 B3
Auto O󰀨 O󰀨 O󰀨 O󰀨
110 On O󰀨 O󰀨 O󰀨
300 O󰀨 On O󰀨 O󰀨
600 On On O󰀨 O󰀨
1200 O󰀨 O󰀨 On O󰀨
2400 On O󰀨 On O󰀨
4800 O󰀨 On On O󰀨
9600 On On On O󰀨
19200 O󰀨 O󰀨 O󰀨 On
20833 On O󰀨 O󰀨 On
28800 O󰀨 On O󰀨 On
38400 On On O󰀨 On
57600 O󰀨 O󰀨 On On
76800 On O󰀨 On On
115200 O󰀨 On On On