Echelon IzoT NodeBuilder - Manual (Page 225)

Upgrading Device Applications
The 5000 and 6000 Series chips are compatible with device applications written for 3150 and 3120
Neuron Chips and Smart Transceivers. You can use the IzoT NodeBuilder tool to port your old
application to a 5000 or 6000 Series chip. To do this, you open the device’s NodeBuilder project,
update the Neuron Chip model used by the hardware template to the Neuron 5000 processor or FT
5000 or FT 6000 Smart Transceiver, and then re-build the device application. See Editing Hardware
Templates in Chapter 5 for more information on using the Hardware Template Editor.
Note: The Neuron C Version 2.2 language includes the following new keywords: interrupt, __lock,
stretchedtriac, __slow, __fast, and __parity. Some of these keywords use a double underscore
prefix to avoid any naming collisions within existing device applications. The Neuron C Version 2.3
language adds the following new keywords: __resident, __type_scope and __type_index.
You can also use the IzoT NodeBuilder tool to upgrade your existing device applications to the new
Version 3 code templates when porting them to a 5000 or 6000 Series chip. The Version 3 code
templates include improved code size, speed, and compliance with interoperability guidelines. To
upgrade existing device applications to the Version 3 template, see Using Code Wizard Templates in
Chapter 6.
Adding and Managing Target Devices
A target device is a L ON W ORKS device application that is built by the IzoT NodeBuilder tool. There
are two types of targets, development targets and release targets. Development targets are used during
development; release targets are used when development is complete and the device will be released to
production. Each NodeBuilder device template specifies the definition for a development target and a
release target. Both target definitions use the same source code and resource files, but they may use
different hardware templates and compiler, linker, and exporter options. The source code may include
code that is conditionally compiled based on the type of target.
Each target device is defined by a LonMaker shape and its corresponding LNS device, a NodeBuilder
device template and its corresponding LNS device template, and a NodeBuilder hardware template.
You can add a target device to a NodeBuilder project using the IzoT Commissioning tool or the
NodeBuilder Project Manager (you should use the IzoT Commissioning tool because it is typically
faster and easier). After you add a target device, you can use the NodeBuilder Project Manager to
re-build and debug it and to view and change its NodeBuilder device template and target type.
Adding a Target Device with the IzoT Commissioning Tool
You can add a target device to a NodeBuilder project using the IzoT Commissioning tool. To add a
target device with the IzoT Commissioning tool, follow these steps:
1. Build the application image for the target as described in Building an Application Image earlier in
this chapter.
2. Correct any build errors.
3. Create a new a LonMaker network or open an existing one. See the IzoT CommissioningTool
User’s Guide for more information on creating and opening LonMaker drawings.
You will use the IzoT Commissioning tool to install, bind, configure, and test the targets in your
project. The IzoT Commissioning tool displays a network drawing that shows the devices,
functional blocks, and connections in your network.
The IzoT Commissioning tool also displays stencils that contain shapes that you can drag to your
LonMaker drawing. The IzoT Commissioning tool includes a NodeBuilder Basic Shapes 4.00
stencil with shapes that you can use to add new devices, functional blocks, and connections to
your network drawing. The NodeBuilder Basic Shapes 4.00 stencil contains shapes that can be
IzoT NodeBuilder FX User's Guide 211