7.DO NOT block any ventilation openings. Install in accordance with the manufacturer's instructions.
8.DO NOT install near any heat sources such as radiators, heat registers, stoves, or other apparatus (including amplifiers) that
produce heat.
9.DO NOT defeat the safety purpose of the polarized or grounding type plug. A polarized plug has two blades with one wider than the
other. A grounding type plug has two blades and a third grounding prong. The wider blade or the third prong are provided for your
safety. If the provided plug does not fit into your outlet, consult an electrician for replacement of the obsolete outlet.
10. PROTECT the power cord from being walked on or pinched, particularly at plugs, convenience receptacles, and the point where
they exit from the apparatus.
11. ONLY USE attachments/accessories specified by the manufacturer.
12. USE ONLY with a cart, stand, tripod, bracket, or table specified by the manufacturer, or sold with the apparatus. When a cart is
used, use caution when moving the cart/apparatus combination to avoid injury from tip-over.
13. UNPLUG this apparatus during lightning storms or when unused for long periods of time.
14. REFER all servicing to qualified service personnel. Servicing is required when the apparatus has been damaged in any way, such as
power-supply cord or plug is damaged, liquid has been spilled or objects have fallen into the apparatus, the apparatus has been
exposed to rain or moisture, does not operate normally, or has been dropped.
15. DO NOT expose this apparatus to dripping or splashing and ensure that no objects filled with liquids, such as vases, are placed on
the apparatus.
16. To completely disconnect this apparatus from the AC Mains, disconnect the power supply cord plug from the AC receptacle.
17. Where the mains plu g or an appliance coup ler is used as the disconnect device, the disconnect device shall remain readily operable.
18. DO NOT overload wall outlets or extension cords beyond their rated capacity as this can cause electric shock or fire.
The exclamation point, within an equilateral triangle, is intended to alert the user to the presence of important operating and maintenance
(servicing) instructions in the literature accompanying the product.
The lightning flash with arrowhead symbol within an equilateral triangle is intended to alert the user to the presence of uninsulated "dangerous
voltage" within the product's enclosure that may be of suff icient magnitude to constitute a risk of electrical shock to persons.
ESD Warning: The icon to the left indicates text regarding potential danger associated with the discharge of static electricity from an outside
source (such as human hands) into an integrated circuit, often resulting in damage to the circuit.
WARNING: To reduce the risk of fire or electrical shock, do not expose this apparatus to rain or moisture.
WARNING: No naked flame sources - such as candles - should be placed on the product.
WARNING: Equipment shall be connected to a MAINS socket outlet with a protective earthing connection.
WARNING: To reduce the risk of electric shock, grounding of the center pin of this plug must be maintained.
No patent liability is assumed with respect to the use of information contained herein. While every precaution has been taken in the preparation of this
publication, AMX assumes no responsibility for error or omissions. No liability is assumed for damages resulting from the use of the information
contained herein. Further, this publication and features described herein are subject to change without notice.
AMX WARRANTY AND RETURN POLICY
The AMX Warranty and Return Policy and related documents can be viewed/downloaded at www.amx.com.
About This Document ..................................................................................................... 14
Differences in DEFINE_PROGRAM Program Execution................................................... 14
CPU Usage ............................................................................................................................................ 15
Quick Setup and Configuration Overview....................................................................... 17
User and Role Name Rules.................................................................................................................................. 42
Role Permissions .................................................................................................................................. 48
Adding a New Role ................................................................................................................................ 49
Viewing and Modifying Role Security Settings Details ......................................................................... 50
Deleting a Role ...................................................................................................................................... 50
Default User Accounts .......................................................................................................................... 51
Adding a New User................................................................................................................................ 52
Viewing and Editing User Security Settings ......................................................................................... 53
Deleting a User ..................................................................................................................................... 53
Locking/Disabling a User...................................................................................................................... 53
Uploading a Module............................................................................................................................................ 60
Archiving a Module ............................................................................................................................................. 60
Deleting a Module ............................................................................................................................................... 60
Video Settings....................................................................................................................................... 73
Inputs Only ......................................................................................................................................................... 73
Outputs Only ....................................................................................................................................................... 73
DXLink Video Settings........................................................................................................................... 75
DXLink (Twisted Pair or Fiber) Transmitters (for selected video input) ............................................................ 75
DXLink (Twisted Pair or Fiber) Receivers (for selected video output)............................................................... 75
Inputs Only ......................................................................................................................................................... 76
Outputs Only ....................................................................................................................................................... 77
CTSPSH OFF ............................................................................................................................................................................ 88
GET BAUD ............................................................................................................................................................................... 89
GET FAULT .............................................................................................................................................................................. 89
GET STATUS............................................................................................................................................................................ 89
SET BAUD............................................................................................................................................................................... 90
SET FAULT DETECT OFF ......................................................................................................................................................... 90
SET FAULT DETECT ON........................................................................................................................................................... 90
XON ........................................................................................................................................................................................ 91
GET BAUD .............................................................................................................................................................................. 94
GET FAULT ............................................................................................................................................................................. 94
GET MODE .............................................................................................................................................................................. 94
GET STATUS........................................................................................................................................................................... 94
POD ......................................................................................................................................................................................... 95
SET BAUD................................................................................................................................................................................ 96
SET FAULT DETECT OFF .......................................................................................................................................................... 96
SET FAULT DETECT ON............................................................................................................................................................ 96
SET IO LINK ............................................................................................................................................................................ 96
SET MODE............................................................................................................................................................................... 97
GET DBT .................................................................................................................................................................................. 99
SET DBT .................................................................................................................................................................................. 99
GET INPUT .............................................................................................................................................................................. 99
SET INPUT .............................................................................................................................................................................. 99
GET CLASS ........................................................................................................................................................................... 100
GET CURRENT ...................................................................................................................................................................... 100
GET FAULT ........................................................................................................................................................................... 100
GET STATUS......................................................................................................................................................................... 100
GET VOLTAGE....................................................................................................................................................................... 100
SET FAULT DETECT OFF ....................................................................................................................................................... 100
SET FAULT DETECT ON......................................................................................................................................................... 100
SET POWER OFF ................................................................................................................................................................... 100
SET POWER ON..................................................................................................................................................................... 100
GET AX FAULT...................................................................................................................................................................... 101
----- Help ----- <D:P:S> ........................................................................................................................................................ 105
? or Help............................................................................................................................................................................... 105
ADD AUDIT SERVER [D:P:P] ................................................................................................................................................. 105
AUTO LOCATE (ENABLE|DISABLE|STATUS) ........................................................................................................................ 105
BOOT STATUS ...................................................................................................................................................................... 105
CLEAR MAX BUFFERS........................................................................................................................................................... 105
CPU USAGE .......................................................................................................................................................................... 105
DATE .................................................................................................................................................................................... 105
DEVICE STATUS <D:P:S>..................................................................................................................................................... 105
DISK FREE ............................................................................................................................................................................ 105
DNS LIST <D:P:S>................................................................................................................................................................ 106
EXPORT (CONFIG|CLONE) TO USB (FRONT|BACK) ............................................................................................................. 106
EXPORT AUDIT to USB (FRONT|BACK)................................................................................................................................ 106
FIPS MODE ........................................................................................................................................................................... 106
GET AUDIT STATUS ............................................................................................................................................................. 106
GET DEVICE HOLDOFF.......................................................................................................................................................... 107
GET DEVICE TRAFFIC........................................................................................................................................................... 107
GET DUET MEMORY.............................................................................................................................................................. 107
GET ICSLAN ......................................................................................................................................................................... 107
GET IP <D:P:S>.................................................................................................................................................................... 107
GET LEASES ......................................................................................................................................................................... 107
GET OCSP URL...................................................................................................................................................................... 107
GET PLATFORM INFO ........................................................................................................................................................... 107
HELP SECURITY ................................................................................................................................................................... 107
IP STATUS ........................................................................................................................................................................... 108
LIST AUDIT FILES ................................................................................................................................................................ 108
LIST AUDIT SERVERS........................................................................................................................................................... 108
LOG FORMAT ........................................................................................................................................................................ 108
MAIL RESET ......................................................................................................................................................................... 108
MAIL STATUS....................................................................................................................................................................... 108
MEM ..................................................................................................................................................................................... 108
OFF [D:P:S or NAME,CHAN].................................................................................................................................................. 109
ON [D:P:S or NAME,CHAN] ................................................................................................................................................... 109
PASS [D:P:S or NAME].......................................................................................................................................................... 110
PROGRAM (ENABLE|DISABLE|STATUS) .............................................................................................................................. 110
PROGRAM INFO.................................................................................................................................................................... 110
PULSE [D:P:S or NAME,CHAN].............................................................................................................................................. 110
REMOVE AUDIT SERVER [D:P:P]........................................................................................................................................... 111
SEND_STRING D:P:S or NAME,STRING ................................................................................................................................ 111
SET DATE ............................................................................................................................................................................. 111
SET DEVICE REBOOT ............................................................................................................................................................ 111
SET DNS <D:P:S> ................................................................................................................................................................. 112
SET DUET MEMORY .............................................................................................................................................................. 112
SET FTP PORT ...................................................................................................................................................................... 112
SET HTTP PORT.................................................................................................................................................................... 112
SET HTTPS PORT.................................................................................................................................................................. 112
SET HTTPS REDIRECT .............................................................................................................
SET ICSLAN.......................................................................................................................................................................... 113
SET ICSP PORT .................................................................................................................................................................... 113
SET ICSP TCP TIMEOUT....................................................................................................................................................... 113
SET IP <D:P:S> .................................................................................................................................................................... 113
SET LOCKOUT....................................................................................................................................................................... 113
SET LOG COUNT ................................................................................................................................................................... 114
SET NOTIFY THROTTLE ........................................................................................................................................................ 114
SET OCSP URL...................................................................................................................................................................... 114
SET QUEUE SIZE .................................................................................................................................................................. 114
SET SELF SIGNED CERTIFICATE .......................................................................................................................................... 114
SET SSH PORT...................................................................................................................................................................... 114
SET SYSTEM NUMBER.......................................................................................................................................................... 115
SET TELNET PORT ................................................................................................................................................................ 115
SET THRESHOLD .................................................................................................................................................................. 115
SET TIME.............................................................................................................................................................................. 115
SET TIMELINE LOOPCNT...................................................................................................................................................... 115
SET UDP BC RATE ................................................................................................................................................................ 115
SET URL <D:P:S> ................................................................................................................................................................. 116
SHOW AUDIT [FILENAME] ................................................................................................................................................... 116
SHOW AUDIT LOG ................................................................................................................................................................ 116
SHOW BUFFERS ................................................................................................................................................................... 116
SHOW COMBINE................................................................................................................................................................... 116
SHOW DEVICE <D:P:S>........................................................................................................................................................ 117
SHOW HTTPS REDIRECT ...................................................................................................................................................... 117
SHOW LOG............................................................................................................................................................................ 117
SHOW MAX BUFFERS ........................................................................................................................................................... 118
SHOW MEM .......................................................................................................................................................................... 118
SHOW NOTIFY ...................................................................................................................................................................... 118
SHOW REMOTE..................................................................................................................................................................... 118
SHOW ROUTE ....................................................................................................................................................................... 118
SHOW START LOG <START>................................................................................................................................................ 118
SHOW SYSTEM <S> ............................................................................................................................................................. 119
SHOW TCP............................................................................................................................................................................ 119
SHOW WATCHDOG ............................................................................................................................................................... 119
TOD ADJUSTMENTS ............................................................................................................................................................. 119
URL LIST <D:P:S> ................................................................................................................................................................ 119
USB LOG [front|back] [enable|disable]............................................................................................................................... 119
Edit Role Menu .................................................................................................................................... 126
Access Rights Menu............................................................................................................................ 126
Adding a Role.................................................................................................................................................... 127
NetLinx NX Integrated Controllers (Masters) can be programmed to control RS-232/422/485, Relay, IR/Serial, and Input/Output
devices using the NetLinx Studio application (version 4.0 or higher).
NetLinx NX Integrated Controllers
NameDescription
NX-1200NetLinx NX Integrated Controller
NX-2200NetLinx NX Integrated Controller
NX-3200NetLinx NX Integrated Controller
NX-4200NetLinx NX Integrated Controller
NOTE: Refer to the Products > Central Controllers > NetLinx NX Integrated Controllers page at www.amx.com for details and
variations available for these products.
NX controllers feature an on-board Web Console which allows you to connect to the NX controller via a web browser and make
various configuration and security settings. The WebConsole is described in this document (starting with the On-Board WebConsole User Interface section on page 34).
NX controllers are Duet-compatible and can be upgraded via firmware. Duet is a dual-interpreter firmware platform from AMX which
combines the proven reliability and power of NetLinx with the extensive capabilities of the JavaEdition Embedded) platform. Duet simplif ies the programming of a system that includes the NX controller and other third party
devices by standardizing device and function definitions, defaulting touch panel button assignments, and controlling feedback
methods.
Dynamic Device Discovery makes integration even easier by automatically identifying and communicating with devices which
support this beaconing technology.
®
MicroEdition (Java Standard
Overview
Enova DVX All-in-One Presentation Switchers
Enova Digital Media Switchers
NameDescription
DVX-3250HD10x4 All-In-One Presentation Switchers with NX Control (Multi-Format, HDMI Inputs)
DVX-3255HD10x4 All-In-One Presentation Switchers with NX Control (Multi-Format, HDMI, 2 DXLink Inputs)
DVX-3256HD10x4 All-In-One Presentation Switchers with NX Control (Multi-Format, HDMI, 4 DXLink Inputs)
DVX-2250HD6x3 All-In-One Presentation Switchers with NX Control (Multi-Format, HDMI Inputs)
DVX-2255HD6x3 All-In-One Presentation Switchers with NX Control (Multi-Format, HDMI, DXLink Inputs)
DVX-2210HD4x2 All-In-One Presentation Switchers with NX Control (Multi-Format, HDMI Inputs)
NOTE: Refer to the Products > All-in-One Presentation Switchers page at www.amx.com for details and variations available for these
products.
Enova DVX-22xxHD & DVX-325xHD
Enova DVX-22xxHD All-in-One Presentation Switchers utilize an NX-2200 Controller, therefore all controller-related information
that applies to the NX-2200 is fully applicable to DVX-22xxHD products.
Enova DVX-325xHD All-in-One Presentation Switchers utilize an NX-3200 Controller, therefore all controller-related information
that applies to the NX-3200 is fully applicable to DVX-325xHD products.
Enova DVX All-In-One Presentation Switchers features many functions that do not apply to NX-series Controllers, most of
which relate directly to the Audio/Video capabilities of the DVX.
Refer to the Enova DVX-325xHD/22xxHD All-in-One Presentation Switchers Instruction Manual for information specific to
NOTE: Refer to the Products > Digital Media Switchers page at www.amx.com for details and variations available for these products.
Massio™ ControlPads
Massio ControlPads
NameDescription
MCP-1066-Button Massio ControlPad
MCP-1088-Button Massio ControlPad
NOTE: Refer to the Products > ControlPads page at www.amx.com for details and variations available for these products.
About This Document
This document describes using the on-board WebConsole, as well as NetLinx send commands and terminal communications to
configure the NX controllers:
Each major section of the WebConsole is described in a separate section of this document. Refer to:
the On-Board WebConsole User Interface section on page 34,
the WebConsole - Network Options section on page 46,
the WebConsole - Security Options section on page 41,
the WebConsole - System Options section on page 57, and
the WebConsole - Switching Options section on page 67.)
The Initial Conf iguration and Firmware Upgrade section on page 5 describes upgrading the firmware on NX controllers.
The NetLinx Programming section on page 82 lists and defines the NetLinx send commands that are supported by the NX
controllers.
The Terminal (Program Port/Telnet) Commands section on page 104 describes the commands and options available via a
Telnet terminal session with the NX controller.
Differences in DEFINE_PROGRAM Program Execution
Due to differences in the underlying architecture of the X-Series masters, changing variables in the DEFINE_PROGRAM section of
code can negatively impact program performance. It has always been considered poor programming practice to change a variable
within the DEFINE_PROGRAM section of code. If you have legacy NetLinx code that does change a variable in this section it’s very
likely that timing differences will cause your code to run slower and appear less respo nsive on an NX-Series controller and can have
other adverse effects on platform reliability in the area of connectivity and data throughput.
The DEFINE_PROGRAM section of NetLinx code contains the code known as mainline. Mainline is the section of the program that is
executed on a periodic basis by the NetLinx Master Controller. Under normal operation, the DEFINE_PROGRAM section executes at
least once every half second. Various system activities can cause the DEFINE_PROGRAM section to execute more frequently than
every half second. For example, any time an external event occurs (button push, level change), the DEFINE_PROGRAM section must
re-execute to ensure that any change caused by the event processes through the DEFINE_PROGRAM section code block. This is
also the case for changes to global variables. Any variable change requires the DEFINE_PROGRAM section to re-execute to process
the new variable value through the DEFINE_PROGRAM code block.
Because high CPU usage can be detrimental to the system functionality on an NX master, AMX recommends the complete
deprecation of the DEFINE_PROGRAM section. Syntactically, it is still valid to use the DEFINE_PROGRAM section in your NetLinx
application, but it is no longer recommended. All logic that you would normally place in the DEFINE_PROGRAM section is handled
better in the DEFINE_EVENT section.
Feedback statements remain the most common usage in the DEFINE_PROGRAM section. Because of periodically executing
DEFINE_PROGRAM, you can rely on the program to update user feedback at a regular interval. However, if the DEFINE_PROGRAM
section executes too frequently with the needless iterations expending the CPU to repetitively evaluate the feedback statements.
TIMELINE_EVENTS provide a much more efficient mechanism for evaluating feedback statements. A single timeline triggering every
500ms provides the same periodic execution as the DEFINE_PROGRAM section without the unwanted recursive execution behavior.
Consider the following DEFINE_PROGRAM section containing feedback statements in PRGM EX. 1:
PRGM EX. 2 Using feedback statements in a timeline
The code in PRGM EX. 2 evaluates the feedback statements every half second regardless of other program activity. If a shorter
feedback refresh is needed, you can specify a smaller constant in the FEEDBACK_TIMES constant. Even a time of 100ms executes
far less frequently than a DEFINE_PROGRAM section stuck in an infinite execution loop due to a global variable change.
By moving all code out of the DEFINE_PROGRAM section, you ensure your NetLinx application is executing only when needed, and
therefore not expending unnecessary CPU cycles.
If you choose to continue to use the DEFINE_PROGRAM section, it is critical that you ensure that you are not modifying a variable
within the section. Any variable change will force a repeated execution of the section, thereby creating an infinite execution loop.
Variables should never fal l o n the left-hand side of an evaluation statement, as in PRGM EX. 3.
DEFINE_PROGRAM
Var1 = !Var1
PRGM EX. 3 Variable declared within the DEFINE_PROGRAM section
You must also take care to not inadvertently change a variable. For example, if a function is called within DEFINE_PROGRAM, then
that function must likewise not change a global variable. Additionally, accessing global “values” such as TIME and DATE constitute
a variable change. Take for example the code in PRGM EX. 4:
IF (TIME = ’22:00:00’)
{…}
PRGM EX. 4 Time check
At first glance, this code does not appear to change a variable. It is simply checking to see if the current time is equal to 22:00:00.
However, this code effectively changes the TIME variable by retrieving the current system time and assigning it to the TIME variable.
If this code were present in a DEFINE_PROGRAM section, it would infinitely re-execute the DEFINE_PROGRAM section. You should
place evaluations such as this in a TIMELINE_EVENT similar to the feedback timeline described earlier.
CPU Usage
The new NX masters provide several diagnostics that can be used to determine if your program is overloading the CPU and, if so,
what might be causing its excessive use. All of these commands are accessible through a Telnet or USB terminal connection with
the master.
>cpu usage
Gathering CPU usage over a 10 second period. Please wait ...
CPU usage = 2.10% over a 10 second period.
An idle application normally runs below 5% of the CPU. If your idle application shows more usage than this, then it is probable that
your application is experiencing excessive execution of the DEFINE_PROGRAM section.
You can use the following diagnostic to diagnose executions of the DEFINE_PROGRAM section:
These statistics indicate how many times mainline has been executed and why it has been executed. Repeatedly executing “show
interp stats” will give you an idea which code construct is causing mainline to execute. For example, if a variable is being changed,
you will see the “Variable Change” count increasing. If a timeline is firing quickly, you will see the TIMELINE_EXPIRATION count
increasing. A normal idle application that is executing DEFINE_PROGRAM every half second will only see the “Periodic Mainline”
count increasing.
For example, consider this diagnostic output from a NetLinx application that is changing a variable in DEFINE_PROGRAM:
>show interp stats
-- Mainline Executions due to:
Variable Change : 50927
Pending Int Event : 1
Pulse Expiration : 0
Hold Expiration : 0
DoPush Expiration : 0
Wait Expiration : 0
Until Expiration : 0
Timeline Expiration : 0
Periodic Mainline : 0
Current internal event count = 1
>show interp stats
-- Mainline Executions due to:
Variable Change : 62295
Pending Int Event : 1
Pulse Expiration : 0
Hold Expiration : 0
DoPush Expiration : 0
Wait Expiration : 0
Until Expiration : 0
Timeline Expiration : 0
Periodic Mainline : 0
Current internal event count = 0
>show interp stats
-- Mainline Executions due to:
Variable Change : 72386
Pending Int Event : 1
Pulse Expiration : 0
Hold Expiration : 0
DoPush Expiration : 0
Wait Expiration : 0
Until Expiration : 0
Timeline Expiration : 0
Periodic Mainline : 0
Current internal event count = 1
Notice the “Variable Change” count is increasing rapidly.
These diagnostics will not tell you where in your application the offending code resides. Finding the offending code requires a
process of code analysis and possibly selectively commenting out sections of code to isolate the offender.
NOTE: NetLinx modules each have a DEFINE_PROGRAM section that must abide by the same rules as the main program, so the
offending code could be in a module.
The general steps involved with most common installations of this device include:
Unpack and confirm the contents of box (see the Specifications tables in the Hardware Reference Guide for each controller).
Connect all rear panel components and supply power to the NX controller from the external power supply.
Conf iguration and Communication
The general steps involved with setting up and communicating with the NX controller’s on-board Master. In the initial
communication process:
Set the boot-time operations on the rear Configuration DIP switch. (The DIP switch is located on the front panel of the
NX-1200.)
Connect and communicate with the on-board Master via the Program port.
Set the System Value being used with the on-board Master.
Re-assign any Device values.
Retrieve the DHCP Address for the on-board Master or assign a Static IP to the on-board Master.
Once the IP information is determined, re-work the parameters for Master Communication to connect to the on-board
Master via the LAN and not the Program port.
Update the On-board Master and Controller Firmware
Before using your new NX controller, you must first update your NetLinx Studio to the most recent release.
Upgrade the Integrated Contro ller f irmware through an IP address via the LAN connector (Upgrading Firmware section on
page 28) (IP recommended).
Upgrade the on-board Master firmware through an IP address via the LAN connector (Upgrading Firmware section on
page 28) (IP recommended).
Conf igure NetLinx Security on the NX Controller
Setup and finalize your NetLinx Security Protocols (WebConsole - Security Options section on page 41).
Program your NX controller (NetLinx Programming section on page 82).
Overview
Using Zero Configuration
NetLinx Masters support using "zero-configuration" client software to quickly install multiple devices on the network.
Bonjour (Zero-Conf iguration) Client
You can use a zero-configuration client to determine the IP address of the Controllers. There are many zero-configuration clients
available which are free and widely available for download. NetLinx Studio includes a zero-configuration client which we will use for
the purposes of this document.
If you don’t already have it installed on your PC, download and install NetLinx Studio 4.0 before you begin.
Connecting to a Network with a DHCP Server
By using the Controller’s Zeroconf feature and the NetLinx Studio, you can install and configure multiple devices on the network
without pre-conf iguring each device befo re installation.
The dealer only needs to match the serial number printed on the backside of the device or from the label on the box to the serial
number that is displayed in the Bonjour browser pane.
1.Launch NetLinx Studio 4.0.
2.Once power is applied to the device, select the Zero-Config tab on the Workspace bar (see FIG. 1).
3.In the Workspace area, right-click and select Refresh Zero Conf ig List. The controller appears in the list of devices as shown in
FIG. 2:
FIG. 2
Workspace bar (Zero-Config tab selected)
4.Double-click the Master you want to access it in the WebConsole.
Accessing the Master requires valid login information. The browser will prompt you for User ID and Password before displaying
the configuration pages for the selected device.
Note that the serial number is appended to the name of the device.
After logging in, you can configure the device (changing IP settings, NetLinx settings, User settings, etc) via the pages in the
WebConsole (see the On-Board WebConsole User Interface section on page 34).
This section describes using the NetLinx Studio software application to perform the initial configuration of the NetLinx Master.
NetLinx Studio is used to setup a System number, obtain/assign the IP/URL for the NX controller, as described in this section (as
well as to transfer firmware Kit files to the Master - see the Upgrading Firmware section on page 28).
Before You Start
1.Verify you have the latest version of the NetLinx Studio application version 4.0 installed on your PC.
NetLinx Studio is available to download from www.amx.com. Login to download the latest version. Alternatively, if it is already
installed, use the Web Update option in NetLinx Studio’s Help menu to obtain the latest version.
The default location for the NetLinx Studio application is Start > Programs > AMX Control Disc > NetLinx Studio > NetLinx
Studi o.
2.Verify that a LAN cable is connected from the Master to the LAN Hub.
3.Connect a programming cable (Type-B USB) from the Program Port on the Master to a USB port on the PC being used for
programming.
4.Apply power to the Master.
Preparing the Master for USB Communication
To establish USB communication with the Master via the PROGRAM port with Type-B-to-Type-A cable:
1.Launch NetLinx Studio and select Settings > Workspace Communication Settings (FIG. 3):
Initial Configuration
NetLinx Studio menu bar - Settings > Workspace Communication Settings
FIG. 3
2.This opens the Workspace Communication Settings dialog (FIG. 4).
3.Click the System Settings button to open the Communications Settings dialog (FIG. 5). If there is no system selected, click the
Default Settings button to open the dialog.
FIG. 5
Communication Settings dialog - Recent tab
4.Select the USB tab to view the USB options (FIG. 6).
FIG. 6 Communications Settings dialog - USB tab
5.On the USB tab, highlight the Master you want to connect to and click Select.
6.Click Edit to open the Edit USB Master’s Username/Password dialog to set the user name and password for authentication
access to the Master. This step is optional. You can only change the user name and password in the dialog. The additional
fields are view-only.
7.Click OK to close the USB Master’s Username/Password dialog, and click OK in the Communication Settings dialog to return to
the Communication Settings dialog, now indicating the USB-connected Master as the current connection conf iguration.
8.Click OK to close the Communication Settings dialog and return to the main application.
9.Right-click the Online Tree tab entry and select Refresh System: the Controller should appear in the Device Tree (FIG. 7):
FIG. 7
Workspace Bar - Online Tree
NOTE: If the Master does not appear in the list, verify that the USB cable is connected properly.
Once USB communication has been established, use NetLinx Studio to configure the Controller for LAN Communication, as
described in the next section.
Conf iguring the NX Controller for LAN Communication
1.Use a LAN cable to connect the Controller to the LAN to which the PC running NetLinx Studio is connected.
2.Select Diagnostics > Network Addresses from the menu bar to open the Network Addresses dialog (FIG. 8). Use the options in
this dialog to select to either use DHCP or specify an IP address.
3.Click Ge t I P I nf o r ma ti o n to enable the fields for editing (FIG. 9):
FIG. 9
Network Addresses dialog showing initial IP information
4.Enter the System, Device (0 for NetLinx Masters), and Host Name information.
NOTE: Host names may contain only the ASCII letters 'a' through 'z' (in a case-insensitive manner), the digits '0' through '9', and the
hyphen ('-').
5.To configure a network address via DHCP (FIG. 10):
FIG. 10 Network Addresses dialog (DHCP)
a. Select Use DHCP.
b. Click Set IP Information to retain the DHCP setting.
c. To finish the process, click Reboot Device.
d. Click Done to close the dialog.
6.To specify a network IP address (FIG. 11):
FIG. 11 Network Addresses dialog (Specify IP Address)
a. Select Spec if y IP Address.
b. Enter the IP parameters into the available fields.
c. Click Set IP Information to retain the pre-reserved IP address to the Master.
d. To finish the process, click Reboot Device.
e. Click OK to close the dialog.
7.Repeat steps 1 - 5 from the previous section, but rather than selecting the USB tab, select Network and edit the settings to
match the IP address you are using (Static or Dynamic).
8.If you want the Master to require authentication for access, enter a User Name and Password in the provided fields to secure
the Master.
9.Click the OK to close all dialogs and return to the main application.
Obtaining the NX Controller’s IP Address (using DHCP)
NOTE: Verify there is an active LAN connection on the NX controller’s LAN port before beginning these procedures.
1.In NetLinx Studio, select Diagnostics > Network Addresses from the Main menu to access the Network Addresses dialog
(FIG. 12).
FIG. 12
2.Verify that both the System number corresponds to the System value previously assigned within the Device Addressing tab
NOTE: The system value must correspond to the Device Address entered in the Device Addressing dialog. Refer to the Manage System
- System Number section on page 46 for more detailed instructions on setting a system value.
3.Click Ge t I PInformation to enable the Use DHCP and Specify IP Address options.
4.Select Use DHCP.
NOTE: DO NOT enter ANY IP information at this time; this step only gets the System Master to recognize that it should begin using an
obtained DHCP Address.
5.Click Reboot Device.
6.After the device has booted, repeat steps 1-3.
7.Note the obtained IP address (read-only). This information is later entered into the Communication Settings dialog and used
NOTE: If the IP Address field is empty, give the Master a few minutes to negotiate a DHCP Address with the DHCP Server, and try
again. The DHCP Server can take anywhere from a few seconds to a few minutes to provide the Master with an IP address.
NOTE: Verify that these IP values are also entered into the related fields within either the IP Settings section of the System
Connection page (on the touch panel) or within the Address field on the web browser.
8.Click Done to close the dialog.
NOTE: On the front panel of the NetLinx Master, the STATUS and OUTPUT LEDs should begin to alternately blink during the
incorporation. Wait until the STATUS LED is the only LED to blink.
Complete the communication process by continuing on to the Communicating via IP Address section on page 25.
NetLinx Studio: Network Addresses dialog
and that zero (0) is entered into the Device field.
by NetLinx Studio to communicate to the NX controller via an IP. This add ress is reserved by the DHCP server and then given to
the Master.
NOTE: Verify there is an active LAN connection on the LAN port of the Master before beginning these procedures.
1.In NetLinx Studio, select Diagnostics > Network Addresses to open the Network Addresses dialog (FIG. 13):
FIG. 13
2.Verify that both the System number corresponds to the System value previously assigned within the Device Addressing tab
NOTE: The system value must correspond to the Device Address previously entered in the Device Addressing tab. Refer to the Manage
System - System Number section on page 46 for more detailed instructions on setting a system value.
3.Click the Ge t I PInformation button to enable the Use DHCP and Specify IP Address options.
4.Select Specif y IP Address to enable the IP fields for editing (FIG. 14):
FIG. 14 NetLinx Studio: Network Addresses dialog (Specify IP Address)
5.Enter the IP Address, SubnetMask, and Ga t e w a y information into their respective fields (as defined by the System
NOTE: Verify that these IP values are also entered into the related fields within either the IP Settings section of the System
Connection page (on the touch panel) or within the Address field on the web browser.
6.Click Set IP Information to cause the on-board Master to retain this new IP address.
7.Click Reboot Master.
8.Click Done to close the dialog.
NOTE: On the front panel of the NetLinx Master, the STATUS and OUTPUT LEDs should begin to alternately blink during the
incorporation. Wait until the STATUS LED is the only LED to blink.
Complete the communication process by continuing on to the Communicating via IP Address section on page 25.
NetLinx Studio: Network Addresses dialog
and that zero (0) is entered into the Device field.
Whether the on-board Master’s IP address was set or obtained via DHCP, use the IP address information from the Network
Addresses dialog to establish communication via the LAN-connected Master.
1.Use NetLinx Studio to obtain the IP address of the NX controller. If you do not have an IP address, follow the steps outlined in
either the Obtaining the NX Controller’s IP Address (using DHCP) section on page 23, or the Assigning a Static IP to the NX Controller section on page 24.
2.Select Settings > Workspace Communication Settings from the Main menu to open the Workspace Communication Settings
dialog (FIG. 15):
FIG. 15
3.Click System Settings to open the Communications Settings dialog. If you do not have a system selected, click the Default
FIG. 16 NetLinx Studio - Communication Settings dialog (TCP/IP selected)
NetLinx Studio - Workspace Communication Settings dialog
5. Click New to open the NewTCP/IP Setting dialog. In this dialog, you can enter both a previously obtained DHCP or static IP
address and an associated Description for the connection into their respective fields. (FIG. 18):
FIG. 18 NetLinx Studio - New TCP/IP Setting dialog
Verify that the Automatically Ping the Master Controller to ensure availability option is selected to make sure the Master is
initially responding on-line before establishing full communication.
If the authentication is required for connecting to the Master at this address, enter a User Name and Password in the text
fields provided.
6.Click OK to close the New TCP/IP Settings dialog and return to the Communication Settings dialog: (FIG. 19).
FIG. 19 NetLinx Studio - Communication Settings dialog
a. Click on the new IP address entry in the List of Addresses window
b. Click Select to use the selected IP address as the current IP address.
7.Click OK to save your newly entered information and close the Communication Settings dialog and return to the
Communication Settings dialog. Note the selected IP address is indicated in the Configuration field (FIG. 20):
FIG. 20
NetLinx Studio - Communication Settings dialog (Current Master Connection field indicating the selected IP address)
8.Click OK to begin the communication process to your Master (and close the dialog).
If you are currently connected to a Master, a pop-up asks whether you would want to stop communication to the current
Master and apply the new settings.
Click Yes to interrupt the current communication from the Master and apply the new settings.
NOTE: On the front panel of the NetLinx Master, the STATUS and OUTPUT LEDs should begin to alternately blink during the
incorporation. Wait until the STATUS LED is the only LED to blink.
9.Click the OnLine Tree tab in the Workspace window to view the devices on the System. The default System value is one (1).
10. Right-click the associated System number and select Refresh System. This establishes a new connection to the specified
System and populates the list with devices on that system. The communication method is then highlighted in green on the
bottom of the NetLinx Studio window.
NOTE: If the connection fails to establish, a Connection Failed dialog appears. Try selecting a different IP address if communication
fails. Press the Retry button to reconnect using the same communication parameters. Press the Change button to alter your
communication parameters and repeat the steps above.
The basic process of upgrading firmware on NX-series controllers involves downloading the latest firmware files from
www.amx.com and using NetLinx Studio to transfer the files to a t arget NX contro ller.
Use the OnLine Device tree in NetLinx Studio to view the firmware files currently loaded on the Central Controller. FIG. 21 shows an
example OnLine Tree indicating an NX-3200:
Upgrading Firmware
FIG. 21
While the method of upgrading firmware f iles is the same for all Central Controllers, there are some specific points relative to the
specific model and type of controller that must be noted:
NetLinx Studio - Sample OnLine Tree
NX Controllers - Firmware Files
NX controllers contain two devices (NX Master and Device Controller), each of which require a separate firmware (*.kit) file.
The NX Master firmware file is not the same as the Device Controller firmware file. These two devices must be kept at compatible
firmware versions for proper operation. Therefore, both f iles should be used when upgrading any firmware associated with the
Integrated Controllers.
NX Controllers - Firmware Files
NX Master FirmwareThe on-board NX Master is listed first in the OnLine Tree as
Device Controller FirmwareThe Device Controller is listed next as "05001 NX-XXXX (<firmware version>)"
"00000 NX Master (<firmware version>)"
For example, the NX Master in FIG. 21 above is "00000 - NX-3200 Master (v3.4.555)".
•"00000" represents Device ID 0, which is reserved for the Master
• The number in parenthesis (in this case "v3.4.555") is the current NX Master firmware
version.
For example, the Device Controller in FIG. 21 above is "05001 - NX-3200 (v1.0.35)".
•"05001" represents Device ID 5001, which is reserved for the Device Control ports.
• The number in parenthesis (in this case "v1.0.35") is the current Device Controller firmware
version.
Enova DVX
Enova DVX All-In-One Presentation Switchers contain three devices (NX Master, Device Controller, and A/V Switcher/ Scaler), each
of which require a separate Kit file. These three devices must be kept at compatible firmware versions for proper operation.
Therefore, all three files should be used when upgrading any firmware associated with the Enova DVX All-In-One Presentation
Switchers.
DVX Controllers - Firmware Files
NX Master FirmwareThe on-board NX Master is listed first in the Online Tree as
Device Controller FirmwareThe Device Controller is listed next as
A/V Switcher/Scaler FirmwareThe A/V Switcher/Scaler is listed third as
"00000 NX Master (<firmware version>)"
• "00000" represents Device ID 0, which is reserved for the Master
• The number in parenthesis is the current Master firmware version.
"05001 NX-XXXX (<f irmware version>)"
• "05001" represents Device ID 5001, which is reserved for the Device Control ports.
• The number in parenthesis is the current Device Controller firmware version.
"05002 NX-XXXX (<firmware version>)"
• "05002" represents Device ID 5002, which is reserved for the A/V Switcher/Scaler.
• The number in parenthesis is the current Device Controller firmware version.
1.Verify you have the latest version of the NetLinx Studio application installed on your PC.
NetLinx Studio is available to download from www.amx.com. Lo gi n to do wnload the latest version. Alternatively, if it is already
installed, use the Web Update option in NetLinx Studio’s Help menu to obtain the latest version.
The default location for the NetLinx Studio application is Start > Programs > AMX Control Disc > NetLinx Studio > NetLinx
Studi o.
2.Verify that a LAN cable is connected from the controller to the LAN Hub.
3.Verify that the controller is powered on.
4.Connect to the controller via IP address.
5.Establish what version of f irmware is currently loaded on the controller (see Verifying the Current Firmware Version below).
Verifying the Current Firmware Version
Use the OnLine Tree in NetLinx Studio (see FIG. 21 on page 28) to verify which version of each firmware file is currently installed.
NOTE: These steps assume that you have already established a connection with the target Central Controller (see the Initial
Configuration section on page 19 for details).
1.In NetLinx Studio, click on the OnLine Tree tab (in the Workspace Bar) to view the devices on the System.
2.Click Display and select Refresh System from the context menu. This establishes a new connection to the System and
populates the device tree with devices on that system.
3.After the Communication Verification dialog indicates active communication between the PC and the Central Controller, verify
the Central Controller and associated devices are listed in the OnLine Tree.
4.Check the appropriate product page on www.amx.com for the latest NX Master and Device Controller firmware files for your
device.
If necessary, follow the procedures outlined in the following sections to obtain these firmware (*.kit) files from www.amx.com and
then transfer the new firmware files to the device.
Downloading the Latest Firmware Files from www.amx.com
NetLinx Integrated Controllers
NX-series Controllers require two firmware (*.kit) files: Master firmware and Device firmware. The Master firmware file is not the
same as the Device firmware file.
Both f iles should be used when upgrading any firmware associated with the Integrated Controllers.
IMPORTANT: The process of downloading and transferring firmware files is the same for all types of firmware. However, it is
important that the firmware files are upgraded in specific following order for NX-series Controllers (see the Required Order of
Firmware Updates section on page 31).
Master and Device Firmware Kit Files for NX-Series Controllers
Below is a table outlining the Master and Device Firmware (*.kit) files used by NetLinx Integrated Controllers:
Master and Device Firmware Files for NX-Series Controllers
NX-4200 / 3200 /
2200 / 1200
NOTE: The HTTP f irmware kit enables you to upgrade firmware via an HTTP server. Follow the same steps in NetLinx Studio as you
would with a typical firmware upgrade. Upgrading firmware via HTTP server is typically much faster than upgrading with the standard
firmware kit files. See the Upgrading Firmware via NetLinx Studio section on page 31 for more information.
Downloading NX-Series Controller Firmware Files on www.amx.com
Visit the appropriate product page on www.amx.com for the latest NX Master and Device Controller firmware (*.kit) files for your NX
controller. Firmware f ile links are available along the right-side of the cat alog page (FIG. 22):
Firmware f iles are b undled in a ZIP f ile, alo ng with a Readme.TXT file that provides details on this firmware release.
1.Accept the AMX Licensing Agreement.
2.Download the ZIP f ile and unzip the contents to a known location.
Enova DVX All-In-One Presentation Switchers
Enova DVX All-In-One Presentation Switchers require an additional Switcher Firmware f ile for the built-in switcher. ALL f iles shou ld
be used when upgrading any firmware associated with the Integrated Controllers.
NOTE: The process of downloading and transferring f irmware files is the same for all types of firmware. However, it is important that
the firmware files are upgraded in specific following order for DVX Controllers (see the Required Order of Firmware Updates for DVX
Controllers section on page 31).
Master, Switcher and Device Firmware Files for Enova DVX All-In-One Presentation Switchers
Below is a table outlining the Master, Device, and Switcher f irmware (*.kit) files used by Enova DVX Controllers:
Master Firmware Kit File Usage for Enova DVX Controllers
NOTE: The HTTP f irmware kit enables you to upgrade firmware via an HTTP server. Follow the same steps in NetLinx Studio as you
would with a typical firmware upgrade. Upgrading firmware via HTTP server is typically much faster than upgrading with the standard
firmware kit files. See the Upgrading Firmware via NetLinx Studio section on page 31 for more information.
Downloading Enova DVX Firmware Files on www.amx.com
Visit the appropriate product page on www.amx.com for the latest NX Master, Device Controller, and A/V Switcher/Scaler firmware
(*.kit) f iles for yo ur Enova DVX All-In-One Presentation Switcher. Firmware f ile links are avai lable along the right-side of the catalog
page (FIG. 23):