Echelon IzoT NodeBuilder - Manual (Page 17)

devices in Compatibility Mode can also communicate with LonTalk devices on different channels as
long as there is a route created between the channels with one or more IzoT routers. In Enhanced
Mode, LonTalk/IP devices cannot communicate with LonTalk devices, even with the use of IzoT
routers.
You can configure the IzoT Router included with the FT 6000 EVK to operate in either Enhanced
Mode or Compatibility Mode. If you are developing devices that will potentially be used with devices
based on the Series 5000 or Series 3100 processors, select Compatibility Mode. If you are developing
devices that will exclusively be used with devices based on Series 6000 processors or other IzoT-
compatible devices such as devices based on the IzoT Device Stack EX, select Enhanced Mode.
BACnet/IP Support
The Series 6000 chips and firmware add support for the BACnet/IP protocol. The BACnet/IP protocol
is the protocol that implements the BACnet services defined by ASHRAE and specified in ISO 16484-
5, with native IP addressing at Layer 3, and link-specific protocols for Layers 1 and 2. The link-
specific protocols may implement compression of the Layer 3 packets depending on the requirements
of the underlying links.
Series 6000 Chip Support
The IzoT NodeBuilder software adds development support for the Series 6000 chips. Development for
Series 5000 and Series 3100 chips is also supported. An FT 6000 Evaluation Board hardware template
file (.NbHwt extension) is included, matching the FT 6000 EVB hardware.
See the FT 6000 EVK Hardware Guide for instructions to emulate the FT 6010 hardware with the FT
6050 Evaluation board. The FT 6010 Evaluation Board hardware template required for this emulation
is included.
An FT 6050 hardware template is included as an example of a typical hardware template for a generic
FT 6050 device.
The Neuron C compiler and its companion tools automatically take advantage of the Series 6000
chips’ features. For example, the Neuron C compiler automatically takes advantage of the extended
address table where available, and the dynamic host configuration protocol (DHCP) is automatically
enabled where supported.
Transient Functions and Automatic Memory Maps
The IzoT NodeBuilder software adds support for transient functions for applications targeting a Series
6000 chip. A transient function is loaded from serial flash memory on demand and automatically
managed by the Neuron firmware, allowing the application’s total code size to exceed the available
physical memory. Functions declared in Neuron C 2.3 compile to transient functions by default, while
when-tasks and interrupt-tasks always compile into resident code.
Individual functions can be made resident with the new Neuron C __resident keyword (note the
leading double underscore characters:
unsigned __resident add(unsigned a, unsigned b) {
return a+b;
}
See the Neuron C Programmer’s Guide for more details about resident and transient functions.
To ease device development and ensure suitable space for transient functions, the Neuron C 2.3 tools
automatically size the memory map to suit the requirements of the Neuron firmware, the Series 6000
chips and your application combined. For these chips, it is no longer necessary to estimate the amount
of volatile memory (“RAM”), persistent data storage (“EEPROM”) or space needed for constant data
and code.
IzoT NodeBuilder User's Guide 3