Echelon Neuron - Manual (Page 35)

Neuron Tools Errors Guide 27
LID# Description
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
www.echelon.com for available software updates that address the problem,
or contact [email protected] . This message is a warning rather
than an error because the condition does not prevent your application from
working. Carefully 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
FTXL device.
4012 The channel type specified in the standard program ID does not match the
channel type served by the transceiver in use
This message reminds you to correct the transceiver choice or the program
ID. While the mismatch does not cause the device to malfunction, it breaks
the interoperability of the device and might cause a network tool to prevent
installation of the device.
This warning code applies only to a ShortStack Micro Server.
4013 Explicit addressing not requested but seems required
The presence of message tags with the bind_info(nobind) modifier in the
model file indicates that explicit addressing is probably required. Enable
explicit addressing and re-generate the application framework using the
LonTalk Interface Developer utility. See also the LID#4014 and LID#4015
warnings.
This warning code applies only to a ShortStack Micro Server.
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.