Implementation-specific scope rules – Echelon FTXL User Manual
Page 54
42
Creating a Model File
devices, and scopes 1 and 2 are reserved for future use. Because scope 0 applies
to all devices, there is a single scope 0 resource file set called the
standard
resource file set
.
The FTXL Developer's Kit includes the scope 0 standard resource file set that
defines the standard functional profiles (SFPTs), SNVTs, and SCPTs (updates
are also available from L
ON
M
ARK
International at
). The kit
also includes the NodeBuilder Resource Editor that you can use to view the
standard resource file set, or use to create your own user functional profiles
(UFPTs), UNVTs, and UCPTs.
You can define your own functional profiles, types, and formats in scope 3
through 6 resource files.
Most LNS tools, including the LonMaker tool assume a default scope of 3 for all
user resources. LNS automatically sets the scope to the highest (most specific)
applicable scope level. However, if you use LNS 3.0 or earlier with scope 4, 5, or
6 resource files, you must explicitly set the scope in LNS so that LNS uses the
appropriate scope. See the
NodeBuilder User’s Guide
for information about
developing a plug-in to set the scope, or see the
LonMaker User's Guide
(or online
help) for information about modifying a device shape to set the scope.
Implementation-Specific Scope Rules
When you add implementation-specific network variables or configuration
properties to a standard or user functional profile, you must ensure that the
scope of the resource definition for the additional item is numerically less than or
equal to the scope of the functional profile, and that the member number is set
appropriately. For example:
• If you add an implementation-specific network variable or configuration
property to a standard functional block (SFPT, scope 0), it must be
defined by a standard type (SNVT, or SCPT).
• If you implement a functional block that is based on a manufacturer
scope resource file (scope 3), you can add an implementation-specific
network variable or configuration property that is defined in the same
scope 3 resource file, and you can also add an implementation-specific
network variable or configuration property that is defined by a SNVT or
SCPT (scope 0).
You can add implementation-specific members to standard functional profiles
using inheritance by performing the following tasks:
1. Use the NodeBuilder Resource Editor to create a user functional profile
with the same functional profile key as the standard functional profile.
2. Set Inherit members from scope 0 in the functional profile definition.
This setting makes all members of the standard functional profile part of
your user functional profile.
3. Declare a functional block based on the new user functional profile.
Add implementation-specific members to the functional block.