Network Automation Engines (NAEs) - Metasys - LIT-1201519 - MS-NAE35xx-2 - MS-NAE45xx-2 - MS-NAE5510-2U - MS-NAE5510-3U - MS-NAE551S-2 - MS-NAE55xx-3 - MS-NCE25xx-0 - MS-NXE85SW-x - Supervisory Device - NAE35 Network Automation Engine - NAE45 Network Automation Engine - NAE55 Network Automation Engine - NAE85 Network Automation Engine - NCE25 Network Control Engine - 11.0

NAE Commissioning Guide

Product
Network Engines > Network Automation Engines > NAE85 Network Automation Engine
Network Engines > Network Automation Engines > NAE35 Network Automation Engine
Network Engines > Network Automation Engines > NAE45 Network Automation Engine
Network Engines > Network Automation Engines > NAE55 Network Automation Engine
Document type
Commissioning Guide
Document number
LIT-1201519
Version
11.0
Revision date
2022-02-09

NAEs are web-enabled, Ethernet-based, supervisory controllers that connect BAS networks to IP networks and the web, and allow you to monitor and control BAS field devices from a computer using the Launcher application. You use the Launcher application to log in to the NAE . If the Launcher is not already installed on your machine, you are prompted to install it when you attempt to log in using a web browser. To install the Launcher, use either a supported version of Windows® Internet Explorer®, Google® Chrome™, or Apple® Safari®. (Other web browsers may work, but are not tested or supported.) Refer to the Launcher Installation Instructions (LIT-12011783) .

The NAE Series of network engines is a scalable line of supervisory controllers with varying network, trunk, and field device capacities to meet the requirements of different applications.

All NAEs provide scheduling, alarm and event management, trending, energy management, data exchange, and password protection. NAEs are factory-loaded with a supported Linux operating system and the current release of the Metasys system software. The NAEs support many different vendor integrations from which you can select during commissioning, such as Modbus, M-Bus, KNX, Tyco® C•CURE®/victor®, Zettler, and OPC Unified Architecture (UA). Each NAE can run two integrations. To commission each protocol, refer to the appropriate document:

  • Modbus - Network Engine Commissioning for Modbus Vendor Integration Application Note (LIT-12013150)
  • M-Bus - Network Engine Commissioning for M-Bus Vendor Integration Application Note (LIT-12013149)
  • KNX - Network Engine Commissioning for KNX Vendor Integration Application Note (LIT-12013148)
  • C•CURE/victor - Network Engine Commissioning for C•CURE/victor Integration Application Note (LIT-12013151)
  • Zettler - Network Engine Commissioning for Zettler MX Speak 6.0 Vendor Integration Application Note (LIT-12013269)
  • OPC UA - Network Engine Commissioning for OPC UA Client Vendor Integration Application Note (LIT-12013545)