System Messages - Alphabetical List Press HIGH POWER button to enable power (57) Explanation: The high power on/off button on the front panel must be pressed to complete the process of enabling high power. User action: When the high power on/off button on the Controller Interface Panel (CIP) blinks, promptly press the button to complete the two-step process of enabling high power. (You must press the button within the time period specified in the eV+ configuration data.) Press HIGH POWER button when blinking (60) Explanation:
When enabling power for Cat3 systems which are in manual mode, the HIGH POWER ON/OFF button on the front panel must be pressed after the Hold-to-run button has been released and held. The light on the HIGH POWER ON/OFF button will blink when it is time to press it. You must press the button within the time period specified in the eV+ configuration data (which by default is ten seconds). User action: When the HIGH POWER ON/OFF button on the VFP blinks, promptly press the button to complete the two-step process of enabling high power. *Processor crash* CPU = n (None) Explanation: eV+ has detected that the specified CPU within the controller has entered a fatal error state.
A crash message from that processor is displayed immediately following. A software error or hardware problem with that processor is likely. User action: It would be appreciated if you would report the error to Omron Adept Application Engineering. Please include the details of the error message and exactly what you were doing at the time the error occurred. You should store the programs that are in memory, power down the controller, and start it again. (If the processor ID shown is 1, you can restart eV+ by pressing Ctrl+G. The robot servos do not function, but you can STORE the programs in memory.) If the problem persists, contact Omron Adept Customer Service.
*Program already exists* (-309) Explanation: An attempt has been made to LOAD a program that already exists, or to COPY or RENAME a program to a name that is already in use. User action: Delete the conflicting program or use a different name. *Program argument mismatch* (-408) Explanation: The arguments in a CALL, CALLS, or EXECUTE instruction do not match the arguments in the program being referenced because they are of different types. User action: Modify the CALL, CALLS, or EXECUTE instruction, or the .PROGRAM statement of the referenced program, so that the argument types match. If arguments are omitted in eV+Language Reference Guide, v2.x, 18319-000 Rev A Page 638