Johnson Controls 300 Series User manual

Technical Bulletin
Issue Date October 20, 2004
Network Control Module 300 Series
Network Control Module 300 Series....................................................3
Introduction......................................................................................................... 3
Key Concepts...................................................................................................... 7
NCM..................................................................................................................................7
ISA Bus Cards.................................................................................................................10
Installation Considerations..............................................................................................17
Design Considerations....................................................................................................19
NCM Cable Guidelines....................................................................................................29
Software Setup................................................................................................................44
Commissioning................................................................................................................47
Setting the N2 End-of-Line Switches ..............................................................................48
Setting the Memory Switches..........................................................................................49
NCSETUP for Windows Operating System (WNCSETUP).............................................49
NCM Idle Time ................................................................................................................52
Specifications and Order Codes .....................................................................................53
Detailed Procedures......................................................................................... 55
Replacing an NCM401 with an NCM300 ........................................................................55
Troubleshooting............................................................................................... 56
Troubleshooting the NCM...............................................................................................56
Communications .............................................................................................................56
Related Commissioning Problems ...................................................................................63
Short Haul Modems (Line Drivers)..................................................................................66
NCM Power-Up LEDs.....................................................................................................67
NCM Module Field Checks .............................................................................................71
NCM300/350 Troubleshooting........................................................................................72
Appendix A: Fire-Net NCM............................................................................... 74
©2004 Johnson Controls, Inc. www.johnsoncontrols.com
Code No. LIT-6360251 Software Release 12.00

Network Control Module 300 Series Technical Bulletin2
Related Documentation...................................................................................................74
System Configuration......................................................................................................75
Hardware.........................................................................................................................76
Interface Boards..............................................................................................................77
Mounting .........................................................................................................................81
Wiring..............................................................................................................................81
Downloading a Fire-Net NCM .........................................................................................86
Error Messages...............................................................................................................86
Order Numbers ...............................................................................................................87
Appendix B: NCM Maintenance....................................................................... 88
Introduction .....................................................................................................................88
NCM Maintenance Flowcharts........................................................................................88
Maintenance Quick Check..............................................................................................92
Field Inspection...............................................................................................................92
System Inspection.......................................................................................................... 92
Appendix C: NCM100 Power Supply Troubleshooting ............................... 105
Introduction ...................................................................................................................105
Products Affected..........................................................................................................105
Recommended Action...................................................................................................105
Preventive Action..........................................................................................................106

Network Control Module 300 Series Technical Bulletin 3
Network Control Module 300
Series
IntroductionThe Network Control Module 300 Series (NCM300) is the main
processing module in the Metasys® Network. Fully programmable,
the NCM coordinates and supervises the control activities for all
objects and control loops connected to it via Network Expansion Units
(NEUs) and Application Specific Controllers (ASCs). Table 1 shows
the models available for the NCM300 Series.
This document also shows how to replace an NCM401 with an
NCM300.

Network Control Module 300 Series Technical Bulletin4
Table 1: NCM300 Series NCMs
Model Description
NCM300 (NU-NCM300-0, -1) The NCM300 is connected to the Metasys network via the
N1 ARCNET® Local Area Network (LAN).
NCM311 (NU-NCM311-1) The NCM311 is the European version of the NCM300. Construction
and operation are similar to the NCM300; however, there are minor modifications that
are required to conform with European Safety and Emission standards that apply in all
European Union countries.
NCM350 (NU-NCM350-1) The NCM350 is functionally the same as the NCM300; however, it
can connect to either an ARCNET or Ethernet LAN.
You can upgrade from an NCM300 either by swapping the NU-NCM300-0 for an
NCM350, or by upgrading an NU-NCM300-1 at Rev. B or later using the
NU-NCM300-1 to NU-NCM350-1 Upgrade Kit (NU-ROM150). Instructions come with
the upgrade kit.
Note: Do not attempt to upgrade NU-NCM300-1s at Rev. A hardware or any
revisions of NU-NCM300-0s to NCM350s. If you have already tried to upgrade one of
these models, choose one of the following options:
Replace the ROM SIMM with an NU-ROM101. The NCM is now an NCM300 suitable
for ARCNET applications only.
Return the NCM to the repair center for upgrade to NU-NCM350-1. Go to the Products
Focus tab and click on Repair Center > NCM3n0Upgrade on The Advisor for details.
The physical difference between the NCM300 and the NCM350 is a Flash chip in
place of the ROM chip. This Flash chip contains everything that is in the ROM, along
with configuration data. The Flash chip also contains information about the ISA drivers,
and the user can download additional information to the Flash chip.
NCM350-8 Updated version of the NCM350. Contains 8 MB total memory. Replaces all previous
versions of NCM300s and NCM350s. Meets UL 864 UUKL for smoke control
applications.
NCM361 (NU-NCM361-1) The NCM361 is the European version of the NCM350. You can
purchase the NCM361 new, or you can upgrade an NCM311 either by swapping the
NU-NCM311-0 for an NCM361 or by upgrading the NU-NCM311-1 using the
NU-NCM311-1 to NU-NCM361-1 Upgrade Kit (NU-ROM150). Instructions come with
the upgrade kit.
Construction and operation are the same as the NCM350; however, there are minor
modifications that are required to conform with European Safety and Emission
standards that apply in all European Union countries.
NCM361-8 Updated version of the NCM361. Contains 8 MB total memory. Replaces all previous
versions of NCM311s and NCM361s.
Fire-Net NCM (NU-NCM300-FIRE/NU-NCMFIRE-1) The Fire-Net NCM is connected to the
Metasys Intelligent Fire Network. It is physically the same as the NCM300; however, it
is UL 864 UOJZ Listed for fire alarm use. The NCM300-FIRE comes with a
preinstalled ARCNET board, 2 MB additional memory, and a special power supply.
The NU-NCMFIRE-1 is the same as the NU-NCM300-FIRE, except that it has 8 MB of
memory. For information on the Fire-Net NCM, refer to the Metasys Intelligent Fire
Network Technical Bulletin (LIT-448196).
Smoke Control NCM (NU-NCM300-2, replaced by NU-NCM350-8) The Smoke Control NCM is physically
similar to the NCM300; however, it is UL 864 UUKL Listed. For information on the
Smoke Control NCM, refer to the Smoke Control Technical Bulletin (LIT-636330).

Network Control Module 300 Series Technical Bulletin 5
Unless otherwise specified, the information in this technical bulletin
refers to all NCM models in the NCM300 Series.
NCMs described in Table 1 require Metasys Release 8.0 software or
later except for the NU-NCM300-0, which requires Release 6.0 or
later, and the NU-NCM350-8, which requires Release 9.01 or later to
use all 8 MB of memory. When using Release 10.0 or later, the
WINCSETUP Information view shows the NCM350-8 with 6 MB
RAM before a download and 8 MB RAM after download. The
problem occurs within the flash memory program code; the
NCM350-8 is not faulty (maintains 8 MB memory throughout
download).
An NCM, via the N1 LAN, also has the ability to control activities for
objects located in other NCMs. An example of exchanged control
would be objects shed or restored by the Demand
Limiting/Load Rolling feature.
Different program sets download to an NCM to support a variety of
devices on its local bus. The program sets are of two types: Standard
Functionality and Migration Functionality. The Standard Functionality
supports one of the following applications:
• Standard NCM software supports: NEU devices (XMs, DCM),
Heating, Ventilating, and Air Conditioning (HVAC) devices such
as Air Handling Units (AHUs), Variable Air Volume (VAV)
controllers, Variable Air Volume Modular Assemblies (VMAs),
Unitary (UNT) controllers, Lab and Central Plant (LCP)
controllers, DX-9100s, Intelligent Fire Controller (IFC) panel,
Extension Modules (XTM), Generic Vendor Devices (VNDs),
Metasys Integrator® units, and lighting application specific
controllers. For details, see NCM Software Options Technical
Bulletin (LIT-636023).
• Fire Management software integrates the fire alarm system
IFC panel (IFC-2020 or IFC-1010) to the Metasys network, as well
as supporting XMs and HVAC devices (listed above) on the
N2 Bus. In this configuration, the IFC panel operates as a
stand-alone fire alarm system, the NCM is part of the Metasys
Intelligent Fire Network, and is not UL Listed for fire alarm
(UOJZ) or for smoke control (UUKL) applications. The NCM
connected to the IFC panel serves as an ancillary annunciation link
between the IFC panel and the Metasys system.
Note: If you are using the Fire-Net NCM on the Metasys
Intelligent Fire Network, refer to Appendix A: Fire-Net NCM in this
document for details on the software used with the Fire-Net NCM.

Network Control Module 300 Series Technical Bulletin6
• Intelligent Access Controller software integrates the IAC-600
access controller to the Metasys network, as well as supporting
XMs and HVAC ASCs (listed above) on the N2 Bus.
• As an alternative to the portable Network Terminal (NT),
Operator Terminal software connects a VT100 (or a Personal
Computer with VT100 emulation software) to the NCM. An NCM
with an Operator Terminal connected also supports NEUs,
Intelligent Lighting Controllers (ILCs), and HVAC Application
Specific Controllers (ASCs) (listed above).
In addition, an Operator Terminal connected to one NCM on the
N1 network can display, schedule, and control Fire, Access, or
S2 applications connected to other NCMs on the network.
The Migration Functionality builds pathways from the NCM to other
systems. While it can support any of the Standard Functionality
program sets described above, the advantage to Migration
Functionality is that it connects one of the following applications to
the Metasys system:
• S2 Migration software brings JC/85® field gear, object
information, and control directly into the Metasys system from the
JC/85 trunks.
• JC/85 Gateway allows Metasys object information to integrate
with the JC/85 Central Processing Unit (CPU). In the Gateway
application, the NCM serves as a high-level protocol translator,
making Metasys object information available to a JC/85 headend.
• The Network Port software lets you monitor and control the
Metasys system from a third-party host. The host computer can be
any of the many types that can communicate with an
ALLEN-BRADLEY® PLC-5® Programmable Logic Controller
(PLC-5 Family). The host, in turn, communicates with the
Network Port, which emulates some features of a
PLC-5 controller.
For complete information on the Network Port, refer to the Network
Port Technical Bulletin (LIT-6295050).

Network Control Module 300 Series Technical Bulletin 7
Key Concepts
NCM The NCM is a microprocessor-based intelligent node in the
Metasys network. It integrates three streams of information:
• system and database information
• application programs
• data and Input/Output (I/O) information arriving from the
communication ports
Figure 1 illustrates the basic components and functions of the NCM,
including callouts referenced throughout this document.
Note: NCM350-8s do not have Single Inline Memory Module
(SIMM) banks on the circuit board. They are delivered from the
factory with their maximum 8 MB of RAM.
12
6
2
RS-232
Port 4
NT
Port 4
Reload
Button
1
SIMMs
Nc3_1
Clock/
Calendar
Battery
Pack
Connector
J1J2J3J4
Power Supply
Connection
XMIT
RECV
LEDs
RS-232
Port 3
RS-232
Port 2
Battery
Pack
REF N2 N2
-
+
Power and
Battery
LEDs
Memory
Configuration
and EOL
Switches
XMIT
RECV
LEDs
XMIT
RECV
LEDs
XMIT
RECV
LEDs
N2
Port 1 4
3
5
7
8
9
10
11
PAL
Bank 1Bank 2
Figure 1: Block Diagram of the NCM

Network Control Module 300 Series Technical Bulletin8
Memory
Each system has different memory requirements in terms of database
size and capabilities for processing information. Dynamic Random
Access Memory (DRAM) memory expansion is available through
industry standard SIMMs. The NCM is delivered from the factory with
2 MB of on board memory. This provides 580 KB of database memory
(which is approximately equivalent to an NCM200 with an NIM204).
Note: The NCM350-8 comes from the factory with 8 MB of
memory. Metasys Release 6.0 through Metasys Release 9.0 only
recognize it as having 6 MB of memory. Metasys Release 9.01
recognizes the full 8 MB of memory. SW1 and SW2 are not used on
the NCM350-8.
For the -0, -1, and -2 versions of the NCM300/350, Johnson Controls
provides four DRAM memory configurations: 2 (default), 4, 6, and
10 MB. The SIMMs (Item 1 in Figure 1) are located under the battery
pack. DIP switches on the board (Figure 1: Callout 2) set the memory
configuration that has been installed.
Note: Disconnect and remove the battery pack before servicing the
DRAM SIMMs.
Table 2: NCM Memory Configuration Options
Total
Memory Database Memory SIMM Type/Qty Where Installed DIP Switch Setting
2 MB 580 KB None On board SW1 = up
SW2 = up 1 2 3 4 5 6 7 8
 EOL
4 MB 2 MB 1 MB SIMMs
(2) Bank 1
(J3, J4) SW1 = down SW2 = up 1 2 3 4 5 6 7 8
 EOL
6 MB 4 MB 1 MB SIMMs
(4) Bank 1 and 2 (J1, J2, J3, J4) SW1 = up
SW2 = down 1 2 3 4 5 6 7 8
 EOL
8 MB
(NCM350-8) 6 MB None On board SW1 = Not used
SW2 = Not used 1 2 3 4 5 6 7 8
 EOL
10 MB 8 MB 4 MB SIMMs
(2) Bank 1
(J3, J4) SW1 = down SW2 = down 1 2 3 4 5 6 7 8
 EOL
Notes: 1 or 4 MB SIMMs should be 9 bits wide on a 30-pin SIMM with a speed rating of 100 nS or faster.
Three-chip SIMMs use less power than 9-chip SIMMs (this can extend your battery backup time). See Table 6
in this document.
Memory is always upgraded in pairs (banks) of SIMMs.
Memory switches are not used in the NCM350-8. The NCM350-8 comes with 8 MB memory.

Network Control Module 300 Series Technical Bulletin 9
Microprocessor
The microprocessor applies the various supervisory programs to the
combined data, and exercises control over the modules and devices
that connect to the NCM via a local bus.
This supervision and control operate in the same manner when any of
the Standard Functionality program sets (Standard, Fire Management,
Intelligent Access Control, or Operator Terminal) are downloaded.
For Migration Functionality, the microprocessor translates data from
the field gear into compatible code for the target system:
• For S2 Migration, the microprocessor integrates the incoming S2
data into the Metasys system and extends NCM supervisory and
control functions over the objects on the S2 trunk.
• For JC/85 Gateway, the NCM microprocessor:
- executes commands from the JC/85 headend to objects on the
Metasys software side
- provides attribute information for all objects on the
Metasys software side
- translates and sends Metasys software reports to the
JC/85 devices
• In Network Port applications, the microprocessor:
- translates the host-generated requests to Metasys software
commands
- applies the various supervisory programs to the combined data,
supporting those functions that relate to the mapping of data
objects to the host computer (mapped analog data and binary
data objects)
All the software applications and supervisory routines take place
inside the NCM; database exceptions and historical files are uploaded
to the Operator Workstation (OWS) for reporting and archival
purposes.
80-Pin SIMM Board
This circuit board (Figure 1: Callout 3) provides Read-Only Memory
(ROM) to the NCM. (For the NCM350 or NCM361, Flash memory
replaces the ROM.)
Communications
The I/O subsystem supports a multi-user environment consisting of
network connections (N1, integrated N2, and N2E) and direct I/O
communication (NT or Operator Terminal [OT], and RS-232 ports).

Network Control Module 300 Series Technical Bulletin10
Local Bus: N2 (Port 1)
The N2 Bus communications also are provided by a built-in interface
(Figure 1: Callout 6). Devices on the N2 Bus constitute a local
network, controlled by the NCM. The NCM polls the devices
according to a user-set priority level, which is set at each device’s
Definition window.
The N2 connects in a daisy-chain fashion and provides the
transmission medium for modules installed within the base frame
(for example, a Digital Control Module or Point Multiplex Module), as
well as the external devices (application specific controllers including
the AHU, UNT, VAV, VMA, LCP, DX-9100, IFC-1010/IFC-2020
Intelligent Fire Controller, and IAC-600 Intelligent Access Controller).
For information on setting N2 End-of-Line (EOL) switches, see
Setting the N2 End-of-Line Switches in this document.
ISA Bus Cards The NCM is equipped with two ISA slots. These slots can hold 16 bit
ISA cards (Figure 1: Callouts 4 and 5). These slots allow for the use of
off-the-shelf communication cards (either 8 or 16 bit).
Metasys Release 8.0 and later support the following communication
cards in the NCM ISA slots:
• ARCNET card (Slot 1 only)
• Ethernet card (NCM350 and NCM361 only [Slot 1 only])
• LONWORKS® interface card; Slot 2 only (Figure 1: Callout 5)
• Non Plug and Play (PnP) serial cards (if downloading is desired,
use the NCM350 or NCM361)
• Media Interface Board (MIB-OWS) must be placed in Slot 2
(Figure 1: Callout 5) (NU-NCM300-FIRE or NU-NCMFIRE-1)
PnP modems and devices are not compatible with NCMs unless the
PnP feature can be disabled. Most new internal modems are designed
to be PnP compatible. Note that the Information
Technology-Acquisition Services (ITAS) Personal Computer (PC)
price list (pcprices.doc) on The Advisor contains an updated list of
recommended modems. Please check the list prior to purchasing an
internal modem. You can find the list by searching for the file name,
pcprices.doc, on The Advisor.

Network Control Module 300 Series Technical Bulletin 11
N1 Local Area Network
The N1 LAN allows communication with both OWSs and other
NCMs.
Whether you are using ARCNET card or Ethernet, each NCM and
OWS on the system contains a Node Manager task, whose
responsibilities include:
• broadcast once per minute that it is still online
• listen to other node managers to track on and offline trunks
• issue a time stamp for every global database in its memory
• compare the time stamps of its own databases to the received time
stamps of other node managers’ databases, and update the current
database if necessary
• monitor the printer for online or offline status
The node with the lowest address number on the network issues time
and date information once per day to ensure system synchronization. A
clock/calendar chip backs up time and date information. This Node
Manager also monitors broadcasts and issues online/offline advisories.
In the event of a severed N1 network, each separated LAN forms an
independent network.

Network Control Module 300 Series Technical Bulletin12
Table 3: N1 LAN Cards
Card Description
ARCNET
Card ARCNET LAN communication is provided by a standard ARCNET card (Ordered separately.
See Specifications and Order Codes for more information.) connected into ISA Bus Slot 1
(Figure 1: Callout 4).
Ethernet
Card An Ethernet card (Ordered separately. See Specifications and Order Codes for more
information.) connected into ISA Bus Slot 1 (Figure 1: Callout 4) of the NCM350 allows you to
connect the Metasys system directly to an Ethernet network. This allows you to communicate
with other devices on the Ethernet LAN, without the use of an Ethernet Router. Metasys
system functionality is the same on both the Ethernet and ARCNET LANs.
Note: You can use either an Ethernet or an ARCNET card in a single NCM350. If you wish
to have both ARCNET and Ethernet connections, you must use the ARCNET LAN and
connect to Ethernet using the Ethernet Router. For details, refer to the Metasys Ethernet
Router Technical Bulletin (LIT-6295035).
You cannot do smoke control on an Ethernet network where UL 864 is required. See the
Smoke Control Restrictions section of the Smoke Control Technical Bulletin (LIT-636330).
LONWORKS
Network The LONWORKS network allows communication between the Metasys network and
LONWORKS compatible devices using the LONWORKS compatible interface cards as follows:
NU-NET201-0 DX-9120 controllers on N2E Bus (N2E-TP78)
NU-NET202-0 DX-9121 controllers on N2E Bus (N2E-FTT10)
NU-NET203-0 LONWORKS compatible devices (requires Metasys Release 10.0 or later
software) (LON-FTT10)
NU-NET203-1 LONWORKS compatible devices (requires Metasys Release 11.00 or later
software) (LON-FTT10)
The LONWORKS interface card must be inserted in Slot 2 (Figure 1, Callout 5) of the NCM.
The LONWORKS network carries all communication between the NCM and the DX-912x or
LONWORKS compatible devices and between the devices themselves. The types of data that
are transferred across the network include:
commands from the NCM to the devices
automatic reporting of alarms and change-of-logic states from the DX-912x to the NCM (N2E
Bus only)
responses from the devices to the NCM, including identification and requested data values
complete databases for the DX-912x controllers (N2E Bus only)
time synchronization message from the NCM
analog and binary point data shared between devices
To meet FCC and CE standards for the N2E Bus installation, install ferrite clamps and beads.
For detailed information, refer to the LONWORKS N2E Bus Technical Bulletin (LIT-6364100).
Media
Interface
Board
The Media Interface Board (MIB-OWS) is a communication card that allows the Fire-Net
NCM to be connected to the Metasys Intelligent Fire Network. Insert the MIB-OWS in the
second ISA slot (Figure 1: Callout 5). Detailed information on setting up the NCM as a
Fire-Net NCM can be found in Appendix A: Fire-Net NCM of this document.
Serial Card A non PnP serial card can be placed in either ISA slot to allow direct connection of a printer
or OWS. See Table 11 for details.
Note: The serial card for Port 5 or Port 6 must be a 16-character FIFO (First-In, First-Out)
serial card. The serial card must use a 16550AF UART or equivalent. An example of a
16550AF serial card is the SIIG Model IO-1809. The card cannot be a PnP device.
Internal modems are not recommended for use with NCM300s unless
the PnP feature can be disabled. Most new internal modems are PnP,
which is not compatible with NCM300s.

Network Control Module 300 Series Technical Bulletin 13
Applications requiring a modem with an NCM300 Series device
should use an external, stand-alone modem. Keep the following in
mind when using an external modem with an NCM300:
• The maximum speed of a device connected to Port 2 or Port 3 is
19.2 K.
• Connect the external modem directly to either Port 2 or Port 3.
However, if the modem is connected to Port 3, that port is no
longer available for direct connect diagnostics.
• An external modem can be used in Port 5 or Port 6 (ISA slots) if a
non-PnP serial adapter board is installed. The serial adapter board
must be a 16-character First-In, First-Out (FIFO) card. The serial
card must use a 16550 UART chip or equivalent.
• Modems connected to the ISA slots via serial adapter boards
support higher baud rates than modems connected to Ports 2 or 3.
• Do not connect an external modem to Port 4.
• Only one dial-up OWS or Operator Terminal (OT) can be
connected to the NCM.
• Set a dial-up printer to its highest baud rate (that is, 9600).
Refer to Port Configurations: Standard Functionality under Design
Considerations in this document for a list of valid baud rates.
Note: You can download from an OWS to an NCM though a serial
card or external modem connected to an ISA slot if you are using an
NCM350 with Metasys Release 8.0 or later software. If you are using
an NCM300, you must download through Port 2 or 3.

Network Control Module 300 Series Technical Bulletin14
RS-232 Ports (Ports 2, 3, and 4)
Table 4 shows the three RS-232 ports (see Figure 1: Callout 7, 8, 9,
10), each connecting to communications options (the port applications
are described more fully in Table 5.
Table 4: RS-232 Ports
Port Description
Port 2 (See Figure 1: Callout 7)
an external modem, either Plain Old Telephone Service (POTS) or ISDN, which can connect to
remote operator devices such as a printer or OWS
a printer (direct or dial-up connection)
OWS (direct or dial-up connection)
Operator Terminal (direct or dial-up connection)
S2 Migration Trunk
JC/85 Trunk
Network Port communications
a second N2 Bus, via an MM-CVT101
Port 3 (See Figure 1: Callout 8)
printer (direct or dial-up connection)
OWS (direct or dial-up connection)
Operator Terminal (direct or dial-up connection)
Port 4 (See Figure 1: Callout 9 and 10)
Only one Port connection is allowed, to either the 9-pin RS-232 connector (Figure 1: Callout 9)
or the RJ-12 connector (Figure 1: Callout 10).
Operator Terminal (directly connected)
Network Terminal or NT Emulator

Network Control Module 300 Series Technical Bulletin 15
Table 5: RS-232 Applications
Application Description
S2 Migration Applications S2 communications are made via RS-232 Port 2 on the NCM to a TableTop
Modem (TTM). The TTM then interfaces with the JC/85 trunk.
The S2 parameters are identical to those of the JC/85 trunks.
The S2 Migration NCM does not accept a second local bus, either through the
other RS-232 port or via the integrated N2 Bus.
Gateway to JC/85
Applications The RS-232 connection on the JC/85 headend connects directly into the
RS-232 Port 2 on the Gateway NCM.
The Metasys software objects on Gateway are connected from throughout the
Metasys network via the N1 LAN in the identical manner of a Standard
Functionality NCM.
The Gateway NCM does not accept a second local bus, either through the
other RS-232 port or via the integrated N2 Bus.
Network Port Applications Network Port communications are made via RS-232 Port 2 on the NCM. Refer
to the Network Port Technical Bulletin (LIT-6295050).
When using the Operator Terminal program set, the VT100 (or PC with VT100
emulation software) connects to the NCM through either Port 2, 3, 4, or
through Port 5 or Port 6 (ISA Slots 1 or 2).
Port 2 direct or dial-up connection via an RS-232 (Figure 1:
Callout 7)
Port 3 direct or dial-up connection (Figure 1: Callout 8) (Dial-up
connection is not recommended here because you lose the
unconfigured laptop connection.)
Port 4 direct connection via an RS-232 (Figure 1: Callout 9) or using
an RJ-12 connection (Figure 1: Callout 10)
ISA
Slots 1 and 2 direct or dial-up connection (Figure 1: Callout 4 or 5)
Note: Port 5 is COM1 and Port 6 is COM2. If Port 5 is
defined, it cannot be used for ARCNET card or Ethernet.
Operator Terminal
Applications
When connecting an Operator Terminal, you do not need to use the Network
Terminal. An Operator Terminal provides a higher level of capability than the
Network Terminal, allowing you to read and write to each attribute of a Control
System object, as well as define and build databases for the Trend and
Totalization features. Refer to the Operator Terminal Technical Bulletin
(LIT-636015).
Network Terminal The Network Terminal, which provides local operator I/O, connects to the
RJ-12 connector (Figure 1: Callout 10) portion of Port 4.
The Network Terminal Emulator connects to the 9-pin RS-232 connector
(Figure 1: Callout 9) portion of Port 4.
Transparent Modem
You can connect a modem to any port on which a direct connection
can be made. Set the baud to the modem one step higher than the
modem communication. For example, if the modem baud is 28,800,
set the baud to 38,400. The higher setting gives extra time for the data
to be compressed when it arrives at the modem before it is transferred
over the telephone lines.

Network Control Module 300 Series Technical Bulletin16
Battery Pack
The battery pack (Figure 1: Callout 11) is secured to a cover and fits
over the SIMMs. It automatically recharges from the NCM and
maintains the operating system and databases in RAM for up to a
72-hour power failure. Refer to Table 6 for backup times according to
memory configuration. You can check on the battery’s status in three
ways: a Light-Emitting Diode (LED) indicator, under NCM
Diagnostics (NCM Misc Data), or by using WNCSETUP and choosing
the Command: Information option (good, bad, not installed).
The NCM arrives from the factory with the battery pack unconnected.
Connect the battery last when installing the NCM.
Table 6: Battery Backup Times
Memory Configuration Backup Time (Hours)
No SIMMs (base memory)* 72
With two 1 MB (3 chip) SIMMs 72
With two 1 MB (9 chip) SIMMs 50
With four 1 MB (3 chip) SIMMs 58
With four 1 MB (9 chip) SIMMs 34
With two 4 MB (3 chip) SIMMs 72
With two 4 MB (9 chip) SIMMs 50
* Standard for the NCM350-8
You must install the battery and power up the NCM for at least
12 hours to ensure the backup times listed in Table 6. As a guideline, if
you have an NCM with no additional SIMMs, you get about 10 hours
of backup time for each hour of charge time.
Power Up Conditions
The Network Control Module powers up in either a cold-start or a
warm-start condition. In the cold-start condition, the NCM
automatically requests the OWS to download the code and database
information into the NCM’s memory. Refer to the Operator
Workstation User’s Manual. In a warm-start condition, the code and
database are stored in memory, and the NCM is fully operational
following the initial diagnostic tests.
By retaining memory during a power cycle, the battery backup
provides a warm-start condition when power returns to the NCM. If a
Power Fail occurs and the battery is good, a Power Fail message is
entered into the NCM error log (NCM3xx and Metasys Release 11.00
or later).

Network Control Module 300 Series Technical Bulletin 17
A System Reload button (Figure 1: Callout 12) resets the NCM,
generating a request for a code and data download from the NC
archive node address. Table 7 describes power up terminology.
Table 7: NCM300/350 Power Up Terminology
Term Description Notes
Cold Start Power up restart condition. Runs diagnostics
and clears memory. Downloads code and data
files from OWS. Not affected by hardware
changes made while power is off.
Start up from no power condition with
battery disconnected or dead. Clears
all memory, runs diagnostics and
reloads all information.
Warm Start Power outage restart. Runs diagnostics but
does not clear memory or reload code and
data. Resets program counter to program start
address after testing unit integrity. It is
assumed that no hardware changes are made
while the power is off.
Start from power off condition with
battery connected and fully charged.
Does not clear memory, but does run
diagnostics.
Software Reset Already powered up restart. Runs diagnostics
but does not clear memory or reload code and
data. Resets program counter to program start
address after testing unit integrity.
Start from power on condition with
battery connected and fully charged.
Does not clear memory, but does run
diagnostics.
Software Reload Already powered up restart. Runs diagnostics,
clears memory, reloads code and data. Start from power on condition with battery connected and fully charged.
Clears all memory, runs diagnostics,
and reloads all information.
Reload Button When the Reload button is depressed, the
NCM requests a Software Reload. This causes
it to restart, run diagnostics, clear the memory,
and reload code and data.
Start from power on condition with
battery connected and fully charged.
Clears all memory, runs diagnostics,
and reloads all information.
!
IMPORTANT: Install the NU-ROM101 or NU-ROM150 before
applying power to the NCM. If either the NU-ROM101 or NU-ROM150 is not
installed when power is applied to the NCM, the NCM DRAM and NOVRAM
may be corrupted. If the NOVRAM is corrupted, replace the NCM.
Installation Considerations
When installing the NCM, note the following:
• Fasten all field ground wires under the top-most screw. This screw
contacts the ground plate of the EWC enclosure.
• Connect the battery as the last step in the installation.
• Cycling power before the battery is connected ensures that
memory is cleared. Not clearing the memory can cause problems
during commissioning, such as rebooting of the NCM.
Space and Load-Bearing
You must mount the NCM in an enclosure to meet local code
requirements. NCM (unmounted) dimensions and weight are:
15 W x 32 H x 14 cm D, 1.7 kg (6 x 12.4 x 5.5 in., 3.8 lb).

Network Control Module 300 Series Technical Bulletin18
Select a wall space or area with sufficient room to mount the enclosure
that contains the NCM. The load-bearing capacity of the wall also
must be able to support the unit. Table 8 indicates the dimensions of
the Universal Packaging Module (UPM), as well as the fully loaded
configuration weight of an NCM with enclosure.
Table 8: UPM Dimensions
Enclosure Dimensions
EN-EWC22-0 41 W x 41 H x 19 cm D, 5.0 kg (16 x 16 x 7.5 in., 11 lb)
EN-EWC35-0 41 W x 59 H x 19 cm D, 7.8 kg (16 x 23 x 7.5 in., 17 lb)
EN-EWC45-0 41 W x 77 H x 19 cm D, 9.7 kg (16 x 30 x 7.5 in., 21 lb)
Environment
The environment where you mount the NCM must have the following
characteristics:
• Ambient temperature limits for the NCM (0 to 50°C, 32 to 122°F)
based on convection cooling, as normally installed. Lower
temperatures can be accommodated by means of field-installed
enclosure heaters. Higher temperatures can be tolerated with some
additional forced cooling.
• Ambient humidity must range within 10-90% RH
(noncondensing).
• The environment must be free of conductive contaminants such as
normal cooking vapors and carbon dust.
IMPORTANT: Do not install the NCM in areas that contain conductive
contaminants. Conductive contaminants can result in damage to the NCM.
• Shielded cables are required for RS-232 connections.
• Shielded cables are required for the N1 and N2 networks only
when the NCM is mounted in close proximity to radio frequency
transmitters (500 to 1000 watts or larger), airport control towers,
and hospital nuclear or electronic imaging equipment (for example,
operating room, imaging lab).
• The NCM can operate while withstanding vibrations of 5 to 60 Hz
of up to 0.5G, and shocks of up to 2G lasting 10 ms. Nonetheless,
mount the unit on as stable a surface as possible.

Network Control Module 300 Series Technical Bulletin 19
Power
!
IMPORTANT: Install the NU-ROM101 or NU-ROM150 before
applying power to the NCM. If either the NU-ROM101 or NU-ROM150 is not
installed when power is applied to the NCM, the NCM DRAM and NOVRAM
may be corrupted. If the NOVRAM is corrupted, replace the NCM.
Consider the following power requirements for the NCM:
• The NCM requires between 90 and 230 VAC, 500 mA at 50/60 Hz
from a single-phase circuit. No switch settings or rewiring are
necessary to change from the 120 VAC to 230 VAC.
• Select a power circuit free of heavy equipment loads (for example,
large multiphase induction motors).
• The NCM must be referenced (grounded) to a green-wire earth
ground.
• Built in AC surge protection circuitry on the NCM is rated to
withstand surges of up to 6 kV @ 3 kA (IEEE 587 standard).
External surge protection is unnecessary, except in high-voltage
environments or in cases of extreme lightning.
• Do not use a Spade Bit to make a hole in the EWC for the power
conduit, or the NCM’s grounding strip will be damaged. Use a
Step-Bit or Greenlee Tool to make a hole for the conduit.
• Figure 4 shows how to wire the NCM power cord into the power
entry box in the EWC22. Once this wiring is complete, the switch
on the power entry box controls power to the NCM.
• Figure 5 shows how to wire the power connection into the
NCM311 or NCM361.
Design Considerations
Mounting
Mount the NCM in a suitable enclosure near its line voltage
connections. The unit is designed to fit into a variety of enclosures.
Figure 2 shows the overall mounting dimensions. Figure 3 shows the
NCM mounted in an EWC22. Figure 4 shows how to wire the NCM
power cord into the power entry box in the EWC22. For more
information on the EWC22, see the Universal Packaging Module
Technical Bulletin (LIT-6363070).

Network Control Module 300 Series Technical Bulletin20
ncm300dm
1 2 3 4 5 6 7 8
1 2345678
IN
OUT
RELOAD
POWER
ON
CONFIG.
ENDOF
LINE
a
b
D-RAM
-ATTENTION -
PLEASE DIS CONNEDT BATTERY
BEFORE INSTALLING MEMORY
BATTERY
NEXT SERVICE DATE:
REF
N2
-
N2 +
a
b
ISA
SLOTS
I
II
IV
COMM-
PORTS
III
POWER
SUPPLY
DISCONNECT
POWER BEFORE
SERVICING
DANGER
LINEVOLTAGE
INSIDE
31.496 cm
30.48 cm
10.16 cm
15.24 cm
(6.0 in.)
(0.375 in.)
0.9575 cm
(12.4 in.)
(4.0 in.)
(12.0 in.)
Figure 2: NCM Dimensions