Echelon OpenLDV - Manual (Page 16)

8 Introduction
Table 1. NI Application Settings
Network
Interface
NI Application Setting for
Layer 2 Image
NI Application Setting for
Layer 5 Image
PCC-10 PCC10VNI NSIPCC
PCLTA-20 PCL10VNI NSIPCLTA
PCLTA-21 PCLTA21VNI PCLTA21NSI
The L ON W ORKS Interfaces application is installed with the OpenLDV driver.
For additional information about developing an OpenLDV application, see the
following chapters:
• Chapter 2, Using the OpenLDV API, on page 9. This chapter describes
each function that is included in the OpenLDV API. It also defines
guidelines for writing applications that use the OpenLDV API to access
multiple network interfaces.
• Chapter 3, Sending and Receiving Messages with the OpenLDV API, on
page 57. You can use the ldv_write() and ldv_read() functions
described in Chapter 2 to send and receive message commands through a
network interface. This chapter describes the various network interface
commands that your OpenLDV application can send and receive with
these functions, as well as the application buffer structure for each type
of message.
• Chapter 4, The OpenLDV Developer Example, on page 89. This chapter
introduces the OpenLDV Developer Example, which is installed with the
OpenLDV SDK. It describes various classes implemented in the
OpenLDV Developer Example. In addition to reviewing the code, you
should also review the code comments in the example.
Getting Started with the xDriver Component
The xDriver component is included with the OpenLDV driver. xDriver supports
scalable access to many network interfaces. The default xDriver implementation
uses a Lookup component that uses the Windows Registry to store a database
containing the information that it requires to connect to each device. For small-
scale deployments, the Windows Registry is an efficient information store for the
xDriver database.
However, for larger deployments (more than 50 network interfaces), you can
improve performance by extending the default xDriver component to use a
database as your information store.
If you do not plan to extend the default xDriver component to use a database, you
can begin using the default xDriver component, as described in Chapter 5, Using
the xDriver Default Profile, on page 93.
If you plan to extend the default xDriver component, see Chapter 6, Extending
xDriver, on page 99. Most developers will not need to extend xDriver.