85
WebConsole - Modules Options
Configuring Application-Defined Devices
Elements such as
DUET_DEV_TYPE_DISPLAY
and
DUET_DEV_POLLED
are defined within the NetLinx.axi file.
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_DISPLAY
).
NOTE:
Physical device names are typically prefixed with “dv” and Virtual device names are typically prefixed with “vdv”.
Example Code:
PROGRAM_NAME=’DDD’
DEFINE_DEVICE
COM1 = 5001:1:0
COM2 = 5001:2:0
dvDisplay = 41001:1:0 dvVideoProjector = 41002:1:0
DEFINE_CONSTANT
DEFINE_TYPE
DEFINE_VARIABLE
DEFINE_START
STATIC_PORT_BINDING(dvDisplay, COM1, DUET_DEV_TYPE_DISPLAY, ‘statbcc Display’, DUET_DEV_POLLED)
DYNAMIC_POLLED_PORT(COM2)
DYNAMIC_APPLICATION_DEVICE(dvVideoProjector, DUET_DEV_TYPE_VIDEO_PROJECTOR, ‘statbcc Serial Projec-
tor’)
(***********************************************************)
(* THE EVENTS GO BELOW *)
(***********************************************************) DEFINE_EVENT
DATA_EVENT [dvVideoProjector]
{
// Duet Virtual device data events go here }
You can find this example code within the DEFINE_START section of your code. This code is reflected in the first two entries listed
in FIG. 87. The code gives the Master a “heads-up” notification to look for those devices meeting the criteria outlined within the
code.
Instruction Manual - Incite Digital Video Presentation Systems
