Echelon LNS - Manual (Page 27)

LNS Programmer's Guide 13
points to the host PC. However, you can still connect network variables to your Network
Service Device using explicit connections, and utilize these with the
SuppressPollingIfBound property.
For more information on monitor and control in this document, see Chapter 9.
Availability of Network Resource Information
The NetworkResources property has been added to the System object for Turbo
Edition. This property returns a NetworkResources object that provides access to
important network resource information for a system, including the number of
AppDevices and Routers that have been installed on the system, the number of
exclusive and sharable network variable selectors available on the system, and the
number of subnets and group IDs allocated on the system.
This information is useful if you are managing a large system. For example, if you are
writing an application that creates large numbers of multicast connections on a system,
you will need to know how many groups and exclusive selector are available on the
system. Or, if you are merging two LNS databases, you will need to know how many
subnets, groups, and exclusive selectors have been assigned in each database, to make
sure that the merged database will not exceed the limits for each resource.
For more information on the NetworkResources object and its properties, see the LNS
Object Server Reference section of the LNS Application Developer’s Kit help file.
Enhanced LonMark Interoperability
Several changes have been made to LNS Turbo Edition to comply with version 3.3 of the
LonMark Application-Layer Interoperability Guidelines, and to better support the latest
versions of the LonMark standard resource files.
When importing a device interface from an external interface file, previous versions of
LNS would set the Mode property of all LonMarkObject objects defined in the device
interface to one of two values. It would set the Mode property of a LonMarkObject object
to 0 if the LonMarkObject object’s TypeIndex property was in the range of standard
Functional Profile Template (FPT) indices, or to 3 if the LonMarkObject object’s
TypeIndex property was in the range of user-defined FPT indices. Turbo Edition
features automatic scope determination, which means LNS will now search the set of
installed and cataloged resource files to find the most device-specific match for the FPT,
and set the LonMarkObject object’s Mode property based on this determination when
the device interface is imported. If no match is found, LNS will set the LonMarkObject
object’s Mode property to lcaResourceScopeUnknown.
In addition, the ResyncToResources() method has been added to the
DeviceTemplate object. You can use this method to re-synchronize a device template
with modified or newly accessible device resource file information. This may be necessary
if you are upgrading to the current version of the LonMark resource files, or if you
imported a device’s external interface file before the resource files for that device were
available in the resource file catalog.
To complement this change, the ResyncToTemplate() method has been added to the
AppDevice object. You can use this method at any time to re-synchronize the
configuration of an AppDevice with the DeviceTemplate it is using. This may be