Echelon Neuron - Manual (Page 106)

98 Neuron C Compiler Errors (NCC)
NCC# Description
427 The context for the ‘: :’ operator is not a valid context [NCC#427]
The :: operator can be used to access the members and the properties of a
functional block, as well as the properties of a network variable, or
properties of the device. This message indicates that the context, or the
portion of the property expression that precedes the :: operator, is neither a
functional block nor a network variable. A functional block array or a
network variable array requires an index expression in the context of the ::
operator. To access device properties, use the :: operator without a context
preceding it. See the examples and description of the :: operator in the
Neuron C Programmer's Guide and the Neuron C Reference Guide for more
information.
428 The specified fblock does not have a director function [NCC#428]
An attempt to access the director property of the functional block was
made, but no director function was declared for the functional block.
429 Incorrect number of arguments for the director function [NCC#429
The function returns void, and it has two parameters. The prototype for a
director function must be in the form shown below:
void f (unsigned index, int cmd);
For more information, consult the Neuron C Programmer's Guide or the
Neuron C Reference Guide .
430 Use of fblock_director function but no fblocks declared [NCC#430]
The compiler has detected an attempt to use the fblock_director( ) but no
functional blocks were declared in the program.
431 FPT name used to declare fblock is not in resource files [NCC#431]
Part of the declaration of a functional block refers to an FPT record in a
L ON M ARK Resource File, however, the name used in the program was not
found in the resource file. Check the spelling of the name (it is case-
sensitive) and check that the resource file containing the FPT is installed in
the resource file catalog on the computer. The catalog can be checked with
the NodeBuilder Resource Editor.
Verify that the program ID chosen for the project allows for the FPT
resource files to be accessed by the compiler. For example, in case the
desired FPT is implemented in an FPT device resource file, scope 3 or
higher, that applies to all code by manufacturer with ID 0x12345, this FPT
cannot be referenced from a project that uses a different manufacturer IF
value in its program ID.