Creating and Configuring a LonWorks Network with MNL...

StruxureWareStruxureWare BuildingBuilding OperationOperationCreatingCreating andand ConfiguringConfiguring aa LonWorksLonWorks NetworkNetwork withwithMNLMNL LonWorksLonWorks DevicesDevicesTutorialTutorial GuideGuide04-14032-01-enJuly 2013

StruxureWare Building OperationCreating and Configuring a LonWorks Network withMNL LonWorks DevicesTutorial Guide04-14032-01-enJuly 2013

Copyright © 2013 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 areprotected, within the meaning of the French intellectual property code (Code de la propriété intellectuelle français, 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.

Contents

IntroductionIntroduction1 About This Guide ........................................................... 91.1 Purpose of This Guide ................................................................. 111.2 How This Guide is Organized ...................................................... 121.3 Typographical Conventions ......................................................... 13

2 Additional Information .................................................. 152.1 Where to Find Additional Information ........................................... 172.2 Regulatory Notices ...................................................................... 18

TutorialTutorial3 Our Case Study ........................................................... 213.1 University X ................................................................................. 233.2 Requirements and Specifications ................................................ 263.2.1 Devices Used for This Case Study ............................................. 263.2.2 Software Used in This Tutorial ................................................... 263.2.3 Specifications ........................................................................... 263.3 Focus of This Tutorial .................................................................. 273.3.1 Pre-existing Database Folder and Programs .............................. 273.3.2 Pre-existing Database Objects .................................................. 28

4 Creating the LonWorks Network .................................. 294.1 Creating a LonWorks Interface .................................................... 324.2 Creating a LonWorks Network .................................................... 334.3 Creating a Folder ........................................................................ 34

5 Adding Devices to the LonWorks Network ................... 375.1 Creating a LonWorks Device ....................................................... 405.2 Importing a Single MNL LonWorks Application Type .................... 425.3 Assigning an MNL LonWorks Application ................................... 45

6 Commissioning the LonWorks Devices ........................ 476.1 Discovering a LonWorks Device .................................................. 506.2 Commissioning a LonWorks Device ............................................ 526.3 Downloading an MNL LonWorks Application Type ...................... 54

04-14032-01-en, July 2013 Creating and Configuring a LonWorks Network with MNL LonWorks Devices5

7 Creating the Local Node and Network Variables ........... 557.1 Creating Network Variables Automatically ................................... 587.2 Creating an Output Network Variable .......................................... 607.3 Configuring the Value for a Network Variable Member ................. 62

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

8.1 Creating a Function Block Program ............................................. 688.2 Importing Function Block Program Code ..................................... 708.3 Creating a Change of State Alarm .............................................. 728.4 Creating a Digital Schedule ......................................................... 788.5 Configuring a Schedule as a Shadow ......................................... 79

9 Creating Bindings for Communication .......................... 819.1 Creating a LonWorks Binding ...................................................... 849.2 Importing a Solution .................................................................... 869.3 Binding Values Using a Binding Template .................................... 889.4 Configuring the Value Transfer Interval ......................................... 939.5 Summary .................................................................................... 95

Creating and Configuring a LonWorks Network with MNL LonWorks Devices 04-14032-01-en, July 20136

Introduction

The Introduction part contains information on the purposeof this guide, how this guide is organized, where to findmore information, and information on regulatory notices.

AboutAbout ThisThis GuideGuide1

TopicsTopicsPurpose of This GuideHow This Guide is OrganizedTypographical Conventions

1 About This Guide1.1 Purpose of This Guide

1.1 Purpose of This GuideThis tutorial provides step-by-step instructions for creating a LonWorks networkconfigured with an Automation Server and MNL LonWorks devices.

This tutorial focuses on the following Building Operation Engineering Certificationobjectives:

• Create a new Building Operation system using an Automation Server and MNLLonWorks devices

• Integrate MNL LonWorks 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

• Use standards and templates for efficient engineering


1 About This Guide1.2 How This Guide is Organized

1.2 How This Guide is OrganizedThis Building Operation Guide is divided into the following parts:

IntroductionThe Introduction part contains information on the purpose of this guide, how thisguide is organized, where to find more information, and information on regulatorynotices.

TutorialThe 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 called 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 thistutorial, 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.


1 About This Guide1.3 Typographical Conventions

1.3 Typographical ConventionsBuilding Operation Guides use the following specially marked texts:

TipHelps you understand the benefits and capabilities of the product.

13

NoteProvides you with supplementary information.

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

CautionAlerts you to a condition that can cause loss of data.

WarningAlerts 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, forexample "On the Filemenu, select New."

Example texts:

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

04-14032-01-en, July 2013 Creating and Configuring a LonWorks Network with MNL LonWorks Devices

AdditionalAdditional InformationInformation2

TopicsTopicsWhere to Find Additional InformationRegulatory Notices

2 Additional Information2.1 Where to Find Additional Information

2.1 Where to Find Additional InformationAll 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


2 Additional Information2.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 CanadaICES-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 CommissionFCC 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.


Tutorial

The Tutorial part contains a step-by-step description ofhow to carry out different tasks. If you want moreinformation, see WebHelp or the corresponding BuildingOperation Guide.The Tutorial part includes a case study for a fictionalcustomer called University X. You can decide if you want tofollow the example or use the described procedures asreference information. The case study in this tutorial is anexample of a typical way of configuring Building Operationfor a customer. When reading through this tutorial, youmight not have access to the devices, programs, and otherfiles that are needed for the fictional customer University X.However, the purpose of having a case study is to see theprocedures put in context, so you see how the procedurescould be used when configuring Building Operation, devices,or programs for your customer.

OurOur CaseCase StudyStudy3

When new knowledge is to be acquired, it is oftenadvantageous to work with a realistic example. Forthis purpose we use a case study, which is basicallythe same in all Building Operation Tutorial Guides.

TopicsTopicsUniversity XRequirements and SpecificationsFocus of This Tutorial

3 Our Case Study3.1 University X

3.1 University XWe 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. Thecase 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 singleconstant 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.



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.



Figure: Heating Plant diagram


3 Our Case Study3.2 Requirements and Specifications

3.2 Requirements and SpecificationsTo 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 StudyThe following devices are used for this case study:

• Power Supply, PS-24V

• Automation Server, AS-L

• Fan Coil Controller, MNL-20RS4

• VAV Controller, MNL-V2RV3-2

Important• Make sure the MNL LonWorks devices are in a configured state before you

start this tutorial. For more information, see theMNL LonWorks Devices topicon WebHelp.

26

3.2.2 Software Used in This TutorialThe 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 datasheets for Enterprise Server,WorkStation, PS-24V Power Supply, Automation Server, MicroNet 100, 150, and200 Series Controllers, and MicroNet VAV Series Controllers MNL-Vx.


3 Our Case Study3.3 Focus of This Tutorial

3.3 Focus of This TutorialThe university requires the new East Wing of the School of Business to becontrolled using MNL 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 MNLLonWorks devices required. This includes organizing the LonWorks network folderstructure, creating the MNL LonWorks devices, establishing communicationbetween the network devices, as well as preparing the Automation Server tomanage the alarms for the LonWorks network.

3.3.1 Pre-existing Database Folder and ProgramsFor 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 HeatingPlant.

CPlant AS has the following folder structure:


3 Our Case Study3.3 Focus of This Tutorial

Figure: CPlant AS and its folder structure

3.3.2 Pre-existing Database ObjectsFor University X, the following objects are available in the Building Operationdatabase prior to the creation and configuration of LonWorks network with MNLLonWorks devices:

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


CreatingCreating thethe LonWorksLonWorks4NetworkNetwork

TopicsTopicsCreating a LonWorks InterfaceCreating a LonWorks NetworkCreating a Folder

4 Creating the LonWorks Network

Our ExampleIn this chapter, you prepare the Automation Server to function as the LonWorksnetwork interface and create the LonWorks network so that MNL LonWorksdevices can be added for controlling the East Wing of the School of Business. Youalso create a folder structure in the System Tree pane to ensure that the network isorganized to maximize engineering and operating efficiency.


4 Creating the LonWorks Network4.1 Creating a LonWorks Interface

4.1 Creating a LonWorks InterfaceYou create a LonWorks interface under the Building Operation server to connect toa LonWorks network.

For more information, see the LonWorks Overview topic on WebHelp.

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

To create a LonWorks interface1.1. In WorkStation, in the System Tree pane, select the server where you want

to create the interface. In this example, select ...University XES1/Servers/CPlant AS.

2.2. On the Filemenu, point to New and then click Interface.

3.3. In the object type list, select LonWorks Local FT-10 Interface orLonWorks Interface. In this example, select LonWorks Local FT-10Interface.

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

5.5. Click Create.

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


4 Creating the LonWorks Network4.2 Creating a LonWorks Network

4.2 Creating a LonWorks NetworkYou create a LonWorks network under the LonWorks interface to connect todevices that are using the LonWorks protocol.

For more information, see the LonWorks Overview topic on 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 MNL LonWorks devices.

To create a LonWorks network1.1. In WorkStation, in the System Tree pane, select the LonWorks interface

where you want to create the network. In this example, select ...UniversityX ES1/Servers/CPlant AS/LonWorks Local FT-10 Interface.

2.2. On the Filemenu, point to New and then click LonWorks Network.

3.3. In the Name box, type a name for the network. In this example, type “EastWing.”

4.4. In the Description box, type a description. In this example, type “Schoolof Business.”

5.5. Click Create.


4 Creating the LonWorks Network4.3 Creating a Folder

4.3 Creating a FolderYou create folders to organize your Building Operation database.

In this example, you create the LonWorks network folder called AHUs in which theMNL-20RS4 LonWorks device is created. Each folder in the LonWorks networkcreates a new subnet.

To create a folder1.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-10Interface/East Wing.

2.2. On the Filemenu, point to New and then click Folder.

3.3. In the Name box, type a name for the folder. In this example, type “AHUs.”

4.4. In the Description box, type a description for the folder. In this example,type “MNL AHU devices.”

5.5. Click Create.

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

Table: LonWorks Network Folders

Name Location Information

VAVs ...University X Two MNL-V2RV3 LonWorksES1/Servers/CPlant devices (VAV controllers) willAS/LonWorks Local FT-10 be created.Interface/East Wing


4 Creating the LonWorks Network4.3 Creating a Folder

Table: Automation Server Folders

Name Location Information

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


AddingAdding DevicesDevices toto thethe5LonWorksLonWorks NetworkNetwork

TopicsTopicsCreating a LonWorks DeviceImporting a Single MNL LonWorks Application TypeAssigning an MNL LonWorks Application

5 Adding Devices to the LonWorks Network

Our ExampleIn this chapter, you add MNL LonWorks devices in the System Tree pane beneaththe LonWorks network.

The MNL-V2RV3 devices are used for controlling the VAV dampers. The MNL-20RS4 device is used for controlling the Air Handling Unit in the East Wing. TheMNL LonWorks applications have already been written, so you will import theseapplications to the database and assign them to the AHU and VAV devices.


5 Adding Devices to the LonWorks Network5.1 Creating a LonWorks Device

5.1 Creating a LonWorks DeviceYou create LonWorks devices under the LonWorks network to connect to physicalLonWorks devices.

For more information, see theWorkflows for Creating and Configuring LonWorksDevices topic on WebHelp.

In this example, you create an MNL-V2RV3 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 device1.1. In WorkStation, in the System Tree pane, select the LonWorks network or

LonWorks network folder where you want to create the device. In thisexample, select ...University X ES1/Servers/CPlant AS/LonWorksLocal FT-10 Interface/East Wing/VAVs.

2.2. On the Filemenu, point to New and then click Device.

3.3. In the object type list, select a device template. In this example, selectMNLV2RV3_VAV.

4.4. In the Name box, type a name for the device. In this example, type “VAV 0101.”

Tip• The name of the LonWorks device must be unique in the

network, even for LonWorks devices in different folders in thenetwork.

40

Continued on next page


5 Adding Devices to the LonWorks Network5.1 Creating a LonWorks Device

5.5. In the Description box, type a description. In this example, type “MNL-V2RV3 - fan powered terminal.”

6.6. Click Next.

7.7. Click Create.

In our example, repeat the procedure to create the other LonWorks devices. Usethe following settings:

VAV 01 02

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

• Device template: MNLV2RV3_VAV

• Name: VAV 01 02

• Description: MNL-V2RV3 - fan powered terminal

• Neuron ID: Default value

• Commission: No

AHU 01

• Location: ...University X ES1/Servers/CPlant AS/LonWorks Local FT-10Interface/East Wing/AHUs

• Device template: MNL20RS4_RoofTop2

• Name: AHU 01

• Description: MNL-20RS4 - fan coil controller

• Neuron ID: Default value

• Commission: No


5 Adding Devices to the LonWorks Network5.2 Importing a Single MNL LonWorks Application Type

5.2 Importing a Single MNL LonWorksApplication TypeYou use WorkPlace Tech Editor to import an MNL LonWorks application type intothe Building Operation database so the new application type is available to assignto MNL LonWorks devices.

ImportantApplications must be from WorkPlace Tech version 4.0 or later, in order to beimported into the Building Operation database.

42

For more information, see theWorkPlace Tech Editor topic on WebHelp.

In this example, you use WorkPlace Tech Editor to import the pre-existingapplication file named AHU.vsd and save it as a new application type named AHU.The application is designed for the AHU 01 (MNL-20RS4) device.

To import a single MNL LonWorks application type1.1. In WorkStation, on the Toolsmenu, click Control Panel.

2.2. In the Server box, select a server. In this example, select CPlant AS.

3.3. ClickWorkPlace Tech Editor.

For more information, see the Intercompatibility Notes topic on WebHelp.




4.4. Click the Add an Application button .

5.5. In the MNL device list box, select the MNL device model. In this example,point toMN 200 and then clickMNL-20RS4.

6.6. In WorkPlace Tech Editor, on the Applicationmenu, click Import Wizard.

7.7. On the Input File Selection page, read the information and then click Next.

8.8. In the Select WorkPlace Tech File to Import dialog box, select theapplication (.vsd) file to be imported. In this example, select AHU.vsd.

9.9. Click Open.

10.10. On the Filemenu, click Save.

11.11. In the Enter a name for this application box, type a name for theapplication. In this example, type “AHU.”

12.12. In the Enter a category for this application box, type a category for theapplication. In this example, type “MNL-20RS4.”

13.13. Click OK.

You can view the new application type in the WorkPlace Tech Applications view inWorkStation. The application type is now available to assign to MNL LonWorksdevices.



In our example, repeat the procedure to import an application type for the VAV(MNL-V2RV3) devices. Use the following settings:

• MNL device model: MN VAV – MNL-V2RV3

• File name: VAV.vsd

• Name: VAV

• Category: MNL-V2RV3


5 Adding Devices to the LonWorks Network5.3 Assigning an MNL LonWorks Application

5.3 Assigning an MNL LonWorks ApplicationYou assign an application to an MNL LonWorks device to specify which applicationtype the device will use.

For more information, see theMNL LonWorks Applications topic on WebHelp.

In this example, you assign the application named AHU to the AHU 01 (MNL-20RS4) device.

When you assign an application to a device, an Application object is createdbeneath the device in the WorkStation System Tree pane. You can select theApplication object to view the available variables for that device application in theList View in WorkStation.

To assign an MNL LonWorks application1.1. In WorkStation, in the System Tree pane, select an MNL LonWorks device.

In this example, select ...University X ES1/Servers/CPlantAS/LonWorks Local FT-10 Interface/East Wing/AHUs /AHU 01.

2.2. On the Actionsmenu, point toMNL and then click Assign application.

3.3. In the list of applications, select an application. In this example, select AHU.

4.4. Click Assign.

For this example, repeat the procedure for the VAV (MNL-V2RV3) devices.

VAV 01 01

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

• Application: VAV

VAV 01 02

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

• Application: VAV


CommissioningCommissioning thethe LonWorksLonWorks6DevicesDevices

TopicsTopicsDiscovering a LonWorks DeviceCommissioning a LonWorks DeviceDownloading an MNL LonWorks Application Type

6 Commissioning the LonWorks Devices

Our ExampleIn this chapter, you bring all available MNL LonWorks devices online in yournetwork. You first discover the devices, which updates the Neuron ID in the BuildingOperation database when the device service pin button is pressed. In this way, youdo not need to manually enter each ID. You then commission the devices to enablethe devices to communicate on the LonWorks network. You also download theMNL LonWorks applications to those devices that have been commissioned.


6 Commissioning the LonWorks Devices6.1 Discovering a LonWorks Device

6.1 Discovering a LonWorks DeviceYou discover LonWorks devices to create or configure the LonWorks devices in theBuilding Operation server. The LonWorks devices must be physically connected tothe Building Operation server field bus.

For more information, see the LonWorks Device Workflow topic on WebHelp.

In this example, you discover the MNL-20RS4 device (AHU 01) in the East Wingnetwork.

To discover a LonWorks device1.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 XES1/Servers/CPlant AS.

2.2. Click the Device Discovery view.

3.3. In the Select device type box, select LonWorks.

4.4. Select the Devices folder.

5.5. On the Actionsmenu, click Activate listen to service pin.

6.6. Press the service pin on the physical device. In this example, press theservice pin on the MNL-20RS4, which is AHU 01.

7.7. In the Device Discovery view, ensure that the LonWorks device is displayedin the Devices folder. This may take up to 5 seconds.



6 Commissioning the LonWorks Devices6.1 Discovering a LonWorks Device

8.8. On the Actionsmenu, click Deactivate listen to service pin. In thisexample, discover all devices before you deactivate “Listen to service pin”.

9.9. Drag the discovered service pin (device) to the System Tree 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 Service Pin 1 device to ...University XES1/Servers/CPlant AS/LonWorks Local FT-10 Interface/EastWing/AHUs/AHU 01.

Important• You cannot drag a standard MNL LonWorks device to theSystem Tree pane if the discovered device is in anunconfigured state. For more information, see the DraggingDiscovered MNL LonWorks Device to System Tree Pane DoesNot Acquire Neuron ID topic on WebHelp. For more information,see the Dragging Discovered MNL LonWorks Device to SystemTree Pane Does Not Create New MNL Device topic on WebHelp.

51

Tip• To verify the device Neuron ID, select the device in the SystemTree pane, and then select Properties on the Filemenu. TheNeuron ID can be found on the Basic tab of the DeviceProperties.

In our example, repeat the procedure to discover the Neuron ID of the VAV 01 01device.

VAV 01 01

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


6 Commissioning the LonWorks Devices6.2 Commissioning a LonWorks Device

6.2 Commissioning a LonWorks DeviceYou commission physical LonWorks devices to make them operational. Thecommission enables the devices to communicate on the LonWorks network.

For more information, see the LonWorks Commission and Decommission topic onWebHelp.

In this example, you commission the AHU 01 device in the East Wing, LonWorksnetwork.

To commission a LonWorks device1.1. In WorkStation, in the System Tree pane, select the device. In this

example, select ...University X ES1/Servers/CPlant AS/LonWorksLocal FT-10 Interface/East Wing/AHUs/AHU 01.

2.2. On the Actions menu, click Commission.

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



6 Commissioning the LonWorks Devices6.2 Commissioning a LonWorks Device

4.4. Select which configuration to use:

• Click Keep current configuration in the device to leave theconfiguration in the device as is.

• Click Download current configuration to device to use the currentconfiguration from Building Operation.

• Click Download default configuration to device to use the defaultconfiguration from the device template.

• Click Upload configuration from device to use the currentconfiguration in the device.

In this example, click Download current configuration to device.

Important• Before downloading or uploading the device configuration,

carefully consider the effects of overwriting the current deviceconfiguration in the LonWorks device or Building Operationserver.

53

5.5. Click Commission.

6.6. Click Close.

The device is commissioned and activated.

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

VAV 01 01


• Configuration: Download current configuration to device


6 Commissioning the LonWorks Devices6.3 Downloading an MNL LonWorks Application Type

6.3 Downloading an MNL LonWorksApplication TypeYou download an application type to an MNL LonWorks device to load the devicewith its assigned application.

ImportantIn Building Operation, use WorkStation to download MNL device applications. Donot use WorkPlace Tech Tool 5.x to download an MNL device that has alreadybeen assigned an application in Building Operation.

54

In this example, you download the application assigned to the AHU 01 (MNL-20RS4) device.

To download an MNL LonWorks application type1.1. In WorkStation, in the System Tree pane, select the MNL LonWorks device

that you want to download the application to. In this example,select ...University X ES1/Servers/CPlant AS/LonWorks Local FT-10Interface/East Wing/AHUs/AHU 01.

WarningPrior to application download, manually override any criticalequipment that is controlled by outputs on the affected field devices.When the download completes, the devices are reset and all outputsare turned off until the application restarts, removing any softwareoverrides (forced values) that were in effect before the download.Such overrides may be in place while service is being performed onthe equipment, and their inadvertent removal can result in personalinjury or equipment damage.

2.2. On the Actionsmenu, point toMNL and then click Download.

For this example, repeat the procedure to download the application assigned to theVAV 01 01 (MNL-V2RV3) device.

VAV 01 01



CreatingCreating thethe LocalLocal NodeNode andand7NetworkNetwork VariablesVariables

TopicsTopicsCreating Network Variables AutomaticallyCreating an Output Network VariableConfiguring the Value for a Network Variable Member

7 Creating the Local Node and Network Variables

Our ExampleIn 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, nvoVAVOccCmd. Finally, youconfigure some properties of the network variables.


7 Creating the Local Node and Network Variables7.1 Creating Network Variables Automatically

7.1 Creating Network VariablesAutomaticallyYou create network variables in the local node by mirroring network variables inLonWorks field bus devices when you want to create and bind multiple networkvariables in one action, which saves you engineering time.

For more information, see the LonWorks Local Node topic on 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 automatically1.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 berepresented in the local node. In this example, select ...University XES1/Servers/CPlant AS/LonWorks Local FT-10 Interface/EastWing/AHUs/AHU 01/UFPTsatelliteS4 [8030].

2.2. In the List View, select the network variables that you want to be representedin the local node. In this example, select nviOccCmd, nviSatTemp1,nviSatPressP1, and nvoSatSwitch1.

3.3. On the Filemenu, point to New and then clickMirrored networkvariables.

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.

58

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

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

• Name:

– nvoOccCmd– nvoSatPercent1– nvoSpaceTemp– nvoTerminalLoad

VAV 01 02 Network Variables

• Location: ...University X ES1/Servers/CPlant AS/LonWorks Local FT-10Interface/East Wing/VAVs/VAV 01 02/UFPTvavV3 [8010]


7 Creating the Local Node and Network Variables7.1 Creating Network Variables Automatically

• Name:

– nvoOccCmd– nvoSatPercent1– 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.


7 Creating the Local Node and Network Variables7.2 Creating an Output Network Variable

7.2 Creating an Output Network VariableYou create output network variables in functional blocks in a local node for bindingLonWorks variables between the Automation Server and LonWorks devices.

For more information, see the LonWorks Local Node topic on WebHelp.

In this example, you create an output network variable called nvoVAVOccCmd inthe AHU 01 functional block that will be bound to the nviOccCmd SNVTs in VAV(MNL-V2RV3) devices.

To create an output network variable1.1. In WorkStation, in the System Tree pane, select the functional block where

you want to create the variable. In this example, select ...University XES1/Servers/CPlant AS/LonWorks Local FT-10 Interface/EastWing/Local Node/AHU 01.

2.2. On the Filemenu, point to New and then click Network Variable.

3.3. In the Resource files kit box, select the DRF that contains the types for thevariable. In this example, select standard.

4.4. In the Type box, select the type of variable. In this example, selectSNVT_occupancy.

5.5. In the Direction box, select Output.

6.6. In the Name box, type a name for the variable. In this example, type“nvoVAVOccCmd.”

7.7. Click Next.



7 Creating the Local Node and Network Variables7.2 Creating an Output Network Variable

8.8. In the Sending enabled box, select Yes to send the variables at periodicintervals.

9.9. In the Send rate box, enter the number of seconds between the sends. Inthis example, enter 60.

10.10. In the Initial Value box, enter the initial value for the variable. In thisexample, enter OC_OCCUPIED.

11.11. Click Create.


7 Creating the Local Node and Network Variables7.3 Configuring the Value for a Network Variable Member

7.3 Configuring the Value for a NetworkVariable MemberYou configure the value for a network variable member by editing its properties.

For more information, see the Network Variables and Configuration Parameterstopic on WebHelp.

In this example, you configure the value for the network variable member namedOccupancy, which is a member of the network variable named nvoOccCmdUFPTsatelliteS4 [8030] in the local node.

To configure the value for a network variable member1.1. In WorkStation, in the System Tree pane, expand the network variable and

then select the variable member. In this example, expand ...University XES1/Servers/CPlant AS/LonWorks Local FT-10 Interface/EastWing/Local Node/AHU 01/nvoOccCmd UFPTsatelliteS4 [8030] andselect Occupancy.

2.2. On the Filemenu, click Properties.

3.3. In the Value box, enter the value of the variable. In this example, enterOC_OCCUPIED.

4.4. Click OK.


7 Creating the Local Node and Network Variables7.3 Configuring the Value for a Network Variable Member

In this example, repeat the procedure to configure the value for the networkvariable members Occupancy and Temperature, which are members of thenetwork variables nvoVAVOccCmd and nvoSatTemp1 respectively in the localnode. Use the following settings:

Table: nvoVAVOccCmd – Occupancy

Component Setting

Location ...University X ES1/Servers/CPlantAS/LonWorks Local FT-10 Interface/EastWing/Local Node/AHU01/nvoVAVOccCmd/Occupancy

Value OC_OCCUPIED

Table: nvoSatTemp1 – Temperature

Component Setting

Location ...University X ES1/Servers/CPlantAS/LonWorks Local FT-10 Interface/EastWing/Local Node/AHU01/nvoSatTemp1 UFPTsatelliteS4[8030]/Temperature

Value 13 °C (55 °F)


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

TopicsTopicsCreating a Function Block ProgramImporting Function Block Program CodeCreating a Change of State AlarmCreating a Digital ScheduleConfiguring a Schedule as a Shadow

8 Creating Programs, Alarms, and Schedules in the Automation Server

Our ExampleIn 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.


8 Creating Programs, Alarms, and Schedules in the Automation Server8.1 Creating a Function Block Program

8.1 Creating a Function Block ProgramYou 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 the Graphical Programming topic on 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 program1.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.2. On the Filemenu, point to New and then click Program.

3.3. In the object type list, select Function Block Program.

4.4. In the Name box, type a name for the function block program. In thisexample, type “DischAirTempSP.”

5.5. Click Create.


8 Creating Programs, Alarms, and Schedules in the Automation Server8.1 Creating a Function Block Program

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

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

• Name:

– Occupancy

– StaticPressSP

– VAVAlarms


8 Creating Programs, Alarms, and Schedules in the Automation Server8.2 Importing Function Block Program Code

8.2 Importing Function Block Program CodeYou import function block program code to reuse all or parts of existing code.Function Block Editor supports import of .aut files previously created in FunctionBlock Editor.

For more information, see the Graphical Programming topic on WebHelp.

In this example, you import program code to the DischAirTempSP function blockprogram for use in the Automation Server.

To import function block program code1.1. In WorkStation, in the System Tree pane, select the function block program

you want to import program code to. In this example, select ...UniversityX ES1/Servers/CPlant AS/AHU 01/Programs/DischAirTempSP.

2.2. On the Actionsmenu, click Edit.

3.3. In Function Block Editor, on the Filemenu, click Import.

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

5.5. Click Open.



8 Creating Programs, Alarms, and Schedules in the Automation Server8.2 Importing Function Block Program Code


Tip• When a Menta file is imported, TSCH blocks and ALARM blocks

are removed, AI/DI blocks are converted to RI/BI blocks, andAO/DO blocks are converted to RO/BO blocks. As a result ofthese conversions, you may need to make adjustments to theimported Menta code.

71

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

Occupancy

• Object location: ...University X ES1/Servers/CPlant AS/AHU01/Programs/Occupancy

• File name: OccupancyPgm.AUT

StaticPressSP

• Object location: ...University X ES1/Servers/CPlant AS/AHU01/Programs/StaticPressSP

• File name: StPrSP.AUT

VAVAlarms

• Object location: ...University X ES1/Servers/CPlant AS/AHU01/Programs/VAVAlarms

• File name: VAVAlarms.AUT


8 Creating Programs, Alarms, and Schedules in the Automation Server8.3 Creating a Change of State Alarm

8.3 Creating a Change of State AlarmYou 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 the Change of State Alarm topic on WebHelp.

In this example, you create a change of state alarm named “VAV 01 TempAlarm” tomonitor VAV_01_TempAlarm in the VAVAlarms Function Block program.

To create a change of state alarm1.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 XES1/Servers/CPlant AS/AHU 01/Alarms.

2.2. On the Filemenu, point to New and then click Alarm.

3.3. In the object type list, select Change of State Alarm.

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

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

6.6. Click Next.




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

• Click True to trigger the alarm when the monitored variable is equal toTrue.

• Click False to trigger the alarm when the monitored variable is equal toFalse.

In this example, click True.

8.8. In theMonitored variable box, enter the variable that the alarm monitors.In this example, enter ...University X ES1/Servers/CPlant AS/AHU01/Programs/VAVAlarms/VAV_01_TempAlarm.

9.9. Under Time delay and shunt variable, in the Alarm delay box, enter thetime delay. In this example, enter 5.

10.10. In the Reset delay box, enter the time delay. In this example, enter 5.

11.11. Click Next.




12.12. In the Alarm message box, type the message to display when themonitored variable exceeds the alarm limit. In this example, type “The Zone01 Temperature is too high.”

13.13. In the Reset message 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 Alarm priority box, enter the priority for the alarm state. In thisexample, enter 2.

15.15. In the Reset priority box, enter the priority for the reset state. In thisexample, enter 10.

16.16. Under Category and Alerts, select the Flashing alert check box to makethe alarm flash in the Alarms pane and Alarm Views when it is triggered. Inthis example, select Flashing alert.




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

18.18. Click Next.




19.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 alarmstate.

• Click Extended when the alarm needs to be acknowledged in the alarmstate and the reset state.

In this example, click Single.

20.20. Click Next.

21.21. Click Create.

In our example, repeat the procedure to create a change of state alarm named“VAV 02 TempAlarm” to monitor VAV_02_TempAlarm in the VAVAlarms FunctionBlock program.

Table: VAV 02 TempAlarm

Component Setting

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

Name VAV 02 TempAlarm

Description Monitors the VAV 02/Zone 02 Temperature

Trigger value True

Monitored variable ...University X ES1/Servers/CPlant AS/AHU01/Programs/VAVAlarms/VAV_02_TempAlarm



Continued

Component Setting

Alarm delay (s) 5

Reset delay (s) 5

Shunt variable No

Alarm message The Zone 02 Temperature is too high

Reset message The Zone 02 Temperature has returned tonormal

Alarm priority 2

Reset priority 10

Category No

Flashing alert Yes

Audible alert Yes

Acknowledgement type Single

Attachment No


8 Creating Programs, Alarms, and Schedules in the Automation Server8.4 Creating a Digital Schedule

8.4 Creating a Digital ScheduleYou create a digital schedule to control the state of a digital value.

For more information, see the Digital Schedules topic on 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 schedule1.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.2. On the Filemenu, point to New and then click Schedule.

3.3. In the object type list, select Digital Schedule.

4.4. In the Name box, type a name for the schedule. In this example, type“AHUSchedule.”

5.5. Click Create.

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


8 Creating Programs, Alarms, and Schedules in the Automation Server8.5 Configuring a Schedule as a Shadow

8.5 Configuring a Schedule as a ShadowYou configure a schedule as a shadow to synchronize it with a schedule thatalready contains all weekly events and exception events.

For more information, see the Schedule and Calendar Synchronization topic onWebHelp.

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 shadow1.1. In WorkStation, in the System Tree pane, select the schedule you want to

configure as a shadow. In this example, select ...University XES1/Servers/CPlant AS/AHU 01/Schedules/AHUSchedule.

2.2. On the Filemenu, click Properties.

3.3. In the Lead object box, enter the schedule that you want to synchronize theshadow schedule with. In this example, enter ...University XES1/Servers/CPlant AS/Cooling Application/Schedules/CoolingPlant Enable Schedule.

4.4. Click OK.


CreatingCreating BindingsBindings forfor9CommunicationCommunication

TopicsTopicsCreating a LonWorks BindingImporting a SolutionBinding Values Using a Binding TemplateConfiguring the Value Transfer IntervalSummary

9 Creating Bindings for Communication

Our ExampleIn 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, Automation Server, and 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.

Finally, you configure delta values for some of the network variables in the localnode. You use the delta value to control the value transfer interval. The networkvariable value is transferred only if the value change exceeds the delta value.


9 Creating Bindings for Communication9.1 Creating a LonWorks Binding

9.1 Creating a LonWorks BindingYou 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 the LonWorks Bindings topic on WebHelp.

In this example, you create the LonWorks binding between the nvoVAVOccCmdoutput variable 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 binding1.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-10Interface/East Wing/Local Node.

2.2. On the Actionsmenu, click Edit bindings.

3.3. In the binding point list, select the variable you want to bind to. In thisexample, select AHU 01/Outputs/nvoVAVOccCmd.

4.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-10Interface/East Wing/VAVs/VAV 01 01.

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



9 Creating Bindings for Communication9.1 Creating a LonWorks Binding

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 UFPTvavV3[8010]/nviOccCmd to the binding box for nvoVAVOccCmd.

Important• To bind more than one variable to a binding point, drag the

variable to the name of the binding point. Each binding adds arow to the binding point.

85


Tip• You cannot use a custom binding template when you create

LonWorks 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 toUnacknowledged Repeated Profile, which is the correct binding profile to usefor this group binding.

Local Node Bindings

Path to Local Node: ...University X ES1/Servers/CPlant AS/LonWorks Local FT-10 Interface/East Wing/Local Node

Table: AHU 01/Outputs

Binding Point Binding

nvoVAVOccCmd ~/LonWorks Local FT-10 Interface/EastWing/VAVs/VAV 01 02/UFPTvavV3[8010]/nviOccCmd


9 Creating Bindings for Communication9.2 Importing a Solution

9.2 Importing a SolutionYou 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 the Import and Export of Solutions topic on 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 LonWorks devices.

To import a solution1.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 ...UniversityX ES1/System/Binding Templates.

2.2. On the Filemenu, click Import.

3.3. In the Open dialog box, select the file and click Open. In this example,select DataFromLocalNodeTemplate.xml.

4.4. In the Import dialog box, resolve any name conflicts listed under Nameconflicts. In this example, there should not be any name conflicts.

5.5. Click Import.


9 Creating Bindings for Communication9.2 Importing a Solution

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.

• Location: ...University X ES1/System/Binding Templates

• File name: SchedAndAlarmsTemplate.xml


9 Creating Bindings for Communication9.3 Binding Values Using a Binding Template

9.3 Binding Values Using a BindingTemplateYou use binding templates to reduce engineering time when creating bindings.Binding templates are defined and created for binding patterns that are frequentlyreused.

Tip• When creating bindings, follow the recommended general guidelines: create

bindings between Inputs and Outputs only and do not create bindings toPublic Signals.

88

For more information, see the Binding Templates topic on WebHelp.

In this example, you create the bindings for the DischAirTempSP program in theAutomation Server AHU 01 folder. You use the custom binding template named“Values From Local Node” to create the required bindings. The created bindings areinternal to the Automation Server.

To bind values using a binding template1.1. In WorkStation, in the System Tree pane, select the object that you want to

bind values to. In this example, select ...University XES1/Servers/CPlant AS/AHU 01/Programs/DischAirTempSP.





3.3. In the binding point browser, drag the object or folder to the binding templatethat you want to apply. In this example, drag ...University XES1/Servers/CPlant AS/LonWorks Local FT-10 Interface/EastWing/Local Node to the Values From Local Node custom bindingtemplate.

4.4. Select the bindings that you want to create. In this example, keep allbindings selected.

5.5. Click OK.




6.6. Verify that all bindings are correctly bound. In this example, verify thebindings against the table below.


Tip• To ensure data flow is occurring as intended, use the Watch pane to view

values and monitor changes.

90

DischAirTempSP Program in the Automation Server AHU 01 Folder

Table: Results Verification – DischAirTempSP Program Bindings


Input - VAV_01_TerminalLoad ~/LonWorks Local FT-10 Interface/EastWing/Local Node/VAV 0101/nviTerminalLoad UFPTvavV3[8010]/Percentage level/Value

Input - VAV_02_TerminalLoad ~/LonWorks Local FT-10 Interface/EastWing/Local Node/VAV 0102/nviTerminalLoad UFPTvavV3[8010]/Percentage level/Value

Output - SatTemp1 ~/LonWorks Local FT-10 Interface/EastWing/Local Node/AHU 01/nvoSatTemp1UFPTsatelliteS4 [8030]/Temperature/Value



For this example, repeat the procedure to create the required bindings for theother 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/AHU01/Programs/Occupancy program:

• Drag ...University X ES1/Servers/CPlant AS/LonWorks Local FT-10Interface/East Wing/Local Node to the Values From Local Nodecustom binding template.

• Drag ...University X ES1/Servers/CPlant AS/AHU 01 to the Schedulesand Alarms custom binding template.

Table: Results Verification – Occupancy Program Bindings


Input - AHUSchedule ~/AHU 01/Schedules/AHUSchedule/Value

Input - VAV_01_OccCmd ~/LonWorks Local FT-10 Interface/EastWing/Local Node/VAV 01 01/nviOccCmdUFPTvavV3 [8010]/Occupancy/Value

Input – VAV_02_OccCmd ~/LonWorks Local FT-10 Interface/EastWing/Local Node/VAV 01 02/nviOccCmdUFPTvavV3 [8010]/Occupancy/Value

Output – OccCmd ~/LonWorks Local FT-10 Interface/EastWing/Local Node/AHU 01/nvoOccCmdUFPTsatelliteS4 [8030]/Occupancy/Value

Output – VAVOccCmd ~/LonWorks Local FT-10 Interface/EastWing/Local Node/AHU01/nvoVAVOccCmd/Occupancy/Value

StaticPressSP Program in the Automation Server AHU 01 Folder

Create the bindings for the ...University X ES1/Servers/CPlant AS/AHU01/Programs/StaticPressSP program:


Table: Results Verification – StaticPressSP Program Bindings


Input - VAV_01_SatPercent1 ~/LonWorks Local FT-10 Interface/EastWing/Local Node/VAV 0101/nviSatPercent1 UFPTvavV3[8010]/Percentage level/Value

Input - VAV_02_SatPercent1 ~/LonWorks Local FT-10 Interface/EastWing/Local Node/VAV 0102/nviSatPercent1 UFPTvavV3[8010]/Percentage level/Value



Continued


Output - SatPressP1 ~/LonWorks Local FT-10 Interface/EastWing/Local Node/AHU 01/nvoSatPressP1UFPTsatelliteS4 [8030]/Pressure(gauge)/Value

VAVAlarms Program in the Automation Server AHU 01 Folder

Create the bindings for the ...University X ES1/Servers/CPlant AS/AHU01/Programs/VAVAlarms program:


Table: Results Verification – VAVAlarms Program Bindings


Input - AHU_01_SatSwitch1 ~/LonWorks Local FT-10 Interface/EastWing/Local Node/AHU 01/nviSatSwitch1UFPTsatelliteS4 [8030]/State/Value

Input - VAV_01_SpaceTemp ~/LonWorks Local FT-10 Interface/EastWing/Local Node/VAV 0101/nviSpaceTemp UFPTvavV3[8010]/Temperature/Value

Input - VAV_02_SpaceTemp ~/LonWorks Local FT-10 Interface/EastWing/Local Node/VAV 0102/nviSpaceTemp UFPTvavV3[8010]/Temperature/Value


9 Creating Bindings for Communication9.4 Configuring the Value Transfer Interval

9.4 Configuring the Value Transfer IntervalYou adapt the value transfer interval between objects in the database to better suitthe transfer workload in the system.

For more information, see the Value Transfer Settings topic on WebHelp.

In this example, you configure the delta value for the network variable membernamed Occupancy, which is a member of the network variable named nvoOccCmdUFPTsatelliteS4 [8030] in the local node.

To configure the value transfer interval1.1. In WorkStation, in the System Tree pane, select the object. In this

example, select ...University X ES1/Servers/CPlant AS/LonWorksLocal FT-10 Interface/East Wing/Local Node/AHU 01/nvoOccCmdUFPTsatelliteS4 [8030]/Occupancy.


3.3. In the Bindings view, click the Edit button .

4.4. In the Value transfer settings dialog box, select the value transfer interval.In this example, in the Delta value box, enter 0.

5.5. Click OK.


9 Creating Bindings for Communication9.4 Configuring the Value Transfer Interval


In this example, repeat the procedure to configure the delta value for the networkvariable members Occupancy and Temperature, which are members of thenetwork variables nvoVAVOccCmd and nvoSatTemp1 respectively in the localnode. Use the following settings:

Table: nvoVAVOccCmd – Occupancy

Component Setting

Location ...University X ES1/Servers/CPlantAS/LonWorks Local FT-10 Interface/EastWing/Local Node/AHU01/nvoVAVOccCmd/Occupancy

Delta value 0

Table: nvoSatTemp1 – Temperature

Component Setting

Location ...University X ES1/Servers/CPlantAS/LonWorks Local FT-10 Interface/EastWing/Local Node/AHU 01/nvoSatTemp1UFPTsatelliteS4 [8030]/Temperature

Delta value 0.5


9 Creating Bindings for Communication9.5 Summary

9.5 SummaryThe East Wing of the School of Business is now being controlled by a LonWorksnetwork comprised of one MNL-20RS4 LonWorks device for the Air Handling Unitand two MNL-V2RV3 LonWorks devices for VAV damper control.

As a result of LonWorks bindings, space temperature, occupancy status, terminalload, and damper position values are all inputs to the VAV controllers and the valveposition and fan status values are inputs to the Air Handling Unit. Occupancycommand, discharge air temperature setpoint, static pressure setpoint are alloutputs to the Air Handling Unit.

As a result of Building Operation bindings, terminal load, occupancy command, andVAV occupancy status and damper position, VAV temperature, and AHU fan statusvalues are inputs to the programming in the Automation Server. Discharge airtemperature setpoint, AHU and VAV occupancy command, ventilation request,static pressure setpoint, and VAV temperature alarm values are outputs from theprogramming in the Automation Server.

The network of LonWorks devices are programmed and configured and are onlineand communicating.

The Automation Server was already functioning as an IP controller for the CentralPlant as a result of previous work in the system. Now the Automation Server is alsofunctioning as an interface to the LonWorks network, a LonWorks devicefunctioning as a data manager for the LonWorks network, and the BuildingOperation database server.


Schneider Electric | Buildings Divisionwww.schneider-electric.com/buildings

© 2013 Schneider Electric. All rights reserved.

04-14032-01-enJuly 2013

Date post:	10-Jul-2020
Category:	Documents
Upload:	others
View:	9 times
Download:	0 times

Creating and Configuring a LonWorks Network with MNL...

Documents