Echelon IzoT Resource Editos - Manual (Page 10)

2 Introduction to Resource Files
Introduction to Resource Files
Resource files provide definitions of functional profiles, type definitions, enumerations,
and formats that can be used by network tools such as the OpenLNS Commissioning tool.
The type definitions include definitions for network variable types and configuration
property types.
Resource files are grouped into resource file sets, where each set applies to a specified
range of program IDs. The program ID range is determined by a program ID template in
the file, and a scope value for the resource file set that specifies the fields of the program
ID template that are used when matching the program ID template to the program ID of
a device. The program ID template has an identical structure to the program ID of a
device, except that the applicable fields may be restricted by the scope. The scope value
can be seen as a filter, indicating the relevant parts of the program ID. The scope may be
one of the following:
0 – Standard
3 – Manufacturer
4 – Manufacturer and Device Class
5 – Manufacturer, Device Class, and Device Subclass
6 – Manufacturer, Device Class, Device Subclass, and Device Model
For a device to use a resource file set, the program ID of the device must match the
program ID template of the resource file set to the degree specified by the scope. This
allows each L
ON W ORKS manufacturer to create resource files that are unique to their
devices.
For example, consider a resource file set with a program ID template of
81:23:45:01:02:05:04:00
and manufacturer and device class scope (scope 4). Any
device with the manufacturer ID fields of the program ID set to 1:23:45 and the device
class ID fields set to 01:02 would be able to use types defined in this resource file set,
whereas resources on devices of the same class but by a different manufacturer could not
access this resource file set.
A resource file set may also reference information in any resource file set with a
numerically lower scope provided the relevant fields of their program ID templates
match. For example, a scope 4 resource file set can reference resources in a scope 3
resource file set, provided the manufacturer ID components of the resource file sets’
program ID templates match.
Scopes 0 through 2 are reserved for standard resource definitions published by Echelon
and distributed by the L
ON M ARK association. Scope 0 applies to all devices, and scopes 1
and 2 are reserved for future use. Since scope 0 applies to all devices, there is a single
scope 0 resource file set called the standard resource file set. A standard resource file set
is included with the NodeBuilder tool, but periodic updates are available from the
L
ON M ARK association at www.lonmark.org . You can define your own functional profiles,
types, and formats in scope 3 through 6 resource files.
Each resource file set may contain definitions for the following resources:
Network Variable Types Type information for network variables. This
information includes the size, units, scaling
factors, and type category (float, integer, signed,
etc) for each type. Network variables can