![background image](http://html1.mh-extra.com/html/amx/fg2105-08/fg2105-08_operation-reference-manual_2937837116.webp)
NetLinx Security within the Web Server
110
NI-3101-SIG Signature Series NetLinx Integrated Controller
3.
To configure a Dynamic application interface:
Add the DYNAMIC_APPLICATION_DEVICE API call to the section of the NetLinx
program (FIG. 65 on page 104) containing the Duet Virtual Device D:P:S, the Duet Device
type constant, and the associated friendly name string.
-
DYNAMIC_APPLICATION_DEVICE
specifies a Duet device that is completely
dynamic. A dynamically discovered device matching the specified deviceType could
be bound to the duetDevice from anywhere in the system.
DYNAMIC_APPLICATION_DEVICE (DEV duetDevice, char[] deviceType,
char[] friendlyName)
Add the DYNAMIC_POLLED_PORT API call for any NetLinx physical device D:P:S's that
should be polled to discover connected devices.
-
DYNAMIC_POLLED_PORT
designates a NetLinx serial port that should be polled
for dynamic device detection. This API must be called for each serial port that
can dynamically have a device plugged into it.
DYNAMIC_POLLED_PORT (DEV netlinxDevice)
4.
Write the remainder of the NetLinx application to communicate with the device via the Duet Virtual
Device (D:P:S) using the Standard NetLinx API for that device type.
5.
Compile the program file and then download it to the target Master via the
Tools > File Transfer
dialog.
6.
Run the NetLinx application on the target Master.
How do I configure a Run-time installation
To utilize Dynamic binding, execute step 1 then step 2 then proceed to Step 3.
To utilize Static binding, execute step 2 then step 1 because the static bindings will try to bring up the
Duet module as soon as the device is discovered. The module should be already available on the Master.
1.
Connect the device to the system.
If the device is a DDD enabled Serial or IP device, then the device will be automatically
discovered and show up in the Master's View Discovered Devices UI page under Manage
Other Devices. (FIG. 68 on page 106).
If the device is not DDD enabled and/or cannot be automatically discovered (ex. IR device)
the installer must enter the device information into the Master via the User Defined Device
Web page under manage Other Devices. (FIG. 70 on page 108)
2.
Verify the appropriate Duet module is available.
If the Master is connected to the Internet, the
Module Search via Internet
button
(FIG. 63 on page 97) can be enabled (
via toggling
).
From within the View Discovered Devices UI page, click the
Search
button adjacent to the
appropriate device to begin the search of an appropriate module.
Any available modules on either the amx.com, AMX's partner website, or within the physical
device itself are downloaded to the Master and then displayed back within the Select Device
Module page (FIG. 69 on page 107). The discovered device is then shown with an adjacent
listing of available modules ranked with associated "match" score.
- The location of these modules can be either indeterminate (in which case they will
reside on the amx.com website) or in some cases be required by the manufacturer to
reside in their own specific source location (such as the manufacturer’s own website
or found within the target unit itself).