Echelon FTXL - Manual (Page 53)

FTXL User’s Guide 41
the program ID template to the program ID of a device. That is, the range of
device types to which a resource file applies is the scope of the resource file.
The program ID template has an identical structure to the program ID of a
device, except that the applicable fields might be restricted by the scope. The
scope value is a kind of filter that indicates the relevant parts of the program ID.
For example, the scope can specify that the resource file applies to an individual
device type, or to all device types.
You can specify a resource file for any of the following scopes:
0 – Standard
Applies to all devices.
1 – Device Class
Applies to all devices with the specified device class.
2 – Device Class and Subclass
Applies to all devices with the specified device class and subclass.
3 – Manufacturer
Applies to all devices from the specified manufacturer.
4 – Manufacturer and Device Class
Applies to all devices from the specified manufacturer with the specified
device class.
5 – Manufacturer, Device Class, and Device Subclass
Applies to all devices from the specified manufacturer with the specified
device class and device subclass.
6 – Manufacturer, Device Class, Device Subclass, and Device Model
Applies to all devices of the specified type from the specified
manufacturer.
For scopes 1 through 6, the program ID template included in the resource file set
specifies the components. Network management tools match this template
against the program ID for a device when searching for an appropriate resource
file.
For a device to be able 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. Thus, each L ON W ORKS manufacturer can create resource
files that are unique to their devices.
Example: Consider a resource file set with a program ID template of
81:23:45:01:02:05:04:00, with 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. However, resources on devices of the same class, but from a
different manufacturer, could not access this resource file set.
A resource file set can also use information in any resource file set that has a
numerically lower scope, as long as the relevant fields of their program ID
templates match. For example, a scope 4 resource file set can use resources in a
scope 3 resource file set, assuming that 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 L
ON
M
ARK
International. Scope 0 applies to all