NAE55 Installation Guide

Part No. 24-10051-43 Rev. V

Releases 11.0
2020-10-30

Application Important: For any other custom integrations,

contact your local Systems Integration Services
The Metasys Network Automation Engine (NAE) is an (SIS) team before an upgrade. Updated drivers are
Ethernet-based, supervisory device that connects BAS available on request.
networks to IP networks. NAEs monitor and control
field-level building automation devices, including HVAC In this installation guide, the term network engine
equipment, lighting, security, and fire safety equipment. applies to any NAE55 model, unless otherwise stated. For
At Release 11.0, the NAE55 is also FIPS 140-2 Level 1 installation instructions on the secure NAE55, refer to
compliant. FIPS 140-2 is a United States government the NAE-S Installation Instructions (Part No. 24-10051-108).
cybersecurity standard that approves cryptographic For installation instructions on the NAE55s that are
modules/algorithms used for encryption. Use this approved for Metasys system smoke control applications,
document to install the NAE. Figure 1 shows the NAE55 refer to the NAE55 Installation Instructions (Part No.
engine. 24-10051-00132).
Note: At Metasys Release 10.0 and later, modems
Figure 1: NAE55 Network Engine (internal and external) and pagers are no longer
supported on NAE55 engines that run the Linux
operating system, but are still supported on prior
releases for engines that use a Windows Embedded
operating system. If you receive from the factory a
network engine with Release 9.0 that has an internal
modem, you can field-upgrade the engine to Release
10.0 or later to acquire new release enhancements,
but its modem and pager functionality are lost. If
you need modem and pager functionality, do not
upgrade the NAE55 engine to Release 10.0 or later.

Installation
Follow these guidelines when installing the network
engine:
• Transport the network engine in the original container
to minimize vibration and shock damage to the network
engine.
The NAE offers various integration options. Ethernet • Verify that all the parts shipped with the network
network integrations include the following options: engine. The data protection battery and network engine
• Johnson Controls and 3rd party BACnet/IP devices ship together but are packaged separately.
• Simplex® Fire Alarm Control Unit (FACU) • Do not drop the network engine or subject it to physical
• Cree® SmartCast® Lighting Control shock.
• Molex® Lighting Control • Do not open the network engine housing (except the
data protection battery compartment). The network
• Tyco® C•CURE® 9000 or victor® Video Management
engine has no user-serviceable parts inside.
• Modbus TCP/IP
• KNX IP Parts included
• OPC UA integration (Release 11.0 only) • one MS-NAE55xx-x model
Field Bus integrations include the following options: • one data protection battery
• BACnet MS/TP • one installation instructions sheet
• N2 Bus Materials and special tools needed
• LonWorks® (NAE552x models only)
You can mount the network engine by using the fasteners
• Modbus Remote Terminal Unit (RTU) option or the DIN rail option.
• Meter Bus (M-Bus)
• Fasteners option - Three fasteners appropriate for the
• Zettler® Fire Panel
mounting surface:
- #8 screws - North America
- M4 screws - Europe

*241005143V*
(barcode for factory use only)
MS-NAE5510-2U, MS-NAE5510-3, MS-NAE5510-3U,
MS-NAE5511-3, MS-NAE5520-3, MS-NAE5521-3
• DIN rail option - 36 cm (14 in.) or longer section of 35 Table 1: Network Engine physical features
mm (1 1/8 in.) for DIN rail mount applications only.
Callout Description
Dimensions 6 End-of-line switches
7 Wall mount feet
Figure 2: NAE55 showing dimensions and mounting
orientation 8 System status LEDs
9 System reboot switch
10 Data protection battery compartment
11 RJ-45 8-pin Ethernet port

Mounting
Location considerations
Follow these guidelines when mounting the network
engine:
• Ensure that the mounting surface can support the
network engine and any user-supplied enclosure.
• Mount the network engine in the proper orientation
(Figure 6).
• Mount the network engine on an even surface in wall
Physical Features mount applications whenever possible. If you must
The following figure displays the physical features of mount the network engine on an uneven surface, be
the network engine. The accompanying table provides careful not to crack the wall mount feet or housing
a description of the physical features. A modem jack when tightening the screws. Use shims or washers to
appears on models with an internal modem and a mount the unit securely on the mounting surface.
LonWorks terminal for LonWorks models (Figure 2). • Mount the network engine in areas free of corrosive
vapors and observe the environmental limitations listed
Figure 3: Physical features of Network Engine (modem in the Technical specifications section.
and LON ports not shown)
• Do not mount the network engine on surfaces that are
prone to vibration or in areas where electromagnetic
emissions from other devices or wiring can interfere
with network engine communication.
• Allow sufficient space for running cable and wire,
making terminal connections, and accessing battery
compartment (Figure 4).
• Mount the power supply above the network engine to
ensure adequate heat dissipation and to position close
to the power wiring conduit.
On panel or enclosure mount applications, observe these
additional guidelines:
• Do not install the network engine in an airtight
enclosure.
• Mount the network engine so that the enclosure wall
or the transformer does not obstruct ventilation of the
network engine housing.

Table 1: Network Engine physical features

Callout Description
1 USB ports
2 RS-232 serial ports
LonWorks terminal (LonWorks models only,
3
Figure 2)
Field controller buses (FC Bus or N2 Bus
4
terminal)
5 24 VAC power terminal

4 NAE55 Installation Guide

Figure 4: DIN rail mount dimensions and mounting 3. Insert appropriate wall anchors in all four holes (if
space requirements, mm (in.) necessary) and insert the screws into the top two
holes. Leave enough space between the wall surface
and the screw head for the wall mount feet.
4. Hang the network engine on the screws with the
top wall mount feet for horizontal wall mount
applications. Hold the network engine in place for
vertical application.
Note: The wall mount feet are designed to
make mounting easier. When the network
engine is wall mounted in the horizontal
orientation, you can hang the network engine
on the screws with the upper two mount feet
(Figure 6).
5. Insert the screws into the lower two wall mount feet
and holes and carefully tighten all of the screws.
Important: Do not overtighten the mounting
Each network engine application is different, and no screws. Overtightening the screws can crack the
general guidelines can be given about the heat dissipating network engine wall mount feet or housing.
devices that may be mounted in an enclosure with the
network engine. Monitor the network engine processor Mounting the Network Engine for DIN rail
temperature for each application to determine the mount applications
acceptable combinations of devices and proper mounting
location for your specific application. To mount the network engine on DIN rails:
1. Mount two DIN rails horizontally, so they are 125 mm
Important: Do not add any devices to an enclosure
(4.9 in.) apart on centers (Figure 4).
with a network engine that could cause the
temperature of the network engine processor 2. Snap the DIN clips on the bottom of the network
to exceed 70˚C (158˚F). View the network engine to the outward position.
engine's CPU Temperature value on the network 3. Hang the network engine on the DIN rail hooks on
engine's Diagnostic tab on the Metasys Site the back of the network engine.
Management Portal. See Technical specifications for
Press the DIN clips back into position to secure the unit on
ambient condition requirements, and refer to the
the DIN rails.
Troubleshooting section of the NAE Commissioning
Guide (LIT-1201519) for additional information. Figure 6: Required orientations for Network Engine
Mounting the Network Engine for wall wall mount applications
mount applications
To mount the network engine on a vertical surface:
1. Mark the location of the four wall mount feet on
the wall using the dimensions in Figure 5 and an
orientation shown in Figure 6, or hold the network
engine up to the wall and mark the hole locations.

Figure 5: Mounting screw hole dimensions, mm (in.)

To remove the network engine from the DIN rails:

1. Snap the DIN clips on the bottom of the network
engine to the outward position.
2. Lift the network engine off the DIN rails.

Mounting the Network Engine in a panel

To mount the network engine in a panel, follow these
requirements:
2. Drill holes in the wall at the marked locations.
• Mount the panel in accordance with the manufacturer’s
instructions.

NAE55 Installation Guide 5

• Mount the network engine in the panel following the to integrate the following field controller networks into the
guidelines in the Location considerations and Mounting Metasys system:
sections of this document. • BACnet MS/TP FC Bus
• N2 Bus
Wiring Overview • Modbus RTU
Power supply, network, and • M-Bus

communication connections Note: Each field controller integration has different

protocols and network requirements. Do not
See Figure 2 and Figure 3 for the location of the power intermix N2, MS/TP, Modbus, or M-Bus devices on
supply terminal, network communication terminals, the same FC Bus port.
Ethernet jack, and modem jack.
The SHD connections on the FC terminal blocks are not
Depending on the model, the network engine can connected to any earth ground connection. The FC A and
connect to an MS/TP field bus trunk, an N2 Bus trunk, FC B terminal blocks are not interchangeable.
or a LonWorks network trunk. Also, all network engines
support multiple vendor integrations, including Modbus, LonWorks network terminal block
M-Bus, and KNX. See Table 21 for a list of all supported
The LonWorks TP/FT-10 network connection, available
trunk applications. The rules, guidelines, and wiring
only on the network engine LonWorks model, is a 3-wire
considerations for each type of network or field bus
removable, keyed terminal block. The Shield connection
application are provided in tables of this document.
on the LonWorks network terminal block is an isolated
Power supply terminal and is not connected in the network engine.
Use the LonWorks terminal block to connect LonWorks
Important: Install the data protection battery before networks to the network engine.
applying 24 VAC power to the network engine. See
the Installing the data protection battery section. Computer serial ports
In North America, use a Class 2, 24 VAC power supply with The network engine has two RS-232-C serial ports labeled
a 50 VA minimum output. Outside North America, use a RS232C A and RS232C B (Figure 3). Use either port to
24 VAC SELV transformer at the appropriate rating. The connect a Modbus RTU or Zettler MXSpeak third-party
minimum input voltage for the network engine to operate integration. For more information on how to use the
properly is 20 VAC. See the Technical specifications section. serial port for third-party vendor integration, refer to the
application note for the particular vendor integration you
Use a dedicated power supply to the network engine
are installing. Lastly, these RS-232-C serial ports do not
only. Do not connect any other loads to the power supply.
support external modems.
Additional loads may cause noise interference.

Ethernet port Universal Serial Bus (USB) ports

The two USB ports labeled USB A and USB B are both
The Ethernet port, labeled ETHERNET, is an 8-pin RJ-45
configured as masters and are independent of each other.
network port for connecting the network engine to
At Release 10.0 or later, the use of a USB port to connect
Ethernet IP networks. Network engine can connect to
an optional external modem is no longer supported.
Ethernet networks at 10 Mbps, 100 Mbps, or 1 Gbps.
This Ethernet port provides IP communications over the Optional Internal Modem
building network and to any third-party integration that
uses Ethernet communication. The devices that you can MS-NAE55x1-x models with Release 9.0 have an internal
connect to the ETHERNET port on the network engine modem and a 6-pin RJ-12 modular jack labeled MODEM.
include the following: Connect a standard phone line into the MODEM jack to
use the internal modem.
• BACnet/IP
• Ethernet TCP/IP Note: Modem functionality is no longer available for
NAE55s upgraded to Release 10.0 or later.
• Modbus TCP/IP
• KNX For information on commissioning an internal modem
on older models, refer to the NAE Commissioning Guide
• Tyco C•CURE 9000 and Tyco victor Video Management (LIT-1201519).
• Simplex FACU
• Cree SmartCast Lighting Control Wiring the Network Engine
• Molex Lighting Control Mount the network engine securely before wiring it. For
• OPC Unified Architecture (UA) details, see Mounting.
FC Bus terminal block
The two Field Controller (FC) Bus connections on a
network engine are 4-pin removable, keyed terminal
blocks labeled FC-A and FC-B. The FC bus connections are
optically isolated RS-485 ports that communicate at 9600,
19,200, 38,400, or 76,800 baud. You can use the FC Bus port

6 NAE55 Installation Guide

 Important: Use this NAE only as an operating
control. Where failure or malfunction of the NAE
 CAUTION could lead to personal injury or property damage
to the controlled equipment or other property,
additional precautions must be designed into the
Risk of Property Damage.
control system. Incorporate and maintain other
Do not apply power to the system before checking devices, such as supervisory or alarm systems or
all wiring connections. Short circuited or improperly safety or limit controls, intended to warn of or
connected wires may result in permanent damage to protect against failure or malfunction of the NAE.
the equipment. Important: Utiliser ce NAE uniquement en tant que
dispositif de contrôle de fonctionnement. Lorsqu'une
défaillance ou un dysfonctionnement du NAE risque
de provoquer des blessures ou d'endommager
l'équipement contrôlé ou un autre équipement, la
 Attention conception du système de contrôle doit intégrer des
dispositifs de protection supplémentaires. Veiller
dans ce cas à intégrer de façon permanente d'autres
Risque de dégâts matériels. dispositifs, tels que des systèmes de supervision
Ne pas mettre le système sous tension avant ou d'alarme, ou des dispositifs de sécurité ou de
d'avoir vérifié tous les raccords de câblage. Des limitation, ayant une fonction d'avertissement
ou de protection en cas de défaillance ou de
fils formant un court-circuit ou connectés de façon
dysfonctionnement du NAE.
incorrecte risquent d'endommager irrémédiablement
l'équipement. Important:
• Do not apply 24 VAC power to the network engine
before completing and checking connections.
Short circuits or improperly connected wires may
result in permanent damage to the equipment.
 WARNING
• Do not apply 24 VAC power to the network engine
before installing the data protection battery. See
Risk of Electric Shock. the Installing the data protection battery section
in this document.
Disconnect or isolate all power supplies before making • Use copper conductors only. Make all wiring in
electrical connections. More than one disconnection accordance with local, national, and regional
or isolation may be required to completely de-energize regulations.
equipment. Contact with components carrying • The network engine is a low-voltage (<30 VAC)
hazardous voltage can cause electric shock and may device. Do not exceed the network engine
result in severe personal injury or death. electrical ratings. Applying high voltage to the
network engine may result in permanent damage
to the network engine and void any warranties.
• Do not remove the terminal block keys. The
 WARNING terminal block plugs and the terminal sockets are
keyed to fit together in the correct configuration
only.
Risque de décharge électrique. • Prevent any static electric discharge to the
network engine. Static electric discharge can
Débrancher ou isoler toute alimentation avant damage the network engine and void any
de réaliser un branchement électrique. Plusieurs warranties.
isolations et débranchements sont peut-être
Follow these guidelines when wiring the network engine:
nécessaires pour -couper entièrement l'alimentation
de l'équipement. Tout contact avec des composants • Route the supply power wires and communication
conducteurs de tensions dangereuses risque cables at least 50 mm (2 in.) away from the vent slots in
d'entraîner une décharge électrique et de provoquer the sides of the network engine housing.
des blessures graves, voire mortelles. • Provide slack in the wires and cables. Keep cables
routed neatly around the network engine to promote
good ventilation, LED visibility, and ease of service.
• Ensure that the building automation network wiring
meets the specifications, rules, and guidelines as
outlined in the Wiring considerations and guidelines for
network integrations section. The network engine does
not require an earth ground connection.

NAE55 Installation Guide 7

• Follow the transformer manufacturer’s instructions Figure 8: Daisy chained devices
and the project installation drawings. Power supply
wire colors may be different on transformers not
manufactured by Johnson Controls.
• While connecting network devices to 24 VAC power,
make sure that transformer phasing is uniform across
all devices. Powering network devices with uniform 24
VAC supply power phasing reduces noise, interference,
and ground loop problems.

Connecting MS/TP or N2 bus devices

To connect devices to the MS/TP Field Controller (FC) Bus
or N2 Bus, complete the following steps:
1. Connect the 3-wire bus cable to the removable blue
4-pin terminal block labeled FC-A as shown in Figure
7.
Note: The FC-A and FC-B terminals can accept
either the MS/TP FC Bus or the N2 Bus, but not a
mixture of both on the same trunk. If you want
to integrate both the MS/TP Bus and the N2
Bus, select one FC terminal for MS/TP FC Bus
use and the other for N2 Bus use. Table 3: FC Bus terminal block wiring
Callout Description
Figure 7: FC Bus terminal block and wiring connections 1 Daisy-chained device on FC Bus segment
2 Terminating device on FC Bus segment
3 FC Bus terminal plugs
4 To next device on FC Bus segment
5 From previous device on FC Bus segment
6 Isolated shield connection terminal
3. Set each FC EOL switch to their proper positions. See
the note in Setting the end-of-line switches.

Table 2: FC Bus terminal block wiring

Callout Description
1 FC Bus terminal block
2 FC Bus terminal block plug
3 Terminating wires (3-wire cable shown)
2. To add additional field devices, wire from one device
to the next as shown in Figure 8. Do not connect
more than two wires to each terminal to ensure that
a daisy chain configuration is used.

8 NAE55 Installation Guide

Connecting LonWorks devices Figure 10: FC Bus terminal block and wiring connections
for Modbus
About this task:
To connect LonWorks devices, complete the following
steps:
1. Connect the 2-wire cable from the LonWorks trunk
to the removable 3-terminal blue plug labeled LON
(Figure 3). The LonWorks network trunk is available
on the MS-NAE5520-3 model only.

Figure 9: LonWorks network terminal block and wiring

connections

Table 5: FC Bus terminal block wiring for Modbus

Callout Description
1 FC Bus terminal block
2 FC Bus terminal block plug
3 Terminating wires for Modbus (2-wire cable shown)
Table 4: LON trunk terminal block wiring 2. For a Modbus RTU device that requires an RS232C
Callout Description serial connection, use a cable to connect the
converter to either the RS232C A or RS232C B serial
1 LonWorks network terminal block
port on the network engine. The maximum cable
2 LonWorks network terminal block plug length between devices connected though an
Terminating wires (2-wire cable shown) RS-232 line depends on the baud rate used. In
3 Note: LonWorks network wires are not polarity general, the cable should not exceed 15 meters for
sensitive. 9600 baud.
3. Wire from the RS-485 terminal on the converter to
2. To add additional vendor devices, wire from one the RS-485 port on the vendor device (Figure 11).
device to the next in a daisy-chained fashion. Do not The RS-485 bus is a two-wire network.
connect more than two wires to each terminal.
a. Connect the converter's + A terminal to the
Connecting Modbus RTU devices device's + (or A) terminal.
About this task: The network engine connects to b. Connect the converter's - B terminal to the
Modbus RTU devices directly if the RS485 protocol is in device's - (or B) terminal.
use or by using a converter if the RS-232 protocol is in Figure 11: Connection between converter and device
use. (After installation and wiring are complete, refer
to the Network Engine Commissioning for Modbus Vendor
Integration Application Note (LIT-12013150) for additional
information.)

1. For a Modbus RTU device that requires an RS-485

connection, terminate the 2-wire bus cable from
the Modbus device to one of the removable 4-
terminal blue plugs on the network engine, labeled
FC-A and FC-B (Figure 10).

4. To add additional vendor devices, wire from one

device to the next in a daisy chain configuration.
The completed wiring should look similar to Figure
12.

NAE55 Installation Guide 9

Figure 12: Modbus RTU wiring detail overview Figure 13: M-Bus Level Converter Connections

Connecting M-Bus devices

About this task: The network engine connects to
the M-Bus network devices by using the M-Bus Level
Converter. Two components are needed: serial connection
cable (INT-DX-KAB01) and the M-Bus Level Converter.
(After installation and wiring are complete, refer to the
Network Engine Commissioning for M-Bus Vendor Integration
Application Note (LIT-12013149) for additional information.)

1. Connect the RS-232 cable from either RS232C

serial port on the network engine to the RS-232
connection on the M-Bus Level Converter using
cable INT-DX-KAB01 (Figure 13). Wire to terminals
GND, RxD, and TxD (Table 6).
Table 6: M-Bus Level Converter connection detail
2. Wire from the M- and M+ terminals on the level
converter to the meters using a free (star, ring, Callout Description
or bus) topology, preferably bus. Specific cabling M-Bus connections:
can vary depending on the topology and site. See
1 13: M+
Wiring considerations and guidelines for network
integrations. 14: M-
Note: If the number of M-Bus unit loads or Power connections (24 VAC/DC):
distances exceeds the specifications of a level 9: PE
converter, an M-Bus repeater can be wired to 2
11: 24+ V/~
the converter to increase the number of unit
loads and distances. The converter shown in 12: 24- V/~
Figure 13 is capable of handling up to 100 unit RS-232 wire connection (serial cable INT-DX-KAB01):
loads. See Ordering information for a list of M- 5: TxD (transmit data); PIN 2 on RJ12
Bus devices. 3
6: RxD (receive data); PIN 3 on RJ12
3. Connect the 24 VAC supply power wires from the 7: GND (ground); PIN 5 on RJ12
transformer to the -/~ and +/~ terminals as shown 4 To network engine RS-232C port
in Figure 13.
Connecting KNX devices
About this task: The network engine connects to a KNX
network device by using the KNX/IP interface router.
(After installation and wiring are complete, refer to the
Network Engine Commissioning for KNX Vendor Integration
Application Note (LIT-12013148) for additional information.)

1. Connect an Ethernet cable from the building's

network jack to the port on the front of the KNX
gateway (Figure 14).

10 NAE55 Installation Guide

 Note: Depending on the size of your network, • Cree SmartCast Lighting Control: Metasys System
you can use either a KNX Interface or Router as Commissioning for Cree Digital Lighting Systems
a gateway. The Interface connects the network Integration (LIT-12013152)
engine to a single KNX line, while the Router • Molex Lighting Control: Metasys System Commissioning
acts as both an Interface and a Line Coupler for Molex Digital Lighting Systems Integration
over Ethernet to connect the network engine to (LIT-12013153)
the network, not to a single device. • Zettler Fire Panel: Network Engine Commissioning for
2. Connect an Ethernet cable from the building's Zettler MX Speak 6.0 Vendor Integration (LIT-12013269)
network jack to the RJ-45, 8-pin Ethernet port on • OPC UA Servers: Network Engine Commissioning for OPC
the network engine. UA Client Vendor Integration (LIT-12013545)
Figure 14: KNX/IP Interface Router
Connecting the power source
About this task: Connect the 24 VAC supply power
wires from the transformer to the removable power
terminal connector on the network engine (Figure 15).
The connections are HOT and COM (common).
Do not apply power yet.
Figure 15: Supply power wiring (24 VAC transformer)

Table 8: Power supply wiring

Callout Description
Table 7: KNX/IP Interface Router connection detail
1 NAE power terminal block
Callout Description 2 NAE power terminal block plug
1 To power supply 3 Terminating wire for 24 VAC (orange)
2 To KNX devices 4 Terminating wire for Common (brown)
3 To Ethernet network Terminating wires from 24 VAC Class 2 power
5
3. For a single KNX line, wire from the red and black transformer
terminals on the gateway to the devices. For Note: Power supply wire colors may be different on
multiple KNX lines, wire from the red and black transformers not manufactured by Johnson Controls.
terminals on each gateway to the devices on the Follow the transformer manufacturer’s instructions
same KNX line. and the project installation drawings.
Note: Specific cabling can vary depending
on the topology and site. See Wiring Setup and adjustments
considerations and guidelines for network
integrations.
Installing the data protection battery
4. Wire each KNX gateway to its own dedicated power
Important: Do not apply 24 VAC power to the
supply on the KNX line.
network engine before installing the data protection
Connecting other third-party devices battery.
About this task: To install the data protection battery:
Network engine models support several other third- 1. Remove the battery from its packaging. Remove the
party devices. Refer to the following documents for battery cover on the network engine to expose the
information about how to connect the network engine to battery compartment (Figure 3).
these devices: 2. Carefully plug the network engine battery connector
• C•CURE-victor: Network Engine Commissioning for from the battery compartment into the connector on
C•CURE-victor Integration Application Note (LIT-12013151) the battery cable (Figure 16).
• Simplex FACU: Network Engine Commissioning for 3. Place the battery into the compartment (Figure 16).
Simplex Fire System Integration (LIT-12013060)

NAE55 Installation Guide 11

4. Slide one end of the battery strap into the hole on Figure 17: FC Bus EOL switch in the factory default ON
the opposite side of the strap (Figure 16), and loop (up) position
the strap tightly around the battery to minimize
battery movement.
5. Replace the cover of the battery compartment.
Important: The data protection battery must
maintain a small residual charge. The battery ships
from the factory with a small residual charge.
You should connect 24 VAC power to the network
engine immediately after connecting the battery to
ensure that the battery does not completely loose its Note: The EOL switches on the network engine are
charge, which may damage the battery. factory set to ON (Figure 17). If the network engine
Note: The 24 VAC power to the network engine is not a terminated device on the FC Bus, reposition
charges the data protection battery. At initial the switch on the EOL switch block to the Off (down)
startup, the battery requires a charging period of at position.
least two hours before it supports data protection Set the EOL switches appropriately for the FC A and
if power fails. Maximum protection (up to three FC B buses. The network engine follows the same
consecutive power failures without recharging time) rules as other switch-terminating devices listed in the
requires a 24-hour charging period. Setting Terminations sections of the N2 Communications
Bus Technical Bulletin (LIT-636018) and the MS/TP
Figure 16: Network Engine data protection battery Communications Bus Technical Bulletin (LIT-12011034).

Powering on the Network Engine

Apply power to the network engine by plugging in the
gray 2-pin terminal connector to the power terminal port
on the network engine (Figure 3). The network engine
requires approximately 3 minutes to start up and become
operational. See the LED test sequence at startup section.
Startup is complete and the network engine is operational
when the (green) RUN LED is On steady and the (red) GEN
FAULT LED is Off. See Figure 18 for LED locations.

Disconnecting power from the Network

Engine
Table 9: Data protection battery details
Important: The data protection battery must be
Callout Description installed and charged before disconnecting the 24
1 Data protection battery VAC supply power.
2 Battery strap Disconnect power from the network engine by removing
3 Data protection battery compartment the gray 2-pin terminal block from the power terminal
4 Battery cable connectors port on the network engine (Figure 3).
When you remove 24 VAC power from the network
engine, or supply power is lost, the network engine is
Setting the end-of-line switches nonoperational after the power management settings
The network devices at each end of an FC Bus segment expire. The POWER LED (Figure 18) remains On, and the
must be set as network terminated devices. The network data protection battery continues to power the network
engine has two EOL switches (one for each FC Bus) engine for approximately 1 to 3 minutes so that volatile
that enable you to set the network engine as a network data can be backed up in nonvolatile memory. The
terminated device on the bus. POWER LED goes Off when the data backup is completed.
To set a network engine as an FC Bus terminated device,
position the switch on the EOL switch block to the ON Troubleshooting
position (Figure 17).
LED status indicators
The LEDs on the front cover of the network engine
indicate power and communication status. See Figure 18
and Table 10.

LED test sequence at startup

About this task: During startup, the network engine
automatically initiates an LED test to verify the operational

12 NAE55 Installation Guide

status of the LEDs. Immediately after connecting supply Figure 18: Network Engine with LED designations
power, the following LED lighting sequence occurs:

1. The network engine emits one short beep,

indicating that the BIOS startup was successful.
2. The PEER COM, RUN, and GENL FAULT LEDs
turn on, indicating that the OS is booting up. For
network engine models, the FC A and FC B LEDs
also turn on.
3. The PEER COM, RUN, GENL FAULT LEDs, and the
FC A and FC B LEDs shut off. The RUN LED flashes
to indicate that the network engine software is
loading.
4. The LEDs display the operational status of the
network engine. When the RUN LED goes On
Steady, the operating system and Metasys
application are running and the network engine is
ready.
Result The total time to start up the network engine System re-boot switch
depends on the size of the database and can take several The System Re-Boot switch (Figure 3) forces a manual
minutes. restart of the network engine processor. All data changes
made to the system since the last time the network
engine saved data are lost on restart, including alarm,
trend, and audit trail data.
Note: Press the System Re-Boot switch only if
the network engine fails to respond and cannot
be accessed by any user device. Do not press the
System Re-Boot switch unless you have tried other
reasonable means to fix the problem.

Network Engine LEDs designation, normal status, description, and other conditions
Table 10: Network Engine LEDs designation, normal status, description, and other conditions
LED Normal Descriptions/Other Conditions
On Steady = Unit is getting power from either the battery or 24 VAC power.
POWER (Green) On Steady
Also see the 24 VAC LED. Off Steady = Unit is shut down.
Flicker = Data is transferring on the Ethernet connection. Ethernet traffic is
general traffic (may not be for the network engine).
ETHERNET (Green) Flicker
Off Steady = No Ethernet traffic, probably indicates a dead Ethernet network
or bad Ethernet connection.
10/LINK (Green) On Steady On Steady = Ethernet connection is established at 10 Mbps.

100/1000 LINK (Green/ On Steady (Green) = Ethernet connection is established at 100 Mbps.
On Steady
Yellow) On Steady (Yellow) = Ethernet connection is established at 1,000 Mbps.
On Steady = Controllers are defined to FC A (FC Bus 1 or N2 Trunk 1) in the
network engine, but none are communicating (network engine transmitting
only).
Flicker = Normal communications; FC A port is transmitting and receiving
FC A (Green) Flicker data. Flickers are generally in sync with data transmission but should not be
used to indicate specific transmission times. Also, the flicker rate for the MS/
TP bus is different from the rate for the N2 Bus.
Off Steady = No field controllers are defined to FC A (FC Bus 1 or N2 Trunk 1)
in the network engine.

NAE55 Installation Guide 13

Table 10: Network Engine LEDs designation, normal status, description, and other conditions
LED Normal Descriptions/Other Conditions
On Steady = Controllers are defined to FC B (FC Bus 2 or N2 Trunk 2) in the
network engine, but none are communicating. (network engine transmitting
only)
Flicker = Normal communications; FC B port is transmitting and receiving
FC B (Green) Flicker data. Flickers are generally in sync with data transmission but should not be
used to indicate specific transmission times. Also, the flicker rate for the MS/
TP bus is different from the rate for the N2 Bus.
Off Steady = No field controllers are defined to FC B (FC Bus 2 or N2 Trunk 2)
in the network engine.
Flicker = Data traffic between network engines. For a network engine that
is not a Site Director, this LED indicates regular heartbeat communications
Varies (see next with the Site Director. For a Site Director network engine, flashes are more
PEER COMM (Green)
column) frequent and indicate heartbeat communications from all other network
engines on the site. For a single network engine on a network without an
ADS, there is no flicker.
On Steady = network engine software is running.
On 1 second, Off 1 second = network engine software is in startup mode.
Run (Green) On Steady
On 0.5 seconds, Off 0.5 seconds = network engine software is shutting down.
Off Steady = Operating system is shutting down or software is not running.
On Steady = 24 VAC power is present.
24 VAC (Green) On Steady Off Steady = Loss of 24 VAC power. In the Off Steady condition, the network
engine can be running on battery power. Also see the POWER LED.
On Steady = Battery fault. Replace the battery. Battery is not connected
or cannot be charged. The BATT FAULT LED may remain On for up to 24
BATT FAULT (Red) Off Steady hours after initially powering on the network engine. If the BATT FAULT LED
remains on longer than 48 hours after initially powering on the network
engine, check the battery connection or replace the battery.
On Steady = General Fault. Fault conditions are user configurable in
software. Preconfigured fault conditions include excessive memory use,
GENL FAULT (Red) Off Steady excessive flash use, excessive CPU or PWB temperature, and Battery Fault.
In normal operation, the GENL FAULT LED stays on steady for the first half of
the startup sequence.

Wiring considerations and guidelines for network integrations

Table 11: Network Engine Ethernet network rules
Category Rules and Maximums
General Star topology with network switches
Number of Devices Maximum of 1,000 devices permitted at one site in the Metasys network.
2,000 m (6,600 ft) for plastic/glass fiber optic with external adapter
10 BaseT: 100 m (330 ft) Cat5 or Cat6 cable
Line Length and Type
100 BaseT: 100 m (330 ft) Cat5 or Cat6 cable
1000 BaseT: 100 m (330 ft) Cat5E or Cat6 cable
Terminations For 10/100/1000 BaseT, no line terminators allowed.

14 NAE55 Installation Guide

Table 12: Guidelines for BACnet protocol MS/TP network topology
Category Rules and Maximums
General Two MS/TP Bus trunks, daisy chain topology only. No T or star topology configurations.
100 devices per FC Bus with no more than two repeaters between network engine and any
device and a maximum of 50 devices between repeaters
Number of Devices Note: If TEC2000 Series Thermostat Controllers or third-party devices are used on the
FC Bus, the maximum total number of devices is 64 and the maximum length is 1,219 m
(4,000 ft).
1,500 m (5,000 ft) cable without a repeater
4,500 m (15,000 ft) cable from network engine to the farthest FC Bus device (three bus
Line Length and Type
segments of 1,500 m [5,000 ft] each, separated by repeaters)
2,000 m (6,600 ft) between two fiber modems
Stranded 0.6 mm (22 AWG) 3-wire twisted, shielded cable is recommended.
Stranded 0.6 mm (22 AWG) shielded 4-wire (two twisted-pairs) shielded cable is acceptable.
Cable Type
Note: Use only twisted pair wire. On applications using 4-wire (two twisted-pairs) cable,
isolate and insulate unused conductor. Refer to the MS/TP Communications Bus Technical
Bulletin (LIT-12011034) for more information.
Two FC devices with EOL switches in the ON position, one at each end of each FC Bus
Terminations
segment
Note: Refer to the MS/TP Communications Bus Terminal Bulletin (LIT-12011034) or the Installation Quick Reference
Handbook (FAN410) for information on cable types and lengths.

Table 13: Guidelines for N2 network topology

Category Rules and Maximums
Two N2 Bus trunks supported.
General
Only daisy-chained devices (with maximum stub length of 3 m [10 ft] to any device)
Up to 100 N2 devices supported per bus, with no more than two repeaters between network
Number of Devices
engine and any N2 device and a maximum of 50 devices between repeaters
1,500 m (5,000 ft) twisted pair cable without a repeater
Line Length and 4,500 m (15,000 ft) twisted pair cable from NAE55 and the farthest N2 device (three segments of
Type 1,500 m [5,000 ft] each, separated by repeaters)
2,000 m (6,600 ft) between two fiber modems
Solid or stranded 1.0 mm (18 AWG) 3-wire is recommended
Solid or stranded 0.5 mm (24 AWG) larger 3-wire or 4-wire (two twisted-pairs) is acceptable
Cable
Note: Use only twisted pair wire. On applications using 4-wire (two twisted-pairs) cable,
isolate and insulate unused conductor.
Preferred Termination Configuration: Two N2 devices with EOL switches in the ON position, one
at each end of each N2 Bus segment
Terminations
Minimally Required Termination Configuration: At least one N2 device with an EOL switch in
the ON position somewhere on each N2 Bus segment

NAE55 Installation Guide 15

Table 14: Modbus RTU rules
Category Rules and Maximums
One direct Modbus RTU (RS-232) connection to either RS232C port is supported; connection
requires an RS-232/RS-485 converter to the RS232C serial port
General
One direct Modbus RTU (RS-485) connection to either FC Bus port is supported
Only daisy-chained devices
RS232C port supports one Modbus RTU (RS-232) device.
RS232C port with RS-232/RS-485 converter supports 32 Modbus (RS-485) devices or more,
depending on the converter used
Number of Devices
Note: The typical maximum Modbus device count between repeaters is 32. Supported
Modbus RTU serial device count may be limited by manufacturer, cable, and
communication speed. Check with the manufacturer for more information.
RS-232 cable length can be up to 15 m (49.2 ft)
Cable Length
RS-485 cable length can be up to 1,520 m (4,987 ft)
RS-232 stranded cable, 3-9 conductors, serial data grade, 20–24 AWG
RS-485 stranded cable, 0.6 mm (22 AWG) 3-wire twisted, shielded cable is acceptable.
Cable
Standard wiring qualified for use with the N2 Bus or FC Bus is acceptable
Stranded 0.6 (22 AWG) 4-wire (two twisted pairs) shielded is acceptable
RS-232: No termination
RS-485: End-of-line (EOL) termination must be set to On (or an EOL terminator installed)
Terminations on the two devices located at either end of each bus segment on an RS-485 bus. The EOL
switches must be set to Off (or EOL termination disabled) for all other devices on the bus
segment on an RS-485 bus.

16 NAE55 Installation Guide

Table 15: M-Bus protocol rules (bus topology)
Category Rules
One direct M-Bus serial (RS-232) connection to either RS232C port is supported; connection requires an
RS232-to-M-Bus Level Converter on the RS232C serial port.
General One direct M-Bus (RS-485) connection to either FC Bus port is supported; connection requires an RS485-
to-M-Bus Level Converter on the FC Bus port.
No restrictions in topology, but bus topology is strongly recommended
Number of Devices Depends on level converter, logical maximum is 250 devices.
Length depends on cable resistance, capacitance, number of devices, position of devices, and configured
communication speed. Example scenarios to help with calculation:
Maximum Number of Unit Maximum Distance
Maximum Distance for
Baud Rate 1 ,2
Between Converter and
Loads Entire Bus
Devices

1
5,000 m (16,404 ft)
(2 x 1.0 mm [18 AWG], shield
64 3,000 m (9,842 ft)
recommended, resistance <
90 Ohms)
4,000 m (13,123 ft)
(2 x 1.0 mm [18 AWG],
2400 64 1,000 m (3,281 ft)
shielded, resistance < 90
Ohms)
4,000 m (13,123 ft)
Line Length and Type (2 x 0.8 mm [20 AWG],
250 350 m (1,148 ft)
shielded, resistance < 30
Ohms)
4,000 m (13,123 ft)
(2 x 0.8 mm [20 AWG],
64 350 m (1,148 ft)
shielded, resistance < 30
Ohms)
9,600
1,000 m (3,281 ft)
(2 x 0.8 mm [20 AWG],
250 350 m (1,148 ft)
shielded, resistance < 30
Ohms)
1,000 m (3,281 ft)
(2 x 0.8 mm [20 AWG],
38,400 64 350 m (1,148 ft)
shielded, resistance < 30
Ohms)
Cable Twisted pair cable (shielding optional)
Termination No termination
1 Unit load is a defined standby current. A device is permitted a current drain of one unit load by default but may consume more if it
is shown at the device (as an integer) and in documentation.
2
2 Use M-Bus Repeaters to increase the length and the number of unit loads permissible.

Table 16: KNX protocol rules

Category Rules and Maximums
General No restrictions in topology
Number of Devices Depends on chosen topology and cable type.
Twisted pair cable recommended; length depends on cable resistance, capacitance, number
Line Length and Type
devices, position of devices, and communication speed.

NAE55 Installation Guide 17

Table 16: KNX protocol rules
Category Rules and Maximums
Copper, solid and stranded wires with outer sheath, one- or two-twisted pair; 0.8 to 1.0 mm
(20 to 18 AWG)
Cable
Screen is required and must cover the entire diameter.
Drain wire: Diameter minimum 0.5 mm (26 AWG)
Termination No termination
Manufacturer's Quality
At least ISO 9002
Management System

Table 17: Network Engine to Level Converter connection rules (M-Bus only)
Category Rules and Maximums
Use either an RS-232 or RS-485 connected level converter or a network connected level
General
converter.
Number Devices Use either one serial level converter or five network level converters per trunk.
RS-232: Level converter maximum length on 15 m (50 ft)
RS-485: Level converter maximum length on 1,500 m (5,000 ft)
Line Length and Type Network level converter: maximum length of 2,000 m (6,600 ft) for plastic/glass fiber optic
with external adapter
10/100 BaseT: 100 m (330 ft) CAT5 cable
Termination No termination

Table 18: Guidelines for LonWorks network bus topology

Maximum Segment Length with Maximum Segment Length with

Cable Type 1
FTT10 Devices Only FTT10 and/or LPT10/11 Devices

1
Belden 85102 Cable 2,700 m (8,850 ft) 2,200 m (7,200 ft)
Belden 8471 Cable 2,700 m (8,850 ft) 2,200 m (7,200 ft)
Level IV 22 AWG 1,400 m (4,600 ft) 1,150 m (3,770 ft)
JY (St.) Y 2 x 2 x 0.8 900 m (2,950 ft) 750 m (2,460 ft)
Note: For the bus topology, the maximum length stub cable is 3 m (10 ft), and the stub lengths must be calculated
into the overall segment length.
1 FTT: Free Topology Twisted Pair Transceiver; LPT: Link Power Twisted Pair Transceiver.

Table 19: Guidelines for LonWorks network free topology

Maximum Segment Length with
Cable Type Maximum Node-to-Node Distance
FTT10 and/or LPT10/11 Devices
Belden 85102 Cable 500 m (1,640 ft) 500 m (1,640 ft)
Belden 8471 Cable 500 m (1,640 ft) 500 m (1,640 ft)
Level IV 22 AWG 400 m (1,300 ft) 500 m (1,640 ft)
JY (St.) Y 2 x 2 x 0.8 320 m (1,050 ft) 500 m (1,640 ft)

18 NAE55 Installation Guide

Table 20: Maximum number of devices per LonWorks network segment
Device Type Maximum Allowed
64 nodes if repeaters are not used; 255 nodes if repeaters
FTT10 Nodes Only
are used
Mixed FTT10 and LPT-10/11 Nodes ([FTT10 x 2] + LPT10/11) < 128
Physical Layer Repeaters Maximum of 1 per segment
Terminators
Bus Topology Two bus type EOL terminators required (NU-EOL202-0)
Free Topology One free topology terminator required (NU-EOL203-0)
Notes:
• Each LPT10/11 channel segment (between repeaters) requires its own power supply. Other factors, such as power
consumption of individual LPT10/11 devices, may limit a segment to fewer devices.
• The MS-NAE552x-x models that support LonWorks Network trunks do not have an internal network terminator.

Table 21: NAE55 with integrations trunk options

Trunk Type Supported Trunk Application
• 2 RS485 or
• 2 RS232 or
• 2 TCP or
Modbus
• 1 RS232 + 1 RS485 or
• 1 RS232 + 1 TCP or
• 1 RS485 + 1 TCP
• 2 RS485 or
• 2 RS232 or
• 2 TCP or
M-Bus
• 1 RS232 + 1 RS485 or
• 1 RS232 + 1 TCP or
• 1 RS485 + 1 TCP
• 1 RS485 Modbus + 1 RS485 M-Bus or
• 1 RS232 Modbus + 1 RS232 M-Bus or
• 1 TCP Modbus + 1 TCP M-Bus or
• 1 RS232 Modbus + 1 RS485 M-Bus or
Modbus and M-Bus • 1 RS485 Modbus + 1 RS232 M-Bus or
• 1 TCP Modbus + 1 RS232 M-Bus or
• 1 TCP Modbus + 1 RS485 M-Bus or
• 1 RS232 Modbus + 1 TCP M-Bus or
• 1 RS485 Modbus + 1 TCP M-Bus
• 1 KNX (routing mode) or
KNX
• 3 KNX (tunneling mode)

Repair information Batteries removed from this device must be recycled

or disposed of in accordance with local, national, and
If you replace a network engine for any reason or add a regional regulations. Only trained technicians or qualified
new network engine to a site, you must update the site building maintenance personnel should service Johnson
registration to ensure that the new network engine is Controls products.
recognized and able to communicate on the Metasys
system site. For details refer to the Replacing an NAE Ordering information
section in the NAE Commissioning Guide (LIT-1201519).
Except for replacing the data protection battery, the The following table lists the product code numbers for all
network engine cannot be repaired in the field. If the available NAE55 network engines based on model. If you
network engine fails to operate, it must be replaced. receive an NAE55 engine from the factory that is imaged
with Release 10.1, you can field-upgrade the engine to
Release 11.0 if the upgrade is supported.

NAE55 Installation Guide 19

 Note: Some network engines are also available in
a Buy American version (add a G after the product
code number). For the European version, add an
E after the product code number. For repair parts,
specify 703 in place of the last digit of the product
code number.
Table 22: NAE55-3 ordering information (Release 8.1 or 11.0)
Product Code Number Release Description
NAE55 Network Automation Engines: Requires a 24 VAC power supply. Each
MS-NAE55xx-x (Base model includes two RS-232-C serial ports, two USB serial ports, two RS-485
N/A
Features of Each NAE55) ports, one Ethernet port, and one MS-BAT1010-0 Data Protection Battery.
Supports a BACnet IP network.
Supports two third-party trunks (Modbus RTU or TCP, M-Bus, or KNX) and two
N2 or two BACnet MS/TP (RS-485) trunks (or one N2 trunk and one BACnet
MS-NAE5510-3 11.0
MS/TP trunk). Supports up to 100 devices on each N2 or BACnet MS/TP trunk.
This model is a BACnet BTL-Listed controller at Protocol Revision 15 (PR15).
Supports two N2 Bus or two BACnet MS/TP (RS-485) trunks (or one N2 Bus
trunk and one BACnet MS/TP trunk).
Note: This model is UL 864 10th Edition UUKL/ORD-C100-13 UUKLC
Standard for Smoke Control Equipment for Release 8.1 only. Refer to
MS-NAE5510-3U
1
8.1 the Metasys® System UL 864 10th Edition UUKL/ORD-C100-13 UUKLC Smoke
1
Control System Technical Bulletin (LIT-12012487) for detailed specifications,
requirements, and procedures for installing and operating UUKL 864
Listed Metasys system devices. For example, in order to be UL/cUL
compliant, this model must be pre-installed and pre-wired in a standard
or custom panel built at the Johnson Controls Reynosa factory.
Supports two third-party trunks (Modbus RTU or TCP, M-Bus, or KNX) and two
N2 or two BACnet MS/TP (RS-485) trunks (or one N2 trunk and one BACnet
MS/TP trunk); includes an internal modem. Supports up to 100 devices on
MS-NAE5511-3 11.0 each N2 or BACnet MS/TP trunk. This model is a BACnet BTL-Listed controller
at Protocol Revision 15 (PR15).
Note: Modem functions are no longer available after this engine is
updated with Metasys Release 10.0 or later.
Supports a LonWorks trunk, two third-party trunks (Modbus RTU or TCP, M-
Bus, or KNX), or two N2 trunks/BACnet MS/TP (RS-485) trunks (or one N2 trunk
MS-NAE5520-3 11.0 and one BACnet MS/TP trunk). Supports up to 255 devices on the LonWorks
trunk. Supports up to 100 devices on each N2 or BACnet MS/TP trunk. This
model is a BACnet BTL-Listed controller at Protocol Revision 15 (PR15).
Supports a LonWorks trunk, two third-party trunks (Modbus RTU or TCP, M-
Bus, or KNX), or two N2 trunks/BACnet MS/TP (RS-485) trunks (or one N2 trunk
and one BACnet MS/TP trunk); includes an internal modem. Supports up to
255 devices on the LonWorks trunk. Supports up to 100 devices on each N2 or
MS-NAE5521-3 11.0 BACnet MS/TP trunk. This model is a BACnet BTL-Listed controller at Protocol
Revision 15 (PR15).
Note: Modem functions are no longer available after this engine is
updated with Metasys Release 10.0 or later.
1 The older MS-NAE5510-2U model may also be available.

20 NAE55 Installation Guide

Table 23: Network engines accessories ordering information
Product Code Number Description
Replacement data protection battery for NAE35, NAE45, and NCE25. Rechargeable
MS-BAT1020-0
NiMH battery: 3.6 V 500 mAh, with a typical life of 5 to 7 years at 21°C (70°F)
Replacement data protection battery for NAE55. Rechargeable gel cell battery: 12 V, 1.2
MS-BAT1010-0
Ah, with a typical life of 3 to 5 years at 21°C (70°F)
Pocket-sized web server that provides a wireless mobile user interface to Metasys field
controllers, thermostats, and smart rooftop units. Refer to the Mobile Access Portal
TL-MAP1810-xx Gateway Catalog Page (LIT-1900869) to identify the appropriate product for your region.
Note: The MAP Gateway serves as a replacement for the BTCVT, which is no
longer available but continues to be supported.
DVD with Network Engine software images for all NAEs and NCEs; for upgrading
MS-MULTENGSW-6
existing, engine-only (no ADS/X) installations.
License enabling Metasys Export Utility software for new installation. Software may be
MS-EXPORT-0
obtained by electronic download from the Licensing Portal or by ordering a DVD copy.
MS-COPY-EXPORT DVD reproduction of Metasys Export Utility product, unlicensed
AS-XFR100-1 Power transformer (Class 2, 24 VAC, 92 VA maximum output), with enclosure
AS-XFR010-1 Power transformer (Class 2, 24 VAC, 92 VA maximum output), no enclosure
Recommended UPS for NxE85 model: APC Smart-UPS SC 450 VA, 280 W, 120 VAC input/
SC450RM1U (OEM Part No.)
output with NEMA 5-15R output connections

Table 24: Modbus accessories ordering information

Product Code Number Description
RS232-to-RS485 converter, 230 VAC
IU-9100-8401 (Europe)
Order this accessory in AOMS from the Essen Distribution Center.
RS232-to-RS485 converter, 24 VAC
IU-9100-8404 (Europe) or For the European market, order this accessory in AOMS from the Essen Distribution
BM485-CIP (North America) Center. For the North American market, order this accessory from duTec (http://
www.interfaceconverter.com or 1-800-248-1632), specify vendor #290904

Table 25: M-Bus accessories ordering information

Product Code Number Description
SIS-MBUSSCSL-1E M-Bus level converter for up to 6 unit loads, 24V AC/DC (RS-232 connection)
SIS-MBUSSCLL-0E M-Bus level converter for up to 100 unit loads, 24V AC/DC (RS-232 connection)
SIS-MBUSNCLL-0E M-Bus level converter for up to 100 unit loads; 24 VAC/VDC (IP connection)
SIS-MBUSNCLH-0E M-Bus level converter for up to 100 unit loads; 230 VAC (IP connection)
SIS-MBUSRPLL-0E M-Bus repeater for up to 100 unit loads, 24V AC/DC
SIS-MBUSRPLH-0E M-Bus repeater for up to 100 unit loads; 230 VAC
INT-DX-KAB01 Optional connection cable SUB-D to RJ-12 for use with SIS-MBUSSCLL-0E
Note: Order these accessories in AOMS from the Essen Distribution Center.

Table 26: KNX accessories ordering information

Product Code Number Description
SIS-KNXNIXL-0E KNX IP interface module to connect KNX line through Ethernet to a network engine
KNX IP router to connect KNX line through Ethernet to a network engine, including line
SIS-KNXNRXL-0E
or area coupler functionality
Note: Order this accessory in AOMS from the Essen Distribution Center.

NAE55 Installation Guide 21

Table 27: Modbus training tool ordering information
Course number Course title and description
VGE Tool Software Training (North America)
C-10077-EN
The VGE tool is required to generate custom Modbus mapping tables.
VGE Tool Software Training (Europe and Asia)
PTK-CONT-26
The VGE tool is required to generate custom Modbus mapping tables.
Note: Modbus Integrations require one or more vendor Modbus definition (VMD) tables for specific third-party
equipment. You can purchase tables from your regional System Integration Services (SIS) office, or you can create
the tables with the VMD Generator Express (VGE) tool. To obtain a license, attend the training listed in this table.

Technical specifications
Table 28: NAE55xx-3 (UL 916, Energy Management) and NAE5510-3U (UL 864, Smoke Control) technical
specifications
Dedicated nominal 24 VAC, Class 2 power supply (North America), SELV power supply
Power Requirement
(Europe), at 50/60 Hz (20 VAC minimum to 30 VAC maximum)
Power Consumption 50 VA maximum
Ambient Operating Conditions 0°C to 50°C (32°F to 122°F); 10% to 90% RH, 30°C (86°F) maximum dew point
Ambient Storage Conditions -40°C to 70°C (-40°F to 158°F); 5% to 95% RH, 30°C (86°F) maximum dew point
Supports data protection on power failure. Rechargeable gel cell battery: 12 V, 1.2 Ah,
Data Protection Battery
with a typical life of 3 to 5 years at 21°C (70°F); Product Code Number: MS-BAT1010-0
Maintains real-time clock through a power failure. Onboard cell; typical life 10 years at
Clock Battery
21°C (70°F)
Processor 1.46 GHz Intel® Atom® Bay Trail E3815 processor for MS-NAE55xx-3 models
16 GB flash nonvolatile memory for operating system, configuration data, and
Memory operations data storage and backup for MS-NAE55xx-3 models.
2 GB DDR3 SDRAM for operations data dynamic memory for all models
NAE5510-3U (UL 864): Johnson Controls OEM Version of Microsoft® Windows®
Operating System Embedded Standard 7 with SP1 (WES7)
NAE55xx-3: (UL 916): Wind River® Linux LTS 17 (LTS=long-term support)
• One Ethernet port; 10/100/1,000 Mbps; 8-pin RJ-45 connector
• Two optically isolated RS-485 ports; 9.6k, 19.2k, 38.4k, or 76.8k baud; pluggable and
keyed 4 position terminal blocks (RS-485 terminal blocks available on NAE55 models
only)
• Two RS-232-C serial ports, with standard 9-pin sub-D connectors, that support all
Network and Serial Interfaces standard baud rates
• Two USB 2.0 serial ports; standard USB connectors support an optional, user-
supplied external modem (no longer supported at Release 10.0 or later)
• One LonWorks port; FTT10 78 Kbps; pluggable, keyed 3-position terminal block
(LonWorks port available on NAE552x-x models only)
Plastic housing with internal metal shield
Housing
Plastic material: ABS + polycarbonate; Protection: IP20 (IEC 60529)
Mounting On a flat surface with screws on four mounting feet or on a dual 35 mm DIN rail
Dimensions 226 mm x 332 mm x 96.5 mm (8.9 in. x 13.1 in. x 3.8 in.) including mounting feet
(Height x Width x Depth) Minimum space for mounting: 303 mm x 408 mm x 148 mm (12.0 in. x 16.1 in. x 5.8 in.)
Shipping Weight 2.9 kg (6.4 lb)

22 NAE55 Installation Guide

Table 28: NAE55xx-3 (UL 916, Energy Management) and NAE5510-3U (UL 864, Smoke Control) technical
specifications
United States: UL Listed, File E107041, CCN PAZX, UL 916, Energy Management
Equipment, FCC Compliant to CFR47, Part 15, Subpart B, Class A
Compliance UL Listed, File S4977, UL 864 UUKL/UUKLC 10th Edition Listed, Smoke Control Units
and Accessories for Fire Alarm Systems Equipment (MS-NAE5510-3U model only with
Release 8.1 software)
Canada: UL Listed, File E107041, CCN PAZX7, CAN/CSA C22.2 No. 205, Signal Equipment,
Industry Canada Compliant, ICES-003
UL Listed, File S4977, UL 864 UUKL/ORD-C100-13 10th Edition Listed, Smoke Control
Units and Accessories for Fire Alarm Systems (MS-NAE5510-3U model only with Release
8.1 software)
Europe: CE Mark - Johnson Controls declares that this product is in compliance with the
essential requirements and other relevant provisions of the EMC Directive.

Australia and New Zealand: RCM Mark, Australia/NZ Emissions Compliant

BACnet International: BTL 135-2016 Listed B-BC/B-BBMD, Protocol Revision 15
FIPS 140-2 Level 1: Compliant with Federal Information Processing Standard (NAE55s
at Release 11.0 only)

The performance specifications are nominal and conform to acceptable industry standard. For application at conditions beyond
these specifications, consult the local Johnson Controls office. Johnson Controls shall not be liable for damages resulting from
misapplication or misuse of its products.

Single point of contact Product warranty

APAC Europe NA/SA This product is covered by a limited warranty, details
JOHNSON CONTROLS JOHNSON CONTROLS JOHNSON CONTROLS of which can be found at www.johnsoncontrols.com/
C/O CONTROLS PRODUCT WESTENDHOF 3 507 E MICHIGAN ST buildingswarranty.
MANAGEMENT 45143 ESSEN MILWAUKEE WI 53202
NO. 32 CHANGJIJANG RD NEW GERMANY USA
Software terms
DISTRICT
Use of the software that is in (or constitutes)
WUXI JIANGSU PROVINCE 214028 this product, or access to the cloud, or hosted
CHINA services applicable to this product, if any, is
subject to applicable end-user license, open-source
North American emissions compliance software information, and other terms set forth at
www.johnsoncontrols.com/techterms. Your use of this
United States product constitutes an agreement to such terms.
This equipment has been tested and found to comply with Patents
the limits for a Class A digital device pursuant to Part 15
of the FCC Rules. These limits are designed to provide Patents: https://jcipat.com
reasonable protection against harmful interference when
this equipment is operated in a commercial environment. Contact information
This equipment generates, uses, and can radiate radio Contact your local branch office:
frequency energy and, if not installed and used in www.johnsoncontrols.com/locations
accordance with the instruction manual, may cause
harmful interference to radio communications. Operation Contact Johnson Controls: www.johnsoncontrols.com/
of this equipment in a residential area may cause harmful contact-us
interference, in which case the users will be required to
correct the interference at their own expense.

Canada
This Class (A) digital apparatus meets all the requirements
of the Canadian Interference-Causing Equipment
Regulations.
Cet appareil numérique de la Classe (A) respecte toutes
les exigences du Règlement sur le matériel brouilleur du
Canada.

NAE55 Installation Guide 23

© 2020 Johnson Controls. All rights reserved. All specifications and other information shown were current as of document revision and
are subject to change without notice.

www.johnsoncontrols.com