Rockwell Automation 47C626 AutoMax Programming Executive V4.2 - Manual (Page 137)

8Ć15
purged so that object files can be reĆcreated if they are needed at a
later time. Follow the procedure below to purge files.
Step 1.
Select Purge from the Commands menu. A dialog box will
be displayed.
Step 2. Select one or more types of files to delete:
Backup files
Log files (*.LOG)
Object files (*.OBJ, *.POB)
Cross Reference files (*.XRF)
Listing files (*.LST, *.CNL)
Tunable files (*.TUN)
Monitor files (*.$IO, *.$MV)
Step 3. Select OK to purge or Cancel to return to the Task
Manager without purging.
8.17.4 Generating the Rack Configuration and Drive
Parameter Files
The Generate Configuration command (from the Commands menu)
is used to generate the rack configuration object file or, for UDC
modules in the rack, the drive parameter object file. When the
Generate Configuration command is selected, the following options
will be displayed: Generate Rack Configuration (either standard or
mapping I/O locations to memory for testing) and Generate Drive
Parameter Files. The next two sections describe these options.
The Transfer command from the On Line menu is used to load the
rack configuration object file into the AutoMax Processor. The same
command is also used to load the drive parameter object file to the
UDC. See section 14.3 for information about loading the drive
parameter object files.
8.17.4.1 Generating the Rack Configuration
The Generate Configuration command can be used to create the
object file (.CNF) for the rack configuration. The generated"
(compiled) rack configuration must be loaded onto the Processor(s)
in the rack before or at the same time application tasks are loaded.
See 14.3 for information about loading the rack configuration file(s).
See Appendix D for information about configuration file size limits.
When generating the rack configuration, you have the option of
mapping variables to common memory for testing. If you select this
option, all variables currently configured as I/O registers or I/O points
will be configured as common memory locations. This allows you to
load application tasks into the Processor(s) in the rack and
run/monitor them without actually placing I/O modules in the rack, or
without connecting the I/O modules in the rack to field devices. The
variables can then be monitored through the OnĆLine command.
Loading the configuration using this option will make the
configuration take up more room on the Processor than loading
without this option. Tasks that depend on hardware interrupts, i.e.,
that use BASIC language WAIT ON statements, will not run. Note that
this option will not necessarily simulate realĆworld results and that
once testing is complete and you connect all field wiring to the rack,
you must reĆload the configuration without the option.