Echelon LonWorks Network XML - Manual (Page 25)

L ON W ORKS Network XML Programmer’s Guide 17
Example
<Subsystem Handle="6" Action=”CREATE”>
<Name>Subsystem 2</Name>
<DocumentName>XML NETWORK</DocumentName>
<PageName>Subsystem 2</PageName>
<Location>Subsystem 1.Subsystem 2</Location>
<SubsystemId>6</SubsystemId>
<Shape>
<StencilName>LONBASIC</StencilName>
<MasterName>Subsystem</MasterName>
<PinX>4.890000</PinX>
<PinY>6.300000</PinY>
</Shape>
<Description/>
<Routers/>
<AppDevices/>
<Subsystem/>
<Extensions>
</Extensions>
Routers
Attributes
Attribute
Applicable
Values Description/Notes
Action 1 IGNORE
2 CREATE
3 CREATE_UNIQUE
4 UPDATE
5 MODIFY
6 DELETE
7 COMMISSION If you are creating a router, you must specify the
Name property and specify the channels
attached to the router within the
NearRouterSide and FarRouterSide
properties.
If you specify the COMMISSION action, the
router’s Neuron ID and Channel properties are
updated.
Commission 0 False
1 True You must set this property to True to enable
commission-related operations.
State 0 DEFAULT
1 ONLINE
2 OFFLINE
3 DISABLE
4 RESTORE You can specify the state of the router
application. The default is DEFAULT, which
indicates the settings of the LNS application are
to be used.
Properties
Supported by
Function?
Property Export Import Description/Notes
Name Y Y Routers are reported in the subsystem in which
their shapes are defined. Routers defined in
multiple subsystems are not supported.
LNS requires that router names be unique within
the entire network (not just within a subsystem).
Class Y Y An enumerated value indicating the router type.