Echelon Neuron - Manual (Page 25)

Neuron Tools Errors Guide 17
LID# Description
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.
10 Failure to attach to LONUCL32 service DLL
The LonTalk Interface Developer utility or one of its components failed to
locate a file by name of “LONUCL32.DLL.” This file usually resides in the
same folder that contains the LID.exe application, but can be in any folder
in your current user search path. This file is typically installed into the
LonWorks Bin folder.
12 Failure reading stdxcvr.xml file
The standard transceiver definition file, stdxcvr.xml, cannot be found or
cannot be read. The stdxcvr.xml file is usually installed into the LonWorks
Types folder. Ensure that the file exists and can be read.
This error code applies only to a ShortStack Micro Server.