Working With System Files; Overview; Identifiers Vs. Disk Filenames - AMX NetLinx Studio Instruction Manual

Working with System Files

Overview

A control system typically uses several different types of files. You must have a Master Source Code file to download to
the Master Controller, but a complete control system also uses an assortment of other file types. The file types
recognized by NetLinx Studio are described below:
Source Code Files
Include files
Block Files
Module Files
User Interface (UI) files
Infrared (IR) library files
IR Database files
Other files

Identifiers vs. Disk Filenames

Workspace and System files (displayed in the Workspace tab of the Workspace Bar) are represented by the Identifier
entered in the Workspace Properties, Project Properties, System Properties, and File Properties dialogs (FIG. 55).
FIG. 55 File Properties dialog
NetLinx Studio - Instruction Manual
These include the Master Source Code File and all other source code (.axs) files
associated with the System. See the Working with Source Code Files section on page 39
for details.
These are Axcess or NetLinx code files (.axi) that are referenced in any source code file
by the 'Include' statement. See the Working with Include Files section on page 46 for
details.
Block Files (.axb) represent blocks of re-usable code. Block files are saved in the Source
folder, and can be referenced in the main Source Code. See the Working with Block
Files section on page 49 for details.
NetLinx Module files provide pre-fabricated (.axs) code or compiled (.TKO) code to control
a specific device on the bus. Module files cannot be designated as master files. When the
System is being compiled, Module files are compiled first, then copied to the directory
where the designated Master Source code file resides. See the Working with Module
Files section on page 51 for details.
These files (.tpd, .tp4 or .kpd) are created in TPDesign3, TPDesign4 or KPDesign, and
contain touch panel pages, buttons and their associated functionality. See the Working
with User Interface Files section on page 59 for details.
These files (.irl or .irv) are created in the IREdit Program, and contain infrared (IR) control
functions for IR controlled devices. See the Working with IR Files section on page 61 for
details.
These files (.irn) contain links to either the AMX IR Database or to a user-defined IR
database. See the Working with IR Files section on page 61 for details.
In many cases, it is helpful to save document and image files (for example, .txt, .DOC,
.BMP) with the other system files, even if they are not directly utilized by the control
system. See the Working with "Other" Files section on page 65 for details.
Working with System Files
35