AMX RPMLoader Manual de usuario descargar pdf (Pagina 4)

What’s New in X-Series Controllers

USB Program port

The X-Series controllers utilize a true USB port for configuration and programming via a connected PC. AMX is

developing a custom USB driver to support the X-Series controllers, but in the interim we are utilizing a standard PC

driver that emulates a COM port. This driver will be installed automatically while installing NetLinx Studio v4.x.

Because a PC COM port can only be used by a single process at a time, having a terminal window open using the COM

port assigned to that USB connection will prevent any other communication to the controller over that same USB

connection, including refreshing the online tree and transferring files.

It is recommended that you use the USB programming port to discover the IP address of the controller, modify it if

necessary, and then connect over Ethernet to that IP address.

USB Firmware upgrade

All X-Series controllers support firmware upgrades via a USB solid-state drive. Selecting the desired .kit file and

initiating the upgrade are done from telnet. The “IMPORT KIT” telnet command will cause the controller to search the

attached USB drive for all valid .kit files and show them as a list. From here you can select the .kit file to use and initiate

the firmware upgrade.

USB Program download

All X-Series controllers support loading NetLinx program files via a USB solid-state drive. Selecting the desired .tkn file

and initiating the upload are done from telnet. The “IMPORT TKN” telnet command will cause the controller to search

the attached USB drive for all valid .tkn files and show them as a list. From here you can select the .tkn file to use and

initiate the program upload.

USB logging

If a USB storage device is connected via an X-Series controller’s USB port it can be used to store a log of system status

messages. Use the “USB LOG” telnet command to enable and disable logging to an attached USB drive.

Copy and Clone configuration

On any X-Series controller, configuration information can be exported to and imported from a USB storage device.

There are two different levels of configuration export, “COPY” and “CLONE”.

The “COPY” export is used when the controller being copied from will remain deployed in the system but you wish to

copy its security and other configuration settings – but not IP address information – to other Masters.

The “CLONE” export is used when the controller being copied from is being removed from the system and replaced by

another controller. In addition to the configuration items exported in the “COPY” method, the “CLONE” export also

exports IP address information and all code elements.

Use the “EXPORT CONFIG” or “EXPORT CLONE” telnet commands to copy or clone the configuration information.

Then use the “IMPORT CONFIG” telnet command to load the saved configurations onto a new controller.

Difference 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 responsive on an X-Series controller.

External SD card slot (NX-3200 and NX-4200 only)

The external SD card slot in the NX-3200 and NX-4200 is for future use. Until firmware is available that supports the

use of an external SD card, the card slot must be left empty.

1 2 3 4 5 6 7

Sin comentarios

AMX RPMLoader Manual de usuario Pagina 4