File Transfer Operations; Overview; Usb Transfers; Sending Files To The Master Or System Devices - AMX NetLinx Studio Instruction Manual

File Transfer Operations

Overview

NetLinx Studio supports asynchronous communications (send and receive to and from the bus on all available
communications ports simultaneously). You can send and receive both Axcess and NetLinx Source Code files to and
from the Master Controller or bus device.









USB Transfers

NetLinx Studio supports file transfers to several G4 touch panels via USB connection, for situations where the target
panel is not connected to a NetLinx Master. In this situation, you will use a USB connector on your PC to connect
directly to the panel, using your PC as a Virtual NetLinx Master.
When you select Virtual NetLinx Master as the Transport Connection Type (in the Communications Settings dialog, you
can perform direct transfers to a touch panel via either TCP/IP or USB connection. See Transferring Files Using a
Virtual NetLinx Master USB Connection on page 162.
USB transfers require that you configure the Master Connection setting on the panel
itself to USB prior to attempting a USB transfer. See Configuring the Touch Panel for
Virtual NetLinx Master USB Transfers on page 161.

Sending Files to the Master or System Devices

Files cannot be transfered unless they have device mapping information. Complete
all device mapping assignments before attempting to send files. See the Device
Mapping section on page 67 for details.
1.
Select Tools > File Transfer to open the File Transfer dialog. By default, this dialog opens the Send tab. The
options in this tab are specific to sending files to the Master Controller or System devices on the bus. (FIG. 228).
NetLinx Studio - Instruction Manual
Axcess or NetLinx Source Code files (.axs) can be sent to the Master Controller, or other control devices on
the bus. Source code files must be successfully compiled before they can be sent.
Touch Panel UI files created in TPDesign3 (.tpd) are sent directly to wired Touch Panels on the bus via an
AxLink/serial connection where the Device ID = 0.
Touch Panel UI files created in TPDesign4 (.tp4) are sent to the Master, either serially or over TCP/IP. G4
panels are connected to the Masters via TCP/IP and cannot be sent over AxLink. You can choose to include
buttons and pages only, or include fonts, bitmaps and/or icons in the transfer.
KeyPad UI files (.kpd) are sent to a NetLinx Master.
IR library files (.irl/.irv) are sent to IR-controlled devices on the bus, or directly to a System device (i.e. Touch
Panels).
NetLinx Studio only transfers TP4 files to G4 devices that have matching device types and resolutions. For
example, this feature would prevent you from accidentally transferring an R-4 Remote type TP4 file to a
MVP touch panel.
The File Transfer dialog (Tools > File Transfer) provides an easy to understand approach to file transfer
while still providing a high level of flexibility.
The Virtual NetLinx Master option allows you to transfer files directly to G4 devices, without the need for
an intermediate NetLinx Master.
File Transfer Operations
149