Echelon LonWorks Router - Manual (Page 90)

Router 5000, the default communications parameters allow you to load an
application image over a 78 kbps network, for example during device
manufacturing. Devices that use a 78 kbps transceiver (such as a 78 kbps EIA-
485 transceiver or an LPT-11 Link Power Transceiver) can use the default
communications parameters within development or manufacturing test
networks. For production networks (networks with many devices), you should
ensure that each device has communications parameters defined for the channel;
use the NodeBuilder FX Development Tool to develop applications with the
correct communications parameters.
Note that devices defined for a TP/XF-1250 channel cannot use the default
communications parameters; each router-half’s external serial non-volatile
memory must be programmed with the correct communications parameters
before connecting to the network.
To create a Series 5000 router configuration that you can program into the Series
5000 router’s EEPROM serial memory, use the NodeBuilder FX Development
Tool to create an NME file:
1. Define a Hardware Template, as described in NodeBuilder Hardware
Template.
2. Define a Device Template, as described in NodeBuilder Device Template.
3. Define the buffer configuration for the router-half, as described in Buffer
Configurations.
4. Use a Neuron C source file to define a well-formed NME router image, such
as the one described in Example Neuron C Source.
Because the NodeBuilder FX Development Tool does not produce an NME file
that allows you control the router mode (configured, learning, repeater) and the
routing tables, the example Neuron C source code defines a minimal application,
with 15 address table entries, zero NV entries, and zero NV alias entries. The
example Neuron C source code places an unused checksum byte out in the
EEPROM space that lies in the Domain:0 Group:80-87 forwarding table. If the
router will be commissioned by an LNS Server, it will clear this byte and set it to
the needed value. If you want to create a preconfigured router image (see
Creating a Pre-Configured NME File), be sure to clear this byte during in the pre-
configuration step.
The router firmware does not use the specific configuration checksum defined in
example Neuron C source code.
NodeBuilder Hardware Template
The hardware template defines the target transceiver configuration in the NME
file produced by the NodeBuilder FX Development Tool. The settings for this
template are (see Figure 40 for an example hardware template for a Router 5000
device):
• Platform: Custom
• Transceiver Type:

Depends on transceiver for a Router 5000
 TP/FT-10 for an FT Router 5000
• Neuron Chip Model:
80 Developing a LONWORKS Router