9-2 Neuron Firmware Error Codes
Every application reserves one byte of on-chip EEPROM memory space to
hold the error log. If the firmware posts an error, it is usually due to a severe
problem. A network diagnostics tool could periodically collect the error log
and device statistics to monitor the health of the system.
An application may post errors too, using the error_log( ) function. Only the
last error posted is saved. users are allocated error numbers 127 and below.
Use the LonMaker Device|Manage shortcut menu item to get the LonMaker
Device Manager Dialog. The test command will fetch the error log and other
statistics from a device.
The NodeBuilder Debugger shows any posted errors on the Results pane, in
the Events Log tab.
Code Description
129 Bad event.
This run-time error is checked only in the development environment.
This error could occur if the network configuration is invalid, if the
network management tool is malfunctioning, or if the Neuron Chip
firmware image is corrupted. If this error occurs, try reloading the
node.
130 NV length mismatch.
This error may occur rarely due to network transmission problems.
The length of the data in a network variable update message is
inconsistent with the length expected by the node. Rebuild and
reload the images if this error continues to occur.
Note this error does not get set in conjunction with the change of a
network variable type for a NV of changeable type. However, if such
type change is performed in an inappropriate manner, this error
might be logged upon the first arrival of the incorrectly sized network
variable data.
131 NV message too short.
This error may occur rarely due to network transmission problems.
This error could occur if a network message is corrupted.
132 EEPROM write failure.
This error may occur rarely due to Neuron Chip, transceiver, or
application failure.
This error occurs if too many erase/write cycles have been performed
on the EEPROM or flash memory. Up to 10,000 erase/write cycles
per byte can be performed in the on-chip EEPROM. This error will
also be logged if an EEPROM write is attempted when a node is
online and has EEPROM locking enabled.
133 Bad address type.
This error could occur if the network configuration is invalid, if the
network management tool is malfunctioning, or if the Neuron Chip
firmware image is corrupted. If this error occurs, try reloading the
node.
