Adding And Modifying Software; Common Mistakes - AMX AXT-CA10 Instruction Manual

On-SIte Installer Overview

Adding and Modifying Software

Each time the application is run, it will generate the necessary software files. If changes are made to
any existing software file to modify itsbehavior for job-specific items, the next time Design XPress
- Professional is run, these changes are overwritten.
One of the files created in the project by the application is CUSTOM.AXI. This file is provided
because all custom software changes made in this file will never be overwritten by the DXP-PRO
application. So, for example, if a new room is added to a Design XPress - Professional-created
system, and those changes are made in CUSTOM.AXI, any changes made down the road via the
Design XPress - Professional application will not affect the room's code when the files are
regenerated. Sooner or later someone will make a change that gets overwritten so it is worth
repeating to avoid the resulting frustration: If you make changes to any file other than
CUSTOM.AXI you are taking it upon yourself to not use the application for any further updates.
Using the application will overwrite your changes.
In a sense this is one of the nice features of Design XPress - Professional. Because all of the
software is made available, an installer who is a strong NetLinx programmer could use the Design
XPress - Professional application as a starting point. The resulting files could get most of the job
complete. Not a bad start! The installer could then go in and modify the software to be job specific
and complete the job, never intending to use the application again. Conversely, there will be
installers who will use the application to do almost all of the work relying on the CUSTOM.AXI file
for any small changes that may be required.

Common Mistakes

The most common mistake made is modifying the software and then using the application to make
changes. As mentioned before, all software changes outside of the special CUSTOM.AXI file will
be overwritten. Only modify the source code generated by DXP-PRO if there is a strong desire to
alter the behavior of the code. To add features, new subsystems, etc. make the changes in the
custom file to avoid the frustration.
DXP-PRO is not a "simple" NetLinx program. Because of the scope and number of features
designed into the system, the code can be quite daunting to someone looking at it, even an
experienced NetLinx programmer. Installers with NetLinx experience should not expect to be able
to modify the software the first time they see it. Most of the features are tied into another feature or
affect another part of the software. The architecture of the system design and the function of the file
being modified should be understood prior to proceeding with changes.
Another common mistake is forgetting to properly address a device. Unless all devices are
addressed as defined in the report file the system will not work as desired.
DXP-PRO v1.1 - On-Site Installer's Guide 11