Echelon OpenLNS Commissioning Tool - Manual (Page 240)

224 Maintaining Networks
3. Select the subsystems and drawing files to update.
4. Click Finish. The Synchronization Status dialog opens and OpenLNS CT begins updating the
subsystem data in the devices within the specified network scope.
5. When the synchronization operation has been completed, click OK.
Using Subsystem Paths
If you select the Set SCPT Location Value to Subsystem Path option, OpenLNS CT stores the
subsystem path in the SCPTlocation configuration property of application devices when they are
commissioned. OpenLNS CT automatically updates the subsystem path stored in SCPTlocation when
the application device is moved. If you set the Update all Devices when Subsystem Name is
Modified option in the Network Properties: Recovery options category to Yes, OpenLNS CT also
automatically updates the subsystem path of the device when you move or rename its subsystem.
If you do not import a CSV file that includes the subsystem location data for an application device, the
recovery wizard places application devices in the subsystem path specified in the SCPTlocation
configuration property. If the device also has a subsystem ID, the recovery wizard will link the
subsystem path to it so that all devices with same subsystem ID but no subsystem path can be placed in
that subsystem path.
Tip:
To optimize the accuracy of the network recovery, keep subsystem paths under 32 characters. If you
are storing subsystem IDs in the SCPTlocation configuration property of devices and you commission
a device that has a subsystem path longer than 31 characters, OpenLNS CT truncates the subsystem
path to fit within 31 characters. This may result in the recovery wizard losing part of the subsystem
path, which may cause the device to be moved to a parent subsystem.
Using Subsystem IDs
If you select the Set Location Property to Subsystem ID option, OpenLNS CT stores the subsystem
ID in application devices or routers when they are commissioned. The subsystem ID is equal to the
lower 15 bits of a device’s subsystem handle, and it opens as a 6-character ASCII or 12-digit hex string
in the Location field of the Basic Properties dialog box. OpenLNS CT automatically updates the
subsystem ID when you move the device. If you set the Update all Devices when Subsystem Name
is Modified option in the Network Properties: Recovery options category to Yes, OpenLNS CT also
automatically updates the subsystem ID of the device when you move or rename its subsystem.
The recovery wizard will place devices in the subsystem path specified by the subsystem ID if the
following is true: you do not import a CSV file that includes the subsystem data; the device does not
have a valid SCPTlocation configuration property; and no other devices that have the same subsystem
ID have a valid SCPTlocation configuration property. In this case, the device will be placed in a
subsystem named “Subsystem <subsystemID>”.
If there are one or more discovered devices that have a subsystem ID or a valid SCPTlocation
configuration property, the following occurs, listed in order of precedence:
• A discovered device with the same subsystem ID but no valid SCPTlocation configuration
property is placed in the subsystem path specified by the first SCPTlocation configuration
property value discovered.
• A discovered device with the same SCPTlocation configuration property but no valid subsystem
ID is placed in the subsystem specified by the first subsystem ID value discovered. If there is no
discovered device that has a valid subsystem ID, all discovered devices with the same
SCPTlocation configuration property are assigned the same new subsystem ID.
Based on this, if OpenLNS CT discovers both devices with the same subsystem ID but different
SCPTlocation configuration properties and devices with the same SCPTlocation configuration
property but different subsystem IDs, OpenLNS CT places the discovered devices in the
subsystem path specified by the first valid SCPTlocation configuration property value discovered.