FieldServer FS-8700-21 用户手册
FS-8700-21 LonWorks Manual
Page 25 of 62
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
Tel: (408) 262 2299 Fax: (408) 262 2269 Toll Free: (888) 509 1970 email: support@fieldserver.com
Appendix A.5. Configuration Properties
Configuration Properties are implemented on the FieldServer using configuration Network Variables. Configuration Network
Variables take the form of update inputs in order to be updated or read by a network management tool. Each Configuration
Network Variable will have its own Map Descriptor. Since the data carried by a Network Variable is intended as a
configuration property for other already declared non-configuration Network Variable(s), no Data Array needs to be assigned
to its Map Descriptor.
Variables take the form of update inputs in order to be updated or read by a network management tool. Each Configuration
Network Variable will have its own Map Descriptor. Since the data carried by a Network Variable is intended as a
configuration property for other already declared non-configuration Network Variable(s), no Data Array needs to be assigned
to its Map Descriptor.
Configuration Properties can be declared to belong to the entire Node, to an Object(s) or to a Network Variable(s). This
declaration defines the scope of the Configuration Property. Configuration Properties that belong to an Object are declared
as a part of the Object; Configuration Properties associated with a Network Variable(s) are declared as belonging to the
Network Variable(s) etc.
declaration defines the scope of the Configuration Property. Configuration Properties that belong to an Object are declared
as a part of the Object; Configuration Properties associated with a Network Variable(s) are declared as belonging to the
Network Variable(s) etc.
A Configuration Property’s Type and Responsible Map Descriptor(s) are declared by the Configuration Network Variable’s
self-documentation string as follows:
self-documentation string as follows:
For linking to the entire node:
“&0,,0\x80,*SCPT Index+”
Example: “&0,,0\x80,20”
For linking to object(s):
“&1,[Object Index(s)],0\x80,*SCPT Index+”
Example: “&1,0.2.3,0\x80,23”
For linking to network variable(s):
“&2,*NV Index(s)+,0\x80,*SCPT Index+”
Example: “&2,0.1.2.4.7,0\x80,20”
Examples of configuration network variables are presented in Section 6.3.6
“&0,,0\x80,*SCPT Index+”
Example: “&0,,0\x80,20”
For linking to object(s):
“&1,[Object Index(s)],0\x80,*SCPT Index+”
Example: “&1,0.2.3,0\x80,23”
For linking to network variable(s):
“&2,*NV Index(s)+,0\x80,*SCPT Index+”
Example: “&2,0.1.2.4.7,0\x80,20”
Examples of configuration network variables are presented in Section 6.3.6
Appendix A.6. LonMark Object Creation
For more information on filling out the Node Self-Documentation String as well as the relevant Network Variable Self-
Documentation Strings in order to create a LonMark Object please consult the following documentation from the LonMark
Interoperability Association at
Documentation Strings in order to create a LonMark Object please consult the following documentation from the LonMark
Interoperability Association at
Understanding LonMark Self-Documentation
LonMark Application Layer Interoperability Guidelines
The two examples given below will show how LonMark Objects can be assigned in FieldServer configuration files:
The first example uses the standard Open Loop Sensor Object (Type 1) to create a Water Temperature Sensor that will send
out its current status via Network Variable Updates.
out its current status via Network Variable Updates.
A typical recipient of these updates is given by example #2 which uses the LonMark Open Loop Actuator Object (Type 3) to
create a Water Heating Element object that will interpret the Network Variable it receives and adjust power to its heating
element accordingly.
create a Water Heating Element object that will interpret the Network Variable it receives and adjust power to its heating
element accordingly.