N2 Integration With The NAE Technical Bulletin: N2 Device Point Mapping Tables

N2 Integration with the NAE Technical Bulletin
Code No. LIT-1201683

Issued December 5, 2014
Refer to the QuickLIT website for the most up-to-date version of this document.
Document Introduction.............................................................................................................2
Switchable Communications Protocols...........................................................................................2
Related Documentation.............................................................................................................2
N2 Integration with the NAE Overview.....................................................................................3
N2 Device Point Mapping Tables Overview.............................................................................3
Supported Application Specific Controllers (ASCs)..............................................................4
Detailed Procedures..................................................................................................................5
Adding N2 Integrations.......................................................................................................................5
Adding N2 Field Devices Manually (Online or Offline)....................................................................7
Adding N2 Field Devices Online Using Auto Discovery...............................................................11
Adding Extensions to an Object......................................................................................................13
Adding a Resource File Extension......................................................................................................16
Adding a Trend Extension...................................................................................................................17
Adding a Totalization Extension..........................................................................................................18
Adding an Alarm Extension.................................................................................................................19
Adding an Averaging Extension..........................................................................................................20
Deleting Extensions from an Object...............................................................................................21
Copying Extensions to a Field Device or Field Point (Offline Only)............................................22
Adding N2 Field Points to an Archive Database............................................................................23
Adding Field Points Using Assisted Mode Definition...................................................................25
Adding Field Points Using Manual Mode Definition......................................................................28
N2 FEC, FAC, and VMA Point Limits......................................................................................33
N2 Device Point Mapping Tables............................................................................................34
AHU....................................................................................................................................................34
Unitary (UNT).....................................................................................................................................35
VAV Controller...................................................................................................................................35
VMA 1400 Series...............................................................................................................................35
Phoenix Fume Hood (PHX)..............................................................................................................36
Metasys Integrator Unit....................................................................................................................36
Vendor Device (VND)........................................................................................................................37
ILC......................................................................................................................................................37
Intelligent Fire Controller (IFC)........................................................................................................37
TC-9100 Terminal Unit Controller....................................................................................................38
Lab and Central Plant Controller/Digital Controller (LCP/DC9100)..............................................41
DX-9100 Extended Digital Controller..............................................................................................47
Extension Module (XTM and XT).....................................................................................................79
TEC1100.............................................................................................................................................83
TEC210x.............................................................................................................................................84
N2 Integration with the NAE Technical Bulletin 1

Document Introduction
This document describes how to integrate an N2 network in the Metasys® system with the Network Automation
Engine (NAE). This document also describes how to add field devices using an archive database or Discovery, add
N2 field points, and create extensions to an object. The N2 device point mapping tables allow you to manually map
points into the NAE using the System Configuration Tool (SCT). This document lists the devices and points that you
can manually map into the NAE, but does not include information on installing, configuring, or updating an NAE.
This document also contains point mapping limitations for newer model Advanced Application Field Equipment
Controllers (FACs), Field Equipment Controllers (FECs), and VAV Modular Assemblies (VMAs). At CCT 10.1, these
devices can be switched between the N2 and MS/TP communications protocols. When determining the number of
points that may be mapped from a newer controller that is being used as an N2 device, it is important to look at the
point limitations of the new device as well as the point limitations of the device which you are mapping it as (for
example, when defining a VMA16xx as a UNT in the mapping table). In all cases, the point limit is the smaller of
what you find in the two tables.
Switchable Communications Protocols

Release 10.1 of CCT can be used to switch the Field Bus communications protocol in FEC Field Controllers to be
either the standard BACnet® Master-Slave/Token-Passing (MS/TP) or the N2 protocol. BACnet MS/TP is the default
communications protocol for all new controllers. Switchable communications protocols provide a cost-effective
upgrade and modernization path for customers with existing N2 controllers. The Modernization Guide for Legacy
N2 Controllers (LIT-12012005) and the controller-specific documentation provide installation and commissioning
support and include tips for efficient and safe replacement. Refer to the N2 Compatibility Options chapter of the
Controller Tool Help (LIT-12011147) for information about mapping N2 Objects in controllers with switchable
communications protocols.
The N2 capable FEC controllers can be used as functional replacements for legacy N2 controllers. The N2 capable
FEC controllers:
• have the I/O quantities and characteristics of the FEC family controllers
• must be programmed with CCT, which has similar, but not identical programming capabilities as HVACPro,
GX9100, GPL, and other legacy tools
• support SA Bus devices
• support WRZ wireless sensors from the controller using the WRZ-7860 receiver
• are available in Buy American and panelized versions (most models)
• support backup schedules in the event of loss of network connection (Advanced Application Field Equipment
Controller [FAC] Series models)
The N2 capable FEC controllers:

• do not support Zone Bus (for example, TMZ sensors and M100 actuators) or XT-Bus (System 91) devices (for
example, XT, XTM, and XP modules)
• do not support a wireless connection to the N2 bus
• do not support NxE passthru
• are not listed for UL864 UUKL. N2 is not supported as part of the Metasys 9th Edition listing for Smoke Control
System Equipment
Related Documentation
Table 1: N2 Device Point Mapping Tables Related Documentation
For Information On See Document
Mapping Points Metasys® SCT Help (LIT-12011964)
Programming the Intelligent Lighting Controller Lighting Control Objects Technical Bulletin (LIT-636105)
(ILC)

Table 1: N2 Device Point Mapping Tables Related Documentation
For Information On See Document
Programming the Intelligent Fire Controller (IFC) IFC-1010/2020 Programming Technical Bulletin
(LIT-448060)
Mapping to programmable function module items Appendix C of the DX-9100 Configuration Guide
(PMK, PMO, PMA) (LIT-6364030)
Configuring the NAE NAE Commissioning Guide (LIT-1201519)
Installing the NAE/NIE NAE55/NIE55 Installation Instructions (Part No.
24-10051-43)
Technology and general rules for replacing legacy Modernization Guide for Legacy N2 Controllers
N2 controllers with N2 capable FEC controllers (LIT-12012005)
N2 Integration with the NAE Overview

For a Metasys network with N2 integration, note the following:
• Devices connected to N30s appear as native N30 objects and when the N30 connects to an NAE, all objects
and devices appear as native NAE objects and devices.
• N2 integration supports Metasys Integrator® units.
• Metasys system/N2 integration supports Pass through downloading to Application Specific Controllers (ASCs)
using the XTM Configurator, HVAC PRO software, N2 Loader user interface (UI), and GX-9100 tool software.
Refer to the Passthrough section in the Metasys SCT Help (LIT-12011964).
• Metasys system/N2 integration stores configuration information for N2 devices separate from the object and
device definitions in the NAE. The data is stored in the archive database in the SCT if the NAE is offline or in the
NAE archive database if the NAE is online.
• Practical performance is defined in project design.
• The NAE35 has a hard limit of a maximum of 50 devices on the N2 trunk.
• The NAE45 and NAE55 have a suggested maximum of 100 devices on the N2 trunk.
• The NCE25 has a hard limit of a maximum of 32 devices on the N2 trunk.
Note: The N2 Pulse Counter object is called the Accumulator object.
The Insert Field Device and Insert Point wizards guide you through the process of discovering controllers, and
importing and mapping N2 points. When you are online with an NAE through the Site Management Portal UI, not
through the SCT, the Insert Field Device wizard can use Auto Discovery to discover controllers connected to each
N2 trunk. With Auto Discovery, manual entry of controller addresses and controller types is unnecessary. You can
then map field points within each controller using N2 controller configuration files or manual point definition. The
database created at the NAE using Auto Discovery can then be uploaded to an archive database in the SCT for
storing or editing.
If two controllers on an N2 trunk have the same address, the controller should display with a status of Duplicate
Address. However, auto discovery cannot identify all duplicates, depending on timing and the type of devices. It is
possible that one or both of the duplicate controllers do not appear in the list of discovered controllers. If a controller
is not shown at an expected address, multiple controllers may exist with the same address.
Important: BD, ADF and ADI points addressed from 1 - 64 are Read-Write for device types of AHU, UNT and
VAV. The VND device type allows Read-Write for addresses 1 - 255.
N2 Device Point Mapping Tables Overview

The point mapping tables indicate:
• which controller points you can map to the NAE
• if the NAE can command (or override) the controller points (whether they are read only or read/write)

• whether the points support override status
• the NAE point types the controller points map to
Table 2 lists the point type abbreviations.
Table 2: Point Type Abbreviations
Abbreviation Definition
AI Analog Input
BI Binary Input
AO Analog Output
BO Binary Output
ADF Analog Data Float
ADI Analog Data Integer
BD Binary (byte) Data
LRS Logic Results
PMK Programmable Module Constants (written to Electrically-Erasable Programmable Read-Only
Memory [EEPROM])
PMO Programmable Module Outputs
PML Programmable Module Logic
PMA Programmable Module Accumulator
Supported Application Specific Controllers (ASCs)

With the exception of the N2 Dialer, the NAE supports all current N2 devices including Metasys system (AS), Facilitator
(FA) models, and the VAV Modular Assembly (VMA) 1400 Series controller. Table 3 shows the firmware versions
of all currently supported ASCs.
Note: Some controllers are unique to a local market and may not be available on a global basis.
Table 3: Firmware Revision of Current ACSs
Device/Controller Type Revision Comments
DR-9100 1.x Room Controller
DC-9100 1.x Plant Controller
DC-9100 2.x Plant Controller
DO-9100 1.x Digital Controller
DX-9100 (V.1) 1.x Digital Controller
DX-9100 (V.2) 2.x Digital Controller
TC-910x 1.x-3.x Digital Controller
TEC1100 1.x N2 Lighting Control Data (LCD) Thermostat
XT-9100 1.x Extension Module
XTM-101 1.x Extension Module
LCP-xxx All Lab and Central Plant Controller
Metasys Integrator Unit 9.0 or later Metasys Integrator Unit

Table 3: Firmware Revision of Current ACSs
Device/Controller Type Revision Comments
UNT All Unitary Controller
VAV All Variable Air Volume (VAV) Controller
AHU All Air Handling Unit Controller
PHX All Phoenix Interface Module
VMA1400 All VAV Modular Assembly
VND (Vendor Device) All Metasys System Compatible (by others) including
TEC1100, TEC210x and VMA1832
1 All ILC
ILC
IF-1010/2020 All Intelligent Fire Controller
1 Information for ILCs is not valid for MicroLite lighting controllers. For MicroLite panels, use the information for Vendor Devices
(VND) instead.
Detailed Procedures
These procedures show how to add field devices using an archive database or Discovery, add N2 points, and create
extensions to an object.
Adding N2 Integrations
The two N2 trunks (N2A and N2B) are part of the default NAE database, and you only need to Select N2 Trunk
(integration) from the Navigation Tree. You need to Add an N2 trunk only if one or both N2 trunks have been deleted
from the default database.
To add N2 integrations:
1. On the Insert menu, click Integration. The Insert Integration Wizard starts (Figure 1).
2. Follow the prompts to configure the integration using Table 4.

Figure 1: Insert Integration Wizard
Table 4: Insert Integration Wizard

Screen Purpose
Object Type Select the type of integration. For example, N2 trunk,
LONWORKS® network, or BACnet® system integration.
Destination Select the supervisory device which connects to the trunk you
are integrating.
Identifier Type a unique name for the trunk. A unique name is required
for each integration under a device. By default, the name of
the object being entered has a number appended to keep it
unique; therefore, if adding an N2 trunk to a site for the first
time, the default name is N2 Trunk1.
Configure Configure information about the integration such as trunk
number and a brief description. Selecting the Advanced button
1
allows you to edit the BACnet Object Identifier.
Summary View the basic parameters of the integration just added.
1 When selecting or adding a second N2 trunk, you must change the default trunk number (which is 1) on the Hardware
tab to 2.
3. Click Finish.

Adding N2 Field Devices Manually (Online or Offline)
You can add N2 field devices manually whether your system is online or offline using the Insert Field Device Wizard.
To add N2 field devices manually:
1. On the Insert menu, click Field Device. The Insert Field Device Wizard starts (Figure 2).
Figure 2: Insert Field Device Wizard Destination Screen
2. Select the trunk where you want to insert the device and click Next. The Insert Field Device Wizard Select
Definition screen appears (Figure 3).
3. On the Select Definition Mode screen, select the Manual device definition radio button.
Note: When using the SCT, the Assisted device definition radio button appears dimmed because that method
is unavailable when the system is offline.

Figure 3: Insert Field Device Wizard Select Definition Screen
4. Select the type of device and an N2 address for the device you are creating. All N2 addresses in the drop-down
combo box are valid N2 addresses because the list is updated each time a new controller object is created. After
choosing an N2 address, click Next. Auto Discovery is only available online for field devices. See the Adding N2
Field Devices Online Using Auto Discovery section in this document.
5. Click Next. The Insert Field Device Wizard Identifier screen appears (Figure 4).

Figure 4: Insert Field Device Wizard Identifier Screen
6. Choose a unique name (within the parent object) for the new controller object and click Next. The Insert Field
Device Wizard Configure screen appears (Figure 5).
The fields of the Configure screen have default data based on the previous information entered. This information
includes the object type and naming parameters of the new controller being created. When you use the Manual
Device Definition, the default name is always the controller type (for example, Air Handling Unit (AHU), , or VMA)
plus an incremental number. The incremental number ensures that the suggested name is unique within the
context of the parent object, in this case an N2 integration.

Figure 5: Insert Field Device Wizard Configure Screen
7. Click Next. The Insert Field Device Wizard Summary screen appears (Figure 6).

Figure 6: Insert Field Device Wizard Summary Screen
8. If you are satisfied with the Summary, click Finish (otherwise click Back and correct any problems).
The object is created, and you are given the opportunity to add extensions to the new controller object. See the
Adding Extensions to an Object section in this document for more information.
Adding N2 Field Devices Online Using Auto Discovery

When you are logged in to an NAE through the Metasys system, you can automatically discover field devices. The
auto discovery process cannot be used through the SCT; however, the devices that are discovered on the network
and added to the NAE database (through the Site Management Portal UI) can be uploaded to the SCT for archiving
and editing.
Using this procedure requires that the NAE be online and connected to an N2 network. To connect to an N2 network,
verify your NAE is connected to the N2 bus via an N2 port.
Note: Auto discovery does not find N2 devices tunneling over an Ethernet network.
To add N2 field devices online using Auto Discovery:
1. On the Insert menu, select Field Device. The Insert Field Device Wizard Destination screen appears (Figure 2).
2. Select the N2 trunk you want to map the field devices to and click Next. The Select Definition Mode screen
appears (Figure 7).

The Assisted Mode and Invoke Auto Discovery options are not available from the SCT. The information discovered
online can be uploaded to an archive database in the SCT.
Figure 7: Insert Field Device Wizard (Online Only) Select Definition Mode Screen
3. Click the Invoke Auto Discovery button. The Auto Detect Utility starts (Figure 8).

Figure 8: Auto Detect Utility (Online Only) Screen
4. Select the device you want to map. If the device is already mapped, you are notified. If the device is not mapped,
the Insert Field Device Identifier screen appears (Figure 4).
5. Enter a unique identifier for the device. The Insert Field Device Wizard Configure screen appears (Figure 5).
6. Click Next. The Insert Field Device Summary screen appears (Figure 6).
7. If you are satisfied with the Summary, click Finish (otherwise click Back and correct any problems). The object
is created and you are given the opportunity to add extensions to the new controller object. See the Adding
Extensions to an Object section in this document for more information.
8. When you have added all discovered devices, use the SCT to upload the NAE database to an archive database
in the SCT.
Adding Extensions to an Object

Add trend, totalization, alarm, and resource file extensions to increase the functionality of a field device or field point
object.
After creating a field device object or a field point object, the Extension Wizard automatically starts (skip to Step 3).
To add extensions to an object:
1. Select an object.
2. On the Action menu, select Show Extensions. The Extension Wizard starts (Figure 9).

Figure 9: Extension Wizard
3. Click the New button in the row next to the type of extension you want to add, and follow the prompts on the
Wizard that appears. See the Adding a Resource File Extension, Adding a Totalization Extension, or Adding an
Alarm Extension sections in this document for more information.
4. Follow the prompts to configure the extension and click Finish when you are done. The Extension Wizard appears
with the new extension listed in the appropriate row (Figure 10).

Figure 10: Extension Wizard with Extension Added
5. Click the Done button when you are finished adding extensions. If the Extension Wizard launched automatically
after creating a new field device object, the Field Device Extension screen opens (Figure 11).

Figure 11: Field Device Extension Screen
6. Add field points under the newly created controller object by selecting the New button in the Field Points panel
of the Field Device Extension Wizard. See the Adding N2 Field Devices Manually (Online or Offline) section for
instructions on adding N2 points.
Adding a Resource File Extension

When using an HVAC PRO (PRN) file as a resource file, be sure you use the long print file format because it provides
the Metasys system with more information than the short print file format. For example, the long print file format
imports the units of measure while the short file format does not import this information into the Metasys system.
The short print file format imports metric HVAC PRO files with imperial attributes that must be individually changed
to Metric. To prevent this problem, use the long print file format when importing an HVAC PRO file. To configure the
long print file format, launch HVAC PRO and select File > Print Format > Long.
The resource file object extension is the most important extension to the N2 controller objects. N2 configuration files
are imported in the Resource File Wizard. These files provide predefined point information that is used for the creation
of N2 point objects in the Insert Field Point Wizard. Resource files enable the assisted point definition mode in the
Insert Point Wizard. They also provide the view information used in the Engineering view of the N2 trunks. If the N2
device does not have a resource file extension, Assisted mode is not available in the Insert Point Wizard.
To add a resource file extension:
1. In the Extension Wizard, click the New button in the Resource File row. The Insert Resource File Wizard Select
File screen appears (Figure 12).

Figure 12: Insert Resource File Wizard Select File Screen
2. Click the Browse button and locate the resource file to import to the object. The default file type is based upon
the file type expected for the parent-controller object. For example, for a UNT controller, the default file type is
.prn. After you select a file, the Wizard validates the file based on the controller type of the newly created object.
If the selected file does not appear to be correct for the controller, a red error message appears in the user text
area of the Resource File Wizard showing the expected controller type from within the selected file.
3. After you select a valid import file, click Next. The Insert Resource Wizard Configure screen appears.
The description property shows the original file location and file name of the selected import file as reference.
The converted XML file based on the selected file is not accessible to the user.
4. If the Configure screen looks correct, click Next. The Insert Resource Wizard Summary screen appears.
5. Click Finish. The Extensions Wizard appears with the new Resource File listed under Resource Files.
Adding a Trend Extension

Adding trend extensions to objects allows you to collect historical data for one or more attributes of an object, then
view that data and/or have the data forwarded to an ADS/ADX for long-term storage. Use Trend Study to view Trend
extensions from multiple items at the same time. For more information on Trend Studies, refer to the Metasys system
Help.
To add a trend extension:

1. In the Extensions Wizard, click the New button in the Trend row. The Insert Trend Wizard Select Attribute screen
appears. The trended attribute defaults to Present Value. To trend a different attribute, click other... The attribute
list appears (Figure 13).
Figure 13: Insert Trend Wizard Select Attribute Screen
2. Select an attribute and follow the prompts in the Wizard to complete the addition of a Trend Extension.
3. Click Finish. The Extensions Wizard appears with the new attribute listed under Trend.
Adding a Totalization Extension

1. In the Extensions Wizard, click the New button in the Totalization row. The Insert Totalization Wizard Select
Attribute screen appears (Figure 14).

Figure 14: Insert Totalization Wizard Select Attribute Screen
2. Select an object in the top of the screen and an attribute in the bottom and click Next.
Note: Click other to display a list of available attributes.
3. Select Totalization type from the available radio buttons on the right (if available).
4. Follow the prompts in the Wizard to complete the addition of a Totalization Extension.
5. Click Finish. The Extensions Wizard appears with the new attribute listed under Totalization.
Adding an Alarm Extension

1. In the Extensions Wizard, click the New button in the Alarm row. The Insert Alarm Wizard Select Attribute screen
appears (Figure 15).

Figure 15: Insert Alarm Wizard Select Attribute Screen
2. Select an object you want to add the Alarm extension to in the top of the screen and an attribute in the bottom
and click Next.
3. Follow the prompts in the Wizard to complete the addition of an Alarm Extension.
4. Click Finish. The Extensions Wizard appears with the new attribute listed under Alarm.
Adding an Averaging Extension

1. In the Extensions Wizard, click the New button in the Averaging row. The Insert Averaging Wizard Select Attribute
screen appears (Figure 16).

Figure 16: Insert Averaging Wizard Select Attribute Screen
2. Select an object you want to add the Averaging extension to at the top of the screen and an attribute at the
bottom. Click Next.
3. Follow the prompts in the Wizard to complete the addition of an Averaging Extension.
4. Click Finish. The Extensions Wizard appears with the new attribute listed under Averaging.
Deleting Extensions from an Object

1. Select a field device or a field point that contains extensions you want to delete.
2. On the Action menu, select Show Extensions. The Extension Wizard starts (Figure 17).

Figure 17: Extension Wizard
3. Select the check boxes next to the extensions you want to delete.
4. Click Delete for each extension.
When you click the Delete button in any extension row, it only deletes the checked extensions in that row. For
example, you have to click both the Totalization delete button and the Averaging delete button to delete both
checked extensions. See Figure 17.
5. Click Done when finished.
Copying Extensions to a Field Device or Field Point (Offline Only)

1. Select a field device or a field point that contains extensions you want to copy.
2. On the Action menu, click Show Extensions. The Extension Wizard starts (Figure 17).
3. Check the extensions that you want to copy and click the Copy Checked Extensions button at the bottom of the
Wizard.
4. Click Done.
5. In the Navigation Tree, select the field device or field point to which you want to add these extensions.
6. On the Edit menu, click Paste. The copied extensions are added to the field device or field point you have
selected. A message appears stating the extension paste has completed.
7. Click OK.
8. Drag the field device or field point to the Display frame (right pane) to verify that the new extensions are correct.

Figure 18: Totalization and Averaging Extensions Pasted into AHU-1
Adding N2 Field Points to an Archive Database

1. On the Insert menu, click Field Point. The Insert Point Wizard Destination screen appears (Figure 19).

Figure 19: Insert Point Wizard Destination Screen
2. Choose a controller or folder in which to insert the new field points and click Next. The Insert Point Wizard Select
Definition Mode screen appears (Figure 20).

Figure 20: Insert Point Wizard Select Definition Mode Screen
Note: There are two methods of adding field points in the SCT and online UI. If you have created a Resource
File extension for the field device to which you are adding points, then Assisted mode definition is available.
Otherwise, the Assisted button is grayed out and your only choice for adding field points is manual mode.
Depending on which mode you are using, see the Adding Field Points Using Assisted Mode Definition
or Adding Field Points Using Manual Mode Definition sections in this document.
Adding Field Points Using Assisted Mode Definition

If you have created a Resource file extension for the field device to which you are adding points, then assisted mode
definition is enabled. Assisted mode definition is the fastest way to add field points to a field device.
To add field points using assisted mode definition:
1. On the Insert Point Wizard Select Definition Mode screen (Figure 20), select the Assisted radio button.
2. Click the Use Point Definition File button. The Point Mapping Utility starts (Figure 21).

Figure 21: Point Mapping Utility
3. Select individual points to map by double-clicking them, or click the Map All button to map all available points
from the file. Each point that is mapped appears in the Points to Map Summary panel on the right and is also
marked with a green check mark to show that it is a mapped point (Figure 22).

Figure 22: Point Mapping Utility with All Points Mapped
Note: In the Point Mapping Utility, you can edit information about individual points in the Points to Map Summary
panel. You can also un-map individual points by double-clicking the point in the middle panel or clicking
the Unmap All button. Selecting a folder in the middle panel displays the points mapped from that folder
in the Points to Map Summary panel, whereas selecting the field device in the middle panel displays a
summary of all points mapped to that device in the Points to Map Summary panel.
4. Click Next when you have mapped all desired points. The Insert Point Wizard Summary screen appears (Figure
22).

Figure 23: Insert Point Wizard Summary Screen
5. If you are satisfied with the Summary, click Finish (otherwise, click the Back button and edit as needed.).
Adding Field Points Using Manual Mode Definition

1. On the Insert Point Wizard Select Definition Mode screen (Figure 24), select the Manual radio button. The Insert
Point Wizard switches to Manual mode (Figure 24).

Figure 24: Insert Point Wizard Manual Definition Mode
2. Select the type of point that you want to add and click Next. The point information on the Select Data Source
screen is pre-configured, based on the object type selected in the Select Definition Mode screen; however, on
the Select Data Source screen you can edit some properties of the point that cannot be edited in the Configure
screen. Depending on how many points of each type were added to a controller, the values available in the
drop-down boxes change so your available selections are valid. The Insert Point Wizard Select Data Source
screen appears (Figure 25).

Figure 25: Insert Point Wizard Select Data Source Screen
3. Edit the point properties as necessary and click Next. The Insert Point Wizard Identifier screen appears (Figure
26).

Figure 26: Insert Point Wizard Identifier Screen
4. Enter a unique name for the new field point. The default name is based on the object type of the new field point.
5. Click Next. The Insert Point Wizard Configure screen appears (Figure 27).

Figure 27: Insert Point Wizard Configure Screen
6. Review the Configuration and Hardware tabs. Edit if necessary and click Next. The Insert Point Wizard Summary
screen appears (Figure 28). Properties edited in the Manual Point Data Source page are not editable in the
normal Configuration view of the object.
Note: The object type and naming parameters of the new point appear in the Insert Point Wizard Summary
screen. When you click Finish, the object is created and you are prompted to add extensions to the new
point object through the Extension Wizard.

Figure 28: Insert Point Wizard Summary Screen
7. Click Finish. Otherwise, click the Back button and edit as needed.
N2 FEC, FAC, and VMA Point Limits

At CCT 10.1, FECs, FACs, and VMAs can be defined as certain N2 devices. These devices include AHUs, UNTs,
VAVs, and vendor devices. The following tables define the point limits of the new devices. To determine the appropriate
point limits, use these tables and the tables for the devices which you are defining them as. In all cases, use the
lower of the point limits of the N2 FEC and of the device it is defined as. For example, if you are defining an FEC1611
as an AHU, your point limit for AIs is 8, as defined in the AHU Point Mapping to NAEs table, rather than the potential
of 12 shown in Table 6.
Table 5: Point Limitations of FAC2611, FAC2612, and FAC3611

Network Point Type Network Point Address
AI 1-50
BI 1-50
AO 1-50
BO 1-50
ADF 1-256
ADI 1-256
BD 1-256
Table 6: Point Limitations of FEC1611 and FEC2611

AI 1-12
BI 1-12

Table 6: Point Limitations of FEC1611 and FEC2611
AO 1-10
BO 1-15
ADF 1-256
ADI 1-256
BD 1-256
Table 7: Point Limitations of VMA1615, VMA1617, VMA1630, VMA1632, and VMA1832

AI 1-8
BI 1-8
AO 1-8
BO 1-8
ADF 1-256
ADI 1-256
BD 1-256
N2 Device Point Mapping Tables

The N2 device point mapping tables allow you to manually map points into the NAE using the SCT. These tables
list the devices and points that you can manually map into the NAE.
AHU
Table 8 describes AHU to NAE object mapping.
Table 8: AHU Point Mapping to NAEs
1 Network Point Address Command Allowed Can Map to NAE Objects:
Network Point Type
AI 1-8 Yes AI, AO, MSI, MSO
AO 1-8 Yes AO, MSO
BI 1-8 Yes BI, BO
BI 7-8 can be mapped to PC
BO 1-10 Yes BO
ADF 1-64 AI, MSI
ADF Yes AI, AO, MSI, MSO
65-256
ADI 1-64 AI, MSI
65-256 Yes AI, AO, MSI, MSO
BD 1-64 AI, BI, MSI
2 Yes AI, AO, BI, BO, MSI, MSO
65-256
1 When configuring an FEC or FAC as an N2 AHU, UNT or VAV type device, the limitations of the new controller must be
considered in addition to those in this table. See N2 FEC, FAC, and VMA Point Limits.
2 BD245 through BD248 are reserved for user-defined data storage points.

Unitary (UNT)
Table 9 describes UNT to NAE object mapping.
Table 9: UNT Point Mapping to the NAE
1 Network Point Address Command Allowed Can Map to NAE Objects
Network Point Type
AO 1-8 Yes AO
BI 1-37 Yes BI, BO
BI 4 can be mapped to PC.
BO 1-14 Yes BO
ADF 1-64 AI, MSI
ADI 1-64 AI, MSI
BD 1-64 AI, BI, MSI
65-256
VAV Controller
Table 10 describes VAV to NAE object mapping.
Table 10: VAV Point Mapping to NAE
1 Network Point Address Command Allowed Can Map to NAE Objects:
Network Point Type
AO 1-8 Yes AO, MSO
BI 1-5 Yes BI, BO
BO 1-8 Yes BO
ADF 1-64 AI, MSI
ADI 1-64 AI, MSI
BD 1-64 AI, BI, MSI
65-256
1 When. configuring an FEC or FAC as an N2 AHU, UNT or VAV type device, the limitations of the new controller must be
VMA 1400 Series

Table 11 describes VMA1400 to NAE object mapping.

Only points defined in the HVAC PRO software configuration can be mapped to the NAE. VMA format errors are
generated if this rule is not followed.
Table 11: VMA Point Mapping to NAE
1 Network Point Address Command Allowed Can Map to NAE Objects
Network Point Type
AO 1-8 Yes AO, MSO
BI 1-5 Yes BI, BO
BO 1-8 Yes BO
ADF 1-64 AI, MSI
ADI 1-64 AI, MSI
BD 1-64 AI, BI, MSI
65-256 Yes AI, AO, BI, BO, MSI, MSO
Phoenix Fume Hood (PHX)

Table 12 describes PHX to NAE object mapping.
Table 12: PHX Point Mapping to NAEs
Network Point Type Network Point Address Command Allowed Can Map to NAE Objects:
AO 1-8 Yes AO, MSO
BI 1-37 Yes BI, BO
BO 1-14 Yes BO
ADF 1-64 AI, MSI
ADI 1-64 AI, MSI
BD 1-64 AI, BI, MSI
65-256
Metasys Integrator Unit

Table 13 describes the Metasys Integrator unit to NAE object mapping.
Table 13: Metasys Integrator Unit Point Mapping to an NAE
AI 1-256 Yes AI, MSI, MSO
AO 1-256 Yes AO, MSO

Table 13: Metasys Integrator Unit Point Mapping to an NAE
BI 1-256 Yes BI, BO, PC
BO 1-256 Yes BO
ADF 1-256 Yes AI, AO, MSI, MSO
ADI 1-256 Yes AI, AO, MSI, MSO, PC
BD 1-256 Yes AI, AO, BI, BO, MSI, MSO
Vendor Device (VND)

Table 14 describes VND to NAE object mapping.
Table 14: VND Point Mapping to an NAE
AI 1-256 Yes AI, MSI, MSO
AO 1-256 Yes AO, MSO
BI 1-256 Yes BI, BO
BO 1-256 Yes BO
ADF 1-256 Yes AI, AO, MSI, MSO
ADI 1-256 Yes AI, AO, MSI, MSO, PC
BD 1-256 Yes AI, AO, BI, BO, MSI, MSO
ILC
Before you map ILC points to NAE objects, the ILC must be programmed. The point mapping table for ILCs is not
valid for MicroLite lighting controllers; instead, use the VND table. Table 15 describes ILC to NAE object mapping.
Table 15: ILC Point Mapping to an NAE
Network Point Network Point Command Override Can Map to NAE Description
Type Address Allowed Status Objects:
ADI 1-32 Yes No AI AO Current month runtime
lighting
Groups 1-32 (hours)
ADI 33-64 Yes No AI AO Previous month runtime
lighting
Groups 1-32 (hours)
BO 1-32 Yes Yes BO Lighting groups (manual
override)
Intelligent Fire Controller (IFC)

Before you map IFC points to NAE objects, the IFC must be programmed.
All points are mapped to NAE BI (Binary Input) points. All points are read-only (no commands allowed). It is the
user’s option to map either a general trouble status point or a trouble status point for each zone.
The fire alarm panel only reports exceptions. Newly added fire points must wait for an exception report before
reporting online. An offline/online transition for the whole controller also generates exception reports. Table 16
describes IFC to NAE object mapping.

Table 16: IFC Point Mapping to an NAE
Network Point Type Network Point Can Map to NAE NAE Object Notes
Address Objects: Description and
Units
BI 1-240 BI Zone State (Nor/Alm) Zone displays trouble
status (T).Override
status (O) = zone
disabled at fire panel.
BD 1-240 BI Zone Trouble (Nor/Tbl) No trouble status (T)
BD 241 BI UPS Battery Low
(Ok/Alm)
BD 242 BI AC Power Fail (Ok/Alm)
BD 243 BI Database Fault (Ok/Alm)
BD 244 BI System Alarm (Nor/Alm) General system alarm
point
BD 245 BI System Trouble General system trouble
(Nor/Tbl) point
BD 246 BI Alarm Silenced (No/Yes)
TC-9100 Terminal Unit Controller

Table 17 shows how TC-9100 points can map to NAE objects. Table 18 provides more detail about the points (for
example, tag names, item descriptions, and which points are commandable). Use the .PRN file generated by HVAC
PRO software to determine which points are applicable to the specific TC-9100 controller you are mapping (for
example, TC-9102).
Note: If BD-2 is mapped into NAE as a BO, commands to this BO switch the controller mode between Night/Comfort.
This scenario allows NAE to schedule the controller mode weekly. If BD-2 is mapped into NAE as an AO/MSO,
a manual command can command this AO/MSO to any of the four controller modes. Only one of these
methods (BO or AO/MSO) may be used. The override status flag for BD-2 is SUPC (BO-11). A command to
BD-2 sets SUPC, and a release or auto command clears it.
Table 17: TC-9100 Point Mapping to an NAE
TC-9100 Network Point Type NAE Object Type
AI 1 to 10 AI
BD 1 to 2
PMK 1 to 42
1
BI 1 to 14 BI
AO 1 to 18 AO
BD 1 to 2
PMK 1 to 42
1
BO 1 to 13 BO
BD 1 to 2
1 All but PMK1 stored in EEPROM (maximum 10,000 write commands).

Table 18: TC-9100 Point Mapping (Detail)
Network Point Network Point Command Override Tag Name Item Description
Type Address Allowed Status
AI 1 AI1 Process Temperature
AI 2 AI2 Remote Temperature Setpoint Bias
AI 3 AI3 Pressure
AI 4 AI4 Override Input
AI 5 AI5 DR-9100 only
AI 6 AI6 DR-9100 only
AI 7 SPARE
AI 8 SPARE
AI 9 WAC Winter Authority Correction
AI 10 SAC Summer Authority Correction
BI 1 WIN Window Sense
BI 2 OCC Occupancy Sense
BI 3 AIRQ Air Quality Sense
BI 4 MODT Temporary Mode
BI 5 ALT Alternate Mode
BI 6 SUPS Supervisory Mode Status
BI 7 SPARE
BI 8 SPARE
BI 9 REVL Reverse Action Local
BI 10 L1A Loop 1 Active
BI 11 ALM General Alarm
BI 12 AFM Low Limit Mode Active
BI 13 FOV Three Speed Fan Override
BI 14 L3A Loop 3 Active
AO 1 Yes Yes OCM1 Output Programmable Module 1
AO 7 Yes Yes WSP 1 Working Set Point Loop 1
AO 13 Yes XAI1 External Input 1

AO 17 Yes AC05 Analog Constant 5
AO 18 Yes AC06 Analog Constant 6
BO 1 Yes Yes D01 TRIAC 1
BO 8 Yes SOFF Shutoff Mode
BO 9 Yes STUP Startup Mode
BO 10 Yes DAY DR-9100 Only
BO 11 Yes SUPC Supervisory Mode Control (See
BD-2 and Note)
BO 12 Yes MAN Manual Operation Mode
BO 13 Yes REVC Reverse Action Command
BD 1 Yes MODS Mode Status: Night, Standby,
Comfort, Off
BD 2 Yes Yes MODC Mode Command: Night, Standby,
Comfort, Off (See Note)
PMK 1 Yes PM1K1 Module 1 K1
Constant:
PMK 2 Yes
1 PM1K2 K2
PMK 3 Yes
1 PM1K3 K3
PMK 4 Yes
1 PM1K4 K4
PMK 5 Yes
1 PM1K5 K5
PMK 6 Yes
1 PM1K6 K6
PMK 7 Yes
1 PM1K7 K7

Constant:
PMK 9 Yes
1 PM2K2 K2
PMK 10 Yes
1 PM2K3 K3
PMK 11 Yes
1 PM2K4 K4
PMK 12 Yes
1 PM2K5 K5
PMK 13 Yes
1 PM2K6 K6
PMK 14 Yes
1 PM2K7 K7

Constant:
PMK 16 Yes
1 PM3K2 K2
PMK 17 Yes
1 PM3K3 K3
PMK 18 Yes
1 PM3K4 K4
PMK 19 Yes
1 PM3K5 K5
PMK 20 Yes
1 PM3K6 K6
PMK 21 Yes
1 PM3K7 K7

Constant:
PMK 23 Yes
1 PM4K2 K2
PMK 24 Yes
1 PM4K3 K3
PMK 25 Yes
1 PM4K4 K4
PMK 26 Yes
1 PM4K5 K5
PMK 27 Yes
1 PM4K6 K6
PMK 28 Yes
1 PM4K7 K7

Constant:
PMK 30 Yes
1 PM5K2 K2
PMK 31 Yes
1 PM5K3 K3
PMK 32 Yes
1 PM5K4 K4
PMK 33 Yes
1 PM5K5 K5
PMK 34 Yes
1 PM5K6 K6
PMK 35 Yes
1 PM5K7 K7

Constant:
PMK 37 Yes
1 PM6K2 K2
PMK 38 Yes
1 PM6K3 K3
PMK 39 Yes
1 PM6K4 K4
PMK 40 Yes
1 PM6K5 K5
PMK 41 Yes
1 PM6K6 K6
PMK 42 Yes
1 PM6K7 K7
1 Item stored in EEPROM (maximum 10,000 write commands).
Lab and Central Plant Controller/Digital Controller (LCP/DC9100)

Table 19 and Table 20 show LCP/DC9100 point mapping. Table 19 shows how LCP/DC9100 points can map to
NAE objects. Table 20 provides more detail about the LCP/DC9100 points (for example, tag names and which points
are commandable).

Table 19: LCP/DC9100 Point Mapping to NAE
LCP/DC9100 Network Point Type NAE Object Type
AI, ADF AI
ADF AO
BI, BD BI
BO, BD BO

Table 20: LCP/DC9100 Point Mapping (Detail)
AI 1 AI1 Analog Input 1
BI 1 DI1 Digital Input 1
BO 1 Yes Yes DO3 Digital Output 3
BO 7 Yes SOFF Shut Off Mode
BO 8 Yes STUP Start Up Mode
ADF 1 NCM1 Output Numeric Module 1
ADF 5 Yes ACO1 Analog Constant 1
ADF 9 Yes Yes OCM1 Output Control Module 1

ADF 17 Yes Yes WSP1 Working Setpoint Control Module 1
ADF 25 Yes LSP1 Control Module 1: Local Setpoint
ADF 26 Yes PB1 Proportional Band
ADF 27 Yes TI1 Reset Action
ADF 28 Yes TD1 Rate Action
ADF 29 Yes HIL1 Output High Limit
ADF 30 Yes LOL1 Output Low Limit
ADF 31 Yes BSB1 Standby STP
Change
ADF 32 Yes BOF1 Off Mode STP
Change
ADF 33 Yes DA1 Deviation Alarm
Limit
Change
Change
Limit

Change
Change
Limit
Change
Change
Limit
Change
Change
Limit

Change
Change
Limit
Change
Change
Limit
Change
Change
Limit
BD 1 LCM1 Output Logic Module 1
BD 5 Yes DCO1 Digital Constant 1

DX-9100 Extended Digital Controller

Table 21 and Table 22 show DX-9100 point mapping. Table 21 shows how DX-9100 points can map to NAE objects.
Table 22 provides details about DX-9100 points (for example, tag names, item descriptions, and which points are
commandable).
Note: For XPs, the actual AO range is AO7 and AO8 and the actual AI range is AI1 through AI8.
Note: EEPROM Items can only be written approximately 10,000 times.
Table 21: DX-9100 Point Mapping to NAE
DX-9100 Network Point Type NAE Object Type
AI 1 to 72 AI
ADF 1 to 8
ADI 1 to 72
PMK 1 to 240
PMO 1 to 96
PMA 1 to 96
AO 1 to 72 AO
ADF 1 to 8
ADI 1 to 72
PMK 1 to 240
PMO 1 to 96
BI 1 to 72 BI
BD 1 to 32
LRS 1 to 64
PML 1 to 96
BO 1 to 72 BO
BD 1 to 32
PML 1 to 96
ADI 1 to 72 PC
PMA 1 to 96
Table 22: DX-9100 Point Mapping (Detail)


AI 9 XT1AI1 Expander 1: Analog Input 1
AI 10 XT1AI2 Analog Input 2
1 15 XT1AI7 Analog Input 7
AI
AI
AI
AI
AI
AI
AI
AI

AI
AI

BI 9 XT1DI1 Expander 1: Digital Input 1
BI 10 XT1DI2 Digital Input 2

AO 1 Yes Yes AO1 Analog Output 1

AO 9 Yes Yes XT1AO1 Expander 1: Analog Output 1
AO 10 Yes Yes XT1AO2 Analog Output 2
1 30 Yes Yes XT3AO6 Analog Output 6
AO
1 33 Yes Yes XT4AO1 Expander 4: Analog Output 1
AO
AO
AO
AO
AO
AO

AO
AO
AO
AO
AO
AO
AO
AO
AO
AO
AO
AO
AO
AO
AO
AO
AO
AO
AO
AO
AO
AO
AO
AO
BO 1 Yes SOFF Shut Off Mode
BO 2 Yes STUP Start Up Mode

BO 9 Yes Yes XT1DO1 Expander 1: Digital Output 1
BO 10 Yes Yes XT1DO2 Digital Output 2


ADI 1 Yes CNT1 DI1 Pulse Count
ADI 9 Yes XT1CNT1 Expander 1: DI1 Pulse Count
ADI 10 Yes XT1CNT2 DI2 Pulse Count


BD 1 Yes DCO1 Logic Constant 1

LRS 1 LRS1 Logic Result 1


Constant:
PMK 2 Yes PM1K2 K2
PMK 3 Yes PM1K3 K3
PMK 4 Yes PM1K4 K4
PMK 5 Yes PM1K5 K5
PMK 6 Yes PM1K6 K6
PMK 7 Yes PM1K7 K7
PMK 8 Yes PM1K8 K8
PMK 9 Yes PM1K9 K9
PMK 10 Yes PM1K10 K10
Constant:
PMK 22 Yes PM2K2 K2
PMK 23 Yes PM2K3 K3
PMK 24 Yes PM2K4 K4
PMK 25 Yes PM2K5 K5
PMK 26 Yes PM2K6 K6
PMK 27 Yes PM2K7 K7
PMK 28 Yes PM2K8 K8
PMK 29 Yes PM2K9 K9

Constant:
Constant:
PMK 42 Yes PM3K2 K2
PMK 43 Yes PM3K3 K3
PMK 44 Yes PM3K4 K4
PMK 45 Yes PM3K5 K5
PMK 46 Yes PM3K6 K6
PMK 47 Yes PM3K7 K7
PMK 48 Yes PM3K8 K8
PMK 49 Yes PM3K9 K9

Constant:
PMK 62 Yes PM4K2 K2
PMK 63 Yes PM4K3 K3
PMK 64 Yes PM4K4 K4
PMK 65 Yes PM4K5 K5
PMK 66 Yes PM4K6 K6
PMK 67 Yes PM4K7 K7
PMK 68 Yes PM4K8 K8
PMK 69 Yes PM4K9 K9
Constant:

Constant:
PMK 82 Yes PM5K2 K2
PMK 83 Yes PM5K3 K3
PMK 84 Yes PM5K4 K4
PMK 85 Yes PM5K5 K5
PMK 86 Yes PM5K6 K6
PMK 87 Yes PM5K7 K7
PMK 88 Yes PM5K8 K8
PMK 89 Yes PM5K9 K9
Constant:

Constant:
Constant:

Constant:
Constant:

Constant:

Constant:

Constant:

Constant:
PMO 1 Yes Yes PM1OU1 Module 1 Output: Channel 1
PMO 2 Yes Yes PM1OU2 Channel 2



PMO 73 Yes Yes PM10OU1 Module 10 Channel 1
Output:
PMO 89 Yes Yes PM12OU1 Module 12 Channel 1
Output:
PML 1 Yes Yes PM1DO1 Module 1 Logic Channel 1
Output:
PML 2 Yes Yes PM1DO2 Channel 2

Output:
Output:
Output:
Output:

Output:
Output:
Output:
Output:

Output:
Output:
Output
PMA 1 Yes PM1AC1 Module 1 Channel 1
Accumulator:
PMA 2 Yes PM1AC2 Channel 2

Accumulator:
Accumulator:
Accumulator:
Accumulator:

Accumulator:
Accumulator:
Accumulator:
Accumulator:

Accumulator:
Accumulator:
Accumulator:
1 Applies to European installations only.
Extension Module (XTM and XT)

Table 23 and Table 24 show point mapping for the XTM or XT. Table 23 shows how XTM or XT points can map to
NAE objects. Table 24 provides more detail about the XTM and XT points (for example, tag names, item descriptions,
and which points are commandable).
Override Status is not supported for any points in the XTM or XT, and the Manual Status of Outputs is available only
from the XTM.
These tables are used for XTM-105 or XT-9100 modules on the N2 Bus. For XTM-905 or XT-9100 modules on a
DX-9100 XT Bus, see the two DX-9100 tables, Table 21 and Table 22.
Table 23: XTM (or XT) Point Mapping to the NAE
Type Address Allowed Status Objects
AI 1-8 No AI
BI 1-16 No BI

Table 23: XTM (or XT) Point Mapping to the NAE
Type Address Allowed Status Objects
AO 1-8 Yes No AO
BO 1-16 Yes No BO
ADI 1-8 Yes No AI, PC, AO Writes restricted to
0-32767. Only AO points
are commandable in the
NAE.
BD 1-24 No BI Auto/Manual Flags for
Outputs.
Table 24: XTM (or XT) Point Mapping (Detail)

Network Point Network Point Command Tag Name Item Description
Type Address Allowed
AI 1 AI1 XP0: Analog Input 1
BI 1 1DI1 XP1: Binary Input 1
BI 2 1DI2 Binary Input 2
BI 9 2DI1 XP2: Binary Input 1

AO 1 Yes AO1 XP0: Analog Output 1
AO 2 Yes AO2 Analog Output 2
BO 1 Yes 1DO1 XP1: Binary Output 1
BO 2 Yes 1DO2 Binary Output 2
BO 9 Yes 2DO1 XP2: Binary Output 1
ADI 1 Yes CNT1 XTS: DI1 Pulse Count
The following Tag Names are available only in the XTM:

BD 1 1DOM1 XP1: Binary Output 1
Manual Status
BD 2 1DOM2 Binary Output 2
Manual Status
Manual Status
Manual Status
Manual Status
Manual Status
Manual Status
Manual Status
BD 9 2DOM1 XP2: Binary Output 1
Manual Status
Manual Status
Manual Status
Manual Status
Manual Status
Manual Status
Manual Status
Manual Status

BD 17 AOM1 XP0: Analog Output 1
Manual Status
BD 18 AOM2 Analog Output 2
Manual Status
Manual Status
Manual Status
Manual Status
Manual Status
Manual Status
Manual Status
TEC1100
When adding the TEC1100 to an NAE, define the TEC1100 as controller type VND. Table 25 describes TEC to NAE
object mapping.
Table 25: VND Point Mapping to an NAE (TEC-1100 Thermostat)
Point Name Network Point CommandAllowed NAEObject Override Range
Type/Address
Room Temp ADI-1 N2 AI 0 to 48°C (28 to 124°F)
Outdoor Temp ADI-2 Yes N2 AI -48 to 48°C (-54 to 124°F)
Heating SP ADI-3 Yes N2 AO 0 to 48°C (28 to 100°F)
Cooling SP ADI-4 Yes N2 AO 0 to 48 °C (28 to 100°F)
Setback Heating SP ADI-5 Yes N2 AO 0 to 48°C (28 to 100°F)
Setback Cooling SP ADI-6 Yes N2 AO 0 to 48°C (28 to 100°F)
Minimum Heat SP ADI-7 Yes N2 AO 0 to 48° C (28 to 100°F)
Maximum Heat SP ADI-8 Yes N2 AO 0 to 48° C (28 to 100°F)
Minimum Cool SP ADI-9 Yes N2 AO 0 to 48° C (28 to 100°F)
Maximum Cool SP ADI-10 Yes N2 AO 0 to 48° C (28 to 100°F)
Fan BD-1 Yes N2 BO 0 = Off/Auto, 1 = On/MAN
Mode BD-2 Yes N2 MSO 0 = Off, 1 = Cool, 2 = Heat, 3 =
Auto, 4 = E Ht Pump ‘O’
Occupancy BD-3 Yes N2 BO 0 = Unoccupied, 1 = Occupied
W1 State-Heating BD-4 N2 BI 0 = Off, 1 = On
W2 State-Heat BD-5 N2 BI 0 = Off, 1 = On
Y1 State-Cooling BD-6 N2 BI 0 = Off, 1 = On
Y2 State-Cooling BD-7 N2 BI 0 = Off, 1 = On

Table 25: VND Point Mapping to an NAE (TEC-1100 Thermostat)
Type/Address
G State-Fan BD-8 N2 BI 0 = Off, 1 = On
Temp Units BD-9 Yes N2 BO 0 = °C, 1 = °F
Wrench BI BI-1 N2 BI 0 = Normal, 1 = Alarm
Temp Alarm BI-2 N2 BI 0 = Normal, 1 = Alarm
Filter BI BI-3 N2 BI 0 = Normal, 1 = Alarm
TEC210x
When adding the TEC210x to an NAE, define the TEC210x as controller type VND. Table 26 describes TEC210x
to NAE object mapping.
Table 26: VND Point Mapping to an NAE (TEC-210x Thermostat)
Type/Address
Room Temp ADI-1 Yes N2 AI 0 to 50°C (32 to 122°F)
Aux Temp/Outdoor Temp ADI-2 Yes N2 AI -40 to 50°C (-40 to 122°F)
Heating SP ADI-3 Yes N2 AO 4.5 to 32°C (40 to 90°F)
Cooling SP ADI-4 Yes N2 AO 12 to 37°C (54 to 100°F)
Setback Heating SP ADI-5 Yes N2 AO 4.5 to 32°C (40 to 90°F)
Setback Cooling SP ADI-6 Yes N2 AO 12 to 37.5°C (54 to 100°F)
Minimum Heat SP ADI-7 N2 AI 4.5° C (40°F)
Maximum Heat SP ADI-8 Yes N2 AO 4.5 to 32° C (40 to 90°F)
Minimum Cool SP ADI-9 Yes N2 AO 12 to 37.5° C (54 to 100°F)
Maximum Cool SP ADI-10 N2 AI 37.5° C (100°F)
Fan BD-1 Yes N2 BO 0 = Auto, 1 = On/MAN
Mode BD-2 Yes N2 MSO 0 = Off, 1 = Cool, 2 = Heat, 3 =
Auto, 4 = E Ht (Auxiliary Heat)
Occupancy BD-3 Yes N2 BO 0 = Unoccupied, 1 = Occupied
W1 State BD-4 N2 BI 0 = Off, 1 = On
W2 State BD-5 N2 BI 0 = Off, 1 = On
Y1 State BD-6 N2 BI 0 = Off, 1 = On
Y2 State BD-7 N2 BI 0 = Off, 1 = On
G State-Fan BD-8 N2 BI 0 = Off, 1 = On
Temp Units BD-9 Yes N2 BO 0 = °C, 1 = °F
Occupancy Override BD-10 N2 BI 0 = No Override, 1 = Override
DI1 BI-1 N2 BI 0 = Off, 1 = On
Temp Alarm BI-2 N2 BI 0 = Normal, 1 = Alarm
DI2 BI-3 N2 BI 0 = Off, 1 = On

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.© 2015 Johnson Controls, Inc.
Published in U.S.A. www.johnsoncontrols.com


N2 Integration With The NAE Technical Bulletin: N2 Device Point Mapping Tables

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

N2 Integration With The NAE Technical Bulletin: N2 Device Point Mapping Tables

Uploaded by

Copyright:

Available Formats

N2 Integration with the NAE Technical Bulletin

Code No. LIT-1201683

N2 Integration with the NAE Technical Bulletin 1

Switchable Communications Protocols

The N2 capable FEC controllers:

N2 Integration with the NAE Technical Bulletin 2

N2 Integration with the NAE Overview

N2 Device Point Mapping Tables Overview

N2 Integration with the NAE Technical Bulletin 3

Supported Application Specific Controllers (ASCs)

N2 Integration with the NAE Technical Bulletin 4

N2 Integration with the NAE Technical Bulletin 5

Table 4: Insert Integration Wizard

N2 Integration with the NAE Technical Bulletin 6

N2 Integration with the NAE Technical Bulletin 7

N2 Integration with the NAE Technical Bulletin 8

N2 Integration with the NAE Technical Bulletin 9

N2 Integration with the NAE Technical Bulletin 10

Adding N2 Field Devices Online Using Auto Discovery

N2 Integration with the NAE Technical Bulletin 11

N2 Integration with the NAE Technical Bulletin 12

Adding Extensions to an Object

N2 Integration with the NAE Technical Bulletin 13

N2 Integration with the NAE Technical Bulletin 14

N2 Integration with the NAE Technical Bulletin 15

Adding a Resource File Extension

N2 Integration with the NAE Technical Bulletin 16

Adding a Trend Extension

N2 Integration with the NAE Technical Bulletin 17

Adding a Totalization Extension

N2 Integration with the NAE Technical Bulletin 18

Adding an Alarm Extension

N2 Integration with the NAE Technical Bulletin 19

Adding an Averaging Extension

N2 Integration with the NAE Technical Bulletin 20

Deleting Extensions from an Object

N2 Integration with the NAE Technical Bulletin 21

Copying Extensions to a Field Device or Field Point (Offline Only)

N2 Integration with the NAE Technical Bulletin 22

Adding N2 Field Points to an Archive Database

N2 Integration with the NAE Technical Bulletin 23

N2 Integration with the NAE Technical Bulletin 24

Adding Field Points Using Assisted Mode Definition

N2 Integration with the NAE Technical Bulletin 25

N2 Integration with the NAE Technical Bulletin 26

N2 Integration with the NAE Technical Bulletin 27

Adding Field Points Using Manual Mode Definition

N2 Integration with the NAE Technical Bulletin 28

N2 Integration with the NAE Technical Bulletin 29

N2 Integration with the NAE Technical Bulletin 30

N2 Integration with the NAE Technical Bulletin 31

N2 Integration with the NAE Technical Bulletin 32

N2 FEC, FAC, and VMA Point Limits

Table 5: Point Limitations of FAC2611, FAC2612, and FAC3611

Table 6: Point Limitations of FEC1611 and FEC2611

N2 Integration with the NAE Technical Bulletin 33

Table 7: Point Limitations of VMA1615, VMA1617, VMA1630, VMA1632, and VMA1832

N2 Device Point Mapping Tables

N2 Integration with the NAE Technical Bulletin 34

VMA 1400 Series

N2 Integration with the NAE Technical Bulletin 35

Phoenix Fume Hood (PHX)

Metasys Integrator Unit