NetLinx Security within the Web Server
109
NI-3101-SIG Signature Series NetLinx Integrated Controller
6.
Enter the name of the manufacturer for the device being used (up to 55 alpha-numeric characters)
(ex: Sony, ONKYO, etc.) into the
Make
field.
Either the GUID or Make/Model must be specified
within this field
.
Note that spaces in the name will be converted to underscores.
7.
Enter the model number of the device being used (up to 255 alpha-numeric characters)
(ex: Mega-Tuner 1000) into the
Model
field.
Either the GUID or Make/Model must be specified
within this field
.
8.
Enter the firmware version used by the target device into the
Revision
field.
Text is required within
this field.
The version must be in the format:
major.minor.micro
(where major, minor, and micro are
numbers). An example is:
1.0.0
(revision 1.0.0 of the device firmware).
9.
Once you are done creating the profile for the new device, click the
New
button to assign additional
Name
and
Value
property information for association with the new User Defined Device.
When the
Add
button is selected, the user-defined device is then inserted into the list of
discovered physical devices which appears within the lower section of the display (FIG. 70).
When the
Cancel
button is selected, the addition of the user defined device is aborted,
no amendment to the existing list is made, and the user is returned back to the
Manage Device
Bindings
page.
10.
Once you have finished entering your devices, click the
Back
button (from within the
Manage
Device Bindings
page) and then navigate to the
View Discovered Devices
page to view the listing of
all Dynamic Devices discovered in the system.
How do I write a program that uses Dynamic Device Discovery
These procedures assume the NetLinx developer does not have the Manufacturer device information
necessary at the time of the initial setup. For more detailed UI information, refer to the
Manage Other
Devices - Manage Device Bindings
section on page 102. For information on the referenced NetLinx
calls, refer to the NetLinx Keywords Help file (found within NetLinx Studio).
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 103 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. 65 on page 104) 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.
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.
