Echelon LonWorks Network XML - Manual (Page 32)

24 Using the XML Schema
is to be assigned.
Subnet/Name Y Y If you specify a subnet name or ID that differs
from the current subnet, the import operation
will attempt to move the application device to
the specified subnet. If you specify both the
subnet name and ID, the subnet name will first
be used to look up the subnet. If the subnet is
not identified, the subnet ID will be used.
If you are creating an application device and
specify a subnet (ID or name), the import
operation will attempt to create the application
device on the specified subnet.
Subnet/NodeId Y N The import operation does not support explicitly
setting the node ID of an application device.
Extensions Y Y Extension records defined for this application
device. See Extension Records for more
information.
FunctionalBlocks Y Y The functional blocks assigned to the application
device that have shapes in the network are
reported.
The global NVs, CPs, and MTs are contained
within the FunctionalBlocks\
VrtualFunctionalBlock property.
See Functional Blocks for more information.
Example
<AppDevice Handle="1">
<NeuronId>FEFA28FFC254</NeuronId>
<Name>LNS Network Interface</Name>
<LocationText/>
<Location>000000000000</Location>
<Template>LNS Network Interface</Template>
<Channel>Channel 1</Channel>
<Description/>
<AuthenticationEnabled ID="0">False</AuthenticationEnabled>
<Priority>0</Priority>
<AliasCapacity>1024</AliasCapacity>
<AliasUseCount>0</AliasUseCount>
<Shape>
<StencilName>LONBASIC</StencilName>
<MasterName>Network Service Device</MasterName>
<PinX>1.070000</PinX>
<PinY>1.320000</PinY>
</Shape>
<CommissionStatus ID="1">UpdatesPending</CommissionStatus>
<AttachmentStatus ID="0">Attached</AttachmentStatus>
<PingClass ID="4">Permanent</PingClass>
<Subnet Handle="1">
<Name>Subnet_1_1</Name>
<NodeId>127</NodeId>
</Subnet>