Echelon LNS - Manual (Page 183)

LNS Programmer's Guide 169
background discovery by setting DiscoveryInterval property to 0.
This is done automatically when the InstallOptions property is set to
lcaSharedMedia.
• Use the confirmed service pin algorithm for device installation. When
using shared media, there is always a small chance that when a service
pin message is received, it is from a device in a neighboring system. The
confirmed service pin algorithm is designed to ensure that devices being
installed belong to the correct system. For more information on this, see
Neuron ID Assignment on page 115.
The above process should greatly minimize the already low probability of installing the
wrong device on a network. Another way to avoid this is to ask the user to explicitly enter
the Neuron ID of each device you install on the network. In all other cases, Echelon
recommends that you perform system-level verification after all connections have been
made when using shared media. If you discover that an incorrect device has been added
to your system, use the Replace() method to associate the AppDevice object with the
correct physical device, as described in Replacing Devices on page 132.
The InstallOptions property must be set before opening the system for the
first time. Setting this property at any other time has no effect. If you initially choose
private media, and decide you want to use shared media later, you can accomplish this by
following these steps:
1. Set the system’s DomainId property to match the Neuron ID of the
Network Service Device that the LNS Server PC is using.
2. Disable automatic discovery and pinging by setting the
DiscoveryInterval and PingIntervals properties to 0.
3. Disable automatic service pin registration by setting the system’s
RegisterServicePin property to False.
NOTE: A L ON W ORKS /IP channel can be considered private media if it is used by a single
network. For each network in a control system, create a separate LonWorks/IP channel
to avoid difficulties common to shared media control networks.
Managing Networks with Multiple Channels
L ON W ORKS networks may contain multiple channels, interconnected by routers or logical
repeaters. This section describes the considerations you need to make when managing a
network with multiple channels. There are several reasons that you might want to use
multiple channels on a network:
• The chosen networking medium for your network has physical layer
constraints, such as wire length or device count, and you want to create a
network that is larger than these constraints would allow if the network
only contained a single channel. Each channel is individually subject to
the physical-layer constraints, but the use of multiple channels allows
you to extend the distance or device count. Segments of a TP/FT-10
channel connected by a physical layer repeater are considered a single
channel.
• The traffic load on your network might approach the channel capacity for
your networking medium. Use of routers can partition the local traffic