Compiling Module Files; Working With User Interface Files; Adding An Existing User Interface File To A System - AMX NetLinx Studio Instruction Manual

Where:
DVVirt
DvDMS
StrFileName
StrVarTextArray

Compiling Module Files

There are several ways to compile individual Module files:

Right-click on a Module file (in the Workspace tab of the Workspace Bar), and select Compile from the
Module File context menu.

Double-click to open the Module file in an Editor window and select Compile <filename.axs> from the
Build menu.

To specify the compiler to use (NetLinx or Axcess), open the Module file in an Editor window, and select
Compile as NetLinx or Compile As Axcess from the Build menu.
The status and results of the build are displayed in the Status tab of the Output Bar.

Working with User Interface Files

User-Interface (UI) files are sent to either touch panels or keypads, and provide the user-interface that allows the end user
to control the system. User Interface files are placed (as links) in the User Interface folder (in the Workspace tab of the
Workspace Bar). There are two basic types of user-files: Touch Panel and Keypad. Touch Panel UI files are created in
either TPDesign3 (.tpd) or TPDesign4 (.tp4), and Keypad UI files (.kpd) are created in KPDesign.

TPDesign3 is a touch panel design program for use with G3-firmware touch panels.

TPDesign4 is a touch panel design program for use with G4-firmware touch panels (all current touch panels).

KPDesign is a keypad design program for use with PLK-DMS and PLK-IMS keypads. Use the KPDesign to
design the keypad display pages and buttons, and their associated functionality, and use NetLinx Studio to
transfer the KPDesign file (KPD) to the NetLinx Master. To use KPDesign file with the appropriate keypads,
the NetLinx code file must first be configured (in NetLinx Studio), compiled, and then transferred to the
NetLinx Master.
Refer to the on-line help files for instructions on generating UI files in these
applications. These software applications are available for transfer via the
www.amx.com website (Dealers > Tech Center > Application Files).
NetLinx Studio allows you to associate UI files with each System and to map and transfer the files to their target panels
or master.
While Touch Panel UI files are transferred to the panels themselves, KPD files are
transferred to the master and not directly to the keypad.
If the TPDesign3, TPDesign4, and/or KPDesign applications are installed on your PC, you can double-click on any UI
file in the Workspace tab to launch the associated editor program (TPDesign3, TPDesign4, or KPDesign). You can add
external programs to the Tools menu via the Add Tool option. See the Customize dialog - Tools tab section on page 213
for details.

Adding an Existing User Interface File to a System

1.
Click to select (highlight) a System (in the Workspace tab of the Workspace Bar).
2.
Right-click on the User Interface folder to access the User Interface File Folder context menu, and select Add
Existing User Interface File (FIG. 115).
NetLinx Studio - Instruction Manual
An arbitrary Virtual Device number you define (range for keypad panels = 32768 -36863).
The real device number of the DMS or IMS panel.
A string variable (CHAR array) containing the file name of the KPD file to transfer or run.
A 2-dimensional array for storing variable text. The first dimension should be the largest
variable text string number you want to use. The second dimension should be the
maximum size of the string you want displayed (maximum is 40 characters).
When using two or more keypad panels, you can create a single 3-dimensional array for
keypad panels instead of separate two-dimensional arrays for each keypad panel.
Working with System Files
59