Echelon OpenLNS Commissioning Tool - Manual (Page 320)

304 Creating and Using Custom OpenLNS CT Shapes and Stencils
Using Custom OpenLNS CT Master SmartShapes
You can reuse a custom OpenLNS CT SmartShape that you create (see
5
Creating Custom OpenLNS CT
Master SmartShapes). The custom OpenLNS CT master SmartShape may contain any number of the
standard OpenLNS CT SmartShapes described in Designing OpenLNS CT Networks. The following
sections describe how OpenLNS CT processes each of the standard OpenLNS CT SmartShapes when
you include them in a custom OpenLNS CT SmartShape.
If you drag a master SmartShape containing multiple SmartShapes and the creation of any of the
SmartShapes fails, that SmartShape will not be added, and all subsequent SmartShapes in the master
SmartShape will not be processed.
Device Master SmartShapes
You can include one or more OpenLNS CT Device SmartShapes in a custom master SmartShape.
Each of these is called a device master SmartShape. Each device master SmartShape includes the
device template name, device interface (XIF) file name, and the configuration property settings from
the original device. The Neuron ID is not included so that you can reuse the master SmartShape with
multiple devices.
When you drag a master SmartShape that includes any device master SmartShapes to a drawing and
automatic channel selection is enabled in the Network Properties: Device options category, the
master SmartShape is added to the drawing without any wizards opening. If automatic channel
selection is disabled, the New Device Wizard opens and you select the channel for the new device.
You can select the same channel as the original device, another existing channel, or create a new
channel. If the custom master SmartShape includes multiple devices on the same channel, the Device
Wizard opens for the first device only on each channel. OpenLNS CT places all subsequent devices
that are on the same channel in the master SmartShape on the channel that you select for the first
device on the channel, and have their properties set as specified in the master SmartShape. To
manually set the channels and properties for each device, select the Force Wizard Prompts check box
in the Network Properties: General options category as described in Appendix A.
When you drag a master SmartShape that includes a device SmartShape to a drawing, OpenLNS CT
does the following for each device master SmartShape:
1. If the master SmartShape includes a program ID in a ProgramID user cell (see
5
Additional Device
User Cells), OpenLNS CT looks up the device template using the program ID. If the master
SmartShape does not include a program ID but includes a device template name in a TmplName
user cell (see Additional Device User Cells), it looks up the device template based on the specified
device template name.
2. If OpenLNS CT does not find a device template in step 1, it looks for the device interface (XIF)
file specified in the XifName user cell. If the device interface file is found, OpenLNS CT looks
up the device template by the program ID specified in the device interface file. If a device
template with a matching program ID is found, the user is given the option of changing the name
of the device template to the name specified by the device SmartShape, or using the existing
device template name. In either case, the existing device template is associated with the device
SmartShape.
3. If OpenLNS CT does not find a device template in steps 1 and 2, but it does find the device
interface file, it creates a new device template by importing the device interface file. OpenLNS
CT gives the new device template the name specified in the device SmartShape, and associates it
with the device SmartShape.
4. If OpenLNS CT 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.
A functional block SmartShape may include a device template name and/or program ID. The device
template name assigned by the above procedure must match the name in any functional block