AMX Signature Series NetLinx Integrated Controller NI-3101-SIG - Manual (Page 98)

NetLinx Security within the Web Server
88 NI-3101-SIG Signature Series NetLinx Integrated Controller
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. 69).
Manage Other Devices Menu - Viewing Discovered Devices
This page (FIG. 70) provides a listing with all of the dynamic devices that have been discovered in the system.
Mousing-over a listed entry presents a popup which displays all of the properties associated with the physical
device. If the physical device is bound to an application device, the associated application device's “friendly
name” will be displayed in the Binding column. The Module Available column indicates if a Duet module is
currently available on the system for the target physical device (the results are: yes, no, or unknown).
For each physical device, a Search button is provided which initiates a search for compatible modules.
 If the Module Search via the Internet option has been previously enabled (via the corresponding
button within the Configure Binding Options section of the Manage Other Devices page ), the
search includes a query of the AMX online database for a compatible module based on the device's
properties.
 If the device specified a URL in its DDD beacon, the file is retrieved from the URL either over the
Internet or from the physical device itself, provided the device has an inboard HTTP or FTP server.
 If Module Search via Internet is NOT enabled, the search does NOT query the AMX online
database nor will it pull any manufacturer specified URLs that do not match the IP Address of the
physical device itself.
Modules that are retrieved from either the Internet or from the manufacturer's device are then placed into the /
unbound
directory and automatically overwrite any existing module of the same name.
Once a list of all compatible modules is compiled, the Select Device Module page (FIG. 71) is then displayed
with a listing of each module along with its calculated “match” value. The greater the “match” value, the better
the match between the Duet Module's properties and the physical device's properties.
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.
FIG. 70 View Discovered Devices page
Properties of the
discovered physical
device
(displayed via a
mouse-over
popup dialog)
Listing of the discovered
Dynamic Devices