Filter
Top Products
NetLinx Security within the Web Server
85
NI-3101-SIG Signature Series NetLinx Integrated Controller
Manage Other Devices - Manage Device Bindings
To access this page, click on the Manage Device Bindings button (from within the Manage Other Device
page). This page is used to configure application-defined Duet virtual devices with discovered physical
devices. The on-screen table (FIG. 68) displays a list of all application-defined devices (including the defined
"friendly name"), the Duet virtual D:P:S, and the associated Duet Device SDK class (indicating the type of the
device). This information would have been pre-coded into the NetLinx file currently on the target Master
(FIG. 67).
Configuring application-defined devices
Elements such as DUET_DEV_TYPE_DISC_DEVICE and DUET_DEV_POLLED are defined within the
NetLinx axi. The latest version of the NetLinx.axi file contains both the new API definitions, as well as the
pre-defined constants that are used as some of the API arguments (ex: DUET_DEV_TYPE_DISC_DEVICE).
Sample code can be found within the DEFINE_START section seen in FIG. 67:
PROGRAM_NAME='DDD'
DEFINE_DEVICE
COM1 = 5001:1:0
COM2 = 5001:2:0
dvRECEIVER1 = 41000:1:0
dvDiscDevice = 41001:1:0
DEFINE_CONSTANT
DEFINE_TYPE
DEFINE_VARIABLE
DEFINE_START
STATIC_PORT_BINDING(dvDiscDevice, COM1, DUET_DEV_TYPE_DISC_DEVICE,
'My DVD', DUET_DEV_POLLED)
DYNAMIC_POLLED_PORT(COM2)
DYNAMIC_APPLICATION_DEVICE(dvRECEIVER1, DUET_DEV_TYPE_RECEIVER,
'My Receiver')
(***********************************************************)
(* THE EVENTS GO BELOW *)
(***********************************************************)
DEFINE_EVENT
DATA_EVENT [dvRECEIVER1]
{
// Duet Virtual device data events go here
}
Physical device names are typically prefixed with "dv" and Virtual device names are
typically prefixed with "vdv". It is recommended that anyone working with these
modules should become familiar with this naming convention.