Developing an hmi, Creating a device installation application – Echelon NodeBuilder FX User Manual

Page 86

Advertising
background image

72

Creating and Opening NodeBuilder Projects

Developing an HMI

You can create a human machine interface (HMI) for your device so that end users can monitor and
control it. You will typically create an HMI if you are building a complete system that requires one;
however, if your device is installed by integrators where each installation is unique, the integrators will
typically develop the required HMIs.

You can use the LonMaker tool to design a simple HMI for your device. With the LonMaker tool, you
use the data point shape in the LonMaker Basic Shapes stencil and standard Visio shapes to create the
HMI. For example, you can create an HMI that displays the current state of a lamp and provides
override switches that let you manually turn the lamp on and off. For more information on creating
HMIs with data point shapes, see Chapter 6 of the LonMaker User’s Guide.

You can use high-end HMI tools, such as Wonderware’s InTouch or Intellution FIX, to represent more
complex types of network interactions. These tools are developed with a scripting language tuned to
specifically address HMI tasks. In addition, these tools offer components that provide reporting and
analysis, history, alarm logging, event handling, and Internet-enabling.

Creating a Device Installation Application

You can create an installation executable that automatically installs all the files required by your
device into the appropriate locations on your customers’ computers. The files that your application
should install include the device application (if your device uses downloadable application memory),
the device interface file, user-defined resource files, the LonMaker stencil, the LNS device plug-in, and
the HMI. Typically, the installation executable is created using an installation application such as the
InstallShield

®

product.

If your device will be installed in a managed network (as opposed to a self-installed network), your
customers must have LNS or an LNS network tool such as the LonMaker tool already installed on their
computers. Installing LNS or an LNS network tool creates a LonWorks folder that is stored by
default in the root directory or program files directory on the user’s computer (for example,
C:\LonWorks or C:\Program Files\LonWorks). The user, however, can change the location of the
LonWorks folder when they are installing LNS or an LNS tool. You can locate the LonWorks folder
in the Windows registry at the following location:

HKEY_LOCAL_MACHINE\SOFTWARE\LonWorks\LonWorks Path

The following table lists and describes the files that your installation application should install:

Advertising