Application Note

Issue Date January 4, 2010

Supersedes October 6, 2008

M-Series Workstation Interface to the NAE

M-Series Workstation Interface to the NAE ........................................2

Introduction......................................................................................................... 2

Key Concepts...................................................................................................... 4
Supported System Configurations .................................................................................... 4
NAE Configuration Considerations ................................................................................. 11
Operation of the M-Series Workstation with the NAE ..................................................... 13
Limitations of the M-Series Workstation Interface to the NAE ........................................ 16

Detailed Procedures......................................................................................... 23
Setting up the M-Series Workstation Interface to the NAE ............................................. 23
Configuring the NAE Device Object Alarms to Send Alarms to M-Alarm........................ 24

© 2010 Johnson Controls, Inc. www.johnsoncontrols.com

Code No. LIT-1201655 Software Release 5.3
2 M-Series Workstation Interface to the NAE Application Note

M-Series Workstation Interface

to the NAE

Introduction
The M-Series Workstation Interface to the Network Automation
Engine (NAE) provides the capability to monitor and write to NAE
devices from the M5 Workstation or the M3 Workstation. You may
use the M-Series Workstation interface to the NAE for applications
where existing N1 or N30 networks are expanded with NAE devices.
This interface also allows the building operator to monitor up to
five NAE devices from the M5 Workstation and browse through the
Building Automation System (BAS) that may consist of existing
Network Control Module (NCM) or N30 supervisory controllers and
NAE devices. However, NCM devices cannot communicate directly to
NAE devices, so you cannot share control sequences between NCM
and NAE devices.
This interface allows the building operator to monitor up to five NAE
devices from the M5 Workstation or M3 Workstation and browse
through the BAS, which may consist of existing N30 supervisory
controllers and NAE devices. However, we do not recommend that
you share control sequences between N30 and NAE devices.
The M-Series Workstation Interface to the NAE should be considered
the first phase of transitioning existing N1 and N30 networks to the
Metasys® system extended architecture. The final transition may
involve installing NAE devices to integrate N30 devices and installing
Network Integration Engine (NIE) devices to integrate NCM devices.
Refer to the N1 Migration with the NIE Technical Bulletin (LIT-
1201535) for information on migrating N1 points to Metasys system
extended architecture.
When the transition to Metasys system extended architecture is
complete, the user interface functions are transferred from the
M-Series Workstation to the User Interface of the Metasys system
extended architecture. However, during the transitional period, the
overall site operation is performed from the M5 Workstation or
M3 Workstation.
 M-Series Workstation Interface to the NAE Application Note 3

This document describes how to:

• set up the M-Series Workstation interface to the NAE
• configure the NAE device object alarms to send alarms to
M-Alarm
Note: Unless otherwise stated, the solutions presented in this
document for the M-Series Workstation apply to both the
M5 Workstation and the M3 Workstation.
Configuration and setup of the NAE must be performed using the Web
browser, either using the online User Interface (UI) or offline using the
System Configuration Tool (SCT). The UI and the SCT are only
supported for configuration in this interface. For more information on
configuring the NAE, refer to the Configuring the Network Automation
Engine (NAE) Technical Bulletin (LIT-1201519) or System
Configuration Tool Technical Bulletin (LIT-1201534).
Note: The M-Series Workstation Interface to the NAE does not
support an Application and Data Server (ADS).
Note: Many of the limitations described in this document do not
apply to the M3integral and M5i workstations available in Europe.
4 M-Series Workstation Interface to the NAE Application Note

Key Concepts
Supported System Configurations
This section describes the supported system configurations that allow
you to use the M-Series Workstation interface to NAE devices to
extend the following existing N1 or N30 networks.
• M5 Workstation communicating with NCM and N30 devices on an
Ethernet Local Area Network (LAN)
• M3 Workstation communicating with N30 devices on a LAN
• M5 Workstation or M3 Workstation communicating with N30
devices on an RS232 serial link direct connection
• M5 Workstation communicating with NCM and N30 devices on a
Dial-up network
• M5 Workstation or M3 Workstation communicating with N30
devices on a Dial-up network

M5 Workstation Communicating with NCM, N30, and NAE

Devices on a LAN
Figure 1 shows an example of an NAE that is added to an Ethernet
LAN as an addition to an already existing BAS consisting of NCM
devices, N30 devices, and an M5 Workstation. In this system:
• the M5 Workstation is used to monitor all connected NCM, N30,
and NAE devices and can view and override objects out of all
monitored devices.
• the NCM devices are engineered with the N1 network
configuration tools provided with Data Definition Language
(DDL), Graphic Programming Language (GPL), and the
Person-Machine Interface (PMI) software.
• the N30 device is engineered with the N30 network configuration
tools provided with M-Tools software.
• the NAE device is engineered with the NAE online UI or the
System Configuration Tool (SCT) software.
• not more than five total NAE devices can be interfaced to the
existing N1 and N30 network configuration.
• a maximum of 20,000 objects may be defined in the M-Series
Workstation referencing all defined N30, NAE, and third-party
BACnet® devices.
 M-Series Workstation Interface to the NAE Application Note 5

M5 Workstation

NCM

NAE

N30

Ethernet

ARCnet/Ethernet
Router
ARCnet (R) network

NCM

FIG :M5L
Figure 1: M5 Workstation communicating with NCM, N30, and NAE Devices on a
LAN
For this configuration to work, the M5 Workstation must reside on the
Ethernet LAN. The M5 Workstation cannot communicate with the
NAE if:
• the M5 is directly connected to the NCM, or if
• the M5 Workstation is connected to the NCM by dial-up interface.
6 M-Series Workstation Interface to the NAE Application Note

M5 Workstation or M3 Workstation Communicating with

N30 and NAE devices on an Ethernet LAN
Figure 2 shows an example of an NAE that is added to an Ethernet
LAN as an addition to an already existing BAS consisting of N30
devices and an M3 Workstation. In this system:
• the M3 Workstation is used to monitor all connected N30 and
NAE devices and can view and override objects out of all
monitored devices
• the N30 device is engineered with the N30 network configuration
tools provided with M-Tools software
• the NAE device is engineered with the NAE online UI or the SCT
software
• not more than five total NAE devices can be interfaced to the
existing N1 and N30 network configuration
• a maximum of 20,000 objects may be defined in the M-Series
Workstation referencing all defined N30s, NAEs, and third-party
BACnet devices
M3 Workstation

NAE

N30
N30

Ethernet

FI G:M3L

Figure 2: M3 Workstation Communicating with N30 and NAE Devices on a LAN

 M-Series Workstation Interface to the NAE Application Note 7

M5 Workstation or M3 Workstation Communicating with

N30 and NAE Devices Using a Serial Connection
Figure 3 shows an NAE that is added to an N30 network as an addition
to an already existing BAS consisting of N30 devices and an
M5 Workstation or M3 Workstation connected to one of the N30
devices using an RS232 serial connection. In this system:
• the M5 Workstation or M3 Workstation is used to monitor all
connected N30 and NAE devices and can view and override
objects out of all monitored devices
• the N30 device is engineered with the N30 network configuration
tools provided with M-Tools software.
• the NAE device is engineered with the User Interface (UI) or the
System Configuration Tool (SCT) software.
• not more than five total NAE devices can be added to the existing
N1 and N30 network configuration.
• a maximum of 20,000 objects may be defined in the M-Series
Workstation referencing all defined N30s, NAEs, and third-party
BACnet devices.
M5 Workstation
Using Direct
Communication

N30

Ethernet

NAE
N30
FIG:M 5N30dir

Figure 3: M5 Workstation Directly Connected to an N30

8 M-Series Workstation Interface to the NAE Application Note

M5 Workstation or M3 Workstation Communicating with

N30 and NAE Devices Using a Dial-up Connection
Figure 4 shows an NAE that is added to an N30 network as an addition
to an already existing BAS consisting of N30 devices and an
M5 Workstation or M3 Workstation connected to one of the N30
devices using a dial-up connection. In this system:
• the M5 Workstation or M3 Workstation is used to dial in to an N30
to monitor all connected N30 and NAE devices, and can view and
override objects out of all monitored devices
• the N30 devices are engineered with the N30 network
configuration tools provided with M-Tools software
• the NAE device is engineered with the NAE online UI or the SCT
• not more than five total NAE devices can be added to the existing
N30 network configuration
• a maximum of 20,000 objects may be defined in the M-Series
Workstation referencing all defined N30s, NAEs, and third-party
BACnet devices
• the N30 acts as a modem host for the NAEs. The N30 accepts
dial-in calls from the M5 Workstation or M3 Workstation for
monitoring the connected N30 and NAE devices. The N30 that
acts as the modem host can initiate Remote Destination Object
(RDO) dial-out calls based on the occurrence of alarms in the N30
and NAE devices on the system
 M-Series Workstation Interface to the NAE Application Note 9

N30
M5 Workstation
Using Dial-up
Communication

Ethernet

NAE
N30

FIG:M 5N30dl
Dial-up Network

Figure 4: M5 Workstation Communicating with N30 and NAE Devices Using

a Dial-up Connection

M5 Workstation Communicating with NCM, N30, and NAE

Devices Using a Dial-up Connection
Figure 5 shows an NAE that is added to an N30 site on an already
existing BAS. The BAS in the example also consists of NCM devices
on a remote site and N30 and NAE devices on another remote site. The
remote sites communicate with the M5 Workstation using dial-up
connections. In this system:
• the M5 Workstation is used to monitor all NCM, N30, and NAE
devices accessible through the available dial-up connections, and
can view and override data in monitored devices
• the NCM devices are engineered with the N1 network
configuration tools provided with DDL, GPL, and PMI software
• the N30 devices are engineered with the N30 network
configuration tools provided with M-Tools software
• the NAE device is engineered with the NAE online UI or the SCT
• no more than five total NAE devices can be added to the whole
system
• a maximum of 20,000 objects may be defined in the M-Series
Workstation referencing all defined N30s, NAEs, and third-party
BACnet devices
10 M-Series Workstation Interface to the NAE Application Note

• the N30 acts as a modem host for the NAE. The N30 accepts
dial-in calls from the M5 Workstation or M3 Workstation for
monitoring the connected N30 and NAE devices. The N30 that
acts as the modem host can initiate Remote Destination Object
(RDO) dial-out calls based on the occurrence of alarms in the N30
and NAE devices on the system.
Note: The Remote sites in this configuration cannot communicate
with each other.

N30
NCM

Remote Site

Remote Site

Example of a
single NAE
at the remote
N30 site
M5 Workstation
Using Dial-Up
Communication

Ethernet

NAE
FIG:M5dl

Remote Site

Figure 5: M5 Workstation Communicating with NCM, N30, and NAE Devices Using
a Dial-up Connection
 M-Series Workstation Interface to the NAE Application Note 11

NAE Configuration Considerations

To allow the M-Series Workstation to interface to NAE devices, you
must follow specific guidelines when configuring the NAE.
All NAE objects that are exposed as BACnet standard objects can be
accessed from the M-Series Workstation through the M3 Workstation
software or with M5 Workstation software.
The NAE BACnet Integration feature (for integrating third-party
BACnet controllers into the NAE) is not supported for this application.
The NAE BACnet Integration object, including BACnet objects that
are integrated into the NAE, are not accessible by the M-Series
Workstation. You can integrate third-party BACnet controllers directly
into the M-Series Workstation.
For information on configuring the NAE, refer to the Configuring the
Network Automation Engine (NAE) Technical Bulletin (LIT-1201519).
Configure the NAE with the following considerations.
• Use American Standard Code for Information Interchange (ASCII)
text strings for BACnet Encoding Type in the Site object.
• Make the NAE Item Reference as short as possible, since the NAE
Item Reference is used as the basis for building up the BACnet
OLE for Process Controls (BN OPC) tag name in the M-Series
Workstation. To make all M-Series Workstation applications work,
the complete BN OPC tag name (object name plus attribute name)
cannot be more than 256 characters. However, M-Trend truncates
a BN OPC tag name to 64 characters.
For defining the maximum length of the NAE all Item Reference,
you need to consider that the BN OPC Server adds the BN OPC
server name, the BACnet site name, and the BACnet object
attribute name to the NAE BACnet Object name for building up
the BN OPC tag name. The NAE BACnet object name is derived
from the NAE all Item Reference, minus the NAE Site Reference.
• Set the BACnet Intrinsic Alarming Defined attribute to True. Also,
set up Event Enrollment Alarming, including BACnet event
notification (Notification Class objects), in the NAE for all NAE
engines that should report event messages to M-Alarm. See Setting
up the M-Series Workstation Interface to the NAE in this
document.
• Do not set up a Domain Name for the NAE Device Object. Setting
up a Domain Name causes name changes for every NAE point
object, making them unavailable to the M-Series Workstation.
12 M-Series Workstation Interface to the NAE Application Note

• Use only supported enumeration sets or the data will not be

displayed correctly. For the list of enumeration sets, refer to the Set
tables in the Metasys system extended architecture Help. For the
list of unsupported enumeration sets, see the Limitations of the
M-Series Workstation Interface to the NAE section in this
document.
The safest alternative is to use the States set in the NAE for the
attributes that need enumerations.
• The Generic Integration Object (GIO) is not a BACnet standard
object. Do not use the GIO for NAE objects interfaced by the
M-Series Workstation. Use standard analog and binary NAE
objects for interfacing points from the NAE to the M-Series
Workstation.
• NAE device object alarms (Battery Condition, CPU Usage, Flash
Usage, Memory Usage, CPU Temperature, and Board
Temperature) are not sent to M-Alarm through the Notification
Class Object (NCO). To have these alarms appear in M-Alarm,
you must configure an Event Enrollment Object (EEO) for each
object alarm to send the alarm to M-Alarm. See Configuring the
NAE Device Object Alarms to Send Alarms to M-Alarm in this
document.
• The user authorizations defined in the NAE Security System do not
pertain to the point objects when interfaced to the M-Series
Workstation. The M-Series Workstation continues to use
M-Password to restrict user access.
• If more than one NAE device is interfaced to the M5 Workstation
or M3 Workstation, and if these interfaced NAE devices need to
exchange information between each other, the NAE devices need
to be set up as a Metasys system extended architecture site, with
one NAE being defined as the Site Director. Although the product
literature of the Metasys system extended architecture points out
that an NAE can be the Site Director for only up to three other
NAE devices. For the M-Series interface to the NAE, the
NAE-based Site Director function can be extended to be the Site
Director for up to four other NAE devices, assuming that most
user interface functions are performed by the M-Series
Workstation.
 M-Series Workstation Interface to the NAE Application Note 13

Table 1 details the versions of the NAE that the M-Series Workstation
can interface.
Table 1: Supported NAE Models and Firmware Revisions
Order Codes Product Description Firmware Version
MS-NAE5510-0 Metasys NAE with two N2 Buses Release 1.0 or later
MS-NAE5511-0
MS-NAE5520-0 Metasys NAE with two N2 Buses Release 1.1 or later
MS-NAE5521-0 and one LONWORKS® bus

Operation of the M-Series Workstation with the NAE

The hardware and software requirements for the M-Series Workstation
Interface to the NAE do not change from the minimum supported
computer platform for the M5 Workstation or M3 Workstation. For
details, refer to the Metasys Software Installation and Platform
Requirements Technical Bulletin (LIT-12012).

Viewing NAE Devices

When properly configured, an NAE device appears on M-Series
workstation applications as a BACnet device and can be explored just
like N30s on an N30 site or NCMs on an N1 network. Figure 6 shows
an NAE device interfaced to an M-Series Workstation as displayed by
M-Explorer.

Figure 6: M-Explorer Showing Objects Interfaced from an NAE

14 M-Series Workstation Interface to the NAE Application Note

M-Series Workstation Software Components Support

Table 2 lists the M-Series Workstation software components supported
for the M-Series Workstation Interface to the NAE.

Table 2: M-Series Workstation Component

Software Component Function Supported
Component Revision
BN OPC Server* Accesses NAE devices and NAE objects that are BACnet compliant. 5.3
M-Password Restricts user access to NAE objects. 5.3
M-Alarm** Manages and acknowledges NAE event messages received through 5.3
the NAE Notification Class Object.
M-Explorer/ Explores and views BACnet compliant NAE objects. 5.3
M-Inspector
M-Command Not all objects accept commands issued from the M-Series
Workstation. We recommend that you do not issue commands to the
NAE from the M-Series Workstation. Instead, you can use M-View or
M-Graphics to override points.
M-View Overrides objects in the NAE.
M-Schedule Views NAE Schedule Objects. You cannot add or change NAE
Schedule Objects.
M-Calendar Views NAE calendar objects. You cannot add or edit NAE calendar
objects.
M-Collector Collects trend data from BACnet compliant NAE objects. Reads the 5.3
trend buffers out of the supported NAE Objects.
Access Historian Archives trend data from BACnet compliant NAE objects. 5.3
SQL Historian Archives trend data from BACnet compliant NAE objects. 5.3
M-Trend Displays archived trend data from BACnet compliant NAE objects. 5.3
M-Graphics Views and overrides BACnet compliant NAE objects. 5.3
MMX Manages NAE event messages received via NAE Notification Class 5.3
Object and the BN OPC Alarm and Event server.
MDV Visualizes data from BACnet compliant NAE objects. 5.3
MHDV Visualize historical data from BACnet compliant NAE objects. 5.3
* Refer to Table 3 for a complete list of supported NAE objects.
** Configure the NAE for supporting BACnet Alarm Notification (using the Notification Class object). Refer
to Setting Up the M-Series Workstation Interface to the NAE in this document.
 M-Series Workstation Interface to the NAE Application Note 15

Supported NAE Objects

The M-Series Workstation Interface to the NAE supports access to the
NAE objects listed in Table 3.
IMPORTANT: You can configure each object in the NAE to use BACnet
Intrinsic Alarming at the time you insert it. The attribute that controls this
feature can also be configured after the object is inserted. When inserting
objects in the NAE, be sure to set the Intrinsic Alarming Defined attribute to
True.

Table 3: Supported NAE Objects

NAE Object
Analog Value (AV) Binary Output*
Binary Value (BV) Multistate Input*
Event Enrollment (EEO) Multistate Output*
Interlock Notification Class
Multiple Command Pulse Meter object
Analog Input* Trend Log object extension**
Analog Output* Totalization object extension**
Binary Input*
* With N2 or LONWORKS Hardware Tab (points can be interfaced from N2
devices as well as LonWorks devices).
** Object extensions appear as a separate object within M-Explorer

Objects from the following devices are not available to the

M5 Workstation or M3 Workstation using the M-Series Workstation
interface to the NAE.
• Network Integration Engine (NIE)
• Application and Data Server (ADS)
• Application and Data Extended Server (ADX)
Note: The NAE GIO cannot be interfaced by the M-Series
Workstation.
In cases where references are made to non M-Series objects, you are
not able to interrogate those objects from the M-Series Workstation.

Commanding NAE Objects from the M5 Workstation or

M3 Workstation
We recommend not using commands from the M-Series Workstation.
You may want to use object overrides when system operation requires
you to interact with an NAE object from the M-Series Workstation.
See the Limitations of the M-Series Workstation Interface to the NAE
section of this document for details.
16 M-Series Workstation Interface to the NAE Application Note

NAE Object Attributes

For NAE object attribute descriptions, please refer to the Metasys
system extended architecture Help.

Limitations of the M-Series Workstation Interface to the NAE

This section describes the Metasys applications that have not been
tested and are not supported with the M-Series Workstation Interface
to the NAE. Table 4 lists the applications that are not supported.

Table 4: Unsupported Metasys Applications

Application
Fire Operator Workstation
(Fire OWS)
Metasys Person-Machine Interface
(PMI) only
BACnet System Integrator (BSI)
Metasys Web Access (MWA)
Metasys system for Validated
Environments (MVE)
Metasys Connectivity to LONWORKS
(MCL) Tools
M3 Workstation Connectivity to
LONWORKS (MCL) Workstation
Component
M-Tools
Description
This application is used only for N1
networks.
This application is used only for N1
networks.
This application is used only for N1
networks.
This application is not supported. If a
Web server is required, we recommend
transferring the user interface from
M-Series Workstation to the UI of the
Metasys system extended architecture.
This application is used only for N1
networks.
This application has not been tested.
This application has not been tested.
This application set is used only to
configure N30 Supervisory Controllers
and N2 Field Controllers.

A number of M-Series Workstation software component features

cannot be applied and are not supported for the M-Series Workstation
Interface to the NAE. The following section describes these
limitations.

Date and Time Synchronization

The M-Series Workstation cannot change the date or time in the NAE
device. To change the date and time in the NAE, you need access the
Site Director of the interfaced NAE using a Web browser. For
information regarding NAE time synchronization or setting the date
and time in the NAE, refer to the Configuring the Network Automation
Engine (NAE) Technical Bulletin (LIT-1201519) or to the Metasys
system extended architecture Help.
 M-Series Workstation Interface to the NAE Application Note 17

Time synchronization with the M-Series Workstation varies depending

on the networks and systems connected.
• M5 Workstations or M3 Workstations can synchronize the date
and time for all connected N30 devices.
• M5 Workstations can synchronize date and time of all connected
NCM devices with the computer’s operating system using PMI.

Unsupported Enumeration Sets

Enumeration Sets, also known as Enum Sets or just Sets, are used to
communicate the NAE object attribute values to any type of user
interface including the M-Series Workstation, a third-party BACnet
workstation, or to another controller (such as the N30).
This section lists the Enumeration Sets that are not supported by the
M-Series Workstation Interface to the NAE. If you select Enumeration
Sets that are not supported, the respective NAE object attribute value
is not displayed correctly for all OPC clients. For example, if the NAE
AV object attribute the Enumeration Set Winter Summer (which is not
supported by this interface) is used, the M-Series Workstation software
components cannot correctly display the respective NAE object
attribute values on the M5 Workstation or M3 Workstation.
• In M-Explorer, Winter Summer is not shown.
• In M-Inspector, Winter Summer appears as three question marks
(???).
Table 5 and Table 6 list NAE supported enumeration sets that cannot
be used and displayed with M-Series Workstation software
components. When configuring NAE objects for use with the M-Series
Workstation Interface to the NAE, avoid using the enumeration sets
shown in the following two tables.
Table 5 lists the multistate enumeration sets that are not supported for
NAE objects.
Table 5: Unsupported Multistate Enumeration Sets for Multistate
Input/Output/Value Objects
Enumeration Set Enumeration Set
SNVT HVAC Emergency SNVT Override
SNVT HVAC Mode SNVT Evaporation State
SNVT HVAC Override SNVT Thermostat Mode
Chart Style SNVT Defrost Mode
Aggregate Function SNVT Defrost Termination
SNVT Day of Week SNVT Defrost State
SNVT Discrete Level SNVT Fire Initiator
SNVT Telcom States SNVT Fire Indicator
SNVT Secure SNVT HVAC Equipment Type
18 M-Series Workstation Interface to the NAE Application Note

Table 6 lists the enumeration sets that are not supported for NAE
objects.

Table 6: Unsupported Two State Enumeration Sets for Binary Input/Output/Value Objects
Enumeration Set Enumeration Set Enumeration Set
Present Absent Replace Normal Off Auto
Manual Auto Reverse Normal Auto Off
Dirty Clean Online Offline Off Reset
Minimum Closed Fault OK Reset Off
Valve Damper Fast Slow Disable Man
Reverse Direct Run StandBy Man Disable
Enable Disable Run Stop ShutdownClosed ShutdownOpen
True False Start Stop ShutdownOpen ShutdownClosed
Reverse Forward Winter Summer Local External
Lead Lag Occ Unocc Access Secure
Remote Local Low Normal Counterclockwise Clockwise
High Low Normal Low Secure Access
Disable Normal Set Reset External Local
Reset NA Reset Set Flow NoFlow
Yes No Mechanical Free
Alarm Normal Free Mechanical

Commands Not Supported

IMPORTANT: Not all objects accept commands issued from the M-Series
Workstation. We recommend that you do not issue commands to the NAE
from the M-Series Workstation.

We recommend that you do not issue commands to the NAE from the
M-Series Workstation. The M-Inspector screen may show commands
available to send to the NAE, but some are invalid and do not work.
An invalid command error appears (Figure 7) on the screen when an
invalid command is sent to the NAE.
 M-Series Workstation Interface to the NAE Application Note 19

Figure 7: Command Error

As an alternative to issuing commands from M-Inspector or
M-Graphics, you can override NAE attributes using M-View or
M-Graphics.

Viewing Data
The Heavy Equip Delay (HED) controller attribute in the Binary
Output (BO) object is invalid.
The HED works correctly in the NAE, but when interfacing with an
M-Series Workstation, the HED:
• does not show a value in M-Explorer or M-Inspector. It does show
correctly in M-Graphics.
• cannot be changed in M-Inspector or M-Graphics
20 M-Series Workstation Interface to the NAE Application Note

Scheduling
Access to NAE Schedule objects and Calendar objects is limited. You
can view Schedule and Calendar objects, but you cannot add or edit
the objects.
For NAE Schedules that are running at NAE Release 1.0 or 1.1, you
cannot access the following NAE Schedule object attributes with
M-Schedule.
• List of Object Property References
• Exception Schedule

Unsupported Object Attributes

Table 7 lists the supported objects in the M-Series interface to the
NAE and the attributes that are unsupported for each object.
For descriptions of NAE object attributes, please refer to the Metasys
system extended architecture Help.
 M-Series Workstation Interface to the NAE Application Note 21

Table 7: Unsupported Object Attributes

NAE Object Unsupported Attributes
Analog Value (AV) Object Identifier (C), Max Value, Min Value, Min Pres Value, Max Present Value
Binary Value (BV) Object Identifier (C), Alarm Value (C), Change of State Time (W), Event Enable
(C), Feedback Value, Minimum Off Time, Minimum On Time (C), Notification
Class (C), Notify Type (C), Relinquish Default (C), Time of Active Reset (W),
Intrinsic Alarming (C), States Text (C)
Event Enrollment (EEO) Event Enable (C), Event Parameters (C)(W)(W)***, Event Type (C), Notify Type
(C), Object Identifier (C), Object Property Ref, Notification Class (C)
Interlock Action Table 2 (False) (C), Action Table 1 (True) (C), Commands Priority (C),
Logic (C), Logic Equation (C), Source (C), States Text (C)
Multiple Command Action Table (C), Commands Priority (C), Number of States (C), Relinquish
Default (C), States Text (C)
Analog Input* Event Enable (C), High Limit (C), Limit Enable (C), Low Limit (C), Max Pres Value
(C), Min Pres Value (C), Notification Class (C), Notify Type (C), Resolution (W),
Time Delay (C), Display Precision (C)
Analog Output* Object Identifier (C), Device Type (C), Event Enable (C), High Limit (C), Limit
Enable (C), Low Limit (C), Max Pres Value (C), Min Pres Value (C), Notification
Class (C), Notify Type (C), Resolution (W), Time Delay (C), Auto Restore (C),
Display Precision (C), Intrinsic Alarming (C), Max Value, Min Value, Net N2
Address (C), Net Point Address (C), Net Point Type (C)
Binary Input* Change of State Time (W), Device Type (C), Event Enable (C), Notification Class
(C), Notify Type (C), Time Delay (C), Time of Active Time Reset (W), Time of
State Count Reset (W), Intrinsic Alarming (C), Net N2 Address (C), Net Point
Address (C), Net Point Type (C), States Text (C)
Binary Output* Object Identifier (C), Active Text (W), Change of State Time (W), Device Type (C),
Event Enable (C), Feedback Value (C), Minimum Off Time (C), Minimum On Time
(C), Notification Class (C), Notify Type (C), Relinquish Default (C), Time Delay
(C), Time of Active Time Reset (W), time of State Count Reset (W)
Multistate Input* Number of States (C), Object Identifier (C), Alarm Values (C), Event Enable (C),
Fault Values (C), Notification Class (C), Notify Type (C), Time Delay (C), Intrinsic
Alarming (C), Net N2 Address (C), Net Point Type (C), States Text (C)
Multistate Output* Number of States (C), Object Identifier (C), Relinquish Default (C), Device Type
(C), Event Enable (C), Feedback Value (C), Notification Class (C), Notify Type
(C), Time Delay (C), Auto Restore (C), Heavy Equip Delay (C), HED Controller
(C) (W), Intrinsic Alarming (C), Net Point Address (C), Net Pint Type (C), States
Text (C)
Notification Class Ack Required (C), Notification Class (C), Object Identifier (C), Priority (C),
Recipient List (C), Commands Priority (C)
Pulse Meter object Consumption Units (C), Counter Object (C), Display Precision (C), Meter Active
(C), Pulse Consumption (C), Rate Constant (C), Rate Default (C), Rate Limit (C),
Rate Units (C), Rollover Limit (C), Sample Time (C)
Trend Log Object Buffer Size (C), Object Identifier (C), Record Count (C), Stop When Full, COV
Extension** Resubscription Interval, Current Notify Time, Log Device Object Property, Log
Interval, Notification Threshold, Previous Notify Time, Records Since Notification,
Execution Trigger, Input Reference
Totalization Object Display Precision (C), Input Reference (C), Scalefactor
Extension**
* With N2 or LONWORKS Hardware Tab
** Object extensions appear as an object within M-Explorer.
*** Both the N30 Writable Flag and the M-Series Writable Flag are unsupported.
(C) Configurable Flag
(W) Writable Flag
22 M-Series Workstation Interface to the NAE Application Note

Product Line Compatibility

The M-Series Workstation interface to the NAE has not been tested
with the ADS/ADX server. If the M-Series Workstation and the ADS
are both connected to the NAE, it will have two uncoordinated user
interfaces that may cause conflicts for a normal system operation. You
should only connect the ADS/ADX during the transitional period
when the existing Metasys system is being migrated to the
Metasys system extended architecture.
 M-Series Workstation Interface to the NAE Application Note 23

Detailed Procedures
Setting up the M-Series Workstation Interface to the NAE
To set up the M-Series Workstation interface to the NAE:
1. Read the following flow chart (Figure 8) to determine which
objects you need to add in which devices.

Configure the NAE using the guidelines

described in this document.

Insert Notification Class Object in the NAE.

Is the NAE
No connected to an N30 Yes
Dial-up Network?

Configure the Notification Configure the Notification

Class object to route alarms Class object to route alarms
to the M-Series Workstation. to the N30.

Insert a Remote Destination

object into the N30 that
performs the dialing.

Configure the Remote

Destination Object to route
alarms to the M-Series
Workstation.

Run Site Book.

Figure 8: Flow Chart for Configuring the NAE to Send Event Messages
to the M-Series Workstation
2. Configure the NAE Notification Class Object according to Table 8.
24 M-Series Workstation Interface to the NAE Application Note

Note: Table 8 describes the fields that you must complete to

properly configure the Notification Class object Recipient List in the
NAE to route alarms to the M-Series workstation. In both dial-up
networks and non dial-up networks, you must choose to route alarms
by Address.

Table 8: Configuring the Notification Class Object Recipient List

Attribute No Dial-up Dial-up
Address Choose Address to route alarms to an address.
IP Address Enter the Internet Protocol (IP) address Enter the IP address of the N30.
of the M-Series Workstation.
Network Number Enter the Network Number of the Enter the Network Number of the N30.
M-Series Workstation.
UDP Port Enter the UDP Port of the M-Series Enter the UDP Port of the N30.
Workstation.
Process ID Enter the Process ID of the M-Series Enter the Process ID of the N30.
Workstation.
When Specify the times that you want alarms to be routed to the address.
Notification on these Specify the types of transitions Notifications that should be sent to the address.
transitions
Notification Messages Specify if Notification Messages should be sent as Confirmed or Unconfirmed.
should be

3. If necessary (according to Figure 8), insert and configure the

Remote Destination Object (RDO) in the N30 to route alarms to
the M-Series Workstation.
4. Run Site Book on the M5 Workstation or M3 Workstation to
discover the NEA devices on the network.
Note: To view an NAE from the M-Series Workstation, run Site
Book. Once Site Book locates the NAE device, you can browse the
NAE objects from the M-Series Workstation. For more information
regarding Site Book, refer to the Site Book User’s Guide
(LIT-6893100).

Configuring the NAE Device Object Alarms to Send Alarms to

M-Alarm
Note: The NAE device object alarms are Battery Condition, CPU
Usage, Flash Usage, Memory Usage, CPU Temperature, and Board
Temperature. Perform this procedure only if your facility requires
M-Alarm to receive NAE object alarms.
 M-Series Workstation Interface to the NAE Application Note 25

To configure the NAE device object alarms to send alarms to

M-Alarm:
1. Create an Event Enrollment Object (EEO) in the NAE.
Note: This procedure defines the minimum configuration necessary
for the M-Series Interface to the NAE. For more information on
objects, refer to the Metasys system extended architecture Help.
2. Configure the EEO according to Table 9.

Table 9: NAE Object EEO Alarm Settings

Analog Alarm* Digital Alarm
(Battery Condition)
On the Configuration Tab
Name Type a name for the EEO (for example “EEO for CPU Use”).
Description Type a short description for the EEO (for example “EEO to send CPU Usage
alarm to M-Alarm”).
Notification Class Set to the same number as the NCO.
Alarm Message Text Type the message that you want to appear in M-Alarm (for example “CPU is
too busy for normal operation”).
On the Event Tab
Input Reference Select the NAE Object and then Select the NAE Object and then
Select an Analog Alarm*. Select Battery Condition.
Event Type Select Out of Range. Select Change of State.
Add Fault as the Value and place a
check in the box.
* The five Analog Alarms include CPU Usage, Flash Usage, Memory Usage, CPU Temperature, and
Board Temperature

3. Set all of the other fields (including Low Limit, High Limit, and
Deadband for analog alarms) according to your needs.
4. Repeat Steps 1 through 3 to add and configure an EEO for each
NAE device object alarm you need.

Building Efficiency
507 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. © 2010 Johnson Controls, Inc.