Echelon IzoT NodeBuilder Uživatelský manuál

Procházejte online nebo si stáhněte Uživatelský manuál pro Software Echelon IzoT NodeBuilder. Echelon IzoT NodeBuilder User Manual Uživatelská příručka

  • Stažení
  • Přidat do mých příruček
  • Tisk
  • Strana
    / 291
  • Tabulka s obsahem
  • KNIHY
  • Hodnocené. / 5. Na základě hodnocení zákazníků

Shrnutí obsahu

Strany 1 - User’s Guide

078-0516-01ADevelop hardware devices and software applications usingEchelon's Series 6000, 5000, and 3100 chips and SmartTransceivers. IzoTTM No

Strany 2 - Chips or LonPoint Modules

Purpose This document describes how to use the IzoT NodeBuilder tool to develop IzoT and LONWORKS device applications and build and test prototype an

Strany 3 - CONTENTS

11. Browse to and open the device template folder backed up in step 3, and then select the NodeBuilder device template file (.NbDt extension). Th

Strany 4

With on the shortcut menu. Choose Microsoft Excel, Internet Explorer, or another XML browsing tool. The following XML files are created and maintain

Strany 5

5 Creating and Using Device Templates This chapter describes how to use the New Device Template wizard in the NodeBuilder Project Manager to creat

Strany 6

Introduction to Device Templates Each type of device that you develop with the IzoT NodeBuilder tool is defined by a pair of device templates: a Node

Strany 7

3. Proceed to the next section to specify the device template name. Specifying the Device Template Name To specify the device template name, foll

Strany 8

2. Optionally, in the Source File Name property, you can enter the name of the Neuron C source file for this device template. By default, this fiel

Strany 9 - Preface

The Standard Program ID Calculator helps you select the appropriate values for the program ID fields. It lets you select the values from lists cont

Strany 10 - Content

c. In the Device Class (CC:CC) property, select the primary function of the device. To enter a device class value that has not yet been added to th

Strany 11 - Related Manuals

3. Click OK to return to the Program ID dialog in the New Device Template wizard. The Program ID property contains the program ID you specified in

Strany 12 - ONMARK SNVT and SCPT Guide

of model numbers specified by the Min Model # and Max Model # properties to avoid two devices having the same program ID but different external inter

Strany 13

Explains how to manage development and release targets and insert libraries into a device template. Describes how to use the Hardware Template Edito

Strany 14

8. Proceed to the next section to specify the hardware templates used by development and release devices. Specifying Target Platforms You can spe

Strany 15 - Introduction

2. In the Release Build Hardware Template property, select the hardware template to be used for release targets. The list contains all the hardwar

Strany 16 - LonTalk/IP Support

menu. The NodeBuilder Project Properties dialog opens. Click the Options tab, change the setting, and then click OK. 4. Click Finish. If you se

Strany 17 - Series 6000 Chip Support

Output Files in Chapter 8 for more information on removing the files and folders produced by a build. Status Displays the build status for all device

Strany 18 - Extended Address Table

menu. When a device template is excluded, you can still explicitly build the device template by right-clicking the device template and selecting Bui

Strany 19

Source Files This folder contains all the source files associated with this device template except for the main source file. When you add source fil

Strany 20 - ONWORKS free

Managing Development and Release Targets Each NodeBuilder device template in the Project pane contains Development and Release targets ( ) that can b

Strany 21

Settings Opens the NodeBuilder Device Template Target Properties dialog, which includes compiling, linking, exporting, and configuration options f

Strany 22 - IzoT Plug-in for Wireshark

You can set the following properties: Defines You can define a symbol, which can then be tested from the program using the ifdef or ifndef directiv

Strany 23 - Network Integration

Debug Kernel Options Disable optimizer Disables the compiler’s code optimizer. Optimization typically generates smaller and faster code, and is typ

Strany 24 - Program IDs

IzoT Commissioning ToolUser’s Guide (078-0514-01) Describes how to use the IzoT Commissioing Tool to design, commission, modify, and maintain LONWOR

Strany 25

Enable Function Execute Enables the debugger to get and update the values of system timers and to update the values of network variables in the watch

Strany 26

Compatible EEPROM to meet system requirements. In NodeBuilder 3.0 and prior releases, the IzoT NodeBuilder tool allocated system on-chip EEPROM aft

Strany 27 - Functional Profiles

You can set the following properties: Boot ID Generation Select whether the boot ID is generated automatically or manually. Note: This option is i

Strany 28 - Device Templates

application image inconsistency, or other fatal application error. • Always. Reboot every time the Neuron Chip is reset. Application Specify whe

Strany 29 - Targets

You can select the Export Configured check box to enable the IzoT NodeBuilder tool build a configured device application for the target. The target

Strany 30 - 16 Introduction

is sent using subnet/node addressing regardless of the addressing format of the original message. • Devices are no longer protected against re

Strany 31 - Development Tool

Because the pragma library directive supports location-independent references to your library, this is the recommended method. To insert a library in

Strany 32 - ONMARK International

Select one or more of the following standard libraries in the C:\LonWorks\Images folder to be explicitly included in the project (for documentation

Strany 33

When you build the application image, the IzoT NodeBuilder tool first searches for the selected libraries in the folder within the Images folder that

Strany 34

however, you can use the Insert Copy feature to create your own custom hardware template based on a Standard template and then edit your custom temp

Strany 35 - ONMARK products

Region Languages Supported Contact Information Europe English German French Italian Echelon Europe Ltd. Suite 12 Building 6 Croxley Green Busi

Strany 36

New Creates a new hardware template to be added to the selected folder. Selecting this option opens the Hardware Template Editor dialog where you ca

Strany 37

• Do not modify hardware templates in the Standard Templates folder because any changes that you make will be overwritten by future NodeBuilder upda

Strany 38

You can set the following properties on the Hardware tab: Hardware Template Name Enter the name of the hardware template. By default, new hardware

Strany 39

Transceiver Type Select the transceiver type supported by the Neuron Chip or Smart Transceiver model selected in the Neuron Chip Model property. Eac

Strany 40 - ONWORKS networks. You can

System Image Version Select the system image version for the selected Neuron Chip or Smart Transceiver model. See your Neuron Chip or Smart Transcei

Strany 41

The Memory Addresses box details how on chip and off-chip memory is organized on the selected Neuron Chip or Smart Transceiver model. These values a

Strany 42

6000 Series Chips The address ranges and consumption for the on-chip and off-chip memory of the 6000 Series chips are as follows: Off-Chip ROM The 60

Strany 43

IzoT NodeBuilder User's Guide 123

Strany 44

6 Defining Device Interfaces and Creating their Neuron C Application Framework This chapter describes how to use the NodeBuilder Code Wizard to de

Strany 45

Introduction to Device Interfaces The NodeBuilder Code Wizard generates Neuron C source code that implements your device interface and creates the Ne

Strany 47 - Application Framework

The NodeBuilder Code Wizard opens. The NodeBuilder Code Wizard user interface is essentially divided into two panes: the Resource pane and the Prog

Strany 48

section. For more information on creating and editing resource file sets and resources, see the NodeBuilder Resource Editor User’s Guide. The Reso

Strany 49

The scope may be one of the following values: Scope Program ID Fields Used 0 Standard 1 Device Class 2 Device Class and Usage 3 Manufacturer 4 Manufa

Strany 50

Resource Description Functional Profiles Functional profiles define a template for functional blocks. A functional block is a collection of network

Strany 51

Resource Description Italian (default) “ita” Italian (Swiss) “its” Norwegian (Bokmal) “nor” Polish “plk” Portuguese (Brazilian) “ptb” Portuguese (de

Strany 52

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

Strany 53 - FT 6000 Evaluation Boards

network variables. The Node Object functional block is a standard functional block that is used by network management tools to test and manage the o

Strany 54

A network variable defines an operational input or output for the device. The structure, range, units, and format of the network variable are define

Strany 55

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 ke

Strany 56

Adding Functional Blocks Functional blocks represent specific device functions. For example, a device could have four hardware digital inputs, and d

Strany 57

1 Introduction This chapter introduces the IzoT NodeBuilder Development Tool. It lists the new features in the IzoT NodeBuilder tool, summarizes th

Strany 58

the Use Array checkbox, enter the number of functional blocks in the array in the Size box, and then click OK. 3. In the Program Interface pane, rig

Strany 59

5. If any of the mandatory network variables do not have a default type set by the functional profile (for example, the nvoValue network variable i

Strany 60

4. In the SFPT or UFPT property, select the desired functional profile template. 5. In the Name property, enter a name for your functional block.

Strany 61

2. The NV Properties dialog opens. 3. Edit the following properties: IzoT NodeBuilder FX User's Guide 139

Strany 62

Name Displays the name of the network variable that will be used in the IzoT Commissioning tool and other network management tools. The default nam

Strany 63

Service Type Displays the service type used by the network variable to send updates as specified in the functional profile (Unspecified, Acknowledged

Strany 64

Modifiers Indicates whether the network variable uses the Synchronized or Polled modifiers. This property is only available for output network va

Strany 65

4. Optionally, you can click Advanced to open the Advanced NV Properties dialog and further specify the storage class used by the network variable.

Strany 66

memory devices. far The network variable is placed in the far section of the variable space. By default, Neuron C variables are placed in the near R

Strany 67

the network variable must have priority enabled when it is installed. To enable priority on a device installed in a LonMaker network, right click th

Strany 68

Introduction to the IzoT NodeBuilder Tool The IzoT NodeBuilder Development Tool is a complete hardware and software platform for developing, debuggin

Strany 69

3. Edit the following properties: Name Displays the name of the configuration property that will be used in the IzoT Commissioning tool and other

Strany 70

Implement as CP Array check box is set appropriately and unavailable. If the functional profile template does not define how this configuration pro

Strany 71

modified only when the device has been set offline by a network tool such as the IzoT Commissioning tool. Do not set this option if you are using FT

Strany 72

cleared by default. Initializer Optionally, you can set the value for the network variable when the device is reset. If this network variable is a

Strany 73

4. If you have shared two mandatory or optional configuration properties or if you have shared two implementation-specific configuration properties

Strany 74 - Creating an IzoT CT Stencil

functional block or network variable arrays, or any combination thereof. • A configuration property that is shared among the members of a functional

Strany 75

Alternatively, you can drag a network variable from the functional profile’s Optional NVs folder in the Resource pane to the functional block’s Opt

Strany 76

The name cannot contain spaces or the following characters: \ / : * ? “ < > |. 5. The Use Array check box in the Array Element Count box is

Strany 77

3. In the FPT Member Name property, select the optional configuration property from the list of those that have not yet been implemented in this fu

Strany 78

See the Neuron C Programmer’s Guide and Neuron C Reference Guide for more information about implementing configuration property arrays. 6. In the

Strany 79 - Developing an HMI

devices in Compatibility Mode can also communicate with LonTalk devices on different channels as long as there is a route created between the channel

Strany 80 - Windows\XifSearchPath

functional block is based. For example, a UNVT could not be added to a SFPT, but a SNVT may be added to a UFPT. To add an implementation-specific ne

Strany 81 - ONMARK Certification

3. In the Name property, enter a name for the network variable as it will appear in the IzoT Commissioning tool and other network management tools.

Strany 82

If you are selecting a UNVT, the list contains all the UNVTs in resource files of the scope specified in the Scope field that match the program ID te

Strany 83 - NodeBuilder Projects

Alternatively, you can right-click the Configuration properties folder in the Program Interface pane and select Add CP from the shortcut menu, or yo

Strany 84

3. In the Name property, enter a name for the configuration property as it will appear in the IzoT Commissioning tool and other network management

Strany 85 - Using the Project Pane

5. In the Select Resource Type box, select whether the configuration property you are adding is based on a Standard or User-Defined type. If you se

Strany 86

Float SNVT_volt_f {0, 0x42, 1, 0x7c, 0x6666} Structure SNVT_switch {200, 0} Enumeration SNVT_hvac_mode HVAC_AUTO If you need help entering a valid in

Strany 87 - Manager

The Structure Fields box displays all the fields in the structured network variable or configuration property. If no initializer has previously be

Strany 88

3. All other fields in the structure are automatically set to their default values, which are defined in resource files. If no default value is de

Strany 89

2. Click anywhere in the Value box, and select a value from the list of possible enumeration values. You can set the enumeration to its default val

Strany 90

FT 6000 EVB Evaluation Board The FT 6000 EVB is a complete 6000 Series IzoT and LONWORKS device that you can use to create IzoT and LONWORKS devices.

Strany 91

3. The current initial value for the float or 32 data type is displayed in the Initializer box. You can edit the values of a field by either selec

Strany 92

Generating Code with the Code Wizard You can use the NodeBuilder Code Wizard to generate Neuron C source code that implements your device interface a

Strany 93

The following table lists and describes the files created by the NodeBuilder Code Wizard. Source File Description <Device Template Name>.nc

Strany 94

Source File Description filesys.nc Contains functions used to facilitate transfer of configuration properties implemented as configuration files. T

Strany 95 - Copying NodeBuilder Projects

Each time you generate code using the Code Wizard, it checks whether each of the common files exists on the Include Search Path property. If a file

Strany 96

Version 1 Templates The version 1 templates were the initial implementation of the Code Wizard templates, which are no longer supported by the Code W

Strany 97

172 Defining Device Interfaces and Creating their Neuron C Framework

Strany 98 - ONWORKS Network Design

7 Developing Device Applications This chapter provides an overview of the Neuron C Version 2.3 programming language. It describes how to edit the

Strany 99

Introduction to Neuron C Neuron C Version 2.3 is a programming language based on ANSI C that you can use to develop applications for Neuron Chips a

Strany 100

Each network variable, configuration property, and functional block is defined by a type definition contained in a resource file. Network variables

Strany 101

// TO DO: add code to return the current length of the network variable // with index "nvIndex." // Example code follows: // // s

Strany 102

Neuron C Variables The following sections briefly discuss various aspects of Neuron C-specific variable declarations. Data types affect what sort o

Strany 103 - Creating Device Templates

• const declares a value that cannot be modified by the application program. Affects self-documentation (SD) data generated by the Neuron C compile

Strany 104

Declaration Example Pointers char *p; Functions int f(int a, int b); Arrays int a[4]; Structures and unions struct s { int field1;

Strany 105 - Specifying the Program ID

• Default directors for functional blocks or functional block arrays. The source code for each functional block or functional block array contains

Strany 106

}; // //<Fblock Output NV Declarations> network output SNVT_lev_percent nvoPercentage; : : // //}}NodeBuilder Code Wizard End You can override

Strany 107

... Add when-tasks Responding to I/O and Timer Events You can add when-tasks to respond to I/O and timer-related events, as needed. Add these eve

Strany 108

The method used by the Neuron firmware to change the size of a network variable uses an NV length override system image extension that is managed by

Strany 109

Neuron C Version 2 Features Not Supported by the Code Wizard The following overview summarizes features of the Neuron C Version 2 language that are c

Strany 110 - Specifying Target Platforms

range_mode_string. The NodeBuilder Code Wizard does not support the range_mode_string option, which supports the setting of LONMARK range modificati

Strany 111

You can cut, copy, and paste text using standard Windows commands. For example, you can cut selected text using CTRL+X, the Cut button on the toolba

Strany 112 - Managing Device Templates

Echelon, LON, LonWorks, Neuron, 3120, 3150, Digital Home, i.LON, IzoT, FTXL, LonScanner, LonSupport, LNS, LonMaker, LONMARK, LonPoint, LonTalk, NodeB

Strany 113

What's Included with the IzoT FT 6000 EVK The FT 6000 EVK includes the following components: • IzoT NodeBuilder Development Tool. The IzoT Nod

Strany 114

4. Set Match Whole Word Only to find only whole words that match the string. Set Match case to make the search case sensitive. 5. Click Find Nex

Strany 115

2. In the Text to Find property, enter the text string to be found. 3. In the File Types property, select the file types to be searched. By def

Strany 116

Expression Description ? The question mark replaces one or zero characters. The search must contain at least two other characters. Use \? to repres

Strany 117

5. In the Where property, select which files to search. You have the following three choices: • Search all Files in Project. Searches all files i

Strany 118

Alternatively, you can access this tab by clicking Project, clicking Settings, and then clicking the Editor tab, or by clicking the Project Settings

Strany 119

8 Building and Downloading Device Applications This chapter describes how to compile Neuron C source code, build an application image, and downloa

Strany 120

Introduction to Building and Downloading Applications You can build an application image for one or more development or release targets in a NodeBuil

Strany 121

• To build one or more targets in the current NodeBuilder project, click one target device template, optionally, hold down CTRL and click the other

Strany 122

Note: To stop a build in progress, open the Project menu and then select Stop Build. 6. If the Load After Build option ()in the IzoT NodeBuilder t

Strany 123

Downloadable Application Image Files (.APB, .NDL., and NXE,) These files contain the application image used by the IzoT Commissioning tool and other

Strany 124

• NodeBuilder Editor. Edit the Neuron C source code generated by the Code Wizard to create your device’s application, or create and edit your own N

Strany 125

flash, or NVRAM (if any). For these devices, this file is used with a device programmer to program the external memory chips. If the application im

Strany 126

Excluding Targets from a Build You can exclude a target or a device template from project builds, and you can exclude a target from a device template

Strany 127

Note: The Clean command only removes files and folders produced by the IzoT NodeBuilder tool. It does not remove any files that you have generated

Strany 128 - Using Hardware Templates

2. The Build Status dialog opens. 3. Each row in this dialog represents a device template target or a target. Targets are listed beneath their a

Strany 129 - Creating Hardware Templates

changed. This status is unlikely to occur. Link required. Applies to device template targets only. Indicates that one of the libraries or the syst

Strany 130

process will move on to the next target, rather than aborting the build. Load after Build Loads the application into a device immediately after the a

Strany 131 - Editing Hardware Templates

Processor System Image Memory Type Application Memory Type Application Image File Extension Application Image Programming Tool Neuron 5000 Processor

Strany 132

Programming 5000 and 6000 Off-chip Memory A 5000 or 6000 Series device requires at least 2K of external serial EEPROM, and it can optionally contain

Strany 133

some pins that are multifunctional; therefore you must program each external non-volatile memory device individually. After you connect the I2C or

Strany 134 - Setting Memory Properties

FT 5000SCLSDA_CS1~AardvarkSCLSDAGND1 2 31 2 3J1J2Serial EEPROM DeviceGNDGND454313210SDASCLGNDVCCR14.99kVCCR24.99kFT 5000/6000-Aardvark I2C Connection

Strany 135 - 5000 Series Chips

For more information on the FT 6000 EVB hardware, including detailed descriptions of its Neuron core, I/O devices, service pin and reset buttons and

Strany 136 - 3120 and 3170 Neuron Core

FT 5000SCLSDA_CS1~RST~AardvarkSCLSDAGNDSerial EEPROM DeviceGNDGND45432813210SDASCLGNDVCCR14.99kVCCR24.99kSerial EEPROM-Aardvark I2C Connection(Direct

Strany 137

Serial Memory Device-Aardvark Connection Scheme for SPI Interface To connect an external serial EEPROM or flash device to the Aardvark programmer and

Strany 138 - Framework

FT 5000MOSIMISOSCKCSO~RST~AardvarkMOSIMISOSCLKSSGNDSerial EEPROM or Flash DeviceGNDGNDVCCR4100kR1..33xR49.948464740288579210CSO~SCKMISOMOSIGNDSerial

Strany 139 - Starting the Code Wizard

When using flash memory, always enable the flash programmer’s software data protect, SDP, feature if possible. You must have at least 0x5600 bytes m

Strany 140 - Using the Resource Pane

areas, as well as in on-chip EEPROM. Whenever the Neuron Chip or Smart Transceiver is reset, the Neuron firmware compares the on-chip and off-chip s

Strany 141

Upgrading Device Applications The 5000 and 6000 Series chips are compatible with device applications written for 3150 and 3120 Neuron Chips and Smart

Strany 142 - Introduction to Resources

used with any device. You can also create custom stencils with shapes customized for your devices and networks. The NodeBuilder Basic Shapes 4.00 st

Strany 143

8. Click Next three times. The window in the New Device Wizard lets you select the application image to be downloaded to your device. 9. Select

Strany 144

10. The next window lets you set the initial device state and the source of configuration property values when your device is commissioned. 11.

Strany 145 - ONWORKS File

13. Press the service pin on the development platform you to be loaded and commissioned. The IzoT Commissioning tool loads the application image f

Strany 146

Introduction to NodeBuilder Device Development and Network Integration An IzoT or LONWORKS network consists of intelligent devices (such as sensors,

Strany 147 - ONMARK Web site at

2. The Insert Device dialog opens. 3. This dialog organizes the devices in currently open LonMaker networks by LNS device template name. If the

Strany 148 - ONMARK certification

7. Click OK to add the target to the Devices folder in the NodeBuilder Project pane. If this device is commissioned, the IzoT NodeBuilder tool wil

Strany 149 - Adding Functional Blocks

Remove Removes the device as a target for future builds. The device is removed from the current NodeBuilder project, but it is not removed from the

Strany 150

3. You can view and set the following properties: Device Name Displays the name of the device specified in the LonMaker drawing. This field is rea

Strany 151

Current LNS Device Template Displays the name of the LNS device template associated with the target. This field is read-only and is automatically up

Strany 152

9 Testing a NodeBuilder Device Using the IzoT Commissioning Tool This chapter describes how to use the Data Point shape and LonMaker Browser in th

Strany 153

Introduction to Testing NodeBuilder Devices You can use the IzoT Commissioning tool to test your NodeBuilder device. You can press the hardware inpu

Strany 154

3. Expand the Subsystem icon, expand your NodeBuilder device icon, expand a functional block in the device interface corresponding to a hardware inp

Strany 155

7. Double-click the Data Point shape for the input network variable, enter a different value, and then click anywhere outside the Data Point shape.

Strany 156

3. The LonMaker Browser opens. It displays the functional blocks in your device interface and the network variables and configuration properties w

Strany 157

channels that use different media (channel types) together. Unlike other devices, routers are always attached to at least two channels. The IzoT R

Strany 158

5. The Network Variable Properties or Configuration Property Properties dialog opens. 6. Verify that the network variable or configuration prop

Strany 159

8. Change network variable and configuration property values and confirm that the device hardware works as designed. For example, toggle a hardware

Strany 160

c. In the New FB Name: property under Functional Block, enter the name for the functional block. The functional block name may be up to 85 alphanum

Strany 161

b. Drag the other end of the Connector shape to the input network variable of the other functional block until it snaps into place and a square box

Strany 162

b. Right-click the new Connector shape it and select Monitor Input Value to display the current value of the input network variable in the connecti

Strany 163

9. Toggle a hardware input to test the connection between the network variables change. Observe the hardware output and the current values of the

Strany 164

232 Testing a NodeBuilder Device Using the LonMaker Tool

Strany 165

10 Debugging a Neuron C Application This chapter describes how the use the NodeBuilder debugger to troubleshoot your Neuron C application. IzoT

Strany 166

Introduction to Debugging You can use the NodeBuilder debugger within the NodeBuilder Project Manager to control and observe the behavior of your de

Strany 167

2. The NodeBuilder debugger opens. 3. The Debug menu appears on the NodeBuilder menu bar and four new panes open in the NodeBuilder project man

Strany 168

Field Description • Standard manufacturer IDs are assigned to manufacturers when they join LONMARK International, and are also published by LONMARK

Strany 169

Debug Device Manager Displays which devices are currently being debugged, and lets you pause and resume the application on each device. If at least

Strany 170

The following table describes each of the buttons in the Debugger toolbar. View Breakpoint List Toggles the breakpoint list pane. See Setting and

Strany 171

Halting an Application You can stop an application while it is running in debug mode by clicking the halt button ( ) on the Debugger toolbar. Altern

Strany 172

Stepping Through Applications You can step through the code in your application one line at a time after you halt the application. You can step into

Strany 173

To add a variable, network variable, or configuration property to the watch list and monitor its value in the Watch List pane, follow these steps: 1

Strany 174

4. If you right-clicked a statement, the drop-down list in the Watch Type box is empty and you need to select one of the following types of variable

Strany 175

Scalar network variables contain a single field that contains their value. If the variable does not exist, a Symbol Not Found dialog opens. 6. Opt

Strany 176

c. Enter the new value for the variable and then click OK. If you are editing the value of an enumerated type, select an enumeration from the list

Strany 177

Stop All Stops debugging all devices, removes all the devices from the Debug Device Manager pane, and closes the NodeBuilder debugger. To restart d

Strany 178

In the Address field, enter the address to start writing in. In the Count field, enter the number of bytes to write. In the Byte field, enter a t

Strany 179

A single network variable may be connected to multiple network variables of the same type but opposite direction. The following example shows the

Strany 180

2. You can set the following options: Default Display Radix Specifies the default format in which data is displayed in the Watch List pane. You ca

Strany 181

Fonts and Colors Specifies the font, font size, and color used for text in the Breakpoint List, Call Stack, and Watch List panes. To change the font

Strany 182

248 Using the NodeBuilder Debugger

Strany 183

Appendix A Using the Command Line Project Make Facility This appendix describes how to use the command line project make facility with the project m

Strany 184 - Using Code Wizard Templates

Using the NodeBuilder Command Line Project Make Facility You can invoke the NodeBuilder build tools from the Windows command line. You can use this

Strany 185 - Version 1 Templates

--defloc <dir> Specifies a directory to search for the default command file. The default command file for the project make facility must be n

Strany 186

-x <nbdt> Indicates that a clean operation will be performed on the specified NodeBuilder device template for the target specified by the –t co

Strany 187

Appendix B Using Source Control With a NodeBuilder Project This appendix describes how to manage a NodeBuilder project using a source control applic

Strany 188 - Introduction to Neuron C

Using Source Control with a NodeBuilder Project When developing a large NodeBuilder project, you can put the project under source control to allow mu

Strany 189

Neuron C Source Files (.nc, .c, and .h) The main source file, <Device Template>.nc, is stored in the C:\Lm\Source\<Project>\<Device Te

Strany 190 - Neuron C Variables

IzoT Commissioning Tool or a customized plug-in created for the device (see the OpenLNS Plug-in Programmer’s Guide for more information on creating O

Strany 191 - Neuron C Declarations

256 Appendix B: Using Source Control with a NodeBuilder Project

Strany 192

Appendix C Glossary This appendix provides definitions for many terms commonly used with NodeBuilder device development.IzoT NodeBuilder User's

Strany 193 - Code Commands

3100 Series Chip The term used to collectively refer to all previous-generation Neuron chips, including the 3150 and 3120 Neuron chips; the 3150 and

Strany 194 - Code Guidelines

Channel The physical media between devices upon which the devices communicate. The LonTalk protocol is media independent; therefore, numerous types

Strany 195

Device A device that communicates on a LONWORKS network. A device may be an application device, network service device, or a router. Devices are so

Strany 196

FT 6000 EVB A LONWORKS evaluation board that uses Echelon’s FT 6000 Smart Transceiver. It features a compact design that includes the following I/O

Strany 197 - Configuration Properties

i.LON IP-852 Router An i.LON IP-852 router forwards ISO/IEC 14908-2 packets enveloped in ISO/IEC 14908-4 packets over an IP-852 channel. i.LON IP-85

Strany 198 - Using the NodeBuilder Editor

IzoT NodeBuilder Tool A hardware and software platform that is used to develop applications for Neuron Chips and Echelon Smart Transceivers. The Iz

Strany 199 - Searching Source Files

LONWORKS 2.0 Platform The next generation of LONWORKS products designed to both increase the power and capability of LONWORKS devices, and to decreas

Strany 200 - Replacing Text

supports the mapping of external non-volatile memory from 0x4000 to 0xDFFF in the Neuron address space (a maximum of 42KB). Neuron Assembler (NAS) A

Strany 201

When a functional block is created from a functional profile, the application designer can determine which of the optional configuration properties a

Strany 202

NodeBuilder Device Template An XML file with a .NbDt extension that specifies the information required for the IzoT NodeBuilder tool to build the dev

Strany 203 - Setting Editor Options

PCC-10 A type II PC (formerly PCMCIA) card network services interface (NSI) that includes an integral FTT-10 transceiver. Other transceiver types ca

Strany 204

SLTA-10 A serial NSI interface with built-in twisted pair transceiver that connects to any host with an EIA-232 (formerly RS232) port. It can also c

Strany 205 - Applications

Target Device A LONWORKS device application that is built by the IzoT NodeBuilder tool. There are two types of targets, development targets and rele

Strany 206

270 Appendix C: Glossary

Strany 207

Appendix D NodeBuilder Software License Agreement When installing the NodeBuilder software, you must agree to the terms of the software license agr

Strany 208

IzoT™ NodeBuilder® Development Tool NOTICE This is a legal agreement between you and Echelon Corporation (“Echelon”). YOU MUST READ AND AGREE TO TH

Strany 209

• “IzoT Device” means a product designed for use in a network based upon Echelon’s IzoT Platform. • “Your Device” means an IzoT Device that you deve

Strany 210

comply with the above restrictions, will result in automatic termination of this license and will make available to Echelon other legal remedies. TER

Strany 211 - Cleaning Build Output Files

MAY NOT APPLY TO YOU. YOU MAY ALSO HAVE OTHER RIGHTS THAT VARY FROM STATE TO STATE AND JURISDICTION TO JURISDICTION. LIMITATION OF LIABILITY IN NO E

Strany 212 - Viewing Build Status

Device manufacturers may also create user resource files that contain manufacturer-defined types and profiles called user network variable types (UNV

Strany 213

IzoT Network Services Applications, or (ii) inform the end-user that there will be no support for Your Devices and Your IzoT Network Services Applica

Strany 215

CONTENTS Preface ... ix Purpose ...

Strany 216

16 Introduction

Strany 217

2 Installing the IzoT NodeBuilder Development Tool This chapter describes how to get started with your IzoT NodeBuilder tool, including how to insta

Strany 218 - C Interface

Installing the IzoT FT 6000 EVK To install your IzoT FT 6000 EVK, follow these steps: 1. Verify that you have a manufacturer ID. A manufacturer ID

Strany 219 - Aardvark

2. Run the IzoT NodeBuilder installer. 3. Run the NodeBuilder430.exe self-extracting installation program. The Welcome window of the NodeBuilder

Strany 220

6. Enter the NodeBuilder serial number on the back of IzoT Commissioning Tool DVD case in the Serial Number box. Optionally, you can enter the fol

Strany 221 - EEPROM or Flash

7. Click Next. If your computer does not have a LONWORKS directory, the Destination Location window appears. Choose a LONWORKS folder in which you

Strany 222

10. Click Install to begin the NodeBuilder software installation. Before installing the IzoT NodeBuilder software, the following programs are auto

Strany 223

13. Once the installation has completed, you will be given the option to view the ReadMe file. See the ReadMe file for updates to the NodeBuilder d

Strany 225

3 IzoT NodeBuilder Quick-Start Exercise This chapter demonstrates how to create an IzoT or LONWORKS device using the IzoT NodeBuilder Development to

Strany 226

FT 6000 Evaluation Boards ... 39 LTM-10A Platform and Gizmo 4 I/O Board ...

Strany 227

IzoT NodeBuilder Quick-Start Exercise The following quick-start exercise demonstrates how to create an IzoT or LONWORKS device with the IzoT NodeBui

Strany 228

1. Create a new IzoT CT network. To do this, follow these steps: a. Click Start on the taskbar, point to Programs, point to Echelon OpenLNS CT, an

Strany 229

f. Select the Network Attached check box and then select the LonTalk/IP network interface you created when you installed your FT 6000 EVK. g. Cl

Strany 230

5. Accept the default NodeBuilder Project Name, which is the same name as the IzoT CT network, and then click Next. 6. Accept the defaults in the S

Strany 231 - Managing Target Devices

3. Click Calculator. The Standard Program ID Calculator dialog opens. 4. Enter the following values for the program ID fields: • In the Man

Strany 232

• In the Device Class (CC:CC) property, select the Multi-I/O module (5.01) option. • In the Usage (UU) property, select the General option. • In t

Strany 233

• If you are using the NodeBuilder FX/PL hardware (LTM-10A Platform with Gizmo 4 I/O Board), select LTM-10A RAM in the Development Build Hardware

Strany 234

Step 3: Defining the Device Interface and Creating its Neuron C Application Framework You can develop device applications with the IzoT NodeBuilder t

Strany 235

• A simple Node Object with no configuration properties (the NodeBuilder Code Wizard automatically creates this functional block). To define your de

Strany 236 - Using the Data Point Shape

c. Rename the openLoopSensor functional block to “Switch”. To do this, right-click the openLoopSensor functional block in the Program Interface pa

Strany 237

3120 and 3170 Neuron Core ... 122 Setting the Hardware Template Description ...

Strany 238 - Using the LonMaker Browser

e. Double-click the nvoValue network variable, or right-click it and then select Properties on the shortcut menu. The NV Properties dialog opens.

Strany 239

2. Create an open-loop actuator with a SNVT_switch network variable. a. Drag a SFPTopenLoopActuator functional profile template from the Resource P

Strany 240

5. Double-click the IzoT NB Example Device.nc file in the Project pane to open the main Neuron C file for this new device template. 6. Open the S

Strany 241

follow the section corresponding with the development platform or platforms you are using for the appropriate code to use. FT 6000 Evaluation Boards

Strany 243

LTM-10A Platform and Gizmo 4 I/O Board 1. Declare the I/O hardware for the Switch following these steps: a. Double-click the Switch.h file in the P

Strany 244

Step 5: Compiling, Building, and Downloading the Application The IzoT NodeBuilder tool includes a complete set of tools for compiling your Neuron C a

Strany 245

CT displays a network drawing that shows the devices, functional blocks, and connections in your network. IzoT CTl also displays stencils that contai

Strany 246

6. Click Next three times. The window in the New Device Wizard lets you select the application image to be downloaded to your device. 7. Select

Strany 247 - Neuron C application

8. The next window lets you set the initial device state and the source of configuration property values when your device is commissioned. 9. Se

Strany 248 - Introduction to Debugging

Neuron C Version 2 Features Not Supported by the Code Wizard 183 Message Tags...

Strany 249

11. Press the service pin on the development platform to be loaded and commissioned. IzoT CT loads the application image for your IzoT NB Example

Strany 250 - Using the Debugger Toolbar

To test your device’s interface with the IzoT Browser, follow these steps: 1. Right-click the IzoT NB Example Device device in your IzoT CT drawing,

Strany 251 - Stopping an Application

4. Press and hold the left button at the bottom of your development board (SW1 on the FT 6000 EVB; IO_6 on the Gizmo 4 I/O Board). The value of the

Strany 252 - Running to the Cursor

3. The NodeBuilder Project Manager appears, and a debug session for the device starts. There is a short pause as the debug session is started whil

Strany 253 - Using the Watch List Pane

6. Right-click the nvoSwitch.state = !input_value line, and then click Toggle Breakpoint on the shortcut menu, or click anywhere in the line and pre

Strany 254

9. Right-click the input_value variable in the line of code in which you set the breakpoint, and then click Watch Variable on the shortcut menu. 1

Strany 255

11. Click Add Watch. The variable is added to the Watch List pane at the bottom of the NodeBuilder Project Manager. This pane displays each of th

Strany 256

16. The NodeBuilder debugger has demonstrated that events occur when the button is both pressed and released. To implement the desired behavior in

Strany 257 - Using the Call Stack Pane

Step 8: Connecting and Testing the Device in a Network Once you determine that your device is functioning as desired, you can test it as part of a ne

Strany 258 - Peeking and Poking Memory

5. Click Finish. The New Functional Block wizard closes and the IzoT CT drawing appears. A new Left Switch functional block shape appears on the

Strany 259 - Setting Debugger Options

Debugging Interrupts for 5000 or 6000 Series chips ... 239 Using Statement Expansion ...

Strany 260

7. Click Finish. The New Functional Block wizard closes and the IzoT CT drawing appears. A new Left LED functional block shape appears on the dra

Strany 261

a. Drag the Connector shape from the NodeBuilder Basic Shapes 4.00 stencil to the drawing. Position the left end of the shape over the tip of the n

Strany 262

b. Right-click the new Connector shape and select Monitor Input Value to display the current value of the nvoSwitch network variable on the Left Sw

Strany 263 - Make Facility

10. Press the left button at the bottom of your development board (SW1 on the FT 6000 EVB; IO_6 on the Gizmo 4 I/O Board) repeatedly to test the co

Strany 264 - Facility

Additional Device Development Steps After you create your device application and successfully test your device in a network, you can perform the foll

Strany 265

b. The Device Properties dialog opens with the Attributes tab selected. This dialog allows you to read and write to the properties of the IzoT CT

Strany 266

e. Set the Location and Ping Interval properties to the values to be saved with the custom device shape in your IzoT CT stencil. See the IzoT CT

Strany 267 - NodeBuilder Project

g. Set the Non-group Receive Timer property to the value to be saved with the custom device shape in your IzoT CT stencil. See the IzoT CT online

Strany 268

3. Create custom functional block shapes. Custom functional block shapes let you provide network integrators with functional block shapes that hav

Strany 269

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 cr

Strany 270

viii Preface

Strany 271 - Glossary

HKEY_LOCAL_MACHINE\SOFTWARE\LonWorks\LonWorks Path The following table lists and describes the files that your installation application should instal

Strany 272

Your installation executable should install your device interface files in a subdirectory labeled with your company name (C:\Program Files (x86)\LonW

Strany 273

68 Creating and Opening IzoT NodeBuilder Projects

Strany 274 - ONWORKS

4 Creating and Opening IzoT NodeBuilder Projects This chapter describes how to create, open, and copy IzoT NodeBuilder projects, and how to copy N

Strany 275

Introduction to the NodeBuilder Project Manager A NodeBuilder project collects all the information about a set of devices that you are developing. Y

Strany 276

Edit Lets you to edit any of the Neuron C source files or header files that are used in the project. See Chapter 7, Developing Device Applications,

Strany 277

Settings Opens the NodeBuilder Project Properties dialog with the Project tab selected. The Project tab displays the project settings. Properties D

Strany 278

Creating a NodeBuilder Project from IzoT CT You can create a NodeBuilder project by starting the NodeBuilder Project Manager from the IzoT Commission

Strany 279 - ONMARK-compliant device

property, and then select the IzoT network interface to be used for communication between the IzoT CT network and your NodeBuilder device in the Netw

Strany 280 - ONWORKS network

8. Specify the following properties: Project Name The name of the project as specified in the Specify New Project Name dialog. This is a read-onl

Strany 281

Preface The IzoT™ NodeBuilder® Development Tool is a complete hardware and software platform that is used to develop applications for Neuron Chips a

Strany 282

Creating a NodeBuilder Project from the New Device Wizard You can create a NodeBuilder project from the New Device Wizard in the IzoT Commissioning T

Strany 283

4. Click Next. The next page in the New Device Wizard lets you select the NodeBuilder device template. 5. Click Start NodeBuilder to create

Strany 284 - 270 Appendix C: Glossary

7. Accept the default Create a New NodeBuilder Project option, and then click Next. 8. Accept the default NodeBuilder Project Name, which is the s

Strany 285 - Agreement

3. In the NodeBuilder Project dialog, select the Open an Existing NodeBuilder Project option and then click Next. 4. The Select NodeBuilder Proj

Strany 286 - Development Tool

• You can open specific windows within the default project by right-clicking a Development Target or Release Target device shape in the IzoT CT draw

Strany 287 - You may:

5. If you have previously associated a IzoT CT network with this NodeBuilder project, it appears in the Project File property. 6. To select a di

Strany 288 - TRADEMARKS

3. In the Database Name property under Existing Network, select the IzoT CT network design associated with the NodeBuilder project to be copied and

Strany 289 - SUPPORT

6. The IzoT CT drawing, IzoT network database, and the NodeBuilder project are all stored in a single IzoT CT backup file (.zip extension) that is s

Strany 290 - GENERAL

11. Click OK. The IzoT CT drawing, IzoT network database, and the NodeBuilder project are copied to the target computer. The NodeBuilder project

Strany 291

5. Copy the user-defined hardware template backup to the C:\Program Files (x86)\LonWorks\NodeBuilder\Templates\Hardware\User directory on the target

Komentáře k této Příručce

Žádné komentáře