NodeBuilder™ Release Notes
Release 4.4 Update 2, April
2021
Copyright
© 1998 – 2021 Dialog Semiconductor Corporation
All Rights Reserved
The NodeBuilder software provides software development tools for Dialog Series 6000, 5000, and 3100 Smart Transceivers and Neuron Chips. The NodeBuilder software requires the Dialog IzoT Commissioning Tool and 32-bit Microsoft Visio software.
You can use the NodeBuilder software with the Dialog FT 6050 EVK. The FT 6050 EVK is a complete hardware and software development platform for creating LON™, LON/IP, and BACnet FT devices based on Dialog Series 6000, Series 5000, and Series 3100 Neuron™ Chips and Smart Transceivers.
The following sections describe NodeBuilder 4.4 Update 2 (NodeBuilder version 4.40.14 with 8-Apr-2021 exporter):
· Requirements
· Releases
· Getting Started
· Changes
· Warnings
See Getting Started below for installation instructions, including the required serial number and installation instructions for the updated exporter. For additional documentation, see the Resources listing at https://www.dialog-semiconductor.com/products/communications/free-topology/ft-6050-evk. For the latest software updates, see http://iecdocs.diasemi.com/display/PortTL/IzoT+NodeBuilder.
Hardware and software requirements for computers running the IzoT NodeBuilder tool are listed in the IzoT NodeBuilder User’s Guide.
This ReadMe document applies to the IzoT NodeBuilder 4.4 Updagte 1 software. You can find your version of the NodeBuilder software by starting the NodeBuilder project manager, opening the Help menu, and then clicking About NodeBuilder. The About NodeBuilder dialog appears. This dialog displays the version number of your NodeBuilder software. The following table summarizes the IzoT NodeBuilder software release history:
Name |
Number |
Date |
IzoT NodeBuilder 4.3 |
4.30.47 |
July 2014 |
IzoT NodeBuilder 4.3 SR1 |
4.30.52 |
September 2014 |
IzoT NodeBuilder 4.3 SR2 |
4.30.53 |
October 2014 |
IzoT NodeBuilder 4.3 SR3 |
4.30.55 |
January 2015 |
IzoT NodeBuilder 4.3 SR4 |
4.30.60 |
October 2015 |
IzoT NodeBuilder 4.3 SR5 |
4.30.61 |
November 2015 |
IzoT NodeBuilder 4.3 SR6 |
4.36.01 |
January 2016 |
IzoT NodeBuilder 4.3 SR7 |
4.37.01 |
February 2016 |
IzoT NodeBuilder 4.3 SR 8 |
4.38.02 |
July 2016 |
IzoT NodeBuilder 4.4 |
4.40.10 |
April 2018 |
IzoT NodeBuilder 4.4 |
4.40.11 |
July 2018 |
IzoT NodeBuilder 4.4 |
4.40.12 |
January 2019 |
IzoT NodeBuilder 4.4 |
4.40.13 |
May 2019 |
IzoT NodeBuilder 4.4 Update 1 |
4.40.14 |
October 2019 |
IzoT NodeBuilder 4.4 Update 2 |
4.40.15 with Neuron Image Exporter dated 8-Apr-2021 |
April 2021 |
To get started with the NodeBuilder software, follow these steps:
1. Install
a 32-bit version of Microsoft Visio. Microsoft Visio is required for the IzoT Commissioning
Tool (CT). You cannot install 32-bit Visio on a computer with 64-bit Microsoft
Office. If you have 64-bit Office, uninstall it before installing Visio.
2. Install
IzoT CT. IzoT CT is required for the NodeBuilder software.
3. Download
the NodeBuilder software from http://iecdocs.diasemi.com/display/PortTL/IzoT+NodeBuilder.
4. Extract
the files from the NodeBuilder zip archive.
5. Run
the NodeBuilder.exe application to start the NodeBuilder software
installation. You can install the NodeBuilder software on the same computer
with an earlier version of the NodeBuilder software. The new NodeBuilder
software will delete any prior installations.
6. When
you are prompted for a serial number, enter the following serial number:
0750B72-70020
7. Copy
the LonNex32.dll file that you extracted in step 4 to the LonWorks bin
directory. The default LonWorks bin directory is c:\Program Files
(x86)\LonWorks\bin, but you may have changed that for your installation. The
new LonNex32.dll file has the same version number as the version you
will replace, but has a newer 8-Apr-2021 file creation date.
8. See
the IzoT Commissioning Tool User’s Guide and the IzoT NodeBuilder
User’s Guide for details on using IzoT CT and NodeBuilder. These manuals
are installed on your computer when you install the IzoT CT and NodeBuilder
software. You can find the documents online on the following pages:
http://iecdocs.diasemi.com/display/PortTL/IzoT+NodeBuilder
http://iecdocs.diasemi.com/display/PortTL/IzoT+CT+and+OpenLNS+CT
9. If
you are using the IzoT WireShark Plug-in, update your WireShark software to
version 1.12 or newer. The version of the IzoT WireShark plug-in included
with SR2 and newer will not work with versions of WireShark prior to 1.12.
10. If you created any custom devices with Neuron firmware 21.03.07 included with the original NodeBuilder 4.3 software, or with Neuron firmware 21.03.09 included with the NodeBuilder 4.30 SR1 software, or if you have an FT 6000 EVBs shipped prior to October 2014 that are running Neuron firmware version 21.03.09 or earlier versions, then update the firmware in your devices or EVBs to match the new Neuron firmware 21.04.08 firmware included with the service release. To update the firmware in your devices or EVBs, follow these steps:
1. If you do not already have a current version of NodeLoad or NodeUtil, download and install one of the utilities from www.echelon.com/downloads. If you are downloading NodeUtil, also download the latest NodeUtil Node Utility User’s Guide. NodeLoad is easier to use for just downloading images to device, whereas NodeUtil provides other useful tools for device developers, including tools for verifying Neuron firmware version numbers.
2. Download the
following boot loader file with NodeLoad or NodeUtil:
<LonWorks>\images\ver21\bla6000.ndl
Enter your LonWorks directory for <LonWorks>. By default,
the LonWorks directory is C:\Program Files (x86)\LonWorks or C:\LonWorks
depending on which Echelon software you previously installed on your computer.
To download with NodeLoad, enter NodeLoad /? to display help. To
download with NodeUtil, see the NodeUtil documentation for the Y
command.
3. Download the
following Neuron firmware image file with NodeLoad or NodeUtil:
<LonWorks>\images\ver21\b6050v4.ndl
4. If you are using NodeUtil, you can verify the firmware version number with the S command.
5. Rebuild any applications you created for your custom devices or FT 6000 EVBs using Neuron firmware version 21.04.08.
The following enhancements and fixes are included in IzoT NodeBuilder 4.4 Update 2
The following fixes are included in IzoT NodeBuilder 4.4 Update 1
The following fixes are included in IzoT NodeBuilder 4.4
The following fixes are included in IzoT NodeBuilder 4.3 SR8.
The following fixes are included in IzoT NodeBuilder 4.3 SR7.
LodInitSettings lis = {0x80, 0x0F00, 0x07};
Then the backward compatible code would be:
LodInitSettings lis = {0x80, 0x0F};
Yes, this allocates more sectors (0x0F) than originally intended (0x07), but it will do so in a way that matches what actually occurred in the old device. [NDB-5674]
The following enhancements are included in IzoT NodeBuilder 4.3 SR6.
This error has been corrected; IzoT NodeBuilder Hardware Template Editor reads “neuron.xml” data correctly, regardless of local and regional settings. [NDB‑5661]
This error has been corrected and the network kernel debugger’s message buffer is correctly accounted for. [NDB-5662]
The following enhancements are included in IzoT NodeBuilder 4.3 SR5.
The following enhancements are included in IzoT NodeBuilder 4.3 SR4.
The following problems were fixed in IzoT NodeBuilder 4.3 SR3.
The following problems were fixed in IzoT NodeBuilder 4.3 SR2.
The following problems were fixed in IzoT NodeBuilder 4.3 SR1:
· Power failure recovery has been improved when downloading an NDL file. (NDB‑5409)
· Network variables bound using the alias table (such as can occur with fan out connections) were not always updated properly. (NRNFW-509)
· Memory was sometimes corrupted when loading large applications. (NRNFW-500)
· Memory allocated for sending a message was sometimes not freed if application_restart() was called while sending a message. (NRNFW-498)
· If an application contained eeprom far data and all of it was declared as uninitialized (uninit without any explicit initializers), the exporter sometimes crashed when creating the NEI or NDL files. Variables declared with the uninit eeprom far attributes variables and not explicitly initialized are now initialized to zero in the NMF file. (NDB-5466)
· The NME file generated by the NodeBuilder software for programming serial EEPROM memory parts for a Series 5000 Smart Transceiver or Neuron Chip was sometimes corrupted, preventing the device from operating correctly. (NDB-5462)
· Open Media Authentication (OMA) could be enabled for targets with version of Neuron firmware prior to version 14 that do not support OMA. (NDB-5462)
· Linker errors were reported by the retrieve_stat() function for the _stats_unlock and _stats_lock symbols. (NDB-5460)
· An incorrect offset out-of-range error was sometimes reported when compiling an application. (NDB-5423)
Following are warnings for NodeBuilder.
The NcMultiSensorExample, NcSimpleIsiExample, and NcSimpleExample examples for the FT 5000 Smart Transceiver fail to compile—the examples for the FT 6050 Smart Transceivers compile correctly. Workaround: No workaround is required if you are building the FT 6050 examples for an FT 6050 Smart Transceiver. To rebuild the FT 5000 examples for an FT 5000 Smart Transceiver, replace all include directive double backslashes with single backslashes. (NDB-5384)
The LON/IP default domain for ISI is 0x49.53.00 ("IS\0"). This is a change from the original ISI default domain of 0x49.53.49 ("ISI"). Workaround: To use the LONk/IP default ISI domain, no workaround is required. To create ISI devices operating on the original ISI default domain of 0x49.53.49 (“ISI”), assign the 0x49.53.49 primary domain ID by overriding the IsiGetPrimaryDid() callback function.
If DHCP is enabled and an IP address is assigned by a DHCP server, the Neuron firmware will use the IP address assigned by the DHCP server, and will not use the default ISI domain. Workaround: To use the default ISI domain, use the #pragma dhcp disabled directive to disable the DHCP client for your devices when using ISI. (NDB‑5337)
The IzoT CT Browser sometimes displays a system error when started after installation. Workaround: Restart Windows to complete the installation. (LMWIN-1930)
After restoring the IzoT NcMultiSensor example network, you must specify the NodeBuilder project. When prompted whether to create a new or open an existing project, select Open an Existing Project and browse to the NcExamples.NbPrj project located in your local C:\Users\Public\Documents\LonWorks\OpenLnsCt\Source\FT 6000 EVB folder. (NDB-5374)
When building a device with BACnet FT support, the examples include a file blonsys.h. blonsys.h references a variable of type TSciRates, which is defined in io_types.h, so within your own project, before including blonsys.h, also include io_types.h (NDB‑5668).
The “IO Model Reference for Smart Transceivers and Neuron Chips” implies that using the __slow keyword gets you an SCL rate of 100 kbps, and the __fast keyword gets you a 400 kbps rate. While this is true with a system clock of 80 MHz, note that the SCL clock rate scales with the system clock rate (NDB-5663).
The “6000 Series Chip Data Book” claims that for the flash memory interface, the 100k pull-down on MISO can be omitted. Instead, this pull-down is required (NDB‑5656).
IzoT CT requires the 32-bit version of Microsoft Visio. Existing installations of the 64-bit version of Microsoft Visio can cause Izot NodeBuilder not to install correctly. Running IzoT NodeBuilder causes runtime errors in reference to missing dynamic link libraries (DLL).
Uninstall Microsoft Visio and re-install it from the Open CT installation media provided. Then execute the "repair" option with the IzoT NodeBuilder installer from the Windows Control Panel. [NDB-5750]
Dialog, Adesto, Echelon, LON, the Dialog logo, the Adesto logo, the Echelon logo, LonWorks, NodeBuilder, LonTalk, LonPoint, Neuron, 3120, 3150, LNS, i.LON, ShortStack, LonMaker, IzoT, OpenLDV, LonScanner, and LonBridge are trademarks of Dialog Corporation that may be registered in the United States and other countries. For a complete list of registered trademarks see the Dialog web site at www.dialog-semiconductor.com. All rights reserved.
Other trademarks belong to their respective holders.