Echelon Neuron - Manual (Page 24)

16 LonTalk Interface Developer Errors (LID)
Overview
The LID error messages described in this chapter do not necessarily include the
same wording that is shown at runtime. Instead, this chapter provides a
summary of the message’s meaning for each message, followed by a brief
discussion of possible reasons and remedies. In all cases, be sure to consult the
actual message reported by the utility at runtime, because the actual message is
likely to contain additional details (for example, the name of the specific file for
which the message is issued, or more details about the precise failure reason).
A numbering convention is used to identify the LID error messages as errors (1-
3999), warnings (4000-7999), or hint codes (8000-9999). Not all messages are
displayed in all contexts, but the numerical message identifier is always unique
and unambiguous.
LID Errors
Table 6 lists the LID error codes.
Table 6. LID Error Codes
LID# Description
1 An NV, CP, or MT item was expected but not present – internal error
Remove the device interface files (.xif and .xfb extension), and re-run the
LonTalk Interface Developer utility to see if the problem persists. Use the
Trace verbosity level to help track down the problem.
2 A file cannot be opened for read access
See the error message received for details of the offending file. Verify that
the file is available and readable and the path is accessible.
3 A file cannot be opened for write access
See the error message received for details of the offending file. Verify that
the file is available and writable and the path is accessible.
4 A property value is required but has not been obtained from any data source
This is an internal error, probably a result of an earlier failure. A non-fatal
error during the creation of the device interface file might lead to this error.
Re-run the LonTalk Interface Developer utility in Trace verbosity mode and
carefully examine the LonTalk Interface Developer utility Summary
window to determine the root cause of the failure.
5 An error occurred when reading a device interface file
This is an internal error, probably a result of an earlier failure. A non-fatal
error during the creation of the device interface file might lead to this error.
Re-run the LonTalk Interface Developer utility in Trace verbosity mode and
carefully examine the LonTalk Interface Developer utility Summary
window to determine the root cause of the failure.