AMX NetLinx Integrated Controllers NI-3000 - Manual (Page 115)

Programming
109 NetLinx Integrated Controllers
Programming
This section describes the Send_Commands, Send_Strings, and Channel commands you can use to
program the Integrated Controller. The examples in this section require a declaration in the
DEFINE_DEVICE section of your program to work correctly. Refer to the NetLinx Programming
Language instruction manual for specifics about declarations and DEFINE_DEVICE information.
Converting Axcess Code to NetLinx Code
In order to compile your existing Axcess code to NetLinx code, minor modifications will be
required. These modifications include identifier names that conflict with NetLinx identifiers,
warning on variable type conversions, and stricter syntax rules.
For more information on NetLinx standards and conversion recommendations, go to
www.amx.com and click on Dealers > Tech Center > Tech Notes. You can either search for the
documents (such as NetLinx Programming Standards and Converting Axcess Code to NetLinx
Code) or Tech Notes (TN numbers: 186, 249, 261, and 310).
Refer to the NetLinx Programming Instruction Manual for more detailed information on the
differences between the two codes and how they can be re-written. The section is called Converting
Axcess Code to NetLinx Code.
Using the ID Button
The ID Button on the rear panel of the Integrated Controller is used in conjunction with the
NetLinx Studio 2.2 software program to allow you to assign new Device and System numbers for
the Integrated Controller.
1. Using NetLinx Studio 2.2, place the system in Identity (ID) Mode. ID Mode means the entire
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 the Integrated Controller). The device that generates
the first event is the identified device.
2. Press the ID Mode button to generate an event from the Integrated Controller and assign new
device and system numbers in NetLinx Studio.
Device:Port:System (D:P:S)
A device is any hardware component that can be connected to an AXlink or ICSNet bus. Each
device must be assigned a unique number to locate that device on the bus. The NetLinx
programming language allows numbers in the range 1-32,767 for ICSNet (255 for AXlink).
NetLinx requires a Device:Port:System (D:P:S) specification. This D:P:S triplet can be expressed
as a series of constants, variables separated by colons, or a DEV structure.
Only the Device number can be changed on the Controllers using the ID button.
Port and System can not be defined.