System Messages - Alphabetical List User action: Modify the program as required. *Attempt to modify active belt* (-614) Explanation: A program instruction has been executed that modifies the belt variable that is currently being tracked by the robot. User action: Change the program in order not to modify the variable while the robot is tracking it. *Attempt to redefine variable class* variable_name (-470) Explanation: Upon exiting from the editor, the named variable was found in two of the following places: the .PROGRAM argument list, an AUTO statement, a LOCAL statement, or a GLOBAL statement. User action: Modify the program to include the variable in only one of these places.
*Attempt to redefine variable type* variable_name (-469) Explanation: If a program is being edited, the line just entered contains a reference to a variable in a manner inconsistent with its use elsewhere in the program. The most likely problem is confusing a location variable with a real variable. If you just exited from the editor, the named variable conflicts with a global variable that already exists. User action: If the new use of the variable is correct, you must delete all references to the incorrect variable and then reenter the statement that caused the error. If the new use is incorrect, use a different variable name.
If there is a conflict with a global variable, either use a DELETE_ command to delete that variable, or make the conflicting variable AUTO or LOCAL to the current program. Auto Startup... (None) Explanation: The automatic start-up procedure has begun. (See the discussion of command programs for more information.) User action: None required for this message, but subsequent commands in the auto- startup command program may require user action. WARNING: The robot may begin to move during the automatic start- up procedure. If necessary, you can stop the robot by pressing EMERGENCY STOP or the controller or PANIC on the pendant. *Backplane E-STOP detected by CPU* (-630) Explanation:
The AdeptMotion system has detected an error or problem and has asserted the BRKSTOP signal on the VME bus. If that error is seen, it indicates a transient BRAKE- ESTOP signal. eV+Language Reference Guide, v2.x, 18319-000 Rev A Page 588