Echelon FTXL - Manual (Page 243)

FTXL User’s Guide 231
LID# Description
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.
6 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.
(This error is similar to LID#5, but refers to a different internal
component recognizing the error.)
7 A device interface file appears malformed
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.
8 An unrecognized escape character has been detected in a file or
NVVAL data record
This is an internal error, probably a result of an earlier failure
during the creation of an intermediate file with a .bif file extension.
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. After
the build, make sure the file with the .bif extension exists and can be
read.
9 A FILE or NVVAL value record cannot be read due to an
unsupported construct
This is an internal error, probably a result of an earlier failure
during the creation of an intermediate file with a .bif file extension.
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. After
the build, make sure the file with the .bif extension exists and can be
read.