Specifications

NetLinx Security within the Web Server
124
NetLinx Security - Web Server
- Dynamic application devices that have not been bound to a physical device display
a Bind button. When this button is selected, a secondary display appears with a
listing of all available unbound physical devices that match the application device's
Device SDK class type (FIG. 82).
- If a currently bound device needs to be replaced or a Duet Module needs to be swapped
out, the device should be unbound and the new module/driver should then be bound.
 The administrator/user can then select one of the available physical devices to bind with
the associated application device. When the Save button is selected, the binding is
created and a process begins within the target Master to find the appropriate Duet Module
driver. Once a driver is found, the Duet Module is then started and associated with the
specified application device (Duet virtual device). If the Cancel button is selected, the
binding activity is then aborted.
- A mouse-over popup dialog is provided to display the properties associated with
each discovered physical device that is listed (FIG. 82).
FIG. 82 Manage Device Bindings - showing a listing of all unbound devices
List of available
unbound physical
devices
Discovered
physical device
properties
(displayed via a
mouse-over
popup dialog)
If the manufacturer device does not support Dynamic Device Discovery (DDD)
beaconing, you must use the Add New Device page to both create and manage those
values necessary to add a dynamic physical device. This process is described in
detail within the following section.