Specifications

NetLinx Security within the Web Server
119
NetLinx Security - Web Server
What is Dynamic Device Discovery?
The Dynamic Device Detector (DDD) monitors the system for newly connected devices. New
devices can be detected via either an external discovery protocol manager (built into firmware
build 320 or higher), Multicast reception of a Dynamic Device Beacon, or via the receipt of a
beacon response on an application specified list of serial devices. This DDD process begins by
detecting new devices within a NetLinx/Duet system, binding those devices to application
instances, and then starting a Duet module to control those new devices.
Manage Other Devices Page (Cont.)
Feature Description
Manage Device Modules: This section displays a list of all currently loaded Duet Modules/
.JAR files on the Master (resident within the /unbound directory);
as well as providing those interfaces necessary to delete, add,
and retrieve these modules.
Select File to Delete • This field provides the listing of loaded Modules/.JAR files.
• These entries can be selected for deletion or archiving.
Delete Selected • Clicking this button causes the deletion of a selected module
from the /unbound directory.
• Any corresponding module within the /bound directory will NOT
be deleted. Bound modules must be deleted via the Purge
Bound Modules on Reset selection described within the
previous Configure Device Bindings section.
Archive Selected • Clicking this button copies the selected JAR file to the PC which
the user is browsing from.
• This option allows an administrator to archive those Duet
Modules resident on a target Master back to a PC.
Select File to Upload • This section allows a user to browse for a target Module/.JAR
file and then upload it to a target Master.
• Browse: Allows the user to browse for Duet Modules on the
PC/Network.
• Upload File: Copies the specified Duet Module to the target
Master's /unbound directory.
- If a file of the same specified name already exists within the
/unbound directory; a prompt is displayed to confirm the
over-write of the existing .JAR file. Only JAR file types are
allowed for Upload to the target Master.
FIG. 79 System Settings - AMX License Agreement page
Accept button