![background image](http://html1.mh-extra.com/html/amx/filetransfer2/filetransfer2_instruction-manual_2938908027.webp)
Using FileTransfer2
23
FileTransfer2
Here’s the syntax:
DEVICE:PORT:SYSTEM
where:
Device
: 16-bit integer representing the device number
Port
: 16-bit integer representing the port number (in the range 1 through the number of
ports on the device)
System
: 16-bit integer representing the system number (0 = this system) that the device
belongs to.
For example, 128:1:0 represents the first port on device 128 on this system.
DEV structure example:
STRUCTURE DEV
{
INTEGER Number // device number
INTEGER Port // port on device
INTEGER System // system device belongs to
}
Step 4: Transferring The Files
FileTransfer2 supports asynchronous communications, which allows you send and receive to and
from the bus on all available communications ports. You can send and receive both Axcess and
NetLinx Source Code files to and from the appropriate Master Controller or bus device.
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).
The Virtual NetLinx Master option allows you to transfer files directly to G4 devices,
without the need for an intermediate NetLinx Master.
File Transfer Status Information
Once you have started a file transfer operation, the status of each transfer item in the Files to Send
or Receive queue is indicated in the Transfer Status Window.
In Axcess, Master Source Code files are always mapped to the Master Controller
(device = 0), and cannot be mapped to any other device. This does not apply to
NetLinx Master Source Code files.