The final step in the process is the selection of a target hardware platform. In the
development phase, a LonBuilder Emulator is used. To select this target hardware,
click the
App Node
button and then the
Target HW
button from the LonBuilder
Navigator. Create a target hardware template that uses
Emulator
as the
HW Type
,
the TP/FT-10 channel definition created earlier (described above) as the
Channel
Name
, and the hardware template created earlier (described above) as the
HW
Prop. Name
.
The LonBuilder environment is now ready for application code to be written, built,
and loaded on the development platform.
Release Hardware Setup
The only difference between the development hardware setup and the release
hardware setup is the selection of the target hardware in the final step. The channel
definition and hardware template used in the development hardware setup may be
used to build the release version of the application.
The change to the target hardware step is not a requirement, because the
programmable application image file (.nxe extension) from the development build can
be used to program the target hardware. However, for target hardware designs that
use flash memory to store the application, the LonBuilder tool can load the
application image over the network.
To select the release hardware as a target for a build, click the
App Node
button and
then the
Target HW
button from the LonBuilder Navigator. Create a target
hardware template that uses
Custom Node
as the
HW Type
, the TP/FT-10 channel
definition created earlier (described above) as the
Channel Name
, and the hardware
template created earlier (described above) as the
HW Prop. Name
.
Refer to the
Building Custom Node
section of Chapter 7 of the
LonBuilder User's
Guide
for a description of how to migrate the application from LonBuilder Emulators
to production hardware.
Warning:
In custom designs using flash memory, the programmed device must be
explicitly secured by the PROM programmer once the image is programmed. See
Software Data Protection (SDP) information provided by the manufacturer of the
PROM programmer.
7-4
Design
Issues