NAE

NAE Commissioning GuideCode No. LIT-1201519MS-NAE35xx-x, MS-NAE45xx-x, MS-NAE55xx-x, MS-NIE55xx-x,

MS-NCE25xx-x, MS-NIE8500-x, NAE-8500-x Software Release 6.0Issued January 30, 2013

Supersedes January 4, 2012Refer to the QuickLIT website for the most up-to-date version of this document.

Document Introduction.............................................................................................................4Related Documentation.............................................................................................................4NAE Commissioning Overview................................................................................................5

Network Automation Engines (NAEs)...............................................................................................5NAE35 Models......................................................................................................................................6NAE45 Models......................................................................................................................................6NAE55 Models......................................................................................................................................6NIE55 Models........................................................................................................................................6NCE25 Models......................................................................................................................................6NxE85 Models.......................................................................................................................................7MS/TP Communications Bus.............................................................................................................7Metasys Network Sites.......................................................................................................................7NAE Commissioning...........................................................................................................................8NAE Configuration..............................................................................................................................9Site Management Portal User Interface..........................................................................................11Ready Access Portal UI....................................................................................................................12Metasys System Help.......................................................................................................................12Browser Recommendations for Downloading the Launcher.......................................................12System Configuration Tool..............................................................................................................12CCT.....................................................................................................................................................13Archive Databases............................................................................................................................13NAE Disk Image Updates and Archive Database Upgrades.........................................................14Site Director.......................................................................................................................................14NAE Computer Name........................................................................................................................14NAE Object Name.............................................................................................................................15Basic Access Operating Mode........................................................................................................15Logon User Names and Passwords................................................................................................15NAE Connectivity..............................................................................................................................16Modems and Dial-Out Features.......................................................................................................16Time Zone, Date, and Time Management........................................................................................18Alarm and Events..............................................................................................................................18Serial Printer DDA (Alarm Printer)...................................................................................................19Recommended Serial Printer..............................................................................................................19Serial Printer Installation Considerations............................................................................................21E-mail Notification.............................................................................................................................22Pager Notification.............................................................................................................................23Simple Network Management Protocol (SNMP) Notification........................................................24Initial Default NAE Configuration....................................................................................................24System and User Preferences.........................................................................................................26Reset Device Command...................................................................................................................26

Detailed Procedures................................................................................................................27Using Launcher to Discover an NAE..............................................................................................27Establishing a Direct Connection to an NAE.................................................................................30Preparing an NAE for an Ethernet LAN That Supports DHCP and DNS......................................30

1NAE Commissioning Guide

http://cgproducts.johnsoncontrols.com/default.aspx

Preparing an NAE for an Ethernet LAN without DHCP and without DNS Support (NAE UsesAPIPA)................................................................................................................................................33Preparing an NAE for an Ethernet LAN without DHCP and without DNS Support (NAE UsesStatic IP Address).............................................................................................................................34Preparing an NAE for an Ethernet LAN That Supports DHCP but Not DNS................................35Preparing an NAE for an Ethernet LAN That Supports DNS but Not DHCP................................36Enabling the Serial Printer DDA......................................................................................................36Preparing the NxE85 for Serial Printing..............................................................................................39Creating Audit Entries for Discarded Events.................................................................................39Accessing the Site Management Portal UI on an NAE..................................................................39Establishing Basic NAE Parameters in the Focus Screen............................................................40Establishing the NAE Network Parameters....................................................................................41Establishing the NAE Direct-Connect and Modem Parameters...................................................42Creating E-mail Alarm and Event Notifications and Destinations...............................................45Creating Pager Alarm and Event Notifications and Destinations................................................48Creating NAE SNMP Alarm Notifications and Destinations.........................................................52Setting the Time, Date, Time Zone, and Time Synchronization....................................................55Setting up the NAE Alarm Parameters............................................................................................55Editing the Existing Alarm Parameters...............................................................................................55Creating a New Alarm.........................................................................................................................57Designating an NAE as the Site Director........................................................................................58Changing the Site Director with the SCT............................................................................................60Removing User Accounts from a Demoted Site Director.............................................................60Moving the Security Database and Clearing It from the Demoted Site Director.................................60Establishing a Dial-up Connection to an NAE...............................................................................60Configuring an NAE to Dial Out to an ADS/ADX............................................................................60Printing Information from the NAE Site Management Portal UI...................................................62Replacing an NAE.............................................................................................................................63

Troubleshooting.......................................................................................................................63Common NAE Problems..................................................................................................................63Corrupted NAE Memory......................................................................................................................63Logon Problems..................................................................................................................................64Network Connection Related Problems..............................................................................................64NAE Reset Related Problems.............................................................................................................64Troubleshooting Guide........................................................................................................................64NAE Diagnostic Tools.......................................................................................................................67NAE Light-Emitting Diode (LED) Status Indicators.............................................................................68NAE35/NAE45 LED Startup Sequence..............................................................................................70NAE55/NIE55 LED Startup Sequence................................................................................................71NCE25 LED Startup Sequence...........................................................................................................71Diagnostic Tab.....................................................................................................................................71Summary Tab......................................................................................................................................73Troubleshooting Procedures...........................................................................................................74Verifying Ethernet/IP Network Communications (Ping).......................................................................74Pre-boot Execution Environment (PXE)..............................................................................................74Determining the NAE IP Address and Device Name for a LAN Connection......................................75Determining the NAE IP Address By Using the NCT..........................................................................75Determining the NAE IP Address and Device Name through a Serial Port Monitor...........................75Notes on Setting a Computer to Use APIPA...................................................................................76For Versions of Windows OS That Do Not Support APIPA.................................................................77

Technical Specifications.........................................................................................................77


Appendix: Time Zone, Date, and Time Management............................................................80Time Zone, Date, and Time Management Introduction..................................................................80Overview of Time Synchronization.................................................................................................80ADS/ADX Site Director with NAEs/NIEs.............................................................................................80NIE and Child Devices........................................................................................................................81Time Synchronization Methods.......................................................................................................81Windows Time Synchronization..........................................................................................................81Multicast Time Synchronization..........................................................................................................81BACnet Time Synchronization............................................................................................................82Example Network..............................................................................................................................82Time Zone..........................................................................................................................................82Site Time Server................................................................................................................................83Time in Device Object and UI Status Bar........................................................................................83Steps for Successful Time Management........................................................................................83Verifying the Site Director Defined for an Engine/Server....................................................................84Setting the Time Synchronization Method..........................................................................................84NAE/NIE Is the Site Director...............................................................................................................85ADS/ADX Is the Site Director..............................................................................................................87Configuring Additional Multicast Time Synchronization Settings........................................................90

Appendix: Configuring and Maintaining Preferences..........................................................92Configuring and Maintaining Preferences Introduction................................................................92Preferences Concepts......................................................................................................................92System and User Preferences............................................................................................................92Managing Preferences........................................................................................................................94Detailed Procedures.........................................................................................................................95Configuring Preferences.....................................................................................................................95Restoring Default System Preferences...............................................................................................95Copying Preferences between Devices..............................................................................................95Restoring Default User Preferences...................................................................................................95Removing User Preference Files........................................................................................................95Copying User Preferences to Another User........................................................................................96Preserving Preferences in an Upgrade...............................................................................................96


Document IntroductionThis document describes how to commission a Network Automation Engine (NAE), Network Integration Engine(NIE), or Network Control Engine (NCE) for network connectivity in several network scenarios; how to access theMetasys® system Site Management Portal UI on an NAE; how to configure the basic NAE parameters for initialoperation on the network; and how to troubleshoot an NAE.

This document also describes how to configure the NAE Destination Delivery Agents (DDAs) for sending alarm andevent messages via e-mail, pager, and Simple Network Management Protocol (SNMP).

This document does not describe how to mount, wire, or power on an NAE. Also, this document does not describehow to build or download an archive database for a Metasys system site or how to configure an NAE to monitor andcontrol a Building Automation System (BAS).

Note: In this document, NAE refers to all NAE35, NAE45, NAE45-Lite, NAE55, NIE55, NCE25, NxE85 models,unless noted otherwise. Refer to the NxE85 Commissioning Guide (LIT-12011044) for additional informationspecific to the NxE85 Series network engines. Refer to the NCE Technical Bulletin (LIT-12011267) foradditional information specific to the NCE25 Series network control engines.

Related DocumentationTable 1: NAE Related Documentation

LIT or Part NumberSee DocumentFor Information OnLIT-1201527Metasys System Extended Architecture

Overview Technical BulletinOverviewof theMetasysSystemNetwork Featuresand Functions

LIT-1201612Metasys System Extended ArchitectureGlossary Technical Bulletin

Definition of Terms, Concepts, and AcronymsCommonly Used to Describe Metasys System

LIT-1201578Network and IT Considerations for theIT Professional Technical Bulletin

General Network and Information TechnologyDefinitions and Concepts, and Creating a PrinterDDA for an NAE

LIT-12017931Metasys System HelpDaily Operation of the Metasys System Network,Navigating the UI, andMonitoring and ControllingBAS Networks

Part No. 24-10050-6NAE35/NAE45 Installation InstructionsInstallation Considerations and Guidelines,Mounting, Wiring, and Starting up an NAE35 orNAE45

Part No. 24-10051-43NAE55/NIE55 Installation InstructionsInstallation Considerations and Guidelines,Mounting, Wiring, and Starting up an NAE55 orNIE55

Part No. 24-10143-63NCE25 Installation InstructionsInstallation Considerations and Guidelines,Mounting, Wiring, and Starting up an NCE25

LIT-12011267NCE Technical BulletinAdditional Guidelines for Commissioning andConfiguring and NCE25 Network Engines

LIT-12011044NxE85 Commissioning GuideAdditional Guidelines for Commissioning NxE85Network Engines

LIT-12011524NAE/NIE Update Tool Technical BulletinUpdating the NAE/NIEDisk Image to NewSoftwareRelease Versions

LIT-12011688ADS-Lite Installation and UpgradeInstructions Wizard2

Installing the ADS-Lite Software

LIT-12011521ADS, ADX, and SCT Installation andUpgrade Instructions Wizard2

Installing theADS, ADX, andSystemConfigurationTool (SCT) Software

LIT-1201534SCT Technical BulletinCreating, Editing, and Loading Archive Databaseswith the SCT

LIT-1201683N2 Integration with the NAE TechnicalBulletin

Integrating N2 Devices into the Metasys SystemNetwork


Table 1: NAE Related DocumentationLIT or Part NumberSee DocumentFor Information OnLIT-12011529CCT Installation InstructionsHow to Install the Controller Configuration Tool

(CCT) Software

LIT-120111471Controller Tool HelpUsing the Controller Configuration Tool

LIT-1201532NAE/NCE Protocol ImplementationConformance Statement TechnicalBulletin

NAE/NCE BACnet Protocol Conformance

LIT-12011034MS/TP Communications Bus TechnicalBulletin

How to Set Up a Master-Slave/Token-Passing(MS/TP) Communications Bus

LIT-12011295ZFR1800 Series Wireless Field BusSystem Technical Bulletin

Enabling NAEs to Communicate with MS/TPControllers over Wireless Mesh Networks

LIT-1201668LONWORKSNetwork Integration with NAEand LCS Technical Bulletin

Integrating LONWORKS® Devices into the MetasysSystem Network

LIT-1201535N1 Migration with the NIE TechnicalBulletin

Migrating N1 Networks to the Metasys SystemNetwork

LIT-1201531BACnet System Integration withNAE/NCE Technical Bulletin

Integrating BACnet® MS/TP and BACnet IPDevices into the Metasys System Network

LIT-1201528Security Administrator SystemTechnical Bulletin

Security Issues, IncludingAddingUsers andRolesto the SystemandConfiguringStandard andBasicAccess Modes

LIT-12011783Launcher Installation InstructionsInstalling the Launcher Application

LIT-12011742Launcher HelpUsing the Launcher, Accessing aMetasys SystemNetwork via Dial-up Connections

LIT-1201639Metasys System Extended ArchitectureDirect Connection and Dial-UpConnection Application Note

Dialing into a Metasys System Network from aComputer

1 This LIT number represents a printer friendly version of the help.2 Use the wizard to generate instructions specific to your system.

NAE Commissioning OverviewNetwork Automation Engines (NAEs)NAEs are web-enabled, Ethernet-based, supervisory controllers that connect BAS networks to IP networks and theweb, and allow you to monitor and control BAS field devices from a computer using the Launcher application. Startingat Release 6.0, you use the Launcher application instead of a web browser to log on to the NAE. If the Launcher isnot already installed on your machine, you are prompted to install it after you attempt to log on using the web browser.For the purpose of installing the Launcher, useWindows® Internet Explorer® Version 8.0 or 9.0. (Other web browsersmay work, but are not tested or supported.) Refer to the Launcher Installation Instructions (LIT-12011783).

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

All NAEs provide scheduling, alarm and event management, trending, energy management, data exchange, dial-outcapability, and password protection. NAEs are factory-loaded with a supportedMicrosoft®Windows operating systemand the current release of the Metasys system software.


NAE35 ModelsThe NAE35 models:

• integrate one RS485 field bus or one LONWORKS network trunk into a Metasys system network. The NAE351xmodels integrate one N2 Bus or one BACnet MS/TP trunk with up to 50 field controllers. The NAE352x-xxxmodels integrate a single LONWORKS trunk with up to 64 LONWORKS devices.

• monitor and control up to 50 BACnet IP devices over Ethernet at the supervisory level• can serve as a Site Director supervising a maximum of two additional network engines, which can be NAE35 or

NCE25 model engines only

Several NAE35 models provide the Basic Access operating mode as the primary UI. See Basic Access OperatingMode for more information.


• integrate either one RS485 field bus or one LONWORKS network trunk into a Metasys® system network. TheNAE451x models integrate one N2 Bus or one BACnet MS/TP trunk with up to 100 field controllers. The NAE452xmodels integrate a single LONWORKS trunk with up to 127 LONWORKS devices.

Note: The NAE45-Lite supports theMS/TP bus and BACnet IP communication to third-party devices. The NAE45-Litedoes not support the N2 Bus, N1 integration, VND integration, Xl5K integration, LONWORKS network, or wirelesssupervisor (N2).

• monitor and control up to 50 BACnet IP field devices over Ethernet at the supervisory level• can serve as a Site Director supervising a maximum of two additional network engines, which can be NAE35,

NAE45, or NCE25 model engines only

Note: The NAE45-Lite must have an ADS-Lite-A as its Site Director, or be stand-alone. The NAE45-Lite cannot bea Site Director to other engines.


• integrate up to two RS485 field buses into a Metasys system. The NAE551x models integrate two N2 Buses,two BACnet MS/TP trunks, or one N2 Bus and one BACnet MS/TP trunk. Each bus or trunk may contain up to100 field controllers. The NAE552x models can also integrate a LONWORKS network trunk with up to 255 LONWORKS

devices. NAE55 models can also monitor and supervise a number of BACnet IP devices; the total number ofBACnet IP devices depends on the number of objects each device supports.

• can serve as a Site Director supervising a maximum of four other network engines, which can be NAE35, NAE45,NCE25, NAE55 or NIE55 model engines

NIE55 ModelsThe NIE55 models:

• migrate N1 networks into a Metasys system network. NIEs do not integrate BACnet networks, N2 trunks, orLONWORKS networks

• can serve as a Site Director supervising a maximum of four other supervisory devices, which can be NAE35,NAE45, NCE25, NAE55, or NIE55 model engines

NCE25 ModelsThe NCE25 models:

• integrate either one RS485 field bus or one LONWORKS network trunk into a Metasys® system network• NCE256x-x models integrate one BACnet MS/TP trunk with up to 32 MS/TP controllers• NCE251x-x models integrate one N2 Bus with up to 32 N2 controllers• NCE252x-x models integrate a single LONWORKS trunk with up to 32 LONWORKS devices• monitor and control up to 50 IP BACnet field devices over Ethernet at the supervisory level


• provide an integral MS/TP Field Equipment Controller with 33 Input/Output (I/O) points• cannot serve as Site Director except in stand-alone applications

NxE85 ModelsAll NxE85 models ship as NIE85s. Use the ChangeModel utility in the NxE85 UI to change an NxE85 to an NAE85.

The NAE85 models integrate large BACnet IP systems into a Metasys network.

The NIE85 models migrate large N1 networks into a Metasys network.

An NxE85 can serve as a Site Director supervising a maximum of four other supervisory devices, which can beNAE35, NAE45, NCE25, NAE55, NIE55, or NxE85 model engines.

Refer to the NxE85 Commissioning Guide (LIT-12011044) for additional information specific to the NxE85 Seriesnetwork engines.

MS/TP Communications BusThe MS/TP bus is a local network that connects supervisory controllers and field controllers to point interfaces usingBACnet MS/TP protocol. The MS/TP bus consists of two types of buses: the Field Controller (FC) Bus or theSensor/Actuator (SA) Bus. Each bus has its own set of device addresses.

Metasys Network SitesA small Metasys network site comprises a single NAE or multiple NAEs with one of the NAEs designated as the SiteDirector (Figure 1). See Site Director for additional information on Site Director hierarchy and the number of networkengines a Site Director can supervise.

Figure 1: Metasys Network with NAE55 as Site Director for Multiple NAEs


Larger Metasys network sites can comprise multiple NAEs and one or more Application and Data Servers (ADSs)or Extended Application and Data Servers (ADXs) with access to multiple remote sites. On any site with one or moreADSs/ADXs, an ADS/ADX is designated as the Site Director. Figure 2 shows an example of a simple Metasysnetwork with multiple NAEs and an ADS as the Site Director.

Figure 2: Metasys Network with ADS as Site Director for Multiple NAEs

NAE CommissioningNAE commissioning includes preparing the NAE for connectivity, connecting to the NAE, adding the NAE to theprofile list in Launcher, and accessing and logging on to the Site Management Portal UI.

Each Metasys network installation, commissioning, and configuration scenario is unique. In some scenarios, theNAEs (on a Metasys network) may be commissioned and configured before they are installed and connected to thenetwork; in other scenarios, the NAEs are mounted and wired to the network before they are commissioned andconfigured.

Note: NAE installation includes locating, mounting, wiring, and powering on an NAE. See Related Documentationfor references to NAE installation instructions for the various NAE models.

The commissioning tasks, the task order, and the required attribute values (at commissioning) for an NAE aredetermined by the specific Metasys network installation, commissioning, and configuration scenario for the site. TheNAE commissioning procedures presented in this document are the procedures required for most scenarios regardlessof when commissioning occurs.


The first task in commissioning an NAE is to establish a connection with the NAE via the Launcher. If the Launcheris not already installed on your machine, you are prompted to install it after you attempt to log on using the webbrowser. Refer to the Launcher Installation Instructions (LIT-12011783).

Note: The Launcher is a software application installed on each client computer that lets you access any Metasysserver or supervisory engine on the building network, regardless of its software version. Its purpose is toremove the dependency on the public Java® Runtime Environment (JRE) for the Site Management Portaluser interface (UI) at Release 6.0 (or later) by placing a private edition of the JRE on the client computer.For details, refer to the Launcher Help (LIT-12011742).

After a connection is established, you can then access the Site Management Portal on the NAE from the Launcher.See NAE Connectivity for six typical network connection scenarios. See Site Management Portal User Interface andAccessing the Site Management Portal UI on an NAE for more information on accessing and navigating the SiteManagement Portal UI.

After you have accessed the Site Management Portal UI on an NAE, you can configure the NAE:

• object name and basic device parameters• host name (Computer Name), domain name, and network parameter• direct-connect and modem parameters• time and date management parameters• alarm and event parameters• SNMP messages and the network management destination• modem dial-out and dial-up parameters• Site Director status

After commissioning an NAE, you must configure the NAE for the specified job site. Figure 3 is a flowchart thatprovides an overview of the sequence of steps needed to install, commission, and configure a new NAE.

NAE ConfigurationNAE configuration is preparing an NAE in the Site Management Portal UI and the System Configuration Tool (SCT)to operate on a specificMetasys network site, and communicate with, monitor, and control specific BAS field deviceson that site. Configuration also includes preparing the NAE to compile, generate, and communicate informationabout site status, alarms, events, and trends.

You can typically accomplish NAE configuration by downloading a pre-built archive database (from the SCT) thatcontains the device objects, object references, attribute values, logic, graphics, user information, and other referencesand data required for the NAE to perform its specific tasks on the network. See Archive Databases.

You can create and edit an archive database online in the Site Management Portal UI, but in almost all cases, youshould create and edit the NAE archive database offline in the SCT. When you download the database, the valuesin the archive database overwrite the existing values on the commissioned NAE. Refer to the SCT Technical Bulletin(LIT-1201534) for information on creating and downloading archive databases.

After you configure an NAE with an archive database containing user information, you can set up the e-mail, pager,and SNMP DDAs and create specific alarm and event notifications for delivery to specific e-mail, pager, networkmanagement destinations.


Figure 3: NAE Commissioning and Configuration Flowchart


Site Management Portal User InterfaceYou can view and edit NAE parameters and the parameters for associated devices in the Site Management PortalUI installed on the NAE. Access the NAE Site Management Portal UI via the Launcher. See Accessing the SiteManagement Portal UI on an NAE. Figure 4 shows an example of the Site Management Portal UI.

In the Display panel on the right side of the window is a series of tabbed screens. Table 2 provides a brief descriptionof the information that you can view and edit in each tabbed screen. The navigation panel on the left displays thenavigation tree for the BAS network integrations, field devices, field points, and their associated objects that theNAE is monitoring and supervising.

Figure 4: NAE Focus Tab in Edit Mode - Advanced

When you view the online NAE Site Management Portal UI, the border around the panels is blue (Figure 4). Whenyou view the offline SCT UI, the border is black (Figure 5).

Table 2: Metasys Site Management Portal UI Tabbed ScreensAccess Online/Offline

PurposeScreen TabDesignation

BothProvides description and name (label) of device object, the local time anddate, the firmware version, message buffer and alarm, and audit repositorysizes. The Focus tab also identifies the local Site Director and includes generalsite information about the ADS/ADX to which the NAE reports (if applicable).

Focus OR Configuration

BothEstablish communication parameters, including Serial port and internal orexternal Universal Serial Bus (USB) modem configuration.

Communications


Table 2: Metasys Site Management Portal UI Tabbed ScreensAccess Online/Offline

PurposeScreen TabDesignation

BothEstablish Computer Name (host name) for network identity, Local AreaNetwork (LAN), and ADS/ADX dial-up parameters (if applicable).

Network

BothEstablish the NAE e-mail alarm-notifications features common to all e-mailmessages and create unique e-mail message destinations.

Email

BothEstablish the NAE pager alarm-notifications features common to all pagermessages and create unique pager message destinations.

Pager

BothEstablish the NAE Simple Network Management Protocol (SNMP) featurescommon to all SNMP notifications and create unique SNMP messagedestinations.

SNMP

BothProvides the NAE alarm setup and destination information. See Alarm andEvents for a description of the default NAE alarms.

Alarm

OnlineProvides network and field device status information and attribute values forsupervisory and field devices on the NAE field trunks.

Summary

OnlineProvides various status reports to aid in troubleshooting the NAE.Diagnostic

Menus, tab screens, attribute lists, values, and units of measure in the Site Management Portal UI are dynamic andchange in the displayed screen according to the item you select from the navigation tree. Refer to the Object andFeature Tabs section in the Metasys system Help for descriptions of menu items.

Ready Access Portal UIIn addition to the Site Management Portal UI, an alternative, optional interface called the Ready Access Portal UIis also available. This software, which comes with the ADS/ADX software, is targeted to users who access onlyspecific key functions of the Metasys system and perform typical tasks through a more intuitive navigation process.Available via a computer or handheld platform, the Ready Access Portal UI requires only a web browser. For moredetails, refer to the Ready Access Portal Software Catalog Page (LIT-1900538).

Metasys System HelpThe Metasys system Help is the User’s Guide for the Metasys system. The Help provides information on proceduressuch as downloading, global searching, commanding, and scheduling and also contains information on objects, theuser interface, and wizards. The Contents, Index, and Search tabs in the left pane of the Help allow you to findinformation by browsing through defined sections, looking up key terms, or by performing a full-text search of theHelp content. You can print the information appearing in the scrollable region in the right pane of the Help, but toprint larger sections of the Help or the entire Help system, go to the PDF file of the Metasys system Help on theJohnson Controls® QuickLIT literature website. The Metasys system Help menu also provides a link to the Help onQuickLIT. QuickLIT is available at the following website address: http://cgproducts.johnsoncontrols.com/default.aspx

Browser Recommendations for Downloading the LauncherThe Metasys system currently supports the Windows Internet Explorer web browser Versions 8.0 and 9.0 for thepurpose of downloading the Launcher application. Other web browsers may work, but are not tested or supported.After you install the Launcher, you use the Launcher, not the web browser, to open the Site Management Portal UI.

System Configuration ToolThe SCT is an offline software tool used to create, edit, save, and restore the various archive and security databasesthat are used to configure Metasys system networks, ADSs/ADXs, NAEs, and supported field devices. The SCT UIopens in its own window and has a similar look and function to the online Site Management Portal UI (Figure 5).

The SCT allows commissioning of N2 devices by allowing HVAC PRO software, GX-Tool software, and XTMConfigurator software to access the devices on the N2 Bus of an NAE, and allows commissioning of FECs, VMA16s,Input/Output Modules (IOMs) by using the CCT software to access the devices on the field bus of an NAE.


http://cgproducts.johnsoncontrols.com/default.aspx

The SCT Manager is a software tool that allows you to use multiple versions of SCT on your computer. The SCTand SCT Manager are separate software installations included on the ADS/ADX installation disk.

The SCT provides a Simulation feature that allows you to simulate an online supervisory device and test a database’scontrol logic prior to downloading it to an NAE. Using the SCT, you can view and configure multiple sites in onearchive.

Figure 5: SCT UI Screen in Edit Mode

CCTUse the CCT in conjunction with the Metasys system user interface to configure, simulate, and commission FieldEquipment Controllers (FECs), IOMs, and VAV Modular Assembly (VMA) 16s, on an MS/TP bus. You must installCCT on the same computer as SCT software to use the Ethernet Passthru option in SCT.

Archive DatabasesAMetasys archive database contains the configuration information for ADSs/ADXs, NAEs, BAS network integrations,field devices, and field points that make up a single site or multiple sites on a Metasys system network. Multiplearchive databases, representing multiple sites, can reside on a single ADS/ADX running the SCT. The SCT navigationpanel in Figure 5 provides graphical representation of some of the items that may be in a Metasys archive database.

An NAE archive database, which resides in the NAE internal memory, contains only the specific configurationinformation that makes up the network integrations, field devices, and field points that the NAE is supervising. EachNAE retains only its own archive database. You can also save the NAE database in a Metasys archive databaseon an ADS/ADX or another computer using the SCT. A graphical representation of some of the items contained inan NAE archive database is shown in Figure 4 in the Site Management Portal UI navigation panel.

You can upload an NAE archive database to the SCT where it can be saved to a hard disk or other long-term storagemedia. You can also edit an NAE archive database offline in the SCT and download the edited archive database tothe NAE.


NAE Disk Image Updates and Archive Database UpgradesThe NAE operating system, Metasys system software, NAE archive database, and recent NAE operation data resideon the NAE disk image.

Use the NAE/NIE Update Tool to update the NAE disk image to the latest release version of the Metasys systemsoftware. Refer to the NAE/NIE Update Tool Technical Bulletin (LIT-12011524).

When you update an NAE to a new version of the Metasys system software, you must also upgrade the NAE archivedatabase to a new release database. For an overview of the upgrade process, refer to the ADS, ADX, and SCTInstallation and Upgrade Instructions Wizard (LIT-12011521).

Note: The NAE45-0, NAE55-0, and NIE55-0 engines with 256 MB flash memory are not supported at Release 4.1or later. For upgrade options, contact the Johnson Controls Field Support Center.

Site DirectorFor each Metasys system network site, a single network engine or a Metasys server is designated as the SiteDirector. The Site Director UI provides a single point of access to the site and all of the web-enabled devices on thesite; and supports functions such as user logon, user administration, user views, time synchronization, and datatraffic management.

On larger Metasys system networks with one or more ADSs/ADXs, an ADS/ADX is designated as the Site Director.On small network sites without an ADS/ADX, you must designate an NAE as the Site Director.

All NAEs are shipped factory-designated as Site Directors. You must demote any NAE that is not the designatedSite Director on a site. See Designating an NAE as the Site Director for more information.

Note: You can establish or change the logon user name and password for the NAE only when the NAE is designatedas a Site Director. Establish these values before demoting an NAE from Site Director.

If an ADS/ADX is on a site, an NAE cannot be the Site Director. You must demote the NAE to be a child of anADS/ADX. See Designating an NAE as the Site Director for more information.

Note: The NAE45-Lite cannot be a Site Director to other engines. The NAE45-Lite can only be a child device of anADS-Lite-A. You must demote the NAE to be a child of an ADS/ADX. See Designating an NAE as the SiteDirector for more information.

If an NAE85 is the Site Director, it can supervise up to four additional engines on the site: NAE35s, NAE45s, NCE25s,NAE55s, NIE55s, or NxE85s.

If an NAE55 is the Site Director, it can supervise up to four additional engines on the site: NAE35s, NAE45s, NCE25s,NAE55s, or NIE55s.

If an NAE45 is the Site Director, it can supervise up to two additional engines on the site: NAE35s, NAE45s, orNCE25.

If an NAE35 is the Site Director, it can supervise up to two additional NAE35s or NCE25s on the site.

An NCE25 cannot be designated as the Site Director, except in stand-alone applications.

Note: If you attempt to add an NAE to a site and the new NAE exceeds the supervisory device limit for the SiteDirector, the Site Director does not accept the additional device. The Site Director records an error messagein the Site Director Audit Trail each time you attempt to add a new device that exceeds the device limit. Ifyou attempt to add the same device more than once, each attempt fails but no error message is recordedafter the first attempt.

NAE Computer NameThe NAE Computer Name is an editable Network Identification attribute on the NAE Network tab. Devices on theLAN and the Metasys system network use the NAE Computer Name to identify and communicate with the NAEacross the network. Computer Name is synonymous with host name on a network.


Each NAE ships with a unique initial Computer Name value NAExxxxxxxxxxxx, where xxxxxxxxxxxx is the EthernetMAC address of the device without the hyphens. For example, if the NAE’s MAC address is 00-80-66-05-0F-FC,the initial computer name is NAE008066050FFC. Changing the Computer Name value initiates a device reset onthe NAE.

The initial computer name is often useful during commissioning for locating and connecting to an NAE before it isconfigured with an archive database download from the SCT. In most cases, the archive database download fromthe SCT overwrites the initial Computer Name value and determines the NAE Computer Name on the Metasys site.

Changing the NAE Computer Name breaks any existing references between the NAE object and other objects onthe site and may break the existing network connection to other devices on the network.

Important: Starting at Release 2.1.10, the NAE/NIE Update Tool placed restrictions on the Host Name (ComputerName) values you can use for NAE35, NAE45, and NCE25 models. Name values must start with aletter, end with either a letter or a number, and may contain dashes only in the interior of the name.The Host Name must contain a letter other than or in addition to the letter A and digits. For example,A522446 is not valid, but either A522446B or AB52446 are valid. B522446 or C522446 are valid HostNames. This restriction is caused by a known problem with Microsoft Windows CE. Failure to followthe Host Name restrictions results in the Computer Name value changing when an NAE35, NAE45, orNCE25 is updated. Refer to the NAE/NIE Update Tool Technical Bulletin (LIT-12011524) for moreinformation on Host Name restrictions.

Note: Before building the archive database in SCT, you should consult the network administrator or InformationTechnology department to determine if there is an existing protocol for host names (computer names) on thenetwork.

NAE Object NameThe NAE Object Name is an editable attribute on the NAE Focus tab that the Metasys software uses to identify theNAE in the Site Management Portal UI and in the SCT. The Object Name is a label only and is not (necessarily) thesame as the Computer Name. Changing the Object Name merely changes the name that you see in the navigationtree, alarm messages, trend reports, and other screens in the Site Management Portal UI and SCT that refer to theNAE. Changing the Object Name does not impact the object references or network communication with otherdevices on the site. You can change the Object Name at any time. We recommend an intuitive name that clearlyidentifies the NAE in the Site Management Portal UI and Metasys site.

Basic Access Operating ModeBasic Access is a mode of operation allowing users with Basic Access user accounts access to a subset of thestandard user interface capabilities based on their assigned permissions. Basic Access user accounts are createdby Metasys system administrators using the Security Administrator system. Basic Access meets the user interfacerequirements for most building operators. Basic Access is provided on all of the Metasys system engines and serversbut is the primary user interface in the NAE3514, NAE3515, NAE3524, and NAE3525 controllers.

You cannot commission or configure an NAE35 in Basic Access mode. You must log on to the full Site ManagementPortal UI on the NAE35 to commission and configure the device. See Logon User Names and Passwords forinformation on logging on to NAE35 Basic Access.

Logon User Names and PasswordsAll NAEs are shipped with the same initial logon user name. The initial logon user name is MetasysSysAgent, andit is not case sensitive. For theMetasysSysAgent default password, contact your local Johnson Controls representative.

Use the initial user name and password to log on to any NAE the first time you commission the NAE. The ChangePassword screen then appears and prompts you to change the initial default password before continuing. You mustchange the MetasysSysAgent default password when you first log in to a new, factory-fresh NAE, or an NAE thatwas recently updated with the NAE/NIE Update Tool.

Note: The NAE logon user name and password values can only be changed when an NAE is a Site Director. If youwant to change the NAE logon user name or password, you must do so before demoting the NAE from SiteDirector status.


The NAE35 models with Basic Access operation mode require an additional logon user name and password toenable and use the Basic Access mode. The initial logon user name is BasicSysAgent, and it is not case sensitive.You are prompted to create your own account password.

For security reasons, we recommend that you change the logon user name before the NAE goes online in a Metasysnetwork. Refer to the Security Administrator System Technical Bulletin (LIT-1201528) for details.

Note: When you change (or add) an NAE logon user name or password, make sure to record the new user nameand password values and store the new values in a safe location. You cannot access the NAE SiteManagement Portal UI without a valid user name and password.

NAE ConnectivityYou can establish a connection between a computer and an NAE using one of the following procedures:

• Establishing a Direct Connection to an NAE• Preparing an NAE for an Ethernet LAN That Supports DHCP and DNS• Preparing an NAE for an Ethernet LAN without DHCP and without DNS Support (NAE Uses APIPA)• Preparing an NAE for an Ethernet LAN without DHCP and without DNS Support (NAE Uses Static IP Address)• Preparing an NAE for an Ethernet LAN That Supports DHCP but Not DNS• Preparing an NAE for an Ethernet LAN That Supports DNS but Not DHCP

Modems and Dial-Out FeaturesYou can set up an NAE with a modem to dial out to an ADS/ADX from a remote location or to be accessible from acomputer remotely. Some NAE models include an optional, factory-installed, internal modem. You can also installa user-supplied external modem on the NAE. See Table 3 for a list of supported modem combinations for the NxEmodels. For example, an NAE55 with an internal modem can have an external USB modem, but not an externalserial modem.

Table 3: Supported Modem CombinationsExternal Serial ModemSupported?

External USB ModemSupported? 1

Internal Modem Present?NxE Model

NoYesYesNAE55/NIE55

NoYesNo

NoYesYesNAE35/NAE45/NCE25

Yes - RS232C Port B Only2YesNo

1 Only one external modem is supported per NAE: USB or Serial.2 The RS232C A serial port does not support an external modem.

Note: The optional factory-installed, internal modem cannot be added to an NAE in the field.

Each NAE is pre-loaded with the modem drivers for the following (optional and user-supplied) supported externalUniversal Serial Bus (USB) modems:

• Zoom® Telephonics 2985-00-00L modem, V.90 external USB modem• Multi-Tech Systems, MT5634ZBA - USB 56K, V.90 external USB modem• U.S. Robotics® USR5637 modem, 56K, external USB modem (requires 4.1.5 image or later

Note: The Multi-Tech Systems modem in Metasys system networks requires the 8.27L Version or higher of theMulti-Tech Systems modem firmware installed on the modem.

Note: The Zoom and Multi-Tech Systems models specified here are discontinued and no longer available fromJohnson Controls, but may be obtained from other vendors.

By default, the NAE is not set up to accept incoming dial-up connections via a modem. To enable modem connections,access the NAE Site Management Portal UI, go to the Communication tab, and set the Allow Incoming Connectionsattribute value in the Internal Modem Config or External Modem Config sections to True.


Modems used for Metasys systemDDAsmust be dedicated for the DDA. For example, a conflict exists if the Launcherapplication attempts to use the same modem that is configured for a Pager DDA. To help you understand supporteduses of internal and external modems, see Table 4. For example, an internal modem can be shared for ADS/ADXdial-out (alarm, event, and audit forwarding) and incoming connection (Launcher) functions, whereas the externalmodem is dedicated to the paging function. If you use the same modem for the ADS/ADX dial-out and Launcherfunctions, you may need to increase the number of redial attempts and time between redial attempts for that modem.

Table 4: Supported Modem Communication UsesPagingDial InDial OutExternalInternalInternalType of Modem

InternalExternalExternal

With the presence of two modems, the NAE is capable of communicating over an incoming modem connection andan outgoing modem connection simultaneously. The supported modem configuration scenarios are summarized inTable 5. As an example, the NAE’s internal modem can handle communications to an ADS/ADX and accept incomingconnections, while its external modem can send out pages. An example of an unsupported combination is for thesame modem (internal or external) to handle all three communication types: dial-out, dial-in, and paging. Table 6lists the unsupported modem scenarios.

Table 5: Supported Modem Configuration Scenarios for NAEPagingDial InDial OutModem enabled

Use external modem

Modem enabled

Use internal modem

Modem enabled

Use internal modem

Modem enabled

Use internal modem

Modem enabled

Use external modem

Modem enabled

Use external modem

Modem disabled

No modem in use

Modem enabled or disabled

Use internal or external modem

Modem enabled or disabled


Modem enabled


Modem disabled

No modem in use

Modem disabled

No modem in use

Table 6: Unsupported Modem Configuration Scenarios for NAEPagingDial InDial OutModem enabled

Internal modem

Modem enabled

Internal modem

Modem enabled

Internal modem

Modem enabled

External modem

Modem enabled

External modem

Modem enabled

External modem

Modem enabled

Internal modem

Modem enabled

Internal modem

Modem disabled

No modem in use

Modem enabled

External modem

Modem enabled

External modem

Modem disabled

No modem in use

Modem enabled

Internal modem

Modem disabled

No modem in use

Modem enabled

Internal modem

Modem enabled

External modem

Modem disabled

No modem in use

Modem enabled

External modem


Time Zone, Date, and Time ManagementThe procedure you use to set the time zone, date, and time on an NAE depends on how the NAE fits into the Metasyssite hierarchy. See Appendix: Time Zone, Date, and Time Management for information and detailed procedures forsetting time zone, date, and time on an NAE and on a Metasys network.

Alarm and EventsEach NAE stores alarm and event messages generated by the NAE and the connected field trunk devices. You canconfigure an NAE to send alarm and event notifications via the NAE DDAs to e-mail destinations, paging devices,and SNMP devices.

DDAs are agents that route and deliver alarm and event messages to destinations such as pagers, printers, e-mailaddresses, and SNMP management systems.

If the site has an ADS/ADX, each NAE can forward alarm and event information to the ADS/ADX for centralizednotification and long-term storage.

Important: If the site depends on alarm paging, printing, or e-mailing alarms, the Metasys system manages theNAE repositories according to the following criteria to avoid a loss of notification if the repository becomesfull:• Events forwarded to an ADS Event Repository are always removed before events that are not

forwarded.• The lowest priority event with the oldest time stamp and Acknowledge Required flag set to false is

replaced first.• If the event about to be created is of a higher priority than at least one event in the repository, the

event with the oldest time stamp and the lowest priority is replaced.• If all events are of the same priority, the event with the oldest time stamp is replaced.• If the event about to be created is of a lower priority than all other events in the Event Repository,

no event is replaced and the new event is discarded.

A loss of alarm paging, printing, or e-mailing can result if the NAE is not commissioned with strictadherence to these criteria. To avoid managing events in this way, move ADS/ADX and the notificationDDAs to the server.

You can designate multiple alarm and event sources in an NAE and in the connected field devices, and then configurethe conditions that trigger those alarms or events. You can also define multiple notification types and multiplenotification destinations for each alarm or event.

The NAE also has several pre-configured internal diagnostic features that are factory set to generate alarms. NAEdevice diagnostic features with factory-set default alarm values include:

• Central Processing Unit (CPU) usage• flash usage• memory usage• battery condition• CPU temperature (NAE55/NIE55 models only)• board temperature

You can check the status of these diagnostic features on the Diagnostic tab. See Diagnostic Tab.

Refer to the Introduction to Alarm and Event Management in the Metasys system Help for more information.

Note: After an alarm is generated, anyone who acknowledges the alarm clears that alarm notification for all otherusers. If an ADS/ADX is the Site Director, you can set the ADS/ADX to deliver alarm and event notificationsto a network printer.


Serial Printer DDA (Alarm Printer)Alarms from supervisory devices can be sent automatically to an alarm printer if one is configured and online. Alarmscan be sent to an NAE55/NIE55 and NxE85. The Serial DDA must be enabled on the Site Director NAE/NIE that isconnected to the serial printer and all NAEs/NIEs from which you want alarms printed. You can print alarms fromall NAEs/NIEs using the serial printer connected to the Site Director Figure 6. You can also print alarms to a localprinter connected to a single NAE/NIE.

Important: Alarms are sent directly to the printer and are not queued or stored by the supervisory device. Alarmssent to an alarm printer that is offline, turned off, or out of paper are not printed and cannot be recovered.Figure 6 and Figure 7 show the possible printer connections to a Site Director NAE/NIE.

Recommended Serial PrinterTable 7 describes the recommended serial printer and accessories.

Table 7: Recommended Serial Printer and AccessoriesITAS NumberDescriptionItemC11C524001Epson® FX890 9-pin, 680 cps printerSerial Printer

C12C824431Serial Card for Epson Dot Matrix printerSerial Card

F2J044-06Serial Null Modem Printer CableSerial Printer Cable

Table 8 shows the recommended settings for the serial card.

Table 8: Serial Card SetupDescriptionPositionSwitch

Switch 1 Setup

Enable CardOnSW1-1

8-bit wordOnSW1-2

parity - noneOffSW1-3

parity - noneOffSW1-4

9600 BaudOnSW1-5

9600 BaudOffSW1-6

Switch 2 Setup

9600 BaudOnSW2-1

9600 BaudOnSW2-2

Xon/XoffOffSW2-3

Xon/XoffOnSW2-4

RS232OffSW2-5

RS232OffSW2-6

Switch 3 Setup

Buffer sizeOffSW3-1

SW3-2 Buffer full recoveryOff

Buffer full recoveryOffSW3-3

DTR + or -OffSW3-4

DSR/DCDOffSW3-5

DTR flag setOffSW3-6

Self test enableOffSW3-7

Self test selectionOffSW3-8


Table 8: Serial Card SetupDescriptionPositionSwitch

Jumper Setup

OnJ1A

OffJ1B

OnJ2A

OffJ2B

OffJ3

OffJ4

Factory set - Do not change.J5



OffJ8

Figure 6 shows a Metasys system with the alarm printer connected to the Site Director NAE/NIE, and alarms forNAEs/NIEs (2 and 3) are routed to the Site Director NAE/NIE (1) for printing. All alarms from the NAEs/NIEs (1, 2,and 3) print on the serial printer. The serial printer DDA must be enabled on all NAEs/NIEs (1, 2, and 3).

Figure 6: Metasys System with One Alarm Printer

Figure 7 shows aMetasys systemwith a local alarm printer (A) connected to an NAE/NIE (3) for printing. Only alarmsfrom this NAE (3) print on this printer. The alarms from all NAEs/NIEs (1, 2, and 3) are routed to the Site DirectorNAE/NIE (1), and all alarms are printed to serial printer B. The serial printer DDA must be enabled on all NAEs (1,2, and 3).


Figure 7: Metasys System with Local Alarm Printer

Figure 8 shows a Metasys system with one local Alarm Printer. The alarms from only one NAE/NIE (3) print on aserial printer (A). Only that NAE/NIE (3) has the serial printer DDA enabled. The Site Director NAE/NIE (1) andNAE/NIE (2) do not have the serial printer DDA enabled.

Figure 8: Metasys System with One Local Alarm Printer

Serial Printer Installation ConsiderationsFollow these guidelines when installing a serial printer:

• You cannot install the serial printer option on an ADS/ADX computer.• You can install the serial printer option on an NIE that has an application that is already using the COM ports if

the NIE is not designated as the Site Director. For example, you can install the serial printer option on an XL5000NIE.


• You must connect the physical connection of the serial printer to COM Port B.• You can install the serial printer option on an NIE85. The NIE85 uses COM1 for the physical connection of the

serial printer.• If your site contains multiple supervisory devices from which alarms are forwarded, you must connect the physical

connection of the serial printer to COM Port B of the Site Director and perform the installation sequence on allsupervisory devices from which alarms are forwarded.

• You must install the serial printer option when an NAE/NIE is reloaded or upgraded with the NAE/NIE UpdateTool.

• You cannot filter alarms. All alarms forwarded from the device on which you install the serial printer DDA areprinted.

• You cannot enable the Serial Printer DDA on an NAE35, NAE45, or NCE25.• The NAE55/NIE55 battery must be in good condition prior to enabling the DDA (the procedure requires you to

remove power from the engine).• Before enabling the Serial Printer DDA, you must have a computer with the NxE Information and Configuration

Tool (NCT) installed that has network access to each NAE/NIE on which the DDA is to be installed. If you haveaccess to an NxE85 with a monitor and keyboard, you do not need to use NCT and may perform the proceduresin this document directly on the NxE85 computer.

Important: Use care and follow instructions carefully when using NCT to access an engine or computer. Failureto follow the steps as written can render your engine or computer inoperable.

E-mail NotificationYou can configure an NAE to generate alarm and event messages via e-mail to one or more e-mail destinationsusing the e-mail DDA.

Configure custom e-mail messages, and specify e-mail message destinations in the Email tab of the Site ManagementPortal UI. Figure 9 provides an example of an e-mail message destination that is active Monday through Friday from7:00 A.M. to 4:00 P.M.


Figure 9: Example of Defining an E-mail Notification

Pager NotificationYou can configure an NAE to generate alarm and event messages using TAP to one or more pager destinationsusing the pager DDA.

TAP is an American Standard Code for Information Interchange (ASCII) based protocol that allows the submissionof a numeric or alphanumeric message.

Configure custom pager messages and specify the pager message destinations in the Pager tab of the SiteManagement Portal UI. Figure 10 provides an example of how to define a set of pager destinations that can routea Fire alarm to the same pager over the weekend (4:00 P.M. Friday to 7:00 A.M. Monday). Note that this applicationrequires the definition of three separate Pager destinations.


Figure 10: Examples of Defining a Pager Notification

Simple Network Management Protocol (SNMP) NotificationSNMP is a protocol governing network management and the monitoring of network devices and their functions. Itis not necessarily limited to Transmission Control Protocol/Internet Protocol (TCP/IP) networks. SNMP monitoringis typically used for large BAS networks with many network devices. Alarm and event notifications are sent to andstored on an SNMP management computer that monitors all devices on the network.

The NAE uses SNMP protocol to deliver network device status and conditions to a designated SNMP managementcomputer. You must set up SNMP monitoring at the network level, and you must assign an SNMP managementdevice on the network. (For details, see Creating NAE SNMP Alarm Notifications and Destinations.) If you areapplying a Metasys system to an existing network, consult with the network administrator or IT department thatadministers the network to determine if SNMP monitoring is available on the network.

Configure custom SNMP messages and specify the SNMP message destinations in the SNMP tab of the SiteManagement Portal UI. Perform this configuration to each NAE individually; SNMP configuration cannot be doneon an ADS/ADX.

Release 3.0 and later provides enhanced SNMP functionality on Metasys systems, including a Metasys systemManagement Information Base (MIB) file for configuring third-party SNMP translation applications to request, receive,and translate specified SNMP trap messages generated by the Metasys SNMP DDA.

Initial Default NAE ConfigurationNAEs are shipped with standard initial values for many of the editable attribute values. Table 9 defines some importantinitial default configuration values for the NAE35, NAE45, and NCE25 models. Table 10 and Table 11 define someimportant initial default configuration values for the NAE55/NIE55 and NxE85 models.


Table 9: NAE35, NAE45, and NCE25 Initial Configuration ValuesNAE35, NAE45, and NCE25 Initial ValueAttribute/Field NameNAExxxxxxxxxxxx, where xxxxxxxxxxxx is the Ethernet Media Access Control(MAC) address of the device without the hyphens. For example, if the EthernetMAC address is 00-80-66-05-0F-FC, the initial Computer Name isNAE008066050FFC.

Computer Name

EnabledDHCP Client

115,200 baud, 8 bits, no parity, 1 stop bit (115200,8,n,1), Direct Connect IP overPoint-to-Point (PTP).

Serial Port RS232C A

115,200 baud, 8 bits, no parity, 1 stop bit (115200,8,n,1)Serial Port RS232C B

A new NAE35/NAE451 is a Site Director by default. If an NAE is not going to bethe Site Director, it must be demoted and the Computer Name or IP address ofthe designated Site Director must be entered here.

Site Director

MetasysSysAgent (not case sensitive)Initial Site Management Portal UI LogonUsername

Contact your local Johnson Controls representative.Initial Site Management Portal UI LogonPassword

1 This information does not apply to the NAE45-Lite.

Table 10: NAE55/NIE55 Initial Configuration ValuesNAE55/NIE55 Initial ValueAttribute/Field NameNAExxxxxxxxxxxx, where xxxxxxxxxxxx is the Ethernet Media Access Control(MAC) address of the device without the hyphens. For example, if the EthernetMAC address is 00-80-66-05-0F-FC, the initial Computer Name isNAE008066050FFC.

Computer Name

EnabledDHCP Client

115,200 baud, 8 bits, no parity, 1 stop bit (115200,8,n,1), Direct Connect IPover Point-to-Point (PTP).

Serial Port A

9600 baud, 8 bits, no parity, 1 stop bit (9600,8,n,1)Serial Port B

A new NAE55/NIE55 is a Site Director by default. If an NAE is not a Site Director,it must be demoted and the Computer Name or IP address of the designatedSite Director is entered here.

Site Director

MetasysSysAgent (not case-sensitive)Initial Site Management Portal UI LogonUsername


MetasysSysAgent (not case-sensitive)Initial Windows Logon ID1

Contact your local Johnson Controls representative.Initial Windows Password

1 The Windows operating system logon ID and password are used with dial-up and direct connections.

Table 11: NxE85 Initial Configuration ValuesNxE85 Initial ValueAttribute/Field NameNAExxxxxxxxxxxx, where xxxxxxxxxxxx is the Ethernet Media Access Control(MAC) address of the enabled Ethernet card without the hyphens. For example,if the Ethernet MAC address is 00-1E-EC-6E-5D-32, the initial Computer Nameis NAE001EEC6E5D32.

Computer Name

EnabledDHCP Client


Table 11: NxE85 Initial Configuration ValuesNxE85 Initial ValueAttribute/Field NameA new NxE85 is shipped as a Site Director. If an NxE85 is not going to be theSite Director, you must demote it by entering the ComputerName or IP addressof the designated Site Director in the SiteDirector attribute field on the AdvancedFocus tab of the NxE85.

Site Director

MetasysSysAgent (not case-sensitive)Initial Site Management Portal UI LogonUsername


MetasysSysAgent (not case-sensitive)Initial Windows Logon ID1

Contact your local Johnson Controls representative.Initial Windows Password

1 The Windows OS has two administrator level user accounts. For security reasons, we strongly recommend changing theWindows OS logon password for both accounts at commissioning. You can disable the administrator account, but do not disablethe MetasysSysAgent account.

System and User PreferencesThe Metasys system provides customized preferences for the Site Management Portal UI. The preferences allowyou to configure how the UI behaves, including the sounds and colors, the startup view, and the ability to add linksto external applications that can be accessed from within the UI of the NAE device. See Appendix: Configuring andMaintaining Preferences for information and detailed procedures on how to customize system and user preferences.

Reset Device CommandThe NAE Reset Device command in the Site Management Portal UI initiates an orderly reset that saves recentchanges to the NAE archive database and restarts the NAE operating system. When the NAE requires a reset,Reset Needed appears in the title bar of the object in the Display panel. A reset is required for new settings to takeeffect after making changes to the following attributes:

• APDU Retries• APDU Segment Time-out• APDU Time-out• BACnet IP Port• Computer Name• Contact Person• Domain Name• External Modem Config• Internal Modem Config• Max APDU Length• Network Address• Port Number• Read Community• SNMP DDA• SNMP Management Device• Serial Port 1 Cable Config• Time Sync Period (NAE55/NIE55 models only)• Write Community• XMS Dial-up Config (NAE55/NIE55 models only)

Note: Changing the NAE Computer Name value forces a device reset.


Important: Do not push the RE-BOOT SYSTEM switch on the NAE to initiate a device reset. Pushing the RE-BOOTSYSTEM switch initiates a CPU reset and restart of the NAE, which causes all unsaved data to be lost,including recent attribute value changes.

Detailed ProceduresYou need the following items to perform the detailed procedures and commission an NAE:

• an NAE with Release 6.0 software• a laptop or desktop computer with Internet ExplorerWeb browser Version 8.0 or 9.0 for the purpose of downloading

the Launcher application

Note: In some scenarios, the computer must be a DHCP client or must be configured to use a static IP addressappropriate for the LAN.

• the NAE Ethernet MAC address

You may also need:

• a null modem Serial cable• an Ethernet crossover cable• a new, unique IP address for the NAE on the Metasys network• a copy of the NAE archive database that configures the NAE for your specific site (The NAE archive database

can be created and stored offline in the SCT.)• Release 6.0 SCT loaded on a computer

Using Launcher to Discover an NAEStarting at Release 6.0, you use the Launcher application instead of a web browser to discover an NAE. If theLauncher application is already installed on your computer, skip to Step 5. If the Launcher application is not installed,follow these steps:

1. Start the Internet Explorer web browser.2. Enter this URL in the Internet Explorer address field: http://NAE-computer-name/metasys. See the NAE

Computer Name section. The Windows Launcher Download screen appears (Figure 11).

Figure 11: Windows Launcher Download

3. Click Download. A user message displays asking you to run or save the file.4. Click Run. Follow the instructions on the screen to install the Launcher. Refer to the Launcher Installation

Instructions (LIT-12011783) if needed. When the Launcher is installed on your computer, proceed to Step 5.5. Start the Launcher application. The Launcher screens appears (Figure 12).


Figure 12: Launcher Screen

6. Click Add. The Add New window appears (Figure 13).

Figure 13: Add New Device


7. Enter the IP address of the NAE, and then click Discover. The Launcher searches for the device on the buildingnetwork. When the device is found, the Add New window refreshes to indicate the found device (Figure 14).

Figure 14: Found Device

8. You may enter a descriptive name for the NAE in the SMP field or keep the default IP address. Click Save. TheNAE is added to the profile list on the SMP tab of the Launcher.

Note: Descriptive names make it easier to find NAEs in the profile list.9. Select the NAE from the SMP profile list and click Launch. If the device you are adding has not yet been

downloaded and installed on your computer, a Downloading screen appears, followed by an Installing screen(Figure 15). The screens clear when the download and installation steps are complete.

Figure 15: Downloading and Installing Metasys Version

The Metasys system logon screen appears.10. Enter the initial Username and Password values for the NAE and click Login. See Logon User Names and

Passwords.11. If necessary, set the time, time zone, and date. See Appendix: Time Zone, Date, and Time Management.


Establishing a Direct Connection to an NAEThis scenario is typical for a single NAE that is not attached to a LAN and can be used to set up an NAE before itis installed and connected to a site network. The following procedure can also be used when an Ethernet crossovercable is not available.

Your computer must be set up for dial-up access as described in Metasys® System Extended Architecture DirectConnection and Dial-Up Connection Application Note (LIT-1201639).

1. Connect the computer Communication (COM) port to the NAE Serial Port A using a null modem cable.2. Establish the connection to the NAE by double-clicking the icon for Direct Connect that was created when the

computer was set up for dial-up access. If you are using Windows XP® Professional OS, the Direct Connecticon is located on the Network Connections screen (Start > Settings > Network Connections). If you are usingWindows 7 OS or Windows Server® 2008 OS, the Direct Connect selection is located under the Network andSharing Center (select Control Panel > Network and Internet > Network and Sharing Center > Connect to aNetwork).

The direct-connect setup is complete. You can access the Metasys system logon screen using the Launcher.See Accessing the Site Management Portal UI on an NAE for information on accessing the NAE UI.

Preparing an NAE for an Ethernet LAN That Supports DHCP and DNSThe following scenario is typical when installing an NAE on an existing building LAN. Your computer must beconnected to the LAN. The computer must be a Dynamic Host Configuration Protocol (DHCP) client or configuredto use a static IP address appropriate for the LAN.

Note: We recommend that DHCP be configured to assign the same IP address to an NAE when the IP addresslease expires and after the NAE device resets. When a different IP address is issued to an NAE, addressbinding to the NAE from other devices breaks.

1. Your LAN Administrator must update the DNS server and the DHCP server with the NAE Ethernet MAC addressand the NAE host name.

2. Connect the NAE to the LAN with an Ethernet patch cable.3. Connect 24 VAC supply power to the NAE. Then wait for the NAE to complete the startup and initialization

sequence.

Note: Startup and initialization is complete when the NAE green RUN LED is steady on and the PEER COM iseither off or flickering to show activity. The startup and initialization sequence may take up to 10 minutesto complete.

If the DHCP server is not online when the NAE is powered on (or if the NAE Ethernet cable is disconnectedand reconnected with no DHCP server online), the NAE assumes a unique IP address between 169.254.0.1and 169.254.255.254 and a subnet mask of 255.255.0.0. This is a feature of Automatic Private InternetProtocol Addressing (APIPA) that applies when DHCP is enabled in the NAE (factory default).

4. Go to Using Launcher to Discover an NAE, follow all instructions, then return to the next step in this section.5. After you have completed the steps in Using Launcher to Discover an NAE, including the step for logging on to

the NAE, select the NAE device object in the Navigation panel, and drag it to the Display panel of the SiteManagement Portal UI. The Focus tab for the selected NAE appears in the Display panel (Figure 16).


Figure 16: NAE Focus Tab - Basic

6. Go to the Network tab and check the Computer Name and Domain Name values. Change these values to theassigned values for your network site (Figure 17).


Figure 17: NAE Network Tab - Edit Mode

Important: Starting at Release 2.1.10, the NAE/NIE Update Tool places restrictions on the Host Name (ComputerName) values you can use for NAE35, NAE45, or NCE25 models. Name values must start with aletter, end with either a letter or a number, and may contain dashes only in the interior of the name.Failure to follow the name restrictions results in the Computer Name value’s changing when anNAE35, NAE45, or NCE25 is updated. Refer to the NAE/NIE Update Tool Technical Bulletin(LIT-12011524) for more information on Host Name restrictions.

Note: Changing the Computer Name value forces a device reset on the NAE. (See NAE Computer Name andReset Device Command.)

7. Go to the Focus tab and check the NAE Object Name value (Figure 18). Change the Object Name value to thedescriptive label used to identify the NAE in the Site Management Portal UI and SCT.


Figure 18: NAE Focus Tab - Advanced Edit Mode

Depending on the DNS server configuration, the NAE should be reachable from the subnet on which the NAE residesor from other subnets.

Preparing anNAE for an Ethernet LANwithout DHCP andwithout DNSSupport(NAE Uses APIPA)This scenario is typical when installing an NAE on a stand-alone LAN designated as a building control network only.Perform these steps from a computer attached to the LAN. The NAE uses APIPA to automatically assign an IPaddress. For this procedure, do not attach an Ethernet crossover cable directly to the NAE. In this scenario, a directconnection to the NAE may affect the assignment of an IP address.

1. Attach the NAE to the LAN using an Ethernet patch cable.2. Connect supply power to the NAE and wait for the NAE to complete initialization.



3. Verify that the computer is configured to use APIPA or a static IP address and subnet mask compatible withAPIPA. If necessary, change the computer’s IP address and subnet mask to be compatible with APIPA.


the NAE, demote the NAE from Site Director if the NAE is not going to be the Site Director. See Designating anNAE as the Site Director.

6. (This step is optional.) Select the Network tab of the NAE device object. Change the Computer Name value fromthe factory default, if desired (Figure 17). See NAE Computer Name and Reset Device Command.

Initial setup is complete. You can now log on to the NAE by entering computer-name in Launcher, wherecomputer-name is the initial computer name of the NAE or the computer name you assigned in Step 6.

Preparing anNAE for an Ethernet LANwithout DHCP andwithout DNSSupport(NAE Uses Static IP Address)This scenario is typical when installing the NAE on a stand-alone LAN dedicated to building control only. Using thisscenario when using APIPA is not appropriate. The steps can be performed from a computer attached to the LANor a computer connected directly to the NAE with an Ethernet crossover cable. If attached to the LAN, the computermust be connected to the same subnet as the NAE. To connect to the NAE with this procedure, you may need toknow the IP address of the NAE. See Determining the NAE IP Address and Device Name for a LAN Connection.

1. Check the LAN IP address and subnet mask of the computer. If needed, change the IP address and subnetmask of the computer so that the computer and NAE are on the same subnet. The IP address assigned to thecomputer must be unique for the subnet.

2. Connect supply power to the NAE and wait for the NAE to complete startup and initialization. Startup andinitialization is complete when the NAE green RUN LED is steady on and the PEER COM is either off or flickeringto show activity. The startup and initialization sequence may take up to 10 minutes to complete.


the NAE, demote the NAE from Site Director if the NAE is not going to be the Site Director. See Designating anNAE as the Site Director.

5. Select the NAE device object from the Navigation panel of the Site Management Portal UI and drag it to theDisplay panel. The NAE device object UI opens in the Display panel.

6. Select the Network tab of the NAE device object and click Edit (Figure 19).7. Change the Computer Name value, if desired. Change DHCP Enabled attribute value to False. This disables

DHCP and APIPA. Change the IP address and subnet mask. The network administrator typically assigns staticIP addresses. Record the assigned IP address for the NAE for future reference. The NAE automatically logs offand resets when you save the Computer Name change.


Figure 19: Network Tab - Edit Mode

8. Wait for the NAE to complete the startup and initialization sequence.


Initial setup is complete.

Note: If you connected your computer directly to the NAE with an Ethernet crossover cable, disconnect thecrossover cable and connect the NAE to the LAN with an Ethernet patch cable.

You can log on to the NAE by entering its IP address in Launcher on any subnet of the LAN.

Preparing an NAE for an Ethernet LAN That Supports DHCP but Not DNSThis scenario is common to many building LANs. The NAE should only use DHCPwithout DNS if you have configuredDHCP to always assign the same IP address after device resets and lease renewals. If this is not the case, usestatic IP addresses as described in Preparing an NAE for an Ethernet LAN without DHCP and without DNS Support(NAE Uses Static IP Address).

1. Attach the NAE to the LAN using an Ethernet patch cable.2. Connect supply power to the NAE and wait for the NAE to complete initialization.

Startup and initialization is complete when the NAE green RUN LED is steady on and the PEER COM is eitheroff or flickering to show activity. The startup and initialization sequence may take up to 10 minutes to complete.



the NAE, update the NAE computer name value on the Network tab. After the computer name is updated, theSite Management Portal UI automatically logs off, and the NAE automatically resets. Wait for the NAE to completethe startup and initialization sequence. (Startup and initialization is complete when the NAE green RUN LED issteady on. This sequence may take up to 10 minutes. See Pre-boot Execution Environment (PXE) for moreinformation.)

Preparing an NAE for an Ethernet LAN That Supports DNS but Not DHCPThis scenario is not typical of today’s networks. The steps are identical to the steps in the Preparing an NAE for anEthernet LAN without DHCP and without DNS Support (NAE Uses APIPA) and Preparing an NAE for an EthernetLAN without DHCP and without DNS Support (NAE Uses Static IP Address).

Using the NAE Ethernet MAC address (from the NAE label), the network administrator can update the DNS serverand the assigned computer name. If this is done, you can enter dns-name in Launcher on any computer on theLAN.

Enabling the Serial Printer DDAImportant: Follow instructions carefully when using Remote Desktop with the NxE Information and Configuration

Tool (NCT) to access an engine or computer. Failure to follow the steps as written can render yourengine or computer inoperable.

1. To prevent data loss, issue an Archive command to the device from the Site Management Portal UI.2. If you are enabling the DDA on an NxE85, complete the steps in Preparing the NxE85 for Serial Printing.3. Access the NAE remotely using the NCT.4. Click Remote Desktop in the NCT. If a Remote Desktop identity message appears, click Yes. The tool logs in

to the NAE, and the Remote Desktop screen with the Command Prompt appears (Figure 20).

Note: If the Command prompt does not appear, press Ctrl+Alt+End to open the Windows Security screen.Click Task Manager. The Windows Task Manager appears. Click the Applications tab, then New Task.The Create New Task window appears. In the Open field, typeCMD and press Enter. When the Commandprompt opens, close the Task Manager.


Figure 20: Command Prompt

5. At the command prompt, type net pause miiidm to pause the Device Manager.6. At the command prompt, type notepad and press Enter. Microsoft Notepad opens in a new window (Figure

21).


Figure 21: Notepad in Remote Desktop

7. In Notepad, on the File menu, select Open.8. From the Files of Type drop-down menu, select All Files.9. Browse to JCI_NAE (C:)\Inetpub\wwwroot\MetasysIII\WS and select Web.config.10. Click Open. The Web.config file opens in Notepad.11. In the <EventRouter> section, locate the serial printer DDA line:

12. Delete  at the end of the serial printer DDA line (see circled text):

13. On the Notepad File menu, click Save.

Note: If the file is not saved with the original name, including the .txt extension, the DDA is not enabled.14. If you are enabling printing on an NAE55/NIE55:

a. At the command prompt enter, shutdown -r -t 0, or remove power from the NAE55/NIE55.b. When the NAE55/NIE55 LEDs are off, reapply power to the NAE55/NIE55.

15. If you are enabling serial printing on an NxE85, restart the computer.

The Serial Printer DDA installation is now complete. The Remote Desktop connection closes and the NAE/NIErestarts.

Preparing the NxE85 for Serial Printing1. Disable COM port B in the Windows Device Manager.2. Configure COM Port A for 9600-8-N-1-N.3. Connect the serial printer to COM port A.

Note: The printer has only one physical port.4. Install the Epson FX-880 printer driver.

Note: The FX-890 printer driver is not available.5. Return to Enabling the Serial Printer DDA. If you have access to an NxE85 with a monitor and keyboard, start

with Step 7; otherwise, start with Step 3.

Creating Audit Entries for Discarded EventsBy default, discarded events that originate at the NAE are not recorded. You can change this behavior so that anaudit entry is recorded and shown in the Audit Viewer each time an event is discarded.

1. Access the NAE remotely using the NCT.2. For an NxE55 or NxE85, click Remote Desktop in the NCT, then start Notepad from the Command Prompt. For

an NAE35/45 or NCE25, click Start FTP in the NCT.3. Open the following file for editing:

NxE55 or NxE85: C:\Inetpub\wwwroot\MetasysIII\WS\web.config

NAE35/45 or NCE25: ftp://<IP address>/Storage/Metasys/wwwroot/metasysIII/WS/Web.ce.config4. Find the line for WriteAuditAckDiscard:

<add key="EventRepository.WriteAuditAckDiscard" value="false"/>

5. Change the value from false to true.6. Save the file.7. Terminate your remote connection to the NAE.8. Exit the NCT.

Accessing the Site Management Portal UI on an NAEAfter an NAE is set up for connectivity, the Site Management Portal UI can be accessed via the Launcher.

See the Site Management Portal User Interface section of this document and theMetasys systemHelp for additionalinformation about navigating the Site Management Portal UI.

You need to know the IP address (or Computer Name) for the NAE you wish to access. If you do not know the IPaddress for the NAE, seeDetermining the NAE IP Address and Device Name for a LANConnection andDeterminingthe NAE IP Address and Device Name through a Serial Port Monitor.

If the NAE has been added to a building’s DNS server, you can access it by its Computer Name value.

To access the Site Management Portal UI on an NAE via the Launcher:

1. Start the Launcher application.2. Select the IP address of the NAE on the SMP tab of the Launcher, and click Launch. The Metasys system logon

screen appears.3. In the Metasys system logon screen, type the NAEUsername and Password, and then click Login or press Enter.4. To view an NAE, select the NAE object from the Navigation panel and drag it to the Display panel. The NAE

object opens with the Focus tab active (Figure 22).


Establishing Basic NAE Parameters in the Focus Screen1. In the Site Management Portal UI, display the NAE device object and click the Focus tab.2. Click Edit (Figure 22). Edit the NAE Object Name and Description values as required.

Figure 22: NAE Focus Tab (Basic)

3. Click Save.4. Select the Advanced option and click Edit (Figure 23).


Figure 23: NAE Focus Tab - Advanced Edit Mode

5. Edit the advanced attribute values as needed. (Refer to the NAE Device Object Help and Audit Trails Help intheMetasys systemHelp for guidance.) If the NAE is on a site with an ADS/ADX, enter the ADS/ADX’s IP addressin Local Site Director field in the Site section of this screen so the NAE can find the ADS/ADX.

Establishing the NAE Network ParametersThe NAE Computer Name and Domain Name on the Network tab identify the NAE on the network so it can be foundby other computers. In many commissioning scenarios, you can use the initial Computer Name value to commissionthe NAE. See NAE Computer Name for more information.

In most site configuration scenarios, you configure many of the Metasys network values in the NAEUI by downloadinga pre-built archive database from the SCT to the commissioned NAE. The download from SCT overwrites the initialComputer Name value with the new value for the Metasys network.

Note: If you are building the NAE database online, youmust establish the production network NAEComputer Namevalue before establishing references to objects on the NAE. After creating object references, changing theComputer Name value breaks all object references to local objects on the site.


Important: Starting at Release 2.1.10, the NAE/NIE Update Tool places restrictions on the Host Name (ComputerName) values you can use for NAE35, NAE45, or NCE25 models. Name values must start with a letter,end with either a letter or a number, and may contain dashes only in the interior of the name. Failureto follow the name restrictions results in the Computer Name value’s changing when an NAE35, NAE45,or NCE25 is updated. Refer to the NAE/NIE Update Tool Technical Bulletin (LIT-12011524) for moreinformation on Host Name restrictions.

To set up the NAE network identification, LAN configuration, and the dial-up attributes:

1. In the Site Management Portal UI, display the NAE device object, click the Network tab, and then click Edit(Figure 24).

Figure 24: NAE Network Tab - Edit Mode

2. In the Network Identification section, type the Computer Name value.3. Fill in the Network Identification and LAN attribute values as needed and click Save.

Note: If you are setting up an NAE to dial out to an ADS/ADX, see Configuring an NAE to Dial Out to an ADS/ADX.

Establishing the NAE Direct-Connect and Modem ParametersOn the NAE Communications tab, you can set the NAE to communicate via a direct connection to Serial Port A(NAE55/NIE55 models), an optional internal modem, or a user-supplied external modem (Figure 25).


Note: On NAE35/NAE45 models, Serial Port A is labeled RS232C A.

Use Serial Port A for direct connections. Set up Serial Port A in the Serial Port Cable Config section of theCommunications tab.

Configure an optional internal modem on the NAE for dial-up connection in the Internal Modem Config section ofthe Communications tab.

Note: You can order specified NAE models with the optional internal modem. An internal modem cannot be addedto an NAE in the field.

Configure a user-supplied external modem on a USB port in the External Modem Config section of theCommunications tab.

SeeModems and Dial-Out Features for the external modems and drivers supported on Metasys® system networks.

Note: To enable modem connections, set the value for the Allow Incoming Connections attribute (in the InternalModem Config or External Modem Config sections) on the Communications tab to True.

NCE25/NAE55/NIE55 serial ports do not support external serial modems. Use only external USB modemswith the NCE25/NAE55/NIE55 models.

Each NAE supports the concurrent use of one internal modem and one external modem. For example, youcan configure the internal modem for dial-out communication and configure the external modem for dial-upcommunication (or vice versa). But you should not configure the internal modem and the external modemfor the same purpose; for example, both modems should not be configured for paging use.

To configure the NAE Serial Port A, an internal modem, or an external modem:

1. In the Site Management Portal UI, display the NAE device object, click the Communications tab, and then clickEdit (Figure 25).


Figure 25: NAE Communications Configuration Tab - Edit Mode

2. To establish a serial port connection to the RS232C A Serial port on NAE35/NAE45 models or Serial Port A onNAE55/NIE55 models, edit the attribute values in the Serial Port Cable Config section (Figure 25).

Note: Direct connections cannot be made to Serial Port B on NAE55/NIE55 models or to the RS232C B Serialport on NAE35/NAE45 models.

To establish an internal modem connection, edit the attribute values in the Internal ModemConfig section (Figure25).

Note: You can connect a user-supplied, external serial modem (such as Zoom models 2949 or 3049) to theRS232C B Serial port only on NAE35/NAE45 models that do not have an internal modem. To establisha connection to the external serial modem, you must edit the Internal Modem Config section on theCommunications tab.

To establish an external modem connection via a USB port, edit the attribute values in the External ModemConfig section (Figure 25). (See theModems and Dial-Out Features section in this document for more informationon external modems.)

Note: On NAE55 and NIE55 models, the Enabled attribute value is False (in the External Modem Configsection) and an external modem cannot be configured in the NAEUI until the external modem is connectedto the NAE and the Communication tab is refreshed in the UI. The refresh may take up to 30 seconds,after which the Enabled attribute value is True and the external modem can be configured in the UI.


3. Click Save.

Creating E-mail Alarm and Event Notifications and DestinationsAn NAE can be set up to generate custom alarm and event e-mail messages and send the messages to one ormore specified e-mail destinations.

Note: In most scenarios, we recommend that you set up the Email DDA and configure the e-mail notifications andthe notification-destinations after the NAE is configured with an archive database that includes the userdatabase.

To create e-mail messages and specify e-mail destinations for the messages:

1. In the Site Management Portal UI, display the NAE device object, click the Email tab, and then click Edit. (Seethe top half of the Display panel in Figure 26.)

2. Enter the Shared Configuration values according to Table 12. These fields establish values for attributes thatare common to all e-mail alarm notifications generated from this NAE. Refer to Alarm and Event Managementin the Metasys system Help for additional information on setting the attribute values for alarm and eventnotifications.

3. Scroll down to the Destinations section of the Email tab.4. Click New. The Email Destinations Configuration edit section appears (Figure 26).

Figure 26: The NAE Email Configuration - Edit Mode


5. Enter the Destination values according to Table 12. (Refer to the Alarm and Events Management section in theMetasys system Help for additional information on setting the attribute values for alarm and event notifications.)

Table 12: Shared Attributes for All E-mail DestinationsInitial ValueDescription (Value Requirement/Range)AttributeFully qualified hostname

Specifies the Simple Mail Transfer Protocol (SMTP) server name thathandles outgoing e-mail. (Required Value)

SMTP Server Host

25Specifies the TCP port that the server uses to deliver e-mail message.(Required Value/1 to 25)

SMTP Port

NoneSpecifies the Authentication Type the NAE uses to log on to the outgoinge-mail server. Select SMTP, Post Office Protocol (POP) before SMTP,or None.

Authentication Type

–Specifies the user name the NAE uses to log on to the SMTP serverthat handles outgoing e-mail messages. (Required only if SMTP isselected for Authentication Type.)

SMTP User Name

–Specifies the password the NAE uses to log on to the SMTP server thathandles outgoing e-mail messages. (Required only if SMTP is selectedfor Authentication Type.)

SMTP Password

–Specifies the POP server name for incoming e-mail messages. (Requiredonly if the e-mail server requires POP before SMTP, before it acceptse-mail messages from client. If this field is left blank, POP before SMTPis disabled.)

POP Server Hostname

Maximum 20characters

Specifies the POP user name. (Required only if POP Authentication isrequired and there is a value specified for POP server host.)

POP User name

Maximum 20characters

Specifies the POP Password. (Required only if POP Authentication isrequired and there is a value specified for POP server host.)

POP Password

E-mail addressSpecifies a valid e-mail address that is recognized and exists on theSMTP Server. (Required Value)

From Email Address

–Displays diagnostic information regarding the communication betweenthe Email DDA (SMTP Client) and the SMTP Server. This attributedisplays both successful and unsuccessful e-mail message deliveries.

Email Diagnostics

Table 13: Attributes for Specific E-mail Destinations and NotificationsInitial ValueDescription (Value Requirement/Range)Attribute–Specifies a name for the e-mail destination (for example, John Doe).Label

–Specifies the destination e-mail addresses (for example, [email protected]).(Required Value)

Email Address

NormalSpecifies the e-mail message priority (High, low, or normal).Priority

–Contains the body text of the e-mail message. (Maximum of 256 characters.)Subject

3Specifies the number of attempts at sending the e-mail message. (0–10Retries)

Retries

TrueEnables or disables E-mail Destination. (True, False)Enabled


Table 13: Attributes for Specific E-mail Destinations and NotificationsInitial ValueDescription (Value Requirement/Range)Attribute–Enables you to specify the rules that filter alarm and event notifications.

Each filter has an Item, Operator, and Value.Filters

–Enables some predefined format characteristics of the notifications thatare sent to a destination. Predefined format characteristics include:• Notification Priority• Notification Message (content)• Value• Site Name• Item Description• Item Fully Qualified Reference• Item Category• Acknowledge Required• Previous Status(Enable a format by selecting the check box next to the format.)

Format

6. Click New to the right of Destination Email Addresses. The Email Import dialog box appears. Import user namesand the associated e-mail addresses from the list of user names for the site. (Refer to the Metasys system Helpfor more information.)

Figure 27: Import Email Addresses Dialog Box

7. To filter the e-mail messages that are sent to a destination, click New next to the Filters section of the EmailDestination Configuration tab. The Add Filter dialog box appears (Figure 28).


Figure 28: Add Filter Dialog Box

8. Select the Item, Operator, and Value (from the drop-down lists) for the condition that you want to trigger thee-mail notification. (Refer to Event Message Routing, Filtering, and Destinations in the Metasys system Helpfor additional information on adding filters.)

9. Click OK.10. Enable the Format characteristics for e-mail notifications sent to the specified destinations by selecting the

check boxes next to the Format characteristic.11. Add additional e-mail destinations with filters and formats as required.12. Click Save.

Creating Pager Alarm and Event Notifications and DestinationsYou can set up an NAE to generate custom alarm and event pager messages and send the messages to one ormore specified pager destinations.

Note: In most scenarios, we recommend that you set up the Pager DDA and configure the pager notifications anddestinations after an NAE is configured with an archive database that includes the user database.

1. In the Site Management Portal UI, display the NAE device object and click the Pager tab.2. Click Edit. The Shared Configuration section of Pager Edit tab appears. (See the top half of the Display panel

in Figure 29.)


Figure 29: NAE Pager Configuration Edit Mode

3. Enter the Shared Configuration values using Table 14 and Table 15 as references. (These fields establishvalues for attributes that are common to all pager alarm notifications generated from this NAE. Refer to Alarmand Event Management in the Metasys system Help for additional information on setting the attribute valuesfor alarm and event notifications.)

Table 14: Shared Attributes for All Pager DestinationsDescription (Value Requirement/Range)AttributeSpecifies the connection type: Internal Modem, External Modem.Connect Using

Specifies the service or modem phone number that the NAE uses to access phoneservice. (This is not a pager destination phone number.)

Access Number

Specifies the number of attempts the NAE makes to connect with the destinationpager before stopping.

Redial Attempts

Specifies the time-delay interval between subsequent attempts to connect with adestination pager.

Time Between Redial Attempts

Specifies the amount of idle time allowed on the connection before disconnecting.Idle Time Before Hanging Up

Specifies whether to redial if connection with destination pager is broken.Redial If Line Is Dropped

Specifies a 6-digit alphanumeric code used as a password. This attribute appearswhen you select External Modem. Enter a password only if required by the pagercompany. An empty/blank password is the default value.

Password

Displays the diagnostic information regarding communication between the PagerDDA, modem, and customer's paging Service. It displays both successful andunsuccessful attempts to send a page.

Pager Diagnostics


Table 15: Attributes for Specific Pager Destinations and NotificationsDescription (Value Requirement/Range)AttributeSpecifies a functional name for the destination pager (for example, John Doe). (Maximum20 characters)

Label

Specifies the complete telephone number of the destination pager. (Maximum 20characters)

Pager Phone Number

Specifies the maximum number of characters allowed (by the service provider) in the textstring that is sent to the pager. (This field cannot have a value of zero.)

Max Characters

Specifies the number of redial attempts that can be made.Retries

Enables or disables the Pager Destination.Enabled

Enables you to specify the rules that filter alarm and event notifications. Each filter hasan Item, Operator, and Value.

Filters

Enables some predefined format characteristics of the notifications that are sent to adestination. Predefined format characteristics include:• Notification Priority• Notification Message (content)• Value• Site Name• Item Description• Item Fully Qualified Reference• Item Category• Acknowledge Required• Previous Status(Enable a format by selecting the check box next to the format.)

Format

4. In the Destination section (Figure 29), click New. The Destinations Configuration edit fields appear (Figure 30).


Figure 30: NAE Pager Destination Tab - Edit Mode

Note: The Max Characters field defines the length of the text string that is sent to the pager. This field cannothave a value of zero (Figure 30).

5. Enter the appropriate values for the specified pager message destination.

Note: These fields establish values for attributes that are specific to the pager destination and message forspecified alarm notifications generated from this NAE. Refer to Alarm and Event Management in theMetasys system Help for additional information on setting the attribute values for alarm and eventnotifications.

6. To filter the conditions that trigger a pager notification, click New next to the filters section of the Pager DestinationConfiguration tab (Figure 30). The Add Filter dialog box appears (Figure 31).

Figure 31: Add Filter Dialog Box

7. Select the item, operator, and value of the condition that you want to trigger a pager notification. (Refer to EventMessage Routing, Filtering, and Destinations in the Metasys System Help for additional information on addingfilters.)


8. Add additional pager destinations and filters as desired.9. Click OK.10. Click Save (Figure 30).

Creating NAE SNMP Alarm Notifications and DestinationsYou can set up an NAE to generate and deliver alarm and event messages on a network using SNMP networkmonitoring.

You can typically use SNMP monitoring for large BAS networks with many network devices. Alarm notifications aresent to and stored on an SNMP management computer that monitors all devices on the network.

You must set up SNMP monitoring at the network level and an SNMP management device must be assigned onthe network. If you are applying a Metasys system to any existing network, consult with the network administratoror IT department that administers the LAN to determine if SNMP monitoring is available on the network.

Note: In most scenarios, we recommend that you set up the SNMP DDA and configure the SNMP notifications andthe notification destinations after an NAE is configured with an archive database that includes the userdatabase.

1. In the Site Management Portal UI, display the NAE device object and click the SNMP tab.2. Click Edit. The SNMP Configuration Edit screen appears (Figure 32).

Figure 32: NAE SNMP Configuration Tab - Edit Mode

3. In the Shared Configuration section, set SNMP Enabled value to True if your network application uses SNMPmonitoring.

4. Type the IP address or host name values of the SNMP Management device (computer).5. In the Read Only Community and Read/Write Community fields, enter the community string used by the

Enterprise/Network Management Systems (E/NMS) to retrieve data from objects maintained by managed devices(Table 16).


Table 16: Share Attributes for SNMP DestinationInitial ValueDescription (Value Requirement/Range)AttributeFalseEnables or disables SNMP DDA on the NAE. (True, False)SNMP Enabled

SNMP Version 1Specifies the version of SNMP used on the network on which the NAEresides. (Not required if SNMP Enabled is set to False)

SNMP Trap Version

–Specifies the IP address or host name of the SNMP Managementdevice on the network on which the NAE resides. (Not required ifSNMP Enabled is set to False)

SNMP Management Device

161Specifies the port on the SNMP server where SNMP notifications aresent. (Not required if SNMP Enabled is set to False)

SNMP Request Port

–Specifies the contact person for the SNMP notifications. (Not requiredif SNMP Enabled is set to False)

Contact Person

publicSpecifies the community name used by the NMS to modify data inobjects maintained by managed devices. (Not required if SNMPEnabled is set to False)

Public Community Name

String BasedSpecifies the format used to generate SNMP notifications. Change toMIB Based when SNMP management application uses the MetasysMIB file to translate SNMP notifications. (Not required if SNMPEnabledis set to False)

SNMP Trap Message Format

6. Click New in the Destinations section. The Destination Configuration edit screen appears (Figure 33).


Figure 33: SNMP Destination Configuration Tab - Edit Mode

7. Enter the Destination information for the SNMP trap (Table 17).

Table 17: Attributes for Specific SNMP NotificationsInitial ValueDescription (Value Requirement/Range)AttributeDestination #Specifies a functional name for the destination SNMP server. (Maximum

20 characters)Label

PublicSpecifies the SNMPCommunity Name used by the Network ManagementSystem (NMS) group to listen to the traps. (Maximum 20 characters)

Trap Community Name

0.0.0.0Specifies the IP Address of the NMS system that receives the trapmessages.

IP Address

162Specifies the target port on the SNMP server that listens for trap messages.(Typically Port Number 162)

Destination Port Number


Table 17: Attributes for Specific SNMP NotificationsInitial ValueDescription (Value Requirement/Range)AttributeTrueEnables or disables the SNMP destination.Enabled

–Enables you to specify the rules that filter alarm and event notifications.Each filter has an item, operator, and value.

Filters

–Allows you to enable some predefined format characteristics of thenotifications that are sent to a destination. Predefined format characteristicsinclude:• Notification Priority• Notification Message (content)• Value• Site Name• Item Description• Item Fully Qualified Reference• Item Category• Acknowledge Required• Previous Status(Enable a format by selecting the check box next to the format.)

Format

8. Click Save when finished.

Setting the Time, Date, Time Zone, and Time SynchronizationHow you set the time zone, date, and time on an NAE depends on how the NAE fits into the Metasys site hierarchy.See Appendix: Time Zone, Date, and Time Management for information and detailed procedures on setting timezone, date, and time on an NAE and on a Metasys network.

Setting up the NAE Alarm ParametersNAEs ship from the factory with several pre-configured default diagnostic alarms that monitor the NAE hardware.You can edit these default alarm settings or create new alarms for the NAE hardware.

You can also create new alarms and edit existing alarms for supported field devices on the NAE field trunks.

Editing the Existing Alarm Parameters1. In the Site Management Portal UI, select and drag the desired NAE object or field device object from the Navigation

panel and drop it in the Display panel. The NAE or field device Focus screen opens.2. Click the Alarm tab. The Alarm Configuration screen opens (Figure 34).


Figure 34: NAE Alarm Configuration Tab

3. Select items in the Select Item(s) list to edit existing alarms. (To create new alarms, see Creating a New Alarm.)4. Click Edit. The NAE Alarm edit screen appears (Figure 35).


Figure 35: NAE Alarms Tab Edit Mode

5. Edit the desired Attributes for the NAE or field device, and click Save to save the edited alarm settings.

Creating a New AlarmYou can create new alarms for the NAE or any of the supported field devices on the field trunks attached to the NAE.

1. Select and drag the desired NAE or field device object from the Navigation panel into the Display panel. TheNAE or field device object Focus screen opens.

2. Select the Alarm tab and the device’s Alarm screen opens. Click New and the Insert AlarmWizard opens (Figure36).


Figure 36: Insert Alarm Wizard

3. Select the device Attribute for which you want to create an alarm.4. Follow the Wizard instructions and create or edit the values for the Attribute for which you want to create an

alarm.5. Click Save when you have finished creating the desired alarm parameters for the device Attribute.

Designating an NAE as the Site DirectorAll NAEs ship from the factory with a Site object and therefore are Site Directors by default. To designate the SiteDirector on a new site, you must demote all the NAEs on the site that are not designated as the Site Director. Youmust reset an NAE when it is demoted.

In many Metasys network site commissioning and configuration scenarios, the Site Director status of the NAEs onthe site is built into the archive database for the site. The status of these devices is established on the NAEs whenthe archive database is downloaded from the SCT to the site devices. The SCT database download overwrites theexisting values in the NAEs.

Note: If an ADS/ADX is on a site, an NAE cannot be the Site Director. If an NAE55 is the Site Director, it cansupervise up to four additional supervisory devices on the site (NAE35s, NAE45s, NCE25, or NAE55s only).If an NAE45 is the Site Director, it can supervise up to two additional supervisory devices on the site (NAE35s,NAE45s, or NCE25s only). If an NAE35 is the Site Director, it can supervise up to two additional NAE35s orNCE25s on the site. NCE25s cannot supervise other network engines and should only be designated as theSite Director in stand-alone applications.

Designating an NAE as Site Director is typically done offline in the SCT but can be done online in the NAE UI. Theprocedure in this section describes how to designate an NAE as the Site Director online in the NAE UI. To do sowith the SCT, go to the Changing the Site Director with the SCT section.

Note: If you do the site promotion/demotion online, you may lose any navigation trees built for the site. If UserViews (navigation trees) have already been built, upload them to the SCT, establish the Site Director, andthen download the navigation trees back to the source devices. The Site Director and NAE Computer Namevalues in the NAE UI must match the values in the SCT archive database.

To designate an NAE as a Site Director:


1. Select on the Navigation panel the NAE that you wish to demote from Site Director.2. Drag the NAE into the Display panel to open the Focus tab.3. Select the Advanced option.4. Click Edit. The NAE Focus edit screen appears (Figure 37).5. Scroll down to the Site attributes and select the Local Site Director field.

Figure 37: Designating the Site Director

6. Type the host name or IP address of the NAE or ADS/ADX that you want to designate as the local Site Director.7. Click Save. A confirmation message box appears (Figure 38).

Figure 38: Confirmation for Demoting Site Director

8. If you wish to proceed, click OK to this confirmation message; otherwise, click Cancel. If you click OK, the NAElogs you off and resets.

Note: To see the Site Director changes just made, wait several minutes for the NAE to reset, then log on again.The navigation tree shows the NAE is no longer the Site Director.


Changing the Site Director with the SCTNote: If you have already changed the Site Director and downloaded the site, go to Moving the Security Database

and Clearing It from the Demoted Site Director.

1. Start the SCT, open the archive database for the site, and choose the new Site Director in the Site object.2. Download the database so that every device recognizes the new Site Director.

Removing User Accounts from a Demoted Site DirectorIf you demote a supervisory controller or ADS/ADX from a Site Director to a child device on the site, all user accountsthat you added to the device while it was a Site Director remain in the security database. If you determine that useraccounts on the demoted site should be removed after the demotion has occurred, use the SCT to perform thefollowing steps to prepare a clean security database with all user-defined accounts deleted. You can then downloadthis clean database to the demoted device.

Moving the Security Database and Clearing It from the Demoted Site Director1. Create a backup of the Security database of the demoted device, but only if you are using the same set of users

on the new or existing Site Director.2. Create a backup of the Security database from one of the devices (NAE/NIE/ADS/ADX) on the site that has

never been a Site Director and has never had a Site Director’s Security database restored to it (in other words,has a clean Security database with only the default user accounts).

3. Restore the clean copy of the Security database that you created in Step 2 to the device that was demoted fromthe Site Director.

4. If you are using the Security database of the demoted device on the new Site Director, restore the Securitydatabase that you backed up in Step 1 to the new or existing Site Director.

5. Create a backup of the Security database from the device that was demoted and restored with a clean databasein Step 3.

This step ensures that the device Security database in the SCT matches the clean Security you restored to thedevice in Step 3.

Establishing a Dial-up Connection to an NAEA dial-up connection configuration is typical for a single NAE at a remote location that does not have an Ethernetconnection to a LAN.

The NAE you are dialing out to and the NAE modem must be configured properly for dial-up connections. See theModems and Dial-Out Features section for additional information on setting up an NAE and modem for dial-up.

Note: Do not use a dial-up connection for the initial setup of an NAE. Use a direct connection or stable networkconnection to commission a new NAE.

The initial default baud rate for dial-up connections is 115,200 baud.

You can use the Launcher application for dial-up connections. Launcher removes the dependency on the publicJava Runtime Engine (JRE) for the Site Management Portal (SMP) user interface at Release 6.0 (or later) by placinga private edition of the JRE on the client computer. Refer to the Launcher Installation Instructions (LIT-12011783)and the Launcher Help (LIT-12011742) for information on installing and using the Launcher tool.

To connect to an NAE through a dial-up connection:

1. Start the computer and initiate a dial-up connection to the NAE.2. Open the Launcher application.3. Select the NAE from the SMP profile list of the Launcher, and click Launch.

Configuring an NAE to Dial Out to an ADS/ADXAn NAE can be configured to dial out through a modem to an ADS/ADX (on a different site) to deliver trend data,alarms, and other information to the ADS/ADX for storage and analysis.


You can use a direct connection from a computer to an NAE to configure the NAE and modem for dial-out. You canalso connect the computer to the NAE with an Ethernet crossover cable to configure the NAE and modem.

Note: The dial-out capability is intended for small networks with a single NAE or only a few NAEs. Each NAErequires its ownmodem and phone line connection to dial out to an ADS/ADX. NAEs without a modem cannotdial out to an ADS/ADX through the Site Director’s modem.

1. In the Site Management Portal UI, display the NAE device object.2. On the Viewmenu, click Selected Item; the NAE Focus window appears in the Display panel. Select the Advanced

option and then click Edit. The NAE Focus edit screen appears. Scroll down to the Site attributes.

Figure 39: Configuring NAE to Dial Out to an ADS/ADX - Focus Tab

3. Make sure that the ADS/ADX Connection Type value is Dial (Figure 39).4. Verify that the ADS/ADX Repository attribute is the first IP address in the range specified when configuring the

ADS/ADX to accept incoming connections. (Refer to theConfiguring an ADS/ADX to Accept Dial-Up Connectionssection of the ADS/ADX Commissioning Guide [LIT-1201645] for more information.)

5. Edit the other ADS/ADX attributes as needed.6. Click Save.7. Select the Network tab and click Edit. The Network edit screen appears. Scroll down to the ADS/ADX Dial-up

section (Figure 40).


Figure 40: Configuring ADS/ADX Dial-up on the NAE - Network Tab

8. In the Connect Using drop-down box, select Internal modem or External modem.9. Type in the Access Number value, which is the complete telephone number of the ADS/ADX or the Internet

Service Provider (ISP) to which the NAE is dialing.10. Verify that the ADS/ADX Dial-up ISP Username and ISP Password values match either the account (user name

and password) selected for incoming messages to the ADS/ADX or the user name and password assigned bythe ISP.

Note: The user name and password values need not match theMetasys system account values because thesevalues are used for establishing dial-up connections only.

11. Click Save.

Printing Information from the NAE Site Management Portal UIThe NAE allows printing of the information displayed in the panels of the Site Management Portal UI. The informationmust be selected before it can be printed.

1. Select an NAE object in the Navigation panel and drag it to the Display panel of the Site Management Portal UI.The Focus tab for the selected NAE appears in the Display panel.

Note: You can preview the print output by selecting Print Preview.2. Select the Item > Print menu option.3. Select from the available printers and click OK.


Replacing an NAETo replace an NAE on a network site, update the site registration to ensure that devices on the site communicatewith the new (replacement) NAE; otherwise, devices may attempt to communicate with the NAE that was removedfrom the site.

If you do not remove an NAE from a site correctly, the Site Director may attempt to send messages to the old NAE,creating unnecessary network traffic.

If the NAE’s trend data is stored in an ADS repository, forward the data prior to beginning the upgrade followingthese steps for each engine:

1. Select a supervisory engine in the Navigation tree.2. Select Action > Commands. A list of available commands appears.3. Select Archive, then click Send. The archived trend data is sent to the ADS/ADX.

To replace an NAE:

1. Using the SCT, upload the current copy of the NAE database, so that it can be downloaded to the new NAElater.

2. Disconnect the old NAE from the network.3. Once the old NAE device is offline, go to the Site Director UI and select the old NAE in the All Items navigation

tree.4. Right-click the NAE and select Remove from Site from the pop-up menu. This removes the old NAE from the

site registration table.5. Connect the new NAE to the network, and power on the new NAE.

Download the old NAE archive database to the new NAE. The new NAE is operational on the network.

Note: When the new NAE comes online, it registers itself with the Site Director.

TroubleshootingThis section describes some of the most common problems encountered when setting up and operating NAEs. Usethe general solution guidelines and procedure references in this section to avoid or resolve these problems. Table18 provides a list of common NAE problems and their solutions.

This section is not a troubleshooting guide for Metasys system networks, customer LANs, BAS networks, or the fielddevices connected to the NAE.

Troubleshooting field devices is covered in the field device documentation. Refer to the appropriate field devicedocumentation for additional information.

Note: To effectively troubleshoot an NAE, it may be necessary to isolate the NAE from the Ethernet network andthe associated field trunks and field devices, and then direct connect to the NAE with a computer to browsethe Site Management Portal UI.

Common NAE ProblemsSee the following sections and Table 18 when you encounter a problem with an NAE.

Corrupted NAE MemoryCorruption of nonvolatile NAE flash memory may render an NAE inoperable. Corrupted flash memory may occurfor a variety of reasons and is one of the most common NAE problems encountered when commissioning, configuring,updating, and operating the NAE.

A typical recovery procedure from corrupted NAE flash memory includes reloading the NAE disk image anddownloading the NAE archive database with a compatible version of the SCT. Refer to the NAE/NIE Update ToolTechnical Bulletin (LIT-12011524 ) for information on installing the NAE disk image. Refer to the SCT TechnicalBulletin (LIT-1201534) for information on upgrading NAE archive databases.


NAE Disk Image Update and Archive Download Related ProblemsOne of the most common causes of corrupted NAE flash memory is interrupting an NAE disk image update or archivedownload that is in progress. To avoid memory corruption and data loss, follow the procedure for disk image updatesand archive downloads carefully, and allow the NAE to complete the update and download without interruption.

Another common cause of update and upgrade related problems is version incompatibility of the SCT software, NAEsoftware, and the NAE archive databases. When you update the NAE disk image, you must update the NAE archivedatabase to match the new software version. The SCT application used to configure a Metasys network or NAEmust also be the same software version as the NAE software.

Refer to the NAE/NIE Update Tool Technical Bulletin (LIT-12011524) and see the Related Documentation sectionof this document for additional information on disk image updates and archive upgrades and downloads.

Data Protection Battery Related ProblemsImproper shipping, handling, installing, charging, or disconnecting of the NAE data protection battery may also resultin flash memory corruption and data loss.

To avoid problems related to the data protection battery, refer to the Setup and Adjustment sections in theNAE35/NAE45 Installation Instructions (Part No. 24-10050-6), the NCE25 Installation Instructions (Part No.24-10143-63), and the NAE55/NIE55 Installation Instructions (Part No. 24-10051-43) for proper procedures forconnecting, charging, and disconnecting the data protection battery before connecting supply power to the NAE.

Logon ProblemsLogon problems may occur when the user name or password are incorrectly entered at logon. If the default username and password fail, these initial values may have been changed by an administrator-level user. You need thedesignated user name and password to log on to an NAE.

Network Connection Related ProblemsMany network connection/communication problems result from incorrect device names, IP addresses, and otherattribute value errors entered into the Site Management Portal UI or incorrect values entered into the UI of theassociated network devices. If the NAE attribute values do not match the respective values entered in the devicesconnected to the NAE, the NAE and associated devices may not establish network connections or communications.

Check for proper device names, IP addresses, gateway, subnet masks, ports, baud rates, and other networkparameters in the Site Management Portal UI. Also check the appropriate servers, other computers, and field devicesconnected to the NAE, and ensure that the attribute values are correct for each computer or device.

See Determining the NAE IP Address and Device Name for a LAN Connection, Determining the NAE IP Addressand Device Name through a Serial Port Monitor, and Verifying Ethernet/IP Network Communications (Ping).

NAE Reset Related ProblemsCertain setting changes, initiated in the Site Management Portal UI, do not take effect until the NAE is reset. Resetthe NAE whenever prompted to, and allow the NAE to complete the reset sequence. See Reset Device Command.

Troubleshooting GuideTable 18 provides information for troubleshooting an NAE.


Table 18: Troubleshooting the NAESolutionProblemCorrupted flash memory or data loss are the most common causes of this problem.To resolve this problem:1. Ensure that the data protection battery is connected and charged. (Refer to

Installation Instructions for more information on handling, installing, andcharging the data protection battery.)

2. Ensure that the database does not exceed the NAE flash memory capacity.3. Reload the disk image and download the archive database to the NAE while

the NAE is disconnected from the network.

NAE does not operate when powered on(and POWER LED is on).

Corrupted flash memory or data loss are the most common causes of this problem.To resolve this problem:1. Ensure that database does not exceed the NAE flash memory capacity.2. Reload the disk image and download the archive database to the NAE while

the NAE is disconnected from the network.

NAE does not operate after updating thedisk image, downloading an archivedatabase, or installing a patch.

Check to make sure that 24 VAC power is connected correctly and that the 24VAC and POWER LEDs are on.

NAEdoes not communicatewith any otherdevice.

Check to make sure that communication terminal blocks and other communicationconnectors are firmly in place.

Check that the wiring is the correct size (18 AWG minimum for power, 18 AWGfor N2 Bus, 26 AWG for Ethernet communication).

Check that you have set the correct baud rate on each connected device.

Check the integrity of the wires and cables.

Check that N2 End-of-Line (EOL) switches are correct. Refer to the SettingTerminations section of the N2 Communications Bus Technical Bulletin(LIT-636018) for details on N2 EOL terminations.

Check that the N2 wires are connected properly and are not loose in the terminationblock.

No N2 Communication

Check that the N2 LEDs indicate communication.

Check that the N2 EOL switches are correctly set. Refer to the Setting Terminationssection of the N2 Communications Bus Technical Bulletin (LIT-636018) for detailson N2 terminations.

Check the entire N2 Bus. Refer to the N2 Communications Bus Technical Bulletin(LIT-636018).

Check that the LONWORKS network wires are connected properly and are not loosein the termination block.

No LONWORKS Communication

Connect the Metasys system Connectivity to LONWORKS network Tool, theCOM.PRO Tool, or a third-party LONWORKS network configuration tool to theLONWORKS network. Verify that it is possible to communicate with the devices onthe network including the NAE. If communication is good, verify that the NAEdatabase has been generated correctly and that the LONWORKS enabled devicedata corresponds to the devices installed. If the NAE does not respond, verify thatthe NAE has been correctly installed in the LONWORKS network database and thatthe network configuration image has been sent to the NAE. If the NAE cannot beinstalled, replace the NAE. Refer to the LONWORKS Network Integration with NAEand LCS Technical Bulletin (LIT-1201668) for NAE database generationinformation.

Check the entire LONWORKS network. Refer to the LONMARK Guidelines - PhysicalLayer for details (http://www.lonmark.org).


http://www.lonmark.org

Table 18: Troubleshooting the NAESolutionProblemVerify that you are using a patch cable for a hub or switch and a crossover cablefor a single computer connection.

No Ethernet Communication

Check the port and cable integrity. Make sure either the 10/Link, 100/Link, or100/1000 Link LED is green or yellow (indicating an established Ethernetconnection [1000 Mbps Ethernet connection is yellow]). Check that the hub orswitch into which the LAN connector is plugged works and is connected correctly.

Check the port connector and cable for integrity and make sure you have the rightdriver installed and configured if you are using an external modem. Three modemdrivers are pre-installed on the NAE:• U.S. Robotics USR5637 modem, 56K, external USB modem (requires 4.1.5

image or later)• Zoom Telephonics 2985 modem driver• Multi-Tech Systems MT5634ZBA-USB modem driver

Refer to the N1 Migration with the NIE Technical Bulletin (LIT-1201535).

No Modem Communication

To correct this issue, manually set the serial port settings. Check with your pagingservice provider to verify the correct number of bits and parity. In this example,the Nortel service uses 7 data bits and even parity. To enter the serial port settings:1. From the NAE Communications tab, click Edit.2. In the External Modem Config section, set the Extra Initialization Commands

to S13=7S19=2, where S13 = the number of data bits (S13=7)S19 = therequired parity: 0=no parity, 1=odd parity, 2=even parity (S19=2)

3. Reset the NAE.

USR 5637 modem connects, but garbledcharacters appear and eventuallycommunication drops.

Check that you have the right modem configuration string and dialing parameters.Refer to the N1 Migration with the NIE Technical Bulletin (LIT-1201535), or theMetasys System Extended Architecture Direct Connection and Dial-Up ConnectionApplication Note (LIT-1201639).

NAE does not dial in or dial out.

Check that the modem is set to the correct baud rate. Refer to the N1 Migrationwith the NIE Technical Bulletin (LIT-1201535).

Check that the phone line is plugged into the modem port and is active. To checkthe phone line, disconnect the NAE modem and use an analog phone to checkthat the line is active.

Check that the modem is set up properly for the application in use. For example,a pager DDA must use a dedicated modem and the Allow Incoming Connectionsattribute for this modem must be set to False. Additionally, the MRA feature andADS/ADX audit forwarding should not be configured to use the same modem asthe pager. For more details, see Modems and Dial-Out Features.

Check to make sure the battery is installed and that the BATT FAULT LED is notlit. Replace, if necessary, with appropriate replacement battery.

NAE loses data.

Do not unnecessarily press the system RE-BOOT switch.

The amount of data you are trying to process is too much for the NAE to handle.A value of 50% or less for the CPU Usage attribute of the NAE is considered OK,although other performance indicators should also be assessed. Refer to theNAEObject and the Diagnostics topics in the Metasys system Help system for moreinformation. Reduce the size of the database.

NAE runs slowly.


Table 18: Troubleshooting the NAESolutionProblemProgramming objects (LCT, Signal Select, Global Data) referencing analog objectswith small COV values (0.5%) are the most common cause. To determine thesource of the high CPU usage, follow these steps:1. Add a Trend extension to the Last Idle Sample of the NAE. This attribute is

the inverted instantaneous CPU Usage. For example, if this number is low(5%), then the CPU usage is high (95%). The CPU usage is an average over15-30 minute period.

2. Locate programming objects (Control System objects [LCT] or Signal Select)that reference objects with small COV Increments and disable them one at atime. Monitor the Last Idle Sample value after disabling the object. Within 30seconds, the Last Idle Sample should significantly increase if that object wasa contributing factor to the high CPU usage.

3. When the problem object is determined, then either manually or with MassEdit Live, update the COV increment to a larger value before re-enabling theprogramming object.

NAE is generating high CPU alarms.

Check for possible external interference. To reduce Radio Frequency (RF)interference, do not use cell phones or handheld transceivers within 3 meters (10feet) of the NAE.

All communication is disrupted.

Check that the power transformer secondary is not shared with another load.

When the internal temperature reaches the high limit, the NAE issues an alarmand lights the GENL FAULT LED, allowing you a chance to intervene beforeheat-related damage results.

NAE overheats.

Check that the unit has been installed according to the installation instructionsand that the mounting orientation is correct.

Make sure cables are not blocking the ventilation of the unit.

Clean out the dust in the unit with canned air (pressurized air used to cleancomputers and other sensitive devices).

Use the USB port and connect an external modem or replace unit. (See themodemliterature for more information on using external modems with the NAE.)

Internal modem no longer functions.

Replace the NAE.Unit has been damaged or all externalcauses of failure have been checked.

NAE Diagnostic ToolsThe NAE hardware and UI provide tools for diagnosing and troubleshooting hardware and software problems withthe NAE.

The primary NAE diagnostic tools include:

• the NAE Light-Emitting Diode (LED) Status Indicators• the Diagnostic Tab• the Summary Tab• a serial point monitor (See Determining the NAE IP Address and Device Name through a Serial Port Monitor.)

Other tools are also available, such as the SNMP Trap Browser and the (ping) command for determining the NAEIP address and ability to communicate on the TCP/IP network. See Determining the NAE IP Address and DeviceName for a LAN Connection and Troubleshooting Procedures for information on using the Trap Browser and theping command.


NAE Light-Emitting Diode (LED) Status IndicatorsFigure 41, Figure 42, and Figure 43 show the location and designation of the NAE35, NAE45, NAE55, and NIE55LEDs that indicate the status of the engines. Some models do not have all the LEDs shown in these figures. Table19 describes their Normal Status and Function. See Figure 44 and refer to the NCE25 Installation Instructions (PartNo. 24-10143-63) for information on the NCE25 LED status indicators.

Figure 41: NAE35/NAE45 LED Status Indicators

Figure 42: NAE55 LED Status Indicators

Figure 43: NIE55 LED Status Indicators


Figure 44: NCE25 LED Status Indicators

Table 19: NAE LED Status IndicatorsDescriptions/Other ConditionsNormal

StatusNAE SeriesLED Label

(Color)On Steady = Unit is getting power from either the battery or 24 VACpower. Also see the 24 VAC LED. Off Steady = Unit is shut down.

On SteadyNAE35/45 NAE55NIE55 NCE25

POWER (Green)

Flicker = Data is transferring on the Ethernet connection. Ethernettraffic is general traffic (may not be for the NAE).

Off Steady = No Ethernet traffic, probably indicates a dead Ethernetnetwork or bad Ethernet connection.

FlickerNAE35/45 NAE55NIE55 NCE25

ETHERNET(Green)

On Steady = Ethernet connection is established at 10 Mb/s.On SteadyNAE35/45 NAE55NIE55 NCE25

10/LINK (Green)

On Steady = Ethernet connection is established at 100 Mb/sOn SteadyNAE35/45 NCE25100/LINK (Green)

On Steady (Green) = Ethernet connection is established at 100Mb/s.

On Steady (Yellow) = Ethernet connection is established at 1,000Mb/s

On SteadyNAE55 NIE55100/1000 Link(Green/Yellow)

On Steady = Controllers are defined to FC A (Trunk 1) in the NAE55,but none are communicating. (NAE55 transmitting only)

Flicker = Normal communications; FCA port is transmitting andreceiving data. Flickers are generally in sync with data transmissionbut should not be used to indicate specific transmission times.

Off Steady = No controllers are defined to FC A (FC Bus 1 or N2Trunk 1) in the NAE55.

FlickerNAE55FCA (Green)

On Steady = Controllers are defined to FCB (Trunk 2) in the NAE55,but none are communicating. (NAE55 transmitting only)

Flicker = Normal communications; FC B port is transmitting andreceiving data. Flickers are generally in sync with data transmissionbut should not be used to indicate specific transmission times.

Off Steady = No controllers are defined to F B (FC Bus 2 or N2Trunk 2) in the NAE55.

FlickerNAE55FCB (Green)


Table 19: NAE LED Status IndicatorsDescriptions/Other ConditionsNormal

StatusNAE SeriesLED Label

(Color)Flicker = N2 controllers are defined to FC BUS in the NAE35/45,but none are communicating. (NAE35/45 transmitting only)

Fast Flicker (may appear Steady on) = Normal communications;FC BUS port is transmitting and receiving data. Flickers are generallyin sync with data transmission but do not indicate specifictransmission times.

Off Steady = No field controllers are defined to FC BUS in theNAE35/45.

NAE35/45 NCE25FC BUS or LON1

Blinking - 5 Hz = Data Transmission (normal communication) OffSteady = No Data Transmission On Steady = Communication lost,waiting to join communication ring

BlinkingNCE25SA BUS (Green)

Flicker = Data traffic between NAE devices. For an NAE that is nota Site Director, this LED indicates regular heartbeat communicationswith the Site Director. For a Site Director NAE, flashes are morefrequent and indicate heartbeat communications from all other NAEdevices on the site. For a single NAE on a network without anADS/ADX, there is no flicker.

Varies (seenext column)

NAE35/45 NAE55NIE55 NCE25

PEER COMM(Green)

On Steady = NAE software is running.

On 1 second, Off 1 second = NAE software is in startup mode.

On 0.5 seconds, Off 0.5 seconds = NAE software is shutting down.

Off Steady = Operating system is shutting down or software is notrunning.

On SteadyNAE35/45 NAE55NIE55 NCE25

RUN (Green)

On Steady = 24 VAC power present

Off Steady = Loss of 24 VAC power. In the Off Steady condition,the NAE may be running on battery power. Also see the POWERLED.

On SteadyNAE55 NIE5524 VAC (Green)

Flicker indicates modem is connected and receiving data.FlickerNAE35/45 NCE25MODEM RX2

Flicker indicates modem is connected and transmitting data.FlickerNAE35/45 NCE25MODEM TX1

On Steady = Battery fault. Replace the battery. Battery notconnected or cannot be charged. The BATT FAULT LEDmay remainOn for up to 24 hours after initially powering on the NAE55. If theBATT FAULT LED remains on longer than 48 hours after initiallypowering on the NAE55, check the battery connection or replacethe battery.

Off SteadyNAE35/45 NAE55NIE55 NCE25

BATT FAULT (Red)

On Steady = General Fault. Fault conditions are user configured insoftware. Pre-configured fault conditions include excessive CPUuse, flash or memory use, excessive CPU or Printed Wire Board(PWB) temperature, or battery fault. In normal operation, the GENLFAULT LED stays on steady for the first half of the startup sequence.Note: On NAE35/45 and NCE25 models the GENL FAULT LED

label designation is FAULT.

Off SteadyNAE35/45 NAE55NIE55 NCE25

GENLFAULTorFAULT(Red)

1 LED labeled FC BUS onmodels that support MS/TP Bus or N2 Bus and labeled LON onmodels that support LONWORKS network.2 Modem LEDs are only on NCE25 models with internal modems.

NAE35/NAE45 LED Startup SequenceDuring startup, the NAE35/NAE45 automatically initiates an LED test to verify the operational status of the LEDs.

Immediately after connecting supply power, the following LED lighting sequence occurs:


1. The POWER, FAULT, RUN, and PEER COM LEDs turn on, indicating that the Operating System (OS) is startingup. (After 2 seconds, the LEDs may change states depending on site-specific network activity.)

2. The PEER COM and FAULT LEDs shut off. The RUN LED flashes to indicate that the NAE35/NAE45 softwareis loading.

3. The LEDs display the operational status of the NAE35/NAE45. When the RUN LED goes on steady, startup iscomplete and the NAE35/NAE45 is operational.

The total time to start up the NAE35/NAE45 depends on the size of the database and may take several minutes.

NAE55/NIE55 LED Startup SequenceDuring startup, the NAE55/NIE55 automatically initiates an LED test to verify the operational status of the LEDs.

Immediately after connecting supply power, the following LED lighting sequence occurs:

1. The POWER, PEER COM, RUN, and GENL FAULT LEDs turn on, indicating that the OS is starting up. For theNAE55, the N2A and N2B LEDs also turn on.

2. The FCA, FCB, PEER COM, and GENL FAULT LEDs shut off. The RUN LED flashes to indicate that theNAE55/NIE55 software is loading.

3. The LEDs display the operational status of the NAE55/NIE55.When the RUN LED goes on steady, the applicationis running and the NAE55/NIE55 is ready.

The total time to start up the NAE55/NIE55 depends on the size of the database and may take up to 15 minutes.

Note: The NIE55 does not have FCA and FCB LEDs.

NCE25 LED Startup SequenceDuring startup, the NCE25 automatically initiates an LED test to verify the operational status of the LEDs. Immediatelyafter connecting supply power, the following LED lighting sequence occurs:

1. The POWER, BATT FAULT, 10 LINK, FAULT, RUN, and PEER COM LEDs turn on, indicating that the OS isstarting up. (After 2 seconds, the LEDs may change states depending on site-specific network activity.)

2. The BATT FAULT, PEER COM, and FAULT LEDs shut off. The RUN LED flashes to indicate that the NCEsoftware is loading.

3. The LEDs display the operational status of the NCE. When the RUN LED goes on steady, startup is completeand the NCE is operational.

The total time to start up the NCE25 depends on the size of the database and can take several minutes.

Diagnostic TabThe Diagnostic tab displays NAE hardware status information that may aid troubleshooting.

With the NAE object selected, click the Diagnostic tab to view current information about the NAE hardware status(Figure 45).


Figure 45: NAE Diagnostic Tab

You can also select, drag, and drop Network Protocol objects into the Display panel and click the Diagnostic tab toview information for the selected Network protocol (Figure 46).


Figure 46: BACnet Protocol Diagnostic Tab

Summary TabThe Summary tab (Figure 47) in the Site Management Portal UI provides a quick view of the status of the objectsand items currently in your site.

Select, drag, and drop an object from the Navigation panel in the Display panel, and click the Summary tab. Whenyou first click the Summary tab, the NAE requests the status of the items in the Display panel (Figure 47). Thisrequest may take a few minutes.

For additional information and explanations of the attributes found in the Summary and Diagnostic tabs, refer to theObject Help in the Metasys® system Help.


Figure 47: NAE Summary Tab

Troubleshooting ProceduresVerifying Ethernet/IP Network Communications (Ping)You can use the ping command to verify that computers on the Ethernet/IP network can communicate with othercomputers on the network.

To use the ping command, you must have a computer configured to use the TCP/IP protocol and at least one othercomputer connected to the network.

To verify the computers can communicate on the network using the ping command:

1. Go to Start > Run.2. Type cmd, then click OK to display the Command prompt.3. Type the ping command. Use the format ping xxx.xxx.xxx.xxx, where xxx.xxx.xxx.xxx is the IP address or domain

name of the computer you want to ping. (For example: ping 198.81.196.2, www.jci.com, or NAE008066050FFC.)4. Press Enter.

If you get a reply, the computers are communicating on the network.

If you do not get a reply, try pinging your own computer address.

• If you can ping your own address but not any other addresses, the problem is with the network. Check the Linklight on the network card.

• If you cannot get a reply from your own address, the problem is probably with the network card in your computeror with the TCP/IP properties. Check the network card in your computer, and verify the TCP/IP properties.

Pre-boot Execution Environment (PXE)The NAE implements a PXE client. If your network uses a PXE server, exclude the NAE MAC address from the PXEserver. If you do not exclude the NAE MAC address, the NAE may not start properly.

Note: Consult with the system administrator or IT department to determine if the network has a PXE server.


Determining the NAE IP Address and Device Name for a LAN ConnectionThe IP Address determined by this procedure is the IP Address used on a LAN connection, not serial or dialconnections.

Determining the NAE IP Address By Using the NCTYou can use the Network Engine (NxE) Information and Configuration Tool (NCT) to discover the NAE. To determinethe IP address of an NxE by using the NCT to discover the device, start the NCT, click Discover, and look for theNxE in the Discovered Devices list. For more information, refer to the NxE Information and Configuration ToolTechnical Bulletin (LIT-1201990).

Note: The NxEs must be connected to the same subnet as the NCT computer for the NCT to detect them. NCE25,NAE35, and NAE45 engines must be at Release 3.0 or later to respond to the NCT discovery request. NxE55engines must be at Release 4.1.11 or later to respond to the NCT discovery request.

Determining the NAE IP Address and Device Name through a Serial Port MonitorWhen an NAE35, NAE45, NAE55, NIE55, or NCE25 is powered on, it sends a text string to its serial port that containshelpful information, such as its current IP address and device name. For the NAE35 or NAE45, this data stream issent to the RS232C A Serial Port. For the NAE55 or NIE55, this data stream is sent to Serial Port B; for the NCE25,the data is sent to the RS232C port. Table 20 and Table 21 provide examples of the data that is sent.

Table 20: Example NAE35, NAE45, and NCE25 Startup Data StreamExample OutputDevice InformationNAE-1Host Name

YesDHCP Enabled

159.222.8.206IP Address

255.255.252.0Subnet Mask

159.222.8.2Default Gateway

159.222.8.9DHCP Server

00-80-66-05-0F-FCMAC Address

00-00-00-00-00-00Neuron® ID

MS-NAE4511-1Model Number

108 MbRAM Memory

101 MbNAND Memory

Windows CEOS Type

115200, 8, –1COM1

115200, 8, –1Internal Modem

115200, 8, –1USB Modem

GoodBattery Status

Table 21: Example NAE55/NIE55 Startup Data StreamExample OutputDevice InformationNAE-1Host Name

YesDHCP Enabled

159.222.8.206IP Address

255.255.252.0Subnet Mask

159.222.8.2Default Gateway

159.222.8.9DHCP Server

00-80-66-05-0F-FCMAC Address


Table 21: Example NAE55/NIE55 Startup Data StreamExample OutputDevice Information00-06-10-25-03-00Neuron ID

MS-NAE5501Model Name

Note: The IP address and device name are internal to the NAE and change if the NAE is attached to a networkusing DHCP, unless the DHCP server is configured to assign a static IP address. Also, if an NAE is connectedto a network and has an IP address and is then disconnected from the network, a VT100 terminal emulatorsees zeros as the IP address until the NAE is restarted.

To determine the NAE IP address and device name through a serial port monitor, a VT100 terminal emulator programmust be installed on the computer connecting to the device. Windows XP includes the terminal emulator programHyperTerminal®, but Windows 7 does not include one. Check with your local IT department (or technical supportteam) for a recommended VT100 terminal emulator program to use with Windows 7.

To determine the NAE IP address and device name through a serial port monitor on a computer running WindowsXP:

1. Connect a VT100 terminal or a computer with a VT100 terminal emulator to the RS232C A serial port on anNAE35/NAE45, the RS232C serial port on an NCE25, or the serial port B on an NAE55/NIE55 using a nullmodem cable.

2. Enter the values in Table 22 to configure the VT100 terminal emulator.

Note: The values for the RS232C A serial port on an NAE35/NAE45, the RS232C serial port on an NCE25, orserial port B on an NAE55/NIE55 cannot be changed using the Site Management Portal UI.

Table 22: VT100 Terminal Emulator SettingsValues for NAE55/NIE55Values for NAE35, NAE45, or

NCE25Setting

88Data Bits

NoNoParity

11Stop Bits

9600 baud115200Baud Rate

Hardware flow controlNoneFlow Control

Note: If using a VT100 terminal emulator, set the emulation setting to VT100.3. Disconnect power to the NAE and wait until it completes its shutdown sequence.4. Connect the NAE to the LAN if using DHCP so the DHCP server can assign the IP address.5. Reconnect power to the NAE. A few minutes after the NAE powers up, its IP address is sent to the serial port.6. Note the IP address and device name listed in the resulting text file on your VT100 emulator.

Notes on Setting a Computer to Use APIPAIf you are configuring an NAE for use on an Ethernet LAN without DHCP or DNS support, you need to change thecomputer’s IP address and subnet mask to be compatible with Automatic Private Internet Protocol Addressing(APIPA). If you are not familiar with these settings, see theWindows operating systems Help or talk to the customer’sNetwork Administrator. If you are familiar with these procedures, the following notes describe how to set yourcomputer to use APIPA (in MicrosoftWindows XP operating systems) or how to set your IP address to be compatiblewith APIPA for other Windows operating systems.

The easiest method to change the computer’s IP address and subnet mask to be compatible with APIPA is to enableAPIPA on the computer (if supported). The Windows XP operating system supports APIPA. To enable APIPA on acomputer with a Windows XP OS:

1. View the local area connection properties of the active network connection as follows:Go to Start > Settings > Network Connections.a.


b. Right-click the icon for the active network connection and select Properties. The Local Area ConnectionProperties screen appears.

2. Select the Internet Protocol (TCP/IP) item and click Properties.3. Under the General tab, select Obtain an IP Address Automatically.4. Under the Alternate Configuration tab, select Automatic Private IP address.

For Versions of Windows OS That Do Not Support APIPA1. View the local area connection properties of the active network connection as follows:

Go to Start > Settings > Network Connections.a.b. Right-click the icon for the active network connection and select Properties. The Local Area Connection

Properties screen appears.2. Select the Internet Protocol (TCP/IP) item and click Properties.3. Select the Use the following IP Address option.4. Enter a static IP address between 169.254.0.1 and 169.254.255.254 and a subnet mask of 255.255.0.0.5. Verify the chosen static IP address is not in use by pinging the proposed IP address. If you receive no reply, the

IP address is not in use.

Technical SpecificationsTable 23: NAE35, NAE45, NAE45-Lite Models

Dedicated nominal 24 VAC, Class 2 power supply (North America), Safety Extra-Low Voltage(SELV) power supply (Europe), at 50/60 Hz (20 VAC minimum to 30 VAC maximum)

Power Requirement

25 VA maximumPower Consumption

0 to 50°C (32 to 122°F); 10 to 90% RH, 30°C (86°F) maximum dew pointAmbient OperatingConditions

-40 to 70°C (-40 to 158°F); 5 to 95% RH, 30°C (86°F) maximum dew pointAmbient Storage Conditions

Supports data protection on power failure. Rechargeable NiMH battery: 3.6 VDC 500 mAh,with a typical life of 5 to 7 years at 21°C (70°F); Product Code Number: MS-BAT1020-0

Data Protection Battery

192 MHz Renesas® SH4 7760 RISC processorProcessor

128 MB Flash nonvolatile memory for operating system, configuration data, and operationsdata storage and backup

128 MB Synchronous Dynamic Random Access Memory (DRAM) for operations data dynamicmemory

Memory

Microsoft® Windows® CE embeddedOperating System

One Ethernet port; 10/100 Mbps; 8-pin RJ-45 connector

One optically isolated RS-485 port; 9600, 19.2k, 38.4k, or 76.8k baud (depending on protocol);with a pluggable and keyed 4-position terminal block (FC Bus available on NAE351x-1 andNAE451x-1 models only)

One LONWORKS port; FTT10 78 Kbps; pluggable, keyed 3-position terminal block (LONWORKS

port available on NAE352x-x and NAE452x models only)

One RS-232-C serial port with standard 9-pin sub-D connector that supports standard baudrates

There is a second serial port on models without an internal modem that supports an optional,user-supplied external modem.

One USB serial port with standard USB connector that supports an optional, user-suppliedexternal modem

Option: One telephone port for internal modem; up to 56 Kbps; 6-pin modular connector (NAEmodels with an optional internal modem have one RS-232-C serial port only.)

Network and Serial Interfaces


Table 23: NAE35, NAE45, NAE45-Lite ModelsPlastic housing material: ABS + polycarbonate

Protection: IP20 (IEC60529)

Housing

On flat surface with screws on three mounting clips or a single 35 mm DIN railMounting

131 x 270 x 62 mm (5.2 x 10.6 x 2.5 in.)

Minimum space for mounting NAE35 and NAE45: 210 x 350 x 110 mm (8.3 x 13.8 x 4.3 in.)

Dimensions (Height x Widthx Depth)

1.2 kg (2.7 lb)Shipping Weight

United States UL Listed, File E107041, CCN PAZX, UL 916, Energy Management Equipment;FCC Compliant to CFR47, Part 15, Subpart B, Class AUL Listed, File S4977, UUKL 864 - 9thEdition, Smoke Control Equipment (MS-NAE35x0-2U and MS-NAE45x0-2U models only)

Compliance

Canada UL Listed, File E107041, CCN PAZX7, CAN/CSA C22.2 No. 205, Signal EquipmentIndustry Canada Compliant, ICES-003

Europe CE Mark - Johnson Controls, Inc., declares that this product is in compliance with theessential requirements and other relevant provisions of the EMC Directive 2004/108/EC.

Australia and New Zealand C-Tick Mark, Australia/NZ Emissions Compliant

BACnet International BACnet Testing Laboratories™ (BTL) 135-2004 Listed BACnet BuildingController (B-BC)

Table 24: NAE55xx-2 and NIE55xx-2Dedicated nominal 24 VAC, Class 2 power supply (North America), Safety Extra-Low Voltage(SELV) power supply (Europe), at 50/60 Hz (20 VAC minimum to 30 VAC maximum)

Power Requirement

50 VA maximumPower Consumption

0 to 50°C (32 to 122°F); 10 to 90% RH, 30°C (86°F) maximum dew pointAmbient Operating Conditions

-40 to 70°C (-40 to 158°F); 5 to 95% RH, 30°C (86°F) maximum dew pointAmbient Storage Conditions

Supports data protection on power failure. Rechargeable gel cell battery: 12 V, 1.2 Ah, witha typical life of 3 to 5 years at 21°C (70°F); Product Code Number: MS-BAT1010-0

Data Protection Battery

Maintains real-time clock through a power failure. Onboard cell; typical life 10 years at 21°C(70°F)

Clock Battery

1.6 GHz Intel® Atom™ processor for MS-NAE55xx-2 modelsProcessor

4 GB Flash nonvolatile memory for operating system, configuration data, and operations datastorage and backup for MS-NAE55xx-2 models.

1 GB Synchronous Dynamic Random Access Memory (DRAM) for operations data dynamicmemory for all models

Memory

Microsoft® Windows® Embedded Standard (WES) 2009Operating System

One Ethernet port; 10/100/1,000 Mbps; 8-pin RJ-45 connector

Two optically isolated RS-485 ports; 9600, 19.2k, 38.4k, or 76.8k baud; pluggable and keyed4 position terminal blocks (RS-485 ports available on NAE55 models only)

Two RS-232-C serial ports, with standard 9-pin sub-D connectors, that support all standardbaud rates

Two USB serial ports; standard USB connectors support an optional, user-supplied externalmodem

Options: One telephone port for internal modem; up to 56 kbps; 6-pin modular connector

One LONWORKS port; FT3120 78 kbps; pluggable, keyed 3-position terminal block (LONWORKS

port available on NAE552x-x models only)


Plastic housing with internal metal shield

Plastic material: ABS + polycarbonate UL94-5VB

Protection: IP20 (IEC 60529)

Housing


Table 24: NAE55xx-2 and NIE55xx-2On flat surface with screws on four mounting feet or on dual 35 mm DIN railMounting

226 x 332 x 96.5 mm (8.9 x 13.1 x 3.8 in.) including mounting feet

Minimum space for mounting: 303 x 408 x 148 mm (12.0 x 16.1 x 5.8 in.)

Dimensions (Height x Width xDepth)

2.9 kg (6.4 lb)Shipping Weight

United States: UL Listed, File E107041, CCN PAZX, UL 916, Energy Management Equipment,FCC Compliant to CFR47, Part 15, Subpart B, Class A

Compliance

Canada: UL Listed, File E107041, CCN PAZX7, CAN/CSA C22.2 No. 205, Signal Equipment,Industry Canada Compliant, ICES-003

Europe: CE Mark - Johnson Controls, Inc., declares that this product is in compliance with theessential requirements and other relevant provisions of the EMC Directive 2004/108/EC.

Australia and New Zealand: C-Tick Mark, Australia/NZ Emissions Compliant

BACnet International: BACnet Testing Laboratories™ (BTL) 135-2004 Listed BACnet BuildingController (B-BC)

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

Table 25: NxE85 ModelDell® PowerEdge® R410 or latest equivalentComputer Type

120–240 VAC 50/60 HzPower Requirement

480 WPower Supply

10 to 35°C (50 to 95°F); 20 to 80% RH (noncondensing twmax = 29°C)Ambient Operating Conditions

-40 to 65°C (-40 to 149°F); 5 to 95% RH (noncondensing twmax = 38°C)Ambient Storage Conditions

Recommended Uninterruptible Power Supply (UPS): American Power Conversion(APC®) Smart-UPS SC 450VA, 280W, 120 VAC input/output, NEMA 5-15R outputconnections, OEM Part No. SC450RM1U

Data Protection

Intel® Xeon® E5506, 2+ GHz, 4 MB Cache2 or comparable (subject to availability)Processor

2 GB or more, 1066MHz or higher, 2 x 1 GB, single ranked UDIMMs for 1 processorMemory

2 total (providing ample storage space, size subject to availability) 7.2K RPM SerialAdvanced Technology Attachment (SATA), 8.9 cm (3.5 in.) cabled

3 Gbps, RAID 1 configuration with add-in SAS6/iR (SATA/SAS Controller) or higher

Hard Disk

DVD ROM, SATAInternal Optical Drive

Windows Server® 2008 R2 OS (64-bit)Operating System

Symantec® Endpoint Protection, Small Business Edition (latest version)Antivirus Software

2 RJ45 1 Gbps Ethernet Ports, Port 2 is disabled.

2 video ports (1 front, 1 back)

1 9-pin Serial port

4 USB ports (2 front, 2 back)


4.3 x 43.4 x 62.7 cm (1.7 x 17.1 x 24.7 in.)Dimensions (Height x Width x Depth)

Mount in an EIA-310D compatible server cabinetMounting

15.9 kg (35 lb)Shipping Weight

Europe: CE Mark (Record Holder: http://www.dell.com/regulatory_compliance)Compliance


http://www.dell.com/regulatory_compliance

Appendix: Time Zone, Date, and Time ManagementTime Zone, Date, and Time Management IntroductionThe time zone, date, and time used by all devices connected to a Metasys site are synchronized automatically,preventing errors from manual time entry and clocks that become inaccurate over time. Network-wide timemanagement ensures that scheduling, trending, audit trailing, data collecting, time-stamping of alarms, and otherfunctions that require accurate time management use the same time zone, date, and time consistently for all systemoperations.

Time synchronization occurs on the Metasys network when an engine or server sends an IAmLive message to theSite Director. If the IAmLive message fails, the engine or server sends another message to retrieve the time fromthe Site Director. When the time is synchronized between the devices, a second IAmLive message is successful.

For network-wide time synchronization, the NAE/NIE/ADS/ADX designated as Site Director is the device time serverbecause it provides the time zone, date, and time for all other engines/servers on the site. All other devices areconsidered time clients because they receive the time zone, date, and time from the Site Director.

To set the date and time in the Site Director (and therefore the entire site), you can set the time manually or selecta time server for the Site Director. The time server for the Site Director is referred to as the site time server andshould be a reliable source not on the Metasys network. Regardless of how you set the date and time, you must setthe time zone in the Site Director.

Important: Edit the Device Time Servers attribute or Time Sync Period attribute in the Site object only.

Note: To ensure that the correct time appears on the Site Management Portal UI accessed from a client computer,apply the most recent Daylight Saving Time (DST) patch for the operating system on all clients that accessthe Site Director. The DST patch is available from Microsoft Corporation.

Overview of Time SynchronizationThis section contains a summary of how time synchronizes on a site with various system components. Table 26summarizes the time sources for various system items. All time is Universal Time Coordinated (UTC) and all systemdevices handle DST.

Table 26: Time SourcesTime SourceItemNAE/NIENAE/NIE Trend Data

NAE/NIENAE/NIE Events

NAE/NIENAE/NIE Commands

ADS/ADXAnnotations

ADS/ADXEvent Acknowledgements

ADS/ADX Site Director with NAEs/NIEsOn a site with an ADS/ADX Site Director and NAEs/NIEs, the following time synchronization steps occur:

1. ADS/ADX Site Director comes online.2. NAEs/NIEs come online and check in with the Site Director.3. Every 15 seconds, the NAEs/NIEs check for ADS/ADX online/offline conditions. If the ADS/ADX is offline, the

NAEs/NIEs send an IAmLive message to the ADS/ADX every 20 seconds.4. When the ADS/ADX receives the IAmLive message, it attempts to validate the security credentials of the

NAEs/NIEs. If the time in the NAEs/NIEs is different than the time in the ADS/ADX by 5 or more minutes, theengine security credentials are invalidated.

5. When the NAE receives back an invalidated credential, the NAEs/NIEs request the current time from the ADS/ADXand update the engine time to match.


Note: Time between an ADS/ADX and NAEs/NIEs synchronizes only if the time differs between the ADS/ADXand NAEs/NIEs by 5 or more minutes. In the worst case scenario, one NAE could be 4 minutes and 59seconds ahead of the ADS/ADX, and another NAE could be 4 minutes and 59 seconds behind theADS/ADX.

6. After time is synchronized and the ADS/ADX is online, the NAEs/NIEs send IAmLivemessages to the ADS/ADXevery 5 minutes (instead of every 20 seconds).

NIE and Child DevicesImportant: We recommend that time be synchronized carefully between the NIE and the N1 network, preferably

using a common external time server. All N1 network data collected by the NIE is time stamped at theNIE (no N1 network time stamps persist in the data collected by the NIE).

While the NIE can push time to the NCM, the preferred method of synchronization for the NIE and N1network is to have both synchronize with an external time server.

On a site with an NIE and child devices (NCMs, for example), the following time synchronization steps occur:

1. The NIE comes online and is mapped to NCMs.2. When the time changes in the NIE (as a result of synchronization with an ADS/ADX, for example), the NIE pushes

the time change down to the NCM. This time push requires that the Synchronize Time attribute of the NIE N1Integration object is enabled.

Time Synchronization MethodsThree methods for network time synchronization are available in the Metasys system, including Microsoft Windows®Simple Network Time Protocol (SNTP) time synchronization, Multicast, and BACnet® time synchronization.

You can use the Microsoft Windows and Multicast methods when an SNTP master time server is available. If theSite Director has no access to SNTP time servers, you can use the BACnet synchronization method.

To enable a time synchronization method, modify the Time Sync Method attribute for the Site. See the Steps forSuccessful Time Management and Setting the Time Synchronization Method sections.

Windows Time SynchronizationThe Windows time synchronization is Microsoft Corporation’s implementation of the standard Windows SNTPw32time. This method is also referred to as unicast synchronization. With this form of time synchronization, all routerscan route User Datagram Protocol (UDP) traffic. Windows time synchronization may have a larger time interval inwhich devices are out of sync with the SNTP master time server due to skewing and convergence.

If you use Windows time synchronization, you must define a device time server in the Site Director using the DeviceTime Servers attribute.

Note: If you implement an intentional time change for your site, in less than 5 minutes, all other devices on the siteupdate with the new time with Windows time synchronization.

Multicast Time SynchronizationTheMulticast time synchronization is the Johnson Controls implementation of SNTPw32time with Multicast capabilitiesand RFC-2030 compliance. This method delivers the same features as the Windows method, but also providesMulticast functionality. The Multicast method provides improved Metasys time synchronization between the SiteDirector and supervisory devices. A time domain server provides the master time to the Site Director, and the SiteDirector in turn multicasts the time to all supervisory devices on the Metasys network.

When a supervisory device first signs up with the Site Director, it polls the Site Director for the current time andmatches its time with the Site Director time. By default, every 5 minutes the Site Director broadcasts the current timeto all supervisory devices. If a particular device time differs 1.5 seconds or more from the Site Director time, thedevice adjusts its time to match. Additionally, if the Site Director time changes by more than 1 to 1.5 seconds, itsends out a Multicast time message to all devices within 2 seconds of the change.


This form of time synchronization requires that all routers on the site support Multicast routing (Internet GroupMulticast Protocol [IGMP]) because the Multicast time message crosses routers. The Johnson Controls SNTP timesynchronization reduces the time interval in which devices are out of sync with the SNTP master time server.

Note: All devices synchronized with Multicast time synchronization must be at Release 3.1 or later. For example,if you have an ADS at Release 3.1 and NAEs at Release 2.2, you cannot sync these devices using Multicasttime synchronization.

Note: If you implement an intentional time change for your site, within a few seconds, all other devices on the siteupdate with the new time with Multicast time synchronization.

BACnet Time SynchronizationBACnet time synchronization uses BACnet protocol to synchronize with BACnet devices such as the NAE. Use thismethod when the Site Director has access to a BACnet time server. This method is not available on the ADS/ADX.

Example NetworkStep 1 shows an example system with a common time zone, date, and time management setup. This example isrepresentative of the Multicast and Windows time synchronization methods.

The Site Director (in this case, an ADS) is configured to receive the date and time from an intranet time server. Thedate and time originates at an Internet time server (such as the Naval atomic clock). Using Simple Network TimeProtocol (SNTP), the intranet time server requests the time from the Internet time server. The Site Director requeststhe time from the intranet time server. Then, using the Metasys system automatic time synchronization, and themanually configured time zone, the Site Director automatically provides the time zone, date, and time to the otherengines/server on the Metasys network.

Figure 48: Time Management Sample System

Time ZoneThe time zone of the Site Director defaults to (GMT-06:00) Central Time (US & Canada). If your site is not in theCentral time zone, set the time zone for your location. When you set the time zone in the Site Director, it propagatesthe current time to all the engines/servers on the site. You must set the time zone in the Site Director even if youselect a site time server. In addition, set the time zone in all ADS/ADX devices, even though none of them are theSite Director.

When a non-Site Director NAE is downloaded in a different time zone than Central Standard Time (CST), the NAEmight revert to CST. This problem indicates that domain name resolution is not working properly. Consequently, theNAE cannot reach the ADX Site Director after download. You can solve this problem in one of two ways:

• Add the ADX name and IP address to the NAE host file. The NAE communicates to the Site Director as long asboth have the same date based on their time zones. Communication fails if the two machines are set to differenttime zones such that one has passed into the next day but the other has not. An example of this would be if the


Site Director is set to Japan Standard Time and the device is set to CST, and the time in Osaka has passedmidnight while the device is just after 10 A.M. the previous day.

• Set the NAE to the Site Director time zone and write the NAE Local Site Director attribute to the ADX IP address;then, upload the NAE. After that step, each download of the device is given the Site Director IP address andcorrect time zone.

Site Time ServerAs an alternative to setting date and time manually for a device, you can select a site time server. A site time serversets the date and time in the Site Director. If you have a split ADX, select the same site time server for both theweb/application server computer and the database server computer. Site time servers can be on your intranet, suchas a Domain Controller/Server; or on the Internet, such as the U.S. Naval Observatory Master Clock.

For a list of Navy master clocks, go to http://tycho.usno.navy.mil/.

See the Selecting a Site Time Server for the Site Director NAE/NIE or Selecting a Site Time Server for the SiteDirector ADS/ADX (Windows Method Only) sections.

Time in Device Object and UI Status BarThe time zone, date, and time in the Status Bar of the UI and the time zone, date, and time in the device object ofthe device to which you are browsing are the same time; however, there may sometimes seem to be a discrepancyor delay between the two.

In the Site Director, the time zone, date, and time in the device object of the device are set by you or by the designatedsite time server. In a non-Site Director NAE, the time zone, date, and time in the device object come from the SiteDirector. In a non-Site Director ADS/ADX, the time zone in the device object comes from your manual setting, butthe date and time come from the Site Director.

The Device object then passes the time zone, date, and time along to the Status Bar for display. If the device isbusy, it may take a few minutes for the time zone, date, and time to update correctly in the Status Bar.

Steps for Successful Time ManagementFor successful time management, do the following:

1. Verify that each non-supervisory engine/server on the Metasys network has the correct Site Director defined.

See the Verifying the Site Director Defined for an Engine/Server section.2. Set the time synchronization method for the site.

See the Setting the Time Synchronization Method section.3. Set the time zone and then set the date and time or select a site time server for the site.

See the NAE/NIE Is the Site Director or ADS/ADX Is the Site Director section.

If you have an NAE/NIE as the Site Director, the time zone, date, and time are set in the UI of the Site DirectorNAE/NIE. See the NAE/NIE Is the Site Director section. If you have non-Site Director ADSs/ADXs on the site,you must set the time zone for these servers.

If you have an ADS/ADX as the Site Director, the time zone, date, and time are set in the Windows OS of thecomputer where the ADS/ADX resides. See the ADS/ADX Is the Site Director section. If you have non-SiteDirector ADS/ADX devices on the site, you must set the time zone for these servers.

4. For Multicast time synchronization only, configure the SNTP Multicast attributes for the site.

See the Configuring Additional Multicast Time Synchronization Settings section.5. If a P2000 Security Management System (SMS) is integrated to the ADS/ADX server, both the P2000 and

ADS/ADX servers should reference the same network time server. If the two systems use different time servers,the P2000 and ADS/ADX servers are not clock synchronized, which results in intermittent or no communicationsbetween the two systems.


http://tycho.usno.navy.mil/

Verifying the Site Director Defined for an Engine/ServerFor time synchronization to work properly, all engines/servers on a site must have the correct name for the SiteDirector in the Local Site Director attribute. If an engine/server has the wrong device defined as Site Director, timesynchronization may not work properly on your Metasys site.

1. Log on to engine/server.2. Drag and drop the engine/server object to the Display frame.3. Select Advanced.4. Scroll to the Site section and verify the Local Site Director attribute contains the correct device (Figure 49). In

this example, the Site Director is an NAE (NAE-THREE).

Note: The Local Site Director may be entered as an IP address or host name. If entered as a host name, thename is case sensitive (for example, NAE-THREE is not the same as nae-three).

Figure 49: Site Director Field

Note: If the Site Director field contains the wrong device or is empty, click Edit. Edit the Site Director entry andclick Save.

5. Go to Setting the Time Synchronization Method.

Setting the Time Synchronization MethodSee the Time Synchronization Methods section for descriptions of the methods.

1. Log on to Site Director engine/server.2. Drag and drop the Site object to the Display frame.3. Click Edit.4. Select Advanced.5. In the Time section, in the Time Sync Method drop-down box, select the desired time synchronization method

(Windows or Multicast).

Figure 50: Time Sync Method Field

6. If you select Windows time, enter a device time server in the Device Time Servers attribute. A device time serveris required for Windows time synchronization.

7. Click Save.


Important: When the Time Sync Method is set to Multicast and the ADS/ADX computer is synchronized witha time source other than itself, the Site Time Server must be an SNTP Time Server to allow theADS/ADX to perform time synchronization. Time synchronization occurs when a change is detectedin the ADS/ADX computer local clock, or at the Site configured Time Sync Period.

Enabling Multicast time synchronization terminates the Windows win32time service, but changingthe Time Sync Method back to Windows does not re-enable the service. If you change the TimeSync Method back to Windows, you must manually start the win32time service, or restart the SiteDirector.

8. Go to NAE/NIE Is the Site Director or ADS/ADX Is the Site Director.

NAE/NIE Is the Site DirectorIf an NAE/NIE is the Site Director, you must set the time zone first, then either set the date and time or select a timeserver for the Site Director NAE/NIE.

Note: See the Verifying the Site Director Defined for an Engine/Server and Setting the Time Synchronization Methodsections before following the steps in this section.

Setting the Time Zone in the Site Director NAE/NIE1. Log on to the Site Director NAE/NIE.2. Drag and drop the Site object to the Display frame.3. Click Edit.4. In the Time section, in the Time Zone drop-down box, select the correct time zone for the device (Figure 51).

Figure 51: Time Zone in the Site Object

5. Click Save.

If you are also manually setting the date and time in the Site Director NAE/NIE, go to the Setting the Date andTime in the Site Director NAE/NIE section.

If you are selecting a time server for the Site Director NAE/NIE, go to the Selecting a Site Time Server for theSite Director NAE/NIE section.

Setting the Date and Time in the Site Director NAE/NIEBefore manually setting the date and time in the Site Director NAE/NIE, follow the steps in the Setting the Time Zonein the Site Director NAE/NIE section.

1. In the navigation tree, right-click the Site object and select Commands. The Commands dialog box appears.2. Click Set Time and enter a value in the text box (Figure 52).


Figure 52: Time in a Site Director NAE/NIE

3. Click Send.

Note: If you have a site time server selected, do not attempt to set the time manually. If you have one or moresite time servers defined, sending this command generates an error.

4. In the navigation tree, right-click the Site object and select Commands. The Commands dialog box appears.5. Click Set Date and select a date from the calendar (Figure 53).

Figure 53: Date in a Site Director NAE/NIE

6. Click Send.

Note: If you have one or more site time servers defined, sending this command produces an error. If you havea site time server defined, do not attempt to set the time manually.

The Site Director time zone, date, and time are now set and propagate to all other engines on the site.


Selecting a Site Time Server for the Site Director NAE/NIEBefore selecting a site time server for the Site Director NAE/NIE, follow the steps in the Setting the Time Zone inthe Site Director NAE/NIE section.

1. Reset the NAE/NIE for the time zone change to take effect.2. Log on to the NAE/NIE.3. Drag and drop the Site object to the Display frame.4. Click Edit.5. In the Time section, in the Site Time Servers field, click the browse button.

Note: The Device Time Servers field should be blank unless you are using Windows time synchronization. Donot change the value for the Time Sync Period attribute.

Figure 54: Site Time Servers in the Site Object

6. In the screen that appears, click Add (Figure 54).7. Enter the IP address of the SNTP server from which the Site Director receives its time (Figure 55).

Note: Specify a host name only if a DNS server is available to the Site Director.

Note: If you add more than one address, the Site Director NAE55/NIE55 tries to contact the first address. Ifthat fails, the NAE55/NIE55 contacts the second one, and so on. The NAE35/NAE45 engines use onlythe first address in the list.

Figure 55: Add Site Time Server

8. Click OK.9. Click Save. The Site Director now requests the date and time from the selected time server and propagates it

to all other engines on the site.10. Go to Configuring Additional Multicast Time Synchronization Settings if needed.

ADS/ADX Is the Site DirectorSet the time zone first, then either set the date and time or select a time server for the Site Director ADS/ADX.

Note: See the Verifying the Site Director Defined for an Engine/Server and Setting the Time Synchronization Methodsections before following the steps in this section.

Note: If you select a site time server for your Site Director ADS/ADX, and you also set the time manually in theADS/ADX, the manual time is overridden at the end of the time specified in the Time Sync Period attribute(default is 1 hour).


Setting the Time Zone in the Site Director ADS/ADX1. In the lower right corner of the ADS/ADX computer screen, double-click the time. If you are using Windows 7

OS, Windows Server 2008 R2 OS, or Windows Server 2008 OS, single-click the time. The Date and TimeProperties box appears (Figure 56). The appearance of this screen varies depending on the OS.

Figure 56: Time and Date on a Site Director ADS/ADX - Windows XP Professional OS

2. If you have Windows XP Professional OS, click the Time Zone tab (Figure 57). If you have Windows 7 OS,Windows Server 2008 R2 OS, or Windows Server 2008 OS, select the Change date and time settings optionand click Change time zone.

Figure 57: Time Zone on a Site Director ADS/ADX

3. Select a time zone from the drop-down list box.4. Select Automatically adjust clock for daylight saving changes, if present.5. If you have non-Site Director ADS/ADX devices on your site, set the time zone in those servers following the

instructions in this section.

If you are also manually setting the date and time in the Site Director ADS/ADX, go to the Setting the Date andTime in the Site Director ADS/ADX section.


If you are selecting a time server for the Site Director ADS/ADX, click OK and go to the Selecting a Site TimeServer for the Site Director ADS/ADX (Windows Method Only) or Selecting a Site Time Server for the Site DirectorADS/ADX (Multicast Method Only) section.

Setting the Date and Time in the Site Director ADS/ADXBefore manually setting the date and time in the Site Director ADS/ADX, follow the steps in the Setting the TimeZone in the Site Director ADS/ADX section.

1. In the Date and Time Properties box, click the Date & Time tab. If you have Windows 7 OS, Windows Server2008 R2 OS, or Windows Server 2008 OS, click the time in the lower right corner of the screen. Select theChange date and time settings option and click Change date and time.

2. Set the time and date.3. Click OK.

The Site Director time zone, date, and time are now set and propagate to all other engines/servers on the site.

Selecting a Site Time Server for the Site Director ADS/ADX (Windows Method Only)If you set up a site time server for your Site Director, you can set the date and time manually in the ADS/ADX, butthe manual settings are overridden at the end of the Time Sync Period.

Before selecting a site time server for the Site Director ADS/ADX, follow the steps in the Setting the Time Zone inthe Site Director ADS/ADX section.

1. On the Windows Start menu of the ADS/ADX computer, select Run. The Run dialog box appears (Figure 58). Ifyou have Windows 7 OS, click the Start icon and select All Programs > Accessories > Run.

Figure 58: Run Dialog Box

2. TypeNet time /setsntp:"10.10.16.1 10.10.16.2 ...", where 10.10.16.1 and 10.10.16.2 are example IP addressesof time servers.

Note: The IT department should provide the address of a suitable time server.

Be sure that the quotation marks are included (especially when listing multiple time servers).3. Click OK.

The Site Director now requests the date and time from the selected time server and propagates it to all otherengines/servers on the site.

Selecting a Site Time Server for the Site Director ADS/ADX (Multicast Method Only)Before selecting a site time server for the Site Director ADS/ADX, follow the steps in the Setting the Time Zone inthe Site Director ADS/ADX section.

1. Log on to ADS/ADX.2. Drag and drop the Site object to the Display frame.3. Click Edit.4. In the Time section, in the Site Time Servers field, click the browse button.

Note: Leave the Device Time Servers field blank. Do not change the value for the Time Sync Period attribute.


Figure 59: Site Time Servers in the Site Object

5. In the screen that appears, click Add (Figure 59).6. Enter the IP address of the SNTP server from which the Site Director receives its time (Figure 60).

Note: Specify a host name only if a DNS server is available to the Site Director. Leave the Device Time Serversfield blank.

For Multicast time synchronization, if you add more than one address, the Site Director ADS/ADX triesto contact only the first address.

7. Click OK.

Figure 60: Add Site Time Server

8. Click Save. The Site Director now requests the date and time from the selected time server and propagates itto all other engines/servers on the site.

9. Go to Configuring Additional Multicast Time Synchronization Settings.

Configuring Additional Multicast Time Synchronization SettingsIn addition to selecting the Multicast time synchronization method (Setting the Time Synchronization Method), youmust define other Multicast attributes.

To configure additional Multicast time synchronization settings:

1. Log on to Site Director engine/server.2. Drag and drop the Site object to the Display frame.3. Click Edit.4. Select Advanced.5. In the Time section, modify the attributes listed in Table 27 (Figure 61).


Figure 61: Multicast Time Synchronization Fields

Table 27: Multicast Time Synchronization FieldsDescriptionAttributeSpecifies the IP address used to multicast the SNTP message. This address identifies thegroup of devices to receive the SNTP message. The RFC-2030 defined standard addressis 224.0.1.1. The address is configurable to allow site specific use.

Multicast Group Address

Specifies the UDP port on which Multicast time synchronization polls and listens formessages. The RFC-2030 defined standard port is 123.The UDP port defined here mustmatch the Time Server’s UDP port for successful polling to occur.

Multicast UDP Port

Specifies the Time-to-Live (TTL) for a Multicast message. The value indicates the numberof router hops (number of routers to pass through) allowed before the message is not sent.Routers must be configured to pass Multicast messages to allow the time sync message topass.

Note: A default value of 1 typically stops the Multicast message from leaving the IP subnetof the Site Director. Most routers decrease the existing TTL upon arrival of a packet,and drop the packet instead of rerouting it when the TTL reaches 0.

Multicast TTL

Specifies the number of minutes between forcing a Multicast time synchronization messagefrom the Site Director to participating devices.

Multicast Heartbeat Interval

6. Click Save.


Appendix: Configuring and Maintaining PreferencesConfiguring and Maintaining Preferences IntroductionTheMetasys system provides customized preferences for the UI. The preferences allow authorized users to configurehow the UI behaves, including the sounds and colors, the startup view, and the ability to add links to externalapplications that can be accessed from within the UI of the ADS/ADX/SCT/NAE device.

Important: Preferences do not persist after an upgrade unless you take manual steps to save the settings beforeyou begin a system upgrade. See Preserving Preferences in an Upgrade.

Some steps in the following sections involve certain file operations, such as copying files and navigating to specificfolders. The tool used for these operations is either Windows Explorer (ADS, ADX, SCT, NAE55, NIE55, NxE85) orInternet Explorer Web browser (NAE35, NAE45, or NCE25). For an NAE55/NIE55, log on to the device remotelyusing the NxE Information and Configuration Tool (NCT), then use the Remote Desktop function in the NCT. Typeexplorer at the command prompt. For an NAE35/NAE45/NCE25, use the Start FTP function in the NCT. Accessthe NAE contents with Internet Explorer and type ftp://<NAE IP Address> in the Address line. For information onthe NCT, refer to the NxE Information and Configuration Tool Technical Bulletin (LIT-1201990).

Preferences ConceptsSystem and User PreferencesPreferences are divided into two categories: System Preferences and User Preferences.

System PreferencesSystem preferences apply to all users who log on to the site or device. System preferences affect the performanceand operation of the system. Only the MetasysSysAgent user and the BasicSysAgent user have authorization toconfigure system preferences. An audible alarm notification change is an example of a system preference. The SCTsupports a subset of system preferences. If the SCT is installed on an ADS/ADX, the preferences are shared by theUI and the SCT.

Before you make system preference changes, the preferences are read from the DefaultSystemPreferences.xmlfile. Once you make system preference changes, a new file called SystemPreferences.xml is created (Figure 62).Both of these files are located in the directory on the Metasys system device as indicated in Table 28.

Table 28: Location of Preferences FilesFile LocationMetasys System

Device

C:\Documents and Settings\All Users\Application Data\Johnson Controls\MetasysIII\Preferences1ADS/ADX

C:\ProgramData\Johnson Controls\MetasysIII\Preferences2

NAE55/NIE55 C:\Documents and Settings\All Users\Application Data\Johnson Controls\MetasysIII\Preferences

C:\ProgramData\Johnson Controls\MetasysIII\PreferencesNAE85/NIE85

\Storage\Metasys\PreferencesNAE35/NAE45/NCE25

1 This location applies if you have Windows XP Professional OS.2 This location applies if you have Windows 7 OS, Windows Server 2008 R2 OS, or Windows Server 2008 OS.

The procedure to synchronize system preferences within a site or to reuse the system preferences on another siteis a manual copy and paste process. Use the process to copy system preferences to other devices on the site or toother sites. See Copying Preferences between Devices.


Figure 62: System Preference Files

As highlighted in Figure 62:

• DefaultSystemPreferences.xml: This is the default system preferences file. It is installed as part of the standardinstallation for all Metasys system devices.

• SystemPreferences.xml: This file stores the configured system preferences. If you have not yet configuredsystem preferences, this file does not appear in the directory.

User PreferencesUser preferences apply to a specific Metasys system user. User preferences define how the information is displayedin the UI and do not affect the operation of the system. The colors and marker styles of a trend display are examplesof user preferences. Each user is authorized to view and edit their own user preferences.

The system automatically assigns a numbered user preference file name for each user calledUserPreferences-userID.xml, where userID is the identification number of the user. Using an identification number,rather than using the actual user name, serves two purposes. First, it avoids any conflicts that might arise if the username contains special characters. Second, it allows the user to be renamed without breaking the connection to theuser preferences file.

To view user identification numbers, open the Security Administrator screen and select User Preference File Namesunder the View menu (this option is available only to the MetasysSysAgent user). The user preference file namesappear in the Roles and Users pane (Figure 63) and correspond to files on the Metasys device in the directory asindicated in Table 28. As shown by two callouts in Figure 63:

• 1: User preference file name as seen in the Security Administration in the UI.• 2: User preference file as seen when accessing an NAE using Remote Desktop in the NCT.

The procedure to synchronize user preferences within a site or to reuse the user preferences on another site is amanual copy and paste process. Use the manual process to copy user preferences to other devices on the site orto other sites. See Copying Preferences between Devices.


Figure 63: User Preference File

Managing PreferencesPreferences are not archived on the SCT and they are not part of the upload/download process. Additionally,Preferences are not saved during a security backup when you upgrade. Preferences must be managed manually.

For information on managing preferences for each preference type, see the following sections:

• System Preferences• User Preferences


Detailed ProceduresConfiguring PreferencesNote: To configure the preferences of a specific user, you must log on as that user or as a user with Administrator

rights.

1. On the Tools menu of the UI, click Configure Preferences. The Metasys Preferences dialog box appears.2. Set the preferences according to the Preferences section of the Metasys system Help.

If you specified Level 1-4 Sound Files on the Alarm Settings tab, place the alarm sound files into the audio folderon the Metasys system device. The audio folder is located in the following directory:

For ADS/ADX/NAE55/NIE55/NAE85/NIE85:

C:\Inetpub\wwwroot\MetasysIII\UI\audio

For NAE35/NAE45/NCE25:

\Storage\Metasys\wwwroot\metasysIII\UI\audio

Note: If a sound file is missing from the folder, the Metasys system uses the default system beep for that alarmpriority.

Restoring Default System Preferences1. Access the Metasys system device on which you want to restore the default system preferences. (For example,

if this is an NAE55, use the Remote Desktop option available in the NCT.2. Navigate to the Preferences directory for the device as shown in Table 28.3. Delete the SystemPreferences.xml file.

Copying Preferences between Devices1. Access the source Metasys system device; that is, the one that contains the preferences you want to copy. (For

example, if this is an NAE55, use the Remote Desktop option available in the NCT. The local hard drive of yourcomputer is automatically mapped to the NAE through the remote desktop function.)

2. Navigate to the Preferences directory for the device as shown in Table 28.3. Copy SystemPreferences.xml (system preference) or UserPreferences-userID.xml (user preference), where

userID is the identification number that appears in the Security Administration tool.4. Paste the file onto the desktop of your computer.5. If you are accessing the Metasys system device remotely, log off.6. Access the destination Metasys system device (where you want to copy the preferences) with the

MetasysSysAgent user and navigate to the Preferences directory for the device as shown in Table 28.7. Paste the SystemPreferences.xml file or UserPreferences-userID.xml file that you copied to your computer

desktop with Step 4.

Restoring Default User Preferences1. Log on to the Metasys UI as the MetasysSysAgent user.2. On the Tools menu of the UI, select Administrator. The Security Administration tool appears.3. On the View menu, select User Preference File Names. The user preference file names appear in the Roles and

Users pane of the Security Administration tool.4. Record the file name of the user whose preferences you want to restore.

Note: If the user has been removed from the system, there is no record of the user preference file name in theSecurity Administration tool. In this case, remove user preference files from the Metasys device that donot have a corresponding user preference file name in the Security Administration tool.

5. Close the Security Administration tool and continue with Removing User Preference Files.

Removing User Preference Files1. Access the Metasys device from which you want to remove the user preference files and navigate to the

Preferences directory for the device as shown in Table 28.


2. Delete files named UserPreferences-userID.xml, where userID is the identification number that appears in theSecurity Administration tool.

Note: Do not delete DefaultUserPreferences.xml.

Copying User Preferences to Another User1. Log on to the Metasys UI as the MetasysSysAgent user.2. On the Tools menu of the UI, select Administrator. The Security Administration tool appears.3. On the View menu, select User Preference File Names. The user preference file names appear in the Roles and

Users pane of the Security Administration tool.4. Record the file name of the user whose preferences you want to copy (Source User) and the file name of the

user whom you want to share those preferences (Destination User).5. Close the Security Administration tool.6. Access the Metasys device and navigate to the Preferences directory for the device as shown in Table 28.7. Delete the preference file (if it exists) of the Destination User that you recorded in Step 4.8. Copy and paste the user preference file of the Source User you recorded in Step 4. If using Windows Explorer,

the file appears in the folder with Copy of appended to the front of the file name.9. Rename the copied file to the original name of the Destination User preference file name.

Preserving Preferences in an UpgradePreferences do not persist after an upgrade unless you take manual steps to save the settings before you begin asystem upgrade.

1. Before you begin the upgrade process, access the source Metasys system device that contains the preferencesyou want to copy. (For example, if this is an NAE55, use the Remote Desktop option available with NCT. Thelocal hard drive of your computer is automatically mapped to the NAE through remote desktop.)

2. Navigate to the Preferences directory for the device as shown in Table 28.3. Copy SystemPreferences.xml (system preference) or UserPreferences-userID.xml (user preference), where

userID is the identification number for each specific user with customized preferences. If you are saving preferencesfor multiple users, be sure to copy all files.

4. Paste these files in a safe location on your computer or network drive, or store them on other media.5. Upgrade your system according to the ADS, ADX, and SCT Installation and Upgrade Instructions Wizard

(LIT-12011521) and other appropriate documentation.6. Copy the files from the safe location in Step 4 back to the directory in Step 1.

Building Efficiency507 E. Michigan Street, Milwaukee, WI 53202

Metasys® and Johnson Controls® are registered trademarks of Johnson Controls, Inc.All other marks herein are the marks of their respective owners. © 2013 Johnson Controls, Inc.

www.johnsoncontrols.comPublished in U.S.A.


NAE

Documents

Transcript of NAE