Echelon Neuron - Manual (Page 163)

Neuron Tools Errors Guide 155
PMK# Description
127 The specified program ID appears malformed and invalid. [PMK#127]
Use a simple ASCII string, or a byte-array format, using a single colon as a
separator between each byte (for example, 94:56:78:9A:0B:0C:0D:0F).
130 Missing hardware template. You must assign a hardware template to device
, build target , first. [PMK#130]
A build was attempted on a build target , that belongs to the
NodeBuilder device template , where the hardware template has
not yet been specified. Use NodeBuilder's device template editor to specify
the hardware template, and re-attempt the build.
132 Cannot read the hardware platforms database . [PMK#132]
Verify that the platform’s database file exists. The default location
for this database file is
\LonWorks\NodeBuilder\Templates\Hardware\nbplatforms.xml
133 Library is required but cannot be found [PMK#133]
The Project Make Facility has aborted the build process because a library
is required, but cannot be found.
4001 An empty program ID has been specified. It is recommended to change the
program ID, using the device template editor [PMK#4001]
An empty program ID, that is, a program ID without a value, has been
specified. It is recommended to change the program ID, using the device
template editor. This might result in a compilation failure. This message
should not occur when using a machine-generated device template file.
4002 The configured program ID results in an unstable build status, and may not
suitable for automatic management. It is recommended to reconsider the
specified program ID, or to disable program ID management. This might lead
to a failure in the remaining build process [PMK#4002]
This message indicates that program ID management causes an unstable
build status. This loop condition has been detected after three fix-up
compilation attempts, and the fix-up attempts have been aborted to prevent
an endless loop condition. A fix-up compilation might occur as a result of
automatic program ID management, where the PID manager detects an
interface change after the initial compilation, where the interface change
impacts the compiler's DRF lookup. Thus, a re-compilation is attempted
with the new program ID, and in this particular case, the problem persists.
This effect might be caused by the combination of automatic program ID
management and a DRF scope value 6. This combination is not
recommended for use in NodeBuilder 3, because program ID management
modifies the model field, and the scope 6 resource file expects the model
field not to change.