IzoTTM Commissioning Tool User’s Guide Design, install, operate, and maintain IzoT and LONWORKS® networks with the IzoT Commissioning Tool.
Echelon, LON, LONWORKS, IzoT, LonTalk, Neuron, LONMARK, 3120, 3150, LNS, LonMaker, LonSupport and the Echelon logo are trademarks of Echelon Corporation that may be registered in the United States and other countries. Other brand and product names are trademarks or registered trademarks of their respective holders.
Table of Contents Preface ...................................................................................................xi Purpose .......................................................................................................... xii Audience ......................................................................................................... xii System Requirements ....................................................................................
Determining User Permissions ............................................................... 28 Optimizing IzoT Commissioning Tool Network Performance ................. 28 Drawing Files .................................................................................... 28 Network Changes ............................................................................. 29 Connections ......................................................................................
Creating Dynamic Functional Block Master SmartShapes ........ 93 Creating a Virtual Functional Block .................................................. 93 Adding a Message Tag SmartShape to a Virtual Functional Block ......................................................................... 94 Deleting Message Tag SmartShapes ........................................ 94 Creating Network Variables .................................................................... 94 Creating a Network Variable SmartShape ...
Managing and Editing Device Templates with the Network Explorer ............................................................................ 134 Managing Device Templates ................................................... 134 Editing Device Template Properties......................................... 135 Working with IzoT Commissioning Tool Layers .......................................... 137 Working with IzoT Commissioning Tool SmartShapes ...............................
Hiding Browser Rows ............................................................... 174 Saving Browser Customization....................................................... 175 Monitoring Network Variables ............................................................... 175 Enabling Network Variable Monitoring ........................................... 175 Disabling Network Variable Monitoring .......................................... 175 Getting Network Variable Values .....................................
Creating a Backup from an OpenLNS CT Drawing ........................ 210 Creating a Backup from the IzoT Commissioning Tool Design Manager ............................................................................. 212 Scheduling Drawing Saves and Database Backups............................. 213 Scheduling Backups with IzoT Commissioning Tool ............... 213 Scheduling Backups with the Windows Task Scheduler ......... 214 Restoring an IzoT Commissioning Tool Network .................................
Maintaining IzoT Commissioning Tool ........................................................ 282 Upgrading IzoT Commissioning Tool Standard Edition to IzoT Commissioning Tool Professional Edition .......................................... 288 Renewing IzoT Commissioning Tool Annual Maintenance ......................... 291 Transferring IzoT Commissioning Tool Licenses ........................................ 291 11 Using Plug-ins .............................................................................
Appendix C OpenLNS Software License Agreement ......................369 OpenLNS CT Software License Agreement................................................ 370 Appendix D Software License Transfer Agreement ........................377 Software License Transfer Agreement ........................................................
Preface The IzoT Commissioning Tool is a software package for designing, installing, and maintaining multi-vendor, open, interoperable LONWORKS® control networks and IzoT networks. Installing the IzoT Network Services Server on the same computer with the OpenLNS Commissioning Tool converts the OpenLNS Commissioning Tool to an IzoT Commissioning Tool.
Purpose This guide outlines the the IzoT Commissioning Tool, and it describes how to use the IzoT Commissioning Tool to design, commission, monitor and control, maintain, and manage a network. The IzoT Commissioning Tool includes online help that provides context-sensitive documentation that supplements the information in this guide. Audience This guide is intended for system designers and integrators with an understanding of control networks.
i.LON 600 LonWorks/IP Server User's Guide (078-0272-01A) Describes how to install, configure, use, and manage the i.LON 600 IP-852 routers, and how to use the Echelon IP-852 Configuration Server. Introduction to the LONWORKS Platform (078-0183-01B) Provides a high-level introduction to LONWORKS networks and the tools and components that are used for developing, installing, operating, and maintaining them.
Region The Americas Languages Supported English Japanese Contact Information Echelon Corporation Attn. Customer Support 550 Meridian Avenue San Jose, CA 95126 Phone (toll-free): 1.800-258-4LON (258-4566) Phone: +1.408-938-5200 Fax: +1.408-790-3801 lonsupport@echelon.com Europe English German French Italian Echelon Europe Ltd. Suite 12 Building 6 Croxley Green Business Park Hatters Lane Watford Hertfordshire WD18 8YH United Kingdom Phone: +44 (0)1923 430200 Fax: +44 (0)1923 430300 lonsupport@echelon.co.
• Getting Started: Provides information on the planning an IzoT Commissioning Tool network design; using the OpenLNS CT Design Manager; setting up a network interface; creating and opening an OpenLNS CT network design; OpenLNS CT client types; using OpenLNS CT remotely; and creating and using user profiles. • Designing Networks: Describes how to design a network using the IzoT Commissioning Tool.
1 Introduction This chapter provides an introduction to the IzoT Commissioning Tool, describes new features, and explains the basics of IzoT Commissioning Tool Network Designs, LONWORKS, and Visio.
Introduction to the IzoT Commissioning Tool The IzoT Commissioning Tool (OpenLNS CT and LonMaker) is a LONWORKS® network tool that runs on the OpenLNS network operating system and uses Microsoft Visio® 2010 or Visio 2003 (Professional or Standard editions) as a graphical user interface.
devices that comply with the ISO/IEC 14908-1 Control Network Protocol. This includes devices based on the FT 6000 Smart Transceiver, FT 5000 Smart Transceiver, Neuron® 6000 Processor, Neuron® 5000 Processor, FT 3150/3120 Smart Transceiver, or PL 3170/3150/3120 Smart Transceiver, and also includes devices based on third-party ISO/IEC 14908-1 protocol processors. This reduces network installation costs, makes installation and maintenance costs more predictable, and simplifies the installation process.
properties, synchronization, and documents [backup/restore, XML export/import]). This manual assumes you are using Visio 2010—if you are using Visio 2003, open the LonMaker menu when this document instructs you to click Add-ins and then select the desired option.
IzoT Commissioning Tool Network Designs An IzoT Commissioning Tool Network Design consists of an OpenLNS network database and an OpenLNS CT drawing. OpenLNS Network Database An OpenLNS network database contains definitions of the devices contained within a LONWORKS network and an OpenLNS CT drawing, including information such as the name, address, application configuration, and network connections for each device.
try to talk at the same time. Meaningful transfer of information between devices on a network, therefore, requires organization in the form of a set of rules and procedures. These rules and procedures are the communication protocol, which may be referred to simply as the protocol. The protocol defines the format of the messages being transmitted between devices and defines the actions expected when one device sends a message to another.
Network variables of identical type and length but opposite directions can be connected to allow the devices to share information. For example, an application on a lighting device could have an input network variable based on the SNVT_switch type, while an application on a dimmer-switch device could have an output network variable of the same SNVT_switch type.
to be performed on the values stored in the network variables. For example, a configuration property may specify a minimum change that must occur on a physical input to a device before the corresponding output network variable is updated. Like network variables, configuration properties have types that determine the type and format of the data they contain. Functional Blocks Applications in devices are divided into one or more functional blocks.
• Standard Configuration Property Types (SCPTs, pronounced skipits). SCPTs contain many common configuration data types. For example, SCPT_location is a configuration property type for configuration properties containing the device location as a text string. See types.lonmark.org for a list and description of all SNVTs and SCPTs.
you create a new drawing. The IzoT Commissioning Tool includes a LONWORKS template that is used automatically when you create an OpenLNS CT drawing. If you wish, you can create your own custom OpenLNS CT template and select it as the default template in the OpenLNS CT Design Manager. See New Network Options in Chapter 3 for more information on selecting the default drawing template.
IzoT Commissioning Tool User’s Guide 11
2 Installing and Activating the IzoT Commissioning Tool This chapter describes how to order the IzoT Commissioning Tool, install the various software and components included in your copy of the IzoT Commissioning Tool, and how to activate the IzoT Commissioning Tool.
Ordering the IzoT Commissioning Tool You can order the IzoT Commissioning Tool directly from Echelon, from an Echelon distributor, or from the Echelon store at store.echelon.com. If you order from the Echelon store, make sure you provide a valid e-mail address when you order the IzoT Commissioning Tool products. Once you complete your order, Echelon will send you an e-mail message to the provided e-mail address with the activation key for your IzoT Commissioning Tool products.
4. Select the components that you wish to install by selecting the appropriate check boxes on the Select Components dialog box. • Microsoft Visio: Installs the 32-bit version of the Visio 2010 drawing tool. To install the 32-bit version of Visio 2010, your computer cannot have the 64-bit version of any Office 2010 application installed on it.
You can use the LONWORKS Interfaces application in the Control Panel to define, configure, and test RNIs, IP-852 network interfaces, USB 10/20 network interfaces, and PCC/PCLTA network interfaces. • SLTA-10 Driver (Serial): Installs the network driver for the SLTA-10 serial network interface. Click this check box if you are using an SLTA-10 serial adapter as your network interface. This option is not available on 64-bit versions of Windows. • Adobe Reader: Installs Adobe Reader 9.
If you selected the Visio component in the Select Components window, the Microsoft Visio setup wizard opens. Follow the instructions in the installation program to complete the Visio setup. 8. 16 Install IzoT Commissioning Tool following these steps: a. The IzoT Commissioning Tool setup program begins automatically with the Welcome window opening. b. Click Next. The License Agreement window opens.
c. Read the license agreement and click Yes if you agree with the terms. The Customer Information window opens. d. Enter your name, organization, and the IzoT Commissioning Tool activation key in the appropriate fields. The name and organization may be entered automatically based on the user currently logged on and whether other Echelon products are installed on your computer.
e. If your computer is connected to the Internet, the IzoT Commissioning Tool installer connects to the Echelon License Server, the License Server issues activation licenses for OpenLNS Server and IzoT Commissioning Tool, and the installer stores the licenses on your computer. If your computer is not attached to the Internet, you can use the Echelon License Wizard to manually activate IzoT Commissioning Tool via e-mail or phone after installing the software (e-mail is recommended).
i. Click Finish. The ReadMe file opens if the Show the Readme File check box was selected. When you finish reading the ReadMe file, close the window. j. A confirmation dialog opens stating that the selected components have been installed. Click OK. Note: Do not uninstall any of the following applications and components that are used by OpenLNS CT: OpenLNS Server, OpenLNS XML Utility, OpenLDV, Visio, LonMark Resource Files, Multi-Port Router 50, and the IP-852 Configuration Server.
Manually Activating IzoT Commissioning Tool If your computer was not attached to the Internet when you installed IzoT Commissioning Tool, you can use the Echelon License Wizard to activate OpenLNS Server and IzoT Commissioning Tool after you complete the software installation. You can activate your software via the Internet if your computer is now online, or you can activate your software via e-mail or phone if your computer is still offline.
3. To activate your IzoT Commissioning Tool software using the over the Internet or via e-mail, click Activate Product Licenses and then click Next. To activate over the phone, click Show Advanced Tasks, Upgrade a Product License over the Phone, and then follow the instructions in the License Wizard. If your computer is offline, activate via e-mail if you have e-mail access because activating over the phone requires manually entering many lengthy alpha-numeric strings. 4.
7. The Step 3: Where Would You Like to Save Your License Requests? dialog opens. 8. In the Request File Name property, enter a full path where a license request file (.elwrq extension) is to be saved, or click Browse, specify the directory where the license request file is to be saved, and then enter a name for the file.
10. Click Send Request to Echelon to e-mail the license request file to Echelon at activation@echelon.com. Echelon will send you an e-mail message with a license response (.elwrs extension) file. For faster activation, copy the license request file to an Internet-connected computer with the License Wizard installed on it and importing it into the License Wizard. The License Wizard creates the license response file, which you can then copy to the original computer. 11. Import the license response (.
24 c. The Import License Request or Response File dialog opens. In the File Name property, enter the full path of the license response file (.elwrs extension), or click Browse and then select the file. Click Next. d. The Check License Response File dialog opens. Confirm that the Echelon product licenses in the license response file are the ones you want to activate. Click Next. The License Server installs and activates the licenses in the license response file. e.
12. Click Exit to close the License Wizard.
3 Getting Started This chapter describes how to plan and create IzoT Commissioning Tool network designs. It describes how to use the IzoT Commissioning Tool Design Manager to create, open, and manage IzoT Commissioning Tool network designs, and it explains how to set up a network interface that enables the IzoT Commissioning Tool to communicate with the network.
Design Overview To prepare to design an IzoT Commissioning Tool network, follow these steps: 1. 2. 3. 4. Define network requirements and organization. Select a network installation scenario. Determine user permissions for viewing and changing the network. Optimize network performance.
Ad-Hoc System Scenario The ad-hoc system scenario allows you to design and install the network onsite. In this scenario, IzoT Commissioning Tool loads the network configuration information into each device as you define devices, configurations, and connections. This is different from the engineered system scenario in that information is incrementally loaded to the physical devices. The advantage of the ad-hoc system scenario is its flexibility, as the installer can make decisions onsite.
When designing multiple drawing files, organize the individual drawing files as subsystems within the top-level drawing file, and limit the top-level drawing to contain only those subsystems. This minimizes the number of drawing files that must be opened as you descend the subsystem hierarchy. Avoid deep subsystem hierarchies with long subsystem names that results in long subsystem paths.
Functional Blocks If you have a large network with many unconnected network variables on the functional blocks, delete the unused network variable SmartShapes. Network variable SmartShapes add performance overhead, yet they are not required if they are not connected. You can re-add network variable SmartShapes to a functional block if you need to connect them later. To simplify following this guideline, you can create functional block master SmartShapes with your most commonly used network variables.
The IzoT Commissioning Tool Design Manager consists of five tabs that let you perform the following functions: • General. Create, open, copy, delete, and backup/restore IzoT Commissioning Tool network designs; start the OpenLNS Server application; and import and defragment OpenLNS network databases. • Options. Set a prioritized list of languages for LONMARK resource files. • New Network Options.
Network Name Specifies the name of the new IzoT Commissioning Tool network design to be created. The name must be unique to all the IzoT Commissioning Tool networks on this computer. You can enter up to 16 characters and include embedded spaces. The name is not case sensitive; therefore, you cannot create two networks with names that differ only in capitalization. The initial default network name is “Network 1”.
Defragment Database Defragments and recreates the index for the IzoT Commissioning Tool database specified in the Database Name list. This can reduce the size of and decrease the access time to a network database that has grown in size because of many changes. Backup the database before defragmenting it in the event an error occurs during the defragmentation process. Start OpenLNS Server Starts the OpenLNS Server application so that remote client computers can access the OpenLNS network database.
When IzoT Commissioning Tool displays documentation for selected devices, functional blocks, and network variables, it uses the definitions contained in LONMARK resource files. You can display the LONMARK resource file information in different languages by specifying a prioritized list of languages for LONMARK resource files in IzoT Commissioning Tool.
Remove Removes the selected language from the list. Add Adds a language to the end of the list. Exit Design Manager after Launching Visio Selecting this option automatically closes the IzoT Commissioning Tool Design Manager after launching Visio. New Network Options You can use the New Network Options tab to set the default network interface, automatically register plug-ins, set the default network management mode, and set the default drawing template.
network. This option is only available if you selected the Network Attached check box. Skip Network Interface Options Page Skips the network interface page in the Network Wizard when you create a new IzoT Commissioning Tool network. Plug-Ins Register Plug-Ins Select this check box to register all enabled plug-ins when you create a new IzoT Commissioning Tool network.
Custom IzoT Commissioning Tool templates installed in the template directory are also listed. Root Subsystem Name Specifies the top-level subsystem name, which opens on the title block on the top-center of the first page of each new OpenLNS CT drawing. Subsystem names may be up to 85 characters, may include embedded spaces, but may not include the period, backslash, colon, forward slash, or double quote characters. Subsystem names are case sensitive. The default top-level subsystem name is “Subsystem 1”.
stencil file associated with the IzoT Commissioning Tool version or description of a stencil file. Add Click Add to open the Add New Stencil dialog. Click Browse, select a Visio stencils (.vss) file from C:\Program Files\LonWorks\LonMaker\Visio (32-bit system), C:\Program Files (x86)\LonWorks\LonMaker\Visio (64-bit system), or from another folder in your computer, and then click Open. You can then enter the IzoT Commissioning Tool version and a description of the selected Visio stencil.
• • • • • • • • • • • • • • • Backup/Restore Configuration Properties Device Functional Blocks General Naming Options Network Explorer NV Browser/Monitoring OpenLNS Events IzoT Commissioning Tool Font Recovery Service Pin SmartShape ToolTips Synchronization Warnings Appendix A details the defaults you can set under each network properties options category. Setting Up a Network Interface To attach your IzoT Commissioning Tool computer to a LONWORKS network, you must define and configure an OpenLDV 4.
or have dynamic IP addresses that do not change. A static IP address is an address that is not dynamically assigned by a DHCP server. 2. Create an IP-852 interface on each computer that is to be connected to the IP-852 channel. This may include the OpenLNS Server computer and one or more IzoT Commissioning Tool computers. To create an IP-852 interface, follow these steps on each of the computers: a. Open the LONWORKS Interfaces application in the Control Panel. b. Click the IP-852 tab. c.
The devices on the IP-852 channel will not be fully commissioned until you run OpenLNS applications such as the OpenLNS Server or IzoT Commissioning Tool on each of the OpenLNS Server or IzoT Commissioning Tool computers. For more information, see the IP-852 Channel User’s Guide. Creating and Opening IzoT Commissioning Tool Networks An IzoT Commissioning Tool network consists of an OpenLNS CT drawing and an OpenLNS network database.
Commissioning Tool as a local client (IzoT Commissioning Tool is running on the same computer as the OpenLNS server). To create a new IzoT Commissioning Tool network, follow these steps: 1. Click Start on the taskbar, point to Programs, point to Echelon IzoT Commissioning Tool, and then select IzoT Commissioning Tool. The IzoT Commissioning Tool Design Manager opens. 2. Under New Network, enter the name of the network in the New Network box, or accept the default network name. 3.
Tips: 5. • You can click Finish at any point in the Network Wizard. Doing so will skip the subsequent series of pages, and your new IzoT Commissioning Tool network design will be created using the current settings in the New Network Options tab of the IzoT Commissioning Tool Design Manager. • By default, the subsequent pages in the Network Wizard will appear each time you re-open the OpenLNS CT drawing.
operational network. See Recovering an IzoT Commissioning Tool Network in Chapter 7, Maintaining Networks, for more information. 44 Network Database Path Specifies the folder that will contain the network database. By default, the database path is C:\Users\Public\Documents\LonWorks\OpenLnsCt\Databases\ . You can specify a different to place the IzoT Commissioning Tool network database; however, the network name in the database path must match the one in the Network Name box.
Notes: • The network interface you select must already have been defined and configured, as described in Setting up a Network Interface. • For IzoT Commissioning Tool to communicate on an IP-852 channel, the IzoT Commissioning Tool computer must be configured as an IP-852 device on the target channel using the IP-852 Configuration Server. If an IP-852 device name has not been defined, create one in the IP-852 Configuration Server as described in Using an IP-852 Network Interface earlier in this chapter.
Show all Options check box under Existing Networks in the IzoT Commissioning Tool Design Manager General tab is selected, the prompt will appear regardless if this check box is selected. 10. Click Next. The Plug-In Registration dialog opens. 11. Use the following commands to register, deregister, enable, and disable plug-ins in your IzoT Commissioning Tool network. Register Adds a plug-in to the Pending list, indicating that the plug-in is to be registered.
You can disable a plug-in to prevent IzoT Commissioning Tool from prompting you to register the plug-in. This button is available when a plug-in listed under Already Registered or Not Registered or either of the category labels is selected. If the Already Registered or Not Registered category label is selected, all the plug-ins under the selected category label will be disabled. Remove Removes a plug-in from the Pending list.
48 1. Click Start on the taskbar, point to Programs, point to Echelon IzoT Commissioning Tool, and then select IzoT Commissioning Tool. The IzoT Commissioning Tool Design Manager opens. 2. Under Existing Network, select which database you want to open in the Database Name list and then select in the Drawing Directory list. A Create Drawing command will appear in place of the Open Network command. 3. Click Create Drawing. Visio starts and the Naming dialog of the Network Wizard opens. 4.
5. Following steps 7 through 9 of Creating a New IzoT Commissioning Tool Network Design, select whether IzoT Commissioning Tool is attached to the network, and if it is attached, select the management mode (OnNet or OffNet). Click Finish. The Synchronization Options dialog box opens.
6. Select the desired synchronization options and subsystem assignments. Create Shapes for all Connected NVs/MTs Adds SmartShapes to functional blocks for all connected network variables or message tags created by the resynchronization. If this check box is cleared, IzoT Commissioning Tool will use generic connections when possible.
8. Select the stencils that you want to be scanned for master SmartShapes. • To add a stencil, click Add Stencil, select the desired Visio stencil file (.vss), and then click Open or double-click the stencil. • To remove a stencil, select the desired stencil and then click Remove. You can also re-order the stencil positions by selecting a stencil and clicking Move Up or Move Down. Click Finish. IzoT Commissioning Tool will then search, in order, all the listed stencils.
automatically. If you have lost Echelon’s signature on a network drawing, you have three options: (1) ignore the macro warnings as described in the next paragraph; (2) disable macro warnings as described in the next paragraph; or (3) sign the drawing with your company’s digital signature as described at http://office.microsoft.com/en-us/excel-help/digitally-sign-a-macro-project-HA001231781.aspx.
3. Click Yes. The Network Wizard opens and the Naming page opens 4. Follow steps 5–11 in Creating an IzoT Commissioning Tool Network Design. By default, the options selected in the existing network will be used in your new network; however, you can change any option. When you have completed the Plug-In Registration page, click Next. The Network Properties: Domain dialog box opens.
5. A new random domain ID is generated. To use a specific domain ID, clear the Use Randomly Generated Domain ID check box and enter your ID in hexadecimal format in the Domain ID box. Click Finish. 6. If you are copying a network created with IzoT Commissioning Tool, your new IzoT Commissioning Tool network will open and you can skip the remaining steps. 7.
and routers will be updated to match the new network database. Verify that IzoT Commissioning Tool is not attached to the original network and then click Yes to proceed with your IzoT Commissioning Tool set OnNet. Click No to return to the Management Mode page and set IzoT Commissioning Tool OffNet. Any devices you created and commissioned in your original network will have the same Neuron IDs in the copied version.
5. If you are opening an IzoT Commissioning Tool network after starting IzoT Commissioning Tool for the first time, a message may appear asking you if you want to enable macros. You must enable macros for IzoT Commissioning Tool to function. See Working with Digital Signatures for more information. 6.
Select the Automatically Determine Server Location check box to have IzoT Commissioning Tool automatically determine the location of the OpenLNS Server when you re-open your IzoT Commissioning Tool network. If this check box is cleared, IzoT Commissioning Tool will prompt you to select the server location each time you open the drawing. 8. Click Next. The Network Interface page opens, unless the Skip this Prompt check box was previously selected.
OpenLNS CT (Local Client) LonWorks Channel Device 1 Device 2 Device 3 Device 4 Device 5 Device 6 OpenLNS Server A local client can also be configured as a local IP client. In this configuration, the IzoT Commissioning Tool computer is attached to an IP-852 channel and communicates remotely with the network through an IP-852 router (SmartServer [with IP-852 routing option], i.LON 100 Internet Server [with IP-852 routing option], or i.LON 600 IP-852 Router).
Remote Full Client A remote full client is an IzoT Commissioning Tool computer that communicates with the OpenLNS Server (running on a separate computer) over a LONWORKS channel. In this configuration, the IzoT Commissioning Tool computer uses a network interface to communicate with the network (for example, a U10/U20 USB network interface or PCC-10, PCLTA-20, or PCLTA-21 network interface card).
To use IzoT Commissioning Tool on a remote full client follow these steps: 1. 2. 60 Prepare for remote operations. a. Copy any custom stencils that you will need to the OpenLNS CT drawing folder on the OpenLNS Server computer. b. Back up the OpenLNS CT drawing for the network you will be using and all other files in the drawing directory. See Backing Up an IzoT Commissioning Tool Network Design in Chapter 7, Maintaining Networks, for instructions. c.
d. Select the OpenLNS network interface or IP-852 network interface to be used to connect to the LONWORKS channel. An OpenLNS Server or remote client can be attached to an IP-852 channel using an IP network interface, such as an Ethernet network interface card (NIC), WiFi interface, or a modem channel with PPP software. The network interface to the LONWORKS channel must be defined and configured before opening an existing IzoT Commissioning Tool network on a remote full client. Click OK.
f. To open an additional network, click Start OpenLNS Server on the IzoT Commissioning Tool Design Manager. The OpenLNS Server window opens. Highlight the next network to open. Click Open Network. The Network Interface page opens. Select the network interface. Click OK. Repeat this process for each additional network you want to open. 3. Copy the IzoT Commissioning Tool backup file that you created in step 1 to the remote client. 4. Start IzoT Commissioning Tool on the remote full client.
OpenLNS CT (Remote Lightweight Client) TCP/IP LonWorks Channel Device 1 Device 2 Device 3 Device 4 Device 5 Device 6 OpenLNS Server To use IzoT Commissioning Tool on a remote lightweight client follow these steps: 1. 2. Prepare for Remote Operations. a. Copy any custom stencils that you will need to the OpenLNS CT drawing folder on the OpenLNS Server computer. b. Back up the OpenLNS CT drawing for the network you will be using and all other files in the drawing directory.
Click Yes to open the network drawing. The Network Wizard opens with the Server Location dialog. 64 6. Select Remote Lightweight Client to access the network and then click Next. 7. If the server address is configured correctly, you can skip to step 10, in which the User Logon window opens. If there is a problem with the server address, or you are opening a drawing created using LonMaker, the Selecting a Remote Network Name dialog opens.
8. Select an IzoT Commissioning Tool network to open. If a connection to this network has already been established, click Next, and skip to step 10. If you are accessing the selected network over an OpenLNS/IP interface for the first time, click Add/Remove. The Remote Networks Collection dialog box opens. 9.
Using Network Service Device SmartShapes A network service device (NSD) is a local or remote client capable of monitoring and controlling the network. Every OpenLNS Server and IzoT Commissioning Tool remote full client in a network may be represented in an OpenLNS CT drawing with an NSD SmartShape. When an IzoT Commissioning Tool network is created, it initially contains an NSD SmartShape for the OpenLNS Network Interface that represents the OpenLNS Server.
Note: If you need to remove a NSD from the physical network, first remove the network service device SmartShape from the drawing by right-clicking it and selecting Delete from the shortcut menu. Listing Network Service Devices If you are using IzoT Commissioning Tool with remote clients, you can view a list of all OpenLNS clients connected to the network. Each client is represented by a network service device.
Upgrading Network Service Devices When you upgrade IzoT Commissioning Tool or switch between an OpenLNS high performance network interface (LonTalk layer 2) and an OpenLNS network interface (LonTalk layer 5), you must upgrade your network service device. When you open the network and either of these conditions is detected, IzoT Commissioning Tool will ask whether you want to upgrade. You should typically perform the upgrade.
Creating a New User Profile To create a new user profile, follow these steps: 1. In the OpenLNS CT drawing, click Add-ins, point to IzoT Commissioning Tool, and then select User Profiles. The User Profiles dialog box opens. 2. Enter the name of the new user name in the Name box, and the password in the Password and Retype Password boxes. Both the user name and password are case sensitive.
3. Set the user interface, access, and privileges of the new user. UI Setting If you are using Visio 2003, you can select the set of IzoT Commissioning Tool and Visio menus that will be available to the user. This option is not available if you are using Visio 2010. If you are using Visio 2003, you have two choices: • Maximum. This setting provides the user a full set of toolbars, menus, and menu items for advanced use of IzoT Commissioning Tool. • Access Control 70 Minimum.
Privileges Select which actions the user can perform on objects in the OpenLNS CT drawing. You can set privileges for reading, modifying, changing the name, adding, deleting, commissioning, and replacing objects, as well as the use of plug-ins for the objects. The objects for which you can set privileges consist of the network, subsystems, channels, application devices, routers, functional blocks, connections, network variables, and configuration properties.
3. Type the old password in the Old Password box, enter the new password in the New Password and Retype Password boxes, and then click OK. The password will be changed. Modifying and Deleting User Profiles Only the Administrator can modify or delete a user profile. To modify or delete a user profile, follow these steps: 1. In the OpenLNS CT drawing, click Add-ins, point to IzoT Commissioning Tool, and then select User Profiles. The User Profiles dialog box opens. 2.
4. Enter the user name and password of the user you want to logon as. 5. Click OK. You will be logged on as the selected user. Using IzoT Commissioning Tool Remotely with User Profiles When you open an IzoT Commissioning Tool network on a remote client, you will be prompted for your user name and password (provided that the administrator password has been set for the network). After logging on to the network, you will have the same privileges as you do when working on a local client.
74 Getting Started
4 Designing Networks This chapter describes how to design a network using IzoT Commissioning Tool. It covers how to create the following objects in an OpenLNS CT drawing: application devices, functional blocks, network variables, routers, channels, and subsystems. It explains how to connect network variables. It explains working with IzoT Commissioning Tool SmartShapes and layers, customizing the IzoT Commissioning Tool user interface, and using IzoT Commissioning Tool with AutoCAD drawings.
Creating a LONWORKS Network You can design a LONWORKS network and then install it using IzoT Commissioning Tool. To design a LONWORKS network with IzoT Commissioning Tool, you create an OpenLNS CT drawing. This entails adding IzoT Commissioning Tool SmartShapes for channels, routers, devices, and functional blocks; making logical connections between devices so they can send and receive data to and from each other; and organizing the network into subsystems.
• If you have licensed IzoT Commissioning Tool as part of the NodeBuilder tool, the IzoT Commissioning Tool Basic Shapes stencil is replaced with a NodeBuilder Basic Shapes stencil that includes Release Target Device and Development Target Device shapes. Creating Application Devices An application device consists of hardware and software that runs an application and communicates with other devices using the ISO/IEC 14908-1 Control Network Protocol.
2. Enter the following information for the device. Device Name Enter the name of the device. This name must be unique within the currently displayed subsystem. The device name may be up to 85 characters and it may include embedded spaces; however, the name may not include period, backslash, colon, forward slash, or double quote characters. The default device name is the abbreviated device SmartShape name followed by a dash, a space, and the instance number “1”.
Device Template Create a New Device Template Select this check box to create a new device template for the device. If you select this check box, the Specify Device Template window opens after you click Next. In this window, you can define a new template by uploading the device interface definition from the device or importing an existing device interface (XIF) file from your computer.
4. Enter the following information: Location Specifies a 6-byte location string that documents the device’s location within the network. To store the device’s subsystem ID in this field, follow these steps: 1. Click Add-ins, point to IzoT Commissioning Tool, and then click OpenLNS Options. Select Recovery from the options category list and then select the Set Location Property to Subsystem ID check box under Subsystem Recovery Options. 2. Resynchronize the network.
with the network. Set the ping interval based on the expected movement of the device. Select Never to disable pinging. To enable pinging, change the ping interval to 15 minutes if you expect the device will seldom move or if the device is on a power line channel, 2 minutes if you expect it will move somewhat frequently, and 1 minute if you expect it will move frequently. You must set a ping value for IzoT Commissioning Tool to display device and functional block errors on their respective SmartShapes.
You can also have automatic channel selection enabled by default in each OpenLNS CT drawing you create or open. In the IzoT Commissioning Tool Design Manager, click the IzoT Commissioning Tool Default Options tab, select Device from the Options Category list, and then select the Enable Automatic Channel Selection check box.
3. Click and hold the mouse button. 4. Drag the Connector tool to the center of the SmartShape of the desired channel so that a red box opens around the channel SmartShape. 5. Release the mouse button. 6.
2. Enter the following information: Source Functional Block Name Type Displays the name of the source functional block (a master SmartShape or an existing functional block) from which the new functional block was created. This box will be empty if the functional block was created by dragging the generic functional block master SmartShape to the OpenLNS CT drawing. Displays the functional profile represented by the source functional block (open loop sensor object, for example).
in the selected subsystem with available functional blocks will be listed. Type Functional Block Type / FPT File Specifies the device template associated with the functional block. Select whether the functional block you are creating is static or dynamic. • Static/Existing. Select a functional block that is defined in the device interface. • Dynamic FB. This option is only available for devices that support dynamic functional blocks (for example, a controller such as the SmartServer).
subsequent functional block with the same name for the same device, the instance number is incremented by one. For example, the default name of a new functional block created from a digital output functional block master SmartShape named “LED” would be “LED” if it was the only one named as such for the assigned device. If a copy of the LED functional block was created and assigned to the same device, the default name would be “LED 1”. A second copy would be named “LED 2”, and so on.
To create the SmartShapes in your OpenLNS CT drawing, select the Create all Network Variables Shapes check box. 3. Click Finish to add the functional block SmartShape to the OpenLNS CT drawing. Using Automatic Device Selection You can use automatic device selection to enable IzoT Commissioning Tool to automatically select the appropriate device for a new functional block, skipping the Functional Block Wizard. This feature lets you create a new functional block with a single click and drag.
To use the Move FB command to reassign a functional block to a different device, follow these steps: 1. Right-click the functional block you want to move, point to Move FB, and click Change Assigned Device to reassign the functional block to a device on the current subsystem. The Functional Block Wizard opens 2. Under Device, select the device to which you want to reassign the functional block.
2. Right-click the functional block you want to update with the configured settings, point to Configuration Properties on the shortcut menu, and then click Paste Config. Tip: You can also paste the configuration properties to a text file to get a summary of the configuration property settings. Right-click the configured functional block, point to Copy Config from the shortcut menu, open a text editor or word processing application, and then paste the configuration properties.
4. Select the target subsystems into which you want the configuration properties to be copied. You can expand a subsystem to view any nested subsystems. 5. Select the criteria used to determine which functional blocks will be updated with the configured settings. You have three choices: • Matching Device/FB name. Both the device and functional block names must match for the functional block to be configured • Matching Device/FB Type.
7. You can remove a functional block target from the list by selecting the target’s subsystem name and then clicking Remove. If you only want to view those functional blocks in which the value of the configuration property in the target functional block differs from the source, click the check box at the bottom. You can sort the entries in a column by clicking the column header. Click the header again to toggle the order (ascending or descending). 8. Click Finish.
Dynamic functional blocks are typically used by controllers that do not have a static interface. These controllers typically require the integrator to run a plug-in or other configuration software that defines the control algorithm and configures the controller. The controller manufacturer can use dynamic functional blocks to enable an IzoT Commissioning Tool user to add functional blocks to the controller using IzoT Commissioning Tool.
5. If the selected functional profile defines mandatory and/or optional network variables, the corresponding check boxes under Dynamic FBs for creating those network variables in the dynamic functional block will be enabled. By default, the Create all Mandatory NVs check box will be selected and the Create all Optional NVs check box will be cleared. Select the check boxes for the types of network variables for which you want IzoT Commissioning Tool to create.
2. Under Device, select the device to which you want to assign the virtual functional block from the Name list 3. Under Functional Block, select Virtual Functional Block from the Name list. This option only opens in the list if the device supports a virtual functional block 4. Click Finish. Adding a Message Tag SmartShape to a Virtual Functional Block You can add a message tag SmartShape to the virtual functional block of a device that supports message tags.
setting) encapsulated within functional blocks that a particular device application expects to receive from other physical devices (an input network variable) or expects to make available to other physical devices (an output network variable). There are two types of network variables: static and dynamic. A static network variable is defined by the device application and is always available in the device. Most LONWORKS devices have functional blocks that include static network variables.
To automatically add all available network variables to a functional block, select the Create Shapes for all Network Variables check box in the New Functional Block Wizard when you add a functional block SmartShape to your drawing. To selectively add network variables, clear the Create Shapes for all Network Variables check box in the New Functional Block Wizard. This creates a functional block with no network variable SmartShapes.
3. The Create Network Variable dialog box opens. Enter the name, number, and type of the dynamic network variable(s) you are creating. a. Enter the name of the dynamic network variable. This name must be unique within the functional block. It may be up to 85 characters long and may include embedded spaces, but it may not include period, backslash, colon, forward slash, or double quote characters. b. Enter the number of dynamic network variables you are creating. c.
d. 4. 98 Select the type of the dynamic network variable based on a defined type, or the type of an existing network variable in your OpenLNS CT drawing. • To select a defined type, select Specify under the New NV Type box and then click Select. The Select Network Variable Type dialog box opens. This dialog box lists built-in data types and resource files. Expand the items listed to view the available built-in data types, SNVTs, and UNVTs.
5. Under Poll Attributes of New NV(s), select whether the dynamic network variable(s) will by default use polled monitoring. You have four choices: • Select Clear to disable polling. • Select Set to enable polling. • Select Same as Source NV to use the same poll attribute of the source network variable (enabled or disabled). This option is only available if the dynamic network variable you are creating is derived from an existing network variable.
8. Select one or more static and/or dynamic network variables SmartShapes to add to the functional block from the list of network variables available for the selected direction. If you select multiple network variables, additional SmartShapes will automatically added to the functional block. To select all of the listed network variables, click Select All. 9. To remove any “nvo” or “nvi” prefixes, select the Remove Prefix from NV Names check box.
2. Following steps 3–6 in Creating Dynamic Network Variables Using Network Variable SmartShapes, change the default name, if desired, enter the number of new dynamic network variable(s) you are creating, and set the poll attributes and the message service type and options. 3. Click OK to add the dynamic network variable to the functional block. Changing a Network Variable Name You can change the network variable name on a functional block.
4. Select one or more network variable SmartShapes to delete. To select multiple network variable SmartShapes, hold down CTRL and click the SmartShapes you want to delete. To select all of the listed network variables, click Select All. 5. Set the following options: Display Apply Changes to 6. 102 Select which network variable and message tag SmartShapes are displayed.
Deleting Dynamic Network Variables You can delete a dynamic network variable from a functional block. When you delete a dynamic network variable, you can either delete the network variable SmartShape, or you can delete both the network variable SmartShape and the implementation. You can also delete a dynamic network variable by deleting the functional block containing it.
Wizard opens each time you add a router SmartShape to your OpenLNS CT drawing. See Using Automatic Channel Selection for Routers in this section for how to enable this feature. To add a router to an OpenLNS CT drawing, follow these steps: 1. Drag a Router SmartShape ( ) from the IzoT Commissioning Tool stencil to the drawing page. The New Router Wizard opens unless you enabled automatic channel selection. 2. Enter the following information: Router Name Enter the name of the router.
Name Select the two channels that you will attach to the router. You can enter a new channel name for one or both of the channels to add new channel SmartShapes to your OpenLNS CT drawing. The channel names must be unique within the network and be no more than 85 characters long. If you are creating one or two new channels, specify the channel type for each channel in the Type box. 3. Click Next. The Router Properties window opens. 4.
the network recovery process. If the Set Location Property to Subsystem ID check box is cleared, you can enter a location description for the router. You can enter up to 6 ASCII text characters, or up to 12 hex digits. If you do not specify a value and the Set Location Property to Subsystem ID check box in the Network Properties: Recovery options category is cleared, the current value in the router will be written to this field and stored in the OpenLNS network database when the router is commissioned.
Router Name Displays the name of the router. Router Type Specify one of the following router types: Configured, Repeater, Permanent Repeater, Bridge, or Permanent Bridge. The default mode is Configured, which means that the router determines which packets to forward based on internal routing tables that are configured by IzoT Commissioning Tool.
If you did not select the Commission Device check box on the first page of the wizard, click Finish to add the router SmartShape to your OpenLNS CT drawing. Using Automatic Channel Selection for Routers You can use automatic channel selection to enable IzoT Commissioning Tool to automatically select the appropriate channels for a new router, skipping the New Router Wizard. This feature lets you create a new router with a single click and drag.
2. Enter the following information: Channel Definition Select whether the SmartShape represents a new or an existing channel. • Select Shape Represents a New Channel if you are adding a new channel to your OpenLNS CT drawing. • Select Shape Represents an Existing Channel to place devices in different subsystems on the same channel. Each subsystem may have only one channel SmartShape for a given channel, but the same channel may be referenced by channel SmartShapes in many subsystems.
selected channel type. Round-Trip Delay Description 3. Select whether to use the default round-trip delay or to specify a time for the channel in milliseconds. • Select Use Default to use the default of two packet cycles based on the average packet size. • Select Specify to set the value to the expected longest round-trip time of a message (for example, message and response).
2. Enter the following information: Subsystem Enter the name of the subsystem. The name must be unique within the current subsystem and may be up to 85 characters long. The name may include embedded spaces, but it may not include periods, backslashes, colons, forward slashes, or double quotes. Subsystem names are case sensitive.
Copy 3. subsystems. You have three choices: • Do not Copy. Only the subsystem SmartShape will be copied. None of the contents of the original subsystem will be copied into the new subsystem. This is the only option available when you create a new subsystem by dragging a Subsystem SmartShape from the IzoT Commissioning Tool Basic Shapes stencil to the drawing (all of the options are available when you create a new subsystem by copying an existing one). • Copy only Selected Subsystem.
4. Right-click the subsystem and click Expand from the network navigator. All devices, functional blocks, and available network variables in the network hierarchy will be displayed. Select one or more network variables to be supernodes. To select all the available network variables, click Select All from the network navigator. 5. Click OK. SmartShapes for the selected network variables appear on the subsystem SmartShape.
2. Right-click anywhere in the OpenLNS CT drawing, in the same or in a different subsystem, and click Paste on the shortcut menu. The New Subsystem Wizard opens. Instead of performing steps 1 and 2, you can hold down CTRL and drag the subsystem or supernode SmartShape to the desired location. 3. Enter the information for the new subsystem following the instructions in Creating a Subsystem. 4. Click Finish. IzoT Commissioning Tool copies the subsystem or supernode.
Creating a Connection with the Connector SmartShape You can create a connection with the Connector SmartShape ( ) in the IzoT Commissioning Tool Basic Shapes stencil. You can only use this method to connect functional blocks or supernodes that are in the same subsystem. You can connect network variables or message tags on functional blocks or supernodes whether they have network variable or message tag SmartShapes or not.
Creating a Connection with the Network Variable Connection Dialog Box You can create a connection using the Network Variable Connection dialog box. This dialog box provides a powerful and flexible method for creating connections. It provides a hierarchal view of the devices, functional blocks, and network variables in your IzoT Commissioning Tool network. You use this view to select the network variable hub and one or more targets to connect.
3. Create the network variable connection by selecting the following options: Hub: (box) Displays the currently selected hub network variable. This is useful when you are selecting the target network variables. Hub (tab) Displays a hierarchal view of the network, consisting of the subsystems, devices, functional blocks, and all available network variables that can be selected as the hub. Select the hub network variable on this tab before clicking the Target tab.
NV. Displays available or compatible network variables. • MT. Displays available message tags. This option is only available if you are connecting virtual functional blocks. Add Adds a connection with the currently selected network variable target to the Connections pane. Add All Adds connections with all compatible network variable targets to the Connection pane. Add FB/SNs Opens the Select Object dialog box, which you can use to add functional blocks or supernodes to the hub and target tabs.
7. In the New Connections box, select a connection description to assign to all the new connections listed in the Connections box. You can click Properties to view and modify the properties of the connection description displayed in the New Connections box. See Using Connection Descriptions in this chapter for more information on using and creating connection descriptions. 8. Click OK. The connections listed in the Connections box will be added to your OpenLNS CT drawing. 9.
eliminates the need to manually move functional block, connector, and connector reference SmartShapes to keep your OpenLNS CT drawing organized. To align all reference connection SmartShapes in a subsystem, right-click an empty space in the subsystem, point to Display Options, and then click Align All Reference Shapes on the shortcut menu.
network overhead for large multicast fan-out connections. For example, a repeated message with three retries to 64 devices generates 4 packets on the network, whereas an acknowledged message requires at least 65 packets • Unacknowledged. The sending device sends out the network variable update only once and does not expect any confirmation from the receiving device. This message service type consumes the least amount of resources, but is the least reliable.
Repeated with Alias Multicast Repeated Alias Repeated with Broadcast Multicast Repeated Broadcast Repeated with Group Multicast Repeated Group Acknowledged Alias Repeated Group (if available); otherwise, domain broadcast SCD_Alias SCD_Default ● ● SCD_SubnetBcast ● Repeated Subnet broadcast SCD_Unicast ● Acknowledged Group Unacknowledged*** Unacknowledged Group Unacknowledged with Alias Multicast Unacknowledged Alias Unacknowledged with Broadcast Multicast Unacknowledged Broadc
To view the properties of a connection description, select the connection description from the Name list. If you do make changes, click OK and IzoT Commissioning Tool then updates all network variable members of the connection with the modified connection description To create a new connection description, click New. The New Connection Description dialog box opens. Enter the name of the new connection description and select whether the currently displayed or default attributes are used, and then click OK.
These automatic SCD selection rules do not apply to message tag connections, fan-in connections (where the hub is an input network variable), or connections in which you specify a non-SCD for the connection description. To modify the automatic SCD selection rules, follow these steps: 124 1. In the OpenLNS CT drawing, click Add-ins, point to IzoT Commissioning Tool, and then select IzoT Commissioning Tool Options. The Network Properties dialog box opens. 2.
3. You can change or disable the connection description used for each condition in the automatic connection description selection process. If you disable the connection description for a given condition, IzoT Commissioning Tool will select the next defined connection description. You can also change the maximum number of target network variables used to select between the Alias Unicast and Default conditions.
Connection Description, and then click the desired connection description on the shortcut menu. To disable automatic connection description selection, select a connection description that does not start with “SCD_”. To enable automatic connection description selection, select .
To hide a connector SmartShape directly attached to two functional block SmartShapes (not attached using a reference SmartShape), select Hide Connectors on both functional blocks. The connector SmartShape will be hidden at both ends. To show the connector SmartShape, you only need to select Show Connectors on one of the attached functional blocks.
If you right click the Switch[0] functional block, point to Display Options, and then click Hide Connectors, the connector and reference SmartShapes attached to this functional block are hidden. There is no change to the connector and reference SmartShapes attached to the Lamp[0] functional block because connector SmartShapes attached via reference are hidden/shown independently on each end.
2. Select the following options for creating and displaying connection SmartShapes for the selected functional block or functional blocks. Create Connection Shapes Select whether SmartShapes are created and displayed in the OpenLNS CT drawing for connections with the selected functional block(s). You have three choices: • Yes.
Show Connection Shapes Select whether connection SmartShapes attached to the selected functional block(s) are displayed. This check box is selected by default, but it is cleared and unavailable if No is selected in the Create Connection Shapes list.
2. The window displays a hierarchal view of the subsystems in your network, with the nested subsystems and devices in the top-level subsystem and the current subsystem shown. You can expand an object to view any others further down the network hierarchy such as nested subsystems, devices, and functional blocks. You can also right-click an object and use the Network Navigator to expand an object.
To use the network navigator, right-click an object that can be expanded and then click one of the following commands in the shortcut menu: Expand Displays all objects below the selected item. Selecting expand on the top-level subsystem will display all objects in the network hierarchy. Select All Expands the item and selects the check boxes of all the objects below it. Click Select All on the top-level subsystem to select the check boxes of all the objects in the network hierarchy.
Network Explorer options category. By default subsystems, devices, and functional blocks are displayed. To expand or reduce the scope of the objects displayed in the Network Explorer, follow these steps: 1. In the OpenLNS CT drawing, click Add-ins, point to IzoT Commissioning Tool, and then select IzoT Commissioning Tool Options. The Network Properties dialog box opens. 2. Select Network Explorer from the Options Category list. 3. Select the desired scope under the Displayed Objects box.
• In the subsystem view, the top-level subsystem and all the subsystems it contains are displayed, and all the other objects in your OpenLNS CT drawing are listed below their respective subsystems in a hierarchal structure (in the order of nested subsystems, devices, functional blocks, and then network variables).
The Device Template shortcut menu contains the following options: Delete Deletes the selected device template. This option is unavailable if there are any devices currently using the device template, or if there is a device that has been discovered by the OpenLNS Server but does not yet appear in the OpenLNS CT drawing. Import XIF Updates the device template (and optionally devices) with the data from the XIF that you select.
The Device Template Properties dialog box contains the following options: Name Specifies the name of the device template. You can change the device template name to any other valid, unique name. Program ID Displays the program ID of the device template. You can select one of the following options for displaying the program ID (this selection does not change the program ID): • ASCII. Displays the program ID as an ASCII string.
When you commission a device, the OpenLNS Server by default will validate that the physical device is on the correct assigned Channel and that the device template has the same Program ID and Program Interface (XIF) defined in the network database. Clearing these check boxes may reduce the time required to commission a device.
Data Layer • Shows/hides all monitored connections. Right-click an empty space in your OpenLNS CT drawing, point to Display Options on the shortcut menu, and select View Subsystems Layers from the shortcut menu. The View Subsystem Layers dialog box opens. Select or clear the IzoT Commissioning Tool Layers you want displayed or hidden. You can click Apply if you want to see how your OpenLNS CT drawing opens with the current settings. When you are done, click OK.
1. Right-click the SmartShape. You can select multiple SmartShapes by holding down CTRL and clicking the SmartShapes, or clicking an empty space in the drawing page and dragging a selection net around the SmartShapes. 2. Point to Move Device (for device, router, and subsystem SmartShapes) or Move FB (for functional block SmartShapes) on the shortcut menu. 3. Click Change Subsystem (for device, router, and functional block SmartShapes) or Move (for subsystem SmartShapes).
2. Set the following options: Original Channel Name Specifies the current channel on which the devices or routers are attached. If you are moving devices or routers from a subsystem SmartShape that has devices or router SmartShapes connected on two or more channels, select the channel with the devices or routers you want to move. Only those devices or routers located on the selected channel will be moved.
• Select Online to put the devices or routers in the online state. This is the default for routers. The behavior in the online state depends on the device. A Neuron-hosted device, for example, will run its application after it has been moved. • Select Offline to put the devices or routers in the offline state. This is the default for devices. The behavior in the offline state depends on the device. A Neuron-hosted device, for example, will not run its application after it has been moved.
2. Change the channel on which the OpenLNS computer is attached following step 2 in Moving a Device or Router to a Different Channel. 3. If you are moving an IzoT Commissioning Tool computer and you will be using a different network interface, click Add-ins, point to LonWorks Network, and then click Network Properties. Click the Network Interface tab, select the name of the new network interface, and then click OK. 4. Click OK.
Deleted IzoT Commissioning Tool Shape Affect on Physical Device Commissioned Application Device Application device is decommissioned and no longer has a network address. Commissioned Router Router is decommissioned and no longer has a network address. OpenLNS Network Interface or NSD IzoT Commissioning Tool attempts to decommission the NSD. If the NSD is using a Layer 2 interface, it cannot be decommissioned. Disconnects any remote full clients using the NSD. Functional block (static) No change.
Commissioning Tool shortcut menus, click Add-ins, point to IzoT Commissioning Tool, and then select or clear the Use IzoT Commissioning Tool Shape Menus option. The following figures illustrate the difference of a device SmartShape menu with IzoT Commissioning Tool Shape Menus selected and cleared. Using AutoCAD Drawings You can import AutoCAD drawings into your OpenLNS CT drawing and export your OpenLNS CT drawing as an AutoCAD drawing. Importing an AutoCAD Drawing You can import an AutoCAD drawing.
4. Specify the drawing page size and scale for the AutoCAD drawing in the Page Size/Scale dialog. These settings do not affect the size of IzoT Commissioning Tool SmartShapes in the drawing. 5. Open the Edit menu and select Go To Foreground. 6. The AutoCAD drawing opens in the OpenLNS CT drawing as a background. Exporting an AutoCAD Drawing You can export an OpenLNS CT drawing as an AutoCAD drawing. This lets you create an as-built report in the same format as your other system blueprints.
146 Designing Networks
5 Installing Networks This chapter describes how to install devices using IzoT Commissioning Tool, including how to load applications into them, set the initial state of their applications, set the source of their configuration properties, and select how they manage device-specific configuration properties. It also explains the different methods for acquiring device Neuron IDs and how to alternatively use the device discovery method to install a network.
Network Installation Overview You can install the devices that you added to your IzoT Commissioning Tool network design in Designing Networks. To install devices, you commission the devices and routers in your IzoT Commissioning Tool network design. Commissioning associates the device SmartShape created in the OpenLNS CT drawing with a physical device on the network and updates the physical device to match the configuration in your network design.
Selecting Devices for Commissioning To select the device or devices to be commissioned, follow these steps: 1. Right-click the device SmartShape of the device you want to commission, point to Commissioning, and then click Commission on the shortcut menu. To select multiple devices, do one of the following: • To select multiple devices within a subsystem, hold down CTRL and click the device SmartShapes, or click an empty space in the drawing page and drag a selection net around them.
2. The Commission Device Wizard opens. Where you start in the wizard depends on whether you are commissioning an application device or router, and whether IzoT Commissioning Tool is attached to the network and OnNet or OffNet. • If IzoT Commissioning Tool is unattached to the network or attached but OffNet, the wizard will skip the Device Application Image and Initial State windows and begin with the Device Identification window.
1. Specify the device application by setting the following options: Load Application Image Select this check box to load an application image into a Neuron-hosted application device that has writeable application memory and comes with an application file (.ndl, .nxe or .apb extensions).
directory as the XIF file of the device template, that directory is the default. XIF Name 2. If you are loading an application file with an .nxe extension, select the pathname of the XIF file. IzoT Commissioning Tool only requires the binary application file (.apb extension) and the binary device interface file (.xfb extension); however, it automatically creates binary files from existing text files (.nxe and .xif extensions) and saves them in the application file folder that contains the corresponding .
Setting the Initial Application Device State and Source of Configuration Property Values When the Device Initial State window opens, follow these steps: 1. Specify the initial state of the device applications, source of the configuration property values, and management of device-specific configuration properties by setting the following options: State Set the state of the device application after it has been commissioned. You have four choices: • Default.
is reset. For a device to be disabled, it must contain a Node Object functional block. If Disable is selected and the device does not contain a Node Object, the device is placed offline. As with offline operation, portions of a disabled device’s application may continue to function. Source of CP Values Specify the source of initial values for the device’s configuration properties. • OpenLNS Database.
Image window. • Upload from New App Image. The current device-specific configuration property values in the selected application image file will be written to the device. This option is only available if you selected the check box to load an application image into the device in the Device Application Image window. • Preserve Device Values.
operation. 2. • Offline. The router will not forward packets. • Online. The router will forward packets between the channels connected to it. This is the default. If the network will have devices installed on the far side of a router (the side furthest away from the OpenLNS Server), you must commission the router before any of the application devices connected on its far side. Click Next to continue. The Device Identification Method window opens.
difficult to access. 2. Click Finish. If you selected the Service Pin method, you are prompted to press the service pin as described in Using the Service Pin Method. Once the Neuron ID is specified or acquired, IzoT Commissioning Tool commissions the device, and changes the color of the device SmartShape to green to indicate that the device has been commissioned.
To acquire the Neuron IDs and finish installing the devices, follow these steps: 1. Select any of the following service pin options Options Display Data from Service Pin Select this check box to display a dialog that contains the information returned in the service pin message. This check box is cleared by default. Filter on Program ID Select this check box to ignore service pin messages that do not include the same program ID as the device being commissioned. This option is selected by default.
Using the Manual Entry Method If you selected Manual as the device identification method or if IzoT Commissioning Tool is not attached to the network, and you are commissioning multiple devices, a prompt opens instructing you to enter the Neuron IDs of the devices you are installing. The device Neuron ID is provided by the manufacturer as a 12-digit hex string or as a bar code label on the device that can be scanned. Entering a Neuron ID Manually To enter a device’s Neuron ID follow these steps: 1. 2. 3.
scanner vendor for prices on the different scanner types. If you are using a LonPoint device, or a device with a similar bar code label, it is recommended that you use a gun-style laser or LED scanner. One scanner that you can use with IzoT Commissioning Tool devices is the Symbol Technologies LS 3000, which is made available by Barcode Logics. See your scanner documentation for instructions on programming the scanner.
2. Select the following options: Device Selection Scope Options Wink Interval Selects which subsystems will be searched for uncommissioned device SmartShapes. You have three choices: • All Subsystems. The entire OpenLNS CT drawing will be searched for uncommissioned device SmartShapes. • The Current Subsystem and Dependent Subsystems. The current subsystem and any subsystems nested in it will be searched for uncommissioned device SmartShapes. • The Current Subsystem only.
Include Devices with Unknown Programs Adds physical devices to the discovered device list that are applicationless or have an unrecognized application. Such physical devices can then be matched to any device SmartShape with a matching channel. However, after matching, you must click Details and specify an application image to load into the device. Discover Configured Devices Discovers devices that have previously been configured.
This dialog box allows you to manually or automatically match the discovered devices on the network with the defined device SmartShapes in the OpenLNS CT drawing. To select a device from any of the lists, click the entry in the leftmost column (the # column in the Discovered Devices list, and the Subsystem column in the Defined Devices and Devices to be Commissioned lists). After selecting a device, its field in the leftmost column will be shaded blue.
appropriate device list. Match Matches the device selected in the Defined Devices list is to the device selected in the Discovered Devices list. The devices are removed from their respective lists and the matched device is added to the Devices to be Commissioned list. This command is only available if one device is selected from each list and the selected devices are compatible.
11. Select an application image and set the options for the initial application state and source of configuration property values. See Loading a Device Application Image and Setting the Initial Application Device State and Source of Configuration Property Values for information on setting these options. Click OK. 12. Click Finish. IzoT Commissioning Tool commissions the devices in the Devices to be Commissioned list and sets the state of their applications.
166 Installing Networks
6 Monitoring and Controlling Networks This chapter describes how you can monitor and control the devices in your network with IzoT Commissioning Tool. It describes the three methods you can use to read and/or write network variables and configuration properties: using monitored connections, browsing with the OpenLNS CT Browser, and using Data Point SmartShapes. This chapter covers how to bind network variables to the host in order to receive event-driven updates.
Monitoring and Controlling Overview You can monitor and control the physical devices in a network by reading and writing the network variables on the devices. You can also read configuration property values. You can use any of the following three methods to read and/or write network variables and configuration properties: • Monitored connections. Monitored connections provide a simple means to view network variable values within your network.
When you enable monitoring on a connection, the network variable values are continuously polled. The default poll interval is 1 second. To change the default poll interval, click Add-ins, point to LonWorks Network, and then click Network Properties. Click the Timing tab, set the default poll rate, and then click OK. Excessive polling can create heavy network traffic and consequently degrade network performance.
Using the OpenLNS CT Browser You can use the OpenLNS CT Browser to monitor and control the network variables and configuration properties in your network. The OpenLNS CT Browser provides a table view of the selected network variables and configuration properties. You can add all the network variables and configuration properties for a functional block or device to the Browser, and you can delete selected network variables and configuration properties from it.
The OpenLNS CT browser color codes the configuration properties and network variables in the following manner: Blue Input network variables. You can write values to these network variables. See Updating Network Variable and Configuration Property Values. Green Writeable configuration properties. You can write values to these configuration properties. See Updating Network Variable and Configuration Property Values. Grey Output network variables and read-only configuration properties.
The OpenLNS CT Browser Toolbar You can use the OpenLNS CT browser toolbar to perform many browser functions quickly. The toolbar contains the following buttons: Open Opens an existing browser file. See Customizing the Browser. Save Saves changes to a browser file. If the browser file is new, the Save As dialog opens. Name the file and choose a folder in which to save the file. See Customizing the Browser for more information. Print Prints the data in the Browser window.
therefore, you would hide the subsystem column. In another example, you may want to monitor and control only a few of the network variables listed in the browser; therefore, you would hide the rows of all the other network variables that you do not want to monitor and control. Customizing Browser Columns You can hide, change the order, or adjust the width of the columns in the OpenLNS CT Browser.
Under the display box, select which objects you want displayed in the browser. You have three choices: • • • Network Variables. Only network variables are displayed in the browser. Configuration Properties. Only configuration properties are displayed in the browser. Both. Network variables and configuration properties are displayed in the browser. Select the Sort NVs by Name check box to list the network variables in the browser alphabetically.
This dialog lists all the hidden objects in the browser. Select the object or objects you want to show, or select the Select All check box to select all the objects, and then click OK. The selected objects appear in the browser again. Saving Browser Customization You can save and later restore the rows and columns that you customize in the OpenLNS CT Browser to a browser (.brw extension) file. To save your rows and columns to a browser file, open the File menu and select Save or Save As.
You can update all network variable values by clicking the Refresh All button ( toolbar or opening the Browse menu and selecting Refresh All. ) on the browser Using Bound Updates You can use bound updates with the OpenLNS CT Browser to reduce the network overhead of polling many network variables. Bound updates use a connection between the network variable being monitored and the browser.
b. Under the Device box, select OpenLNS Network Interface from the Name list. c. Under the Functional Block box, select Virtual Functional Block from the Name list. d. Enter the name of the Virtual Functional Block in the New FB Name box. 2. Drag an Input Network Variable SmartShape from the IzoT Commissioning Tool Basic Stencil to the virtual functional block. The Choose a Network Variable dialog opens. 3. Click Create NV.
All the fields for the selected object are listed in structural order in the Field List box. To set the value for a field, expand that field and then click twice slowly on the value that opens below it. Enter a valid value for the field (the minimum and maximum values appear in the Field Info box to the right). Click OK to apply the changes.
Setting Values for Configuration Property Arrays You can view and set values for a configuration property array using a table instead of using the Value box or the Set Configuration Properties dialog. To view a configuration property array, right-click a configuration property array and then click Table on the shortcut menu. The Edit Configuration Property Table dialog opens. This dialog contains a table listing the values for each element in the configuration property array.
Clearing Values You can clear the displayed value of a network variable or configuration property by right-clicking the object you want to clear and then clicking Clear Value on the shortcut menu. To clear all values in the browser display, open the Browse menu and select Clear All Values. Clearing the values in the browser display does not affect the values in the functional block. Getting Values You can get the current value of a network variable or configuration property.
This dialog lists built-in data types, and resource files containing defined network variable types (SNVTs and UNVTs). Expand the items listed to view the available data types. Click the type for the network variable and then click OK. • Select the Show Only Types with Matching Length check box to display only those types with the same size as the current network variable type.
The format may include scaling and offset values to convert one type of data to another such as Celsius to Fahrenheit or kilograms to pounds, localized formatting specifications, or text strings that are to be displayed as part of the value. For example, a temperature sensor may report a temperature value with a type of SNVT_temp_f. The SNVT_temp_f type is defined as a 32-bit signed floating-point value representing a Celsius temperature.
• Select the Show Obsolete Types check box to list those network variable types that are marked obsolete in the current standard resource file set. • The Length box displays the size (in bytes) of the currently selected type. Tip: Many standard network variable types include formats with “#US” and “#SI” format specifiers. You can use these specifiers to identify default formats when the appropriate default is determined by the regional settings on the computer running IzoT Commissioning Tool.
Using Data Point SmartShapes You can use a Data Point SmartShape in an OpenLNS CT drawing to monitor the value of any network variable configuration property, or functional block state (enabled or in override). You can also use a Data Point SmartShape to update the value of an input network variable or configuration property. You can use Data Point SmartShapes to create simple human-machine interface (HMI) applications within your OpenLNS CT drawing.
default. If this check box is selected, the same data point will be monitored in a new Data Point SmartShape. If this check box is cleared, IzoT Commissioning Tool will attempt to locate the appropriate data point using the relative subsystem\device\functional block path of the source. In addition, you can create a Data Point SmartShape that you can copy to a different subsystem and have it refer to a data point in that subsystem.
and field name [if defined]). This is the default. Device.FB.NV (the device name, functional block name, network variable name, and field name [if defined]). If the selected data point is a functional block state, the following options are available: • • • • None (no label). Status (the status name [enable/override]). FB.Status (the functional block name and status name). This is the default. • Device.FB.Status (the device name, functional block name, and status name).
a functional block state. Polling Interval Specifies how frequently (in seconds) the data point is polled. The default is 5 seconds for polled network variables and 15 seconds for monitored configuration properties and functional block states. If you change the polling interval, the value you enter becomes the default for new Data Point SmartShapes of that object type until you close the drawing and then re-open it from the IzoT Commissioning Tool Design Manager.
• A structured value is a value that contains multiple fields such as a switch value with state and level fields. • An enumerated value is a value with multiple states each represented by an enumeration string, such as an occupancy state with occupied and unoccupied values or an HVAC mode. A functional block state is also an enumerated value. Updating a Scalar Data Point To set the value of a scalar data point, follow these steps: 1.
5. • Expand a field in the Field List box and then click twice slowly on the value that opens below the field. Enter a valid value for the field (the minimum and maximum values appear in the Field Info box to the right). Repeat for any other fields for which you want to set the value. • Enter a valid value in the Data Value box for one or more of the fields in the structured data point.
Creating and Using a Custom Data Point Master SmartShape You can create a custom data point master SmartShape from an existing Data Point SmartShape, and you can include a Data Point SmartShape with other SmartShapes in a custom IzoT Commissioning Tool master SmartShape. All the properties of the Data Point SmartShape—including the selected data point, label, fonts, and colors—are saved in the custom master SmartShape.
1.Building1.Floor2.Room10” subsystem. The subsystem path stored in the Data Point SmartShape is therefore “^.^.Floor2.Room10”. This indicates that when the custom Data Point master SmartShape is added to a drawing, IzoT Commissioning Tool is to attempt to locate the monitored object by moving two subsystem levels up the network hierarchy and then down to the “Floor2.Room10” subsystem in the network.
You can use high-end HMI tools, such as Wonderware’s InTouch or Intellution FIX, to represent more complex types of network interactions. These tools are developed with a scripting language tuned to specifically address HMI tasks. In addition, these tools offer components that provide reporting and analysis, history, alarm logging, event handling, and Internet-enabling. To create a simple HMI with Data Point and Visio SmartShapes, you do the following: 1.
o To get the ID of a Data Point SmartShape, click the Data Point SmartShape, click the Developer tab, and then click Shape Name. An index is appended to the Shape ID when you add a second SmartShape of a given type to your drawing. For example, the ID of the first Data Point SmartShape added in the lighting HMI example is Data Point; the ID of the second data point is Data Point.50. If the SmartShape has an index, you can use the following naming convention to enter the Data Point Shape ID: Sheet..
In the X cell of the Scratch section, enter a formula. For example, to create a formula that brightens a lamp when you double-click the Visio shape, enter the following: =FORMAT(MODULUS("!User.MonValue"+10,110), "0"). Using a Macro to Write Values To write to a value to a Data Point SmartShape using a Macro, follow these steps: 1. Click the Developer tab, and then click Macros. The Macros dialog box opens. 2. In the Macros Name: dialog box, enter a name for the Macro.
Data Point SmartShape ID index refers to the numeric digits at the end of the Data Point SmartShape name. For example, if the name of Data Point SmartShape is Data Point.53, you will enter Sheet.53!User.MonValue (essentially, replace “Data Point” with “Sheet”). 4. • To change the color for the “on” state, you can perform some arithmetic function on the Data Point SmartShape value. For example, to change the color of the Visio SmartShape to yellow when the lamp is on, enter the following function: Sheet.
If myShape2.Cells("User.MonValue") = 1 Then myShape.Cells("FillForegnd") = 5 myShape.Text = "ON" Else myShape.Cells("FillForegnd") = 0 myShape.Text = "OFF" End If End Sub 6. In the OpenLNS CT drawing, right-click the Visio shape used to monitor the Data Point SmartShape, and then click Show ShapeSheet on the shortcut menu. The ShapeSheet of the selected Visio shape opens. 7.
7 Maintaining Networks This chapter provides an overview of network maintenance tasks that you can perform with IzoT Commissioning Tool. It describes loading, replacing, and decommissioning devices. It explains how to resynchronize and propagate configuration properties values.
Maintaining Networks Overview You can perform routine maintenance to update, repair, and optimize an installed network. You can maintain the network and its components, the OpenLNS CT drawing, and the OpenLNS network database. For example, if a device or router fails, you can replace it on the physical network and then logically replace it in the IzoT Commissioning Tool network, preserving the device’s configuration and all of its connections.
To load a new application into a device, the devices must have writeable application memory, and IzoT Commissioning Tool must be attached to the network and OnNet. To load a new application into a device, follow the five steps described in the subsequent sections: 1. Select the device or devices to upgrade. 2. Select or create a device template. 3. Select an application image to load into the device(s). 4.
name without a path only if the XIF file is in the folder specified in the XIF Search Path box Network Properties: Device options category (to access this property, click Add-ins, click IzoT Commissioning Tool, click IzoT Commissioning Tool Options, and then select Device from the Options Category list). The device template name in the Template Name box is automatically set to the name of the XIF file (without the extension), but you can change it to any name that is unique to the network.
Load Application Image Select this check box to enable loading a new application image into the device. Update Firmware in Device to Match Application Image Select this check box to load a new Neuron firmware image to make the Neuron firmware on the device compatible with the new application image file. For a device to support Neuron firmware updates, it must be based on a Nueron 5000 or Neuron 3150 core with a nonvolatile memory layout supporting at least 32K starting from address 0.
Selecting Initial Device State and Source of Configuration Property Values To select the initial device state and the source of configuration property values, follow these steps: 1. Specify the initial state of the device applications, and select the source of the configuration property values and management of device-specific configuration properties as follows: State Specify the state of the device application after it has been commissioned. You have four choices: • Default.
after a reset. • Source of CP Values Device Specific CPs Disable. Keeps the device application disabled even if the device is reset. For a device to be disabled, it must contain a Node Object functional block. If Disable is selected and the device does not contain a Node Object, the device is placed offline. As with offline operation, portions of a disabled device’s application may continue to function. Specify the source of the device’s configuration property values.
new device. 2. Click Next. The Device Identification Method window opens. Follow the steps in Installing Devices and Routers in Chapter 5, Installing Networks, to continue loading the devices. Replacing Devices You can replace a device with a new device if the device fails or a newer version of the device becomes available. The replacement device can use the same device template used by the old device or it can use a different device template.
5. Specify the initial state of the replacement device’s application, and select the source of the configuration property values and management of device-specific configuration properties as follows: State Set the state of the device application after the replacement device has been commissioned. You have four choices: • Default. The state of the replacement device’s application is determined by the current setting under the New Device Options box in the Network Properties: Device options category.
and the device does not contain a Node Object functional block, the device is placed offline. As with offline operation, portions of a disabled device’s application may continue to function. This option is not available for routers. Source of CP Values Device Specific CPs 6. 206 Specify the source of the replacement device’s configuration property values. You have three choices: • OpenLNS Database.
case, follow the steps in Installing Devices and Routers in Chapter 5, Installing Networks, to continue installing the devices). Removing the Old Device If the old device still functions, and if physically possible, leave the old device connected to the network until the device replacement has been completed. This allows IzoT Commissioning Tool to deconfigure the old device so that you can easily reuse it in a new network. This step is not required if the device has failed.
network tool not based on OpenLNS is used to update the physical devices, or if the devices themselves update their own configuration properties. To resynchronize the configuration properties for a device, follow these steps: 1. Right-click the device, or select multiple devices and right-click one of them, point to Commissioning, and then click Resync CPs on the shortcut menu. The Set Configuration Properties dialog opens. 2.
3. Click OK. IzoT Commissioning Tool updates the device and the OpenLNS network database, as required. Using IzoT Commissioning Tool as a Passive Configuration Tool You can use IzoT Commissioning Tool as a passive configuration tool. A passive configuration tool is a tool that that configures the application in a device without affecting its network configuration. A passive configuration tool is required when a network tool not based on OpenLNS is being used to manage the configuration of a network.
You can manually back up an IzoT Commissioning Tool network design, or you can have IzoT Commissioning Tool schedule periodic backups. Manually Backing Up an IzoT Commissioning Tool Network You can back up an IzoT Commissioning Tool network design from an OpenLNS CT drawing or from the IzoT Commissioning Tool Design Manager.
3. 4. • Select the Backup Database check box to back up the OpenLNS network database only. Use this option to move the network database to an OpenLNS Server computer that does not have IzoT Commissioning Tool installed. • Select the Backup NodeBuilder Project check box to back up the NodeBuilder project associated with the IzoT Commissioning Tool network, if there is one. This option is only available if you are using the NodeBuilder Development Tool.
6. 7. • If the backup file includes the drawing and database, the default backup file is [_index].zip. • If the backup file includes only the drawing, the default backup file is Dwg[_index].zip. • If the backup file includes only the database, the default backup file is Db[_index].zip. Click OK.
Scheduling Drawing Saves and Database Backups You can schedule regular backups of an IzoT Commissioning Tool network using IzoT Commissioning Tool or the Windows Task Scheduler. Scheduling Backups with IzoT Commissioning Tool You can schedule IzoT Commissioning Tool to automatically save an OpenLNS CT drawing and back up the network database. To use this feature, you set an interval in which the OpenLNS CT drawing is to be saved and the network database backed up.
5. You can set the maximum number of hot backups that are saved for all IzoT Commissioning Tool networks (includes hot backups created automatically and manually). By default, IzoT Commissioning Tool will save five hot backups of a given network database before deleting older hot backups to create new ones. To change the maximum number of hot backups, enter the desired maximum in the Max Number of OpenLNS Hot Backups box. 6.
7. Click Next. 8. Click Finish. Windows XP SP3 To create a scheduled task in Windows XP3, follow these steps: 1. Open the Windows Task manager. Click Start on the taskbar, click Run, and the enter C:\Windows\tasks. The Windows Task dialog opens. 2. Double-click Add Scheduled Task. The Scheduled Task Wizard opens. 3. Click Next. 4. Under the Application column, locate and then click LonMaker. Click Next. 5. Modify the task name, if desired, and select how often you want the backup performed.
Restoring an IzoT Commissioning Tool Network You can restore an IzoT Commissioning Tool network from a standard IzoT Commissioning Tool backup or a hot backup. If you restore an IzoT Commissioning Tool network containing only a network database or an OpenLNS CT drawing, IzoT Commissioning Tool replaces the current drawing file and/or database with the backup copy (unless the network does not already exist on a local client).
IzoT Commissioning Tool backup file (.zip extension) of the desired database backup (the database backup file names are in the following format by default: Db[_index].zip), and click Open or double-click the IzoT Commissioning Tool backup file. • If you select the Restore from OpenLNS Hot Backup check box, select the OpenLNS hot backup to restore. The OpenLNS hot backups appear in the order they were created. By default, the first OpenLNS hot backup created is selected.
7. This dialog box displays the paths where the restored network database will be saved. You cannot change the directory if the database already exists on your computer. Click OK. A message will appear prompting you to select whether to delete or overwrite the existing directory. 8. Click Yes to delete the existing drawing folder before restoring the network, or click No to overwrite it. The database restore operation begins. 9. When the network database has been restored, a confirmation dialog opens.
6. Select the IzoT Commissioning Tool backup file (.zip extension) of the desired OpenLNS CT drawing to restore (the drawing backup files are in the following format by default: Dwg[_index].zip), and click Open or double-click the IzoT Commissioning Tool backup file. 7. Click OK in the IzoT Commissioning Tool Restore dialog box. 8. IzoT Commissioning Tool checks for user privileges.
Click Yes to restore the files; click No to skip restoring the files; or clear the Only Restore New Files check box, select one or both of the Overwrite Read-only Files and Overwrite more Recent Files check boxes, and click Yes. The overwrite options will replace existing files with backup versions. If you do not want to be prompted, in the Network Properties: Backup/Restore options category, you can set whether IzoT Commissioning Tool automatically installs the backup files in the Import and Types folders.
the drawing has been opened, click Add-ins, point to Synchronization, click Resynchronize, and follow steps 14–18. 14. The Synchronize OpenLNS CT Drawing dialog box opens. 15. Click Next to next to accept the default synchronization operation, which is Synchronize Network to Database (the option for recommissioning devices). The Choose Synchronization Scope dialog opens. 16. Click Next to accept the default synchronization scope (all the subsystems and drawing files in the network).
17. Select the state of the devices after they have been recommissioned. You have four choices: • Preserve Current State. The devices will be restored to the state they were in prior to being recommissioned. This is the default. • Offline. All devices will be left in the offline state. The behavior in the offline state depends on the device. A Neuron-hosted device, for example, will not run its application. You can set all device offline so that you can recommission the system incrementally.
19. This window displays the status of the resynchronization. Resynchronization events will be listed in the order they occur. Click OK when the resynchronization is complete. The resynchronization events, including any errors, are shown in the status pane and recorded in a log file (Resync.log). The resync log is stored in the drawing directory of the current IzoT Commissioning Tool network. Notes: • Recommissioning a device may temporarily interrupt its operation.
3. Verify that the recovered network opens to be correct. The recovery wizard logs the recovery tasks as well as any errors that occurred in the detailed recovery log. A trace log lists the steps, with the times and dates, that the wizard took to recover the database. You can view the logs after the database has been recovered. These logs are useful for tracking any errors that the recovery process encounters, such as connection errors or lost data. 4.
4. Click OK. You can update the recovery data in the physical devices in a network after setting the subsystem recovery options and after recovering a network. To update the recovery data, follow these steps: 1. Click Add-ins, point to Synchronization, and then click Resynchronize. The Synchronize OpenLNS CT Drawing dialog opens. 2.
3. Select the subsystems and drawing files to update. 4. Click Finish. The Synchronization Status dialog opens and IzoT Commissioning Tool begins updating the subsystem data in the devices within the specified network scope. 5. When the synchronization operation has been completed, click OK.
configuration property but different subsystem IDs, IzoT Commissioning Tool places the discovered devices in the subsystem path specified by the first valid SCPTlocation configuration property value discovered. IzoT Commissioning Tool then assigns the discovered devices the first subsystem ID value discovered. IzoT Commissioning Tool resolves any conflict that occurs in this scenario.
228 5. The Plug-In Registration dialog opens. Register or disable plug-ins as desired and click Next. 6. The Authentication dialog opens. If you use authentication on your network, select the Enable Authentication check box and click Set New Authentication Key. Enter the correct authentication key for your network (IzoT Commissioning Tool cannot recover your database without the authentication key). Click Next.
7. The Domain Definition dialog opens. If you know the domain ID of the network that you want to recover, enter it in hexadecimal format into the Domain ID box. If you do not know the domain ID, select the Recover Domain ID from Network Device check box. To recover a domain ID, you must have access to the service pin of an unauthenticated device that is on the same channel as the network interface. 8. Click Finish.
9. If you selected the Recover Domain ID from Network Device check box, the Service Pin dialog box opens. Press the service pin on one of the unauthenticated devices that are on the same channel as the network interface, and then click OK. 10. The OpenLNS Database Recovery Wizard opens. Click Next. 11. The What Would You Like To Do Now? dialog box opens. Click Recover a Network and click Next. 12. The Select LonManager Database dialog box opens.
13. The Recovery Options dialog box opens. If you expect your network to have more than 200 devices, select the Large Network check box. The Domain ID and Authentication Key boxes are read-only, as these settings are determined by the input from step 7. Click Next. 14. The Device Resource Files dialog box opens. Before proceeding, check if any LONMARK resource files are contained in directories not displayed in this dialog box.
15. The External Interface Files dialog box opens. Add or remove device templates based on device interface (XIF) files. When finished, click Next. 16. The Recovering dialog box opens. Click Next to begin the network recovery. The time of the recovery process depends on the size and complexity of the network. Throughout this process, messages will appear.
17. When the data recovery is complete, the Optimizing Database dialog box opens. Select the Organize Database check box and click Next. 18. Throughout this process numerous messages will appear. When the database organization is complete, a Congratulations dialog box opens. This dialog box displays the number of errors and warnings, and the number of devices, bindings, warnings, routers, and channels found.
19. If there are any errors or warnings, click Details to view the recovery log listing each recovery phase initiated and any problems encountered. Investigate any errors before you set the final network design OnNet. You can also research warnings, but they are not considered as serious as errors. Click Trace to view the trace log listing the steps taken by the OpenLNS Database Recovery Wizard to recover your network.
22. The Select Stencils dialog box opens. Add, remove, or re-order stencils. Click Finish 23. The Synchronization Status dialog box opens as the synchronization process begins. It then displays the progress of the synchronization. Once “Synchronization Complete” opens, click OK to open your IzoT Commissioning Tool network. 24. Verify that your OpenLNS CT drawing accurately represents the network.
25. Compare the recovered OpenLNS network database to your expected results. Because network recovery occurs while IzoT Commissioning Tool is OffNet, required changes to device configuration properties are stored in the OpenLNS network database instead of being propagated to the network. Once you have checked the recovered OpenLNS network database and validated your IzoT Commissioning Tool network design, change the management mode to OnNet.
• If a bound dedicated message tag does not have any targets, its address table entry is marked as empty and removed from the associated connection. • Any address table entries that are not associated with a network variable or message tag (source or target) are marked as empty. A lost source or a lost target may create this scenario. Group use counts are updated as necessary, and group IDs are freed as necessary.
While it is possible for multiple users to be modifying the same page of an OpenLNS CT drawing at the same time, if the users are working in the same subsystem, it is possible for one user to delete an IzoT Commissioning Tool object that the other user is trying to modify at the same time. As a result, multiple users will typically be more productive if they are working in different subsystems.
You can sort the IzoT Commissioning Tool event log by any of the column headers. To sort by a column header, click the header. Click the header again to toggle the order in which the data in that column is listed (ascending or descending). The columns contain the following data: Date/Time The date and time the event occurred. By default, the IzoT Commissioning Tool Event Log lists the changes by date/time in ascending order. Document The name of the document in which the change occurred.
To view the exported IzoT Commissioning Tool event log, find the XML file in C:\Users\Public\Documents\LonWorks\OpenLnsCt\XML\network name and double-click it. The file opens in your default XML viewing application, which is Internet Explorer unless you change it. You can also open the XML file from a text or XML editor or report generator. The exported XML version of the IzoT Commissioning Tool event log contains the following information for each log entry.
ObjectId The handle of the object that was modified. For events related to network variables and message tags, the object ID will be the index of their functional block. DeviceHandle The handle of the device in which the object is defined. This field only applies to events related to network variables, message tags, and functional blocks. NvHandle The index of the network variable in the device. This field only applies to events related to network variables.
3. Choose the synchronization operation(s) you want to perform by selecting the following options. OpenLNS Database The network database resynchronization options are only available if IzoT Commissioning Tool is running on the same computer as the OpenLNS Server. Validate OpenLNS Database Validates the structure of the OpenLNS network database. Validate and Repair OpenLNS Database Validates the structure of the OpenLNS network database and repairs the database if any errors are detected.
OpenLNS CT Drawing Synchronize Drawing to Database (fix-up Drawing) Updates the OpenLNS CT drawing to be consistent with the OpenLNS database. Synchronize Monitor Sets between Drawing and Database Updates the monitor sets in the OpenLNS CT drawing to be consistent with the OpenLNS database. A monitor set is a group of point definitions that IzoT Commissioning Tool uses to monitor and control network variables.
5. Select the scope of the selected synchronization operation(s) by choosing which subsystems and drawing files to resynchronize. If you know that the current subsystem is the only one needing resynchronization, resynchronize just that subsystem. If you aren’t sure which subsystem needs to resynchronized, resynchronize all subsystems. The same logic applies if your IzoT Commissioning Tool network contains multiple drawing files.
Otherwise, if you are synchronizing the network or the OpenLNS CT drawing to the network database, click Next and skip to step 10 in which the Synchronization Options dialog opens. If you are performing any other synchronization operation, click Finish to begin resynchronization. Skip to step 16 in which the Synchronization Status dialog opens. 7. If you are recommissioning devices, the Commissioning Options dialog box opens. Select the state of the devices after they have been recommissioned.
9. Select the following options and then click Next. Shapes All SmartShapes that have newer versions available than the ones currently in the drawing are listed. Select the SmartShapes to update. Items Select Menu to update the shortcut menus for the selected SmartShapes. Set Appearance to have the appearance of the SmartShapes updated. 10. The Synchronization Options dialog opens. 11. Select the options to be applied during the synchronization of the OpenLNS CT drawing to the network database.
during Resync network during resynchronization. This speeds up resynchronization, as it reduces the time Visio spends updating the drawings. Check for Connections for Missing FB Shapes Enables IzoT Commissioning Tool to check for connections to functional blocks that are in the network database but are not represented by functional block SmartShapes in the OpenLNS CT drawing. Subsystem to Visio Document Assignment Select in which Visio drawing file to place the subsystems in your network.
15. Specify the stencils that will be scanned for master SmartShapes during resynchronization. When objects are found within the OpenLNS network database that are not already represented in the drawing, IzoT Commissioning Tool scans the listed stencils and automatically adds the appropriate SmartShape to the drawing. If the object’s particular master SmartShape is not found, an appropriate generic master SmartShape (e.g., a LONWORKS Device SmartShape) will be used.
The resync log is stored in the drawing directory of the current IzoT Commissioning Tool network design. 17. If the OpenLNS CT drawing is being synchronized to match the network database and the Automatically Drop Device, FB, and Subsystem Shapes check box was cleared, the Missing Shape dialog opens for each object in the network database that is not represented in the OpenLNS CT drawing. a. Click OK. The Missing Shape dialog closes and you are returned to the OpenLNS CT drawing. b.
single network using a portable network server under a sequential network installation scenario, in which no permanent server is needed. In most cases, however, it may be easier (if not necessary) to install each floor as a separate network. Once the entire site has connectivity, the individual floor networks can be merged into a single network representing the high rise. To support these scenarios, IzoT Commissioning Tool provides the ability to merge IzoT Commissioning Tool networks.
• Unreferenced connection descriptions. Connection descriptions that have been created but do not have any corresponding connections are not created in the destination network. • User profiles. User profiles in the source network are not created in the destination network. • Non IzoT Commissioning Tool extension records.
The merge export utility also automatically decommissions all configured devices in the network that use authenticated message service so that they can be recommissioned in the new network. Select the Decommission Unauthenticated Devices check box to decommission all the configured devices in the network. 5. Click Finish to prepare the IzoT Commissioning Tool network design for merging. The IzoT Commissioning Tool Database Merge Export Status dialog opens.
12. Select the source network you exported in steps 4 – 6 from the Select Network to be Merged list. This list contains only those networks that have been exported using the Merge Export Utility. 13. Enter a name for the root subsystem of the source network in the Name to Be Assigned box. 14. Click Finish to begin the network merge. The source network and its underlying subsystem hierarchy will be added as a new subsystem.
This dialog displays the status of the network merge and lists the events in the order they occur. Any errors encountered are shown in the status pane, and they are also available in a log file for the network merge. The log file is named Merge_.log. The merge log is stored in the drawing directory of the destination network. 15.
8 Managing Networks This chapter explains how to test and verify application devices, functional blocks, and routers. It also describes IzoT Commissioning Tool styles, and it details how to generate device status summary reports, network resource reports, and OpenLNS network reports.
Using the IzoT Commissioning Tool Device Manager You can manage application devices, functional blocks, and routers using the IzoT Commissioning Tool Device Manager. You can switch between performing management tasks and making changes in your OpenLNS CT drawing without having to close the IzoT Commissioning Tool Device Manager.
Managing Devices To manage a device, right-click a device (or select multiple objects including at least one application device or functional block and right-click one of them), and then select Manage on the shortcut menu. You can also select the Devices tab after you have opened one of the other tabs with one or more application devices or functional blocks selected. The Devices tab of the IzoT Commissioning Tool Device Manager opens. You can use this tab to manage the selected application devices.
network variable values or send network variable updates. If the device was previously offline, the device state does not change. If the device is reset while offline, it will be placed in the online state. Enable Activates all functional blocks on a disabled device. The device must be online to be enabled. This command only applies to devices containing a Node Object functional block. Disable Keeps the device application disabled even if the device is reset. The device must be online to be disabled.
The commands in this dialog require that the device application associated with the functional block includes a Node Object functional block and that the device is online. Click one or more functional blocks in the Object List and then click any of the following buttons: Test Tests the functional block to ensure that it is operating correctly. The tests run are determined by the options set in the Device Manager Settings dialog, which you can open by clicking Settings.
Managing Routers To manage a router, right-click a router (or select multiple objects including at least one router and right-click one of them), and then and select Manage on the shortcut menu. You can also select the Routers tab after you have opened one of the other tabs with one or more routers selected. The Routers tab of the IzoT Commissioning Tool Device Manager opens. You can use this tab to manage the selected routers.
Click Settings to open the Device Manager Settings dialog box. There, you can set options for testing routers and options for the results log. Device Manager Settings You can customize the error reporting, testing, and winking operations performed by the IzoT Commissioning Tool Device Manager. To customize these setting, click the Settings button on any of the tabs in the Device Manager. The Device Manager Settings dialog opens. Set the following options and then click OK to apply any changes.
Repetition Control Repeat Number of Times Specifies how many times a Wink or Test command will be repeated. The default is 1, which means that these commands are not repeated. If you enter a value greater that 1 in this box, you must enter a non-zero value in the Wait Between Operations box. Wait Between Operations Specifies how many seconds the IzoT Commissioning Tool Device Manager waits between repeating a Wink or Test command when the number in the Repeat Number of Times box is greater than 1.
Error Red diagonal Changes have been made in the network database, but an error has occurred while updating the device. The device may not be responding properly, a router or channel between the OpenLNS Server and the device may have failed, or a physical connection may be faulty. If IzoT Commissioning Tool is OnNet, the OpenLNS Server periodically tries to update the device. Once the device has been updated to match the network database, the device style changes to Normal.
Normal Solid cyan. The functional block is in a normal state and none of the states listed above are active. When multiple functional blocks states are concurrently active, the style displayed is based on the order of the states listed above. For example, a functional block in the normal state that is disabled and placed in override mode will be crosshatched yellow, indicating the disabled state (disabled is the highest-order state of the three).
Network Variable and Message Tag SmartShape Styles IzoT Commissioning Tool indicates the state of network variable and message tag SmartShapes using the following styles: Connection Point State Default Style Description Connection Point Normal Solid black fill The network variable or message tag SmartShape is normal (not currently exported to a supernode). Connection Point Exported Solid blue fill The network variable or message tag SmartShape has been exported to one or more supernodes.
Monitoring Enabled Text is black. Monitoring Disabled Text is magenta. IzoT Commissioning Tool updates the style of the connection SmartShapes, as required, if changes are made to the connections that affect the service type used.
3. • Select Subsystem Page to include the application devices, routers, and functional blocks in the current subsystem. This is the default. • Select Subsystem Hierarchy to include the application devices, routers, and functional blocks in the current subsystem and subsystems nested in it. • Select Entire Network to include all the application devices, routers, and functional blocks in the current IzoT Commissioning Tool network.
268 4. Select additional functional blocks to include in the status summary based on the type of errors or exceptions they have reported. For more information on the status items themselves, refer to hardware manuals or LONMARK documentation. 5. Click Next. The Device Status Summary Results dialog opens. This dialog displays the status of devices, routers, and specified functional block types within the scope specified in the Device Status Summary Options dialog.
For functional blocks, this dialog displays the following data in the top pane: subsystem, device, functional block name, applicable status (indicated by "YES"), and any comments about the functional block. For application devices and routers, this dialog displays the following data in the bottom pane: subsystem, device name, state, and any comments about the device or router. 7. To save the status summary to a text file (.txt extension), click Save As.
Alias Table Summary You can display a summary of the usage and availability of alias table entries for a device. The usage and availability is displayed in a ToolTip for a device. The device SmartShape ToolTip lists the total number of network variable aliases for the device, and the number of aliases currently available.
IzoT Commissioning Tool User’s Guide 271
9 Exporting and Importing Networks with XML This chapter describes how to export a LONWORKS network to a LONWORKS network XML file, view a LONWORKS network XML file in a web browser, edit a LONWORKS network XML file, and import a LONWORKS network XML file to update a network.
Using XML Export/Import Overview You can speed up your network design and ensure your devices are configured correctly by creating an IzoT Commissioning Tool network report or by creating a custom IzoT Commissioning Tool user interface. IzoT Commissioning Tool includes an IzoT Commissioning Tool XML plug-in that you can use to export all the devices, connections, network variables, and configuration properties within all or a part of an IzoT Commissioning Tool network design to a LONWORKS network XML file.
Programmer’s Guide for details on how applications can use the plug-in and the schema used for the XML file. To manually export your OpenLNS CT drawing to a LONWORKS network XML file, follow these steps. 1. Click Add-ins, point to IzoT Commissioning Tool Documents, and then click Export to XML. The XML Export Options dialog box opens. 2. Set the following options to select the data to be included in the XML file: Export Scope Select the portion of the network to be included in the XML file.
Report Self-Documentation Includes the self-documentation data for all exported devices and their network variables. This option is unavailable if the IzoT Commissioning Tool computer is not attached to the physical network. This option can add significant processing time to the export if there are many network variables within the export scope. Report Device Specific CP Values Includes the values of all device-specific configuration properties.
1. Generate a LONWORKS network XML file. 2. Clear the Exclude XSLT Stylesheet check box in the XML Export Options dialog box. 3. Optionally modify the LONWORKS network XML file directly or with another application. 4. Either open the IzoT Commissioning Tool XML file from Internet Explorer, or open the folder containing the IzoT Commissioning Tool XML file and double-click the file (Internet Explorer must be your default Web browser for this method to work).
Click a device link to open a page with detailed data on that device and a table listing its functional blocks, with links to view detailed data on each one. Click a functional block link to open a page with detailed data on that functional block and a table listing its network variables and configuration properties, with links to view detailed data on each one.
You can continue moving down the network hierarchy until reaching the end, which is at the network variable\configuration property or configuration property paths. Click Up to go back one level in the network hierarchy, or click Root to return to the main network page.
2. Set the following options: Import to Subsystem Select the root subsystem for the XML file. There are two choices: • As Defined in XML File. Imports the XML file into the subsystem specified in the XML file. • Select Subsystem. Imports the XML file into the subsystem you specify. By default, the top-level root subsystem will be selected. To change the subsystem, click Browse. Input File Name Specifies the name of the XML file to import.
10 Managing IzoT Commissioning Tool Licenses This chapter provides an overview of IzoT Commissioning Tool licensing. It describes how to upgrade IzoT Commissioning Tool, upgrade an IzoT Commissioning Tool Standard Edition to the Professional Edition, renew your IzoT Commissioning Tool annual maintenance, and transfer an IzoT Commissioning Tool license.
Commissioning Devices with IzoT Commissioning Tool IzoT Commissioning Tool lets you install devices without commissioning fees (known as “credits” in LonMaker Turbo Editions and previous versions of the LonMaker software). IzoT Commissioning Tool features no-cost installation for all LONWORKS devices that comply with the ISO/IEC 14908-1 Control Network Protocol.
2. The License Wizard guides you through the process of manually updating or upgrading your IzoT Commissioning Tool license. Click Next. 3. The Step 1: What would you like to do? dialog opens. 4. To update or upgrade your IzoT Commissioning Tool software using the over the Internet or via e-mail, click Activate Product Licenses and then click Next. To upgrade over the phone, click Show Advanced Tasks, Upgrade a Product License over the Phone, and then follow the instructions in the License Wizard.
284 6. Select Upgrade from the Action list for both OpenLNS Server and IzoT Commissioning Tool, and then click Next. 7. If your computer is online, the Step 3: Status dialog opens, and the License Server upgrades OpenLNS Server and IzoT Commissioning Tool. If your computer is offline, the Step 3: Where Would You Like to Save your License Requests? dialog opens.
8. In the Request File Name property, enter a full path where a license request file (.elwrq extension) is to be saved, or click Browse, specify the directory where the license request file is to be saved, and then enter a name for the file. Under Authentication Details, enter the Echelon ID (e-mail address) and Password you created for your Echelon download account. The Activation Key box displays the 25-character alphanumeric string for the Echelon product to be upgraded. Do not modify this property.
10. Click Send Request to Echelon to e-mail the license request file to Echelon at activation@echelon.com. Echelon will send you an e-mail message with a license response (.elwrs extension) file. You can upgrade your license faster by copying the license request file to an Internet-connected computer with the License Wizard installed on it and importing it into the License Wizard. The License Wizard creates the license response file, which you can then copy to the original computer. 11.
d. The Check License Response File dialog opens. Confirm that the Echelon product licenses in the license response file are the ones you want to activate. Click Next. The License Server installs and upgrades the licenses in the license response file. e. The Status dialog opens and confirms that the OpenLNS Server and IzoT Commissioning Tool licenses have been successfully upgraded.
12. Click Exit to close the License Wizard. Upgrading IzoT Commissioning Tool Standard Edition to IzoT Commissioning Tool Professional Edition You can upgrade a copy of IzoT Commissioning Tool Standard Edition to IzoT Commissioning Tool Professional Edition if you need support for more networks. The Standard Edition supports up to five networks and the Professional Edition supports an unlimited number of networks.
d. If your computer is online, the Step 3: Enter Customer Information dialog opens. Complete the following steps to return your software (if your computer is offline, proceed to step e): • Enter the User ID (e-mail address) and Password you created for your Echelon download account. If you do not have an Echelon download account, click the Sign Up for a New Account link, and create one on the Echelon Web site. If you forgot your password, you can retrieve it by clicking the Forgot your Password link.
• The Step 4: Status dialog opens, and the License Server returns your IzoT Commissioning Tool Standard license. • Click Exit to close the License Wizard. e. If your computer is offline, the Step 3: Where Would You Like to Save your License Requests? dialog opens. f. In the Request File Name property, enter a full path where a license request file (.
Click Next. g. The Step 4: Status dialog opens. The License Wizard confirms the creation of the license request file. h. Click Send Request to Echelon to e-mail the license request file to Echelon at activation@echelon.com. Echelon will send you an e-mail message with a license response (.elwrs extension) file. You can upgrade your license faster by copying the license request file to an Internet-connected computer with the License Wizard installed on it and importing it into the License Wizard.
Commissioning Tool computer without losing your license. You cannot use the License Wizard to install one IzoT Commissioning Tool license on multiple computers. To transfer your IzoT Commissioning Tool license, follow these steps: 1. On the source computer, return the IzoT Commissioning Tool license following these steps: a. Open the Echelon License Wizard. Click Start, click Programs, point to Echelon License Wizard, and then click License Wizard. The Echelon License Wizard opens. Click Next. b.
the target computer by e-mailing the license request file to Echelon at activation@echelon.com, or by copying it to the target computer (if it has an Internet connection) and importing it into the License Wizard. e. 2. Your OpenLNS Server and IzoT Commissioning Tool licenses are returned to the Echelon License Server. The Step 4: Status dialog opens and report the results of the license return.
11 Using Plug-ins This chapter provides an overview of plug-ins and then describes how to start a plug-in, get plug-in information, and re-register, enable, and disable plug-ins.
Using Plug-ins Overview Plug-ins are applications that you can start from within IzoT Commissioning Tool to perform a specialized task, often relating to a specific type of device or functional block. Device manufacturers may provide plug-ins that you can use with IzoT Commissioning Tool to configure their devices. Any plug-in conforming to the OpenLNS plug-in guidelines may be used with IzoT Commissioning Tool. You can view and download free Echelon and third-party plug-ins at www.echelon.com/plugins.
• To start a plug-in using a default command, right click a device or functional block SmartShape, and then select Configure or Browse. If a plug-in is registered for the selected command and functional block type, the plug-in window opens. You can display information about the plug-in commands that are installed on your computer and registered for the network, and which commands are default commands, as described in Getting Plug-in Information.
Viewing Plug-in Information You can perform the following operations for registered plug-ins: • • • • • View general information about the selected plug-in. Disable the plug-in. Set whether the plug-in is the default for a given command. Select whether the plug-in is pre-launched for commands that invoke it. View whether the plug-in supports multiple objects and single instance use.
Commissioning Tool does not change the attribute on any other plug-ins. If multiple plug-ins are registered for the same command and object class, the plug-in with this check box selected will be the one invoked. If multiple plug-ins have this check box selected, IzoT Commissioning Tool invokes the first plug-in that it finds with this option set. Prelaunch Keeps one instance of the plug-in program active (if registered) so that it is immediately available for commands that invoke it.
The columns contain the following data. You can sort the data by clicking a column header. Click a header again to toggle the order (ascending or descending) in which the data in that column opens. Server Name The registered ActiveX name for the plug-in. Multi-Object Whether the plug-in supports multiple objects simultaneously. Single Instance Whether the plug-in supports using a single instance of the plug-in when it is requested for the same object multiple times.
Follow these steps to register or re-register a plug-in: 1. Choose the plug-in to register from the Already Registered or the Not Registered list. You can register all the plug-ins listed under these lists by clicking the category label. 2. Click Register. The plug-in or plug-ins are added to the Pending list (they also remain under their existing lists), and their status, “[Register]”, is indicated. 3. Once you have chosen all the plug-ins to register or re-register, click Apply.
Enabling a Plug-in To enable a plug-in, follow these steps: 1. Select the plug-in under the Disabled list. You can enable all of the disabled plug-ins by clicking the category label. 2. Click Enable. The selected plug-in or plug-ins are added to the Pending list (they also remain under their existing categories), and their pending status, “[Enable]”, is indicated. 3. Click Apply to enable the selected plug-in or plug-ins. 4.
12 Creating and Using Custom Commissioning Tool SmartShapes and Stencils This chapter describes IzoT Commissioning Tool stencils and the process to create them; creating and using custom master SmartShapes for devices, functional blocks, subsystems, and connections; using additional user cells for devices, functional blocks, and routers; and setting user-defined functional block modes and types.
IzoT Commissioning Tool Stencils IzoT Commissioning Tool uses Visio stencils to speed your LONWORKS network engineering. A stencil is a collection of master SmartShapes (also called masters) that you can easily reuse in your drawings. To add a master SmartShape to your drawing, you drag the master SmartShape from the stencil to your drawing. IzoT Commissioning Tool includes LONWORKS specific master SmartShapes called IzoT Commissioning Tool SmartShapes.
4. Right-click the title bar of the new stencil and then click Save on the shortcut menu. Select a folder, assign a name for the stencil file, and click Save. Save the stencil to the LonWorks\LonMaker\Visio directory (by default, C:\Program Files\LonWorks\LonMaker\Visio [32-bit system] or C:\Program Files (x86)\LonWorks\LonMaker\Visio [64-bit system]) to easily access it with the open stencil ( ) button, or save the stencil to the drawing folder for simplified backup.
section. Do not hold down CTRL and drag or use copy/paste between drawings from different networks. Using Custom IzoT Commissioning Tool Master SmartShapes You can reuse a custom IzoT Commissioning Tool SmartShape that you create (see Creating Custom IzoT Commissioning Tool Master SmartShapes). The custom IzoT Commissioning Tool master SmartShape may contain any number of the standard IzoT Commissioning Tool SmartShapes described in Designing IzoT Commissioning Tool Networks.
Commissioning Tool gives the new device template the name specified in the device SmartShape, and associates it with the device SmartShape. 4. If IzoT Commissioning Tool does not find a device template or device interface file in steps 1 through 3, it prompts you to select an existing device template or to define a new device template by importing a device interface file. The resulting device template is associated with the device SmartShape.
For each channel listed, click anywhere in the Method field and then select how the channel is to be defined when the subsystem or supernode master SmartShape is added to your OpenLNS CT drawing. You have four choices: • Prompt User. The Channel Definition dialog box will appear, enabling you to select whether the channel represents a new or an existing channel. This is the default. • Automatic.
SmartShape can represent several connections in your OpenLNS CT drawing, allowing you to quickly and easily establish multiple network connections with one operation. You can use connection master SmartShapes to do the following: • Specify a connection with a connection description other than the default connection description. A connection description is a set of properties that apply to a connection, such as protocol service, retry count, priority, and authentication.
If you drag this master SmartShape to any subsystem in the same network, IzoT Commissioning Tool creates two new functional blocks, and adds their outputs to the same Alarm connection for the Central Monitoring Station. If you also include the Central Monitoring Station in the master SmartShape, IzoT Commissioning Tool creates three new functional blocks and a new reference connection when you drag the master SmartShape to a drawing.
4. Every IzoT Commissioning Tool SmartShape has an IzoT Commissioning Tool ShapeType user cell. The value of this cell specifies the IzoT Commissioning Tool SmartShape type. You are most likely to use the DEVICE (LonMakerShapeType 4), FUNCTIONAL_BLOCK (type 5), and FB_NAME (type 13) SmartShape types. 5. You can use the FB_NAME value to include a functional block within a group that may include other functional block SmartShapes.
• A value of 0 indicates no. • A value of 1 indicates yes. • A value of 2 indicates that the IzoT Commissioning Tool user will be prompted. The default value is 2 to prompt the user. ChanTypeList A semicolon-separated list of valid channel type IDs for the device. A value of -1 in the list indicates that the user has the option of selecting from all channels in addition to the channels of the specific types defined. Channel type IDs correspond to the ChannelTypeNumber values contained in the StdXcvr.
The scope selector definitions are: 0 Standard functional profile defined in the standard resource file set. 3 User-defined functional profile, defined in a manufacturer-specific resource file set. 4 User-defined functional profile, defined in a manufacturer and device class specific resource file set. 5 User-defined functional profile, defined in a manufacturer and device class/subclass specific resource file set.
Property to Subsystem ID check box in the Network Properties: Recovery options category. NewAdvPropCap NewPropCap NonGrpRcvTimer NxeName Specifies handling of the advanced properties dialog in the new device wizard. • A value of 0 specifies that the advanced properties dialog is not to be displayed. • A value of 1 indicates that the advanced properties dialog is to be displayed, but cannot be modified.
ObjStateStyle Specifies whether the coloring style is applied to the SmartShape’s fill, line, text, or a combination of the three. • A value of 1 indicates that the style applies to the SmartShape’s lines. • A value of 2 indicates that the value applies to the SmartShape’s fill. • A value of 4 indicates that the style applies to the SmartShape’s text. You can add values together to specify combinations.
not specified here, the IzoT Commissioning Tool user may be prompted for a device interface when the device master SmartShape is dragged to the to the OpenLNS CT drawing, depending on the ProgramId and TmplName values. Additional Functional Block User Cells You can include the following additional user cells in a functional block SmartShape. Not every functional block has all of these cells, but you can add any of them by right-clicking an existing user-defined cell and selecting Insert Row.
information. Additional Router SmartShape User Cells You can include the following additional user cells in a router SmartShape. Not every router has all of these cells, but you can add them by right-clicking an existing user-defined cell and selecting Insert Row. Class Specifies the type of router. Valid values are as follows: 0 1 2 3 4 5 Configured router Learning router Repeater Bridge Permanent Repeater Permanent Bridge The default and recommended value is 0 for a configured router.
3. Drag the generic Device SmartShape ( 4. Open the Edit menu and then click Open Device. The Group window opens for the device. 5. Open the Insert menu, point to Picture, and then click From File. Select a bitmap file. Position the bitmap on the device as desired. Close the Group window. 6. Click the bitmap, open the Format menu, and then click Behavior. Clear the three check boxes under the Selection Highlighting box. 7. Open the Windows menu and then click Show ShapeSheet. The ShapeSheet opens.
Appendix A Setting IzoT Commissioning Tool Default Options This appendix documents the IzoT Commissioning Tool Default Options you can set either in the IzoT Commissioning Tool Design Manager or in your OpenLNS CT drawing.
Setting IzoT Commissioning Tool Default Options You can set IzoT Commissioning Tool Default Options either in the IzoT Commissioning Tool Design Manager or in your OpenLNS CT drawing. For new networks, you can set the default options in the Default IzoT Commissioning Tool Options tab in the IzoT Commissioning Tool Design Manger. For an existing network, you can set them in the OpenLNS CT drawing by clicking Add-ins, pointing to IzoT Commissioning Tool, and then clicking IzoT Commissioning Tool Options.
You can click Restore Defaults to reset all the options and values in the currently displayed options category to their defaults. Every default IzoT Commissioning Tool option has one of the following three scopes that determine which networks and IzoT Commissioning Tool computers are updated when you change the value of an option: • Current network, current IzoT Commissioning Tool computer. Value is updated in the network on the IzoT Commissioning Tool computer in which the change was made.
files in the LONWORKS Import folder when creating an IzoT Commissioning Tool backup file. This option is selected by default. If selected, a new Import folder will be inserted in the network database directory, and all the files in the LONWORKS Import folder (even those files that are not resource files or are not used in the OpenLNS CT drawing) will be copied into that new Import folder prior to creating the IzoT Commissioning Tool backup.
OpenLNS backup file is created. If the Delete OpenLNS Hot Backup after LM Backup check box is cleared, the OpenLNS hot backup copies are preserved. Select a value between 1 and 99. The default value is 5. Scope: All networks, current IzoT Commissioning Tool computer Auto Save Intervals Drawing Save Sets how frequently (in minutes) the OpenLNS CT drawing (.VSD) file is automatically saved. The default value is 60 minutes. To disable this feature, set the interval to 0.
Restore New Files check box is selected. Scope: All networks, current IzoT Commissioning Tool computer Only Restore New Files Automatically restores unique backup device application, device interface, and resource files. Backup files with the same name as an existing version will not be installed.
Configuration Properties Options The Configuration Properties category contains the following options. Enable Configuration Properties Enables access to configuration properties. This option is selected by default. Also enables automatic extension record copying. When this check box is selected, a device’s extension records that are marked for copying will automatically be copied when you create a new device by copying an existing one and when you create a new custom device master SmartShape.
Copy Values on Functional Block Copy Copies CP values when creating a new functional block from a master SmartShape or from another functional block. This check box is only available if the Enable Configuration Properties check box has been selected, and it is selected by default.
Device Options The Device category contains the following options. Device Options XIF Search Path Specifies the path that IzoT Commissioning Tool uses to search for device interface (XIF) files. You can enter multiple directories by separating them with semicolons. Scope: All networks, current IzoT Commissioning Tool computer NXE/APB Search Path Specifies the path that IzoT Commissioning Tool uses to search for device application files (.NXE and .APB extensions).
selected using the preceding criteria, the Device Wizard will appear. Scope: All networks, current IzoT Commissioning Tool computer Prompt for Device State During Commissioning Remove Unreferenced Device Templates Includes the window in the Commissioning Device Wizard for setting the initial state of application device/router applications and the source of device configuration property values. This option is selected by default. If this check box is cleared, this window will be skipped.
application may continue to function. Scope: Current network, all IzoT Commissioning Tool computers Routers Specifies the initial state of a new router after it has been commissioned. You have two choices: • Online. The router will forward packets between the channels connected to it. Use this setting to ensure routers are operational as they are commissioned. This is the default. • Offline. The router will not forward packets between the channels connected to it.
The Functional Block category contains the following options. Functional Block Options Enable Automatic Device Selection Automatically assigns the appropriate device to a new functional block SmartShape, thereby skipping the Functional Block wizard. This option is cleared by default. The functional block SmartShape must contain a functional block type specification for this feature to work.
whether to delete the dynamic network variable. Scope: All networks, current IzoT Commissioning Tool computer Delete Dynamic NV when NV SmartShape is Deleted Deletes a dynamic network variable from a device when its network variable SmartShape is deleted from a functional block SmartShape. You have three choices: • No. The dynamic network variable is not deleted. • Yes. The dynamic network variable is automatically deleted. • Ask.
variable SmartShapes to which they are connected. The default reference SmartShape spacing value is 1.1. Scope: Current network, current IzoT Commissioning Tool computer General Options The General category contains the following options. Confirm Deletes Prompts you to confirm the deleting of an IzoT Commissioning Tool SmartShape. This option is selected by default.
The IzoT Commissioning Tool tracing output is saved in a file called trace.log, which is stored in the C:\Users\Public\Documents\LonWorks\OpenLnsCt\ \Drawings\ folder. Scope: Current network, current IzoT Commissioning Tool computer Enable Monitoring Enables connection monitoring and data point monitoring. Clear this check box to disable all NV polling by IzoT Commissioning Tool. This check box does not affect the OpenLNS CT Browser. This option is selected by default.
The OpenLNS Event category contains the following options. The changes you make in the OpenLNS Events options category are all applied to the current network on your computer. Device/router Commission and Attachment Events Device Interface Change Events Connection Change Events Device/router Change Events Subsystem Change Events Device Template Change Events Updates the OpenLNS CT drawing when devices or routers are attached to the network, detached, commissioned, or decommissioned.
Channel Change Events Updates the OpenLNS CT drawing when channels are added, removed, or modified. This option is selected by default. Scope: Current network, current IzoT Commissioning Tool computer Naming Options The Naming category contains the following options. The changes you make in the Naming options category are applied to the current network on your computer. Naming Options Controls how IzoT Commissioning Tool constructs a unique name for new IzoT Commissioning Tool SmartShapes.
Name/instance ID Separator Character Selects the character to be inserted between the IzoT Commissioning Tool SmartShape name and the instance ID. The choices are Space ( ), Underscore (_), Dash (-), Exclamation Point (!), and Hash (#). The default separator character is Space ( ). For example, the default name of the first analog input (AI-) LonPoint device added to your OpenLNS CT drawing with a space ( ) selected as the separator character is AI- 1.
Network Explorer Options The Network Explorer is an auto-hide window that displays a hierarchal view of the OpenLNS CT drawing. You can use the Network Explorer to navigate, view, and modify the subsystems, devices, and device templates in your network design. The Network Explorer category contains the following options. The changes you make in the Network Explorer options category are applied to all networks on your computer.
• Subsystems, Devices, FBs, and NVs. Lists the subsystems, devices, functional blocks, and network variables in the IzoT Commissioning Tool network. Scope: All networks, current IzoT Commissioning Tool computer NV Browser/Monitoring Options The NV Browser/Monitoring category contains the following options. NV Browser/Monitoring Options Catalog Directory Specifies the directory containing resource files (.TYP, .FMT, .FPT, and language files). The default directory is LONWORKS\Types.
to correlate a lightweight client to its monitor sets. By default, this tag is the computer’s Windows network name. If you have existing monitor sets and you change this tag, the existing monitor sets can no longer connect to the lightweight client. To remove the monitor sets, use the Remove Monitor Sets command from the Network Service Devices command on the IzoT Commissioning Tool menu.
The IzoT Commissioning Tool Font category contains the following options. IzoT Commissioning Tool Font Name Displays the name of the current IzoT Commissioning Tool font. The default value is Arial. Scope: Current network, current IzoT Commissioning Tool computer Size Displays the size of the current IzoT Commissioning Tool font. The default value is 8 points.
Recovery Options The Recovery options category lets you store and automatically update subsystem data in application devices and routers. This is useful in the event you need to recover your OpenLNS network database from the network. Setting these options enables IzoT Commissioning Tool to use the saved subsystem data to place application devices and routers in their correct subsystems.
OpenLNS CT Drawing dialog. This check box is cleared by default. If an application device and its functional blocks span multiple subsystems, IzoT Commissioning Tool will use the subsystem path in which the application device SmartShape is located. If IzoT Commissioning Tool cannot locate the applicable SCPTlocation configuration property in an application device, the subsystem path will not be stored in the device.
Service Pin Options You can set options for using the service pin when commissioning a device. Show Service Pin Data Displays the service pin data received by IzoT Commissioning Tool when you press the device’s service pin. This option is cleared by default. You can change this option when you commission a device or router in the Commission Device/Router Wizard.
Clear this check box if the network includes any logical repeaters. Scope: Current network, all IzoT Commissioning Tool computers Shape ToolTips Options You can enable a ToolTip to appear when the mouse pointer is over an IzoT Commissioning Tool SmartShape in your OpenLNS CT drawing and select the type of data that opens in the ToolTip.
Synchronization Options The Synchronization category contains the following options. Automatic Update Interval (Seconds) Maximum Log Entries per Drawing File Sets how frequently (in seconds) an IzoT Commissioning Tool client checks the IzoT Commissioning Tool Event Log and updates its copy of an OpenLNS CT drawing to incorporate any changes made by other clients. The default automatic update interval is 10 seconds. Set the interval to 0 to disable automatic updates.
Warnings Options The Warnings category contains the following options, which are all selected by default. Enable Warning When New Device Requires Commissioning Enable Warning When Functional Block has no Matching Device Displays a message when you create a new device that needs to be commissioned. Scope: Current network, current IzoT Commissioning Tool computer Displays a message when you drag a functional block SmartShape onto a drawing but there is no compatible device on the drawing page.
LonMaker Release 3, or if you are switching between a fast OpenLNS network interface (layer 2) and an OpenLNS network interface (layer 5). If you attempt to do either of these, IzoT Commissioning Tool will ask whether to upgrade the NSD. For best performance, perform the upgrade. If you are only temporarily using a different network interface, you may choose not to upgrade. In this case, communication with physical devices is limited until you reopen the network with the original network interface.
Appendix B Glossary This appendix provides definitions for terms commonly used with IzoT Commissioning Tool.
Glossary Acknowledged Service A service of the ISO/IEC 14908-1 Control Network Protocol that ensures a message was received by the addressee(s). After a configurable number of retries, failures are logged in a status register in the device, which can be accessed by network management tools. Actuator Any component that affects a physical variable of a system under control or indicates the values of system variables for human operators.
or, for Neuron-hosted devices, you may load it into the device from application files (.nld, .apb, and .nxe extensions) using IzoT Commissioning Tool. The application program interfaces with the ISO/IEC 14908-1 protocol stack to communicate over the network. It may reside completely in the Smart Transceiver or Neuron Chip, or it may reside on an attached host processor (in a host-based device). Applicationless A state a device enters when it has determined that it does not have a valid application image.
Channel Segment A portion of a channel. A single segment can be comprised of multiple sections connected by physical layer repeaters. Channel Type Channels are categorized into channel types, which are characterized by the device transceiver. Common channel types include the following: TP/FT-10 (ISO/IEC 14908-3 twisted pair free topology channel), TP/XF-1250 (high-speed twisted pair channel), PL-20 (ISO/IEC 14908-2 power line channel), FO-20 (ANSI/CEA-709.
Control Network Protocol (CNP) A communication protocol standard for control networks defined by the ISO/IEC 14908-1 standard. The CNP provides a standard method for devices on a LONWORKS network to exchange data. The CNP defines the format of the messages being transmitted between devices, and it defines the actions expected when one device sends a message to another. The protocol normally takes the form of embedded software or firmware code in each device on the network.
Device Template A device template contains all the attributes of a given device type, such as its functional blocks, network variables, and configuration properties. You can create a device template by importing a device interface (XIF) file supplied by the device manufacturer, or by uploading the device interface definition from the physical device. A device template is identified by its name and its program ID.
Dynamic Network Variable A network variable that is added to a functional block after the device has been commissioned. Devices that support dynamic network variables include controllers and gateways with dynamic interfaces. Engineered System Scenario A control network installation scenario in which configuration data is collected into the network database when the system is being designed with IzoT Commissioning Tool and downloaded into the physical devices when the network is installed.
Group Addressing A logical addressing mode in the ISO/IEC 14908-1 Control Network Protocol that allows a message to be sent simultaneously to a pre-configured group of devices. Each group has an 8-bit group ID. Each domain can have up to 256 groups defined. Host A device implementing layer 7 of the ISO/IEC 14908-1 Control Network Protocol. A host may be based on a Smart Transceiver or Neuron Chip, in which case it is called a Neuron hosted device.
IP-852 Network Interface Software that enables IP-852 devices such as OpenLNS Server computers, IzoT Commissioning Tool computers, IP-852 routers, and native IP-852 devices to be attached to an IP-852 channel. An IP-852 network interface requires that the IP-852 Configuration Server be configured before trying to communicate with remote devices or remote computers. IP-852 routers include the SmartServer, i.LON 100 Internet Server, and i.LON 600 IP-852 Router.
Local Client An IzoT Commissioning Tool computer that is also running the OpenLNS Server. LonMark International A global membership organization created to promote and advance the business of efficient and effective integration of open, multi-vendor control systems utilizing ISO/IEC 14908-1 and related standards.
• Configuring the various Control Network Protocol parameters in each device for the desired features and performance, including channel bit rate, acknowledgement, authentication, priority service, etc. Network Explorer An auto-hide window that displays a hierarchical view of your IzoT Commissioning Tool network and supports all of the commands available within the drawing pages. The Network Explorer can be used in an OpenLNS CT drawing as a navigational tool or as a network management tool.
format also specifies how data entered by a user or application is translated to the raw data to be transmitted on a LONWORKS network. Network Variable/Configuration Property Types A network variable or configuration property type defines the structure and contents of the object. A network variable type can be either a standard network variable type (SNVT) or a user-defined network variable type (UNVT).
OffNet A network management mode in which network configuration changes are stored in the OpenLNS network database, but not propagated to the devices on the network. To send the changes to the devices, you place IzoT Commissioning Tool OnNet. If IzoT Commissioning Tool is OffNet and attached to the network, you can still read and write network variables, and read configuration properties.
OpenLNS Event An action fired by an OpenLNS Server to notify an OpenLNS client application of a change to the OpenLNS network. IzoT Commissioning Tool uses OpenLNS events to keep it synchronized with other OpenLNS applications or plug-ins that are making changes to the network database. OpenLNS Network Database A database (also referred to as the network database), which includes the network and device configuration data for the devices in a LONWORKS network.
Priority An ISO/IEC 14908-1 Control Network Protocol service for messages sent from LONWORKS devices that allow a message priority access to a channel. Priority traffic is delivered before other traffic. Priority is a resource of the channel. Protocol Analyzer A tool that can read every packet on a LONWORKS channel.
Replacement Process in which a failed or obsolete device is replaced on a network and in an OpenLNS CT drawing with a new or upgraded device. IzoT Commissioning Tool preserves the device’s functional blocks, network variables, configuration properties, and connections and transfers them into the new device. Router Routers manage network message traffic, extend the physical size of a channel (both length and number of devices attached), and connect different channel types.
Smart Connection Description (SCD) A pre-defined connection description that IzoT Commissioning Tool automatically assigns to a connection being created or changed based on the number of target network variables, whether the target network variables are located on the same or different subnet, and the availability of network variable aliases. Source Address The logical node address of the transmitting device contained in every packet transmitted over a LONWORKS network.
Synchronized The state of an IzoT Commissioning Tool network design when an OpenLNS CT drawing and the physical devices on the network match the OpenLNS network database. Target The destination of a connection. Each connection is defined in terms of a hub and a one or more targets connected to the hub. For network variable connections, the hub may only be a single input or output network variable in the connection.
Virtual Functional Block A static functional block that that contains the network inputs and outputs for a device that are not part of other functional blocks on the device. Wink A management command used to identify a device on the network and verify that is communicating. Winking a device causes it to generate application-dependant audio or visual feedback such as a beep or a flashing service LED.
368 Appendix C – OpenLNS CT Software License Agreement
Appendix C OpenLNS Software License Agreement This appendix provides a copy of the OpenLNS Software License Agreement.
OpenLNS CT Software License Agreement Echelon OpenLNS Commissioning Tool (CT) Software License Agreement I. NOTICE This OpenLNS Commissioning Tool (CT) Software License Agreement (the "Agreement") is enterered between you ("You" or "Your") and Echelon Corporation ("Echelon"). YOU MUST READ AND AGREE TO THE TERMS OF THIS AGREEMENT BEFORE DOWNLOADING, INSTALLING, OR USING THE ECHELON OPENLNS COMMISSIONING TOOL SOFTWARE (THE "LICENSED SOFTWARE").
• "Trial Period" is a 60-day period during which the Licensed Software can be used with limited functionality for a maximum of two networks, with a maximum of five devices per network, and a maximum run time of 60 minutes. • "Use Period" means a time period during which you can use the Licensed Software. The Use Period is limited to the Trial Period for Trial Editions of the Licensed Software, and is unlimited for all other editions Licensed Software.
Echelon with a copy of same upon request; this right of transfer is exercisable no more than one (1) time every year. V.
The functionality of the Microsoft Visio product as integrated in specified editions of the Licensed Software may differ from a non-integrated Microsoft Visio product and any issues concerning the functionality or performance of the Echelon OpenLNS Commissioning Tool and the integrated Microsoft Visio product should be directed to Echelon and not to Microsoft Corporation. VII. TERMINATION This License will continue until terminated by either party in writing.
$1000). YOU HEREBY AGREE THAT THE FOREGOING LIMITATIONS REFLECT THIS REASONABLE ALLOCATION OF RISK. XI. SAFE OPERATION YOU ASSUME THE SOLE RESPONSIBILITY FOR, AND HEREBY AGREE TO USE YOUR BEST EFFORTS IN, DESIGNING, MANUFACTURING, COMMISSIONING, ROUTING, MONITORING, AND CONTROLLING DEVICES USING THE ISO/IEC 14908-1 PROTOCOL TO PROVIDE FOR SAFE OPERATION THEREOF, INCLUDING, BUT NOT LIMITED TO, COMPLIANCE OR QUALIFICATION WITH RESPECT TO ALL SAFETY LAWS, REGULATIONS AND AGENCY APPROVALS, AS APPLICABLE.
expense and are deemed to be "commercial computer software" and "commercial computer software documentation", respectively, pursuant to DFAR Section 227.7202 and FAR 12.212(b), as applicable. Any use, modification, reproduction, release, performance, display or disclosure of the Licensed Software and/or the accompanying documentation by the U.S.
376 Appendix C – OpenLNS CT Software License Agreement
Appendix D Software License Transfer Agreement If you purchased a license for the OpenLNS CT software, you can transfer the license to another party. To do this, you and the other party must sign the agreement in this appendix.
Software License Transfer Agreement THIS SOFTWARE LICENSE TRANSFER AGREEMENT is entered into as of : (Date) by and between “Assignor” ______________________________________ (Company name of original purchaser) and "Assignee" _____________________________________ (Name of company purchasing the software) for the transferred “Software” _____________________________________ (Name of software product being transferred) 1. Software License Agreement.
