Example, Properties within device template object elements – Echelon LonWorks Network XML User Manual
Page 35
L
ON
W
ORKS
Network XML Programmer’s Guide
27
information.
Example
<FunctionalBlock Handle="1">
<Name>AI- 1</Name>
<IsVirtualFb ID="0">False</IsVirtualFb>
<ProgrammaticName>Analog Input[0]</ProgrammaticName>
<FuncProfileName>Echelon Analog/Digital Input</FuncProfileName>
<Scope ID="3">Manf</Scope>
<FuncProfileProgrammaticName>UFPTAnalogDigitalInput</FuncProfileP
rogrammaticName>
<Shape>
<StencilName>LonPoint3</StencilName>
<MasterName>Analog Input</MasterName>
<PinX>5.860000</PinX>
<PinY>2.560000</PinY>
</Shape>
<IsDynamic ID="0">False</IsDynamic>
<SubsystemName>$Subsystem 1.Subsystem</SubsystemName>
</Extensions>
</NetworkVariables>
</ConfigProperties>
Properties within Device Template Object Elements
Supported by
Function?
Property
Export Import
Description/Notes
Name
Y Y
ProgrammaticName Y N
FuncProfileName Y N
FuncProfileProgrammatic
Name
Y
N
The programmatic name given by the functional
profile’s LonMark definition
Virtual functional blocks do not contain this
property.
FuncProfileDescription
Y
N
A description of the functional profile.
PrincipalNv
Y
N
The principal NV is used to resolve the type of a
CP that inherits its type. If a CP applies to a
functional block and inherits its type, the CP
uses the type of the principal NV.
Scope
Y Y
IsVirtualFb
Y N
ComponentApps
Y
Y
The set of LNS plug-ins registered to operate on
the functional block.
NetworkVariables Y N
MTs
Y N
ConfigProperties
Y N