Rockwell Automation 8520-MUM 9/Series CNC Mill Operation and Programming Manual Documentation Set - Manual (Page 892)

Error and System Messages
Appendix B
B-20
Message Description
INVALID CHECKSUM DETECTED This error is common for several different situations. Most typically it results when writing or
restoring invalid data to flash memory. For example if axis calibration data is being restored to
flash and there was an error or invalid memory reference in the axis calibration data file.
Typically this indicates a corrupt or invalid file.
INVALID CNC FILENAME An error occurred in G05 DH+ communications block.
INVALID CODE PROGRAMMED FOR 7300 An invalid G or M code was programmed during 7300 tape compatibility mode.
INVALID COMMUNICATIONS PARAMETER Parameters in G05 and/or G10.2 communication blocks are incorrect.
INVALID CONTROL FOR DUAL PROCESS SYS The system executive downloaded to the control does not match the hardware configuration
established by your option chip.
INVALID CUTTER COMPENSATION NUMBER A compensation number (or TTRC number) out of the range of allowable compensation
numbers (either too large or too small) was programmed.
INVALID CYCLE PROFILE The path defining the cycle profile is not valid. This is typically caused by the cutter radius being
set to the wrong sign, being set too large, or the values for U, W, I, K, and the cutter radius
combined are not valid for the profile to be cut.
INVALID DATA AFTER A MACRO COMMAND Typically caused by a non-paramacro command following a paramacro command. Macro and
non-macro commands cannot exist in the same block.
INVALID DATA BEFORE A MACRO COMMAND Typically caused by a non-paramacro command preceding a paramacro command. Macro and
non-macro commands cannot exist in the same block.
INVALID DATA FORMAT MUST BE MM/DD/YY An invalid date format was entered. The format must be Month / Day / Year (MM/DD/YY).
INVALID DEPTH PROBE CONTROLLING AXIS The axis name which is AMPed as the controlling axis for the depth axis is not an axis that has
been configured on the system or the adaptive depth controlling axis is configured as the same
axis defined to have depth probe feedback. Refer to your AMP reference manual for details on
axis configuration.
INVALID DESKEW MASTER The AMPed name specifying the master deskew servo is not one of the AMPed axes.
INVALID DESKEW SLAVE The AMPed name specifying the master deskew servo is not one of the AMPed axes, or it has
already selected as a master axis.
INVALID DH COMMAND TYPE An error occurred in G05 DH+ communications block.
INVALID (DO) COMMAND NUMBER The specified loop number in a paramacro DO command is out of the legal range, or not found.
DO commands must be followed by a 1, 2, or 3.
INVALID (END) COMMAND NUMBER A paramacro END command has been encountered without a matching DO or WHILE, or
outside the valid range. END commands must be followed by a 1, 2, or 3, as programmed with
the corresponding DO command.
INVALID ENDPOINT IN G27 BLOCK The position programmed in the G27 block is not the home position. The end-point of a G27
block must be the machine home position.
INVALID EXPECTED LIFE The data just entered for the expected life of the cutting tool for tool management is invalid.
INVALID EXPECTED TOOL LIFE The current program is attempting to enter an invalid value for the tool management expected
life of a tool. Tool life is programmed in a G10 block with an L-word.
INVALID FB COUNTS At power up the control checks the AMP configured position and velocity feedback counts per
revolution. If either of these parameters are invalid (for this hardware type) this error appears
and the control is held in E--Stop.
INVALID FDBK/MTR TYPE COMBO When changing between an executive from system 9.xx to 10.xx some major changes occurred
to how a servo is configurated in AMP. When copying this AMP project from 9.xx to 10.xx you
must open and reconfigure some of the AMP servo group parameters before saving and
downloading to the control.
INVALID FILE TYPE An error has occurred in a file that has been sent from the ODS workstation to the control.
Typically it is the result of ODS sending the wrong file type to the control (for example, an AMP
file is sent when a PAL download is taking place, etc.). Attempt to download the file again,
making sure that the correct file type is selected when downloaded.