Using xdriver interfaces – Echelon LNS User Manual

Page 285

Advertising
background image

LNS Programmer's Guide

271

You should note that if a high performance network interface is replaced with another

high performance network interface, the new network interface will use the same Neuron
ID as the old one.

Changing the network interface’s Neuron ID does not affect the operation of Local or

Lightweight clients. However, if the Neuron ID assigned to a Full client’s network
interface has been modified, it may be necessary to use the PreReplace() method to

replace the Network Service Device when using it to open a network. For more

information on this, see Using the PreReplace Method on page 166.

If the Neuron ID of the active network interface on the PC containing the LNS Server
has changed, a remote Full client using the RemoteNetworks collection may not be able

to connect to the server, since the RemoteNetworks collection may have the old Neuron

ID. In that case the remote Full client can reestablish the connection to the LNS Server
by opening the Networks collection. For more information on using these collections with

remote Full client applications, see Initializing a Remote Full Client Application on page

52.

Using xDriver Interfaces

You can use the OpenLDV xDriver to connect network interfaces such as the

i

.LON 10

Ethernet Adapter and the

i

.LON 100 Internet Server to a L

ON

W

ORKS

network via an IP

network. The OpenLDV xDriver is an integral part of LNS versions 3.07 and higher, and

of OpenLDV Versions 1.0 and higher.

The OpenLDV xDriver can provide authenticated and encrypted connections from an

LNS server to hundreds or even thousands of remote L

ON

W

ORKS

networks through

network interfaces like the

i

.LON 10 Ethernet Adapter and the

i

.LON 100 Internet

Server. As shown in Figure 11.1, the LNS Server accesses each network interface, and

the L

ON

W

ORKS

channels they are using, through a TCP/IP connection.

Figure 11.1 xDriver Overview

Advertising