Echelon IzoT NodeBuilder - Manual (Page 148)

Each functional profile has a name and number that is unique for the scope of the resource file set.
The number is called the functional profile key or FPT key. If your device is a simple sensor or
actuator, you can use functional profiles 1–4: SFPTopenLoopSensor (1), SFPTclosedLoopSensor
(2), SFPTopenLoopActuator (3), or SFPTclosedLoopActuator (4). If your device is more complex,
you can browse the other SFPTs in the Standard resource file set for any suitable standard profiles
have been defined.
If you cannot find an SFPT that fits your device, you can define a user-defined functional profile
template (UFPT). You can create a UFPT from scratch, or you can create a UFPT that inherits from a
SFPT and then add network variables and configuration properties to the UFPT. See the NodeBuilder
Resource Editor User’s Guide for more information on creating UFPTs.
After you determine the functional profiles that your device interface needs to implement, you do the
following to finish defining your device interface:
1. Add functional blocks.
2. Edit mandatory network variables.
3. Implement desired optional network variables.
4. Implement desired optional configuration properties.
If your device needs network variables or configuration properties that are not included in any
functional profile, you can create a UFPT that inherits from a SFPT as described in the NodeBuilder
Resource Editor User’s Guide. Alternatively, you can add implementation-specific network variables
and configuration properties to the device interface; however this is not recommended because your
device will not pass L
ON M ARK certification.
134 Defining Device Interfaces and Creating their Neuron C Framework