The IzoT Interface Interpreter issues error or warning messages when necessary, following this general format:
type: filename (line number): description [IML#message-number]
Error: "izot_device.c" (8): onOffline: Handler "offline" is already used with the onOnline event [IML#29]
Errors and Warnings
|A general syntax error occurred, with details shown in the error message.|
|The offending construct does not declare a datatype or variable. Block, Datapoint, Property, and Tag directives require the declaration of a datatype and at least one variable on the left of the //@IzoT tag|
|An option's numeric value is outside of the supported range.|
|An option's alphanumeric value fails to match the required format.|
|A required input file cannot be read.|
|A generated output file cannot be written.|
The number of bindable message tags exceeds the supported maximum.
Duplicate type name. Different items sharing the same base type (a block type, or a datapoint type, for example) can implement different characteristics, and the type names must be unique. You can resolve this issue by selecting a different, unique, type name modifier within a block or datapoint declaration.
Too many type modifiers. Blocks and datapoints require type modifiers to be provided with the type declaration in order to produce unique type names for the implementation. For example: SNVT_amp(amp) amp; ....
One type modifier is required for datapoints or profiles that do not implement a generic SNVT_xxx member. Two type modifiers are required to implement profiles that declare members with SNVT_xxx, and the second modifier must resolve the generic type to an absolute datapoint type.
The variable has been re-declared. Variables implementing blocks, datapoints, and properties are global C variables and must have unique names.
An error occurred when processing the attributes supplied to the right of the //IzoT tag.
A name error occurred when processing the attributes supplied to the right of the //IzoT tag.
An attribute error occurred when processing the attributes supplied to the right of the //IzoT tag.
A type error occurred when processing the attributes supplied to the right of the //IzoT tag.
The alphanumeric ("string") value supplied with an attribute does not meet the minimum length requirements.
The alphanumeric ("string") value supplied with an attribute exceeds the maximum length requirements.
An intermediate file cannot be deleted.
The specified resource cannot be located.
The specified block member does not exist, or is not implemented.
The array option may only be used with property block members.
The specified property block member's array size does not meet the array size limitations defined in the profile.
An unspecified error occurred when processing an IzoT Interface Interpreter instruction.
A property must be unique within its application set. For example, only one SCPTlocation property can be implemented and applied to the entire device, and only one such property can be implemented and applied to each datapoint.
Invalid typename modifier. A typename modifier must begin with a lower or upper case letter (a-z or A-Z) or an underscore character. It must consist of letters (a-z or A-Z), digits (0-9), and underscore characters.
Unknown property flag.
The specified attribute cannot be applied to the current class. For example, the implement attribute can be applied to a Block class, but is not supported by the Datapoint class.
A required type modifier is missing.
Another Node object has already been implemented. There can only be one Node object. This error can occur when an application makes an explicit declaration of a Node object too late—the IzoT Interface Interpreter automatically supplies a Node object when required, generally at the time the second block is implemented.
The given event handler has already been used with another event type. Any given event handler can be registered more than once, but only with the same event type. For example, an onOnline event handler cannot also be used to implement an onOffline event.
The onUpdate event cannot be used with an output.
The onComplete event cannot be used with an input.
The minimum buffer size requested with the buffersize option does not meet this application's minimum required buffer size (the requested and required minimum buffer size values are listed in the diagnostic message).
The node object is required and must be defined.
The selected option is not available with this target.
Invalid combination of property flags.
A profile specifies a SCPTnvType property which appears to have an empty application set. This error indicates an incorrectly defined profile.
The application's program ID has been updated to indicate that the application includes at least one changeable-type datapoint.
Your implementation of an optional property that applies to an optional datapoint, where the datapoint is not currently implemented, promotes the datapoint to the implementation.
Too many datapoints. The target's maximum number of datapoints was exceeded.
An error occurred when recognizing or applying an explicit initial value supplied with your IML declaration.
A block implements a profile that declares a principal datapoint member, but does not implement this member.
A polling attribute is incorrectly used for an output or a polled attribute is incorrectly used for an input—you can only use the polled attribute for an output and the polling attribute for an input.
A polling or polled attribute is incorrectly used with a property—you can only use the polling and polled attributes with a datapoint.
A polled attribute is incorrectly used with a polling attribute—the polled andpolling attributes are mutually exclusive.
The implementation of the polled or polling attribute differs from the profile's recommendation.
Notes: (*) This diagnostic is a warning by default, but can be changed into an error with the strict option.