n2 integration with the nae technical bulletincgproducts.johnsoncontrols.com/met_pdf/1201683.pdf ·...

N2 Integration with the NAE Technical BulletinCode No. LIT-1201683

Issued February 4, 2019Refer to the QuickLIT website for the most up-to-date version of this document.

Document Introduction.............................................................................................................2Switchable Communications Protocols...........................................................................................2

Related Documentation.............................................................................................................3N2 Integration with the NAE Overview.....................................................................................3N2 Device Point Mapping Tables Overview.............................................................................4Supported Application Specific Controllers (ASCs)..............................................................4Detailed Procedures..................................................................................................................5

Adding N2 Integrations.......................................................................................................................5Adding N2 Field Devices Manually (Online or Offline)....................................................................7Adding N2 Field Devices Online Using Auto Discovery...............................................................11Adding Extensions to an Object......................................................................................................13Adding a Resource File Extension......................................................................................................16Adding a Trend Extension...................................................................................................................17Adding a Totalization Extension..........................................................................................................18Adding an Alarm Extension.................................................................................................................19Adding an Averaging Extension..........................................................................................................20Deleting Extensions from an Object...............................................................................................21Copying Extensions to a Field Device or Field Point (Offline Only)............................................22Adding N2 Field Points to an Archive Database............................................................................23Adding Field Points Using Assisted Mode Definition...................................................................25Adding Field Points Using Manual Mode Definition......................................................................28

N2 FEC, FAC, and VMA Point Limits......................................................................................33N2 Device Point Mapping Tables............................................................................................34

AHU....................................................................................................................................................34Unitary (UNT).....................................................................................................................................35VAV Controller...................................................................................................................................35VMA 1400 Series...............................................................................................................................35Phoenix Fume Hood (PHX)..............................................................................................................36Metasys Integrator Unit....................................................................................................................36Vendor Device (VND)........................................................................................................................37ILC......................................................................................................................................................37Intelligent Fire Controller (IFC)........................................................................................................37TC-9100 Terminal Unit Controller....................................................................................................38Lab and Central Plant Controller/Digital Controller (LCP/DC9100)..............................................41DX-9100 Extended Digital Controller..............................................................................................47Extension Module (XTM and XT).....................................................................................................79TEC1100.............................................................................................................................................82TEC210x.............................................................................................................................................83

1N2 Integration with the NAE Technical Bulletin

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

Document IntroductionThis document describes how to integrate an N2 network in the Metasys® system with the Network AutomationEngine (NAE). This document also describes how to add field devices using an archive database or Discovery, addN2 field points, and create extensions to an object. The N2 device point mapping tables allow you to manually mappoints into the NAE using the System Configuration Tool (SCT). This document lists the devices and points that youcan 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 EquipmentControllers (FACs), Field Equipment Controllers (FECs), and VAV Modular Assemblies (VMAs). At CCT 10.1, thesedevices can be switched between the N2 and MS/TP communications protocols. When determining the number ofpoints that may be mapped from a newer controller that is being used as an N2 device, it is important to look at thepoint limitations of the new device as well as the point limitations of the device which you are mapping it as (forexample, when defining a VMA16xx as a UNT in the mapping table). In all cases, the point limit is the smaller ofwhat you find in the two tables.

Switchable Communications ProtocolsRelease 10.1 of CCT can be used to switch the Field Bus communications protocol in FEC Field Controllers to beeither the standard BACnet®Master-Slave/Token-Passing (MS/TP) or the N2 protocol. BACnet MS/TP is the defaultcommunications protocol for all new controllers. Switchable communications protocols provide a cost-effectiveupgrade and modernization path for customers with existing N2 controllers. The Modernization Guide for LegacyN2 Controllers (LIT-12012005) and the controller-specific documentation provide installation and commissioningsupport and include tips for efficient and safe replacement. Refer to the N2 Compatibility Options chapter of theController Tool Help (LIT-12011147) for information about mapping N2 Objects in controllers with switchablecommunications protocols.

The N2 capable FEC controllers can be used as functional replacements for legacy N2 controllers. The N2 capableFEC 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 FX-PC controllers can be used as functional replacements for legacy N2 controllers. The N2 capableFX-PC controllers:

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 DocumentationTable 1: N2 Device Point Mapping Tables Related Documentation

See DocumentFor Information OnMetasys® SCT Help (LIT-12011964)Mapping Points

Lighting Control Objects Technical Bulletin (LIT-636105)Programming the Intelligent Lighting Controller(ILC)

IFC-1010/2020 Programming Technical Bulletin(LIT-448060)

Programming the Intelligent Fire Controller (IFC)

Appendix C of the DX-9100 Configuration Guide(LIT-6364030)

Mapping to programmable function module items(PMK, PMO, PMA)

NAE Commissioning Guide (LIT-1201519)Configuring the NAE

NAE55/NIE55 Installation Instructions (Part No.24-10051-43)

Installing the NAE/NIE

Modernization Guide for Legacy N2 Controllers(LIT-12012005)

Technology and general rules for replacing legacyN2 controllers with N2 capable FEC controllers

N2 Integration with the NAE OverviewFor 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 objectsand 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 anddevice definitions in the NAE. The data is stored in the archive database in the SCT if the NAE is offline or in theNAE 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, andimporting and mapping N2 points. When you are online with an NAE through the Site Management Portal UI, notthrough the SCT, the Insert Field Device wizard can use Auto Discovery to discover controllers connected to eachN2 trunk. With Auto Discovery, manual entry of controller addresses and controller types is unnecessary. You canthen map field points within each controller using N2 controller configuration files or manual point definition. Thedatabase created at the NAE using Auto Discovery can then be uploaded to an archive database in the SCT forstoring or editing.

If two controllers on an N2 trunk have the same address, the controller should display with a status of DuplicateAddress. However, auto discovery cannot identify all duplicates, depending on timing and the type of devices. It ispossible that one or both of the duplicate controllers do not appear in the list of discovered controllers. If a controlleris 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 OverviewThe 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 AbbreviationsDefinitionAbbreviationAnalog InputAI

Binary InputBI

Analog OutputAO

Binary OutputBO

Analog Data FloatADF

Analog Data IntegerADI

Binary (byte) DataBD

Logic ResultsLRS

Programmable Module Constants (written to Electrically-Erasable Programmable Read-OnlyMemory [EEPROM])

PMK

Programmable Module OutputsPMO

Programmable Module LogicPML

Programmable Module AccumulatorPMA

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 versionsof 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 ACSsCommentsRevisionDevice/Controller TypeRoom Controller1.xDR-9100

Room Controller2.xDR-9100

Room Controller2.xDR-9101

Plant Controller1.xDC-9100

Plant Controller2.xDC-9100

Digital Controller1.xDO-9100

Digital Controller1.xDX-9100 (V.1)

Digital Controller2.xDX-9100 (V.2)

Digital Controller1.x-3.xTC-910x

N2 Lighting Control Data (LCD) Thermostat1.xTEC1100

Extension Module1.xXT-9100


Table 3: Firmware Revision of Current ACSsCommentsRevisionDevice/Controller TypeExtension Module1.xXTM-101

Extension Module1.xXTM-105

Extension Module1.xXTM-905

Lab and Central Plant ControllerAllLCP-xxx

Metasys Integrator Unit9.0 or laterMetasys Integrator Unit

Unitary ControllerAllUNT

Variable Air Volume (VAV) ControllerAllVAV

Air Handling Unit ControllerAllAHU

Phoenix Interface ModuleAllPHX

VAV Modular AssemblyAllVMA1400

Metasys System Compatible (by others) includingTEC1100, TEC210x and VMA1832

AllVND (Vendor Device)

ILCAllILC1

Intelligent Fire ControllerAllIF-1010/2020

1 Information for ILCs is not valid for MicroLite lighting controllers. For MicroLite panels, use the information for Vendor Devices(VND) instead.

Detailed ProceduresThese procedures show how to add field devices using an archive database or Discovery, add N2 points, and createextensions to an object.

Adding N2 IntegrationsThe 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 deletedfrom 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 WizardPurposeScreenSelect the type of integration. For example, N2 trunk,LONWORKS® network, or BACnet® system integration.

Object Type

Select the supervisory device which connects to the trunk youare integrating.

Destination

Type a unique name for the trunk. A unique name is requiredfor each integration under a device. By default, the name ofthe object being entered has a number appended to keep itunique; therefore, if adding an N2 trunk to a site for the firsttime, the default name is N2 Trunk1.

Identifier

Configure information about the integration such as trunknumber and a brief description. Selecting the Advanced buttonallows you to edit the BACnet Object Identifier.1

Configure

View the basic parameters of the integration just added.Summary

1 When selecting or adding a second N2 trunk, you must change the default trunk number (which is 1) on the Hardwaretab 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 SelectDefinition 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 methodis 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-downcombo box are valid N2 addresses because the list is updated each time a new controller object is created. Afterchoosing an N2 address, click Next. Auto Discovery is only available online for field devices. See the Adding N2Field 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 FieldDevice Wizard Configure screen appears (Figure 5).

The fields of the Configure screen have default data based on the previous information entered. This informationincludes the object type and naming parameters of the new controller being created. When you use the ManualDevice 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 thecontext 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 theAdding Extensions to an Object section in this document for more information.

Adding N2 Field Devices Online Using Auto DiscoveryWhen you are logged in to an NAE through the Metasys system, you can automatically discover field devices. Theauto discovery process cannot be used through the SCT; however, the devices that are discovered on the networkand added to the NAE database (through the Site Management Portal UI) can be uploaded to the SCT for archivingand 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 discoveredonline 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 AddingExtensions 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 databasein the SCT.

Adding Extensions to an ObjectAdd trend, totalization, alarm, and resource file extensions to increase the functionality of a field device or field pointobject.

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 theWizard that appears. See the Adding a Resource File Extension, Adding a Totalization Extension, or Adding anAlarm Extension sections in this document for more information.

4. Follow the prompts to configure the extension and click Finish when you are done. The ExtensionWizard appearswith 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 automaticallyafter 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 panelof the Field Device Extension Wizard. See the Adding N2 Field Devices Manually (Online or Offline) section forinstructions on adding N2 points.

Adding a Resource File ExtensionWhen using an HVAC PRO (PRN) file as a resource file, be sure you use the long print file format because it providesthe Metasys system with more information than the short print file format. For example, the long print file formatimports 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 changedto Metric. To prevent this problem, use the long print file format when importing an HVAC PRO file. To configure thelong 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 filesare imported in the Resource File Wizard. These files provide predefined point information that is used for the creationof N2 point objects in the Insert Field Point Wizard. Resource files enable the assisted point definition mode in theInsert Point Wizard. They also provide the view information used in the Engineering view of the N2 trunks. If the N2device 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 SelectFile 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 uponthe 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 textarea 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 ExtensionAdding trend extensions to objects allows you to collect historical data for one or more attributes of an object, thenview that data and/or have the data forwarded to an ADS/ADX for long-term storage. Use Trend Study to view Trendextensions frommultiple items at the same time. For more information on Trend Studies, refer to the Metasys systemHelp.

To add a trend extension:


1. In the Extensions Wizard, click the New button in the Trend row. The Insert Trend Wizard Select Attribute screenappears. The trended attribute defaults to Present Value. To trend a different attribute, click other... The attributelist 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 Extension1. 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 Extension1. In the Extensions Wizard, click the New button in the Alarm row. The Insert AlarmWizard 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 bottomand click Next.

Note: Click other to display a list of available attributes.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 Extension1. In the ExtensionsWizard, click the New button in the Averaging row. The Insert AveragingWizard 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 thebottom. Click Next.

Note: Click other to display a list of available attributes.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 Object1. 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. Forexample, you have to click both the Totalization delete button and the Averaging delete button to delete bothchecked 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 Database1. 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 SelectDefinition 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 ResourceFile 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 Definitionor Adding Field Points Using Manual Mode Definition sections in this document.

Adding Field Points Using Assisted Mode DefinitionIf you have created a Resource file extension for the field device to which you are adding points, then assisted modedefinition 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 pointsfrom the file. Each point that is mapped appears in the Points to Map Summary panel on the right and is alsomarked 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 Summarypanel. You can also un-map individual points by double-clicking the point in the middle panel or clickingthe Unmap All button. Selecting a folder in the middle panel displays the points mapped from that folderin the Points to Map Summary panel, whereas selecting the field device in the middle panel displays asummary 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 (Figure22).


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 Definition1. 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 Sourcescreen is pre-configured, based on the object type selected in the Select Definition Mode screen; however, onthe Select Data Source screen you can edit some properties of the point that cannot be edited in the Configurescreen. Depending on how many points of each type were added to a controller, the values available in thedrop-down boxes change so your available selections are valid. The Insert Point Wizard Select Data Sourcescreen 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 (Figure26).


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 Summaryscreen appears (Figure 28). Properties edited in the Manual Point Data Source page are not editable in thenormal Configuration view of the object.

Note: The object type and naming parameters of the new point appear in the Insert Point Wizard Summaryscreen. When you click Finish, the object is created and you are prompted to add extensions to the newpoint 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 LimitsAt 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 appropriatepoint limits, use these tables and the tables for the devices which you are defining them as. In all cases, use thelower of the point limits of the N2 FEC and of the device it is defined as. For example, if you are defining an FEC1611as an AHU, your point limit for AIs is 8, as defined in the AHU Point Mapping to NAEs table, rather than the potentialof 12 shown in Table 6.

Table 5: Point Limitations of FAC2611, FAC2612, and FAC3611Network Point AddressNetwork Point Type1-50AI

1-50BI

1-50AO

1-50BO

1-256ADF

1-256ADI

1-256BD

Table 6: Point Limitations of FEC1611 and FEC2611Network Point AddressNetwork Point Type1-12AI

1-12BI


Table 6: Point Limitations of FEC1611 and FEC2611Network Point AddressNetwork Point Type1-10AO

1-15BO

1-256ADF

1-256ADI

1-256BD

Table 7: Point Limitations of VMA1615, VMA1617, VMA1630, VMA1632, and VMA1832Network Point AddressNetwork Point Type1-8AI

1-8BI

1-8AO

1-8BO

1-256ADF

1-256ADI

1-256BD

N2 Device Point Mapping TablesThe N2 device point mapping tables allow you to manually map points into the NAE using the SCT. These tableslist the devices and points that you can manually map into the NAE.

AHUTable 8 describes AHU to NAE object mapping.

Table 8: AHU Point Mapping to NAEsCan Map to NAE Objects:Command AllowedNetwork Point AddressNetwork Point Type1

AI, AO, MSI, MSOYes1-8AI

AO, MSOYes1-8AO

BI, BO

BI 7-8 can be mapped to PC

Yes1-8BI

BOYes1-10BO

AI, MSI1-64ADF

AI, AO, MSI, MSOYesADF

65-256

AI, MSI1-64ADI

AI, AO, MSI, MSOYes65-256

AI, BI, MSI1-64BD

AI, AO, BI, BO, MSI, MSOYes65-2562

1 When configuring an FEC or FAC as an N2 AHU, UNT or VAV type device, the limitations of the new controller must beconsidered 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 NAECan Map to NAE ObjectsCommand AllowedNetwork Point AddressNetwork Point Type 1


AOYes1-8AO

BI, BO

BI 4 can be mapped to PC.

Yes1-37BI

BOYes1-14BO

AI, MSI1-64ADF


AI, MSI1-64ADI


AI, BI, MSI1-64

65-2562BD

AI, AO, BI, BO, MSI, MSOYes



VAV ControllerTable 10 describes VAV to NAE object mapping.

Table 10: VAV Point Mapping to NAECan Map to NAE Objects:Command AllowedNetwork Point AddressNetwork Point Type 1


AO, MSOYes1-8AO

BI, BO


Yes1-5BI

BOYes1-8BO

AI, MSI1-64ADF


AI, MSI1-64ADI


AI, BI, MSI1-64BD


1 When. configuring an FEC or FAC as an N2 AHU, UNT or VAV type device, the limitations of the new controller must beconsidered in addition to those in this table. See N2 FEC, FAC, and VMA Point Limits.


VMA 1400 SeriesTable 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 aregenerated if this rule is not followed.

Table 11: VMA Point Mapping to NAECan Map to NAE ObjectsCommand AllowedNetwork Point AddressNetwork Point Type1


AO, MSOYes1-8AO

BI, BOYes1-5BI

BOYes1-8BO

AI, MSI1-64ADF


AI, MSI1-64ADI


AI, BI, MSI1-64BD



Phoenix Fume Hood (PHX)Table 12 describes PHX to NAE object mapping.

Table 12: PHX Point Mapping to NAEsCan Map to NAE Objects:Command AllowedNetwork Point AddressNetwork Point TypeAI, AO, MSI, MSOYes1-40AI

AO, MSOYes1-8AO

BI, BO


Yes1-37BI

BOYes1-14BO

AI, MSI1-64ADF


AI, MSI1-64ADI


AI, BI, MSI1-64BD



Metasys Integrator UnitTable 13 describes the Metasys Integrator unit to NAE object mapping.

Table 13: Metasys Integrator Unit Point Mapping to an NAECan Map to NAE Objects:Command AllowedNetwork Point AddressNetwork Point TypeAI, MSI, MSOYes1-256AI

AO, MSOYes1-256AO


Table 13: Metasys Integrator Unit Point Mapping to an NAECan Map to NAE Objects:Command AllowedNetwork Point AddressNetwork Point TypeBI, BO, PCYes1-256BI

BOYes1-256BO

AI, AO, MSI, MSOYes1-256ADF

AI, AO, MSI, MSO, PCYes1-256ADI

AI, AO, BI, BO, MSI, MSOYes1-256BD

Vendor Device (VND)Table 14 describes VND to NAE object mapping.

Table 14: VND Point Mapping to an NAECan Map to NAE Objects:Command AllowedNetwork Point AddressNetwork Point TypeAI, MSI, MSOYes1-256AI

AO, MSOYes1-256AO

BI, BOYes1-256BI

BOYes1-256BO

AI, AO, MSI, MSOYes1-256ADF

AI, AO, MSI, MSO, PCYes1-256ADI

AI, AO, BI, BO, MSI, MSOYes1-256BD

ILCBefore you map ILC points to NAE objects, the ILC must be programmed. The point mapping table for ILCs is notvalid for MicroLite lighting controllers; instead, use the VND table. Table 15 describes ILC to NAE object mapping.

Table 15: ILC Point Mapping to an NAEDescriptionCan Map to NAE

Objects:OverrideStatus

CommandAllowed

Network PointAddress

Network PointType

Current month runtimelighting

Groups 1-32 (hours)

AI AONoYes1-32ADI

Previous month runtimelighting

Groups 1-32 (hours)

AI AONoYes33-64ADI

Lighting groups (manualoverride)

BOYesYes1-32BO

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 theuser’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 beforereporting online. An offline/online transition for the whole controller also generates exception reports. Table 16describes IFC to NAE object mapping.


Table 16: IFC Point Mapping to an NAENotesNAE Object

Description andUnits

Can Map to NAEObjects:


Network Point Type

Zone displays troublestatus (T).Overridestatus (O) = zonedisabled at fire panel.

Zone State (Nor/Alm)BI1-240BI

No trouble status (T)Zone Trouble (Nor/Tbl)BI1-240BD

UPS Battery Low(Ok/Alm)

BI241BD

AC Power Fail (Ok/Alm)BI242BD

Database Fault (Ok/Alm)BI243BD

General system alarmpoint

System Alarm (Nor/Alm)BI244BD

General system troublepoint

System Trouble(Nor/Tbl)

BI245BD

Alarm Silenced (No/Yes)BI246BD

TC-9100 Terminal Unit ControllerTable 17 shows how TC-9100 points can map to NAE objects. Table 18 provides more detail about the points (forexample, tag names, item descriptions, and which points are commandable). Use the .PRN file generated by HVACPRO software to determine which points are applicable to the specific TC-9100 controller you are mapping (forexample, 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 thesemethods (BO or AO/MSO) may be used. The override status flag for BD-2 is SUPC (BO-11). A command toBD-2 sets SUPC, and a release or auto command clears it.

Table 17: TC-9100 Point Mapping to an NAENAE Object TypeTC-9100 Network Point TypeAI1 to 10AI

1 to 2BD

1 to 421PMK

BI1 to 14BI

AO1 to 18AO

1 to 2BD

1 to 421PMK

BO1 to 13BO

1 to 2BD

1 All but PMK1 stored in EEPROM (maximum 10,000 write commands).


Table 18: TC-9100 Point Mapping (Detail)Item DescriptionTag NameOverride

StatusCommandAllowed


Network PointType

Process TemperatureAI11AI

Remote Temperature Setpoint BiasAI22AI

PressureAI33AI

Override InputAI44AI

DR-9100 onlyAI55AI

DR-9100 onlyAI66AI

SPARE7AI

SPARE8AI

Winter Authority CorrectionWAC9AI

Summer Authority CorrectionSAC10AI

Window SenseWIN1BI

Occupancy SenseOCC2BI

Air Quality SenseAIRQ3BI

Temporary ModeMODT4BI

Alternate ModeALT5BI

Supervisory Mode StatusSUPS6BI

SPARE7BI

SPARE8BI

Reverse Action LocalREVL9BI

Loop 1 ActiveL1A10BI

General AlarmALM11BI

Low Limit Mode ActiveAFM12BI

Three Speed Fan OverrideFOV13BI

Loop 3 ActiveL3A14BI

Output Programmable Module 1OCM1YesYes1AO






Working Set Point Loop 1WSP 1YesYes7AO






External Input 1XAI1Yes13AO





Network PointType




Analog Constant 5AC05Yes17AO

Analog Constant 6AC06Yes18AO

TRIAC 1D01YesYes1BO

TRIAC 2D02YesYes2BO

TRIAC 3D03YesYes3BO

TRIAC 4D04YesYes4BO

TRIAC 5D05YesYes5BO

TRIAC 6D06YesYes6BO

Shutoff ModeSOFFYes8BO

Startup ModeSTUPYes9BO

DR-9100 OnlyDAYYes10BO

Supervisory Mode Control (SeeBD-2 and Note)

SUPCYes11BO

Manual Operation ModeMANYes12BO

Reverse Action CommandREVCYes13BO

Mode Status: Night, Standby,Comfort, Off

MODSYes1BD

Mode Command: Night, Standby,Comfort, Off (See Note)

MODCYesYes2BD

K1Module 1Constant:

PM1K1Yes1PMK

K2PM1K2Yes12PMK

K3PM1K3Yes13PMK

K4PM1K4Yes14PMK

K5PM1K5Yes15PMK

K6PM1K6Yes16PMK

K7PM1K7Yes17PMK

K1Module 2Constant:

PM2K1Yes8PMK

K2PM2K2Yes19PMK

K3PM2K3Yes110PMK

K4PM2K4Yes111PMK

K5PM2K5Yes112PMK

K6PM2K6Yes113PMK

K7PM2K7Yes114PMK





Network PointType

K1Module 3Constant:

PM3K1Yes15PMK

K2PM3K2Yes116PMK

K3PM3K3Yes117PMK

K4PM3K4Yes118PMK

K5PM3K5Yes119PMK

K6PM3K6Yes120PMK

K7PM3K7Yes121PMK

K1Module 4Constant:

PM4K1Yes22PMK

K2PM4K2Yes123PMK

K3PM4K3Yes124PMK

K4PM4K4Yes125PMK

K5PM4K5Yes126PMK

K6PM4K6Yes127PMK

K7PM4K7Yes128PMK

K1Module 5Constant:

PM5K1Yes29PMK

K2PM5K2Yes130PMK

K3PM5K3Yes131PMK

K4PM5K4Yes132PMK

K5PM5K5Yes133PMK

K6PM5K6Yes134PMK

K7PM5K7Yes135PMK

K1Module 6Constant:

PM6K1Yes36PMK

K2PM6K2Yes137PMK

K3PM6K3Yes138PMK

K4PM6K4Yes139PMK

K5PM6K5Yes140PMK

K6PM6K6Yes141PMK

K7PM6K7Yes142PMK

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 toNAE objects. Table 20 provides more detail about the LCP/DC9100 points (for example, tag names and which pointsare commandable).


Table 19: LCP/DC9100 Point Mapping to NAENAE Object TypeLCP/DC9100 Network Point TypeAIAI, ADF

AOADF

BIBI, BD

BOBO, BD


Table 20: LCP/DC9100 Point Mapping (Detail)Item DescriptionTag NameOverride



Network PointType

Analog Input 1AI11AI








Digital Input 1DI11BI








Digital Output 3DO3YesYes1BO






Shut Off ModeSOFFYes7BO

Start Up ModeSTUPYes8BO

Output Numeric Module 1NCM11ADF




Analog Constant 1ACO1Yes5ADF




Output Control Module 1OCM1YesYes9ADF










Network PointType



Working Setpoint Control Module 1WSP1YesYes17ADF








Local SetpointControl Module 1:LSP1Yes25ADF

Proportional BandPB1Yes26ADF

Reset ActionTI1Yes27ADF

Rate ActionTD1Yes28ADF

Output High LimitHIL1Yes29ADF

Output Low LimitLOL1Yes30ADF

Standby STPChange

BSB1Yes31ADF

Off Mode STPChange

BOF1Yes32ADF

Deviation AlarmLimit

DA1Yes33ADF







Standby STPChange

BSB2Yes40ADF

Off Mode STPChange

BOF2Yes41ADF


DA2Yes42ADF





Network PointType







Standby STPChange

BSB3Yes49ADF

Off Mode STPChange

BOF3Yes50ADF


DA3Yes51ADF







Standby STPChange

BSB4Yes58ADF

Off Mode STPChange

BOF4Yes59ADF


DA4Yes60ADF







Standby STPChange

BSB5Yes67ADF

Off Mode STPChange

BOF5Yes68ADF


DA5Yes69ADF





Network PointType







Standby STPChange

BSB6Yes76ADF

Off Mode STPChange

BOF6Yes77ADF


DA6Yes78ADF







Standby STPChange

BSB7Yes85ADF

Off Mode STPChange

BOF7Yes86ADF


DA7Yes87ADF







Standby STPChange

BSB8Yes94ADF

Off Mode STPChange

BOF8Yes95ADF


DA8Yes96ADF

Output Logic Module 1LCM11BD




Digital Constant 1DCO1Yes5BD





Network PointType




DX-9100 Extended Digital ControllerTable 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 arecommandable).

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 NAENAE Object TypeDX-9100 Network Point Type

AI1 to 72AI

1 to 8ADF

1 to 72ADI

1 to 240PMK

1 to 96PMO

1 to 96PMA

AO1 to 72AO

1 to 8ADF

1 to 72ADI

1 to 240PMK

1 to 96PMO

BI1 to 72BI

1 to 32BD

1 to 64LRS

1 to 96PML

BO1 to 72BO

1 to 32BD

1 to 96PML

PC1 to 72ADI

1 to 96PMA

Table 22: DX-9100 Point Mapping (Detail)Item DescriptionTag NameOverride



Network PointType








Network PointType






Analog Input 1Expander 1:XT1AI19AI

Analog Input 2XT1AI210AI





Analog Input 7XT1AI715AI1






























Network PointType







Analog Input 7XT5AI747AI 1




































Network PointType



Digital Input 1Expander 1:XT1DI19BI

Digital Input 2XT1DI210BI



































Network PointType

































Analog Output 1AO1YesYes1AO










Network PointType



Analog Output 1Expander 1:XT1AO1YesYes9AO

Analog Output 2XT1AO2YesYes10AO




















Analog Output 6XT3AO6YesYes30AO1



Analog Output 1Expander 4:XT4AO1YesYes33AO1












Network PointType

































Shut Off ModeSOFFYes1BO

Start Up ModeSTUPYes2BO





Network PointType







Digital Output 1Expander 1:XT1DO1YesYes9BO

Digital Output 2XT1DO2YesYes10BO



































Network PointType











































Network PointType



DI1 Pulse CountCNT1Yes1ADI








DI1 Pulse CountExpander 1:XT1CNT1Yes9ADI

DI2 Pulse CountXT1CNT2Yes10ADI



























Network PointType





































Network PointType









Logic Constant 1DCO1Yes1BD


































Network PointType



Logic Result 1LRS11LRS








































Network PointType

































Network PointType

K1Module 1Constant:

PM1K1Yes1PMK

K2PM1K2Yes2PMK

K3PM1K3Yes3PMK

K4PM1K4Yes4PMK

K5PM1K5Yes5PMK

K6PM1K6Yes6PMK

K7PM1K7Yes7PMK

K8PM1K8Yes8PMK

K9PM1K9Yes9PMK

K10PM1K10Yes10PMK

K11PM1K11Yes11PMK

K12PM1K12Yes12PMK

K13PM1K13Yes13PMK

K14PM1K14Yes14PMK

K15PM1K15Yes15PMK

K16PM1K16Yes16PMK

K17PM1K17Yes17PMK

K18PM1K18Yes18PMK

K19PM1K19Yes19PMK

K20PM1K20Yes20PMK

K1Module 2Constant:

PM2K1Yes21PMK

K2PM2K2Yes22PMK

K3PM2K3Yes23PMK

K4PM2K4Yes24PMK

K5PM2K5Yes25PMK

K6PM2K6Yes26PMK

K7PM2K7Yes27PMK

K8PM2K8Yes28PMK

K9PM2K9Yes29PMK

K10PM2K10Yes30PMK

K11PM2K11Yes31PMK

K12PM2K12Yes32PMK

K13PM2K13Yes33PMK

K14PM2K14Yes34PMK

K15PM2K15Yes35PMK

K16PM2K16Yes36PMK





Network PointType

K17Module 2Constant:

PM2K17Yes37PMK

K18PM2K18Yes38PMK

K19PM2K19Yes39PMK

K20PM2K20Yes40PMK

K1Module 3Constant:

PM3K1Yes41PMK

K2PM3K2Yes42PMK

K3PM3K3Yes43PMK

K4PM3K4Yes44PMK

K5PM3K5Yes45PMK

K6PM3K6Yes46PMK

K7PM3K7Yes47PMK

K8PM3K8Yes48PMK

K9PM3K9Yes49PMK

K10PM3K10Yes50PMK

K11PM3K11Yes51PMK

K12PM3K12Yes52PMK

K13PM3K13Yes53PMK

K14PM3K14Yes54PMK

K15PM3K15Yes55PMK

K16PM3K16Yes56PMK

K17PM3K17Yes57PMK

K18PM3K18Yes58PMK

K19PM3K19Yes59PMK

K20PM3K20Yes60PMK





Network PointType

K1Module 4Constant:

PM4K1Yes61PMK

K2PM4K2Yes62PMK

K3PM4K3Yes63PMK

K4PM4K4Yes64PMK

K5PM4K5Yes65PMK

K6PM4K6Yes66PMK

K7PM4K7Yes67PMK

K8PM4K8Yes68PMK

K9PM4K9Yes69PMK

K10PM4K10Yes70PMK

K11PM4K11Yes71PMK

K12PM4K12Yes72PMK

K13PM4K13Yes73PMK

K14PM4K14Yes74PMK

K15PM4K15Yes75PMK

K16PM4K16Yes76PMK

K17PM4K17Yes77PMK


PM4K18Yes78PMK

K19PM4K19Yes79PMK

K20PM4K20Yes80PMK





Network PointType

K1Module 5Constant:

PM5K1Yes81PMK

K2PM5K2Yes82PMK

K3PM5K3Yes83PMK

K4PM5K4Yes84PMK

K5PM5K5Yes85PMK

K6PM5K6Yes86PMK

K7PM5K7Yes87PMK

K8PM5K8Yes88PMK

K9PM5K9Yes89PMK

K10PM5K10Yes90PMK

K11PM5K11Yes91PMK

K12PM5K12Yes92PMK

K13PM5K13Yes93PMK

K14PM5K14Yes94PMK

K15PM5K15Yes95PMK

K16PM5K16Yes96PMK

K17PM5K17Yes97PMK

K18PM5K18Yes98PMK

K19PM5K19Yes99PMK

K20PM5K20Yes100PMK

K1Module 6Constant:

PM6K1Yes101PMK

K2PM6K2Yes102PMK

K3PM6K3Yes103PMK

K4PM6K4Yes104PMK

K5PM6K5Yes105PMK

K6PM6K6Yes106PMK

K7PM6K7Yes107PMK

K8PM6K8Yes108PMK

K9PM6K9Yes109PMK

K10PM6K10Yes110PMK

K11PM6K11Yes111PMK

K12PM6K12Yes112PMK

K13PM6K13Yes113PMK

K14PM6K14Yes114PMK

K15PM6K15Yes115PMK

K16PM6K16Yes116PMK

K17PM6K17Yes117PMK





Network PointType


PM6K18Yes118PMK

K19PM6K19Yes119PMK

K20PM6K20Yes120PMK

K1Module 7Constant:

PM7K1Yes121PMK

K2PM7K2Yes122PMK

K3PM7K3Yes123PMK

K4PM7K4Yes124PMK

K5PM7K5Yes125PMK

K6PM7K6Yes126PMK

K7PM7K7Yes127PMK

K8PM7K8Yes128PMK

K9PM7K9Yes129PMK

K10PM7K10Yes130PMK

K11PM7K11Yes131PMK

K12PM7K12Yes132PMK

K13PM7K13Yes133PMK

K14PM7K14Yes113PMK

K15PM7K15Yes135PMK

K16PM7K16Yes136PMK

K17PM7K17Yes137PMK

K18PM7K18Yes138PMK

K19PM7K19Yes139PMK

K20PM7K20Yes140PMK





Network PointType

K1Module 8Constant:

PM8K1Yes141PMK

K2PM8K2Yes142PMK

K3PM8K3Yes143PMK

K4PM8K4Yes144PMK

K5PM8K5Yes145PMK

K6PM8K6Yes146PMK

K7PM8K7Yes147PMK

K8PM8K8Yes148PMK

K9PM8K9Yes149PMK

K10PM8K10Yes150PMK

K11PM8K11Yes151PMK

K12PM8K12Yes152PMK

K13PM8K13Yes153PMK

K14PM8K14Yes154PMK

K15PM8K15Yes155PMK

K16PM8K16Yes156PMK

K17PM8K17Yes157PMK

K18PM8K18Yes158PMK


PM8K19Yes159PMK

K20PM8K20Yes160PMK





Network PointType

K1Module 9Constant:

PM9K1Yes161PMK

K2PM9K2Yes162PMK

K3PM9K3Yes163PMK

K4PM9K4Yes164PMK

K5PM9K5Yes165PMK

K6PM9K6Yes166PMK

K7PM9K7Yes167PMK

K8PM9K8Yes168PMK

K9PM9K9Yes169PMK

K10PM9K10Yes170PMK

K11PM9K11Yes171PMK

K12PM9K12Yes172PMK

K13PM9K13Yes173PMK

K14PM9K14Yes174PMK

K15PM9K15Yes175PMK

K16PM9K16Yes176PMK

K17PM9K17Yes177PMK

K18PM9K18Yes178PMK

K19PM9K19Yes179PMK

K20PM9K20Yes180PMK





Network PointType


PM10K1Yes181PMK

K2PM10K2Yes182PMK

K3PM10K3Yes183PMK

K4PM10K4Yes184PMK

K5PM10K5Yes185PMK

K6PM10K6Yes186PMK

K7PM10K7Yes187PMK

K8PM10K8Yes188PMK

K9PM10K9Yes189PMK

K10PM10K10Yes190PMK

K11PM10K11Yes191PMK

K12PM10K12Yes192PMK

K13PM10K13Yes193PMK

K14PM10K14Yes194PMK

K15PM10K15Yes195PMK

K16PM10K16Yes196PMK

K17PM10K17Yes197PMK

K18PM10K18Yes198PMK

K19PM10K19Yes199PMK

K20PM10K20Yes200PMK





Network PointType


PM11K1Yes201PMK

K2PM11K2Yes202PMK

K3PM11K3Yes203PMK

K4PM11K4Yes204PMK

K5PM11K5Yes205PMK

K6PM11K6Yes206PMK

K7PM11K7Yes207PMK

K8PM11K8Yes208PMK

K9PM11K9Yes209PMK

K10PM11K10Yes210PMK

K11PM11K11Yes211PMK

K12PM11K12Yes212PMK

K13PM11K13Yes213PMK

K14PM11K14Yes214PMK

K15PM11K15Yes215PMK

K16PM11K16Yes216PMK

K17PM11K17Yes217PMK

K18PM11K18Yes218PMK

K19PM11K19Yes219PMK

K20PM11K20Yes220PMK





Network PointType


PM12K1Yes221PMK

K2PM12K2Yes222PMK

K3PM12K3Yes223PMK

K4PM12K4Yes224PMK

K5PM12K5Yes225PMK

K6PM12K6Yes226PMK

K7PM12K7Yes227PMK

K8PM12K8Yes228PMK

K9PM12K9Yes229PMK

K10PM12K10Yes230PMK

K11PM12K11Yes231PMK

K12PM12K12Yes232PMK

K13PM12K13Yes233PMK

K14PM12K14Yes234PMK

K15PM12K15Yes235PMK

K16PM12K16Yes236PMK

K17PM12K17Yes237PMK

K18PM12K18Yes238PMK

K19PM12K19Yes239PMK

K20PM12K20Yes240PMK

Channel 1Module 1 Output:PM1OU1YesYes1PMO

Channel 2PM1OU2YesYes2PMO



















Network PointType





































Network PointType

























Channel 1Module 10Output:

PM10OU1YesYes73PMO












Network PointType


PM11OU1YesYes81PMO









PM12OU1YesYes89PMO








Channel 1Module 1 LogicOutput:

PM1DO1YesYes1PML

Channel 2PM1DO2YesYes2PML









PM2DO2YesYes10PML











Network PointType


PM3DO1YesYes17PML









PM4DO1YesYes25PML









PM5DO1YesYes33PML









PM6DO1YesYes41PML












Network PointType


PM7DO1YesYes49PML









PM8DO1YesYes57PML









PM9DO1YesYes65PML









PM10DO1YesYes73PML












Network PointType


PM11DO1YesYes81PML








Channel 1Module 12 LogicOutput

PM12DO1YesYes89PML








Channel 1Module 1Accumulator:

PM1AC1Yes1PMA

Channel 2PM1AC2Yes2PMA








PM2AC1Yes9PMA












Network PointType


PM3AC1Yes17PMA









PM4AC1Yes25PMA









PM5AC1Yes33PMA









PM6AC1Yes41PMA












Network PointType


PM7AC1Yes49PMA









PM8AC1Yes57PMA









PM9AC1Yes65PMA









PM10AC1Yes73PMA












Network PointType


PM11AC1Yes81PMA









PM12AC1Yes89PMA








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 toNAE 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 onlyfrom 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 aDX-9100 XT Bus, see the two DX-9100 tables, Table 21 and Table 22.

Table 23: XTM (or XT) Point Mapping to the NAEDescriptionCan Map to NAE

ObjectsOverrideStatus

CommandAllowed


Network PointType

AINo1-8AI

BINo1-16BI

AONoYes1-8AO

BONoYes1-16BO

Writes restricted to0-32767. Only AO pointsare commandable in theNAE.

AI, PC, AONoYes1-8ADI

Auto/Manual Flags forOutputs.

BINo1-24BD


Table 24: XTM (or XT) Point Mapping (Detail)Item DescriptionTag NameCommand

AllowedNetwork PointAddress

Network PointType

Analog Input 1XP0:AI11AI








Binary Input 1XP1:1DI11BI

Binary Input 21DI22BI








Binary Input 1XP2:2DI19BI








Analog Output 1XP0:AO1Yes1AO

Analog Output 2AO2Yes2AO










Network PointType

Binary Output 1XP1:1DO1Yes1BO

Binary Output 21DO2Yes2BO







Binary Output 1XP2:2DO1Yes9BO








DI1 Pulse CountXTS:CNT1Yes1ADI








The following Tag Names are available only in the XTM:

Binary Output 1Manual Status

XP1:1DOM11BD


1DOM22BD


1DOM33BD


1DOM44BD


1DOM55BD


1DOM66BD


1DOM77BD


1DOM88BD




Network PointType


XP2:2DOM19BD


2DOM210BD


2DOM311BD


2DOM412BD


2DOM513BD


2DOM614BD


2DOM715BD


2DOM816BD

Analog Output 1Manual Status

XP0:AOM117BD


AOM218BD


AOM319BD


AOM420BD


AOM521BD


AOM622BD


AOM723BD


AOM824BD

TEC1100When adding the TEC1100 to an NAE, define the TEC1100 as controller type VND. Table 25 describes TEC to NAEobject mapping.

Table 25: VND Point Mapping to an NAE (TEC-1100 Thermostat)Override RangeNAEObjectCommandAllowedNetwork Point

Type/AddressPoint Name

0 to 48°C (28 to 124°F)N2 AIADI-1Room Temp

-48 to 48°C (-54 to 124°F)N2 AIYesADI-2Outdoor Temp

0 to 48°C (28 to 100°F)N2 AOYesADI-3Heating SP

0 to 48 °C (28 to 100°F)N2 AOYesADI-4Cooling SP


Table 25: VND Point Mapping to an NAE (TEC-1100 Thermostat)Override RangeNAEObjectCommandAllowedNetwork Point


0 to 48°C (28 to 100°F)N2 AOYesADI-5Setback Heating SP

0 to 48°C (28 to 100°F)N2 AOYesADI-6Setback Cooling SP

0 to 48° C (28 to 100°F)N2 AOYesADI-7Minimum Heat SP

0 to 48° C (28 to 100°F)N2 AOYesADI-8Maximum Heat SP

0 to 48° C (28 to 100°F)N2 AOYesADI-9Minimum Cool SP

0 to 48° C (28 to 100°F)N2 AOYesADI-10Maximum Cool SP

0 = Off/Auto, 1 = On/MANN2 BOYesBD-1Fan

0 = Off, 1 = Cool, 2 = Heat, 3 =Auto, 4 = E Ht Pump ‘O’

N2 MSOYesBD-2Mode

0 = Unoccupied, 1 = OccupiedN2 BOYesBD-3Occupancy

0 = Off, 1 = OnN2 BIBD-4W1 State-Heating

0 = Off, 1 = OnN2 BIBD-5W2 State-Heat

0 = Off, 1 = OnN2 BIBD-6Y1 State-Cooling

0 = Off, 1 = OnN2 BIBD-7Y2 State-Cooling

0 = Off, 1 = OnN2 BIBD-8G State-Fan

0 = °C, 1 = °FN2 BOYesBD-9Temp Units

0 = Normal, 1 = AlarmN2 BIBI-1Wrench BI

0 = Normal, 1 = AlarmN2 BIBI-2Temp Alarm

0 = Normal, 1 = AlarmN2 BIBI-3Filter BI

TEC210xWhen adding the TEC210x to an NAE, define the TEC210x as controller type VND. Table 26 describes TEC210xto NAE object mapping.

Table 26: VND Point Mapping to an NAE (TEC-210x Thermostat)Override RangeNAEObjectCommandAllowedNetwork Point


0 to 50°C (32 to 122°F)N2 AIYesADI-1Room Temp

-40 to 50°C (-40 to 122°F)N2 AIYesADI-2Aux Temp/Outdoor Temp

4.5 to 32°C (40 to 90°F)N2 AOYesADI-3Heating SP

12 to 37°C (54 to 100°F)N2 AOYesADI-4Cooling SP

4.5 to 32°C (40 to 90°F)N2 AOYesADI-5Setback Heating SP

12 to 37.5°C (54 to 100°F)N2 AOYesADI-6Setback Cooling SP

4.5° C (40°F)N2 AIADI-7Minimum Heat SP

4.5 to 32° C (40 to 90°F)N2 AOYesADI-8Maximum Heat SP

12 to 37.5° C (54 to 100°F)N2 AOYesADI-9Minimum Cool SP

37.5° C (100°F)N2 AIADI-10Maximum Cool SP

0 = Auto, 1 = On/MANN2 BOYesBD-1Fan

0 = Off, 1 = Cool, 2 = Heat, 3 =Auto, 4 = E Ht (Auxiliary Heat)

N2 MSOYesBD-2Mode


Table 26: VND Point Mapping to an NAE (TEC-210x Thermostat)Override RangeNAEObjectCommandAllowedNetwork Point


0 = Unoccupied, 1 = OccupiedN2 BOYesBD-3Occupancy

0 = Off, 1 = OnN2 BIBD-4W1 State

0 = Off, 1 = OnN2 BIBD-5W2 State

0 = Off, 1 = OnN2 BIBD-6Y1 State

0 = Off, 1 = OnN2 BIBD-7Y2 State

0 = Off, 1 = OnN2 BIBD-8G State-Fan

0 = °C, 1 = °FN2 BOYesBD-9Temp Units

0 = No Override, 1 = OverrideN2 BIBD-10Occupancy Override

0 = Off, 1 = OnN2 BIBI-1DI1

0 = Normal, 1 = AlarmN2 BIBI-2Temp Alarm

0 = Off, 1 = OnN2 BIBI-3DI2

Building Technologies & Solutions507 E. Michigan Street, Milwaukee, WI 53202

Metasys® and Johnson Controls® are registered trademarks of Johnson Controls.All other marks herein are the marks of their respective owners.© 2019 Johnson Controls

www.johnsoncontrols.comPublished in U.S.A.


n2 integration with the nae technical bulletincgproducts.johnsoncontrols.com/met_pdf/1201683.pdf ·...

Documents