Echelon LonWorks Network XML - Manual (Page 36)

28 Using the XML Schema
Example
<FunctionalBlock Handle="2">
<Name>Analog Input[1]</Name>
<IsVirtualFb ID="0">False</IsVirtualFb>
<ProgrammaticName>Analog Input[1]</ProgrammaticName>
<FuncProfileName>Echelon Analog/Digital Input</FuncProfileName>
<Scope ID="3">Manf</Scope>
<FuncProfileProgrammaticName>UFPTAnalogDigitalInput</FuncProfileP
rogrammaticName>
<FuncProfileDescription>A generic object without feedback, used
with any form of sensor</FuncProfileDescription>
<PrincipalNv>AI_Analog_2</PrincipalNv>
</NetworkVariables>
</ConfigProperties>
Network Variables
Attributes
Attribute
Applicable
Values Description/Notes
Action 1 IGNORE
2 CREATE
3 CREATE_UNIQUE
4 UPDATE
5 MODIFY
6 DELETE
7 COMMISSION You can create dynamic NVs on application
devices that support them. To create a dynamic
NV, you must do the following:
1. Specify the CREATE, UPDATE, or
CREATE_UNIQUE action.
2. Set the IsDynamic property to True.
3. Specify the Name, TypeSpec, and
Direction properties.
Ref <reference name> Allows references to the NV in target
definitions. See Targets for more information
on using references.
Properties within Application Device Object Elements
Supported by
Function?
Property Export Import Description/Notes
Name Y Y The name of the NV.
Index Y N The index of the NV within the application
device.
LonMarkMemberIndex Y N The ordinal index of the NV within its
functional block.
ProgrammaticName Y Y The name of this network variable as
represented to the Neuron C programmer.
This property is supported on import if you
creating a dynamic NV.
LonMarkMemberNumber Y Y A unique number within the functional block
assigned by the LonMark Application Layer
Interoperability Guidelines, a LonMark