creating and configuring a lonworks network with xenta lonworks devices

7/23/2019 Creating and Configuring a LonWorks Network With Xenta LonWorks Devices

1/136

StruxureWareStruxureWare BuildingBuilding OperationOperation

CreatingCreating andand ConfiguringConfiguring aa LonWorksLonWorks NetworkNetwork withwithXentaXenta LonWorksLonWorks DevicesDevices

TutorialTutorial GuideGuide

04-13033-01-enOctober 2012


2/136


3/136

StruxureWare Building Operation

Creating and Configuring a LonWorks Network withXenta LonWorks Devices

Tutorial Guide

04-13033-01-enOctober 2012


4/136

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 SchneiderElectric 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"), underthe 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, non-commercial 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 alsoagree 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 non-commercial 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.


5/136

Contents

IntroductionIntroduction

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

1.1 Purpose of This Guide ................................................................. 11

1.2 How This Guide is Organized ...................................................... 12

1.3 Typographical Conventions ......................................................... 13

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

2.1 Where to Find Additional Information ........................................... 17

2.2 Regulatory Notices ...................................................................... 18

TutorialTutorial

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

3.1 University X ................................................................................. 23

3.2 Requirements and Specifications ................................................ 26

3.2.1 Devices Used for This Case Study ............................................. 26

3.2.2 Software Used in This Tutorial ................................................... 26

3.2.3 Specifications ........................................................................... 26

3.3 Focus of This Tutorial .................................................................. 27

3.3.1 Pre-existing Database Folder and Programs .............................. 27

3.3.2 Pre-existing Database Objects .................................................. 28

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

4.1 Creating a LonWorks Interface .................................................... 32

4.2 Creating a LonWorks Network .................................................... 33

4.3 Changing the Domain ID for a LonWorks Network ....................... 34

4.4 Creating a Folder ........................................................................ 37

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

5.1 Creating a LonWorks Device ....................................................... 42

5.2 Creating a Programmable Xenta Device ...................................... 44

6 Commissioning the LonWorks Network and Devices .... 47

6.1 Discovering a Xenta Device ......................................................... 50

6.2 Commissioning a Xenta Device ................................................... 53

6.3 Commissioning a LonWorks Device ............................................ 54

04-13033-01-en, October 2012 Creating and Configuring a LonWorks Network with Xenta LonWorks Devices5


6/136

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

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

7.1 Creating Network Variables Automatically ................................... 62

7.2 Creating an Output Network Variable .......................................... 64

7.3 Configuring the Value and Propagation Delta for a Network VariableMember ...................................................................................... 66

8 Creating Programs, Alarms, and Schedules in theAutomation Server ....................................................... 69

8.1 Creating a Function Block Program ............................................. 72

8.2 Importing Function Block Program Code ..................................... 74

8.3 Creating a Change of State Alarm .............................................. 76

8.4 Creating a Digital Schedule ......................................................... 82

8.5 Configuring a Schedule as a Shadow ......................................... 83

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

9.1 Creating a LonWorks Binding ...................................................... 889.2 Importing a Solution .................................................................... 90

9.3 Binding Values Using a Binding Template .................................... 92

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

10.1 Uploading the LonWorks Device Configuration ......................... 100

10.2 Replacing an Online LonWorks Device ...................................... 101

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

11.1 Uploading the Xenta Device Configuration ................................. 106

11.2 Replacing an Online Xenta Device ............................................. 107

11.3 Downloading the Xenta Device Configuration ............................ 109

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

12.1 Replacing a Xenta I/O Module ................................................... 114

13 Editing the Menta Application for a Commissioned XentaDevice ....................................................................... 117

13.1 Uploading the Xenta Device Configuration ................................. 120

13.2 Editing a Menta Application ....................................................... 121

13.3 Commissioning a Xenta Device ................................................. 122

13.4 Downloading the Xenta Device Configuration ............................ 123

14 Adding a Xenta Device to a Commissioned LonWorks

Network ..................................................................... 12514.1 Copying a Folder or Object ........................................................ 128

14.2 Renaming a Folder or Object ..................................................... 129

14.3 Discovering a Xenta Device ....................................................... 130

14.4 Commissioning a Xenta Device ................................................. 132

14.5 Summary .................................................................................. 133

Creating and Configuring a LonWorks Network with Xenta LonWorks Devices 04-13033-01-en, October 20126


7/136

Introduction

The Introduction part contains information on the purpose

of this guide, how this guide is organized, where to findmore information, and information on regulatory notices.


8/136


9/136

AboutAbout ThisThis GuideGuide1

TopicsTopics

Purpose of This Guide

How This Guide is Organized

Typographical Conventions


10/136


11/136

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 networkconfigured with an Automation Server and Xenta devices.

This tutorial focuses on the following Building Operation Engineering Certificationobjectives:

Create a new Building Operation system using an Automation Server andXenta 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 andservers

Replace a device

Edit an application

Use standards and templates for efficient engineering



12/136

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 thisguide is organized, where to find more information, and information on regulatorynotices.

Tutorial

The Tutorial part contains a step-by-step description of how to carry out differenttasks. If you want more information, see WebHelp or the corresponding BuildingOperation Guide.

The Tutorial part includes a case study for a fictional customer cal led University X.You can decide if you want to follow the example or use the described proceduresas reference information. The case study in this tutorial is an example of a typicalway of configuring Building Operation for a customer. When reading through this

tutorial, you might not have access to the devices, programs, and other files thatare needed for the fictional customer University X. However, the purpose of havinga case study is to see the procedures put in context, so you see how theprocedures could be used when configuring Building Operation, devices, orprograms for your customer.



13/136

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.

13

Note

Provides you with supplementary information.

Important

Alerts you to supplementary information that is essential to the completion of atask.

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.

BoldBold texts:texts:

User interface items, such as property names and buttons, are written in bold, forexample "On the FileFile menu, select NewNew."

ExampleExample textstexts:

All the example related information is indicated by blue lines and bullets.

04-13033-01-en, October 2012 Creating and Configuring a LonWorks Network with Xenta LonWorks Devices


14/136


15/136

AdditionalAdditional InformationInformation2

TopicsTopics

Where to Find Additional Information

Regulatory Notices


16/136


17/136

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 DevicesTutorial 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 TutorialGuide

Creating and Configuring a LonWorks Network with MNL LonWorks DevicesTutorial Guide



18/136

2 Additional Information

2.2 Regulatory Notices

2.2 Regulatory Notices

UL 916 Listed products for the Unites States and Canada, OpenClass Energy Management Equipment.

WEEE - Directive of the European Union (EU)

This equipment and its packaging carry the waste of electrical and electronicequipment (WEEE) label, in compliance with European Union (EU) Directive2002/96/EC, governing the disposal and recycling of electrical and electronicequipment 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 EuropeanUnion, for governing the Self Declaration of the CE Marking for the European Unionas 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 CanadianInterference Causing Equipment Regulations.

C-Tick (Australian Communications Authority (ACA))

AS/NZS 3548

This equipment carries the C-Tick label and complies with EMC and radiocommunications 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 thefollowing two conditions: (1) This device may not cause harmful interference. (2)This device must accept any interference received, including interference that maycause undesired operation.



19/136


20/136


21/136

OurOur CaseCase StudyStudy3

When new knowledge is to be acquired, it is oftenadvantageous to work with a realistic example. For

this purpose we use a case study, which is basicallythe same in all Building Operation Tutorial Guides.

TopicsTopics

University X

Requirements and Specifications

Focus of This Tutorial


22/136


23/136

3 Our Case Study

3.1 University X

3.1 University X

We are going to install Building Operation as the building management system forUniversity X. The university is a campus of buildings for which heating and coolingare 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 theSchool of Business.

Figure: The School of Business and the Central Plant

The Cooling Plant consists of a single chiller with a primary-secondary pumpingsystem. The secondary water loop serves four VAV air handling units with chilledwater coils located in the School of Business. The secondary loop has two waterpumps. Only one pump is required for 100 % of the load. The second pumpprovides 100 % backup. The secondary pumps are variable speed. The primarychilled water loop has a single constant volume chilled water pump. The condenserloop 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, draw-through 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 thermalshock. The water leaving the condenser can be diverted back to the inlet of thecondenser without any cooling effect.



24/136

3 Our Case Study

3.1 University X

Figure: Cooling Plant diagram

The heating plant consists of two boilers in parallel, each with their own inlinepumps. Much of the time only one boiler is required to meet the load but undergreater load, both boilers will operate at the same time. The flow from the twoboilers comes together in a common supply header. There is a line from the supplyheader to the mechanical systems that require a source of hot water. This line hastwo constant volume distribution pumps in parallel. Only one is required to meetthe load. The second is back-up and lead-lag is used to alternate which pumpruns. The water returning from the mechanical systems flows into the return headerwhere it can be pumped by the inline pumps through the boilers. There is acommon line between the supply header and the return header. When the inlinepumps are flowing at a rate that exceeds the distribution pump flow rate, the waterflow in the common line is from the supply header to the return header. When thedistribution pump is flowing at a rate that exceeds the combined inline pump flowrates, flow in the common line is from the return header to the supply header. Eachboiler has its own self contained control system that interfaces with BuildingOperation through a combination of binary electrical control and network variables.The inline pumps are locally controlled by the self contained control system.



25/136

3 Our Case Study

3.1 University X

Figure: Heating Plant diagram



26/136

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 devicesand 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 SpecificationsYou find specifications in the Building Operation data sheets for Enterprise Server,WorkStation, PS-24V Power Supply, Automation Server, Xenta 300, Xenta421A/422A, and Xenta 102-AX.



27/136

3 Our Case Study

3.3 Focus of This Tutorial


The university requires the new East Wing of the School of Business to becontrolled using Xenta LonWorks devices. The equipment consists of one VAV-AirHandling Unit and two VAVs.

In this tutorial, you create and configure the LonWorks network and the Xentadevices 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 theAutomation 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 followingfolder 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:



28/136

3 Our Case Study


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 Operationdatabase prior to the creation and configuration of LonWorks network with XentaLonWorks devices:

...University X ES1/Servers/CPlant AS/Cooling Application/Schedules/CoolingPlant Enable Schedule



29/136

CreatingCreating thethe LonWorksLonWorks4NetworkNetwork

TopicsTopics

Creating a LonWorks Interface

Creating a LonWorks Network

Changing the Domain ID for a LonWorks Network

Creating a Folder


30/136


31/136

4 Creating the LonWorks Network

Our Example

In this chapter, you prepare the Automation Server to function as the LonWorksnetwork interface and create the LonWorks network so that LonWorks devices canbe added for controlling the East Wing of the School of Business. You also changethe domain ID for the LonWorks network to make it is possible to easily use theXenta Operator Panel for handheld servicing of the Xenta devices.

Additionally, you create a folder structure in the System Tree pane to ensure thatthe network is organized to maximize engineering and operating efficiency. Thefolder structure also represents the Xenta group organization for Xentaprogrammable devices added to the network for controlling Air Handling Units.



32/136


4.1 Creating a LonWorks Interface

4.1 Creating a LonWorks Interface

You create a LonWorks interface under the Building Operation server to connect toa LonWorks network.

For more information, see WebHelp.In this example, you create the LonWorks Local FT-10 Interface under the CPlantAS in the System Tree pane.

To create a LonWorks interface

1.1. In WorkStation, in the SystemSystem TreeTree pane, select the server where you want tocreate the interface. In this example, select ...University...University XXES1/Servers/CPlantES1/Servers/CPlant ASAS.

2.2. On the FileFile menu, point to NewNew and then clickInterfaceInterface.

3.3. In the object type list, select LonWorksLonWorks LocalLocal FT-10FT-10 InterfaceInterface or LonWorksLonWorksInterfaceInterface. In this example, select LonWorksLonWorks LocalLocal FT-10FT-10 InterfaceInterface.

4.4. In the NameName box, type a name for the interface. In this example, keep thedefault name LonWorks Local FT-10 Interface.

5.5. ClickCreateCreate.

You can now discover the interface and/or create the LonWorks network. You canalso configure the default settings of the interface.



33/136


4.2 Creating a LonWorks Network

4.2 Creating a LonWorks Network

You create a LonWorks network under the LonWorks interface to connect todevices 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 anew wing of the School of Business building. This building will be controlled by afield bus comprised of Xenta 280/300/401 LonWorks devices and other LonWorksdevices.

To create a LonWorks network

1.1. In WorkStation, in the SystemSystem TreeTree pane, select the LonWorks interfacewhere you want to create the network. In this example, select ...University...UniversityXX ES1/Servers/CPlantES1/Servers/CPlant AS/LonWorksAS/LonWorks LocalLocal FT-10FT-10 InterfaceInterface.

2.2. On the FileFile menu, point to NewNew and then clickLonWorksLonWorks NetworkNetwork.

3.3. In the NameName box, type a name for the network. In this example, type EastWing.

4.4. In the DescriptionDescription box, type a description. In this example, type School ofBusiness.




34/136


4.3 Changing the Domain ID for a LonWorks Network

4.3 Changing the Domain ID for aLonWorks 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 XentaOperator 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 XentaOperator Panel on Vista sites as well as Building Operation sites.

To change the domain ID for a LonWorks network

1.1. In WorkStation, in the SystemSystem TreeTree pane, select the LonWorks network thatyou want to change the domain ID for. In this example, select ...University...UniversityXX ES1/Servers/CPlantES1/Servers/CPlant AS/LonWorksAS/LonWorks LocalLocal FT-10FT-10 Interface/EastInterface/East WingWing.

2.2. On the FileFile menu, clickPropertiesProperties.

3.3. Click the AdvancedAdvanced tab.

4.4. Under DomainDomain tabletable forfor NetworkNetwork InterfaceInterface, select IndexIndex 00, and then clickEditEdit.

Continued on next page



35/136



5.5. In the IDID (decimal)(decimal) box, enter the domain ID. In this example, enter 1717.

6.6. ClickOKOK.




36/136



7.7. ClickOKOK.

Important

If there are commissioned devices connected to the LonWorksnetwork, you need to recommission the network as well as all

devices that indicate they are out of sync.

36Creating and Configuring a LonWorks Network with Xenta LonWorks Devices 04-13033-01-en, October 2012


37/136


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 iscreated. The AHUs folder represents the Xenta Group.

To create a folder

1.1. In WorkStation, in the SystemSystem TreeTree pane, select the folder, server, or networkwhere you want to create the folder. In this example, select ...University...University XXES1/Servers/CPlantES1/Servers/CPlant AS/LonWorksAS/LonWorks LocalLocal FT-10FT-10 Interface/EastInterface/East WingWing.

2.2. On the FileFile menu, point to NewNew and then clickFolderFolder.

3.3. In the NameName box, type a name for the folder. In this example, type AHUs.

4.4. In the DescriptionDescription box, type a description for the folder. In this example,type Programmable Xenta Devices location and a Xenta Group.


In our example, repeat the procedure to create the following folders:

Table: LonWorks Network Folders

NameName LocationLocation InformationInformation

VAVs ...University X Two Xenta 102-AXES1/Servers/CPlant LonWorks devices will be

AS/LonWorks Local FT-10 created and represent theInterface/East Wing LonWorks Group.



38/136



Table: Automation Server Folders

NameName LocationLocation InformationInformation

AHU 01 ...University X Function Block programs,ES1/Servers/CPlant AS alarms, schedules, trend

logs in the AutomationServer will be created andimported as part of the fieldbus control and supervisorylogic.

Alarms ...University X Alarm objects will be createdES1/Servers/CPlant AS/AHU in this folder to indicate field01 bus device variables that are

in alarm as part of theAutomation Server's functionas a supervisory logic deviceto the LonWorks field bus.

Programs ...University X Function Block programs willES1/Servers/CPlant AS/AHU be created and imported in01 this folder as the Automation

Server functions as asupervisory logic device tothe LonWorks field bus and,therefore, requiresprogramming.

Trends ...University X Trend log objects can beES1/Servers/CPlant AS/AHU created in this folder to log01 field bus device variables

from the LonWorks devicesas part of the AutomationServer's function as a

supervisory logic device tothe LonWorks field bus.

Schedules ...University X A schedule in theES1/Servers/CPlant AS/AHU Automation Server will be01 created in this folder to

control when the air system,controlled by LonWorksnetwork field bus devices,should be running.



39/136

AddingAdding DevicesDevices toto thethe5LonWorksLonWorks NetworkNetwork

TopicsTopics

Creating a LonWorks Device

Creating a Programmable Xenta Device


40/136


41/136

5 Adding Devices to the LonWorks Network

Our Example

In this chapter, you add both Xenta application-specific devices (Xenta LonWorksdevices that are configurable) and a programmable Xenta LonWorks device in theSystem Tree pane beneath the LonWorks Network.

The Xenta 102-AX devices, which are already programmed, are used for controllingthe VAV dampers. The Xenta 300 device is used for controlling the Air Handling Unitin the East Wing. The Menta program for the Xenta 300 device has already beenwritten, so you will import that existing program.



42/136


5.1 Creating a LonWorks Device


You create LonWorks devices under the LonWorks network to connect to physicalLonWorks 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 beencommissioned, so you create the LonWorks device using the offline procedures.

To create a LonWorks device

1.1. In WorkStation, in the SystemSystem TreeTree pane, select the LonWorks network orLonWorks network folder where you want to create the device. In thisexample, select ...University...University XX ES1/Servers/CPlantES1/Servers/CPlant AS/LonWorksAS/LonWorks LocalLocalFT-10FT-10 Interface/EastInterface/East Wing/VAVsWing/VAVs.

2.2. On the FileFile menu, point to NewNew and then clickDeviceDevice.

3.3. In the object type list, select a device template. In this example, select 102-102-AXAX.

4.4. In the NameName box, type a name for the device. In this example, type VAV 01

01.

Tip

The name of the LonWorks device must be unique in thenetwork, even for LonWorks devices in different folders in thenetwork.

42

5.5. In the DescriptionDescription box, type a description. In this example, type Xenta102-AX - fan powered terminal.




43/136



6.6. ClickNextNext.


In our example, repeat the procedure to create another LonWorks device. Use thefollowing settings:

LocationLocation: ...University X ES1/Servers/CPlant AS/LonWorks Local FT-10Interface/East Wing/VAVs

DeviceDevice templatetemplate: 102-AX

NameName: VAV 01 02

DescriptionDescription: Xenta 102-AX - fan powered terminal

NeuronNeuron IDID: Default value

CommissionCommission: No



44/136


5.2 Creating a Programmable Xenta Device


You create programmable Xenta devices under the LonWorks network to connectto 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 youcreate the Xenta 300 device using the offline procedures.

To create a programmable Xenta device

1.1. In WorkStation, in the SystemSystem TreeTree pane, select the LonWorks network orLonWorks network folder where you want to create the programmable Xentadevice. In this example, select ...University...University XX ES1/Servers/CPlantES1/Servers/CPlantAS/LonWorksAS/LonWorks LocalLocal FT-10FT-10 Interface/EastInterface/East Wing/AHUsWing/AHUs.

2.2. On the FileFile menu, point to NewNew and then clickDeviceDevice.

3.3. In the object type list, select ProgrammableXentaProgrammableXenta.

4.4. In the NameName box, type a name for the device. In this example, type AHU01.

Tip The name of the programmable Xenta device must be unique in

the network, even for programmable Xenta devices in differentfolders in the network.

44

5.5. In the DescriptionDescription box, type a description. In this example, typeProgrammable Xenta 300.

6.6. ClickNextNext.




45/136



7.7. In the FilesFiles box, enter the Menta application (MTA) file. In this example,enter AHU1.MTAAHU1.MTA.


Note

Xenta I/O modules are not added in this way. As they are defined in theMenta application program, they are automatically added to the I/O folderwhen the Xenta application is downloaded.



46/136


47/136

CommissioningCommissioning thethe LonWorksLonWorks6NetworkNetwork andand DevicesDevices

TopicsTopics

Discovering a Xenta Device

Commissioning a Xenta Device

Commissioning a LonWorks Device

Configuring a Configuration Property


48/136


49/136

6 Commissioning the LonWorks Network and Devices

Our Example

In this chapter, you bring all available devices online in your network. You firstdiscover the devices, which updates the Neuron ID in the Building Operationdatabase when the device service pin button is pressed. In this way, you do notneed to manually enter each ID. You then commission the Xenta 102-AX devices toenable the devices to communicate on the LonWorks network. The Xenta 300device is also commissioned. During this process, the Menta program isdownloaded 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 functionaloptions for the preprogrammed devices.



50/136


6.1 Discovering a Xenta Device


You discover Xenta 280/300/401 LonWorks devices to create or configure theprogrammable Xenta devices in the Building Operation server. The Xenta280/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 Wingnetwork.

To discover a Xenta device

1.1. In WorkStation, in the SystemSystem TreeTree pane, select the server that is connectedto the device you want to discover. In this example, select ...University...University XXES1/Servers/CPlantES1/Servers/CPlant ASAS.

2.2. Click the DeviceDevice DiscoveryDiscovery view.

3.3. In the SelectSelect devicedevice typetype box, select LonWorksLonWorks.

4.4. Select the DevicesDevices folder.

5.5. On the ActionsActions menu, clickActivateActivate listenlisten toto serviceservice pinpin.

6.6. Press the service pin on the physical device. In this example, press theservice pin on the Xenta 300, which is AHU 01.




51/136



7.7. In the DeviceDevice DiscoveryDiscovery view, ensure that the Xenta device is displayed in theDevicesDevices folder. This may take up to 5 seconds.

8.8. On the ActionsActions menu, clickDeactivateDeactivate listenlisten toto serviceservice pinpin. In thisexample, discover all four devices before you deactivate Listen to servicepin.

9.9. Drag the discovered service pin (device) to the SystemSystem TreeTree pane:

Drag to an existing device to associate it with the discovered physicaldevice.

Drag to the LonWorks network to create the device.

In this example, drag the ServiceService PinPin 11 device to ...University...University XXES1/Servers/CPlantES1/Servers/CPlant AS/LonWorksAS/LonWorks LocalLocal FT-10FT-10 Interface/EastInterface/EastWing/AHUs/AHUWing/AHUs/AHU 0101.

Tip

To verify the device Neuron ID, select the device in the SystemSystemTreeTree pane, and then select PropertiesProperties on the FileFile menu. TheNeuron ID can be found on the BasicBasic tab of the DeviceDevicePropertiesProperties.

51

In our example, repeat the procedure to discover the Neuron ID of the Xenta I/OModule and the VAV devices.

M1M1 (Xenta(Xenta 422A)422A)

LocationLocation: ...University X ES1/Servers/CPlant AS/LonWorks Local FT-10Interface/East Wing/AHUs/AHU 01/IO/M1

VAVVAV 0101 0101

LocationLocation: ...University X ES1/Servers/CPlant AS/LonWorks Local FT-10Interface/East Wing/VAVs/VAV 01 01



52/136



VAVVAV 0101 0202




53/136


6.2 Commissioning a Xenta Device

6.2 Commissioning a Xenta Device

You commission physical Xenta 280/300/401 LonWorks devices to make themoperational. The commission downloads the Menta application, gives the device asubnet node address, and sets the device status to online. After a commission, the

device can communicate with other devices on the LonWorks network and executeits 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.1. In WorkStation, in the SystemSystem TreeTree pane, select the device. In thisexample, select ...University...University XX ES1/Servers/CPlantES1/Servers/CPlant AS/LonWorksAS/LonWorks LocalLocalFT-10FT-10 Interface/EastInterface/East Wing/AHUs/AHUWing/AHUs/AHU 0101.

2.2. On the ActionsActions menu, clickCommissionCommission.

3.3. ClickCommissionCommission.

4.4. ClickCloseClose.

Tip

The Xenta I/O Modules communication automatically beginsupon commissioning the Xenta 280/300/401 LonWorks device,as long as the I/O module's Neuron ID was associated to the I/Omodule prior to commissioning the Xenta 280/300/401LonWorks device.



54/136


6.3 Commissioning a LonWorks Device


You commission physical LonWorks devices to give them their addresses, whichare defined in the LonWorks devices in the Building Operation server. Thecommission 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.1. In WorkStation, in the SystemSystem TreeTree pane, select the device. In thisexample, select ...University...University XX ES1/Servers/CPlantES1/Servers/CPlant AS/LonWorksAS/LonWorks LocalLocalFT-10FT-10 Interface/EastInterface/East Wing/VAVs/VAVWing/VAVs/VAV 0101 0101.

2.2. On the ActionsActions menu, clickCommissionCommission.

3.3. In the NeuronNeuron IDID box, make sure that the correct Neuron ID is entered.




55/136



4.4. Select which configuration to use:

ClickKeepKeep currentcurrent configurationconfiguration inin thethe devicedevice to leave theconfiguration in the device as is.

ClickDownloadDownload currentcurrent configurationconfiguration toto devicedevice to use the currentconfiguration from Building Operation.

ClickDownloadDownload defaultdefault configurationconfiguration toto devicedevice to use the defaultconfiguration from the device template.

ClickUploadUpload configurationconfiguration fromfrom devicedevice to use the current configurationin the device.

In this example, clickUploadUpload configurationconfiguration fromfrom devicedevice.

Important

Before downloading or uploading the device configuration,carefully consider the effects of overwriting the current deviceconfiguration in the LonWorks device or Building Operationserver.

55

5.5. ClickCommissionCommission.

6.6. ClickCloseClose.

The device is commissioned and activated.

In our example, repeat the procedure to commission VAV 01 02.

VAVVAV 0101 0202


ConfigurationConfiguration: Upload configuration from device

DeviceDevice applicationapplication filefile: No



56/136


6.4 Configuring a Configuration Property


You configure the Configuration properties of the LonWorks devices to ensure thatthe device performs as required by the project.

For more information, see WebHelp.In this example, you configure the nciSndHrtBt communication configurationproperty of VAV 01 01 (a Xenta 102-AX LonWorks device) to enable it to send datato other devices on the LonWorks network.

To configure a configuration property

1.1. In WorkStation, in the SystemSystem TreeTree pane, select the configuration property.In this example, select ...University...University XX ES1/Servers/CPlantES1/Servers/CPlant AS/LonWorksAS/LonWorksLocalLocal FT-10FT-10 Interface/EastInterface/East Wing/VAVs/VAVWing/VAVs/VAV 0101 01/Node01/Node ObjectObject[0]/nciSndHrtBt[0]/nciSndHrtBt.

2.2. In the ListList ViewView, right-click on the column heading bar and clickAdd/RemoveAdd/Removecolumnscolumns.

3.3. Select ValueValue.

4.4. ClickOKOK.

5.5. In the ValueValue column, click on the value.

6.6. Enter the value for the configuration property. In this example, enter 1010seconds.

7.7. On the FileFile menu, clickSaveSave.

Tip

When all configuration properties are defined for a LonWorksdevice, you can copy and paste the device in the System Treepane and then rename it as a means to add another device ofthe same type and configuration to maximize engineeringprocess efficiency.

56

For our example, repeat the procedure for the following configuration properties.

ConfigurationConfiguration PropertiesProperties inin VAVVAV 0101 0101 NodeNode ObjectObject

LocationLocation: ...University X ES1/Servers/CPlant AS/LonWorks Local FT-10Interface/East Wing/VAVs/VAV 01 01/Node Object [0]

Table: Configuration Properties in VAV 01 01 Node Object

ConfigurationConfiguration PropertyProperty MemberMember ValueValue

nciRcvHrtBt Elapsed time 30 seconds

nciMinSendTime Elapsed time 5 seconds

ConfigurationConfiguration PropertiesProperties inin VAVVAV 0101 0101 VAVControllerVAVController

LocationLocation: ...University X ES1/Servers/CPlant AS/LonWorks Local FT-10Interface/East Wing/VAVs/VAV 01 01/VAVController [8010]



57/136



Table: Configuration Properties in VAV 01 01 VAVController


nciMinDelTempSnd Temperature 0.3 C (0.5 F)

nciSetPnts Occupied cooling setpoint 23 C (74 F)

Occupied heating setpoint 21 C (70 F)

Standby cooling setpoint 24 C (76 F)

Standby heating setpoint 20 C (68 F)

Unoccupied cooling setpoint 27 C (80 F)

Unoccupied heating setpoint 18 C (65 F)

ConfigurationConfiguration PropertiesProperties inin VAVVAV 0101 0202 NodeNode ObjectObject

LocationLocation: ...University X ES1/Servers/CPlant AS/LonWorks Local FT-10Interface/East Wing/VAVs/VAV 01 02/Node Object [0]

Table: Configuration Properties in VAV 01 02 Node Object


nciSndHrtBt Elapsed time 10 seconds

nciRcvHrtBt Elapsed time 30 seconds

nciMinSendTime Elapsed time 5 seconds

ConfigurationConfiguration PropertiesProperties inin VAVVAV 0101 0202 VAVControllerVAVController

LocationLocation: ...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


nciMinDelTempSnd Temperature 0.3 C (0.5 F)

nciSetPnts Occupied cooling setpoint 23 C (74 F)

Occupied heating setpoint 21 C (70 F)

Standby cooling setpoint 24 C (76 F)

Standby heating setpoint 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.



58/136


59/136

CreatingCreating thethe LocalLocal NodeNode andand7NetworkNetwork VariablesVariables

TopicsTopics

Creating Network Variables Automatically

Creating an Output Network Variable

Configuring the Value and Propagation Delta for a NetworkVariable Member


60/136


61/136

7 Creating the Local Node and Network Variables

Our Example

In this chapter, you create network variables in the local node in the AutomationServer by mirroring network variables in the LonWorks field bus devices. You createand bind multiple network variables in one action to maximize engineeringefficiency. The Mirrored network variables command automatically creates the localnode, which is required to add network variables in a server that will be bound tonetwork variables in LonWorks field bus devices. The command also createsfunctional blocks, which are used to organize the network variables created in thelocal node.

You also create one network variable manually, nvoOccCmd. Finally, you configuresome properties of the network variables.



62/136


7.1 Creating Network Variables Automatically

7.1 Creating Network VariablesAutomatically

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 networkvariables 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 networkvariables in the AHU 01 device. The mirrored network variables are created in thelocal node, within a functional block named AHU 01. The local node and thefunctional block are automatically created.

To create network variables automatically

1.1. In WorkStation, in the SystemSystem TreeTree pane, in the LonWorks network, select thefunctional block that contains the network variables that you want to berepresented in the local node. In this example, select ...University...University XX

ES1/Servers/CPlantES1/Servers/CPlant AS/LonWorksAS/LonWorks LocalLocal FT-10FT-10 Interface/EastInterface/EastWing/AHUs/AHUWing/AHUs/AHU 01/SFPTcontroller01/SFPTcontroller [5][5].

2.2. In the ListList ViewView, select the network variables that you want to be representedin the local node. In this example, select nviAHUOccCmdnviAHUOccCmd, nviDatSPnviDatSP,nviStPrSPnviStPrSP, nviVentReqnviVentReq, nvoFanStatusnvoFanStatus, and nvoVlvPosnnvoVlvPosn.

3.3. On the FileFile menu, point to NewNew and then clickMirroredMirrored networknetwork variablesvariables.

Mirrored network variables of the network variables that you selected, areautomatically created and bound in the local node, within functional blocks that arealso automatically created and named according to the LonWorks devices fromwhere 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.

62

In this example, repeat the procedure to create bound counterparts in the localnode of the following network variables:

VAVVAV 0101 0101 NetworkNetwork VariablesVariables



NameName:

nvoMotorPositn

nvoOccpncyStatus

nvoSpaceTemp

nvoTerminalLoad

VAVVAV 0101 0202 NetworkNetwork VariablesVariables





63/136


7.1 Creating Network Variables Automatically

NameName:

nvoMotorPositn

nvoOccpncyStatus

nvoSpaceTemp

nvoTerminalLoad

The mirrored network variables are created in the local node, within functionalblocks that are automatically created and named VAV 01 01 and VAV 01 02respectively.



64/136


7.2 Creating an Output Network Variable


You create output network variables in functional blocks in a local node for bindingLonWorks variables between the Automation Server and the Xenta 280/300/401LonWorks devices or other LonWorks devices.

For more information, see WebHelp.In this example, you create an output network variable called nvoOccCmd in theAHU 01 functional block that will be bound to the nviOccCmd SNVTs in VAV 01 01and VAV 01 02 (Xenta 102-AX devices).

To create an output network variable

1.1. In WorkStation, in the SystemSystem TreeTree pane, select the functional block whereyou want to create the variable. In this example, select ...University...University XXES1/Servers/CPlantES1/Servers/CPlant AS/LonWorksAS/LonWorks LocalLocal FT-10FT-10 Interface/EastInterface/EastWing/LocalWing/Local Node/AHUNode/AHU 0101.

2.2. On the FileFile menu, point to NewNew and then clickNetworkNetwork VariableVariable.

3.3. In the ResourceResource filesfiles kitkit box, select the DRF that contains the types for thevariable. In this example, select standardstandard.

4.4. In the TypeType box, select the type of variable. In this example, selectSNVT_occupancySNVT_occupancy.

5.5. In the DirectionDirection box, select OutputOutput.

6.6. In the NameName box, type a name for the variable. In this example, typenvoOccCmd.

7.7. ClickNextNext.




65/136



8.8. In the SendingSending enabledenabled box, select YesYes to send the variables at periodicintervals.

9.9. In the SendSend raterate box, enter the number of seconds between the sends. Inthis example, enter 6060.

10.10. In the InitialInitial ValueValue box, enter the initial value for the variable. In thisexample, enter OC_OCCUPIEDOC_OCCUPIED.

11.11. In the DeltaDelta box, select the delta to be used before sending the value. Inthis example, select AtAt anyany changechange.




66/136


7.3 Configuring the Value and Propagation Delta for a Network Variable Member

7.3 Configuring the Value and PropagationDelta 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 networkvariable member named Occupancy, which is a member of the network variablenamed nvoAHUOccCmd in the local node.

To configure the value and propagation delta for a networkvariable member

1.1. In WorkStation, in the SystemSystem TreeTree pane, expand the network variable andthen select the variable member. In this example, expand ...University...University XXES1/Servers/CPlantES1/Servers/CPlant AS/LonWorksAS/LonWorks LocalLocal FT-10FT-10 Interface/EastInterface/EastWing/LocalWing/Local Node/AHUNode/AHU 01/nvoAHUOccCmd01/nvoAHUOccCmd SFPTcontrollerSFPTcontroller [5][5] and select

OccupancyOccupancy.


3.3. In the PropagationPropagation deltadelta forfor valuevalue changeschanges box, select AtAt anyany changechange orOffOff, or type a delta value. In this example, select AtAt anyany changechange.

4.4. In the ValueValue box, enter the value of the variable. In this example, enterOC_OCCUPIEDOC_OCCUPIED.

5.5. ClickOKOK.

In this example, repeat the procedure to configure the value and the propagation

delta for the network variable members Temperature, Pressure (gauge), andOccupancy, which are members of the network variables nvoDatSP, nvoStPrSP,and nvoVentReq respectively in the local node. Use the following settings:



67/136


7.3 Configuring the Value and Propagation Delta for a Network Variable Member

Table: nvoDatSP Temperature

ComponentComponent SettingSetting

LocationLocation ...University X ES1/Servers/CPlantAS/LonWorks Local FT-10 Interface/EastWing/Local Node/AHU 01/nvoDatSP

SFPTcontroller [5]/Temperature

PropagationPropagation deltadelta forfor valuevalue changeschanges 0.5

ValueValue 13 C (55 F)

Table: nvoStPrSP Pressure (gauge)


LocationLocation ...University X ES1/Servers/CPlantAS/LonWorks Local FT-10 Interface/East

Wing/Local Node/AHU 01/nvoStPrSPSFPTcontroller [5]/Pressure (gauge)

PropagationPropagation deltadelta forfor valuevalue changeschanges 0.5

ValueValue 1.0 Pa (water pressure)

Table: nvoVentReq Occupancy


LocationLocation ...University X ES1/Servers/CPlant

AS/LonWorks Local FT-10 Interface/EastWing/Local Node/AHU 01/nvoVentReqSFPTcontroller [5]/Occupancy

PropagationPropagation deltadelta forfor valuevalue changeschanges At any change

ValueValue OC_OCCUPIED



68/136


69/136

CreatingCreating Programs,Programs, Alarms,Alarms,8andand SchedulesSchedules inin thetheAutomationAutomation ServerServer

TopicsTopics

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


70/136


71/136

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 EastWing.

In the Automation Server, you create four function block programs:DischAirTempSP, Occupancy, StaticPressSP, and VAVAlarms. The actual programcode has already been completed, so you import the program code into theindividual function block programs.

You create change of state alarms that are triggered when the Zone01 and Zone02temperatures, which are sent from the VAVs to the Automation Server, exceed orfall below the limits established in the Automation Server programming.

Finally, you create a digital schedule named AHUSchedule and configure it as ashadow schedule of the Cooling Plant Enable Schedule. The Occupancy programwill use the value of the AHUSchedule to control the Air Handling Unit.



72/136


8.1 Creating a Function Block Program


You create a Function Block program to import existing program code or toprogram 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 theAutomation Server, which will be used in conjunction with the field bus devices tocontrol 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 Scriptprograms for the same control logic in the Automation Server. For example, you canuse a Function Block program to control Secondary Chilled Water Pump 1 and aScript program to control Secondary Chilled Water Pump 2 in the same AutomationServer.

When you decide to use Function Block programming or Script programming,consider the engineer's familiarity with programming tools and whether theprograms require standard programming features or customized details.

To create a function block program

1.1. In WorkStation, in the SystemSystem TreeTree pane, select the server or folder whereyou want to create the function block program. In this example,select ...University...University XX ES1/Servers/CPlantES1/Servers/CPlant AS/AHUAS/AHU 01/Programs01/Programs.

2.2. On the FileFile menu, point to NewNew and then clickProgramProgram.

3.3. In the object type list, select FunctionFunction BlockBlock ProgramProgram.

4.4. In the NameName box, type a name for the function block program. In thisexample, type DischAirTempSP.




73/136



In this example, repeat the procedure to create the following function blockprograms:

LocationLocation: ...University X ES1/Servers/CPlant AS/AHU 01/Programs

NameName:

Occupancy

StaticPressSP

VAVAlarms



74/136


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 Xenta280/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 blockprogram for use in the Automation Server.

To import function block program code

1.1. In WorkStation, in the SystemSystem TreeTree pane, select the function block programyou want to import program code to. In this example, select ...University...University XXES1/Servers/CPlantES1/Servers/CPlant AS/AHUAS/AHU 01/Programs/DischAirTempSP01/Programs/DischAirTempSP.

2.2. On the ActionsActions menu, clickEditEdit.

3.3. In Function Block Editor, on the FileFile menu, clickImportImport.

4.4. Select the file you want to import. In this example, select DatSP.AUTDatSP.AUT.

5.5. ClickOpenOpen.




75/136




Tip

When a Menta file is imported, TSCH blocks and ALARM blocksare removed, AI/DI blocks are converted to RI/BI blocks, and

AO/DO blocks are converted to RO/BO blocks. As a result ofthese conversions, you may need to make adjustments to theimported Menta code.

75

In this example, repeat the procedure to import .aut files to the following FunctionBlock programs:

OccupancyOccupancy

ObjectObject locationlocation: ...University X ES1/Servers/CPlant AS/AHU01/Programs/Occupancy

FileFile namename: OccupancyPgm.AUT

StaticPressSPStaticPressSP

ObjectObject locationlocation: ...University X ES1/Servers/CPlant AS/AHU01/Programs/StaticPressSP

FileFile namename: StPrSP.AUT

VAVAlarmsVAVAlarms

ObjectObject locationlocation: ...University X ES1/Servers/CPlant AS/AHU01/Programs/VAVAlarms

FileFile namename: VAVAlarms.AUT



76/136


8.3 Creating a Change of State Alarm


You create a change of state alarm to trigger an alarm when a variable, such as aswitch, is either true or false.

For more information, see WebHelp.In this example, you create a change of state alarm called VAV 01 TempAlarm tomonitor VAV_01_TempAlarm in the VAVAlarms Function Block program.

To create a change of state alarm

1.1. In WorkStation, in the SystemSystem TreeTree pane, select the folder or server whereyou want to create the alarm. In this example, select ...University...University XXES1/Servers/CPlantES1/Servers/CPlant AS/AHUAS/AHU 01/Alarms01/Alarms.

2.2. On the FileFile menu, point to NewNew and then clickAlarmAlarm.

3.3. In the object type list, select ChangeChange ofof StateState AlarmAlarm.

4.4. In the NameName box, type a name for the alarm. In this example, type VAV 01TempAlarm.

5.5. In the DescriptionDescription box, type a description for the alarm. In this example,type Monitors the VAV 01/Zone 01 Temperature.

6.6. ClickNextNext.




77/136



7.7. Select the state of the monitored variable that triggers the alarm:

ClickTrueTrue to trigger the alarm when the monitored variable is equal toTrueTrue.

ClickFalseFalse to trigger the alarm when the monitored variable is equal toFalseFalse.

In this example, clickTrueTrue.

8.8. In the MonitoredMonitored variablevariable box, enter the variable that the alarm monitors.In this example, enter ...University...University XX ES1/Servers/CPlantES1/Servers/CPlant AS/AHUAS/AHU01/Programs/VAVAlarms/VAV_01_TempAlarm01/Programs/VAVAlarms/VAV_01_TempAlarm.

9.9. Under TimeTime delaydelay andand shuntshunt variablevariable, in the AlarmAlarm delaydelay box, enter the timedelay. In this example, enter 55.

10.10. In the ResetReset delaydelay box, enter the time delay. In this example, enter 55.

11.11. ClickNextNext.




78/136



12.12. In the AlarmAlarm messagemessage box, type the message to display when the monitoredvariable exceeds the alarm limit. In this example, type The Zone 01Temperature is too high.

13.13. In the ResetReset messagemessage box, type the message to display when the alarm isreset. In this example, type The Zone 01 Temperature has returned tonormal.

14.14. In the AlarmAlarm prioritypriority box, enter the priority for the alarm state. In thisexample, enter 22.

15.15. In the ResetReset prioritypriority box, enter the priority for the reset state. In thisexample, enter 1010.

16.16. Under CategoryCategory andand AlertsAlerts, select the FlashingFlashing alertalert check box to make thealarm flash in the Alarms pane and Alarm Views when it is triggered. In thisexample, select FlashingFlashing alertalert.




79/136



17.17. Select the AudibleAudible alertalert check box to make the alarm sound when it istriggered. In this example, select AudibleAudible alertalert.





80/136



19.19. Select the type of acknowledgement to use:

ClickNoNo when the alarm does not need to be acknowledged.

ClickSingleSingle when the alarm needs to be acknowledged in the alarmstate.

ClickExtendedExtended when the alarm needs to be acknowledged in the alarmstate and the reset state.

In this example, clickSingleSingle.



In our example, repeat the procedure to create a change of state alarm called VAV02 TempAlarm to monitor VAV_02_TempAlarm in the VAVAlarms Function Blockprogram.

Table: VAV 02 TempAlarm


LocationLocation ...University X ES1/Servers/CPlant AS/AHU01/Alarms

NameName VAV 02 TempAlarm

DescriptionDescription Monitors the VAV 02/Zone 02 Temperature

TriggerTrigger valuevalue True

MonitoredMonitored variablevariable ...University X ES1/Servers/CPlant AS/AHU01/Programs/VAVAlarms/VAV_02_TempAlarm

AlarmAlarm delaydelay (s)(s) 5



81/136



Continued


ResetReset delaydelay (s)(s) 5

ShuntShunt variablevariable No

AlarmAlarm messagemessage The Zone 02 Temperature is too high

ResetReset messagemessage The Zone 02 Temperature has returned tonormal

AlarmAlarm prioritypriority 2

ResetReset prioritypriority 10

CategoryCategory No

FlashingFlashing alertalert Yes

AudibleAudible alertalert Yes

AcknowledgementAcknowledgement typetype Single

AttachmentAttachment No



82/136


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 shadowschedule to the Cooling Plant Enable Schedule.

To create a digital schedule

1.1. In WorkStation, in the SystemSystem TreeTree pane, select the server or the folder whereyou want to create the schedule. In this example, select ...University...University XXES1/Servers/CPlantES1/Servers/CPlant AS/AHUAS/AHU 01/Schedules01/Schedules.

2.2. On the FileFile menu, point to NewNew and then clickScheduleSchedule.

3.3. In the object type list, select DigitalDigital ScheduleSchedule.

4.4. In the NameName box, type a name for the schedule. In this example, typeAHUSchedule.


Now you can add events to the digital schedule and bind it to a digital value.



83/136


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 thatalready contains all weekly events and exception events.

For more information, see WebHelp.In this example, you configure the digital schedule named AHUSchedule as ashadow schedule of the Cooling Plant Enable Schedule.

To configure a schedule as a shadow

1.1. In WorkStation, in the SystemSystem TreeTree pane, select the schedule you want toconfigure as a shadow. In this example, select ...University...University XXES1/Servers/CPlantES1/Servers/CPlant AS/AHUAS/AHU 01/Schedules/AHUSchedule01/Schedules/AHUSchedule.


3.3. In the LeadLead objectobject box, enter the schedule that you want to synchronize theshadow schedule with. In this example, enter ...University...University XX

ES1/Servers/CPlantES1/Servers/CPlant AS/CoolingAS/Cooling Application/Schedules/CoolingApplication/Schedules/Cooling PlantPlantEnableEnable ScheduleSchedule.

4.4. ClickOKOK.



84/136


85/136

CreatingCreating BindingsBindings forfor9CommunicationCommunication

TopicsTopics

Creating a LonWorks Binding

Importing a Solution

Binding Values Using a Binding Template


86/136


87/136

9 Creating Bindings for Communication

Our Example

In this chapter, you create bindings, which are used to designate what is to becommunicated and how the designated communication is to occur. Bindings arecreated between LonWorks variables, the Automation Server, and the Xenta280/300/401 LonWorks devices or other LonWorks devices.

You create a LonWorks binding to communicate with a LonWorks device becauseit enables event-driven communication, which is more efficient than communicationusing the polling method.

You create a Building Operation binding to bind points in a Building Operationserver program, graphics, alarm, or trend log to LonWorks network variables in thelocal node. In our example, you create bindings to establish data flow in and out ofAutomation Server programs. For engineering efficiency, you import two custombinding templates that you use to create the necessary bindings.



88/136


9.1 Creating a LonWorks Binding


You create a LonWorks binding between the Automation Server local node and aLonWorks device or between two LonWorks devices. You create the bindingbetween LonWorks Network Variables or Configuration Parameters (NV based).

You use a LonWorks binding to communicate with a LonWorks device because itenables event-driven communication, which is more efficient than communicationusing the polling method.

For more information, see WebHelp.In this example, you create the LonWorks binding between the nvoOccCmd outputvariable in the AHU 01 Functional Block in the CPlant AS Local Node and thenviOccCmd input variable in the VAV 01 01 device.

To create a LonWorks binding

1.1. In WorkStation, in the SystemSystem TreeTree pane, select the local node or device forwhich you want to create a LonWorks binding. In this example,select ...University...University XX ES1/Servers/CPlantES1/Servers/CPlant AS/LonWorksAS/LonWorks LocalLocal FT-10FT-10

Interface/EastInterface/East Wing/LocalWing/Local NodeNode.

2.2. On the ActionsActions menu, clickEditEdit bindingsbindings.

3.3. In the binding point list, select the variable you want to bind to. In thisexample, select AHUAHU 01/Outputs/nvoOccCmd01/Outputs/nvoOccCmd.

4.4. In the binding point browser, select the device to bind from. In this example,select ...University...University XX ES1/Servers/CPlantES1/Servers/CPlant AS/LonWorksAS/LonWorks LocalLocal FT-10FT-10Interface/EastInterface/East Wing/VAVs/VAVWing/VAVs/VAV 0101 0101.

5.5. Expand the selected device to display the variables that are available to bebound.




89/136



6.6. Select the variable to be bound and drag it to the binding box for the variablein the binding point list. In this example, drag VAVControllerVAVController[8010]/nviOccCmd[8010]/nviOccCmd to the binding box for nvoOccCmdnvoOccCmd.

Important

To bind more than one variable to a binding point, drag thevariable to the name of the binding point. Each binding adds arow to the binding point.

89


Tip

You cannot use a custom binding template when you createLonWorks bindings. Custom binding templates can be usedwhen you create Building Operation bindings.

For our example, repeat the procedure to complete the following LonWorksbinding. Note that the binding profile is automatically updated toUnacknowledgedUnacknowledged RepeatedRepeated ProfileProfile, which is the correct binding profile to use forthis group binding.

LocalLocal NodeNode BindingsBindings

PathPath toto LocalLocal Node:Node: ...University X ES1/Servers/CPlant AS/LonWorks Local FT-10 Interface/East Wing/Local Node

Table: AHU 01/Outputs

BindingBinding PointPoint BindingBinding

nvoOccCmd ~/LonWorks Local FT-10 Interface/East

Wing/VAVs/VAV 01 02/VAVController[8010]/nviOccCmd



90/136


9.2 Importing a Solution


You import a solution that was created or modified on another Building Operationserver. You can also use the standard copy and paste method to copy solutions toother 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 beused to create bindings for data flow between programs in the Automation Serverand the Xenta LonWorks devices.

To import a solution

1.1. In WorkStation, in the SystemSystem TreeTree pane or ListList ViewView, select a location whereyou want to import a solution. In this example, select ...University...University XXES1/Servers/CPlantES1/Servers/CPlant AS/System/BindingAS/System/Binding TemplatesTemplates.

2.2. On the FileFile menu, clickImportImport.

3.3. In the OpenOpen dialog box, select the file and clickOpenOpen. In this example,select DataFromLocalNodeTemplate.xmlDataFromLocalNodeTemplate.xml.

4.4. In the ImportImport dialog box, clickImportImport.



91/136



For this example, repeat the procedure to import a custom binding template to beused to create bindings for data flow between Automation Server programs andschedules.

LocationLocation: ...University X ES1/Servers/CPlant AS/System/Binding Templates

FileFile namename: SchedAndAlarmsTemplate.xml



92/136


9.3 Binding Values Using a Binding Template

9.3 Binding Values Using a BindingTemplate

You use binding templates to reduce engineer

creating and configuring a lonworks network with xenta lonworks devices

Documents