Working With Systems and System Files
45
NetLinx Studio (v2.4 or higher)
System Files
System Files represent the actual files that are needed to operate a particular controlled device in
the named System. System files include Source Code, Include files, NetLinx Module files, IRLib
files, User-Interface (UI) files and any other (*.*) files that you might want to include. System files
are placed in the appropriate System file folder (in the Workspace tab of the Workspace Window)
as links only.
System file types are described below:
Master Source Code
file
This is the Source Code file that defines the devices in the System. Mas-
ter Code files are sent only to the Axcess or NetLinx Master Controller.
Master Source Code files are placed in the Source file folder.
Source Code files
These include all code files (.AXS) that are not Master Code Files. Source
Code Files are created in NetLinx Studio, and are sent to specific devices
on the bus. Source Code files are placed in the Source file folder.
Include files
These are Axcess or NetLinx code files (.AXI) that are separate from the
main Master and Source Code files, but are included in the compile pro-
cess. These files are created in NetLinx Studio. Include files are placed in
the Include file folder.
Module Files
These files provide pre-fabricated (.AXS) code or compiled (.TKO) code to
control a specific device on the bus.
NetLinx Studio v2.3 (or higher) supports Duet (.JAR) Module files.
Module files cannot be designated as master files.
When the System is being compiled, these Module files are compiled first,
then copied to the directory where the designated Master Source code file
resides.
Module files are placed in the Module file folder.
User-Interface (UI)
files
These are (.TPD/.TP4) or (.KPD) files that are imported into Projects.
TPD/TP4 touch panel UI files define the look and functionality of touch
panel pages. TPD files are touch panel UI files created in TPDesign3 (for
use with G3 level firmware touch panels), TP4 files are created in
TPDesign4 (for use with G4 level firmware touch panels, i.e. Modero
series panels). KPD files are created in the KPDesign KeyPad Design pro-
gram, and define the buttons and functionality of PLK-DMS and PLK-IMS
Keypads. UI files represent the user-interface for the control system. UI
files are placed in the User Interface file folder.
Infrared (IR) library
files
These files (.IRL or .IRV) are created in IR Edit and contain infrared (IR)
control functions for IR controlled devices. IR files are placed in the IR
folder.
IRN files
IRN files provide links to the AMX IR Database and/or user-defined IR
Database files.
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. "Other" files are placed in the Other file
folder.
Summary of Contents for NETLINX STUDIO V2.4
Page 1: ...instruction manual Software NetLinx Studio v2 4 or higher ...
Page 16: ...NetLinx Studio v2 4 or higher 4 NetLinx Studio v2 4 or higher ...
Page 32: ...The NetLinx Studio v2 4 Work Area 20 NetLinx Studio v2 4 or higher ...
Page 44: ...Working With Workspace Files 32 NetLinx Studio v2 4 or higher ...
Page 88: ...Working With Systems and System Files 76 NetLinx Studio v2 4 or higher ...
Page 118: ...Programming 106 NetLinx Studio v2 4 or higher ...
Page 152: ...Working With Online Devices 140 NetLinx Studio v2 4 or higher ...