Echelon NodeBuilder Resource Report Generator - Manual (Page 38)

Table 5.1 Resource File Validation Warnings
Warning Message Displayed Description
Missing Strings Warning: String ^<scope
selector>:<index> can not
be located for program ID
<program_id>: <detailed
reason> This warning occurs if a string with scope selector and
index as detailed in the message cannot be located for
the given program ID. The typical reason is that the
string is missing or the resource file set’s scope scope
selector was lowered after a resource was created.
Min/Max Data
Validation Warning: <type name>
minimum value (<value>)
exceeds maximum value
(<value). You should contact the resource file set manufacturer.
Minimum values must not exceed maximum values (but
the minimum might be equal to the maximum).
This validation is not currently being performed for
configuration property types, or configuration property
members of functional profiles.
Missing Format Warning: No format
definition was found in
<format file> to match type
<typename> This may be as designed, but generally indicates a
missing or misnamed format file entry. Each network
variable and configuration property type should have at
least one distinct format each.
Invalid Format
#1 Warning: Cannot validate
existing format(s) for type
<typename>: <reason> A problem occurred while validating the formats for
<typename>. This warning can point to a missing or
corrupt format file, or to a corrupted installation of the
local machine.
Invalid Format
#2 Warning: Format <name>
cannot be used with type
<typename> (and test data
that is <number> bytes of
0x00): <reason> This warning is a result of an attempt to use format
<name> with type <typename>, and <number> bytes of
test data (all zeroes). This message might be benign (in
case a test vector of all zeroes is inappropriate and the
formatter fails to apply the format to the data offered),
but more typically suggests an invalid syntax being
used within the format specification.
CP “Applies To”
Validation Warning: Cannot resolve
‘apples to’ information: <fpt-
name>::<cp-member-name>
applies to NV with index
<nv-index>, no such NV
found” This is a serious problem. The functional profile <fpt-
name> is invalid. It might be possible to use the
functional profile in case the CP <cp-member-name> is
optional and not implemented, but the profile must be
corrected so that the CP applies to the entire functional
profile, or to an existing member-NV.
Overloading
FPT Warning: Functional profile
<fp-name> uses key <key-
value>, without using
inheritance. Consider
inheriting rather than
overriding, or adjust the FPT
key to a value >= 20000. This is a recommendation, and may be as designed by
the resource file set developer. Generally it is better to
derive a user functional profile from a standard
functional profile by inheritance rather than by re-
defining (overriding).
This warning is only shown for user functional profiles.
Bad FPT
Inheritance Warning: Functional profile
<fp-name> uses key <key-
value> and inheritance. You
cannot inherit from a UFPT;
consider correcting the
inheritance preference, or
indicate the correct SFPT to
inherit from by setting the
key to < 20000.
This is a serious problem. The implementer of the user
functional profile <fp-name> plans to inherit from a
functional profile that is not defined with a profile
number that indicates it being part of the standard
functional profile range.
36 NodeBuilder Resource Report Generator User’s Guide