Echelon IzoT NodeBuilder - Manual (Page 162)

modified only when the device has been set offline by a network
tool such as the IzoT Commissioning tool. Do not set this option
if you are using FTP to transfer configuration properties because
devices must be online to run the file transfer protocol.
• const_flg. Specifies that the configuration property should be
considered read-only. It must not be written. It might be stored
in ROM. An example of this kind of property is the device major
version number.
• obj_disabl_flg. Specifies that the configuration property should
only be modified when the functional block has been disabled by
a network tool such as the IzoT Commissioning tool. The
application will have a chance to initialize the functional block
when the network management tool enables it.
Note: The reset_flg, offline_flg, and obj_disabl_flag flags comprise
a hierarchy, where the reset_flg has the highest precedence and the
obj_disabl_flag flag has the lowest.
For example, if you specify the offline_flg flag for a configuration
property, the device will be set offline, but other steps or
configuration property updates occurring at the same time might also
require that the device be reset.
Similarly, the offline_flg flag, which applies to devices, has a higher
precedence than the obj_disabl_flag, which applies to functional
blocks. As a result, if you specify the offline_flg flag, it is expected
that the device is offline or the functional block is disabled.
Implement As You can specify the following implementation options for the
configuration property.
Configuration
Network Variable Enables you to read, write, and bind the configuration property like a
network variable. If this check box is cleared, the configuration
property is implemented as a configuration file (file CP). This check
box is cleared by default.
Note that CPNVs are have the following limitations: (1) they must be
based on network variable types and must meet the target platform’s
network variable size limit (228 bytes starting with version 21
firmware, 31 bytes with earlier versions); and (2) if the CPNV is
implemented as an array that applies to multiple functional blocks or
network variables, the CPNV array must always be shared statically
or globally. It is therefore recommended that you only use CPNVs if
your application requires configuration properties that must be bound
or if you are adding a SCPTnwrkCnfg configuration property.
Static CP Creates a single configuration property that is shared by all the
functional blocks in a functional block array. Sharing configuration
properties can simplify device configuration by reducing the number
of configuration properties that must be set by an integrator, and can
also reduce the memory required for the device application.
This property is only available if the configuration property is in a
functional block array. Modifying the value of the configuration
property on any functional block in the array modifies it for all of
them (only one variable is allocated).
If this check box is cleared, a separate configuration property is
created for each functional block in the array. This check box is
148 Defining Device Interfaces and Creating their Neuron C Framework