An out of sync keyboard is one in which the one or more of the keyboard special keys - that is, the numlock, control , alt, etc. keys - appear to be depressed when the keyboard LEDs say that it is not - or vice versa. This document is a checklist to run through to isolate and resolve the cause of this.

First, confirm that you have CCI Concurrent V3.05 release 8C or greater (XIOS date of 09/10/92). If you do not, we will provide an update at no charge, if you are running V3.05. If you are running V3.04 or less, there is a nominal upgrade fee that our sales team can help you with. To troubleshoot you will need two stations, one that displays the "out-of-sync" problem and another on which to run the diagnostics. You will need to know the port and user numbers of the "out-of-sync" terminal. Start with both stations in sync, and before going ahead, make whatever entries are necessary to put the first station out-of-sync. Please complete each step before going on to the next.

1. First use TERMSET on the second station to confirm the "out-of-sync" condition on the first. TERMSET Ux should reflect that one or more of the terminal keyboard special keys (CAPSLOCK, NUMLOCK, ALT, etc.) are set differently from what the LEDs on the keyboard show. For example, your NUMLOCK light is on but TERMSET says it is OFF.
2. If you are using an intelligent I/O board, go on to step 3.. If you are using a standard I/O board, use CCICOUNT on the second station to check for serial overruns, parity and/or framing errors on the serial channel to which the out-of-sync terminal is attached. If you have any of these errors, it means that characters are being lost; this usually results in a station keyboard getting out-of-sync. The serial overruns must be corrected to fix the out-of-sync condition.

   Possible causes of the serial overruns, check and eliminate, one by one:

   1. power glitches (reflected by framing errors)
   2. bad cabling (reflected by serial overruns)
   3. using polled mode in CONFIG (reflected by serial overruns)
   4. using a device driver (in CCONFIG.SYS) that disables interrupts for too long (reflected by serial overruns)
   5. bad bus timing (reflected by some or all three types of errors)
   6. terminal firmware setup (in particular, the terminal pacing - that rate at which characters are sent from the keyboard to the system - is critical. IBM 3151 calls it PACING, Wyse terminals call it XMIT LIMIT, Relisys terminals call it KEYCODE TX LIMIT; set it above 0, but as low as possible.)NOTE: on Relisys terminals, you may have to use 60 rather than the 30 we would normally recommend if serial overruns persist at the 30 setting. This has been reported to Relisys and is under investigation.

If no serial overruns are shown, go to step 4.

3. If you are using intelligent I/O boards, characters can't be lost by the operating system and the possible causes are greatly decreased. Please check the following:
   1. power glitches (reflected by framing errors)
   2. bad cabling (reflected by serial overruns)
   3. bad bus timing (reflected by some or all three types of errors)
   4. terminal firmware setup  - see item f in number 2 above.

5. If you eliminate all of the possible causes, and your operating system is 8C or later, then call CCI technical support .  Please have printscreens of your TERMSET, CONFIG, CCICOUNT and CCONFIG contents, and a CCIDUMP of the system ready when you call.