Specifications

NetLinx Security within the Web Server
117
NetLinx Security - Web Server
Manage Other Devices Page
Feature Description
Dynamic Device Discovery links: These links direct the user to additional Dynamic Device
Discovery (DDD) configuration pages which include:
• Manage Device Bindings page is used for configuring
application-defined Duet virtual devices by using discovered
physical devices.
- If your current NetLinx program (running on the target Master)
has been written, and you have notified the Master of a set of
Dynamic Devices on your system, you will then want to start
by managing those devices through this page.
• Create User Defined Device page provides a Web interface
used in creating and managing the values necessary to add a
dynamic physical device to the system. The devices added on
this page do not support the DDD beaconing technology.
- If after you have confirmed the presence of your programmed
Dynamic Devices (provided to the Master via your NetLinx
code), and have allowed the Master to confirm the presence
of any other Dynamic Devices, its then time to manually enter
in those remaining devices on your system via the User
Defined Device page.
Note: IR-controlled devices (such as a VCR or Receiver)
must always be User-Defined devices.
• View Discovered Devices page displays a listing of all the
dynamic devices that have been discovered within the system.
- After you have confirmed the presence of those previously
coded Dynamic Devices within the Manage Device Bindings
page, it is then recommended that you navigate to the View
Discovered Devices page to continue the process of detecting
Dynamic Devices which have been detected by the system,
and then assign Module/drivers to those devices via the View
Discovered Devices page.
Configure Binding Options: This section contains configuration settings regarding the DDD
process.
Enable Auto Bind • This selection allows an end-user to toggle the state of the
automatic binding for DDD (On/Off).
• When auto-binding is enabled, the Master automatically
attempts to connect any newly discovered device with an
associated application device (defined in the running NetLinx
application).
• Auto-binding can only be accomplished if the Master's firmware
determines a one-to-one correlation between the newly
discovered device and a single entry within the list of defined
application devices (accessed by pressing the Manage Device
Bindings button at the top of the page).
• For example, if the application only has one VCR defined and a
VCR is detected in the system, auto-binding can then be
accomplished.
- If there were two VCRs defined within the application,
auto-binding could not be completed due to the lack of
a clearly defined one-to-one correspondence.
• When the Enable Auto Bind option is not selected, no
auto-binding activity takes place and all binding of the newly
discovered devices must be accomplished manually via the
Web control interface Manage Other Devices - Manage Device
Bindings section on page 121.