NCE Technical Bulletin

Transcription

1 NCE Technical Bulletin MS-NCE25xx-x Code No. LIT Software Release 3.1 Issued November 9, 2007 Supersedes May 2, 2007 Document Introduction Related Documentation Network Control Engine Overview NCE Commissioning and Configuration Field Controller Configuration Supervisory Controller Commissioning Supervisory Controller Configuration System Configuration Tool (SCT) Archive Databases Controller Configuration Tool (CCT) Controller Application File (CAF) NCE SA Bus Input/Output Points Optional Display and Display Keypad General Procedures Procedure Requirements General Guidelines for Commissioning and Configuring an NCE Configuring a Laptop or Computer Configuring the NCE Field Controller Commissioning the NCE Supervisory Controller Configuring the NCE Supervisory Controller NCE Series Model Information Technical Specifications NCE

2 2

3 NCE Technical Bulletin Document Introduction This document describes the Metasys Network Control Engine (NCE) and outlines the general procedures for commissioning and configuring an NCE for operation. This document does not provide the detailed procedures for commissioning, configuring, operating, or troubleshooting an NCE, or using the Local Controller Display. Detailed procedures are available in related documents and referenced where appropriate. This document does not describe how to install or wire the NCE. Refer to the NCE25 Installation Instructions (Part No ) for information on and procedures for installing and wiring the NCE. This document does not describe how to integrate a Master-Slave/Token-Passing (MS/TP) bus, an N2 Bus, or a LONWORKS network trunk with the NCE. See Related Documentation for references to integration information and procedures. 3

4 Related Documentation Table 1: NCE Related Documentation For Information On See Document LIT or Part Number Installation of and Specifications for the NCE25 Series Controllers Commissioning a Network Automation Engine (NAE) and the NCE Supervisory Controller Installing the Application and Data Server (ADS), Extended Application and Data Server (ADX), and System Configuration Tool (SCT) on a Computer Using the SCT to Build, Edit, and Download an Archive Database Installing the Controller Configuration Tool (CCT) Software Using the CCT Software to Configure the NCE Field Controller Wireless Commissioning Converter Installation and Specifications, and Setting up a Bluetooth Wireless Adapter Installation of and Specifications for the DIS1710 Local Controller Display Operate and Troubleshoot the DIS1710 Local Controller Display Designing and Configuring an MS/TP Bus Application, a Field Controller (FC) Bus, and a Sensor-Actuator (SA) Bus Integrating an MS/TP Bus and MS/TP Field Devices into the Metasys System Integrating an N2 Bus and N2 Field Devices into the Metasys System Integrating a LONWORKS Network Trunk and LONWORKS Network Field Devices into the Metasys System NCE25 Installation Instructions Part No NAE Commissioning Guide ADS, ADX, and SCT Installation Instructions Wizard SCT Technical Bulletin 1. Use the wizard to generate instructions specific to your system. 2. This LIT number represents a printer friendly version of the Help. LIT Part No LIT CCT Installation Instructions Part No CCT Help LIT Wireless Commissioning Converter Installation Instructions Metasys CCT Bluetooth Technology Communication Commissioning Guide DIS1710 Local Controller Display Installation Instructions DIS1710 Local Controller Display Technical Bulletin MS/TP Communications Bus Technical Bulletin BACnet MS/TP Integration with NAE Technical Bulletin N2 Integration with the NAE Technical Bulletin LONWORKS Network Integration with NAE Technical Bulletin Part No LIT Part No LIT LIT LIT LIT LIT

5 Network Control Engine Overview The Network Control Engine (NCE) Series controllers combine the network supervisory capabilities and Internet Protocol (IP) network connectivity of a NAE with an MS/TP Field Equipment Controller (FEC). NCE Series controllers provide a cost-effective solution designed for central plants, including larger built-up air handlers, chiller plants, and boiler plants. The NCE brings together a supervisory controller and an MS/TP field controller into a single hardware package. The two controllers have separate hardware platforms with independent microprocessors and memory. The two NCE controller platforms are connected internally on an FC Bus. Each platform requires different application files to operate on the network. The NCE supervisory controller provides IP Ethernet network connectivity, the Metasys software User Interface (UI), and the network supervisory capabilities featured on an NAE35/NAE45. The NCE supervisory controller connects and operates like an NAE35/NAE45 on the Metasys network. See Figure 2 for an illustration of several NCEs on a Metasys network. The NCE supervisory controller also provides connectivity to and control of a specified field bus trunk with up to 32 field controllers (maximum). Depending on the model, an NCE supports either a BACnet MS/TP bus trunk, an N2 Bus trunk, or a LONWORKS network trunk. The NCE field controller supports an SA Bus and features 33 hardwired Input/Output (I/O) points. (See Input/Output Points on page 11.) The NCE field controller functions like an integral FEC. The NCE field controller is connected and mapped to the NCE supervisory controller. Input/Output Modules (IOMs) can be connected to the NCE s SA Bus to increase the I/O points controlled by the NCE. Note: The NCE supervisory controller is the MS/TP bus supervisor for the integral NCE field controller. All NCE supervisory controllers have a default, fixed device address value of 0 on the FC Bus. The integral NCE field controllers have a fixed device address value of 4 on the FC Bus. On NCE models that support an MS/TP bus (MS-NCE256x-xx), the first available device address value on the FC Bus is 5. Refer to the MS/TP Communications Bus Technical Bulletin (LIT ) for more information on device addresses on the MS/TP bus. Some NCE models feature an integral display with a navigation keypad (Figure 1). The display and keypad provide field controller information for setup, monitoring, and control of the NCE field controller features and I/O points. See Optional Display and Display Keypad on page 13 for more information. Some NCE models feature an internal modem that supports standard dial-up capabilities. Refer to the NAE Commissioning Guide (LIT ) for more information on and procedures for setting up an internal modem on an NCE. Figure 1 shows the physical features of an MS-NCE model. See Table 2 on page 17 for NCE25 Series model information and features. 5

6 O N Binary Output, Configurable Output, and Analog Output Terminal Blocks are located RJ-Style 6-Pin Modular Bus Ports FC Bus port (MS/TP models only) connects to a Wireless Commissioning Converter (MS-BTCVT-1). SA Bus port connects to a NS network sensor, a DIS1710 Local Controller Display, or a Wireless Commissioning Converter (MS-BTCVT-1). Wiring the on the top side of NCE. See Input/Output Points. 24 VAC Class 2 Supply Power Terminal Block is located on the top side of the NCE. LED Status Indicators The LED indicators vary depending on the NCE model. See LED Status Indicators. Data Protection Battery Compartment NCE Reset Switch Display Screen (on specified models) displays NCE menus and commands. Display Navigation Keypad is used to navigate the display menus and initiate commands. NCE FC BUS Cover Screw SA BUS FC BUS SA BUS COM SHLD FC EOL COM SA PWR FC Bus Terminal Block connects NCE to an N2 Bus or FC Bus segment. Standard USB Port End-of-Line Termination Switch sets the NCE as an EOL terminating device. Set the EOL switch according to the NCE position on the N2 or FC Bus segment. Ethernet Port RJ-45 8-pin modular jack connects the NCE to the IP Network. Modem Jack RJ-style 6-pin modular jack, only on NCE models with optional internal modems. Universal Input and Binary Input Terminal Blocks are located on the bottom side of the NCE. See Wiring RS-232 Serial Port FIG_NCE25_FEATURS SA Bus Terminal Block connects the NCE field controller to the SA Bus.. the Input/Output Points Note: NCE25 models have either a FC Bus terminal block or a L ON W ORKS terminal block but not both. Depending on the model, an FC Bus terminal block supports either an N2 Bus or an MS/TP FC Bus. (All NCE25 models have an SA Bus terminal block.) Figure 1: NCE Physical Features (Power and I/O Terminal Blocks, and NCE Mounting Clips Not Shown) 6

7 Printer Laptop with SCT and CCT for Configuring an NCE25 Web Browser ADS with SCT and CCT FIG: NCE_SYSTEM_DIAGRM Ethernet Patch Cable IP Network Internet NCE2560 NCE2510 NCE2520 Firewall Hardwire Input/Output Points SA Bus (MS/TP) FC Bus Field Trunk Hardwire Input/Output Points SA Bus Hardwire Input/Output Points SA Bus N2 Bus Field Trunk LONWORKS Network Field Trunk Figure 2: NCEs in a Metasys Network Web Browser 7

8 NCE Commissioning and Configuration Each Metasys network installation, commissioning, and configuration scenario is unique. The commissioning and configuration tasks, the task order, and the required attribute values (at commissioning) for an NCE are determined by the project workflow. In some scenarios, the NCEs may be commissioned and configured before they are installed and connected to the Metasys network; in other scenarios, the NCEs may be mounted and wired to the networks and I/O points before they are commissioned and configured. Note: Installation includes locating, mounting, wiring, and powering on an NCE. Refer to the NCE25 Installation Instructions (Part No ) for more information and detailed procedures for installing an NCE. To completely commission and configure an NCE for operation on the field network and the supervisory (IP) network, you must perform three general tasks: configure the NCE field controller for your NCE field controller application by creating a Controller Application File (CAF) in CCT and loading the CAF into the NCE field controller. See Field Controller Configuration. commission the NCE supervisory controller to connect to a computer, access the NCE Metasys UI, and set the basic NCE supervisory controller attributes. See Supervisory Controller Commissioning. configure the NCE supervisory controller for your network and field bus application by creating an archive database in SCT and downloading it to the NCE supervisory controller. See Supervisory Controller Configuration. Field Controller Configuration Field controller configuration prepares the NCE field controller for operation in a specific local field application. Note: The NCE field controller can be configured without commissioning and configuring the NCE supervisory controller. The NCE can operate in an application as a stand-alone field controller until the NCE supervisory controller is commissioned and configured. The first task in configuring the NCE field controller is to create a Controller Application File (CAF) in CCT for the NCE field control application. See Controller Application File (CAF) for more information. To configure the NCE field controller, download the CAF to the NCE field controller. You can download a CAF to an NCE field controller two ways: directly from a computer with CCT to the NCE field controller using a Wireless Commissioning Converter (MS-BTCVT-1) connected to the NCE SA Bus port (6-pin RJ-style modular jack) indirectly from a computer with SCT and CCT by attaching the CAF to the archive database in SCT and using the Passthru tool to download the CAF to the NCE field controller via the NCE Ethernet connection 8

9 Supervisory Controller Commissioning Commissioning the NCE supervisory controller establishes connectivity to the NCE, allows you to access the NCE Metasys UI, and prepares the NCE to receive an archive database download from the SCT. The first task in commissioning the NCE supervisory controller is to establish a connection between the NCE and a computer with Microsoft Internet Explorer. After a connection is established, you can access, navigate, and edit the NCE UI, and commission the NCE for operation on the supervisory network. Refer to the Metasys User Interface and Accessing the Metasys UI on an NAE sections in the NAE Commissioning Guide (LIT ) for typical network connection scenarios and information and procedures on accessing, navigating, and editing the NCE UI. After accessing the NCE UI, you can set the NCE supervisory controller attributes: object name and basic device parameters host name (Computer Name), domain name, and network parameters direct-connect and modem parameters time and date management parameters alarm and event parameters Simple Network Management Protocol (SNMP) messages and the network management destination modem dial-out and dial-up parameters Site Director status After commissioning the NCE supervisory controller to establish connectivity, UI access, and the supervisory controller s basic attributes, you can configure the NCE supervisory controller for your specific Metasys network application. Supervisory Controller Configuration Configuring the NCE supervisory controller prepares the NCE to operate in a specific Metasys network application, and communicate with, monitor, and control the NCE field controller and the field controllers on the NCE s field bus. After the NCE supervisory controller is configured, the NCE can compile, generate, and communicate information about site status, alarms, events, and trends. The NCE supervisory controller (typically) is configured by downloading a prebuilt archive database (from SCT) that contains the device objects, object references, attribute values, logic, graphics, user information, and other references and data required for the NCE supervisory controller to perform its specific tasks on the Metasys network. See Archive Databases. Refer to the SCT Technical Bulletin (LIT ) for information on creating and downloading archive databases. 9

10 In most configuration scenarios, the values in the archive database download overwrite the existing values on a commissioned NCE supervisory controller. After an NCE supervisory controller is configured with an archive database containing user information, you can set up the and pager Destination Delivery Agents (DDAs) and create specific alarm and event notifications for delivery to specific and pager destinations. System Configuration Tool (SCT) The SCT is an offline software tool used to create, edit, save, and restore the various archive and security databases that are used to configure Metasys system networks, ADSs/ADXs, NAEs, NCEs, and supported field devices. The SCT UI opens in Internet Explorer and has a similar look and function to the online Metasys system UI. The SCT allows commissioning of N2 devices by allowing HVAC PRO software, GX-Tool software, and XTM Configurator software to access the devices on the N2 Bus of an NCE. The SCT also allows commissioning of BACnet MS/TP devices using CCT software to access the devices on an NCE s MS/TP bus. The SCT Manager is a software tool that allows you to use multiple versions of SCT on your computer. The SCT and SCT Manager are separate software installations included on the ADS/ADX installation CD. The SCT provides a logic-simulation feature that allows you to simulate an online supervisory device and test a database s control logic prior to downloading it to an NCE. Using the SCT, you can view and configure multiple sites in one archive. Archive Databases A Metasys archive database contains the configuration information for ADSs/ADXs, NAEs, NCEs, controllers, field devices, and field points that make up a single site or multiple sites on a Metasys system network. Multiple Metasys archive databases, representing multiple sites, can reside on a single computer running the SCT. An NCE archive database, which resides in the NCE disk image, contains only the specific configuration information that makes up the network integrations, field devices, and field points that the NCE is supervising. Each NCE retains only its own archive database, but the NCE database also can be saved in a Metasys archive database on an ADS/ADX or another computer using the SCT. You can upload an NCE archive database to the SCT where it can be saved to a hard disk or other long-term storage media. You can also edit an NCE archive database offline in the SCT and download the edited archive database to the NCE. Controller Configuration Tool (CCT) The CCT is a software application used in conjunction with the SCT to commission, configure, and simulate FECs, Input/Output Modules (IOMs), and Variable Air Volume Modular Assembly (VMA) 1600s on an MS/TP bus. The CCT is included on the CD with the SCT. 10

11 Use the CCT worksheets and wizards to create and/or edit a Controller Application File (CAF), and then download the CAF to the NCE field controller. See Controller Application File (CAF) and Field Controller Configuration for more information on CAFs and downloading CAFs. Note: You must install CCT on the same computer as SCT to use the Ethernet Passthru feature in SCT to download a CAF. Controller Application File (CAF) A CAF is a resource file that contains all the logic components needed to represent a field control system that is monitored and controlled by an FEC, VMA1600, or NCE field controller. The CAFs for field controllers are much like the archive databases for supervisory controllers. A valid CAF is required to configure the NCE field controller. A CAF is created and edited in CCT and downloaded to a field controller. See Field Controller Configuration for more information on downloading CAFs to field controllers. CCT prompts you to save the CAF for each system you create. Saving the CAF allows you to access it offline and make changes, or copy and edit it for use in similar systems on other field controllers. The default location to save a CAF is C:\Documents and Settings\username. You cannot use certain characters when saving a Controller Application File. Illegal characters include: *? " < > / \ Refer to the CCT Help for detailed information on creating, editing, and downloading CAFs. NCE SA Bus The NCE field controller supports one Sensor-Actuator (SA) Bus and all NCE models have an SA Bus terminal block and an RJ-style modular SA Bus port. The SA Bus supports up to 128 I/O points. Refer to the MS/TP Communications Bus Technical Bulletin (LIT ) for more information on setting up and addressing an SA Bus. Input/Output Points The NCE field controller includes 33 hard wire I/O points, which can be configured for multiple types of inputs or outputs (Figure 3 and Figure 4). Most of the points are configured in the CCT software. The Binary Outputs are configured by positioning two jumpers next to the output terminal block (Figure 3). Each NCE model has: 10 Universal Inputs, each of which can be configured as either a Voltage Analog Input (0-10 VDC), Current Analog Input (4-20 ma), Resistive Analog Input, or a Dry-Contact Binary Input. See Figure 4. 11

12 8 Binary Inputs, each of which can be configured as either a Dry-Contact Maintained Input or a Pulse Counter Mode Input (100 Hz high-speed). See Figure 4. 4 Analog Outputs, each of which can be configured as either a Voltage Analog Output (0-10 VDC) or Current Analog Output (4-20 ma). See Figure 3. 7 Binary Outputs, each of which can be configured as either an internally powered or externally powered 24 VAC Triac output. See Figure 3. 4 Configurable Outputs, each of which can be configured as either a Voltage Analog Output (0-10 VDC) or a Binary Output (24 VAC Triac). See Figure 3. Binary Output 2 jumpers positioned for an Internal source of power. Binary Outputs are Analog Outputs can be defined as: 24 VAC Triac Outputs Voltage Analog Outputs (0-10 VDC) Current Analog Outputs (4-20 ma) Back of NCE (Flush to Mounting Surface) NCE_OUTPOINTS BO TYP EXT INT OUT8 OCOM8 OUT9 OCOM9 OUT10 OCOM10 OUT11 OCOM11 OUT12 OCOM12 OUT13 OCOM13 OUT14 OCOM14 OUT15 OCOM15 COM HOT Required jumper positions for setting a Binary Output's power source. BINARY CONFIGURABLE ANALOG 24V~ Front of NCE Binary Output 4 jumpers positioned for an External source of power. Configurable Outputs Voltage Analog Outputs Binary Outputs 24 VAC, Class 2 Supply Power Terminal Block (Center terminal not used.) can be defined as: (0-10 VDC) (24 VAC Triac) Figure 3: NCE Output Terminal Blocks, Binary Output Jumpers, and Supply Power Terminal Block as Viewed from the Top of an NCE Universal Inputs can be defined as: Voltage Analog Inputs (0-10 VDC) Current Analog Inputs (4-20 ma) Resistive Analog Inputs: 0-2k ohm RTD: 1k Nickel, 1k Platinum, or A99B SI NTC: 10k Type L or 2.225k Type 2 Dry Contact Binary Inputs UNIVERSAL Front of NCE Binary Inputs can be defined as: Dry Contact Maintained Pulse Counter Mode (100 Hz high-speed) BINARY IN11 ICOM 11 IN12 ICOM 12 IN13 ICOM 13 IN14 ICOM 14 IN15 ICOM 15 IN16 ICOM 16 IN17 ICOM 17 IN18 ICOM 18 NCE_INPOINTS Back of NCE (Flush to Mounting Surface) Figure 4: NCE Universal Input and Binary Input Terminal Blocks as Viewed from the Bottom of an NCE 12

13 Optional Display and Display Keypad Specified NCE models feature an integral display with display navigation keypad (Figure 1 on page 6). The display and keypad provide user interface to the NCE field controller (only). On NCE models without an integral display and keypad, an optional stand-alone display is available, which can be connected to the NCE on the SA Bus to provide the same functionality as an integral display and keypad. Refer to the DIS1710 Local Controller Display Technical Bulletin (LIT ) for more information on and detailed procedures for using the integral or remote display and display keypad. The screen displays NCE field controller information, field controller I/O point information, and command menus, which allow you to directly monitor the NCE field controller s I/O point status on the display and change I/O point settings using the display keypad. The display is configured in CCT and the display s configuration information is part of the NCE field controller s CAF. Refer to the CCT Help for information and procedures on configuring the display. General Procedures Procedure Requirements To commission and configure an NCE for your application, you need the following: an NCE with the Release 3.0 (or later) Metasys software installed a laptop with Internet Explorer Version 6.0 (or later) browser the Release 3.0 (or later) System Configuration Tool (SCT) software the Release 3.0 (or later) Controller Configuration Tool (CCT) software the NCE Ethernet Media Access Control (MAC) address (on the label on the NCE housing) Depending on your NCE application/project commissioning workflow, you may also need some of the following: a Wireless Commissioning Converter (MS-BTCVT-1) for downloading to the NCE field controller via the SA Bus port a null modem Serial cable an Ethernet crossover cable a unique IP address for the NAE on the Metasys network a copy of the NCE archive database that configures the NCE for your specific application and site You should also be familiar with or have access to the following documentation: NAE Commissioning Guide (LIT ) 13

14 SCT Technical Bulletin (LIT ) CCT Help in the CCT UI, or refer to a printer friendly version of the CCT Help (LIT ) Metasys Help in the Metasys UI and the SCT UI, or refer to Metasys system Help (LIT ) MS/TP Communications Bus Technical Bulletin (LIT ) DIS1710 Local Controller Display Technical Bulletin (LIT ) General Guidelines for Commissioning and Configuring an NCE There are many different workflows for commissioning and configuring an NCE and each project or site application has different requirements. Identical results can be achieved using different workflows. Consider the following guidelines when commissioning and configuring an NCE: The NCE supervisory controller and the NCE field controller are separate hardware platforms with different functions merged together into a single hardware package and internally connected on an FC Bus. Each controller has its own microprocessor and memory that is independent of the other. Each controller performs different functions on the Metasys network and requires different application files to operate on the network. You can apply the commissioning and configuration tasks to an NCE in almost any order, but the NCE supervisory controller can not operate without a valid archive database and the NCE field controller can not operate without a valid CAF. The NCE supervisory controller should be demoted from Site Director and an NAE or ADS/ADX should be assigned as its Site Director (unless the NCE is used in a stand-alone application). The archive database should be created, edited, and stored offline in the SCT, and then a copy of the database can be downloaded to the NCE supervisory controller at any time before or after installing the NCE. The archive database can be created with all of the objects for the field devices on the NCE s field bus in the database or with only some or none of the devices on the field bus. After an incomplete archive database is downloaded to the NCE, you can access the Metasys UI on the NCE and auto-discover the remaining field devices on the N2 or MS/TP trunk. Note: Each field device on the N2 or MS/TP trunk must have a valid configuration file so the NCE supervisory controller can discover it and upload the device file to the database. The archive database can be downloaded to the NCE supervisory controller from the SCT over a direct connection to the NCE Serial port. 14

15 The archive database can also be downloaded to the NCE supervisory controller from the SCT over an Ethernet connection to the Local Area Network (LAN). The CAF should be created, edited, and stored offline in CCT and then a copy of the CAF can be downloaded to the NCE field controller at any time before or after installing the NCE. A CAF from another field controller application can be edited in CCT to create a new CAF that supports the new NCE field controller application. The CAF can be downloaded directly to an NCE field controller from the CCT application on a laptop using a Wireless Commissioning Converter (MS-BTCVT-1) that is connected to the NCE s SA Bus port. The CAF can be attached to the archive database in the SCT before downloading the archive database to the NCE supervisory controller. The CAF can also be downloaded to the NCE field controller indirectly, by attaching the completed CAF to the application s archive database in SCT, downloading the archive database (and attached CAF) from SCT to the NCE supervisory controller, and then using the Passthru feature in the SCT to download the CAF to the NCE field controller. The CAF can be downloaded to the NCE field controller independent of the archive database, and the NCE field controller can operate as a stand-alone field controller independent of supervisory control. The NCE supervisory controller can be commissioned and configured later to provide network supervisory control of the NCE field controller. Configuring a Laptop or Computer The SCT and CCT Release 3.0 software must be loaded on your laptop before you can commission and configure an NCE. Your laptop must meet the minimum requirements for loading the SCT and CCT software. Refer to the ADS, ADX, and SCT Upgrade Installation Instructions Wizard (Part No ) for more information, minimum requirements, and detailed procedures for installing the SCT and CCT software on your laptop or desktop. Configuring the NCE Field Controller You can configure the NCE field controller before configuring the NCE supervisory controller and operate the NCE as a stand-alone field controller in your application. If you have not downloaded the CAF with the archive database using SCT and the Passthru feature to the NCE field controller, you must download the CAF directly to the NCE field controller. To configure the NCE field controller: 1. Create a CAF in CCT. (Refer to CCT Help.) 2. Download a copy of the CAF to the NCE field controller. There are two ways to download a CAF to the NCE field controller: 15

16 directly from a computer with CCT to the NCE field controller using a Wireless Commissioning Converter (MS-BTCVT-1) connected to the NCE SA Bus port (6-pin RJ-style modular jack) indirectly from a computer with SCT and CCT by attaching the CAF to the archive database in SCT and using the Passthru tool to download the CAF to the NCE field controller via the NCE Ethernet connection Commissioning the NCE Supervisory Controller Refer to the NAE Commissioning Guide (LIT ) for more information on and detailed procedures for commissioning the NCE supervisory controller. To commission the NCE supervisory controller: 1. Establish a network or direct connection to the NCE supervisory controller. 2. Access the NCE Metasys UI. 3. Establish basic NCE supervisory controller parameters in the NCE Focus screen. 4. Establish NCE supervisory controller network parameters. 5. Set time, date, time zone, and time synchronization for the NCE. 6. Demote NCE from Site Director. Note: In most applications, the NCE should not be the designated Site Director. 7. Set up the internal modem on NCE models with optional internal modems. 8. Establish , pager, and SNMP alarm and event notifications and destinations for the NCE supervisory controller. Configuring the NCE Supervisory Controller Configuring the NCE supervisory controller requires creating an archive database for your NCE application and downloading the database to the NCE supervisory controller. There are various scenarios to accomplish this task and the scenario you use depends on the job workflow. Refer to the SCT Technical Bulletin (LIT ) and the Metasys Help for information on creating, editing, and downloading an archive database. To configure the NCE supervisory controller: 1. Create an archive database in SCT for your NCE application. Note: You can also download a preliminary archive database to the NCE supervisory controller and use the Auto-Discovery feature in the NCE Metasys UI to discover and map any active devices and points connected to the NCE. After Auto-Discovery is complete, you should upload a copy of the enhanced archive database to the SCT. 2. Connect to the NCE supervisory controller and download the archive database to the NCE. 16

17 Note: You can also load a preliminary archive database to the NCE supervisory controller and use the Auto-Discovery feature in the NCE Metasys UI to discover and map the devices and points connected to the NCE. You should upload a copy of the enhanced archive database with the newly discovered devices and points to the SCT. Note: If the CAF for the NCE field controller application is available, you can attach the CAF to the archive database in SCT and download the CAF with the archive data base to the NCE using the Passthru feature in SCT. NCE Series Model Information Table 2 provides NCE series model information. Table 2: NCE Model Ordering Information Product Code Description Number MS-NCE25xx-xxx (Base Features on Each NCE25) MS-NCE MS-NCE MS-NCE MS-NCE MS-NCE MS-NCE MS-NCE MS-NCE MS-NCE MS-NCE MS-NCE MS-NCE Each NCE25 Series model requires a 24 VAC power supply and includes one RS-232-C serial port, one Universal Serial Bus (USB) port, one Ethernet port, and an MS-BAT Data Protection Battery. Each NCE25 Series model supports 33 hard wire Input/Output points. Supports one N2 Bus trunk with up to 32 N2 devices. Supports one N2 Bus trunk with up to 32 N2 devices. Includes an internal modem. Supports one N2 Bus trunk with up to 32 N2 devices. Includes an integral display. Supports one N2 Bus trunk with up to 32 N2 devices. Includes an integral display and internal modem. Supports one LONWORKS network trunk with up to 32 LONWORKS devices. Supports one LONWORKS network trunk with up to 32 LONWORKS devices. Includes an internal modem. Supports one LONWORKS network trunk with up to 32 LONWORKS devices. Includes an integral display. Supports one LONWORKS network trunk with up to 32 LONWORKS devices. Includes an integral display and an internal modem. Supports one FC Bus trunk with up to 32 MS/TP devices. Supports one FC Bus trunk with up to 32 MS/TP devices. Includes an internal modem. Supports one FC Bus trunk with up to 32 MS/TP devices. Includes an integral display. Supports one FC Bus trunk with up to 32 MS/TP devices. Includes an integral display and an internal modem. Table 3: NCE Accessories Ordering Information Product Code Description Number MS-BAT MS-BTCVT-1 AS-XFR100-1 AS-XFR010-1 Replacement data protection battery for NAE35, NAE45, and NCE25. Rechargeable NiMH battery: 3.6 V 500 mah, with a typical life of 10 years at 21 C (70 F) Wireless Commissioning Converter, with Bluetooth technology, for configuring and commissioning the NCE field controller and the devices on the NCE SA Bus Power transformer (Class 2, 24 VAC, 92 VA maximum output), with enclosure Power transformer (Class 2, 24 VAC, 92 VA maximum output), no enclosure 17

18 Technical Specifications NCE25 (Part 1 of 2) Power Requirement Power Consumption Ambient Operating Conditions Ambient Storage Conditions Data Protection Battery Processor Memory Operating System Network and Serial Interfaces (Depending on NCE model. See Table 2 for model information.) Analog Input/Analog Output Point Resolution Dimensions (Height x Width x Depth) Housing Mounting Shipping Weight Dedicated nominal 24 VAC, Class 2 power supply (North America), Safety Extra-Low Voltage (SELV) power supply (Europe), at 50/60 Hz (20 VAC minimum to 30 VAC maximum) 25 VA maximum for NCE25 only Note: The 25 VA rating does not include any power supplied to devices connected at the NCE Binary Outputs (BOs). BO devices connected to and powered by an NCE can require an additional 125 VA (maximum). 0 to 50 C (32 to 122 F), 10 to 90% RH, 30 C (86 F) maximum dew point -40 to 70 C (-40 to 158 F), 5 to 95% RH, 30 C (86 F) maximum dew point Supports data protection on power failure. Rechargeable NiMH battery: 3.6 VDC 500 mah, with a typical life of 5 to 7 years at 21 C (70 F); Product Code Number: MS-BAT MHz Renesas SH RISC processor 128 MB Flash nonvolatile memory for operating system, configuration data, and operations data storage and backup 128 MB Synchronous Dynamic Random Access Memory (DRAM) for operations data dynamic memory Microsoft Windows CE embedded One Ethernet port; 10/100 Mbps; 8-pin RJ-45 connector One optically isolated RS-485 SA Bus port; with a pluggable and keyed 4-position terminal block (all NCE25 models) One optically isolated RS-485 port; with a pluggable and keyed 4-position terminal block (only on NCE25 models that support an N2 Bus or MS/TP bus trunk) One LONWORKS port; FTT10 78 Kbps; pluggable, keyed 3-position terminal block (only on NCE25 models that support a LONWORKS network trunk) One RS-232-C serial port with standard 9-pin sub-d connector that supports standard baud rates One USB serial port with standard USB connector Option: One 6-pin RJ-12 jack for connecting to internal modem; up to 56 Kbps Analog Input Points: 16-bit resolution Analog Output Points: 16-bit resolution, mv accuracy 155 x 270 x 64 mm (6.1 x 10.6 x 2.5 in.) Minimum mounting space required: 250 x 370 x 110 mm (9.8 x 14.6 x 4.3 in.) Plastic housing Plastic material: ABS and polycarbonate Protection: IP20 (IEC60529) On flat surface with screws on three mounting clips or a single 35 mm DIN rail 1.2 kg (2.7 lb) 18

19 NCE25 (Part 2 of 2) Compliance United States UL Listed, File E107041, CCN PAZX, UL 916, Energy Management Equipment FCC Compliant to CFR47, Part 15, Subpart B, Class A Canada UL Listed, File E107041, CCN PAZX7, CAN/CSA C22.2 No. 205, Signal Equipment Industry Canada Compliant, ICES-003 Europe CE Mark, EMC Directive 89/336/EEC, in accordance with EN (2001) Generic Emission Standard for Residential and Light Industry and EN (2001) Generic Immunity Standard for Heavy Industrial Environment Australia and New Zealand C-Tick Mark, Australia/NZ Emissions Compliant BACnet International BACnet Testing Laboratories (BTL) Listed BACnet Building Controller (B-BC) The performance specifications are nominal and conform to acceptable industry standard. For application at conditions beyond these specifications, consult the local Johnson Controls office. Johnson Controls, Inc. shall not be liable for damages resulting from misapplication or misuse of its products. Controls Group 507 E. Michigan Street Milwaukee, WI Metasys is a registered trademark of Johnson Controls, Inc. All other marks herein are the marks of their respective owners Johnson Controls, Inc. 19 Published in U.S.A.