Echelon LonTal Stack User Manual
Page 239
LonTalk Stack Developer’s Guide
227
LID#
Description
4006
A file cannot be copied
This is possibly, but not necessarily, fatal. When the LonTalk
Interface Developer utility creates the host framework, it produces
several files based on input provided by the user. It also copies the
necessary files into the destination folder. The utility-generated files
refer to these files, which are required to build the host application.
Thus, this issue is non-fatal for the LonTalk Interface Developer
utility, but probably fatal when building the host application. See
also warning LID#4017.
4011
The .NCT file references a built-in type with no host equivalent
known to LonTalk Interface Developer utility
This condition is unlikely to occur and does report an internal error.
Check
available software updates that address
the problem, or contact
. This message is a
warning rather than an error because the condition does not prevent
your application from working. Check the type definitions provided
in LonNvTypes.h and LonCpTypes.h (both generated by LonTalk
Interface Developer utility) and correct the offending type. Continue
using these files and build your LonTalk Stack device.
4014
Explicit addressing specified but not required
This warning reminds you that you have requested support for
explicit addressing, although it does not seem to be required.
Explicit addressing requires larger buffers on the host, therefore
support for explicit addressing is advisable only when needed.
Message tag declarations that are intended for use with explicit
addressing should be marked with the bind_info(nobind) modifier
to signal the use of explicit messaging. See also the LID#4013 and
LID#4015 warnings.
4015
Explicit addressing specified but neither supported nor required
Although support for explicit addressing has been requested, it does
not appear to be required. See also the LID#4013 and LID#4014
warnings.
4016
FTP implementation suspect –no message tag but SNVT_file_*
implemented
The implementation of the file transfer protocol is suspect, as the
FTP-related network variables are present but no message tag has
been declared.