Recommended netlinx device numbers – AMX Signature Series NetLinx Integrated Controller NI-3101-SIG User Manual
Page 31
Configuration and Firmware Update
21
NI-3101-SIG Signature Series NetLinx Integrated Controller
Recommended NetLinx Device Numbers
Using the ID Button to Change the Controller’s Device Value
Use the ID Button on the rear panel (in conjunction with ID Mode function in NetLinx Studio) to establish a
NetLinx Device ID for the device.
The steps described and the dialogs shown in this section are in the NetLinx Studio application.
NetLinx Studio is available to download from www.amx.com.
Refer to the NetLinx Studio on-line help for information on using NetLinx Studio.
1.
Access the Device Addressing dialog (FIG. 18) by selecting Diagnostics > Device Addressing.
2.
Enter the system number in the Destination System field.
3.
Enter the desired device number in the Change to Device box (Device field), and again enter the system
number (in the System field).
4.
Click the Start Identify Mode button. This action activates Identify Mode on the named System.
The Device Addressing dialog displays the "Waiting...Press Cancel to Quit..." message, indicating that
Identify Mode is currently active (NetLinx Studio is waiting to detect a device - FIG. 19).
• 1 - 255
• Axcess Devices use Axcess standards
• 301 - 3072
• NetLinx CardFrames start at frame number 25 - (frame# * 12) + Card #
• 5001 - 5999
• ICSNet NetLinx devices: NXI, NXM-COM2, NXM-IRS4, etc.
• 6001 - 6999
• ICSNet Landmark devices: PLH-VS8, PLH-AS16, PLB-AS16
• 7001 - 7999
• InConcert Devices
• 8001 - 8999
• PCLink Device: PCLink devices are PC programs
• 10000 - 31999
• ICSNet Panels: DMS, IMS, and future panels
• 33001 - 36863
• Virtual devices: these start at 33001
• 32001 - 32767
• Dynamic devices: the actual range used by Master
• 32768 - 36863
• Virtual devices: the actual range used by Master
FIG. 18
Device Addressing dialog
"Identify Mode" means that the system is put on hold while it waits for an event from
any NetLinx device in the named system (for example, pushing the ID button on a
NetLinx device). The device that generates the first event is the device that gets
identified.