System Messages - Alphabetical List User action: Specify all subsequent windows as /NOCLOSEABLE, or delete some existing windows that appear in this pull-down. *Too many network errors* (-536) Explanation: (1) The number of errors detected by the DDCMP protocol has exceeded the maximum allowed. The local protocol is stopped, and all pending I/O requests are completed with this error. (2) The eV+ Kermit driver experienced more errors than permitted by the KERMIT.RETRY parameter. User action: (1) Use the NET monitor command to determine the type of errors that have occurred.
Check for noise on the communication line, errors in the remote DDCMP implementation, or program logic that sends messages faster than they can be processed. Use the appropriate FCMND instruction to increase the maximum number of errors. (2) Set the KERMIT.RETRY parameter to a larger value, increase the retry threshold on the remote server, restart the Kermit session, and retry the operation that failed. *Too many vision requests pending* (-703) Explanation: A program has issued too many VLOCATE commands before the first ones have completed. User action: Edit the program to wait for pending VLOCATE requests to complete before issuing more. *Too many windows* (-550) Explanation:
An attempt was made to create a graphics window when the maximum number of windows were already defined. (The eV+ system uses two windows for the screen and the top status line. Every title bar, menu bar, and scroll bar is a separate window. The pull-down window is always allocated even if it is not visible. Systems with AdeptVision always have the vision-training window allocated.) User action: Where possible, change your window definitions to omit menu bars and scroll bars. If necessary, use the utility program CONFIG_C to increase the number of window buffers. *Trajectory clock overrun* (-636) Explanation: One of these three conditions has occurred:
(1) the time for a new trajectory point has arrived, but the internal trajectory task has not finished computing the previous point; (2) the servos did not receive trajectory data at the expected time because the trajectory task took too long to compute and write out the data; or (3) the trajectory interval is equal to or less than the servo interval. eV+Language Reference Guide, v2.x, 18319-000 Rev A Page 656