LONWORKS Systems Manual 1162 Networking Section Technical Bulletin Issue Date 0101

LONWORKS Network Layout

Introduction Page 3

About LONWORKS Technology 3 LONWORKS Compatible Features Implemented in the Metasys System 4 Notes Regarding the N2E Bus 6 Definition of Terms 6 Theory of Operation 13 Components 15 Network Layout Considerations 20

Installation Procedures 25

General Guidelines 25 Installing LONWORKS Card into NCM350/361 26 Terminations (Connecting Network Wiring) 29 Recording the Neuron ID 33

Commissioning Procedures 35

Overview 35 Checking Network Installation 35 Power Up 35 Metasys Supervisory System Only (Unbound) 36 Peer-to-Peer (Bound or Fully Bound) 37

Overview 39 Checking Network Wiring 40 Checking End-of-Line Terminations 42 Checking Cable Lengths 42 • Checking LONWORKS Devices 42 Checking Number of Defined Devices 43

Ordering Codes 45

Johnson Controls Code Numbers 45

2 Networking—LONWORKS Network Layout Introduction

About LONWORKS network technology was developed by Echelon® LONWORKS Corporation to provide an industry-standard local operating network. The Technology network is built around the Neuron® chip, a microprocessor that combines three Central Processing Units (CPUs) into one chip. The Neuron chip is an integral component of any LONWORKS compatible device. The following terms are used in conjunction with LONWORKS network technology:

LONWORKS is the general term covering all aspects of the network technology including the physical media layer, the protocol, data type definition, Neuron chip, transceivers, and the specifications to implement a local operating network.

LonTalk® Protocol is the protocol used on LONWORKS networks to standardize communication. It defines a standard way for devices to exchange information.

The LONMARK® Interoperability Association issues guidelines to ensure that devices from different vendors can coexist and cooperate on a single LONWORKS network. The organization certifies specific devices as LONMARK compliant. The addressing schemes and transmission technology used on LONWORKS compatible systems make them more like Local Area Networks (LANs) than single-segment, bus-based systems. This provides extreme flexibility in network topology design, where routers, bridges, and repeaters can be used to allow control devices on different segments of the network to communicate with each other and/or a supervisory system. LONWORKS technology also supports the use of different physical transport media on the same network, such as twisted-pair wiring, twisted-pair with device supply voltage (Link Power), power line A- and C-band, fiber optic links, etc. In addition, traditionally separate subsystems such as Heating, Ventilating, and Air Conditioning (HVAC), lighting, space comfort, and sunblind control can be combined on the LONWORKS network to provide more comprehensive coordination and control. LONMARK compliance ensures that the devices of these subsystems can communicate with each other, even if they are supplied by different manufacturers. For more information on LONWORKS technology, contact the LONMARK Interoperability Association (www.lonmark.org) or Echelon Corporation (www.echelon.com).

Networking—LONWORKS Network Layout 3 LONWORKS The Metasys® Building Automation System (BAS) fully supports the Compatible LONWORKS network and LONMARK compliant devices. Features The Metasys system implements the following LONWORKS technology Implemented in features: the Metasys System high speed network (78K baud) over standard, twisted-pair wiring support of an NCM350/361 with a LONWORKS interface card installed in an ISA slot of the NCM (in this document, this is referred to as the NCM350). The LONWORKS interface card uses the FTT-10 transceiver (Free Topology Transceiver) for twisted-pair wiring as standard, and is also compatible with devices using the Link Power LPT-10 transceiver connected to the same network segment.

support of the LONMARK compliant TCU series, VMA1200 Series, and DX-9200 controllers with FTT-10 transceivers Note: In the DX-9200 controller, only the network variables can be accessed by the NCM350 via the LONWORKS network; the other controller items may only be read and set by the GX-9100 Configuration Tool. Refer to the DX-9200 LONWORKS Compatible Digital Controller Technical Bulletin (LIT-1162250)

support of LONMARK compliant third-party devices monitoring of up to 127 devices per NCM350 (may require at least one repeater on the LONWORKS network segment, see Network Layout Considerations later in this document)

device configuration mapping tables for each supported LONWORKS compatible device (refer to the LONWORKS Compatible Devices Supported by NCM350 Technical Bulletin [LIT-1162100]) peer-to-peer communications configured on the network using LONWORKS network configuration tools from various suppliers The Metasys system implements LONWORKS technology with Metasys Release 10.01 or later. The NCM350 enables supervisory communication for monitoring a network of LONMARK compliant controllers, and for event reporting at the Metasys Operator Workstation. The NCM350 is a supervisory controller, but does not take part in the exchange of data among the controllers on the network, or communicate on a peer-to-peer basis. However, third-party software configuration tools can be used to set up peer-to-peer communication on the LONWORKS network, in accordance with the standard LONWORKS guidelines. Devices are defined through the Metasys system Person-Machine Interface (PMI) or Data Definition Language (DDL). The device type that identifies a LONMARK compliant controller is prefixed by LON (e.g., LONTCU, LONVMA, etc.).

4 Networking—LONWORKS Network Layout Figure 1 shows an example of a network in which the NCM350s are interconnected by the Metasys N1 Local Area Network (LAN), and supervise a LONWORKS network that includes a LONWORKS network backbone using routers to limit the network traffic from each NCM350 to the segment of the network to which it is connected.

I N I N I N 12 345 678 D 1 234 567 8 D 12 3456 78 D O A O A O A U T E L U T E L U T E L O R O R O R 1 2 3 4 5 6 7 8 7 8 1 2 3 4 5 6 7 8 7 8 1 2 3 4 5 6 7 8 7 8

. . . G G G FI O F FI OF F I OF N D N D N D N O N E N O N E N O N E O C E NI -ATTE NTION - N1 LAN O C E I N - ATTENTION - O C E NI -ATTENTIO N - L L L PLEASEDISCO NNEDT BATTERY PLEASE DISC ONNED TBATTERY PLEASEDISCON NEDTBATTERY BEFOREIN STALLING ME MO RY M BEFOR EINSTAL L INGME M ORY M BEFOREINSTALLI NGMEMORY M b R A b R A b R A ER - E R - E R - W a D W a D W a D O O O P P P REF REF REF N2 N2 N2 - I - I - I N2 N2 N2 + + +

II I I II

NEXT SERVICEDATE : NEXTSERVICE DATE: NEXT SERVICEDATE : a RY a R Y a RY TE T E T E T T T BA BA B A

A A A IS I S IS T S T S T S O O O S L SL S L

b b b III III III

DISCO NNECT DISCONNEC T DISCON NECT POW ER BEFOR E ER POW ER BEFO RE E R POW ER BEFORE ER W Y W Y W Y SERVICING O PL SERVICIN G O P L SERVICING O PL P P P P P P S U SU S U I I I

IV IV IV

II II II

M- M - M- O M OM O M C TS C TS C TS R R R PO PO PO

I I I II I I II

IV DANGER IV DAN GER I V DA NG ER

LINEVOLTAGE LI NE VOLTAGE LI NE VOLTAGE INSIDE INSIDE INSIDE

NCM350/361 NCM350/361 NCM350/361

Id: 010013937600 Id: 010013937600 Id: 010013937600 Johnson Cont rol s Johnson Cont rol s Johns on Cont rol s AD-TCU2220- 0XXX AD-TCU2220- 0XXX AD-TCU2220- 0XXX

Id: 0100139 37600 Prod.Dat e:L 9751 Id: 0100139 37600 Prod.Dat e:L 9751 Id: 0100139 37600 Prod.Dat e:L 9751

LONTCU LONTCU

Id: 010013937600 Johnson Cont rol s AD-TCU2220- 0XXX

Id: 0100139 37600 Prod.Dat e:L 9751

LONTCU

LONVMA LONVMA

Id: 010013937600 Johnson Cont rol s AD-TCU2220- 0XXX

Id: 0100139 37600 Prod.Dat e:L 9751

LONTCU

End-of-Line Terminator Third-party Third-party LONMARK Device LONMARK Device

Router Router

LONWORKS Backbone Layout

Figure 1: LONWORKS Network Layout

The LONWORKS network is a free topology network, meaning that devices can be connected to the network in a variety of geometric configurations. For example, the devices can be daisy-chained from one device to the next, connected with stub cables branching off from a main cable, connected using a tree or star topology, or any of these configurations can be mixed on the same network. For more information, see Network Topologies in the Network Layout Considerations section later in this document.

Networking—LONWORKS Network Layout 5 Notes The LONWORKS interface of the DX-9120 and DX-9121 controllers Regarding the provide both the logical N2 items interface of the DX-9100 controller and N2E Bus LONMARK object interface comprised of network variables. The Metasys N2 Echelon (N2E) Bus is a special implementation of LONWORKS technology designed specifically for DX-9120 and DX-9121 controllers. The controllers communicate with the NCM using N2 messages transported within the LonTalk protocol, and they automatically configure themselves for peer-to-peer network communication using LONMARK network variables. The standard NCM with an N2E Bus can only monitor DX-912x controllers using the logical N2 interface, and does not support the network variable interface of the DX or other LONMARK compliant controllers. The LONWORKS network of an NCM with the N2E implementation should be kept physically separate from a LONWORKS network monitored by an NCM350 as described in this bulletin.

Definition of LONWORKS network technology introduces several concepts that you Terms should understand in order to design a Metasys system implementation of the network. The following terms all apply to LONWORKS technology, with Metasys system-specific details where noted. Additional information can be obtained from the LONMARK Interoperability Association (www.lonmark.org) or the Echelon Corporation (www.echelon.com).

Binding and The network configuration process establishes the network image of the Network network, which defines each device’s unique network address and how it Configuration is bound to other devices. The binding process defines connections between network variables in LONWORKS compatible devices (see Network Variables). Connections define the data that devices share with one another (peer-to-peer communications). In the present implementation, the NCM350 does not have its own network variables, and therefore, does not participate in peer-to-peer communication on the LONWORKS network. The NCM350 polls the network variables of its LONWORKS compatible devices to request data, and directly addresses a device to send it a command.

6 Networking—LONWORKS Network Layout The following terms are used in the Metasys system to describe how the LONWORKS network is configured: Unbound: network addressing and peer-to-peer communication is not configured on the LONWORKS network. The NCM350 acts as the network configuration tool, and automatically assigns the logical network addresses for the devices on its network segment using the default (or user-defined) Domain/Subnet IDs and sequential Node IDs for each device (see Logical Addressing). In this case, each NCM350 is supervising an independent and physically separate LONWORKS network channel, and there can be no connection, or routing of messages, from one channel to another. Bound: a third-party network configuration tool was used to create the network addressing of the network and configure peer-to-peer communication, but the NCM350 was not assigned an address. In this case, you must use NCSETUP to manually assign a logical address (domain/subnet/node ID) to the NCM350. This address must be chosen with specific reference to the addressing scheme already defined on the network, because the NCM350 can only communicate with devices within its own domain, and it must have a unique subnet/node address within that domain. This mode is normally used only for demonstration purposes. It enables the NCM to interface to an existing LONWORKS network without changing the network image in the network tool database or in any of the nodes. For permanent operation, change a bound network configuration to a fully bound configuration so there is a record of the NCM within the network image in case of future changes to the network structure. Fully Bound: a network configuration tool was used to create the network addressing of the network and configure peer-to-peer communication, and the NCM350 was assigned an address. In this case, the NCM350 recognizes that it already has a LONWORKS network logical address, which is displayed in NCSETUP and cannot be edited. To add an NCM LONWORKS interface card to the network image using a network configuration tool, you need the device specific XIF file. The necessary files are available from your local Johnson Controls office as NU-NET203-0.XIF and NU-NET203-1.XIF. Note: As far as the NCM350 is concerned, the type of network configuration has no further consequence aside from determining who assigns logical addresses. As stated previously, the NCM350 does not participate in, but can coexist with, peer-to-peer communications.

Networking—LONWORKS Network Layout 7 Bridge An active LONWORKS compatible device that physically connects two LONWORKS channels. A bridge can receive a message from one channel, and make a decision as to whether the message needs to be transmitted on the other channel. The bridge forwards all messages in a given domain.

Channel A physical network segment of communications media, such as twisted-pair cable, that interconnects LONWORKS compatible devices. Channels are interconnected by LONWORKS compatible routers or bridges. In this document, the term network segment is used interchangeably with the term channel.

Channel A portion of a channel. A single channel can be comprised of multiple Segment channel segments connected by repeaters.

Connection A connection links one or more logical outputs (network variables or message tags) of one device to one or more logical inputs of the same or another device to enable the transfer of data (see Network Variables). The process of making connections is also called binding, and a network variable with a connection is referred to as being bound within the network.

Domain A logical collection of devices on one or more channels. Communications can take place only among devices configured in the same domain. Domains are further logically subdivided into subnets (up to 255), each containing up to 127 nodes (devices), which gives a maximum of 32,385 nodes per domain.

Domain ID The top level of the LonTalk protocol domain/subnet/node addressing hierarchy. The Domain ID can be 0, 1, 3, or 6 bytes long. The zero-length domain is a valid domain, and is used as the default for NCM350s in an unbound configuration. The domain length and Domain ID are assigned at installation time by the network configuration tool or by the NCM350.

Interoperability The ability to integrate multiple devices from the same or different manufacturers into a single network without requiring custom development or modification of the devices or the network configuration tool.

Link Power Nodes (devices) on the network either can be locally powered or Devices link-powered. A link-powered node derives its power from the network. A link-power source device must be connected to the network wiring to supply DC power to the link-powered nodes.

8 Networking—LONWORKS Network Layout Link-powered devices use the LPT-10 transceiver circuit, and locally-powered devices use the FTT-10 transceiver circuit. Both types of nodes can be connected to the same network wiring, because the transceiver circuits decouple the DC voltage from the signal voltage. For more information, refer to the LONWORKS LPT-10 Link-Power Transceiver User’s Guide available from the Echelon Corporation.

Logical Each Neuron chip device stores a globally (i.e., worldwide) unique, 48-bit Addressing serial number called the Neuron ID (see Neuron ID). The Neuron ID can be used to address the device on the LONWORKS network. However, for the purposes of logically grouping devices and routing messages on the network, each device is assigned (and stores) a logical address consisting of three parts: Domain ID (see Domain ID) Subnet ID (see Subnet ID) Node ID (see Node ID) The network configuration tool (or NCM350 when the network is unbound) maps device Neuron IDs to the domain/subnet/node logical addressing scheme when it creates the network image.

LONWORKS A device that communicates on a LONWORKS network. A LONWORKS Compatible compatible device may be a device with a control or network management Device (router) application. LONWORKS compatible devices are also referred to as nodes when installed on a network. Each LONWORKS compatible device has local processing capability, and may include Input/Output (I/O) hardware to process input data from sensors and to control actuators. Each device also includes the capability to communicate with other devices using the LonTalk protocol in firmware. Each LONWORKS compatible device contains an application program and the following hardware: Neuron chip transceiver (physical network interface) application electronics to connect the Neuron chip to I/O devices such as sensors, actuators, displays, and keypads an optional host processor. If a host processor is used, the application executes on the host processor and the Neuron chip is used only to process network communications. A LONWORKS compatible router is a special type of LONWORKS compatible device that performs only communications processing (see Router).

Networking—LONWORKS Network Layout 9 LONWORKS A collection of LONWORKS devices or LONWORKS compatible devices Network that communicate and interact with one another over some type of communication media. The network may be configured as one domain or a set of domains. A LONWORKS network can contain a single channel or multiple channels connected by LONWORKS compatible routers. A LONWORKS network can be used by a supervisory controller to monitor a subsystem of smart sensors with supervisory communication for data collection and event reporting. LONWORKS networks also can be used as standalone control systems, called peer-to-peer networks, where each device controls its own inputs and outputs, and shares information with its peers on the network as needed to provide coordinated control of the entire system. Both supervisory control and peer-to-peer communication can be implemented on the same network.

Network Image The logical network addresses and connection information for all devices (nodes) on the network. The network configuration tool creates the network image, and loads the node-relevant portion of the image into each device. The node’s network image is stored in EEPROM on the Neuron chip. The network configuration tool stores the entire network image in a database, which must be accessible when the network is changed, expanded, or defective devices are replaced.

Network A synonym used in this document for channel (see Channel in this Segment Definition of Terms section).

Network The LONMARK guidelines describe the data and message types a device Variables can receive or send on the LONWORKS network. The individual items of data are contained in Network Variables (NVs). These NVs represent the data communication interface among devices on the network, and only data that is exposed in the NVs can be exchanged between devices. The NVs are defined in external interface files in a standardized format. To promote interoperability, LONMARK functional profiles define the names and functions of the most commonly used NVs for specific applications, and profiles exist for most standard applications, such as the Space Comfort Controller (SCC) profile. The guidelines do not specify how the device actually stores or processes the data, and the device can store any other data that may or may not be exposed in additional manufacturer-defined NVs. The NVs are specified with strict data typing, i.e., the data of an NV in one device can be received only by an NV of the same data type in another device. The typing specifies not only the physical size of the data (number of bytes), but also the physical quantity represented, its resolution, range, and storage format.

10 Networking—LONWORKS Network Layout The network variables are further classified according to whether they contain active (live) or static data, and whether they are standard or user-defined variable types. The variables containing live data are defined by: Standard Network Variable Type (SNVT) User-defined Network Variable Type (UNVT) The variables containing static data are called Network Configuration Inputs (NCI) and are defined by: Standard Configuration Property Type (SCPT) User-defined Configuration Property Type (UCPT)

Neuron ID A 48-bit number burnt into each Neuron chip at manufacture time. Like a serial number, each Neuron chip has a unique Neuron ID.

Node A LONWORKS device (see also LONWORKS Compatible Device) installed on a LONWORKS network.

Node ID The third part of the LonTalk protocol domain/subnet/node addressing hierarchy. Node IDs can range from 1 to 127. At installation time, each device is assigned a unique Node ID within its subnet by the network configuration tool or by the NCM350.

Peer-To-Peer A network communication strategy in which independent intelligent devices share information directly with each other and make their own control decisions without the need or delay of using an intermediate, central or master controller. Enhanced system reliability is provided by eliminating the master (a single point of failure) and the system flexibility can reduce installation time and configuration cost. The Metasys system does not support the configuration of peer-to-peer communication; a third-party network configuration tool is required. The NCM350 can coexist with, and monitor, devices on the LONWORKS network that participate in peer-to-peer communication (see Binding and Network Configuration in this document).

Repeater A hardware device that connects two segments of a channel. The repeater is used to extend the length of the channel and/or allow more devices to be connected to the channel. Unlike a router, a repeater has no intelligence, so it cannot selectively forward messages to reduce traffic in a segment and increase network capacity (i.e., it forwards all messages).

Networking—LONWORKS Network Layout 11 The two classes of repeaters are: Physical Layer Repeater: only processes signals electrically. Because the physical layer repeater introduces timing variations into the signals, only one repeater is recommended per channel. The physical layer repeater also has no error detection, so it will forward damaged messages. Logical Repeater: processes signals in software, (i.e., it receives and rebuilds the messages), and then retransmits the messages. The logical repeater has error detection and rejects damaged messages. The restrictions that apply to physical layer repeaters do not apply to logical repeaters.

Router An active LONWORKS compatible device that physically connects two LONWORKS channels. A router can receive a message from one channel, and make a decision as to whether the message needs to be transmitted on the other channel. The router necessarily injects some delay in message transmission. The two classes of routers are: Learning Router: messages are routed only for a given domain. The router starts as a bridge (i.e., it forwards all messages in the domain), and reduces forwarding as it learns the topology of the network and the location of subnet addresses. Learning routers are vulnerable to failures if configured devices are incorrectly moved within the topology. Configured Router: messages are routed only for a given domain. The router forwards messages based on configured tables of subnet addresses. This is the most reliable and efficient form of routing. Each side (or port) of the router can be addressed by its Neuron ID or by a logical network address.

Service Pin Each Neuron chip has a service pin for use during installation to acquire the Neuron chip’s Neuron ID. When this pin is grounded, the Neuron chip sends a broadcast message containing its Neuron ID. The method used to ground the service pin varies from device to device. Examples of mechanical methods include grounding via a pushbutton or using a magnetic reed switch. The TCU and VMA1200 Series controllers have a recessed pushbutton. The DX-9200 does not have a service pin, but transmits the Neuron ID on the network whenever the controller is powered up (provided that the device has not been set offline by a network tool).

12 Networking—LONWORKS Network Layout Service LED The service pin also drives the Service Light-Emitting Diode (LED) that indicates the Neuron chip’s state. The Service LED is solid on when the Neuron chip has no application (invalid firmware), blinks slowly when the Neuron chip has an application (valid firmware downloaded) but is not configured on the network (doesn’t yet have its network image), is off when the Neuron chip has an application and is configured, and blinks once quickly each time the Neuron chip is reset. The service LED will also light three times in short succession when the device receives a Wink message with its Neuron ID from a network tool.

Subnet A logical collection of up to 127 devices within a domain. Up to 255 subnets can be defined within a single domain. All devices in a subnet must be on the same channel (network segment). Subnets cannot cross routers, which means that you cannot have devices of the same subnet on both sides of the router.

Subnet ID The second level of the LonTalk domain/subnet/node addressing hierarchy. Subnet IDs are assigned at installation time by the network configuration tool or by the NCM350.

Transceiver The component in each LONWORKS compatible device that provides the physical interface and connection to the network transport media (channel). The NCM350, TCU, and Variable Air Volume Modular Assembly (VMA) use the Echelon FTT-10 transceiver for free-topology, twisted-pair wiring. Devices using the Link Power LPT-10 transceiver circuit and FTT-10 devices can be connected to the same physical network segment (see also Link Power Devices).

Theory of The LONWORKS network can be configured as a supervisory system Operation network without peer-to-peer communication, as a stand alone peer-to-peer network, or as a supervisory system with peer-to-peer communication. In all cases, the twisted-pair network operates at 78K bits per second. Peer-to-peer configurations must be set up with a third-party network configuration tool (see Binding and Network Configuration under Definition of Terms in this document).

Networking—LONWORKS Network Layout 13 Mapping The NCM350 acts as a gateway between the Metasys N1 LAN and the LONWORKS LONWORKS network, and enables you to map LONWORKS network Network variables (see Network Variables under Definition of Terms) to Metasys Variables to software objects: Analog Input (AI), Analog Output Setpoint (AOS), Metasys Objects Binary Input (BI), Binary Output (BO), Control System (CS), etc. This allows the Metasys supervisory system to monitor and command LONWORKS compatible devices. The Metasys architecture and standardized LONMARK technology make it easy for the NCM350 to support any LONMARK compliant devices, because only an NV mapping table is required to provide this support for each device. Tables showing the LONWORKS NVs that can be mapped to Metasys software objects for both Metasys and third-party LONWORKS compatible controllers can be found in the LONWORKS Compatible Devices Supported by NCM350 Technical Bulletin (LIT-1162100).

Message Types The LONWORKS network carries the communication between the NCM350 and the LONWORKS controllers, and among the controllers themselves. The types of messages and data that are transmitted on the network include: generic device poll (life check) from the NCM350 to the controllers to determine whether the device is online or offline commands from the NCM350 to the controllers polling of data by the NCM350 to check for alarms and change-of-logic states in the controllers (see the Poll Priorities subheading later in this section) responses from the controllers to the NCM350, including identification and requested data values time synchronization message from the NCM350 to all controllers (Some controllers, such as the TCU, do not receive this message because they do not have an internal clock.) analog, binary, and multistate point data shared between controllers (if peer-to-peer communication is configured on the network)

Poll Priorities Poll priority levels establish how often the NCM350 polls the network variables of a device on the LONWORKS network to obtain data for alarm and change-of-state reporting. The NCM350 has three priority levels: 1, 2, and 3, where 1 is the highest. For example, a Priority 2 device is polled more often than a Priority 3 device. Note that the generic device poll to determine whether a device is online or offline (life check) is not prioritized, but is transmitted at the same rate to all devices.

14 Networking—LONWORKS Network Layout You set the priority level when defining the device object in the NCM350 for the LONWORKS compatible hardware device. We recommend that you keep the priority level for all controllers at 3, the system default. You may, however, assign higher priorities to a limited number of controllers if your application requires faster notification of changes in the values of network variables in those controllers. Realize that the poll priority gives a device a relative advantage over other devices and that the rate at which the NCM transmits messages on the network is not affected by the poll priorities of the devices. As you assign more devices to Priority 1, the speed advantage of these devices becomes less, and change-of-state detection performance will be significantly decreased for lower priority devices. Use the LON Statistics window under NC Diagnostics from the Metasys Operator Workstation software to view the actual poll cycle times for each of the three priority levels.

Components The components of the Metasys system implementation of the LONWORKS network are the NCM350/361, a LONWORKS interface card for the NCM350/361, the LONWORKS compatible devices, end-of- line terminators, and twisted-pair cabling.

NCM350/361 The NCM350/361 (Figure 2) is required to monitor or report alarms and changes-of-state to the Metasys supervisory system. Each NCM350/361 can support up to 127 LONWORKS compatible devices in either an unbound, bound, or fully bound network configuration.

Networking—LONWORKS Network Layout 15 1 2 3 4 5 6 7 8 I N D A O L T E U R O 1 2 3 4 5 6 7 8 7 8

. IG F F O N D N O N E E O C IN L - ATTENTI ON - PLEASE DISC O N NED T BATTERY BEFOR E NSTALLINGI MEMORY M A R -R E b D W a O P REF N2 - I N2 +

NEXT SERVICE DATE: Y R a E T T A B

A S I S T LO S

b III

DISCONNECT R E POWER BEFORE W Y O L P P SERVICING P U S I

- M M O C TS R PO

I II

IV DANGER

LI NE VOLTA GE INS IDE

ncm350

Figure 2: NCM350/361

LONWORKS To connect the NCM350/361 to the LONWORKS network, a LONWORKS Interface Card ISA card is required. Install one of two interface cards. The NU-NET203-1 card fully replaces the NU-NET203-0 card, which has been withdrawn from production by the manufacturer (Echelon Corporation) and is available only while stocks last. Table 1 shows the software release of Metasys software required for each card.

Table 1: LONWORKS Interface Cards and Metasys Compatibility Ordering Code Required Metasys Software NU-NET203-0 Release 10.01 or later NU-NET203-1 Release 11.00 or later

16 Networking—LONWORKS Network Layout NU-NET203-0 The NU-NET203-0 consists of two parts (see Johnson Controls Ordering Codes in this document for details):

the LONWORKS Interface ISA card the FTT-10 transceiver daughterboard The card is installed into Slot 2 (right-hand slot) of the NCM350/361. The Service LED on the card provides diagnostic information. The Busy LED on the daughterboard indicates that the host is busy, or transmitting a message. The Service Jumper (JP1) can be momentarily shorted (e.g., with a screwdriver) to cause the Neuron chip to send out a message over the network with its unique Neuron ID. This is useful when configuring or commissioning the LONWORKS network, but has no use with the Metasys system. Shorting the jumper does not harm the card, and the message does not affect the network or any Metasys component. Plug-on Screw Terminal Network Termination (For Network Cable Jumper Connection)

20-pin Socket BUS FREE JP3 TERM Transceiver Daughterboard

Busy LED 20-pin Transceiver Daughterboard Connector P3

Service LED SERVICE 10S1

DS1

Service JP1 Jumper BT1 I/O ADDRESS

Battery

LON W ORKS Interface ISA Card I/O Address Switches

FTM-10

Figure 3: NU-NET203-0 Interface Card

Networking—LONWORKS Network Layout 17 NU-NET203-1 The NU-NET203-1 consists only of the LONWORKS Interface ISA card (see the Johnson Controls Ordering Codes section in this document). Install the card into Slot 2 (right-hand slot) of the NCM350/361. The Service LED on the card provides diagnostic information. The Service Pin (P1) can be momentarily pressed to cause the Neuron chip to send out a message over the network with its unique Neuron ID. This is useful when configuring or commissioning the LONWORKS network, but has no use with the Metasys system. Pressing the Service Pin does not harm the card, and the message does not affect the network or any Metasys component. EchelonLONWORKS Firmware Chip Echelon LONWORKS Neuron Chip

Service Pin and LED NSI Neuron 3150 Chip Screw Plug FTT-10A Terminal for LONWORKS Network Connection

9-pin D-type Connector (Not Used)

I/O Address Switches (350 H) NUNET203-1mb

Figure 4: NU-NET203-1 LONWORKS Interface Card

Ferrite Ring A ferrite ring is included with the NU-NET203-1 card, which must be installed on the wires that connect the LONWORKS network to the NU-NET203-1 card. Installation of the ferrite ring is required to meet United States FCC and European CE Mark emission requirements (see Connecting LONWORKS Interface Card NU-NET203-1 in this document).

18 Networking—LONWORKS Network Layout Cable A twisted-pair cable is required, and we recommend 22 AWG solid or stranded wire. As an option, shielded cable can be used. For recommended cable types, refer to the tables in the Cable Type and Segment Length section under Network Layout Considerations in this document.

CABLE

Figure 5: Twisted-pair Cable

End-of-Line End-of-Line (EOL) terminators (Figure 6) must be installed on each Terminators channel segment (i.e., a continuous section of wiring between repeaters or routers) to balance the LONWORKS network communication signals. There are two types of terminator modules that differ only in their impedance values, but otherwise have the same packaging. The type, placement, and number of terminators required depends on the topology of the network segment, as follows: A bus-topology segment requires two terminators of type NU-EOL202-0, and they must be placed at each end of the bus (see Network Layout Considerations and Figure 7). A free-topology segment requires one terminator of type NU-EOL203-0, and it can be placed anywhere on the segment, preferably at a central location. (See Figure 8.) Note: Some network devices including repeaters, routers, and Link Power devices may have internal terminators that can be used instead of the separate terminator modules. An internal switch or jumper is normally provided to connect the terminator to the network. Refer to Installing LONWORKS Card into NCM350/361 later in this document for a practical example. The EOL Terminator unit has two sets of screw terminals, where the top set is used and the other is not. The terminator can be wired to the network at a device’s terminals (use a short length of twisted-pair cable), or directly to the network in daisy-chain fashion (see Figure 15). The terminator can be mounted on DIN rails, or next to the controller with double-sided tape or Velcro.

Networking—LONWORKS Network Layout 19 Terminator Type Screw Terminals

Not Used

termin

Figure 6: End-of-Line Terminator

Network When designing a LONWORKS network installation, you need to consider Layout the network topology, cable type, maximum cable lengths, maximum Considerations number of devices allowed, and number of LONWORKS network segments required.

Network Each LONWORKS network segment may be designed using one of Topologies two basic types of topology, each having specific advantages. Bus topology (Figure 7) uses two EOL terminators allowing for a longer total cable length on a channel segment (between repeaters or routers). The geometric design is restricted to a single bus, where devices are linked in the form of a daisy-chain. Free topology (Figure 8) uses only one terminator, which results in shorter overall cable length, but allows a more flexible geometric design. Within the bus topology, the devices may be wired to the network only in a daisy-chain fashion, with stub cables of up to 3m in length. Within the free topology, bus sections may be connected in a tree or star configuration. The NCM350 can be placed anywhere on a network segment, at either end of the bus topology, or somewhere in the middle with LONWORKS compatible devices on both sides. For more information on network configurations, refer to the documents available from Echelon Corporation. The following diagrams show examples of acceptable layouts for the LONWORKS network.

20 Networking—LONWORKS Network Layout Daisy-chained Bus Topology

Stub-wired Bus Topology

Legend: LON W ORKS Compatible Device (Including NCM350/361)

Bus EOL Terminator Bus_Top

Figure 7: Bus Topology Network Layouts

Free Topology (Tree or Star)

Legend: LONWORKS Compatible Device (Including NCM350/361)

Free Topology Terminator Free_Top

Figure 8: Free Topology Network Layouts

Figure 9 shows a Metasys system with the LONWORKS network segments configured with bus and free topology segments.

Networking—LONWORKS Network Layout 21

12345678 IN D 12345678 IN D 12345678 IN D LOA LOA LOA OUT RE OUT RE OUTRE 12345678 78 1234567878 1234567878 . . . FIG OF FGI OF FIG OF N ON NDE N ON NDE N ON NDE O C ELNI -ATENTION- N1 LAN O C ELNI -ATTENTION- O C ELIN -ATTENTION- PLEASEDISCONEDTBATERY M PLEASEDISCONNEDTBATERY M PLEASEDISCONEDTBATERY M R b BEFOREINSTALINGMEMORY -RA R b BEFOREINSTALINGMEMORY -RA R b BEFOREINSTALINGMEMORY -RA WE a D WE a D WE a D PO PO PO R R R E E E F F F N N N - - - 2 I 2 I 2 I N N N + + + 2 2 2

II II II

a NEXTSERVICEDATE: RY a NEXTSERVICEDATE: RY a NEXTSERVICEDATE: RY TTE TTE TTE BA BA BA ISA SIA SIA OTS OTS OTS SL SL SL

b b b III R III III DISCONNECT E DISCONECT ER DISCONNECT ER POWERBEFOREPOPY POWERBEFOREPOWPLY POWERBEFOREPOWPLY WSERVICING SUPL SERVICING SUP SERVICING SUP I I I

IV IV IV II II II

- - - MM M M CO TS CO TS CO TS POR POR POR

III III III

IV DANGER IV DANGER IV DANGER LINEVOLTAGE LINEVOLTAGE LINEVOLTAGE INSIDE INSIDE INSIDE NCM350/361 NCM350/361 NCM350/361

Id: 0100 13937600 Id: 0100 13937600 Johnson Controls Johnson Controls AD- TCU2220-0 XXX AD- TCU2220-0XXX

Id: 010013937600 Prod.Da te: L9751 Id: 010013937600 Prod.Da te: L9751 LONTCU LONTCU

Id: 0100 13937600 Johnson Controls AD- TCU2220-0XXX

Id: 0100 13937600 Johnson Controls AD- TCU2220-0XXX Id: 010013937600 Prod.Da te: L9751 LONVMA

Id: 0100 13937600 Johnson Controls AD- TCU2220-0 XXX

Id: 0100 13937600 Johnson Controls AD- TCU2220-0 XXX LONTCU Free Topology Id: 010013937600 Prod.Da te: L9751 Terminator LONTCU

LONVMA

Id: 0100 13937600 Id: 0100 13937600 Id: 0100 13937600 Johnson Controls Johnson Controls Johnson Controls AD- TCU2220-0 XXX AD- TCU2220-0XXX AD- TCU2220-0 XXX

Id: 0100 13937600 Id: 0100 13937600 Id: 0100 13937600 Johnson Controls Johnson Controls Johnson Controls AD- TCU2220-0 XXX AD- TCU2220-0XXX AD- TCU2220-0 XXX Id: 010013937600 Prod.Da te: L9751 Id: 010013937600 Prod.Da te: L9751 Id: 010013937600 Prod.Da te: L9751 LONVMA LONTCU LONTCU LONTCU

Free Topology Third-party End-of-Line LONMARK Compatible Terminator Device Third-party Bus Topology LONMARK Compatible Device

Layout_1

Figure 9: Metasys Network Layouts with Bus and Free Topology

Cable Type and The LONWORKS network requires twisted-pair cable with two wires. Segment Length Shielded cable also can be used. The maximum length of a channel segment depends on the topology of the segment (bus or free), the type of cable used (cable size and quality), and the types of devices connected to the segment (using FTT-10 transceivers and/or LPT-10 transceivers). Use only one cable type for one channel segment. Mixing cable types in one segment reduces the overall performance of the network and can cause an unacceptable number of transmission errors. A channel segment is a portion of a channel (or network segment as designated in this document). A single channel can be comprised of multiple channel segments connected by repeaters. The total channel length and number of nodes can be extended by using a physical layer repeater, or multiple logical repeaters, on the channel. The tables in this section list the maximum channel segment lengths (i.e., total lengths of continuous wiring between repeaters or routers).

22 Networking—LONWORKS Network Layout Notes: The maximum lengths presented in these tables are absolute maximum values. Other factors that affect network performance and reliability, such as noisy Electromagnetic Interference (EMI) environments or a large distance between two individual devices on a free topology segment, may limit a segment to fewer devices or shorter overall cable length. For the bus topology, the maximum length for a single stub cable is 3m (10 ft), and the stub lengths must be calculated into the overall segment length.

Table 2: Cable Types and Segment Lengths for Bus Topology Cable Type Maximum Segment Length Maximum Segment Length with FTT-10 Devices Only with FTT-10 and/or LPT-10 Devices Belden 85102 2700m (8850 ft) 2200m (7200 ft) Belden 8471 2700m (8850 ft) 2200m (7200 ft) Level IV 22AWG 1400m (4600 ft) 1150m (3770 ft) JY (St) Y 2 x 2 x 0.8 900m (2950 ft) 750m (2460 ft)

Table 3: Cable Types and Segment Lengths for Free Topology Cable Type Maximum Node-to-node Maximum Segment Length Distance with FTT-10 and/or LPT-10 Devices Belden 85102 500m (1640 ft) 500m (1640 ft) Belden 8471 500m (1640 ft) 500m (1640 ft) Level IV 22AWG 400m (1300 ft) 500m (1640 ft) JY (St) Y 2 x 2 x 0.8 320m (1050 ft) 500m (1640 ft)

Table 4: Cable Types and Technical Specifications Type Shield Solid AWG mm dia ohm/km nF/km Belden 85102 No No 16 1.3 28 56 Belden 8471 No No 16 1.3 28 72 Level IV No Yes 22 0.65 106 49 JY (St) Y Yes Yes 20.4 0.8 73 98

If you are considering a cable type other than one of those specified, compare the technical specification of the cable with the specifications of the recommended cable types to assess the maximum segment length. For a safe assessment, use the maximum segment length of the cable type with a higher resistance (ohm/km) and a higher capacitance (nF/km). If the resistance of the cable is higher than 106 ohm/km with a capacitance higher than 49 nF/km, or the capacitance of the cable is higher than 98 nF/km with a resistance higher than 73 ohm/km, do not use the cable.

Networking—LONWORKS Network Layout 23 Number of The maximum number of devices allowed per channel segment Devices per (i.e., between repeaters or routers) depends on the types of devices Segment connected to the segment (using FTT-10 transceivers and/or LPT-10 transceivers), as shown in Table 5: Note: Other factors, such as the power consumption of individual LPT-10 devices, may limit a segment to fewer devices.

Table 5: Maximum Number of Devices per Segment Device Type Maximum Allowed FTT-10 Nodes Only 64 (if repeaters are not used) LPT-10 Nodes Only 128 (if repeaters are not used) Mixed FTT-10 and LPT-10 ((FTT-10 x 2) + LPT-10) ≤ 128 Nodes Terminators: Bus Topology Two bus type EOL terminators required (NU-EOL202-0) Free Topology One free topology terminator required (NU-EOL203-0) Physical Layer Repeaters Maximum of 1 per channel Note: Each LPT-10 channel segment (between repeaters) requires its own power supply.

Number of Each NCM350 supports up to 127 logically addressed devices (nodes). Devices per Notes: For the best use of available network bandwidth, connect the NCM350 NCM350 to the same channel (network segment) as the devices that it is monitoring, and the channel should use only the minimum number of repeaters required for the channel length and/or number of devices. This is the recommended configuration when the network is unbound such that there is a separate, dedicated channel (network segment) for each NCM350. In bound and fully bound networks, the NCM350 network segments may be interconnected by routers to allow peer-to-peer communication between devices on different channels. Routers are necessary to limit the NCM350 communications traffic to the appropriate network segments for best network performance. An NCM350 may be separated from its devices by one or more routers, but a careful analysis of the network traffic must be carried out to ensure that no segment is overloaded by traffic from multiple NCM350s.

24 Networking—LONWORKS Network Layout Installation Procedures

General When installing LONWORKS network wiring throughout a building, be Guidelines aware of the following: Follow all National Electric Code (NEC) and local code restrictions. Do not exceed the maximum device limits given in this document. Do not run network cables close to transformers or high frequency generating equipment. We recommend the use of a daisy-chained bus topology because it offers the maximum cable length with the lowest risk of communication errors. Run network and other low voltage cables separately from line voltage and power cables. Use solid or stranded 16 to 22 AWG (1.5 mm2 or 0.8 mm diameter) cable. Do not use wire of a thinner gauge because it breaks easily, and it reduces the performance of the network. Use the same cable type throughout the installation of any network segment, and avoid the poor wiring practices described in the Poor Wiring Practices section under Troubleshooting Procedures, Checking Network Wiring later in this document. If shielded cable is used, install a 470K ohm, 1/4W, ±10% metal-film resistor between the shield and ground at one location only (normally at the NCM350). Do not connect the cable shield to a device’s ground/earth terminal (labeled GND or ). Connect a device’s ground/earth terminal (labeled GND or ) to a clean electrical ground point. This connection provides a discharge path for any high voltage interference that could otherwise damage the device or the LONWORKS network.

Networking—LONWORKS Network Layout 25 Installing In order for the NCM350/361 to be connected to and communicate over LONWORKS the LONWORKS network, a LONWORKS Interface ISA card is required. As Card into part of installation, the card’s I/O address factory setting is verified and the NCM350/361 card installed into the second ISA slot (right-hand slot) of the NCM350/361. 1. Turn power off at the NCM350/361. 2. Verify that the I/O address on the card is set to the factory default address of 350 hex before installing the card in the NCM. The address is set with the DIP switches labeled S1 on the interface card. The switches of S1 represent Bits 3 through 9 of the address. Refer to Figure 10 and Figure 11 for details. I/O Address (hex): 350

Switch Set to: 110100 10

Hex Value of B it: 21842184 10

Note: The dark gray shading indicates the switch position and shows the side that is pushed in. A switch is set to 1 when it is pushed down on the OFF side as indicated by the 1 on the printed circuit board.

IOAddress

Figure 10: NU-NET203-0 LONWORKS Card I/O Address Switch Settings

I/O Address (hex): 350

Switch Set to: 1 1100100

Hex Value of B it: 21842184 ON DIP

12 3456 7 8

Note: The position of each of the eight slide switches is shown by the white area. A switch is set to 1 when it is pushed towards the ON side as indicated on the switch assembly.

203IO

Figure 11: NU-NET203-1 LONWORKS Card I/O Address Switch Settings

26 Networking—LONWORKS Network Layout Note: The I/O address is the address the NCM uses to communicate with the ISA card, and has nothing to do with the NCM’s address on either the N1 LAN or on the LONWORKS network. 3. NU-NET203-0 only: Optionally set the Network Termination jumper (Figure 12) on the transceiver daughterboard according to the topology of the network segment connected to the NCM350. If you use the card’s built-in network termination, you can save having to install one of the separate End-of-Line (EOL) terminators on the network cabling. A jumper is supplied with the daughterboard, but it is plugged perpendicularly onto only the middle pin of the JP3 jumper block, so that the built-in termination is disabled. To use the built-in termination for a free topology network segment, place the jumper over the middle pin and the pin labeled FREE on the jumper block (right position in Figure 12). Note that no other EOL terminators are used on the segment for a free topology network, and the NCM should be centrally located in the network topology. To use the built-in termination for a bus topology network segment, place the jumper over the middle pin and the pin labeled BUS on the jumper block (left position in Figure 12). Here, the NCM must be located at one end of the bus (last device), and another bus-type EOL terminator must be installed at the other end of the bus. BUS FREE BUS FREE

JP3TERM JP3 TERM

Bus Topology on Free Topology on Network Segment Network Segment

Term_Jmp

Figure 12: Network Termination Jumper on Transceiver Daughterboard

4. NU-NET203-0 only: Install the transceiver daughterboard on the LONWORKS card. To do this: a. Remove the standoff, spacer, and screw that hold one side of the transceiver’s faceplate bracket (see Figure 13 for the location of the standoff). b. Remove the nut from the middle threaded post holding the faceplate on the ISA card (the nut can be discarded because it is no longer needed). c. Install the spacer and standoff on the middle threaded post.

Networking—LONWORKS Network Layout 27 d. Align the 20-pin connector on the transceiver daughterboard over the 20-pin connector (P3) on the ISA card. The component sides of both boards are facing each other. e. Make sure that the transceiver faceplate (with the network connector) is inside the ISA card faceplate, and properly aligned with the hole in the ISA card faceplate. Press the 20-pin connector down firmly in place. f. Insert the screw back through the hole in the transceiver board, and thread it into the standoff. Tighten the screw, but do not use excessive force.

1. Remove screw, washer, and standoff

P3 from here.

2. Remove nut from SERVICE 10S1 here and thread DS1 on washer and standoff. JP1

BT1 I/O ADDRESS

Brd-Inst

Figure 13: Installing Daughterboard on Interface Card

5. Install the LONWORKS card into Slot 2 of the NCM350/361 (right-hand slot), referring to Figure 14. To insert the card, temporarily remove the colored plug-on screw terminal block from the LONWORKS card.

28 Networking—LONWORKS Network Layout 1 2 3 4 5 6 7 8 IN

-ATTENTION - D PLEASE DISCONNEDT BATTERY -RA OUT RE BEFORE INSTALLING MEMORY M L 1 2 3 4 5 6 7 8 7 8 OAD

C EN O D Do not use Metasys O N L O N F IN F IG E . P N2 Bus terminal O W E a b for network wiring. R

RE F Use plug-on terminal block

- N2 on LONWORKS card for + N2 LONWORKS network wiring.

REF Slot 1Slot 2 N2 - NEXT SERVICE DATE: BA

N2 I TTE + R Y DS3 DS4

DISCONNECT POWER POWER BEFORE SUPPL SERVICING a Y I Port 2 I

A S IS T O L S

DS5 LED DS5 DS6 LED DS6 b

I II

DANGER

LINE VOLTAGE INSIDE

Note location of DS5 LED for power up diagnostics.

Slot 1 is reserved for Install LON W ORKS Network Interface Card (NIC) card into Slot 2. for N1 LAN. ISA_Inst .

Figure 14: LONWORKS Card Installs into Slot 2 of NCM350/361

6. Return power to the NCM350/361.

Terminations The LONWORKS network segment is connected to the NCM350 at its (Connecting LONWORKS interface card (Figure 15). Do not use the N2 Bus terminal Network on the NCM for LONWORKS network wiring. Each device, including Wiring) the NCM, can be wired to the network using stub length or daisy-chain wiring, or you can mix both types of wiring. Where cable runs permit, daisy-chain wiring is the preferred method.

Networking—LONWORKS Network Layout 29 Notes: Stub lengths can be up to 3m (10 ft) long, but shorter lengths are preferred. Note that stub lengths must be calculated into the overall maximum cable length allowed for the chosen network topology (see the Cable Type and Segment Length section under Network Layout Considerations earlier in this document). If the NCM you are connecting is at the end-of-line, a stub length is not needed. Some LONWORKS devices and LONWORKS compatible devices, including the LONWORKS interface card, use a standard plug-on screw terminal for network wiring. This terminal can be temporarily removed to facilitate wiring. 1. If you are wiring stub lengths, cut a short length of cable (about 15 cm [6 in.] long is recommended) from the same type of twisted-pair cable as used for the network wiring. 2. Remove the colored plug-on screw terminal from the LONWORKS card or LONWORKS device. 3. Connect the stub length (or network cable for daisy-chain wiring) to the plug-on screw terminal, stripping back enough wire to make the connection. There are no + or - terminals because the twisted-pair network is not polarity sensitive. (However, we recommend that you maintain the same polarity between similar devices.) 4. For stub length wiring, use a standard screw terminal block to connect the free end of the stub length to the network twisted-pair wires that lead to the other devices (Figure 15). Insert the stripped wires to be connected under one screw and tighten to allow direct contact between the wires. 5. If shielded cable is used for the network wiring, connect the shields together and insulate with tape or a rubber sleeve, as shown in Figure 15. 6. Reconnect the plug-on screw terminal to the LONWORKS card or LONWORKS device. 7. Determine where, and how many, separate terminators are required on the network segment, according to the segment’s topology. (If you enabled the built-in network termination on the LONWORKS card or on any other device with a built-in terminator, this saves one separate terminator module.) A bus-topology segment must be terminated at both ends of the bus (two NU-EOL202-0 bus-type terminators). A free-topology segment must have one terminator (NU-EOL203-0 free-topology terminator) connected to the segment, preferably centrally located.

30 Networking—LONWORKS Network Layout Stub Length Wiring: Daisy Chain Wiring: To Next Device LWON ORKS Network

Plug-on Screw Terminal Stub lengths no longer than 3 meters. The LON W ORKS twisted pair network is not sensitive to polarity; however, it is recommended to maintain same Shielded Cable: polarity between similar devices. Connect shields together Ground shield at

and insulate with tape. only one point. I/O ADDRESS I/O S1 10

470K ohm Resistor

End-of-Line (EOL) Terminators:

Bus-type EOL Terminator (one at each end of bus) JP1 SERVICE DS1 BT1 To Next Device LONWORKS Interface Card in NCM

Free Topology Terminator (only one per segment)

Lonwire

Figure 15: LONWORKS Network Wiring

Networking—LONWORKS Network Layout 31 Connecting When connecting the NU-NET203-1 to the network, the ferrite ring LONWORKS (supplied with the card) must be installed on the network cable. If the card Interface Card is not at the end of the network segment, a stub length of cable must be NU-NET203-1 installed. Strip about eight centimeters (three inches) of the sheath from the network cable and pass the two wires four times through the ferrite ring and pull the wires tight to secure the ring no more than five centimeters (two inches) from the end of the wires.

To Network To LON W ORKS Card

Ferrite

Figure 16: Ferrite Ring Installation for NU-NET203-1

Connecting TCU The TCU controller does not have a plug-on screw terminal for connecting Controllers to the network wiring. Therefore, refer to Figure 17 for the location of the the Network network wiring terminals on the TCU base:

LONTCU Base with Cover Removed

NET A NET B Ground Terminal (do not use for cable shield)

TCU_Wire

Figure 17: Connecting a TCU Controller to the LONWORKS Network

32 Networking—LONWORKS Network Layout Recording the LONWORKS compatible TCU devices (and other LONWORKS compatible Neuron ID devices) are supplied with adhesive bar code labels attached to the front of the device (Figure 18). The Bar Code 128 Standard is used by Johnson Controls and is commonly used by the other manufacturers. Two peel-off portions on the label show the Neuron ID of the device in plain text and as a bar code. When mounting LONWORKS compatible devices in your facility, you must accurately record the Neuron ID of each device. Note: It is important to correctly record the Neuron IDs, because the network configuration software (whether NCM software or third-party software) uses the Neuron IDs to automatically generate logical network addresses for the devices. During initial setup, the software physically polls each device using its Neuron ID and sets the logical addresses in the memory of the device. Thereafter, the devices are addressed on the network using only their logical addresses. If the Neuron IDs get mixed up, then commands and configuration settings are sent to the wrong devices, possibly causing erratic behavior or even physical damage to the devices. When mounting LONWORKS devices in your facility, record the Neuron ID of each device, as follows: 1. Peel off one of the two bar code portions of the device label (if available), and stick it onto the site or floor plan to show the location of the device you have just installed. (If there is no such label, write the Neuron ID on the plan.)

Id: 010013937600 Johnson Controls AD-TCU2220-0XXX

Id: 010013937600 Prod. Date: L 9751

Bar_Labl

Figure 18: Neuron ID Bar Code Label

Networking—LONWORKS Network Layout 33 2. Using the plan, enter (or scan using an attached bar code reader) the Neuron ID of the device into the appropriate field of the configuration software: For the Metasys system (with unbound, bound, or fully bound network configurations), this is the Definition window in the Metasys Operator Workstation (OWS) (or in the NC DDL file) for the LONWORKS device’s hardware object. For bound or fully bound network configurations, you must also enter the Neuron ID in appropriate field in the third-party network configuration tool.

34 Networking—LONWORKS Network Layout Commissioning Procedures

Overview This section covers commissioning steps for the LONWORKS network. Commissioning the network includes checking the network installation, defining Metasys software objects for the devices on the network, and binding the devices on the LONWORKS network. For information on commissioning the NCM, refer to the Network Control Module 300 Series Technical Bulletin (LIT-6360251) and the NC SETUP for Windows Technical Bulletin (LIT-6360251d) under the Control Modules section of the Metasys Network Technical Manual (FAN 636).

Checking Checking the network installation involves verifying that: Network the network wiring for all devices has been completed. Installation the network has been installed according to the rules described in the Installation Procedures section.

Power Up When the NCM350/361 with a LONWORKS interface card is powered up, the Service LED on the LONWORKS interface card blinks while startup diagnostics are running. Note: With the NU-NET203-0, you can’t see the Service LED on the LONWORKS interface card when the ISA slot cover is installed on the NCM. Therefore, during initial startup and troubleshooting procedures, remove the ISA slot cover from the NCM. After startup diagnostics complete normally and the LONWORKS network is defined, the Service LED on the LONWORKS interface card remains off. A problem may be indicated if the Busy LED (Figure 3) is on steadily, or if it is not flashing when devices have been defined and communication enabled. Note: The Service Pin can be pressed on the LONWORKS interface card (or Jumper JP1 on the LONWORKS interface card NU-NET203-0 can be momentarily shorted with a screwdriver) to cause the Neuron chip to broadcast a message containing its Neuron ID over the network. Some third-party network configuration tools can use this message to automatically configure or troubleshoot the device.

Networking—LONWORKS Network Layout 35 Metasys If no third-party network configuration tool is used, the NCM350 acts as Supervisory the network configuration tool, and it automatically creates the network System Only image (using default Domain/Subnet IDs and sequential Node IDs for each (Unbound) device on its segment). This is called Unbound configuration, where peer-to-peer communication is not configured on the LONWORKS network (see Binding and Network Configuration under Definition of Terms earlier in this document).You must define Metasys software objects for the devices, as follows: 1. Define an NC software object for each NCM350 (either online in the NC-Definition window, or using DDL). Make sure the Port 2 Type is set to LON, and Port 1 Type is blank. Note: The NC Subnet Address and NC Node Address fields in the NC-Definition window refer to the NCM’s address on the N1 LAN, and have nothing to do with the NCM’s address on the LONWORKS network. 2. Use NCSETUP for Windows to define the LONWORKS parameters for the NCM (LON Parameters option on the Command menu). In the dialog box that appears, select Unbound under Binding Mode, and accept the default values for the other fields. Notes: You must use Metasys Release 10.01 or later in order to set the LON parameters with NCSETUP for Windows. If you select the unbound option on a network where a network configuration tool was used to create a network configuration, the NCM destroys that network configuration. If more than one NCM350 is connected to the same unbound network segment and there are a large number of devices on the segment, the NCM350s could run out of network addresses. Each NCM350 assigns device addresses using a range of three consecutive Subnet IDs, starting with its own Subnet ID, and it checks the network to make sure that it does not assign duplicate addresses. To avoid running out of addresses in an unbound configuration, enter different Subnet IDs (in steps of 3) for each NCM350 on the network in the LONWORKS Parameters dialog box of NCSETUP.

36 Networking—LONWORKS Network Layout 3. Make sure to reset the NCM after the parameters are downloaded to the NCM. This causes the NCM to initialize the LONWORKS card, and load the new LONWORKS parameters into the card. The NCM can be reset several ways: If the computer running NCSETUP is able to communicate with the NCM, select Reset NCM on the Command menu. Press the System Reload button on the NCM, which generates a request for a code and data download from the NC archive node address. Toggle power to the NCM to cause it to re-initialize the LONWORKS interface card. 4. Create Metasys device objects for each LONWORKS compatible device on the network segment monitored by the NCM 350 (either online in the LON-Definition window, or using DDL). Using the site plan or floor plan, make sure to enter the correct Neuron ID for the device in the Neuron ID field and the correct Device Type (refer to the LONWORKS Compatible Devices Supported by NCM350 Technical Bulletin (LIT-1162100). Enter 2 in the NC Trunk Number field, and enter 0 in the Device Address field.

Peer-to-Peer If a third-party network configuration tool has been used to assign logical (Bound or Fully network addresses and set up peer-to-peer communication, then this Bound) network configuration tool contains the network image (see Binding and Network Configuration under Definition of Terms earlier in this document). If you used the tool to assign addresses to the NCM350s, the configuration is called Fully Bound. If you did not assign addresses to the NCM350s, the configuration is called Bound, and you must manually assign addresses to the NCM350s in a separate step. In either case, you define Metasys software objects for the devices if the network contains NCM350s, as follows: 1. Use NCSETUP for Windows to configure the NCM350. Click the LON Parameters option on the Command menu to open the LONWORKS Parameters dialog box. In the dialog box, click Set Defaults, then select Fully Bound or Bound. Adjust the Maximum Poll Image Size and Time to Live parameters if necessary. More information about these parameters is in the NCSETUP for Windows Technical Bulletin (LIT-6360251d). Reset the NCM. 2. Use the network configuration tool to configure the logical addressing and peer-to-peer connections between controllers on the LONWORKS network. Note: NCM350s do not have network variables, and therefore, do not take part in peer-to-peer communications.

Networking—LONWORKS Network Layout 37 3. If the configuration is Fully Bound, a logical network address is already assigned to the NCM350s. Accept the addresses displayed in the corresponding fields. Make sure to select Fully Bound under Binding Mode in the LONWORKS Parameters dialog box in NCSETUP. No further steps are required. or if the configuration is Bound, then you must manually assign logical network addresses to the NCM350s. When you use NCSETUP for Windows to define the LONWORKS parameters for the NCM, select Bound in the LONWORKS Parameters dialog box. Select the Domain ID Length (number of bytes) already defined with the network configuration tool. Enter the correct Domain ID (hex) and Subnet ID corresponding to where the NCM is physically located on the LONWORKS network. Enter a unique Node ID for the NCM350 within its subnet. Refer to the network configuration tool to find an address that is still free, (i.e., is not assigned to one of the LONWORKS compatible devices). Make sure the network configuration tool does not assign the NCM’s address to another device during re-configurations or changes to the network configuration. Note: The NCM350 can see only devices that have the same Domain ID as the NCM350. If the devices are not physically connected to the same network segment as the NCM, then routers must be installed to pass messages to the NCM’s segment. 4. Create Metasys software objects for all devices, as described in the Metasys Supervisory System Only (Unbound) section of this document.

38 Networking—LONWORKS Network Layout Troubleshooting Procedures

Overview The LONWORKS network is a reliable communications network. However, there are situations in which communication problems may occur. Under most circumstances, a problem is indicated by LEDs on the NCM motherboard and LONWORKS card. A communication problem exists if: the DS5 LED (Figure 14) on the NCM350 is not on steadily

the Service LED (Figure 3) on the LONWORKS card is on or flashing If one or both of these lights are behaving in this way, the network is not working properly. You may also refer to the LON Statistics window under NC Diagnostics at the Operator Workstation. Examine the number of offline polls, which, ideally, should be relatively small and not increasing. (If LONWORKS compatible devices are defined that are not presently connected to the network, disable communication to these devices in the software object to prevent them from being polled.) A large and increasing number of offline polls indicates that timing, network traffic, or other problems may be causing devices to fail to respond to the life-check poll. You also may want to use the network configuration tool to read out diagnostic statistics from individual devices, or use a LONWORKS network analyzer from a third-party supplier. The most likely problems with a malfunctioning LONWORKS network are: faulty network wiring, including broken or frayed wires, improper cable termination, poor wiring practices, or ground loops missing or improperly installed end-of-line terminator network segment is too long

defective LONWORKS device or LONWORKS compatible device, or mismatch of Neuron ID and logical address too many devices defined These problems are discussed in this section.

Networking—LONWORKS Network Layout 39 Checking The wire used for the network must be free of broken or frayed sections. Network Wiring If either of the two signal lines is broken or frayed, the devices that are located after the break do not answer the life check message, and are reported as offline. To determine which part of the cable is defective, start at the device that physically precedes the first offline device. The problem is likely in the cable between the last online device and the first offline device.

Proper Cable To verify proper cable termination, examine all network wiring. There Termination must not be any breaks in the two signal lines, and the wires must be connected to their proper terminals. Lightly tug on each wire to ensure that it is secure. For the LONWORKS network, polarity normally does not need to be checked. However, it is good practice to maintain the same polarity for similar devices. The standard plug-on connectors for LONWORKS twisted-pair wiring are keyed, making it easy to maintain polarity once the color coded wires are connected properly.

Poor Wiring Impedance is a form of electrical resistance in Alternating Current (AC) Practices circuits. Any impedance changes in the signal path may cause signal reflections and be a source of signal degradation on the network. Any number of common wiring mistakes can cause increased impedance, such as: Using lengths of wire that have a different cross section (larger or smaller) than the rest of the wiring. This mistake is commonly made for stub wiring. Use the same type of wire throughout a network segment. Changing materials, such as going from copper to iron and back to copper within terminal blocks and screw connectors. The longer the path in the foreign material, the worse the signal degradation. (Clamp both wires under one screw such that the wires make a direct connection.) Inadvertently introducing an inductive impedance into the wiring, such as by coiling wire that is too long. It is generally not good practice to leave unnecessary lengths of cable connected to a network, and any extra cable must be included in the calculation of total cable length. Any extra cable should be laid flat in the cable runs and not left in a coil. Figure 19 illustrates how all of these mistakes can be made in one simple stub-wiring junction. Note: Most of the mistakes shown apply to the junctions used for stub wiring. The best wiring method, where cable runs permit, is to daisy chain the network cable directly from device to device (see Figure15).

40 Networking—LONWORKS Network Layout Extra Length Coiled

Normal Cross Section Unnecessary Connectors

Large Cross Section

Small Cross Section

Device Very Bad Wiring

Normal Cross Section

Device Better

Wires have direct contact under single screw terminal.

Device Best

bad_wire

Figure 19: Wiring Mistakes

Ground Loops Shielded network cable must be grounded at only one location using a 470K ohm resistor, preferably at the NCM350. If grounded at two or more locations, a ground loop is created that can introduce electrical noise into the cable and disrupt normal communications.

Networking—LONWORKS Network Layout 41 Checking For every LONWORKS bus-type segment, you must have an end-of-line End-of-Line terminator installed at each device that is at the end of the bus (total of Terminations two bus terminators per segment). In most installations, the terminators are located at the NCM350 and the last LONWORKS compatible device on the segment. For free-topology-type segments, you must have one free-topology terminator (which is a different type than the bus terminator) installed at a preferably central location on the segment. If these terminators are not installed, or they are installed at incorrect locations, signal reflections may interfere with communication. If you install too many terminators, the bus may be loaded down, reducing the total number of devices that can be connected. Verify that the location and number of terminators are correct. Note: Routers, repeaters, and link power devices may have internal terminators that can be switched in or out of the network. Check each device carefully to determine if a terminator is connected.

Checking The LONWORKS network may not communicate because the length of the Cable Lengths network segment is too long. Refer to the tables in the Cable Type and Segment Length section earlier in this document for recommended cable lengths, and be aware that these lengths mean the total length of all cables used on the segment, including stub cables. Also, any single stub cable must be no longer than 3m. If you exceed these maximum lengths, reconfigure the network using repeaters and/or routers, as necessary.

Checking Any device, if internally shorted, can bring down the network. However, LONWORKS this situation is rare. If you suspect this problem, you’ll need to disconnect Devices each device, one at a time, and observe when the network comes back online. It is more common for a device to be reported as offline. The most likely reason is a defective device or a mismatch between the Neuron ID of the device and the logical address originally stored for that ID. This can occur if you have replaced a defective device without changing the Neuron ID in the device’s Focus window, or the wrong Neuron ID was entered in the site plan at the device’s location. Also, be aware that as devices on the LONWORKS network are connected again, the NCM has to read various data from the devices to bring them back online. Allow enough time for any device to come online before performing troubleshooting steps.

42 Networking—LONWORKS Network Layout Replacing a To replace a defective LONWORKS compatible device, follow these steps: LONWORKS 1. Disconnect the network wiring from the old device (in most cases by Device pulling off the plug-on connector). 2. Install the new device in its position, following all termination rules. Peel off one of the Neuron ID labels, and place the label in the proper location on the site plan for later reference. 3. Open the Focus window for the old LONWORKS compatible device’s hardware object (e.g., LONTCU - Focus window). Enter the new device’s Neuron ID in the Neuron ID field; and, if the segment is bound or fully bound, start the network configuration tool you used to address the old device. Select the Replace option for the device. Enter the new device’s Neuron ID or follow instructions for the automatic recognition of the Neuron ID when the Service Pin on the device is pressed. The tool then updates the network image.

Checking If you have too many devices defined and connected to a network segment, Number of the LONWORKS network may not communicate. The maximum number of Defined devices allowed per NCM350 network segment is 64 without repeaters, or Devices 127 with repeaters. However, depending on how you install these devices, the actual maximum may be fewer. When you reach the maximum number, you’ll need to connect any remaining devices to another LONWORKS network segment on a different NCM350.

Networking—LONWORKS Network Layout 43 44 Networking—LONWORKS Network Layout Ordering Codes

Johnson Table 6: Johnson Controls Ordering Codes Controls Code Description Product Code Number Numbers Network Control Module NU-NCM350-8 (North American version) NCM350/361 NU-NCM361-8 (European version) LONWORKS Interface Card NU-NET203-1 for bus-type or free-topology network for NCM350/361 complete segments and Metasys Release 11.00 or later with FTT-10 Transceiver LONWORKS Interface Card NU-NET203-0 for bus-type or free-topology network for NCM350/361 complete segments and Metasys Release 10.01 or later with FTT-10 Transceiver daughterboard (Echelon) End-of-Line Terminators NU-EOL202-0 for bus-type network segments NU-EOL203-0 for free-topology network segments Note: For other networking components, such as repeaters or routers, contact Echelon Corporation (www.echelon.com) or other third-party vendors.

Networking—LONWORKS Network Layout 45 Notes

46 Networking—LONWORKS Network Layout Notes

Networking—LONWORKS Network Layout 47 Notes

www.johnsoncontrols.com Controls Group FAN 1162 507 E. Michigan Street LONWORKS Systems Manual P.O. Box 423 Release 11.00 Milwaukee, WI 53201 Printed in U.S.A.

48 Networking—LONWORKS Network Layout