Echelon Neuron User Manual

Page 164

Advertising
background image

156

Project Make Errors (PMK)

PMK#

Description

4003

Can't write file <make dependency file>. This might cause the build status

calculator to malfunction, but does not impact the build results (system error

code <code>) [PMK#4003]

Failure to write a .nkdep dependency file. Insufficient write-permission, or

a write-protected media could cause this effect. This failure does not harm

the build itself, but causes the build status calculator not being able to
determine the build status correctly. Solution: make .nkdep file writable,

or disable automatic program ID management.

4004

Can't delete intermediate folder <folder>: <reason> (system error code

<code>)[PMK#4004]

Failure to complete a "clean" command. Write-protected files or folders in

that area might cause this, or it could be caused by user-defined data in the

intermediate folder(s) ("IM" folder(s)) or in the target folders
("Development" or "Release" folder(s)). NodeBuilder attempts only to

"clean" files produced by NodeBuilder.

4005

Can't delete intermediate file <file>: <reason> [PMK#1005]

See PMK#4004, but for an individual file. Failure reasons include the file

being locked by another process, the file being write-protected, and so on.
Failure details are given in <reason>, part of the actual message being

displayed.

4006

The channel type number noted in the program ID <id> is <cid1>, whereas the

transceiver is designed for channel type <cid2> [PMK#4006]

The channel type ID field in the standard program ID describes a channel

type that is different from the one referred to by the transceiver used by the

current hardware template. This does not affect the build, but might result
in an improperly implemented L

ON

M

ARK

device. This warning may only

occur if a standard program ID is used (0x8* or 0x9* format).

4007

The program ID model number field has reached the configured maximum of

<maximum>. The previous program ID <previous_pid> will be changed to use

the configured minimum model number <minumum>. Note that this might

cause a failure when importing the external interface template into LNS

[PMK#4007]

Automatic program ID management detected a required program ID
change and reached the end of the configured range. Program ID

management proceeds by re-starting at the beginning of the specified
range. This is likely to cause a problem when importing the external

interface into LNS, you will have to delete the relevant LNS device

template objects and reattempt the build.

Advertising