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 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 47
for details.
Include files These are 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 53
for details.
Block Files 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 56
for details.
Module Files NetLinx Module files provide pre-fabricated (.AXS) 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 58
for details.
User Interface (UI) files These files (.tp4 or .tp5) are created in TPDesign4 or TPDesign5, and contain touch panel pages, buttons and their associated functionality. See the
Working with User Interface Files section on page 68
for details.
Infrared (IR) library files 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 70
for details.
IR Database files 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 70
for details.
Other files 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 73
for details.