Echelon OpenLNS - Manual (Page 986)

OpenLNS Programmer's Reference 949
components can not be matched if their
types differ.
2 lcaUgRsName
The external interface component was
preserved because it matched the name of
a component in the new external interface.
4 lcaUgRsIndex
The external interface component was
preserved because it matched the index of
a component in the new external interface.
8 lcaUgRsObjMembership
The external interface component was
preserved because it is a network variable
or configuration property which is a
member of a LonMark object, and its
member index and member number in the
old LonMark object is the same in the new
LonMark object (which may have a new
object ID) in the new external interface.
16 lcaUgRsRecreated
The external interface component was
re-created in the new external interface.
This only applies to dynamic network
variables, monitor sets, and monitor
points.
32 lcaUgRsConvertFromStatic
The external interface component existed
as a static component on the old device
interface, but not the new one. As a result,
it has been added to the new device
interface as a dynamic component. All
such components will have the same
programmatic name as the original, unless
the original was an array. In this case an
index value will be appended to the name,
or if the name does not fit, the name will
be truncated.
This may result in the assignment of
duplicate names, but an OpenLNS
application may change both the user
name (Name property) and programmatic
name (ProgrammaticName property) in
this case.
A new custom interface will be created by
OpenLNS to house network variables and
LonMarkObjects that are converted from
static to dynamic in this fashion. The