Johnson Controls Metasys NCE25 series User manual

NCE25 Installation Instructions
Application
The Metasys® Network Control Engine (NCE) 25 Series controllers combine the network supervisor
capabilities and Internet IP network connectivity of a Metasys Network Automation Engine (NAE)
with the I/O point connectivity and direct digital control capabilities of a Metasys Field Equipment
Controller (FEC). These network engines provide a cost-effective solution designed for central plant
applications and large built-up air handlers.
NCE25 Series controllers provide integration to the following network protocols: BACnet/IP, BACnet
MS/TP, and N2 Bus and integrations to other building management communication technologies,
including Modbus®, M-Bus, and KNX. The network engine at 9.0.7 is shipped with the licenses and
drivers for all three communication protocols: Modbus, M-Bus, and KNX.
Note: LonWorks® is no longer supported for an NCE at Release 9.0.7. All NCEs that feature the
LonWorks integration remain at Release 9.0 or earlier.
Figure 3 shows the physical features of an MS-NCE2567-0 model. See Table 18 for NCE25 Series
model information and features.
Important: For existing custom integrations, contact your local Systems Integration Services
(SIS) team before an upgrade. Updated drivers can be provided on request.
Installation
Follow these guidelines when installing an NCE:
• Transport the NCE in the original container to minimize vibration and shock damage to the
network .
• Verify that all the parts shipped with the NCE.
• Do not drop the NCE or subject it to physical shock.
Parts included
• One NCE with removable terminal plugs.
• One data protection battery installed and connected when the NCE is shipped.
• One installation instructions sheet.
Materials and special tools needed
• Three fasteners appropriate for the mounting surface (M4 screws [#8] screws).
• One 20 cm (8 in.) or longer piece of 35 mm DIN rail, and appropriate hardware for mounting the
DIN rail.
Mounting
Location considerations
Follow these guidelines when mounting a network engine:
• Ensure that the mounting surface can support the NCE and any user-supplied panel or enclosure.
Part No. 24-10143-63 Rev. S
2018-12-17
Release 9.0.7
(barcode for factory use only)
*241014363S*

• Mount the NCE in a horizontal, upright orientation.
• Mount the NCE on an even surface in wall mount applications whenever possible. If you must
mount the network engine on an uneven surface, be careful not to crack the mounting clips or
network engine housing when tightening the screws. Use shims or washers to mount the NCE
evenly on the mounting surface.
• Mount the NCE in areas free of corrosive vapors, and observe the environmental limitations
listed in the Technical specifications section.
• Allow sufficient space to accommodate cable and wire connections. See Figure 1.
• Do not mount the network engine where the ambient temperature may exceed 50°C (122°F).
• Do not mount the network engine on surfaces that are prone to vibration or in areas where
electromagnetic or radio frequency emissions can interfere with network engine communication.
• Do not obstruct the network engine housing ventilation holes.
• Do not mount a power transformer below the network engine.
On applications where the network engine is mounted inside a panel or enclosure, follow these
additional guidelines:
• Do not install the network engine in an airtight enclosure.
• Do not install heat-generating devices in the enclosure with the network engine that may cause
the ambient temperature to exceed 50°C (122°F).
Wall mount applications
Use the holes in the three mounting clips for wall mount applications.
To mount the network engine on a wall or other vertical surface, complete the following steps:
1. Ensure that all three mounting clips are inserted into the back of the network engine housing
and then pulled outward and snapped firmly into the extended position. See Figure 2.
2. Mark the location of the three wall mount holes using the dimensions in Figure 1, or hold the
network engine up to the wall as a template and mark the locations.
3. Drill holes in the wall at the locations marked in Step 2 and insert wall anchors, if necessary.
NCE25 Installation Instructions2

Figure 1: NCE mounting screw hole dimensions,
(mm/in.), and mounting area requirements
4. Position the network engine and insert the screws through the holes in the mounting clips, and
carefully tighten all the screws.
Important: Do not overtighten the mounting screws. Overtightening the screws may
damage the mounting clips or NCE housing.
DIN rail mount applications
To mount the network engine on a DIN rail:
1. Securely mount a 20 cm (8 in.) or longer section of DIN rail horizontally and centered in the
required space.
2. Pull out the two mounting clips and snap them firmly. See Figure 2.
3NCE25 Installation Instructions

Figure 2: DIN rail and mounting clip features on the back of an NCE
3. Hang the network engine by the DIN rail hooks on the top track of the DIN rail, and position
the network engine DIN rail channel snugly against the tracks of the DIN rail. See Figure 2.
4. Push the bottom mounting clips up to secure the network engine on the DIN rail tracks.
To remove the network engine from the DIN rail, snap the bottom DIN clips to the outward
extended position and carefully lift the network engine off the DIN rail.
Enclosure mount applications
Mount the enclosure in accordance with the manufacturer’s instructions, and then mount the
network engine in the enclosure following the guidelines in the Location considerations and
Mounting sections.
NCE25 Installation Instructions4

NCE25 physical features
Figure 3: Front of NCE2567-0 showing physical features (power
and I/O terminal blocks, and NCE mounting clips not shown)
Table 1: Callout table for NCE25 physical features
Callout Description
1 The LED status indicators vary depending on the NCE model. See LED status
indicators.
2 Binary output, configurable output, and analog output terminal blocks are located
on the top side of the NCE. See Input and output wiring guidelines.
3 6-Pin modular Bus ports.
• FC Bus port for 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).
4 Data protection battery component.
5 NCE reset switch.
6 24 VAC Class 2 supply power terminal block is located on the top side of the NCE.
7 Display screen on specified models and displays NCE menus and commands.
8 Display navigation keyypad is used to navigate the display menus and initiate
commands.
9 Cover screw.
5NCE25 Installation Instructions

Table 1: Callout table for NCE25 physical features
Callout Description
10 FC Bus teminal block connects an NCE to an N2 Bus or FC Bus segment. It is not
available on all models.
11 End-of-Line (EOL) 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.
12 SA Bus Terminal Block connects the NCE field controller to the SA Bus.
13 Standard USB port.
14 Universal inputs and Binary input terminal blocks are located on the bottom side of
the NCE. See Input and output wiring guidelines.
15 Ethernet port RJ-45 8-pin modular jack connects the NCE to the IP network.
16 RS-232 Serial port.
17 Modem Jack - 6 pin modular jack, only on NCE models with optional internal
modems.
Wiring
Power supply, network, and communication connections
See Figure 3 for the location of the NCE’s power supply terminal, bus terminals and ports, USB port,
Ethernet port, and modem port.
Important: Modem functions are available with Metasys Release 9.0, but are not available if
you update the NCE25 to Release 9.0.7.
Note: Do not remove the red terminal block keys from the board mounted terminal blocks as
this can cause a removable terminal plug being plugged into the wrong terminal block, which
can cause the network engine to malfunction.
The NCE25 supports Modbus, M-Bus, and KNX integrations when upgraded to Release 9.0.7.
24~ supply power terminal block
The 24~ supply power terminal block is a gray, keyed, removable 3-terminal block located on the
top side of all NCE models. See Figure 3, Figure 11, and Figure 12.
In North America, the NCE25 requires a Class 2, 24 VAC, 25 VA minimum power supply. Outside
North America, use a 24 VAC SELV transformer at the appropriate rating. A minimum input voltage
of 20 VAC is required for the network engine to operate properly.
Note: The maximum power consumption of an NCE25 is 25 VA, but that does not include
power for internally sourced BO points. Applications that provide power to BO points and CO
points configured as BO points can require up to 125 VA of additional power over the 25 VA
minimum required for the NCE25.
SA Bus terminal block
All NCE models provide a brown, keyed, removable 4 terminal Sensor/Actuator (SA) Bus terminal
block. See Figure 3. Connect the 4-wire SA Bus cable to the SA BUS terminal block. See SA Bus rules.
SA Bus modular port
The 6-Pin modular SA Bus port is available on all NCE models. See Figure 3 and Figure 4. The SA Bus
port connects to the following:
NCE25 Installation Instructions6

• A Wireless Commissioning Converter (MS-BTCVT-1) to commission the network engine with the
Controller Commissioning Tool.
• A DIS1710 Local Controller Display to provide a display screen on NCE25 models without an
integral display screen.
• An NS Series Network Sensor to provide room temperature data to the network engine.
Figure 4: Pin number assignments for Sensor, SA
Bus, and FC Bus Ports on NCE, FEC, IOM, and VMA16
FC Bus terminal block
The blue, keyed, removable 4-terminal block FC BUS terminal block is designed for RS485 serial
protocol field buses and is available on NCE models that support N2 Bus or MS/TP FC Bus
applications. See Figure 3 for more information. You can complete the following connections:
• Connect the 3-wire N2 Bus to the FC BUS terminal block on NCE models that support N2 Bus
applications. See Figure 3 and N2 Bus rules for more information.
• Connect the 3-wire MS/TP FC Bus to the FC BUS terminal block on NCE models that support MS/
TP FC Bus applications. See Figure 3 and MS/TP FC Bus rules for more information.
The SHLD terminal on the FC BUS terminal block is a convenient terminal to connect cable shield
drains in daisy-chain bus applications that use shielded cable.
LonWorks network terminal block
Note: LonWorks® is no longer supported for an NCE at Release 9.0.7. All NCEs that feature the
LonWorks integration remain at Release 9.0 or earlier.
The blue, keyed, removable, 3-position LON terminal block connects a LonWorks network trunk
to NCE25 models that support a LonWorks network trunk. The Shield (SHD) on the LON terminal
block is soft grounded to the network engine chassis terminal, and you can use it as a convenient
terminal to connect cable shield drains in daisy-chain bus applications that use shielded cable.
FC Bus modular port
The 6-pin modular FC BUS port is available only on NCE models that support MS/TP FC Bus
applications (Figure 3 and Figure 4). Connect a Wireless Commissioning Converter (MS-BTCVT-1) to
the modular FC BUS port to commission the NCE with the CCT.
RS232C serial port
For a network engine updated with Release 9.0.7, the RS232C serial port only outputs information
during startup to a VT100 or a computer with a VT100 emulator. For a network engine at 9.0.7
configured with vendor integrations, the RS232C serial port provides a direct connection to a
Modbus RTU or M-Bus network using a standard 9-pin female data terminal equipment (DTE) to 9-
pin female DTE null modem cable. You can integrate only one device on this port.
7NCE25 Installation Instructions

Standard USB port
A network engine updated to Release 9.0.7, does not support modem functionality through
the USB port. However, for a network engine with vendor integrations, you can configure the
vendor integration to use an external flash drive connected to the USB port to capture diagnostic
information when the engine is in diagnostic mode.
Ethernet port
The Ethernet port, labeled ETHERNET, is an 8-pin RJ-45 network port for connecting the network
engine to Ethernet networks (10 or 100 Mbps). For a network engine configured for vendor
integrations, use this port for connecting a Modbus TCP, M-Bus TCP, or KNX network.
Internal modem
Modem functionality for NCE25 models that feature an internal modem is removed supported
when you update the NCE25 with Release 9.0.7. If your application requires a modem, image the
engine with Release 9.0.
Wiring rules for networks and field buses
All NCE25 Series models are designed to connect to Ethernet IP networks and support a single SA
Bus.
A network engine also supports an MS/TP field bus trunk, an N2 Bus trunk, and up to two vendor
integrations. For example, an NCE support two Modbus, two M-bus, or one of each. If a KNX
integration is required, an NCE25 supports only one KNX IP Integration.
IP Ethernet network rules
All NCE25 models are designed to connect to properly configured IP Ethernet networks. Observe
the IP Ethernet network rules in the following table.
Note: You can find the Media Access Control (MAC) address on a label on the network engine
housing.
Table 2: Ethernet network rules
Category Rules/maximums allowed
General Star topology with network hubs/switches.
Number of devices Maximum number of supervisory devices that you can connect to
one site in the Metasys system depends on the Metasys server. For
details, refer to Metasys System Configuration Guide (LIT-12011832).
2,000 m (6,561 ft) for plastic/glass fiber optic with external adapter.Line length and type
100 m (328 ft) CAT5 cable.
Terminations For 10/100 BaseT, no line terminators allowed.
MS/TP FC Bus rules
The MS/TP FC Bus connects FECs, VMA1600s, IOMs, TEC Series thermostats, and third-party MS/TP
controllers to NCE256x models.
NCE256x models support an FC Bus trunk with up to 32 MS/TP devices. Observe the rules in the
following table when designing and installing the connected FC Bus.
NCE25 Installation Instructions8

Table 3: FC Bus rules
Category Rules/maximums allowed
General One FC Bus with up to 32 MS/TP devices (on NCE256x models only).
Note: An FC port on a network engine can connect to only one
bus segment on an FC Bus.
Only a daisy-chain topology is allowed (no T or Star topology
configurations).
Number of devices One FC Bus Supports up to 32 MS/TP controllers on a single FC Bus
segment.
FC Bus can be up to 1,520 m (4,987 ft) using 0.6 mm (22 AWG) 3-wire
twisted, shielded cable.
Cable length for FC bus
When using fiber-optic connections: 2,010 m (6,594 ft) between two
fiber-optic modems.
Cable Stranded 0.6 mm (22 AWG) 3-wire twisted, shielded cable is
recommended.
Stranded 0.6 mm (22 AWG) 4-wire (two twisted-pairs) shielded cable
is acceptable.
Note: Ensure the + and - bus leads are a twisted pair. On
applications using 4-wire (two twisted-pairs) cable, isolate and
insulate unused conductor. Refer to the MS/TP Communications
Bus Technical Bulletin (LIT-12011034) for more information.
EOL termination on the FC
bus
The EOL switch must be set to On (or an EOL terminator installed)
on the two devices located at either end of each bus segment on
an FC Bus. The EOL switches must be set to Off (or EOL termination
disabled) for all other devices on the bus segment on an FC Bus. See
Setting the end-of-line switch for information on setting the EOL
switch.
SA Bus rules
The SA Bus connects the Metasys Input/Output Modules (IOMs), NS Series Network Sensors,
DIS1710 Local Controller Display, specified variable frequency drives, and Wireless Commissioning
Converter (MS-BTCVT-1) to an NCE.
Observe the rules in the following table when designing and installing the SA Bus for your
application.
Table 4: SA Bus rules
Category Rules/limits
General Each bus supervisor supports one SA Bus.
The SA Bus supports up to 10 devices.
Note: The SA Bus supervisor provides power for the NS
network sensors on the bus. Due to power limitations, only 4
of the 10 devices on a SA Bus can be NS sensors. The SA Bus on
NCE25 models that have an integral Local Controller Display do
not support an optional DIS1710 Local Controller Display.
Number of devices
supported on the bus
The SA Bus does not support repeaters.
9NCE25 Installation Instructions

Table 4: SA Bus rules
Category Rules/limits
365 m (1,198 ft) maximum bus length.
152 m (500 ft) maximum between an NS network sensor and the
bus supervisor FEC or VMA supplying power to the sensor) using
bus cable connected to the SA Bus screw terminal blocks.
30 m (98 ft) maximum length for network sensors using bus cables
connected to the 6-pin modular jack (6-Pin SA Bus port).
366 m (1,198 ft) maximum Bus Length.
Cable length for SA Bus
1.5 m (5 ft) maximum between the network engine and DIS1710
Local Controller Display.
Recommended bus cable
type
Screw Terminal Connections: 0.6 mm (22 AWG) Stranded 4-wire, 2-
Twisted Pairs, Shielded Cable for screw terminals.
Modular Jack Connections: 6-Pin Modular Connectors with 24 or
26 AWG 6-Wire, 3 Twisted-Pairs.
EOL termination on the SA
Bus
Each SA Bus supervisor has integral (fixed ON) EOL termination,
which typically provides sufficient EOL termination on a SA Bus.
Long SA Bus runs or persistent communication problems on a SA
Bus may require EOL termination at the last device on the SA Bus in
addition to the integral EOL termination at the SA Bus supervisor)
All NCE25 models are SA Bus supervisors.
N2 Bus rules
The N2 Bus connects N2 controllers to specified NCE25 models. NCE251x models support a single
N2 Bus trunk with up to 32 N2 devices.
Observe the rules in the following table when designing and installing the connected N2 Bus.
Table 5: N2 Bus rules
Category Rules/maximums allowed
One N2 trunk supported (on NCE251x models only).General
Only daisy-chained devices (with maximum stub length of 3 m [10
ft] to any device).
Number of N2 devices
supported
Up to 32 N2 devices supported on the N2 trunk.
1,500 m (4,921 ft) twisted pair cable.Cable length and type
2,000 m (6,561 ft) between two fiber modems.
Cable Solid or stranded 1.0 mm (18 AWG) 3-wire is recommended. Solid
or stranded 0.5 mm (24 AWG) larger 3-wire or 4-wire (two twisted-
pairs) is acceptable.
Note: Ensure the + and - bus leads are a twisted pair. On
applications using 4-wire (two twisted-pairs) cable, isolate and
insulate unused conductor.
Bus termination N2 devices are self-terminating and have no EOL setting.
NCE25 Installation Instructions10

Modbus RTU rules
The RS-232 port supports the connection of one Modbus RTU (RS-232) device. With the addition
of an RS-232/RS-485 converter and connection to the RS-232 port, up to 32 Modbus RTU (RS-485)
devices are supported. Observe the rules in the following table when designing and installing the
connected Modbus RTU Bus.
Table 6: Modbus RTU rules table
Category Rules/maximums allowed
General Supports one direct Modbus RTU (RS-232) connection to the RS232C port.
A connection of an RS-232/RS-485 converter to the RS232C port supports
up to 32 Modbus (RS-485) devices.
FC port does not support Modbus integration.
Number of Devices RS232C port supports one Modbus RTU (RS-232) device.
RS232C port with RS-232/RS-485 converter supports up to 32 Modbus
(RS-485) devices.
Cable Length RS-232 cable length can be up to 15 m (49.2 ft).
RS-485 cable length can be up to 1,520 m (4,987 ft).
Cable RS-232 stranded cable, 3-9 conductors, serial data grade, 20–24 AWG.
RS-485 stranded cable, 0.6 mm (22 AWG) 3-wire twisted, shielded cable is
recommended. Stranded 0.6 (22 AWG) 4-wire (two twisted pairs) shielded
is acceptable.
EOL Termination RS-232: requires no termination.
RS-485: End-of-line (EOL) termination must be set to On (or an EOL
terminator installed) on the two devices located at either end of each
bus segment on an RS-485 bus. The EOL switches must be set to Off (or
EOL termination disabled) for all other devices on the bus segment on an
RS-485 bus.
11NCE25 Installation Instructions

M-Bus protocol rules
Note: Unit load is a defined standby current. A device is permitted a current drain of one
unit load by default but may consume more if it is shown at the device (by an integer) and in
documentation. Use M-Bus Repeaters to increase the length and the number of unit loads
permissible.
Table 7: Rules for M-Bus protocol
Category Rules/maximums allowed
General Supports one direct M-Bus serial (RS-232) connection to the RS232C port.
Connection requires an RS232-to-M-Bus Level Converter on the RS232C
port.
FC port does not support M-Bus integration.
No restrictions in topology, but Bus topology is strongly recommended.
Number of devices Depends on level converter (logical maximum is 250 devices).
Length depends on cable resistance, capacitance, number of devices,
position of devices, and configured communication speed. Example
scenarios to help with calculation:
Baud
rate
Maximum number
of unit loads
Maximum
distance between
converter and
devices
Maximum
distance for entire
Bus
64 3,000 m (9,842 ft) 5,000 m (16,404 ft)
(2 x 1.0 mm (18
AWG), shield
recommended,
resistance < 90
Ohms)
64 1,000 m (3,281 ft) 4,000 m (13,123 ft)
(2 x 1.0 mm (18
AWG), shielded,
resistance < 90
Ohms)
2,400
250 350 m (1,148 ft) 4,000 m (13,123 ft)
(2 x 0.8 mm (20
AWG), shielded,
resistance < 30
Ohms)
Line length and type
9,600 64 350 m (1,148 ft) 4,000 m (13,123 ft)
(2 x 0.8 mm (20
AWG), shielded,
resistance < 30
Ohms)
NCE25 Installation Instructions12

Table 7: Rules for M-Bus protocol
Category Rules/maximums allowed
250 350 m (1,148 ft) 1,000 m (3,281 ft)
(2 x 0.8 mm (20
AWG), shielded,
resistance < 30
Ohms)
38,400 64 350 m (1,148 ft) 1,000 m (3,281 ft)
(2 x 0.8 mm (20
AWG), shielded,
resistance < 30
Ohms)
Cable Twisted pair cable (shielding optional).
Termination No termination.
KNX protocol rules
Table 8: Rules for KNX protocol
Category Rules/maximums allowed
General No restrictions in topology.
Number of devices Depends on chosen topology and cable type.
Line length and type Twisted pair cable recommended; length depends on cable resistance,
capacitance, number devices, position of devices, and communication
speed.
Cable Copper, solid and stranded wires with outer sheath, one- or two-
twisted pair; 0.8 mm to 1.0 mm (20 to 18 AWG).
Screen is required and must cover the entire diameter.
Drain wire: Diameter minimum 0.4 mm (26 AWG).
Termination No termination.
Manufacturer's Quality
management system
At least ISO 9002.
Dual trunk options
Table 9: Dual trunk options
Trunk type Supported dual trunk application
1 RS232
1 TCP
Modbus
2 TCP
1 RS232
1 TCP
M-Bus
2 TCP
13NCE25 Installation Instructions

Table 9: Dual trunk options
Trunk type Supported dual trunk application
1 RS232 Modbus
1 TCP M-Bus
1 RS232 M-Bus
1 TCP Modbus
Modbus and M-Bus
1 TCP Modbus
1 TCP M-Bus
Wiring
Important: Do not connect 24 VAC supply power to the NCE before finishing wiring and
checking all wiring connections. Short circuits or improperly connected wires may result in
permanent damage to the equipment.
Important:
• Use copper conductors only. Make all wiring in accordance with local, national, and regional
regulations. The NCE is a low-voltage device (<30 VAC) in North America and an extra low-
voltage device in Europe. Do not exceed the NCE electrical ratings.
• Do not remove the terminal block keys. The terminal block plugs and the terminal sockets
are keyed to fit together in the correct configuration only.
• Prevent any static electric discharge to the NCE. Static electric discharge can damage the
NCE and void any warranties.
• Ensure the network and field bus wiring meets the specifications, rules, and guidelines in
the Power supply, network, and communication connections section in this document.
Mount the network engine securely before wiring.
Follow these guidelines when wiring a network engine:
• Route the supply power wires and communication cables at least 50 mm (2 in.) away from the
vent slots on the sides of the network engine housing.
• Provide slack in the wires and cables. Keep cables routed neatly around the network engine to
promote good ventilation, LED visibility, and ease of service.
Wiring for N2, MS/TP, or Modbus RTU Protocol
1. Connect the Ethernet cable to the RJ-45, 8-pin Ethernet port as shown in NCE25 physical
features.
2. Connect the BAS network cables to the appropriate ports.
3. For Modbus RTU protocol using the RS232C serial port, use a cable to connect the RS-232/
RS-485 converter to the RS232C serial port on the network engine.
Note: The maximum cable length between devices connected though an RS-232 line
depends on the baud rate used. In general, at 9600 baud ensure the length does not
exceed 15 meters.
4. Wire from the RS-485 terminal on the converter to the RS-485 port on the vendor device. The
NCE25 Installation Instructions14

RS-485 bus is a two-wire network. See Figure 5.
a. Connect the converter's + A terminal to the device's + (or A) terminal.
b. Connect the converter's - B terminal to the device's - (or B) terminal.
c. If the device has a Signal Ground or Reference terminal, connect this to the converter's
CG2 terminal.
Figure 5: Connection between converter and device
5. To add additional vendor devices, terminate the wires from one device to the next as shown in
Figure 6. There must be no more than two wire connected to each terminal to ensure the daisy
chain configuration is used.
Figure 6: Daisy Chained Devices
Note: Ensure the completed wiring looks similar to the following figure.
15NCE25 Installation Instructions

Figure 7: Modbus RTU Wiring Detail Overview
6. Connect the 24 VAC supply power wires from the transformer to the removable power terminal
block plug on the network engine as shown in the following figure.
Figure 8: 24 VAC Supply Power Wiring
Note: Power supply wire colors may be different on transformers not manufactured by
Johnson Controls. Follow the transformer manufacturer’s instructions and the project
installation drawings.
7. Connect the 24 VAC supply power wires from the transformer to the converter. No additional
external power adapter is required. Terminate the hot and common wires as you need. The
network engine does not require an earth ground connection.
Note: The 24 VAC power should be terminated to all network devices so transformer
phasing is uniform across the devices. Powering network devices with uniform 24 VAC
supply power phasing reduces noise, interference, and ground loop problems.
Wiring for serial M-Bus Protocol
1. Connect the Ethernet cable to the RJ-45, 8-pin Ethernet port shown in NCE25 physical features.
2. Connect from the RS232C serial port on the network engine to the RS-232 connecter of the
level converter. Wire to terminals GND, RxD, and TxD as shown in NCE25 physical features.
3. Wire from the M- and M+ terminals on the level converter (Figure 9) and to use the line (daisy-
NCE25 Installation Instructions16

chain) topology, especially for long distances and many devices. Specific cabling can vary
depending on the topology and site.
Note: If the number of M-Bus unit loads or distances exceeds the specifications of a level
converter, youcan wire a M-Bus repeater to the converter to increase the number of unit
loads and distances. The converter shown in Figure 9 is capable of handling up to six units
loads, while other models can handle up to 100.
4. Connect the 24 VAC supply power wires from the transformer to the removable power terminal
block plug.
Note: Power supply wire colors may be different on transformers not manufactured by
Johnson Controls®. Follow the transformer manufacturer’s instructions and the project
installation drawings.
5. Connect the 24 VAC supply power wires from the transformer to the -/~ and +/~ terminals as
shown in Figure 9.
Figure 9: M-Bus Level Converter
Wiring for KNX Protocol
1. Connect an Ethernet cable to the RJ-45, 8-pin Ethernet port shown in NCE25 physical features.
2. Connect another Ethernet cable to the port on the front of the KNX gateway (Figure 10).
Note: Depending on the size of your KNX network, you can use either a KNX Interface or
KNX Router as an access point to the KNX network. The interface connects the network
engine to a single KNX line, while the router acts as both an interface and a line coupler
over Ethernet to connect the NCE to the network.
17NCE25 Installation Instructions

Figure 10: KNX/IP Interface Router
3. For a single KNX line, wire from the red and black terminals on the gateway to the devices. For
multiple KNX lines, wire from the red and black terminals on each gateway to the devices on
the same KNX line.
Note: Specific cabling can vary depending on the topology and site. See Wiring rules for
networks and field buses.
4. Wire each KNX gateway to its own dedicated power supply on the KNX line.
Wiring input and output terminals
NCE25 Series models support up to 33 hard-wired I/O points including:
• 7 BO points
• 4 CO points
• 4 AO points
• 8 BI points
• 10 UI points
See Figure 11, Figure 12, and Table 12 for more information.
I/O points are compatible with multiple types of input and output and most of the points are
configured in the CCT software.
NCE25 Installation Instructions18

Figure 11: NCE25 series output terminal blocks, Binary output jumpers,
and supply power terminal block as viewed from the top of an NCE25
Table 10: Call-out table for NCE25 series output terminal blocks, binary output jumpers, and supply
power terminal block as viewed from the top of an NCE25
Callout Description
1 Binary output - Two jumpers positioned for an internal source of power.
2 Binary outputs are 24 VAC Triac outputs.
3 Back of NCE (Flush to mounting surface).
4 Analog outputs can be defined as:
• Voltage Analog outputs (0-10 VDC)
• Current Analog outputs (4-20 mA)
5 24 VAC, Class 2 supply power terminal block. The center terminal is not used.
6 Configurable outputs can be defined as the following:
• Voltage Analog outputs (0-10 VDC)
• Binary outputs (24 VAC Triac)
7 Front of NCE.
8 Binary output - Four jumpers positioned for an external source of power.
9 Required jumper positons for setting a Binary output's power source.
Figure 12: Universal input and Binary input terminal
blocks as viewed from the bottom of an NCE25
19NCE25 Installation Instructions

Table 11: Call-out table for Universal input and Binary input terminal blocks as viewed from the
bottom of an NCE25
Callout Description
1 Universal inputs can be defined as the following:
• 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
2 Front of NCE.
3 Binary inputs can be defined as:
• Dry contact maintained
• Pulse counter mode (50 Hz at 50% Duty Cycle)
4 Back of NCE (Flush to Mounting Surface)
Terminal functions, ratings, requirements, and
wiring guidelines
Input and output wiring guidelines
Table 12 provides information and guidelines about the functions, ratings, and requirements for
the NCE input and output terminals and references to guidelines for determining proper wire sizes
and cable lengths.
In addition to the wiring guidelines in Table 12, observe these guidelines when wiring inputs and
outputs:
• Run all low-voltage wiring and cables separate from high-voltage wiring.
• Ensure all input and output cables, regardless of wire size or number of wires, consist of
stranded, insulated, and twisted copper wires.
• Shielded cable is not required for input or output cables.
• Shielded cable is recommended for input and output cables that are exposed to high
electromagnetic or radio frequency noise.
NCE25 Installation Instructions20