Echelon IzoT NodeBuilder - Manual (Page 142)

The scope may be one of the following values:
Scope Program ID Fields Used
0 Standard
1 Device Class
2 Device Class and Usage
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 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 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 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–2 are reserved for standard resource definitions published by Echelon and distributed by
L
ON M ARK International. Scope 0 applies to all devices; therefore, there is a single scope 0 resource
file set called the standard resource file set. A standard resource file set is included with the IzoT
NodeBuilder tool. You can download updated standard resource files from the L
ON M ARK Web site at
www.lonmark.org/technical_resources/resource_files .
You can define your own functional profiles, network variable and configuration property types, and
formats in scope 3–6 resource files.
Introduction to Resources
Each resource file set may contain definitions for the following resources:
Resource Description
Network Variable
Types Type information for network variables. This information includes the
size, units, scaling factors, and type category (float, integer, signed, and so
on) for each type. Network variable types can contain a single scalar
value, a structure containing multiple fields (for example, the
SNVT_switch network variable contains 2 fields for the value and state),
or enumerated values that allow the network variable to be set to one of a
discrete number of values. Network variables types are defined in a
resource file with a .typ extension.
Configuration
Property Types Type information for configuration properties. This information includes
the size, units, scaling factors, and type category (float, integer, signed,
and so on) for each type. Like network variable types, configuration
property types can contain scalar, structured, or enumerated values.
Configuration property types are defined in a resource file with a .typ
extension (this is the same file used for network variable types).
128 Defining Device Interfaces and Creating their Neuron C Framework