AMX NETLINX PROGRAMMING LANGUAGE, Manual

Page: 46 / 246

NetLinx Programming Overview
30 NetLinx Programming Language Reference Guide
Modules will eventually replace System calls. Where several system calls are currently needed to
provide device initialization, buffer processing, and device functionality, one module will handle all
three functions.
The first line of a Module contains the
MODULE_NAME
keyword, the Module name, and the parameter
list. The format is shown below:
MODULE_NAME = '<module name>' [(<param1>, <param2>, … , <paramN>)]
The
<module name>
must match the file name, but has the .AXS extension. The module name can be
64 characters long and contain valid file name characters. The parameter name is optional and follows
the same restrictions as subroutine parameters, with the exception that constants and expressions cannot
be used as arguments.
Within the NetLinx program, the Module is referenced using the following format:
DEFINE_MODULE '<module name>' <instance name> [(<pass1>, <pass2>, … , <passN>)]
The
<module name>
must match the module name specified in the Module file, as shown above. The
<instance name>
is a unique name given to each occurrence of the module within the program. If
the module is used twice within the program, each occurrence gets a unique instance name. The
parameter list passed to the module must match number and types of parameters listed in the module file
above. The
DEFINE_MODULE
statements are listed in the code after the
DEFINE_CALL
and
DEFINE_FUNCTION
sections, but before the
DEFINE_START
section.
The
DEFINE_MODULE
statements cannot appear within the
DEFINE_PROGRAM
or
DEFINE_EVENTS
section.
In order to use a module, the module must be compiled with the Source Code, and
the Master must be rebooted to run the new module.