Parker Hannifin
you save the configuration, the wizard generates AcroBASIC code
and saves it to specific user and PLC programs.
The Configuration Wizard saves all configuration data to a Setup.8K
file. Depending on which controller and the firmware version, it may
also save Drive I/O or Configuration Wizard data to various user and
PLC program files.
NOTE:
Do not edit the source files generated by the Configuration
Wizard.
Firmware Versions 1.18.15 and up (ACR9000 only)
The wizard generates AcroBASIC code and places it in the Setup.8K
file. The Prog15.8K file contains the configuration wizard data.
Firmware Versions Up to 1.18.14 (All ACR Controllers)
The wizard generates AcroBASIC code and places it in the Setup.8K
file. The Prog7.8K, PLC5.8K, PLC6.8K, and PLC7.8K files contain the
configuration wizard data and code for Hardware Limits, Software
Limits, and Drive Fault (hardware-input based drive fault, or
software-based following error drive fault) features.
PLC programs have limited memory space. If the resulting code
exceeds the limit for a PLC program, the Configuration Wizard splits
it among several PLC programs. The wizard uses the PLC5.8K file first,
and uses the PLC6.8k and PLC7.8k files as needed.
NOTE:
By default, the wizard matches motion profiles to programs
of the same number. Because the wizard reserves the
Prog7.8k file for the above-mentioned features, the
MASTER07 motion profile definition is placed in the Prog08.8k
file.
If no other programs are defined beyond the Prog08.8k file,
the controller continues scanning programs 00-08 without
delay. There is no delay executing the Prog08.8k file and
MASTER07. If any of the programs Prog09 through Prog15 are
used, then Prog08 will not execute as quickly as PROG00 to
PROG07.S
Global (P) Variables
The wizard generates code using global variables P100-P131 for
Software end-of-travel limits routines. Each variable corresponds to a
specific axis and direction of travel, as summarized below.
NOTE:
Do not change these values in user programs unless
specifically modifying them to change the end-of-travel
limit.
•
P100-P115 Positive Software End-of-Travel Limits:
For example,
P100 contains the value for Axis0, P101 for Axis1, etc.
46 Programmer’s Guide