Defining the device interface – Echelon NodeBuilder FX User Manual

Page 152

Advertising
background image

138

Defining Device Interfaces and Creating their Neuron C Framework

• The Functional Blocks folder contains all the functional blocks contained in this device interface.
• The Network Variables folder contains all the device network variables for this device interface.

Device network variables belong to the device and therefore are not contained in any functional
block. You can use device network variables to create a portion of your device interface for
proprietary or legacy information.

• The Configuration Properties folder contains all device configuration properties for this device

interface. Device configuration properties belong to the device and therefore are not contained in
any functional block. You can use device configuration properties to create a portion of your
device interface for proprietary or legacy information.

If you use device network variables or device configuration properties in your
device interface, your device will not comply with interoperability guidelines version
3.4 (or better) and therefore cannot be certified by L

ON

M

ARK

.

A better alternative for adding members to a functional profile is to create a user-defined functional
profile template (UFPT) that inherits from an existing standard functional profile template (SFPT), and
then add new mandatory or optional member network variables to the UFPT. This method results in a
new functional profile that you can easily reuse in new devices. See the NodeBuilder Resource Editor
User’s Guide
for more information on creating new functional profiles.

You can right-click the device template to open a shortcut menu that has the following commands:

CP Access Method

Configuration properties may be accessed using read and write network
management commands, or they be accessed using the L

ON

W

ORKS

File

Transfer Protocol (FTP). Select this option to choose the configuration
property access method: Direct Memory Read/Write (recommended)
or File Transfer Protocol.

Direct Memory Read/Write. This method requires less space and

code on the target device. This is the recommended option and the
default. When this option is selected, the Code Wizard
automatically implements the Node Object functional block’s
optional nvoFileDirectory network variable. The optional
nviFileReq, nviFilePos, and nvoFileStat network variables may
not be in the Node Object functional block when this option is
selected.

File Transfer Protocol. When this option is selected, the Code

Wizard automatically implements the Node Object functional
block’s optional nviFileReq, nviFilePos, and nvoFileStat network
variables. The optional nvoFileDirectory network variable may
not be in the Node Object functional block when this option is
selected.

You can also select one of these options in the Configuration Property
Access Method
box at the top of the user interface.

The NodeBuilder Code Wizard requires every device interface to
contain a Node Object functional block with nviRequest and nvoStatus

Advertising