Creating and Configuring A LonWorks Network With Xenta LonWorks Devices

StruxureWare Building Operation
Creating and Configuring a LonWorks Network with Xenta LonWorks Devices Tutorial Guide
04-13033-01-en October 2012
StruxureWare Building Operation

Creating and Configuring a LonWorks Network with Xenta LonWorks Devices Tutorial Guide
04-13033-01-en October 2012
Copyright 2012 Schneider Electric. All rights reserved. The Schneider Electric brand and any registered trademarks of Schneider Electric Industries SAS referred to in this guide are the sole property of Schneider Electric SA and its subsidiaries. They may not be used for any purpose without the owner's permission, given in writing. This guide and its content are protected, within the meaning of the French intellectual property code (Code de la proprit intellectuelle franais, referred to hereafter as "the Code"), under the laws of copyright covering texts, drawings and models, as well as by trademark law. You agree not to reproduce, other than for your own personal, noncommercial use as defined in the Code, all or part of this guide on any medium whatsoever without Schneider Electric's permission, given in writing. You also agree not to establish any hypertext links to this guide or its content. Schneider Electric does not grant any right or license for the personal and noncommercial use of the guide or its content, except for a non-exclusive license to consult it on an "as is" basis, at your own risk. All other rights are reserved. Trademarks and registered trademarks are the property of their respective owners.
Contents
Introduction
1
1.1 1.2 1.3
About This Guide ........................................................... 9

Purpose of This Guide ................................................................. 11 How This Guide is Organized ...................................................... 12 Typographical Conventions ......................................................... 13
2
2.1 2.2
Additional Information .................................................. 15

Where to Find Additional Information ........................................... 17 Regulatory Notices ...................................................................... 18
Tutorial
3
3.1 3.2 3.2.1 3.2.2 3.2.3 3.3 3.3.1 3.3.2
Our Case Study ........................................................... 21

University X ................................................................................. 23 Requirements and Specifications ................................................ 26 Devices Used for This Case Study ............................................. 26 Software Used in This Tutorial ................................................... 26 Specifications ........................................................................... 26 Focus of This Tutorial .................................................................. 27 Pre-existing Database Folder and Programs .............................. 27 Pre-existing Database Objects .................................................. 28
4
4.1 4.2 4.3 4.4
Creating the LonWorks Network .................................. 29

Creating a LonWorks Interface .................................................... 32 Creating a LonWorks Network .................................................... 33 Changing the Domain ID for a LonWorks Network ....................... 34 Creating a Folder ........................................................................ 37
5
5.1 5.2
Adding Devices to the LonWorks Network ................... 39

Creating a LonWorks Device ....................................................... 42 Creating a Programmable Xenta Device ...................................... 44
6
6.1 6.2 6.3
04-13033-01-en, October 2012
Commissioning the LonWorks Network and Devices .... 47

Discovering a Xenta Device ......................................................... 50 Commissioning a Xenta Device ................................................... 53 Commissioning a LonWorks Device ............................................ 54
Creating and Configuring a LonWorks Network with Xenta LonWorks Devices 5
6.4
Configuring a Configuration Property ........................................... 56
7
7.1 7.2 7.3
Creating the Local Node and Network Variables ........... 59

Creating Network Variables Automatically ................................... 62 Creating an Output Network Variable .......................................... 64 Configuring the Value and Propagation Delta for a Network Variable Member ...................................................................................... 66
8
8.1 8.2 8.3 8.4 8.5
Creating Programs, Alarms, and Schedules in the Automation Server ....................................................... 69

Creating a Function Block Program ............................................. 72 Importing Function Block Program Code ..................................... 74 Creating a Change of State Alarm .............................................. 76 Creating a Digital Schedule ......................................................... 82 Configuring a Schedule as a Shadow ......................................... 83
9
9.1 9.2 9.3
Creating Bindings for Communication .......................... 85

Creating a LonWorks Binding ...................................................... 88 Importing a Solution .................................................................... 90 Binding Values Using a Binding Template .................................... 92
10
10.1 10.2
Replacing a LonWorks Device ...................................... 97

Uploading the LonWorks Device Configuration ......................... 100 Replacing an Online LonWorks Device ...................................... 101
11
11.1 11.2 11.3
Replacing a Xenta Device ........................................... 103

Uploading the Xenta Device Configuration ................................. 106 Replacing an Online Xenta Device ............................................. 107 Downloading the Xenta Device Configuration ............................ 109
12
12.1
Replacing a Xenta I/O Module .................................... 111

Replacing a Xenta I/O Module ................................................... 114
13
13.1 13.2 13.3 13.4
Editing the Menta Application for a Commissioned Xenta Device ....................................................................... 117
Uploading the Xenta Device Configuration ................................. 120 Editing a Menta Application ....................................................... 121 Commissioning a Xenta Device ................................................. 122 Downloading the Xenta Device Configuration ............................ 123
14
14.1 14.2 14.3 14.4 14.5
Adding a Xenta Device to a Commissioned LonWorks Network ..................................................................... 125

Copying a Folder or Object ........................................................ 128 Renaming a Folder or Object ..................................................... 129 Discovering a Xenta Device ....................................................... 130 Commissioning a Xenta Device ................................................. 132 Summary .................................................................................. 133
04-13033-01-en, October 2012
Introduction
The Introduction part contains information on the purpose of this guide, how this guide is organized, where to find more information, and information on regulatory notices.
About This Guide
Topics
Purpose of This Guide How This Guide is Organized Typographical Conventions
1 About This Guide 1.1 Purpose of This Guide
1.1
Purpose of This Guide

This tutorial provides step-by-step instructions for creating a LonWorks network configured with an Automation Server and Xenta devices. This tutorial focuses on the following Building Operation Engineering Certification objectives: Create a new Building Operation system using an Automation Server and Xenta devices Integrate Xenta devices in a new Building Operation system Organize folders and objects in the System Tree pane Identify engineering process and communication flow between devices and servers Replace a device Edit an application Use standards and templates for efficient engineering
04-13033-01-en, October 2012
1 About This Guide 1.2 How This Guide is Organized
1.2
How This Guide is Organized

This Building Operation Guide is divided into the following parts:
Introduction
The Introduction part contains information on the purpose of this guide, how this guide is organized, where to find more information, and information on regulatory notices.
Tutorial
The Tutorial part contains a step-by-step description of how to carry out different tasks. If you want more information, see WebHelp or the corresponding Building Operation Guide. The Tutorial part includes a case study for a fictional customer called University X. You can decide if you want to follow the example or use the described procedures as reference information. The case study in this tutorial is an example of a typical way of configuring Building Operation for a customer. When reading through this tutorial, you might not have access to the devices, programs, and other files that are needed for the fictional customer University X. However, the purpose of having a case study is to see the procedures put in context, so you see how the procedures could be used when configuring Building Operation, devices, or programs for your customer.
04-13033-01-en, October 2012
1 About This Guide 1.3 Typographical Conventions
1.3
Typographical Conventions
Building Operation Guides use the following specially marked texts:
Tip
Helps you understand the benefits and capabilities of the product.
Note
Provides you with supplementary information.
Important
Alerts you to supplementary information that is essential to the completion of a task.
Caution
Alerts you to a condition that can cause loss of data.
Warning
Alerts you to a condition that can cause product damage or physical harm. Bold texts: User interface items, such as property names and buttons, are written in bold, for example "On the File menu, select New." Example texts: All the example related information is indicated by blue lines and bullets.
04-13033-01-en, October 2012
Additional Information
Topics
Where to Find Additional Information Regulatory Notices
2 Additional Information 2.1 Where to Find Additional Information
2.1
Where to Find Additional Information

All the technical Building Operation information is available online, on WebHelp. You also find additional information in the Building Operation Guides: Hardware Reference Guide Plain English and Script Difference Guide Function Block Editor and Menta Editor Difference Guide WebReports Reference Guide WebReports Operating Guide System Reference Guide Technical Reference Guide WorkStation Operating Guide IT Reference Guide WebStation Operating Guide System Upgrade Reference Guide Administering Reports Tutorial Guide Configuring an Automation Server as a Controller Tutorial Guide Creating and Configuring a LonWorks Network with Xenta LonWorks Devices Tutorial Guide Creating and Configuring a Modbus Network Tutorial Guide Creating and Configuring Alarms Tutorial Guide Creating and Configuring Graphics Tutorial Guide Creating and Configuring Schedules Tutorial Guide Creating and Configuring Trend Logs Tutorial Guide Creating and Configuring Users Tutorial Guide Starting a Project Tutorial Guide Creating and Configuring a BACnet Network with b3 BACnet Devices Tutorial Guide Creating and Configuring a LonWorks Network with MNL LonWorks Devices Tutorial Guide
04-13033-01-en, October 2012
2 Additional Information 2.2 Regulatory Notices
2.2
Regulatory Notices
UL 916 Listed products for the Unites States and Canada, Open Class Energy Management Equipment.
WEEE - Directive of the European Union (EU)

This equipment and its packaging carry the waste of electrical and electronic equipment (WEEE) label, in compliance with European Union (EU) Directive 2002/96/EC, governing the disposal and recycling of electrical and electronic equipment in the European community.
CE - Compliance to European Union (EU)

2004/108/EC Electromagnetic Compatibility Directive This equipment complies with the rules, of the Official Journal of the European Union, for governing the Self Declaration of the CE Marking for the European Union as specified in the above directive(s) per the provisions of the following standards: IEC/EN 61326-1 Product Standard, IEC/EN 61010-1 Safety Standard.
Industry Canada
ICES-003 This is a Class B digital device that meets all requirements of the Canadian Interference Causing Equipment Regulations.
C-Tick (Australian Communications Authority (ACA))

AS/NZS 3548 This equipment carries the C-Tick label and complies with EMC and radio communications regulations of the Australian Communications Authority (ACA), governing the Australian and New Zealand (AS/NZS) communities.
Federal Communications Commission

FCC Rules and Regulations CFR 47, Part 15, Class B This device complies with part 15 of the FCC Rules. Operation is subject to the following two conditions: (1) This device may not cause harmful interference. (2) This device must accept any interference received, including interference that may cause undesired operation.
04-13033-01-en, October 2012
Tutorial
The Tutorial part contains a step-by-step description of how to carry out different tasks. If you want more information, see WebHelp or the corresponding Building Operation Guide. The Tutorial part includes a case study for a fictional customer called University X. You can decide if you want to follow the example or use the described procedures as reference information. The case study in this tutorial is an example of a typical way of configuring Building Operation for a customer. When reading through this tutorial, you might not have access to the devices, programs, and other files that are needed for the fictional customer University X. However, the purpose of having a case study is to see the procedures put in context, so you see how the procedures could be used when configuring Building Operation, devices, or programs for your customer.
Our Case Study
When new knowledge is to be acquired, it is often advantageous to work with a realistic example. For this purpose we use a case study, which is basically the same in all Building Operation Tutorial Guides.
Topics
University X Requirements and Specifications Focus of This Tutorial
3 Our Case Study 3.1 University X
3.1
University X
We are going to install Building Operation as the building management system for University X. The university is a campus of buildings for which heating and cooling are supplied from a Central Plant with an underground distribution system. The case study focuses on the renovation of the Central Plant and the expansion of the School of Business.
Figure: The School of Business and the Central Plant
The Cooling Plant consists of a single chiller with a primary-secondary pumping system. The secondary water loop serves four VAV air handling units with chilled water coils located in the School of Business. The secondary loop has two water pumps. Only one pump is required for 100 % of the load. The second pump provides 100 % backup. The secondary pumps are variable speed. The primary chilled water loop has a single constant volume chilled water pump. The condenser loop rejects heat by means of a cooling tower. The condenser loop has a single constant volume condenser water pump. The tower has two constant speed, drawthrough fans to increase the capacity of the tower above the natural draft capacity. A diverting valve can be used to protect the chiller from condenser water thermal shock. The water leaving the condenser can be diverted back to the inlet of the condenser without any cooling effect.
04-13033-01-en, October 2012
Figure: Cooling Plant diagram
The heating plant consists of two boilers in parallel, each with their own inline pumps. Much of the time only one boiler is required to meet the load but under greater load, both boilers will operate at the same time. The flow from the two boilers comes together in a common supply header. There is a line from the supply header to the mechanical systems that require a source of hot water. This line has two constant volume distribution pumps in parallel. Only one is required to meet the load. The second is back-up and lead-lag is used to alternate which pump runs. The water returning from the mechanical systems flows into the return header where it can be pumped by the inline pumps through the boilers. There is a common line between the supply header and the return header. When the inline pumps are flowing at a rate that exceeds the distribution pump flow rate, the water flow in the common line is from the supply header to the return header. When the distribution pump is flowing at a rate that exceeds the combined inline pump flow rates, flow in the common line is from the return header to the supply header. Each boiler has its own self contained control system that interfaces with Building Operation through a combination of binary electrical control and network variables. The inline pumps are locally controlled by the self contained control system.
04-13033-01-en, October 2012
Figure: Heating Plant diagram
04-13033-01-en, October 2012
3 Our Case Study 3.2 Requirements and Specifications
3.2
Requirements and Specifications

To be able to configure Building Operation for University X, the following devices and software are used in this tutorial.
3.2.1
Devices Used for This Case Study

The following devices are used for this case study: Power Supply, PS-24V Automation Server, AS-L Freely Programmable Controller, Xenta 302 or Xenta 301 I/O Module, Xenta 422A VAV Controllers: 2 x Xenta 102-AX
3.2.2
Software Used in This Tutorial

The following software is used in this tutorial: License Administrator, and a valid license Enterprise Server WorkStation
3.2.3
Specifications
You find specifications in the Building Operation data sheets for Enterprise Server, WorkStation, PS-24V Power Supply, Automation Server, Xenta 300, Xenta 421A/422A, and Xenta 102-AX.
04-13033-01-en, October 2012
3 Our Case Study 3.3 Focus of This Tutorial
3.3
Focus of This Tutorial

The university requires the new East Wing of the School of Business to be controlled using Xenta LonWorks devices. The equipment consists of one VAV-Air Handling Unit and two VAVs. In this tutorial, you create and configure the LonWorks network and the Xenta devices required. This includes organizing the LonWorks network folder structure, creating the Xenta application specific and Xenta programmable devices, establishing communication between the network devices, as well as preparing the Automation Server to manage the alarms for the LonWorks network.
3.3.1
Pre-existing Database Folder and Programs

For University X, the Enterprise Server called University X ES1 has the following folder structure:
Figure: University X ES1 and its folder structure
The Automation Server called CPlant AS controls the Cooling Plant and Heating Plant. CPlant AS has the following folder structure:
04-13033-01-en, October 2012
3 Our Case Study 3.3 Focus of This Tutorial
Figure: CPlant AS and its folder structure
3.3.2
Pre-existing Database Objects

For University X, the following objects are available in the Building Operation database prior to the creation and configuration of LonWorks network with Xenta LonWorks devices: ...University X ES1/Servers/CPlant AS/Cooling Application/Schedules/Cooling Plant Enable Schedule
04-13033-01-en, October 2012
Creating the LonWorks Network
Topics
Creating a LonWorks Interface Creating a LonWorks Network Changing the Domain ID for a LonWorks Network Creating a Folder
4 Creating the LonWorks Network
Our Example
In this chapter, you prepare the Automation Server to function as the LonWorks network interface and create the LonWorks network so that LonWorks devices can be added for controlling the East Wing of the School of Business. You also change the domain ID for the LonWorks network to make it is possible to easily use the Xenta Operator Panel for handheld servicing of the Xenta devices. Additionally, you create a folder structure in the System Tree pane to ensure that the network is organized to maximize engineering and operating efficiency. The folder structure also represents the Xenta group organization for Xenta programmable devices added to the network for controlling Air Handling Units.
04-13033-01-en, October 2012
4 Creating the LonWorks Network 4.1 Creating a LonWorks Interface
4.1
Creating a LonWorks Interface

You create a LonWorks interface under the Building Operation server to connect to a LonWorks network. For more information, see WebHelp. In this example, you create the LonWorks Local FT-10 Interface under the CPlant AS in the System Tree pane.
To create a LonWorks interface

1. In WorkStation, in the System Tree pane, select the server where you want to create the interface. In this example, select ...University X ES1/Servers/CPlant AS. 2. On the File menu, point to New and then click Interface. 3. In the object type list, select LonWorks Local FT-10 Interface or LonWorks Interface. In this example, select LonWorks Local FT-10 Interface.
4. In the Name box, type a name for the interface. In this example, keep the default name LonWorks Local FT-10 Interface. 5. Click Create. You can now discover the interface and/or create the LonWorks network. You can also configure the default settings of the interface.
04-13033-01-en, October 2012
4 Creating the LonWorks Network 4.2 Creating a LonWorks Network
4.2
Creating a LonWorks Network

You create a LonWorks network under the LonWorks interface to connect to devices that are using the LonWorks protocol. For more information, see WebHelp. In this example, you create a LonWorks network called the East Wing, which is a new wing of the School of Business building. This building will be controlled by a field bus comprised of Xenta 280/300/401 LonWorks devices and other LonWorks devices.
To create a LonWorks network

1. In WorkStation, in the System Tree pane, select the LonWorks interface where you want to create the network. In this example, select ...University X ES1/Servers/CPlant AS/LonWorks Local FT-10 Interface. 2. On the File menu, point to New and then click LonWorks Network. 3. In the Name box, type a name for the network. Wing. In this example, type East
4. In the Description box, type a description. Business. 5. Click Create.
In this example, type School of
04-13033-01-en, October 2012
4 Creating the LonWorks Network 4.3 Changing the Domain ID for a LonWorks Network
4.3
Changing the Domain ID for a LonWorks Network

You change the domain ID for a LonWorks network to suit your requirements. For example, you can change the domain ID to make it possible to use the same Xenta Operator Panel on different sites. For more information, see WebHelp. In this example, you change the domain ID for the East Wing LonWorks network. You change the ID to 17 (decimal) to make it possible to use the same Xenta Operator Panel on Vista sites as well as Building Operation sites.
To change the domain ID for a LonWorks network

1. In WorkStation, in the System Tree pane, select the LonWorks network that you want to change the domain ID for. In this example, select ...University X ES1/Servers/CPlant AS/LonWorks Local FT-10 Interface/East Wing. 2. On the File menu, click Properties. 3. Click the Advanced tab.
4. Under Domain table for Network Interface, select Index 0, and then click Edit.
Continued on next page
04-13033-01-en, October 2012
5. In the ID (decimal) box, enter the domain ID.
In this example, enter 17.
6. Click OK.
04-13033-01-en, October 2012
7. Click OK.
Important
If there are commissioned devices connected to the LonWorks network, you need to recommission the network as well as all devices that indicate they are out of sync.
04-13033-01-en, October 2012
4 Creating the LonWorks Network 4.4 Creating a Folder
4.4
Creating a Folder
You create folders to organize your Building Operation database. For more information, see WebHelp. In this example, you create the folder called AHUs in which the Xenta 300 device is created. The AHUs folder represents the Xenta Group.
To create a folder
1. In WorkStation, in the System Tree pane, select the folder, server, or network where you want to create the folder. In this example, select ...University X ES1/Servers/CPlant AS/LonWorks Local FT-10 Interface/East Wing. 2. On the File menu, point to New and then click Folder. 3. In the Name box, type a name for the folder. In this example, type AHUs.
4. In the Description box, type a description for the folder. In this example, type Programmable Xenta Devices location and a Xenta Group. 5. Click Create. In our example, repeat the procedure to create the following folders: Table: LonWorks Network Folders
Name VAVs Location ...University X ES1/Servers/CPlant AS/LonWorks Local FT-10 Interface/East Wing Information Two Xenta 102-AX LonWorks devices will be created and represent the LonWorks Group.
04-13033-01-en, October 2012
4 Creating the LonWorks Network 4.4 Creating a Folder
Table: Automation Server Folders

Name AHU 01 Location ...University X ES1/Servers/CPlant AS Information Function Block programs, alarms, schedules, trend logs in the Automation Server will be created and imported as part of the field bus control and supervisory logic.
Alarms
...University X Alarm objects will be created ES1/Servers/CPlant AS/AHU in this folder to indicate field 01 bus device variables that are in alarm as part of the Automation Server's function as a supervisory logic device to the LonWorks field bus. ...University X Function Block programs will ES1/Servers/CPlant AS/AHU be created and imported in 01 this folder as the Automation Server functions as a supervisory logic device to the LonWorks field bus and, therefore, requires programming. ...University X Trend log objects can be ES1/Servers/CPlant AS/AHU created in this folder to log 01 field bus device variables from the LonWorks devices as part of the Automation Server's function as a supervisory logic device to the LonWorks field bus. ...University X A schedule in the ES1/Servers/CPlant AS/AHU Automation Server will be 01 created in this folder to control when the air system, controlled by LonWorks network field bus devices, should be running.
Programs
Trends
Schedules
04-13033-01-en, October 2012
Adding Devices to the LonWorks Network
Topics
Creating a LonWorks Device Creating a Programmable Xenta Device
5 Adding Devices to the LonWorks Network
Our Example
In this chapter, you add both Xenta application-specific devices (Xenta LonWorks devices that are configurable) and a programmable Xenta LonWorks device in the System Tree pane beneath the LonWorks Network. The Xenta 102-AX devices, which are already programmed, are used for controlling the VAV dampers. The Xenta 300 device is used for controlling the Air Handling Unit in the East Wing. The Menta program for the Xenta 300 device has already been written, so you will import that existing program.
04-13033-01-en, October 2012
5 Adding Devices to the LonWorks Network 5.1 Creating a LonWorks Device
5.1
Creating a LonWorks Device

You create LonWorks devices under the LonWorks network to connect to physical LonWorks devices. For more information, see WebHelp. In this example, you create a Xenta 102-AX LonWorks device called VAV 01 01, located in the East Wing of the School of Business. The network has not been commissioned, so you create the LonWorks device using the offline procedures.
To create a LonWorks device

1. In WorkStation, in the System Tree pane, select the LonWorks network or LonWorks network folder where you want to create the device. In this example, select ...University X ES1/Servers/CPlant AS/LonWorks Local FT-10 Interface/East Wing/VAVs. 2. On the File menu, point to New and then click Device. 3. In the object type list, select a device template. AX. In this example, select 102-
4. In the Name box, type a name for the device. 01.
In this example, type VAV 01
Tip
The name of the LonWorks device must be unique in the network, even for LonWorks devices in different folders in the network. 5. In the Description box, type a description. 102-AX - fan powered terminal. In this example, type Xenta
Creating and Configuring a LonWorks Network with Xenta LonWorks Devices 42 04-13033-01-en, October 2012
5 Adding Devices to the LonWorks Network 5.1 Creating a LonWorks Device
6. Click Next. 7. Click Create. In our example, repeat the procedure to create another LonWorks device. Use the following settings: Location: ...University X ES1/Servers/CPlant AS/LonWorks Local FT-10 Interface/East Wing/VAVs Device template: 102-AX Name: VAV 01 02 Description: Xenta 102-AX - fan powered terminal Neuron ID: Default value Commission: No
04-13033-01-en, October 2012
5 Adding Devices to the LonWorks Network 5.2 Creating a Programmable Xenta Device
5.2
Creating a Programmable Xenta Device

You create programmable Xenta devices under the LonWorks network to connect to physical Xenta 280/300/401 LonWorks devices. In this example, you create a Xenta 300 device, called AHU 01, located in the East Wing of the School of Business. The network has not been commissioned, so you create the Xenta 300 device using the offline procedures.
To create a programmable Xenta device

1. In WorkStation, in the System Tree pane, select the LonWorks network or LonWorks network folder where you want to create the programmable Xenta device. In this example, select ...University X ES1/Servers/CPlant AS/LonWorks Local FT-10 Interface/East Wing/AHUs. 2. On the File menu, point to New and then click Device. 3. In the object type list, select ProgrammableXenta.
4. In the Name box, type a name for the device. 01.
In this example, type AHU
Tip
The name of the programmable Xenta device must be unique in the network, even for programmable Xenta devices in different folders in the network. 5. In the Description box, type a description. Programmable Xenta 300. 6. Click Next.
In this example, type
04-13033-01-en, October 2012
5 Adding Devices to the LonWorks Network 5.2 Creating a Programmable Xenta Device
7. In the Files box, enter the Menta application (MTA) file. enter AHU1.MTA. 8. Click Create.
In this example,
Note
Xenta I/O modules are not added in this way. As they are defined in the Menta application program, they are automatically added to the I/O folder when the Xenta application is downloaded.
04-13033-01-en, October 2012
Commissioning the LonWorks Network and Devices
Topics
Discovering a Xenta Device Commissioning a Xenta Device Commissioning a LonWorks Device Configuring a Configuration Property
6 Commissioning the LonWorks Network and Devices
Our Example
In this chapter, you bring all available devices online in your network. You first discover the devices, which updates the Neuron ID in the Building Operation database when the device service pin button is pressed. In this way, you do not need to manually enter each ID. You then commission the Xenta 102-AX devices to enable the devices to communicate on the LonWorks network. The Xenta 300 device is also commissioned. During this process, the Menta program is downloaded and the device is enabled to communicate on the LonWorks network, as well. Finally, you configure the Xenta 102-AX devices to determine the VAV functional options for the preprogrammed devices.
04-13033-01-en, October 2012
6 Commissioning the LonWorks Network and Devices 6.1 Discovering a Xenta Device
6.1
Discovering a Xenta Device

You discover Xenta 280/300/401 LonWorks devices to create or configure the programmable Xenta devices in the Building Operation server. The Xenta 280/300/401 LonWorks devices must be physically connected to the Building Operation server field bus. For more information, see WebHelp. In this example, you discover the Xenta 300 device (AHU 01) in the East Wing network.
To discover a Xenta device

1. In WorkStation, in the System Tree pane, select the server that is connected to the device you want to discover. In this example, select ...University X ES1/Servers/CPlant AS. 2. Click the Device Discovery view. 3. In the Select device type box, select LonWorks.
4. Select the Devices folder. 5. On the Actions menu, click Activate listen to service pin. 6. Press the service pin on the physical device. In this example, press the service pin on the Xenta 300, which is AHU 01.
04-13033-01-en, October 2012
7. In the Device Discovery view, ensure that the Xenta device is displayed in the Devices folder. This may take up to 5 seconds.
8. On the Actions menu, click Deactivate listen to service pin. In this example, discover all four devices before you deactivate Listen to service pin. 9. Drag the discovered service pin (device) to the System Tree pane: Drag to an existing device to associate it with the discovered physical device. Drag to the LonWorks network to create the device. In this example, drag the Service Pin 1 device to ...University X ES1/Servers/CPlant AS/LonWorks Local FT-10 Interface/East Wing/AHUs/AHU 01.
Tip
To verify the device Neuron ID, select the device in the System Tree pane, and then select Properties on the File menu. The Neuron ID can be found on the Basic tab of the Device Properties. In our example, repeat the procedure to discover the Neuron ID of the Xenta I/O Module and the VAV devices. M1 (Xenta 422A) Location: ...University X ES1/Servers/CPlant AS/LonWorks Local FT-10 Interface/East Wing/AHUs/AHU 01/IO/M1 VAV 01 01 Location: ...University X ES1/Servers/CPlant AS/LonWorks Local FT-10 Interface/East Wing/VAVs/VAV 01 01
04-13033-01-en, October 2012
VAV 01 02 Location: ...University X ES1/Servers/CPlant AS/LonWorks Local FT-10 Interface/East Wing/VAVs/VAV 01 02
04-13033-01-en, October 2012
6 Commissioning the LonWorks Network and Devices 6.2 Commissioning a Xenta Device
6.2
Commissioning a Xenta Device

You commission physical Xenta 280/300/401 LonWorks devices to make them operational. The commission downloads the Menta application, gives the device a subnet node address, and sets the device status to online. After a commission, the device can communicate with other devices on the LonWorks network and execute its application. For more information, see WebHelp. In this example, you commission the Xenta 300 device (AHU 01) in the East Wing, LonWorks network.
To commission a Xenta device

1. In WorkStation, in the System Tree pane, select the device. In this example, select ...University X ES1/Servers/CPlant AS/LonWorks Local FT-10 Interface/East Wing/AHUs/AHU 01. 2. On the Actions menu, click Commission. 3. Click Commission. 4. Click Close.
Tip
The Xenta I/O Modules communication automatically begins upon commissioning the Xenta 280/300/401 LonWorks device, as long as the I/O module's Neuron ID was associated to the I/O module prior to commissioning the Xenta 280/300/401 LonWorks device.
04-13033-01-en, October 2012
6 Commissioning the LonWorks Network and Devices 6.3 Commissioning a LonWorks Device
6.3
Commissioning a LonWorks Device

You commission physical LonWorks devices to give them their addresses, which are defined in the LonWorks devices in the Building Operation server. The commission enables the devices to communicate on the LonWorks network. For more information, see WebHelp. In this example, you commission VAV 01 01 in the East Wing, LonWorks network.
To commission a LonWorks device

1. In WorkStation, in the System Tree pane, select the device. In this example, select ...University X ES1/Servers/CPlant AS/LonWorks Local FT-10 Interface/East Wing/VAVs/VAV 01 01. 2. On the Actions menu, click Commission. 3. In the Neuron ID box, make sure that the correct Neuron ID is entered.
04-13033-01-en, October 2012
6 Commissioning the LonWorks Network and Devices 6.3 Commissioning a LonWorks Device
4. Select which configuration to use: Click Keep current configuration in the device to leave the configuration in the device as is. Click Download current configuration to device to use the current configuration from Building Operation. Click Download default configuration to device to use the default configuration from the device template. Click Upload configuration from device to use the current configuration in the device. In this example, click Upload configuration from device.
Important
Before downloading or uploading the device configuration, carefully consider the effects of overwriting the current device configuration in the LonWorks device or Building Operation server. 5. Click Commission. 6. Click Close. The device is commissioned and activated. In our example, repeat the procedure to commission VAV 01 02. VAV 01 02 Location: ...University X ES1/Servers/CPlant AS/LonWorks Local FT-10 Interface/East Wing/VAVs/VAV 01 02 Configuration: Upload configuration from device Device application file: No
04-13033-01-en, October 2012
6 Commissioning the LonWorks Network and Devices 6.4 Configuring a Configuration Property
6.4
Configuring a Configuration Property

You configure the Configuration properties of the LonWorks devices to ensure that the device performs as required by the project. For more information, see WebHelp. In this example, you configure the nciSndHrtBt communication configuration property of VAV 01 01 (a Xenta 102-AX LonWorks device) to enable it to send data to other devices on the LonWorks network.
To configure a configuration property

1. In WorkStation, in the System Tree pane, select the configuration property. In this example, select ...University X ES1/Servers/CPlant AS/LonWorks Local FT-10 Interface/East Wing/VAVs/VAV 01 01/Node Object [0]/nciSndHrtBt. 2. In the List View, right-click on the column heading bar and click Add/Remove columns. 3. Select Value. 4. Click OK. 5. In the Value column, click on the value. 6. Enter the value for the configuration property. seconds. 7. On the File menu, click Save. In this example, enter 10
Tip
When all configuration properties are defined for a LonWorks device, you can copy and paste the device in the System Tree pane and then rename it as a means to add another device of the same type and configuration to maximize engineering process efficiency. For our example, repeat the procedure for the following configuration properties. Configuration Properties in VAV 01 01 Node Object Location: ...University X ES1/Servers/CPlant AS/LonWorks Local FT-10 Interface/East Wing/VAVs/VAV 01 01/Node Object [0] Table: Configuration Properties in VAV 01 01 Node Object
Configuration Property nciRcvHrtBt nciMinSendTime Member Elapsed time Elapsed time Value 30 seconds 5 seconds
Configuration Properties in VAV 01 01 VAVController Location: ...University X ES1/Servers/CPlant AS/LonWorks Local FT-10 Interface/East Wing/VAVs/VAV 01 01/VAVController [8010]
04-13033-01-en, October 2012
6 Commissioning the LonWorks Network and Devices 6.4 Configuring a Configuration Property
Table: Configuration Properties in VAV 01 01 VAVController

Configuration Property nciMinDelTempSnd nciSetPnts Member Temperature Occupied cooling setpoint Occupied heating setpoint Standby cooling setpoint Standby heating setpoint Value 0.3 C (0.5 F) 23 C (74 F) 21 C (70 F) 24 C (76 F) 20 C (68 F)
Unoccupied cooling setpoint 27 C (80 F) Unoccupied heating setpoint 18 C (65 F)
Configuration Properties in VAV 01 02 Node Object Location: ...University X ES1/Servers/CPlant AS/LonWorks Local FT-10 Interface/East Wing/VAVs/VAV 01 02/Node Object [0] Table: Configuration Properties in VAV 01 02 Node Object
Configuration Property nciSndHrtBt nciRcvHrtBt nciMinSendTime Member Elapsed time Elapsed time Elapsed time Value 10 seconds 30 seconds 5 seconds
Configuration Properties in VAV 01 02 VAVController Location: ...University X ES1/Servers/CPlant AS/LonWorks Local FT-10 Interface/East Wing/VAVs/VAV 01 02/VAVController [8010] Table: Configuration Properties in VAV 01 02 VAVController
Configuration Property nciMinDelTempSnd nciSetPnts Member Temperature Occupied cooling setpoint Occupied heating setpoint Standby cooling setpoint Standby heating setpoint Value 0.3 C (0.5 F) 23 C (74 F) 21 C (70 F) 24 C (76 F) 20 C (68 F)
Unoccupied cooling setpoint 27 C (80 F) Unoccupied heating setpoint 18 C (65 F)
Note
More configurations than shown here in the example are necessary for all performance configurations to match the project requirements.
04-13033-01-en, October 2012
Creating the Local Node and Network Variables
Topics
Creating Network Variables Automatically Creating an Output Network Variable Configuring the Value and Propagation Delta for a Network Variable Member
7 Creating the Local Node and Network Variables
Our Example
In this chapter, you create network variables in the local node in the Automation Server by mirroring network variables in the LonWorks field bus devices. You create and bind multiple network variables in one action to maximize engineering efficiency. The Mirrored network variables command automatically creates the local node, which is required to add network variables in a server that will be bound to network variables in LonWorks field bus devices. The command also creates functional blocks, which are used to organize the network variables created in the local node. You also create one network variable manually, nvoOccCmd. Finally, you configure some properties of the network variables.
04-13033-01-en, October 2012
7 Creating the Local Node and Network Variables 7.1 Creating Network Variables Automatically
7.1
Creating Network Variables Automatically

You create network variables in the local node by mirroring network variables in LonWorks field bus devices when you want to create and bind multiple network variables in one action, which saves you engineering time. For more information, see WebHelp. In this example, you create bound counterparts in the local node of network variables in the AHU 01 device. The mirrored network variables are created in the local node, within a functional block named AHU 01. The local node and the functional block are automatically created.
To create network variables automatically

1. In WorkStation, in the System Tree pane, in the LonWorks network, select the functional block that contains the network variables that you want to be represented in the local node. In this example, select ...University X ES1/Servers/CPlant AS/LonWorks Local FT-10 Interface/East Wing/AHUs/AHU 01/SFPTcontroller [5]. 2. In the List View, select the network variables that you want to be represented in the local node. In this example, select nviAHUOccCmd, nviDatSP, nviStPrSP, nviVentReq, nvoFanStatus, and nvoVlvPosn. 3. On the File menu, point to New and then click Mirrored network variables. Mirrored network variables of the network variables that you selected, are automatically created and bound in the local node, within functional blocks that are also automatically created and named according to the LonWorks devices from where the network variables originate.
Note
This procedure uses a lot of the Automation Server CPU and takes some time to complete. System alarms might be triggered. In this example, repeat the procedure to create bound counterparts in the local node of the following network variables: VAV 01 01 Network Variables Location: ...University X ES1/Servers/CPlant AS/LonWorks Local FT-10 Interface/East Wing/VAVs/VAV 01 01/VAVController [8010] Name: nvoMotorPositn nvoOccpncyStatus nvoSpaceTemp nvoTerminalLoad VAV 01 02 Network Variables Location: ...University X ES1/Servers/CPlant AS/LonWorks Local FT-10 Interface/East Wing/VAVs/VAV 01 02/VAVController [8010]
04-13033-01-en, October 2012
7 Creating the Local Node and Network Variables 7.1 Creating Network Variables Automatically
Name: nvoMotorPositn nvoOccpncyStatus nvoSpaceTemp nvoTerminalLoad The mirrored network variables are created in the local node, within functional blocks that are automatically created and named VAV 01 01 and VAV 01 02 respectively.
04-13033-01-en, October 2012
7 Creating the Local Node and Network Variables 7.2 Creating an Output Network Variable
7.2
Creating an Output Network Variable

You create output network variables in functional blocks in a local node for binding LonWorks variables between the Automation Server and the Xenta 280/300/401 LonWorks devices or other LonWorks devices. For more information, see WebHelp. In this example, you create an output network variable called nvoOccCmd in the AHU 01 functional block that will be bound to the nviOccCmd SNVTs in VAV 01 01 and VAV 01 02 (Xenta 102-AX devices).
To create an output network variable

1. In WorkStation, in the System Tree pane, select the functional block where you want to create the variable. In this example, select ...University X ES1/Servers/CPlant AS/LonWorks Local FT-10 Interface/East Wing/Local Node/AHU 01. 2. On the File menu, point to New and then click Network Variable. 3. In the Resource files kit box, select the DRF that contains the types for the variable. In this example, select standard.
4. In the Type box, select the type of variable. SNVT_occupancy. 5. In the Direction box, select Output.
In this example, select
6. In the Name box, type a name for the variable. nvoOccCmd. 7. Click Next.
04-13033-01-en, October 2012
7 Creating the Local Node and Network Variables 7.2 Creating an Output Network Variable
8. In the Sending enabled box, select Yes to send the variables at periodic intervals.
9. In the Send rate box, enter the number of seconds between the sends. this example, enter 60. 10. In the Initial Value box, enter the initial value for the variable. example, enter OC_OCCUPIED. In this
In
11. In the Delta box, select the delta to be used before sending the value. this example, select At any change. 12. Click Create.
In
04-13033-01-en, October 2012
7 Creating the Local Node and Network Variables 7.3 Configuring the Value and Propagation Delta for a Network Variable Member
7.3
Configuring the Value and Propagation Delta for a Network Variable Member
You can configure the value and the propagation delta for value changes for a network variable member by editing its properties. For more information, see WebHelp. In this example, you configure the value and the propagation delta for the network variable member named Occupancy, which is a member of the network variable named nvoAHUOccCmd in the local node.
To configure the value and propagation delta for a network variable member
1. In WorkStation, in the System Tree pane, expand the network variable and then select the variable member. In this example, expand ...University X ES1/Servers/CPlant AS/LonWorks Local FT-10 Interface/East Wing/Local Node/AHU 01/nvoAHUOccCmd SFPTcontroller [5] and select Occupancy. 2. On the File menu, click Properties. 3. In the Propagation delta for value changes box, select At any change or Off, or type a delta value. In this example, select At any change.
4. In the Value box, enter the value of the variable. OC_OCCUPIED. 5. Click OK.
In this example, enter
In this example, repeat the procedure to configure the value and the propagation delta for the network variable members Temperature, Pressure (gauge), and Occupancy, which are members of the network variables nvoDatSP, nvoStPrSP, and nvoVentReq respectively in the local node. Use the following settings:
04-13033-01-en, October 2012
7 Creating the Local Node and Network Variables 7.3 Configuring the Value and Propagation Delta for a Network Variable Member
Table: nvoDatSP Temperature

Component Location Setting ...University X ES1/Servers/CPlant AS/LonWorks Local FT-10 Interface/East Wing/Local Node/AHU 01/nvoDatSP SFPTcontroller [5]/Temperature 0.5 13 C (55 F)
Propagation delta for value changes Value
Table: nvoStPrSP Pressure (gauge)

Component Location Setting ...University X ES1/Servers/CPlant AS/LonWorks Local FT-10 Interface/East Wing/Local Node/AHU 01/nvoStPrSP SFPTcontroller [5]/Pressure (gauge) 0.5 1.0 Pa (water pressure)
Table: nvoVentReq Occupancy

Component Location Setting ...University X ES1/Servers/CPlant AS/LonWorks Local FT-10 Interface/East Wing/Local Node/AHU 01/nvoVentReq SFPTcontroller [5]/Occupancy At any change OC_OCCUPIED
04-13033-01-en, October 2012
Creating Programs, Alarms, and Schedules in the Automation Server
Topics
Creating a Function Block Program Importing Function Block Program Code Creating a Change of State Alarm Creating a Digital Schedule Configuring a Schedule as a Shadow
8 Creating Programs, Alarms, and Schedules in the Automation Server
Our Example
In this chapter, you ensure that the programming is in place for controlling the East Wing. In the Automation Server, you create four function block programs: DischAirTempSP, Occupancy, StaticPressSP, and VAVAlarms. The actual program code has already been completed, so you import the program code into the individual function block programs. You create change of state alarms that are triggered when the Zone01 and Zone02 temperatures, which are sent from the VAVs to the Automation Server, exceed or fall below the limits established in the Automation Server programming. Finally, you create a digital schedule named AHUSchedule and configure it as a shadow schedule of the Cooling Plant Enable Schedule. The Occupancy program will use the value of the AHUSchedule to control the Air Handling Unit.
04-13033-01-en, October 2012
8 Creating Programs, Alarms, and Schedules in the Automation Server 8.1 Creating a Function Block Program
8.1
Creating a Function Block Program

You create a Function Block program to import existing program code or to program new logic for the Automation Server using Function Block Editor. For more information, see WebHelp. In this example, you create the DischAirTempSP function block program in the Automation Server, which will be used in conjunction with the field bus devices to control the Air Handling system. You can use Function Block programs or Script programs in the Automation Server. You use Function Block programs in this example, but you can also use Script programs for the same control logic in the Automation Server. For example, you can use a Function Block program to control Secondary Chilled Water Pump 1 and a Script program to control Secondary Chilled Water Pump 2 in the same Automation Server. When you decide to use Function Block programming or Script programming, consider the engineer's familiarity with programming tools and whether the programs require standard programming features or customized details.
To create a function block program

1. In WorkStation, in the System Tree pane, select the server or folder where you want to create the function block program. In this example, select ...University X ES1/Servers/CPlant AS/AHU 01/Programs. 2. On the File menu, point to New and then click Program. 3. In the object type list, select Function Block Program.
4. In the Name box, type a name for the function block program. example, type DischAirTempSP. 5. Click Create.
In this
04-13033-01-en, October 2012
8 Creating Programs, Alarms, and Schedules in the Automation Server 8.1 Creating a Function Block Program
In this example, repeat the procedure to create the following function block programs: Location: ...University X ES1/Servers/CPlant AS/AHU 01/Programs Name: Occupancy StaticPressSP VAVAlarms
04-13033-01-en, October 2012
8 Creating Programs, Alarms, and Schedules in the Automation Server 8.2 Importing Function Block Program Code
8.2
Importing Function Block Program Code

You import function block program code to reuse all or parts of existing code. Function Block Editor supports import of .aut and .mta files created for Xenta 280/300/400 LonWorks devices in Menta Editor, as well as .aut file previously created in Function Block Editor. For more information, see WebHelp. In this example, you import program code to the DischAirTempSP function block program for use in the Automation Server.
To import function block program code

1. In WorkStation, in the System Tree pane, select the function block program you want to import program code to. In this example, select ...University X ES1/Servers/CPlant AS/AHU 01/Programs/DischAirTempSP. 2. On the Actions menu, click Edit. 3. In Function Block Editor, on the File menu, click Import. 4. Select the file you want to import. 5. Click Open. In this example, select DatSP.AUT.
04-13033-01-en, October 2012
8 Creating Programs, Alarms, and Schedules in the Automation Server 8.2 Importing Function Block Program Code
6. On the File menu, click Save.
Tip
When a Menta file is imported, TSCH blocks and ALARM blocks are removed, AI/DI blocks are converted to RI/BI blocks, and AO/DO blocks are converted to RO/BO blocks. As a result of these conversions, you may need to make adjustments to the imported Menta code. In this example, repeat the procedure to import .aut files to the following Function Block programs: Occupancy Object location: ...University X ES1/Servers/CPlant AS/AHU 01/Programs/Occupancy File name: OccupancyPgm.AUT StaticPressSP Object location: ...University X ES1/Servers/CPlant AS/AHU 01/Programs/StaticPressSP File name: StPrSP.AUT VAVAlarms Object location: ...University X ES1/Servers/CPlant AS/AHU 01/Programs/VAVAlarms File name: VAVAlarms.AUT
04-13033-01-en, October 2012
8 Creating Programs, Alarms, and Schedules in the Automation Server 8.3 Creating a Change of State Alarm
8.3
Creating a Change of State Alarm

You create a change of state alarm to trigger an alarm when a variable, such as a switch, is either true or false. For more information, see WebHelp. In this example, you create a change of state alarm called VAV 01 TempAlarm to monitor VAV_01_TempAlarm in the VAVAlarms Function Block program.
To create a change of state alarm

1. In WorkStation, in the System Tree pane, select the folder or server where you want to create the alarm. In this example, select ...University X ES1/Servers/CPlant AS/AHU 01/Alarms. 2. On the File menu, point to New and then click Alarm. 3. In the object type list, select Change of State Alarm.
4. In the Name box, type a name for the alarm. TempAlarm.
In this example, type VAV 01 In this example,
5. In the Description box, type a description for the alarm. type Monitors the VAV 01/Zone 01 Temperature. 6. Click Next.
04-13033-01-en, October 2012
7. Select the state of the monitored variable that triggers the alarm: Click True to trigger the alarm when the monitored variable is equal to True. Click False to trigger the alarm when the monitored variable is equal to False. In this example, click True.
8. In the Monitored variable box, enter the variable that the alarm monitors. In this example, enter ...University X ES1/Servers/CPlant AS/AHU 01/Programs/VAVAlarms/VAV_01_TempAlarm. 9. Under Time delay and shunt variable, in the Alarm delay box, enter the time delay. In this example, enter 5. 10. In the Reset delay box, enter the time delay. 11. Click Next.
In this example, enter 5.
04-13033-01-en, October 2012
12. In the Alarm message box, type the message to display when the monitored variable exceeds the alarm limit. In this example, type The Zone 01 Temperature is too high.
13. In the Reset message box, type the message to display when the alarm is reset. In this example, type The Zone 01 Temperature has returned to normal. 14. In the Alarm priority box, enter the priority for the alarm state. example, enter 2. 15. In the Reset priority box, enter the priority for the reset state. example, enter 10. In this In this
16. Under Category and Alerts, select the Flashing alert check box to make the alarm flash in the Alarms pane and Alarm Views when it is triggered. In this example, select Flashing alert.
04-13033-01-en, October 2012
17. Select the Audible alert check box to make the alarm sound when it is triggered. In this example, select Audible alert.
18. Click Next.

04-13033-01-en, October 2012
19. Select the type of acknowledgement to use: Click No when the alarm does not need to be acknowledged. Click Single when the alarm needs to be acknowledged in the alarm state. Click Extended when the alarm needs to be acknowledged in the alarm state and the reset state. In this example, click Single.
20. Click Next. 21. Click Create. In our example, repeat the procedure to create a change of state alarm called VAV 02 TempAlarm to monitor VAV_02_TempAlarm in the VAVAlarms Function Block program. Table: VAV 02 TempAlarm
Component Location Name Description Trigger value Monitored variable Setting ...University X ES1/Servers/CPlant AS/AHU 01/Alarms VAV 02 TempAlarm Monitors the VAV 02/Zone 02 Temperature True ...University X ES1/Servers/CPlant AS/AHU 01/Programs/VAVAlarms/VAV_02_TempAla rm 5
04-13033-01-en, October 2012
Alarm delay (s)

Continued
Component Reset delay (s) Shunt variable Alarm message Reset message Alarm priority Reset priority Category Flashing alert Audible alert Acknowledgement type Attachment Setting 5 No The Zone 02 Temperature is too high The Zone 02 Temperature has returned to normal 2 10 No Yes Yes Single No
04-13033-01-en, October 2012
8 Creating Programs, Alarms, and Schedules in the Automation Server 8.4 Creating a Digital Schedule
8.4
Creating a Digital Schedule

You create a digital schedule to control the state of a digital value. For more information, see WebHelp. In this example, you create a digital schedule that will be used as a shadow schedule to the Cooling Plant Enable Schedule.
To create a digital schedule

1. In WorkStation, in the System Tree pane, select the server or the folder where you want to create the schedule. In this example, select ...University X ES1/Servers/CPlant AS/AHU 01/Schedules. 2. On the File menu, point to New and then click Schedule. 3. In the object type list, select Digital Schedule.
4. In the Name box, type a name for the schedule. AHUSchedule. 5. Click Create.
Now you can add events to the digital schedule and bind it to a digital value.
04-13033-01-en, October 2012
8 Creating Programs, Alarms, and Schedules in the Automation Server 8.5 Configuring a Schedule as a Shadow
8.5
Configuring a Schedule as a Shadow

You configure a schedule as a shadow to synchronize it with a schedule that already contains all weekly events and exception events. For more information, see WebHelp. In this example, you configure the digital schedule named AHUSchedule as a shadow schedule of the Cooling Plant Enable Schedule.
To configure a schedule as a shadow

1. In WorkStation, in the System Tree pane, select the schedule you want to configure as a shadow. In this example, select ...University X ES1/Servers/CPlant AS/AHU 01/Schedules/AHUSchedule. 2. On the File menu, click Properties. 3. In the Lead object box, enter the schedule that you want to synchronize the shadow schedule with. In this example, enter ...University X ES1/Servers/CPlant AS/Cooling Application/Schedules/Cooling Plant Enable Schedule.
4. Click OK.
04-13033-01-en, October 2012
Creating Bindings for Communication
Topics
Creating a LonWorks Binding Importing a Solution Binding Values Using a Binding Template
9 Creating Bindings for Communication
Our Example
In this chapter, you create bindings, which are used to designate what is to be communicated and how the designated communication is to occur. Bindings are created between LonWorks variables, the Automation Server, and the Xenta 280/300/401 LonWorks devices or other LonWorks devices. You create a LonWorks binding to communicate with a LonWorks device because it enables event-driven communication, which is more efficient than communication using the polling method. You create a Building Operation binding to bind points in a Building Operation server program, graphics, alarm, or trend log to LonWorks network variables in the local node. In our example, you create bindings to establish data flow in and out of Automation Server programs. For engineering efficiency, you import two custom binding templates that you use to create the necessary bindings.
04-13033-01-en, October 2012
9 Creating Bindings for Communication 9.1 Creating a LonWorks Binding
9.1
Creating a LonWorks Binding

You create a LonWorks binding between the Automation Server local node and a LonWorks device or between two LonWorks devices. You create the binding between LonWorks Network Variables or Configuration Parameters (NV based). You use a LonWorks binding to communicate with a LonWorks device because it enables event-driven communication, which is more efficient than communication using the polling method. For more information, see WebHelp. In this example, you create the LonWorks binding between the nvoOccCmd output variable in the AHU 01 Functional Block in the CPlant AS Local Node and the nviOccCmd input variable in the VAV 01 01 device.
To create a LonWorks binding

1. In WorkStation, in the System Tree pane, select the local node or device for which you want to create a LonWorks binding. In this example, select ...University X ES1/Servers/CPlant AS/LonWorks Local FT-10 Interface/East Wing/Local Node. 2. On the Actions menu, click Edit bindings. 3. In the binding point list, select the variable you want to bind to. example, select AHU 01/Outputs/nvoOccCmd. In this
4. In the binding point browser, select the device to bind from. In this example, select ...University X ES1/Servers/CPlant AS/LonWorks Local FT-10 Interface/East Wing/VAVs/VAV 01 01. 5. Expand the selected device to display the variables that are available to be bound.
04-13033-01-en, October 2012
9 Creating Bindings for Communication 9.1 Creating a LonWorks Binding
6. Select the variable to be bound and drag it to the binding box for the variable in the binding point list. In this example, drag VAVController [8010]/nviOccCmd to the binding box for nvoOccCmd.
Important
To bind more than one variable to a binding point, drag the variable to the name of the binding point. Each binding adds a row to the binding point. 7. On the File menu, click Save.
Tip
You cannot use a custom binding template when you create LonWorks bindings. Custom binding templates can be used when you create Building Operation bindings. For our example, repeat the procedure to complete the following LonWorks binding. Note that the binding profile is automatically updated to Unacknowledged Repeated Profile, which is the correct binding profile to use for this group binding. Local Node Bindings Path to Local Node: ...University X ES1/Servers/CPlant AS/LonWorks Local FT10 Interface/East Wing/Local Node Table: AHU 01/Outputs
Binding Point nvoOccCmd Binding ~/LonWorks Local FT-10 Interface/East Wing/VAVs/VAV 01 02/VAVController [8010]/nviOccCmd
04-13033-01-en, October 2012
9 Creating Bindings for Communication 9.2 Importing a Solution
9.2
Importing a Solution
You import a solution that was created or modified on another Building Operation server. You can also use the standard copy and paste method to copy solutions to other file locations on the same server. For more information, see WebHelp. In this example, you import a file that contains a custom binding template to be used to create bindings for data flow between programs in the Automation Server and the Xenta LonWorks devices.
To import a solution
1. In WorkStation, in the System Tree pane or List View, select a location where you want to import a solution. In this example, select ...University X ES1/Servers/CPlant AS/System/Binding Templates. 2. On the File menu, click Import. 3. In the Open dialog box, select the file and click Open. select DataFromLocalNodeTemplate.xml. 4. In the Import dialog box, click Import. In this example,
04-13033-01-en, October 2012
9 Creating Bindings for Communication 9.2 Importing a Solution
For this example, repeat the procedure to import a custom binding template to be used to create bindings for data flow between Automation Server programs and schedules. Location: ...University X ES1/Servers/CPlant AS/System/Binding Templates File name: SchedAndAlarmsTemplate.xml
04-13033-01-en, October 2012
9 Creating Bindings for Communication 9.3 Binding Values Using a Binding Template
9.3
Binding Values Using a Binding Template

You use binding templates to reduce engineering time when creating bindings. Binding templates are defined and created for binding patterns that are frequently reused.
Tip
When creating bindings, follow the recommended general guidelines: create bindings between Inputs and Outputs only and do not create bindings to Public Signals. For more information, see WebHelp. In this example, you create the bindings for the DischAirTempSP program in the Automation Server AHU 01 folder. You use the custom binding template named Values From Local Node to create the required bindings. The created bindings are internal to the Automation Server.
To bind values using a binding template

1. In WorkStation, in the System Tree pane, select the object that you want to bind values to. In this example, select ...University X ES1/Servers/CPlant AS/AHU 01/Programs/DischAirTempSP. 2. On the Actions menu, click Edit bindings. 3. In the binding point browser, drag the object or folder to the binding template that you want to apply. In this example, drag ...University X ES1/Servers/CPlant AS/LonWorks Local FT-10 Interface/East Wing/Local Node to the Values From Local Node custom binding template.
04-13033-01-en, October 2012
4. Select the bindings that you want to create. bindings selected.
In this example, keep all
5. Click OK. 6. Verify that all bindings are correctly bound. bindings against the table below. In this example, verify the
Tip
To ensure data flow is occurring as intended, use the Watch pane to view values and monitor changes. DischAirTempSP Program in the Automation Server AHU 01 Folder Table: Results Verification DischAirTempSP Program Bindings
Binding Point Input - VAV_01_TerminalLoad Binding ~/LonWorks Local FT-10 Interface/East Wing/Local Node/VAV 01 01/nviTerminalLoad VAVController [8010]/Percentage level/Value ~/LonWorks Local FT-10 Interface/East Wing/Local Node/VAV 01 02/nviTerminalLoad VAVController [8010]/Percentage level/Value
Input - VAV_02_TerminalLoad
04-13033-01-en, October 2012
Continued
Binding Point Output - DatSP Binding ~/LonWorks Local FT-10 Interface/East Wing/Local Node/AHU 01/nvoDatSP SFPTcontroller [5]/Temperature/Value
For this example, repeat the procedure to create the required bindings for the other supervisory programs in the Automation Server. Use the following settings: Occupancy Program in the Automation Server AHU 01 Folder Create the bindings for the ...University X ES1/Servers/CPlant AS/AHU 01/Programs/Occupancy program: Drag ...University X ES1/Servers/CPlant AS/LonWorks Local FT-10 Interface/East Wing/Local Node to the Values From Local Node custom binding template. Drag ...University X ES1/Servers/CPlant AS/AHU 01 to the Schedules and Alarms custom binding template. Table: Results Verification Occupancy Program Bindings
Binding Point Input - AHUSchedule Input - VAV_01_OccpncyStatus Binding ~/AHU 01/Schedules/AHUSchedule/Value ~/LonWorks Local FT-10 Interface/East Wing/Local Node/VAV 01 01/nviOccpncyStatus VAVController [8010]/Occupancy/Value ~/LonWorks Local FT-10 Interface/East Wing/Local Node/VAV 01 02/nviOccpncyStatus VAVController [8010]/Occupancy/Value ~/LonWorks Local FT-10 Interface/East Wing/Local Node/AHU 01/nvoAHUOccCmd SFPTcontroller [5]/Occupancy/Value ~/LonWorks Local FT-10 Interface/East Wing/Local Node/AHU 01/nvoOccCmd/Occupancy/Value ~/LonWorks Local FT-10 Interface/East Wing/Local Node/AHU 01/nvoVentReq SFPTcontroller [5]/Occupancy/Value
Input VAV_02_OccpncyStatus
Output AHUOccCmd
Output OccCmd
Output VentReq
StaticPressSP Program in the Automation Server AHU 01 Folder Create the bindings for the ...University X ES1/Servers/CPlant AS/AHU 01/Programs/StaticPressSP program: Drag ...University X ES1/Servers/CPlant AS/LonWorks Local FT-10 Interface/East Wing/Local Node to the Values From Local Node custom binding template.
04-13033-01-en, October 2012
Table: Results Verification StaticPressSP Program Bindings

Binding Point Input - VAV_01_MotorPositn Binding ~/LonWorks Local FT-10 Interface/East Wing/Local Node/VAV 01 01/nviMotorPositn VAVController [8010]/Percentage level/Value ~/LonWorks Local FT-10 Interface/East Wing/Local Node/VAV 01 02/nviMotorPositn VAVController [8010]/Percentage level/Value ~/LonWorks Local FT-10 Interface/East Wing/Local Node/AHU 01/nvoStPrSP SFPTcontroller [5]/Pressure (gauge)/Value
Input - VAV_02_MotorPositn
Output - StPrSP
VAVAlarms Program in the Automation Server AHU 01 Folder Create the bindings for the ...University X ES1/Servers/CPlant AS/AHU 01/Programs/VAVAlarms program: Drag ...University X ES1/Servers/CPlant AS/LonWorks Local FT-10 Interface/East Wing/Local Node to the Values From Local Node custom binding template. Table: Results Verification VAVAlarms Program Bindings
Binding Point Input - AHU_01_FanStatus Binding ~/LonWorks Local FT-10 Interface/East Wing/Local Node/AHU 01/nviFanStatus SFPTcontroller [5]/Discrete level/Value ~/LonWorks Local FT-10 Interface/East Wing/Local Node/VAV 01 01/nviSpaceTemp VAVController [8010]/Temperature/Value ~/LonWorks Local FT-10 Interface/East Wing/Local Node/VAV 01 02/nviSpaceTemp VAVController [8010]/Temperature/Value
Input - VAV_01_SpaceTemp
Input - VAV_02_SpaceTemp
04-13033-01-en, October 2012
10
Replacing a LonWorks Device
Topics
Uploading the LonWorks Device Configuration Replacing an Online LonWorks Device
10 Replacing a LonWorks Device
Our Example
In this chapter, you replace a LonWorks device that is online. The reason why you need to replace a device could be, for example, that its inputs and outputs have been damaged. First, you upload the device configuration from the physical device to update the configuration parameters stored in the Building Operation server. You do this because you want to save the local configuration, which might have been changed through an operator panel. You decommission the old device before you remove the physical device. You then install the new (or decommissioned) physical device. You press the service pin on the new physical device to retrieve its Neuron ID and update the server with this information. Finally, you commission the new device and download the device configuration from the server to update the configuration parameters in the new physical device.
04-13033-01-en, October 2012
10 Replacing a LonWorks Device 10.1 Uploading the LonWorks Device Configuration
10.1
Uploading the LonWorks Device Configuration

You upload the device configuration from the LonWorks device to update the configuration parameters in the Building Operation server with local device configuration changes, which have been made through, for example, an operator panel.
Important
Before uploading the device configuration from a device, carefully consider the effects of overwriting the current device configuration in the Building Operation server. In this example, you upload the device configuration from the VAV 01 01 device.
To upload the LonWorks device configuration

1. In WorkStation, in the System Tree pane, select the LonWorks device. In this example, select ...University X ES1/Servers/CPlant AS/LonWorks Local FT-10 Interface/East Wing/VAVs/VAV 01 01. 2. On the Actions menu, click Upload device configuration. The configuration is uploaded to the Building Operation server.
04-13033-01-en, October 2012
10 Replacing a LonWorks Device 10.2 Replacing an Online LonWorks Device
10.2
Replacing an Online LonWorks Device

You replace a physical LonWorks device because of malfunction issues, new requirements, or misplacement. For more information, see WebHelp. In this example, you replace the VAV 01 01 device.
To replace an online LonWorks device

1. In WorkStation, in the System Tree pane, select the LonWorks device that you want to replace. In this example, select ...University X ES1/Servers/CPlant AS/LonWorks Local FT-10 Interface/East Wing/VAVs/VAV 01 01.
Tip
If the device configuration in the physical LonWorks device is not synchronized with the configuration that is stored in the Building Operation server, you can upload the device configuration to the Building Operation server before you decommission and remove the LonWorks device. For more information, see section 10.1 Uploading the LonWorks Device Configuration on page 100. 2. On the Actions menu, click Decommission. 3. Remove the old physical LonWorks device. 4. Install the new physical LonWorks device. 5. On the Actions menu, click Commission.
04-13033-01-en, October 2012
10 Replacing a LonWorks Device 10.2 Replacing an Online LonWorks Device
6. In the Neuron ID box, type or retrieve the Neuron ID of the new LonWorks device: Type the Neuron ID in the box. Click Service Pin and then press the service pin on the physical device to retrieve the Neuron ID. In this example, click Service Pin and then press the service pin on the physical Lonworks device.
7. Click Download current configuration to device. 8. Click Commission. 9. Click Close. The LonWorks device is replaced, commissioned, and activated.
04-13033-01-en, October 2012
11
Replacing a Xenta Device
Topics
Uploading the Xenta Device Configuration Replacing an Online Xenta Device Downloading the Xenta Device Configuration
11 Replacing a Xenta Device
Our Example
In this chapter, you replace a Xenta 300 LonWorks device that is online. The reason why you need to replace a device could be, for example, that the interface toward the I/O module has been damaged. First, you upload the device configuration from the physical device to update the configuration parameters stored in the Building Operation server. You do this because you want to save the local configuration, which might have been changed through an operator panel. You decommission the old device before you remove the physical device. You then install the new (or decommissioned) physical device. You press the service pin on the new physical I/O module to retrieve its Neuron ID and update the server with this information. You commission the new device and download the Menta application to the physical device. Finally, you download the device configuration from the server to update the configuration parameters in the new physical device.
04-13033-01-en, October 2012
11 Replacing a Xenta Device 11.1 Uploading the Xenta Device Configuration
11.1
Uploading the Xenta Device Configuration

You upload the device configuration from the Xenta 280/300/401 LonWorks devices to update the configuration parameters in the Building Operation server with local device configuration changes, which have been made through, for example, an operator panel.
Important
Before uploading the device configuration from a device, carefully consider the effects of overwriting the current device configuration in the Building Operation server. For more information, see WebHelp. In this example, you upload the device configuration from the AHU 01 device.
To upload the Xenta device configuration

1. In WorkStation, in the System Tree pane, select the Xenta 280/300/401 LonWorks device that you want to upload the device configuration from. this example, select ...University X ES1/Servers/CPlant AS/LonWorks Local FT-10 Interface/East Wing/AHUs/AHU 01. 2. On the Actions menu, click Upload device configuration. The device configuration is uploaded to the Building Operation server. In
04-13033-01-en, October 2012
11 Replacing a Xenta Device 11.2 Replacing an Online Xenta Device
11.2
Replacing an Online Xenta Device

You replace a physical Xenta 280/300/401 LonWorks device because of malfunction issues, new requirements, or simply because of misplacement.
Important
Manually override essential equipment that is controlled by outputs on I/O modules. Otherwise, this equipment will be turned on and off during the application download.
Important
Replace a device with a new device or a decommissioned device. Do not install a commissioned device in a new network as the reused device might contain an application or an address that can cause serious problems in the new network. In this example, you replace the AHU 01 device.
To replace an online Xenta device

1. In WorkStation, in the System Tree pane, select the programmable Xenta device that you want to replace. In this example, select ...University X ES1/Servers/CPlant AS/LonWorks Local FT-10 Interface/East Wing/AHUs/AHU 01.
Tip
If the device configuration in the physical Xenta 280/300/401 LonWorks device is not synchronized with the configuration that is stored in WorkStation, you can upload the device configuration to WorkStation before you remove the Xenta 280/300/401 LonWorks device. For more information, see section 11.1 Uploading the Xenta Device Configuration on page 106. 2. On the Actions menu, click Decommission. 3. Remove the old physical Xenta 280/300/401 LonWorks device. 4. Install the new physical Xenta 280/300/401 LonWorks device. 5. On the Actions menu, click Commission.
04-13033-01-en, October 2012
11 Replacing a Xenta Device 11.2 Replacing an Online Xenta Device
6. In the Neuron ID box, type or retrieve the Neuron ID of the new Xenta 280/300/401 LonWorks device: Type the Neuron ID in the box. Click Service Pin and then press the service pin on the physical device to retrieve the Neuron ID. In this example, click Service Pin and then press the service pin on the physical device.
7. Select Application download. 8. Click Commission. 9. Click Close.
Important
Restore equipment that you manually overrode before you replaced the device. The Xenta 280/300/401 LonWorks device is replaced, the application is downloaded, and the device is commissioned and activated.
04-13033-01-en, October 2012
11 Replacing a Xenta Device 11.3 Downloading the Xenta Device Configuration
11.3
Downloading the Xenta Device Configuration

You download the device configuration from the Building Operation server to update the configuration parameters in the Xenta 280/300/401 LonWorks device.
Important
Before downloading the device configuration from the Building Operation server, carefully consider the effects of overwriting the current device configuration in the Xenta 280/300/401 LonWorks device. For more information, see WebHelp. In this example, you download the device configuration to the AHU 01 device.
To download the Xenta device configuration

1. In WorkStation, in the System Tree pane, select the Xenta 280/300/401 LonWorks device that you want to download the device configuration to. this example, select ...University X ES1/Servers/CPlant AS/LonWorks Local FT-10 Interface/East Wing/AHUs/AHU 01. 2. On the Actions menu, click Download device configuration. The configuration is downloaded to the Xenta 280/300/401 LonWorks device. In
04-13033-01-en, October 2012
12
Replacing a Xenta I/O Module
Topics
12 Replacing a Xenta I/O Module
Our Example
In this chapter, you replace a Xenta I/O module. First, you remove the old physical I/O module and then you install the new I/O module. You press the service pin on the new physical I/O module to retrieve its Neuron ID and update the server with this information. Finally, you commission and download the Menta application to the Xenta 300 LonWorks device to which the Xenta I/O module belongs.
04-13033-01-en, October 2012
12 Replacing a Xenta I/O Module 12.1 Replacing a Xenta I/O Module
12.1

You replace a physical Xenta I/O module because of malfunction issues, new requirements, or simply because of misplacement.
Important
Manually override essential equipment that is controlled by outputs on I/O modules. Otherwise, this equipment will be turned on and off during the application download. In this example, you replace the M1 I/O module, which belongs to the AHU 01 device.
To replace a Xenta I/O module

1. Remove the old physical Xenta I/O module. 2. Install the new physical Xenta I/O module. 3. In the System Tree pane, select the programmable Xenta device to which the Xenta I/O module belongs. In this example, select ...University X ES1/Servers/CPlant AS/LonWorks Local FT-10 Interface/East Wing/AHUs/AHU 01. 4. On the Actions menu, click Commission. 5. Verify the identity of the Xenta 280/300/401 LonWorks device by checking the Neuron ID.
04-13033-01-en, October 2012
6. Select Application download.
Important
Do not forget to select Application download before you commission the device, otherwise the application will not be downloaded properly.
04-13033-01-en, October 2012
7. Under IO modules, type or retrieve the Neuron ID of the new Xenta I/O module: Type the Neuron ID in the box. Click Service Pin and then press the service pin on the physical Xenta I/O module to retrieve the Neuron ID. In this example, click Service Pin and then press the service pin on the physical Xenta I/O module.
8. Click Commission. 9. Click Close.
Important
Restore equipment that you manually overrode before you replaced the device. The green LED on the new I/O module flashes at a normal, low frequency rate. The Out of sync icon is removed from the Xenta device in the System Tree pane.
04-13033-01-en, October 2012
13
Editing the Menta Application for a Commissioned Xenta Device
Topics
Uploading the Xenta Device Configuration Editing a Menta Application Commissioning a Xenta Device Downloading the Xenta Device Configuration
13 Editing the Menta Application for a Commissioned Xenta Device
Our Example
In this chapter, you edit the Menta application for a commissioned Xenta 300 LonWorks device. First, you upload the device configuration from the physical device to update the configuration parameters stored in the Building Operation server. You do this because you want to save the local configuration, which might have been changed through an operator panel. You edit the Menta application to change the control logic for the device. You commission the device and download the edited Menta application to the physical device. Finally, you download the device configuration from the server to update the configuration parameters in the physical device.
04-13033-01-en, October 2012
13 Editing the Menta Application for a Commissioned Xenta Device 13.1 Uploading the Xenta Device Configuration
13.1
Uploading the Xenta Device Configuration

You upload the device configuration from the Xenta 280/300/401 LonWorks devices to update the configuration parameters in the Building Operation server with local device configuration changes, which have been made through, for example, an operator panel.
Important
Before uploading the device configuration from a device, carefully consider the effects of overwriting the current device configuration in the Building Operation server. For more information, see WebHelp. In this example, you upload the device configuration from the AHU 01 device.
To upload the Xenta device configuration

1. In WorkStation, in the System Tree pane, select the Xenta 280/300/401 LonWorks device that you want to upload the device configuration from. this example, select ...University X ES1/Servers/CPlant AS/LonWorks Local FT-10 Interface/East Wing/AHUs/AHU 01. 2. On the Actions menu, click Upload device configuration. The device configuration is uploaded to the Building Operation server. In
04-13033-01-en, October 2012
13 Editing the Menta Application for a Commissioned Xenta Device 13.2 Editing a Menta Application
13.2
Editing a Menta Application

You edit a Menta application to change the control logic for a Xenta 280/300/401 LonWorks device. For more information, see WebHelp. In this example, you edit the Menta application for the AHU 01 device.
To edit a Menta application

1. In WorkStation, in the System Tree pane, select the device that you want to edit the Menta application for. In this example, select ...University X ES1/Servers/CPlant AS/LonWorks Local FT-10 Interface/East Wing/AHUs/AHU 01. 2. On the Actions menu, click Edit. 3. In Menta Editor, edit the application. In this example, add the following objects:
Tip
In Menta Editor, on the Options menu, click Simulate if you want to validate the program and identify the location of errors in the program.
Tip
In simulation mode, on the Commands menu, click Generate if you want to make sure that it is possible to generate the output files, for example, binary files, OP menu tree files, and .XIF file, for the program.
04-13033-01-en, October 2012
13 Editing the Menta Application for a Commissioned Xenta Device 13.3 Commissioning a Xenta Device
13.3

You commission physical Xenta 280/300/401 LonWorks devices to make them operational. The commission downloads the Menta application, gives the device a subnet node address, and sets the device status to online. After a commission, the device can communicate with other devices on the LonWorks network and execute its application. For more information, see WebHelp. In this example, you commission the Xenta 300 device (AHU 01) in the East Wing, LonWorks network.

1. In WorkStation, in the System Tree pane, select the device. In this example, select ...University X ES1/Servers/CPlant AS/LonWorks Local FT-10 Interface/East Wing/AHUs/AHU 01. 2. On the Actions menu, click Commission. 3. Select Application download to download the application program to the device.
4. Click Commission. 5. Click Close.
Tip
The Xenta I/O Modules communication automatically begins upon commissioning the Xenta 280/300/401 LonWorks device, as long as the I/O module's Neuron ID was associated to the I/O module prior to commissioning the Xenta 280/300/401 LonWorks device.
04-13033-01-en, October 2012
13 Editing the Menta Application for a Commissioned Xenta Device 13.4 Downloading the Xenta Device Configuration
13.4
Downloading the Xenta Device Configuration

You download the device configuration from the Building Operation server to update the configuration parameters in the Xenta 280/300/401 LonWorks device.
Important
Before downloading the device configuration from the Building Operation server, carefully consider the effects of overwriting the current device configuration in the Xenta 280/300/401 LonWorks device. For more information, see WebHelp. In this example, you download the device configuration to the AHU 01 device.
To download the Xenta device configuration

1. In WorkStation, in the System Tree pane, select the Xenta 280/300/401 LonWorks device that you want to download the device configuration to. this example, select ...University X ES1/Servers/CPlant AS/LonWorks Local FT-10 Interface/East Wing/AHUs/AHU 01. 2. On the Actions menu, click Download device configuration. The configuration is downloaded to the Xenta 280/300/401 LonWorks device. In
04-13033-01-en, October 2012
14
Adding a Xenta Device to a Commissioned LonWorks Network
Topics
Copying a Folder or Object Renaming a Folder or Object Discovering a Xenta Device Commissioning a Xenta Device Summary
14 Adding a Xenta Device to a Commissioned LonWorks Network
Our Example
In this chapter, you add a Xenta 300 LonWorks device to a commissioned LonWorks network. First, you copy the existing programmable Xenta device (AHU 01) in the Building Operation server and paste the copy in the same folder as the original. You then rename the new device to AHU 02. You discover the physically connected device to configure the new device (AHU 02) in the Building Operation server. You commission the new device and download the Menta application to the physical device. Finally, you commission the AHU 01 device to inform this device that the AHU 02 device has been added to the network and the Xenta group.
04-13033-01-en, October 2012
14 Adding a Xenta Device to a Commissioned LonWorks Network 14.1 Copying a Folder or Object
14.1
Copying a Folder or Object

You copy a folder or object when you quickly want to create a new folder or object. In this example, you copy the programmable Xenta device (AHU 01) and paste the copy (AHU 01_2) in the same folder.
To copy a folder or object

1. In WorkStation, in the System Tree pane, select the folder or object you want to copy. In this example, select ...University X ES1/Servers/CPlant AS/LonWorks Local FT-10 Interface/East Wing/AHUs/AHU 01. 2. On the Edit menu, click Copy. 3. In the System Tree pane, select the folder where you want to paste the copied folder or object. In this example, select ...University X ES1/Servers/CPlant AS/LonWorks Local FT-10 Interface/East Wing/AHUs. 4. On the Edit menu, click Paste.
04-13033-01-en, October 2012
14 Adding a Xenta Device to a Commissioned LonWorks Network 14.2 Renaming a Folder or Object
14.2
Renaming a Folder or Object

You rename a folder or object to make the name more suitable to your needs.
Note
When changing the name of a folder or server, you also have to reconfigure users and user groups path permissions to this server or folder. For more information, see WebHelp.
Note
You cannot change the name of a domain that is shared between servers. For more information, see WebHelp. In this example, you change the name of the copied programmable Xenta device from AHU 01_2 to AHU 02.
To rename a folder or object

1. In WorkStation, in the System Tree pane, select the folder or object you want to rename. In this example, select ...University X ES1/Servers/CPlant AS/LonWorks Local FT-10 Interface/East Wing/AHUs/AHU 01_2. 2. On the Edit menu, click Rename. 3. In the Rename object dialog box, type the new name. AHU 02. 4. Click OK. 5. In the Confirm Rename dialog box, click Yes. In this example, type
04-13033-01-en, October 2012
14 Adding a Xenta Device to a Commissioned LonWorks Network 14.3 Discovering a Xenta Device
14.3
Discovering a Xenta Device

You discover Xenta 280/300/401 LonWorks devices to create or configure the programmable Xenta devices in the Building Operation server. The Xenta 280/300/401 LonWorks devices must be physically connected to the Building Operation server field bus. For more information, see WebHelp. In this example, you discover the Xenta 300 device (AHU 02) in the East Wing network.
To discover a Xenta device

1. In WorkStation, in the System Tree pane, select the server that is connected to the device you want to discover. In this example, select ...University X ES1/Servers/CPlant AS. 2. Click the Device Discovery view. 3. In the Select device type box, select LonWorks.
4. Select the Devices folder. 5. On the Actions menu, click Activate listen to service pin. 6. Press the service pin on the physical device. In this example, press the service pin on the new Xenta 300 device, which is AHU 02.
04-13033-01-en, October 2012
14 Adding a Xenta Device to a Commissioned LonWorks Network 14.3 Discovering a Xenta Device
7. In the Device Discovery view, ensure that the Xenta device is displayed in the Devices folder. This may take up to 5 seconds.
8. On the Actions menu, click Deactivate listen to service pin. 9. Drag the discovered service pin (device) to the System Tree pane: Drag to an existing device to associate it with the discovered physical device. Drag to the LonWorks network to create the device. In this example, drag the discovered Service Pin device to ...University X ES1/Servers/CPlant AS/LonWorks Local FT-10 Interface/East Wing/AHUs/AHU 02.
Tip
To verify the device Neuron ID, select the device in the System Tree pane, and then select Properties on the File menu. The Neuron ID can be found on the Basic tab of the Device Properties.
04-13033-01-en, October 2012
14 Adding a Xenta Device to a Commissioned LonWorks Network 14.4 Commissioning a Xenta Device
14.4

You commission physical Xenta 280/300/401 LonWorks devices to make them operational. The commission downloads the Menta application, gives the device a subnet node address, and sets the device status to online. After a commission, the device can communicate with other devices on the LonWorks network and execute its application. For more information, see WebHelp. In this example, you commission the new AHU 02 device in the East Wing, LonWorks network. You need to recommission programmable Xenta devices (AHU 01) on a commissioned LonWorks network to inform the devices that a new device (AHU 02) has been added to the network. If you do not commission the devices again, they become out of sync. For more information, see WebHelp. The number of programmable Xenta devices you need to recommission depends on whether you have added the new device as member or master of a Xenta group. The following rule applies: Commission all Xenta group members if you have added a new group member. Commission all programmable Xenta devices on the LonWorks network if you add a new Xenta group master.

1. In WorkStation, in the System Tree pane, select the device. In this example, select ...University X ES1/Servers/CPlant AS/LonWorks Local FT-10 Interface/East Wing/AHUs/AHU 02. 2. On the Actions menu, click Commission. 3. Click Commission. 4. Click Close.
Tip
The Xenta I/O Modules communication automatically begins upon commissioning the Xenta 280/300/401 LonWorks device, as long as the I/O module's Neuron ID was associated to the I/O module prior to commissioning the Xenta 280/300/401 LonWorks device. In our example, repeat the procedure to commission the AHU 01 device again. Use the following settings: AHU 01 Location: ...University X ES1/Servers/CPlant AS/LonWorks Local FT-10 Interface/East Wing/AHUs/AHU 01 Application download: No
04-13033-01-en, October 2012
14 Adding a Xenta Device to a Commissioned LonWorks Network 14.5 Summary
14.5
Summary
The East Wing of the School of Business is now being controlled by a LonWorks network comprised of one Xenta 300 programmable device for the Air Handling Unit and two Xenta 102-AX application specific LonWorks devices for VAV damper control. As a result of LonWorks bindings, space temperature, occupancy status, terminal load, and damper position values are all inputs to the VAVs and the valve position and fan status values are inputs to the Air Handling Unit. Occupancy command, discharge air temperature setpoint, static pressure setpoint are all outputs to the Air Handling Unit. As a result of Building Operation bindings, terminal load, occupancy command, and VAV occupancy status and damper position, VAV temperature, and AHU fan status values are inputs to the programming in the Automation Server. Discharge air temperature setpoint, AHU and VAV occupancy command, ventilation request, static pressure setpoint, and VAV temperature alarm values are outputs from the programming in the Automation Server. The network of Xenta LonWorks and programmable devices are programmed and configured and are online and communicating. The Automation Server was already functioning as an IP controller for the Central Plant as a result of previous work in the system. Now the Automation Server is also functioning as an interface to the LonWorks network, a LonWorks device functioning as a data manager for the LonWorks network, and the Building Operation database server.
04-13033-01-en, October 2012
Schneider Electric | Buildings Division

www.schneider-electric.com/buildings 2012 Schneider Electric. All rights reserved. 04-13033-01-en October 2012

Creating and Configuring A LonWorks Network With Xenta LonWorks Devices

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Creating and Configuring A LonWorks Network With Xenta LonWorks Devices

Uploaded by

Copyright:

Available Formats

StruxureWare Building Operation

StruxureWare Building Operation

About This Guide ........................................................... 9

Additional Information .................................................. 15

Our Case Study ........................................................... 21

Creating the LonWorks Network .................................. 29

Adding Devices to the LonWorks Network ................... 39

Commissioning the LonWorks Network and Devices .... 47

Configuring a Configuration Property ........................................... 56

Creating the Local Node and Network Variables ........... 59

Creating Programs, Alarms, and Schedules in the Automation Server ....................................................... 69

Creating Bindings for Communication .......................... 85

Replacing a LonWorks Device ...................................... 97

Replacing a Xenta Device ........................................... 103

Replacing a Xenta I/O Module .................................... 111

Adding a Xenta Device to a Commissioned LonWorks Network ..................................................................... 125

Creating and Configuring a LonWorks Network with Xenta LonWorks Devices 6

04-13033-01-en, October 2012

About This Guide

1 About This Guide 1.1 Purpose of This Guide

Purpose of This Guide

04-13033-01-en, October 2012

Creating and Configuring a LonWorks Network with Xenta LonWorks Devices 11

1 About This Guide 1.2 How This Guide is Organized

How This Guide is Organized

Creating and Configuring a LonWorks Network with Xenta LonWorks Devices 12

04-13033-01-en, October 2012

1 About This Guide 1.3 Typographical Conventions

04-13033-01-en, October 2012

Creating and Configuring a LonWorks Network with Xenta LonWorks Devices 13

2 Additional Information 2.1 Where to Find Additional Information

Where to Find Additional Information

04-13033-01-en, October 2012

Creating and Configuring a LonWorks Network with Xenta LonWorks Devices 17

2 Additional Information 2.2 Regulatory Notices

WEEE - Directive of the European Union (EU)

CE - Compliance to European Union (EU)

C-Tick (Australian Communications Authority (ACA))

Federal Communications Commission

Creating and Configuring a LonWorks Network with Xenta LonWorks Devices 18

04-13033-01-en, October 2012

Our Case Study

3 Our Case Study 3.1 University X

Figure: The School of Business and the Central Plant

04-13033-01-en, October 2012

Creating and Configuring a LonWorks Network with Xenta LonWorks Devices 23

3 Our Case Study 3.1 University X

Figure: Cooling Plant diagram

Creating and Configuring a LonWorks Network with Xenta LonWorks Devices 24

04-13033-01-en, October 2012

3 Our Case Study 3.1 University X

Figure: Heating Plant diagram

04-13033-01-en, October 2012

Creating and Configuring a LonWorks Network with Xenta LonWorks Devices 25

3 Our Case Study 3.2 Requirements and Specifications

Requirements and Specifications

Devices Used for This Case Study

Software Used in This Tutorial

Creating and Configuring a LonWorks Network with Xenta LonWorks Devices 26

04-13033-01-en, October 2012

3 Our Case Study 3.3 Focus of This Tutorial

Focus of This Tutorial

Pre-existing Database Folder and Programs