System Messages - Alphabetical List User action: Perform one or more of the following: (1) if the trajectory cycle time is less than 16 msec, change it to the next longer time; (2) move servo tasks off CPU #1 to allow more time for trajectory generation; (3) upgrade the system processor to increase the throughput; (4) reduce the number of robots or axes that you are operating; or (5) if the trajectory cycle time is set to 2 msec, make sure the servo interval is 1 msec. *Unable to acquire an image from camera* (-776) Explanation: ACE Sight is unable to acquire an image. User action: Verify that camera is plugged into the SmartVision EX vision controller.
Make sure the drivers are working properly. Change the camera if necessary. *Unable to read the robot position latch* (-777) Explanation: The robot position has not been latched. User action: Verify the latch signal cabling. Verify the latch signal configuration in eV+. *Undefined program or variable name* (-406) Explanation: The program or variable, referenced in a command or program step, does not exist-possibly because the name was mistyped. User action: If the correct name was entered, create the program or variable using one of the eV+ editors or the appropriate eV+ monitor commands, or by loading from a disk file. *Undefined value* (-401) Explanation:
(1) A variable has been referenced that has not been assigned a value. (2) Using the SEE editor, an attempt has been made to use a macro, return to a memorized cursor position, or perform a repeat string search or change without first performing the appropriate initialization sequence. User action: (1) Assign the variable a value or correct its name. (2) Define the macro, record a cursor position, or enter the desired search/replacement string (s). *Undefined value in this context* (-420) Explanation: An automatic variable or subroutine argument value appears in a monitor command, but the specified program is not on the execution stack for the specified program task.
Automatic variables and subroutine arguments have values only when the program that defines them is on a stack. User action: Change the monitor command to not reference the variables. Make sure that the program is on the expected execution stack. You can place a PAUSE instruction or breakpoint in the program to stop it while it is on the execution stack. eV+Language Reference Guide, v2.x, 18319-000 Rev A Page 657