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

NetLinx Security within the Web Server
91 NI-3101-SIG Signature Series NetLinx Integrated Controller
1. Decide whether the application interface is to be Dynamic or Static bound and how the device will be
connected to the system (Serial, IP, IR, etc).
 Refer to page 87 for a definition of Static and Dynamic Application devices.
2. To configure a Static application interface:
 Add the NetLinx STATIC_PORT_BINDING API call to the section of the NetLinx program
(FIG. 67 on page 86) containing the: Duet Virtual Device D:P:S, the NetLinx physical device
D:P:S, the Duet Device type constant, and the associated friendly name string.
- STATIC_PORT_BINDING designates an application device along with its SDK class
and the physical interface it is bound to. The complete API is:
STATIC_PORT_BINDING (DEV duetDevice, DEV netlinxDevice, char[]
deviceType, char[] friendlyName, integer polled)
 Determine whether the physical device D:P:S should be polled to discover the connected devices.
Only serial ports should be polled. Polled is a boolean integer which is part of the NetLinx AXI
file.
3. To configure a Dynamic application interface:
 Add the DYNAMIC_APPLICATION_DEVICE API call to the section of the NetLinx program
(FIG. 67 on page 86) 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. 70 on page 88).
 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. 72 on page 89)
2. Verify the appropriate Duet module is available.
IP devices cannot be statically bound because they do not have an associated
NetLinx D:P:S port value to associate with the application device.