Announcement

Collapse

Forum etiquette

Our mission ...

This forum is part of our mission to promote the preservation of vintage computers through education and outreach. (In real life we also run events and have a museum.) We encourage you to join us, participate, share your knowledge, and enjoy.

This forum has been around in this format for over 15 years. These rules and guidelines help us maintain a healthy and active community, and we moderate the forum to keep things on track. Please familiarize yourself with these rules and guidelines.


Remain civil and respectful

There are several hundred people who actively participate here. People come from all different backgrounds and will have different ways of seeing things. You will not agree with everything you read here. Back-and-forth discussions are fine but do not cross the line into rude or disrespectful behavior.

Conduct yourself as you would at any other place where people come together in person to discuss their hobby. If you wouldn't say something to somebody in person, then you probably should not be writing it here.

This should be obvious but, just in case: profanity, threats, slurs against any group (sexual, racial, gender, etc.) will not be tolerated.


Stay close to the original topic being discussed
  • If you are starting a new thread choose a reasonable sub-forum to start your thread. (If you choose incorrectly don't worry, we can fix that.)
  • If you are responding to a thread, stay on topic - the original poster was trying to achieve something. You can always start a new thread instead of potentially "hijacking" an existing thread.



Contribute something meaningful

To put things in engineering terms, we value a high signal to noise ratio. Coming here should not be a waste of time.
  • This is not a chat room. If you are taking less than 30 seconds to make a post then you are probably doing something wrong. A post should be on topic, clear, and contribute something meaningful to the discussion. If people read your posts and feel that their time as been wasted, they will stop reading your posts. Worse yet, they will stop visiting and we'll lose their experience and contributions.
  • Do not bump threads.
  • Do not "necro-post" unless you are following up to a specific person on a specific thread. And even then, that person may have moved on. Just start a new thread for your related topic.
  • Use the Private Message system for posts that are targeted at a specific person.


"PM Sent!" messages (or, how to use the Private Message system)

This forum has a private message feature that we want people to use for messages that are not of general interest to other members.

In short, if you are going to reply to a thread and that reply is targeted to a specific individual and not of interest to anybody else (either now or in the future) then send a private message instead.

Here are some obvious examples of when you should not reply to a thread and use the PM system instead:
  • "PM Sent!": Do not tell the rest of us that you sent a PM ... the forum software will tell the other person that they have a PM waiting.
  • "How much is shipping to ....": This is a very specific and directed question that is not of interest to anybody else.


Why do we have this policy? Sending a "PM Sent!" type message basically wastes everybody else's time by making them having to scroll past a post in a thread that looks to be updated, when the update is not meaningful. And the person you are sending the PM to will be notified by the forum software that they have a message waiting for them. Look up at the top near the right edge where it says 'Notifications' ... if you have a PM waiting, it will tell you there.

Copyright and other legal issues

We are here to discuss vintage computing, so discussing software, books, and other intellectual property that is on-topic is fine. We don't want people using these forums to discuss or enable copyright violations or other things that are against the law; whether you agree with the law or not is irrelevant. Do not use our resources for something that is legally or morally questionable.

Our discussions here generally fall under "fair use." Telling people how to pirate a software title is an example of something that is not allowable here.


Reporting problematic posts

If you see spam, a wildly off-topic post, or something abusive or illegal please report the thread by clicking on the "Report Post" icon. (It looks like an exclamation point in a triangle and it is available under every post.) This send a notification to all of the moderators, so somebody will see it and deal with it.

If you are unsure you may consider sending a private message to a moderator instead.


New user moderation

New users are directly moderated so that we can weed spammers out early. This means that for your first 10 posts you will have some delay before they are seen. We understand this can be disruptive to the flow of conversation and we try to keep up with our new user moderation duties to avoid undue inconvenience. Please do not make duplicate posts, extra posts to bump your post count, or ask the moderators to expedite this process; 10 moderated posts will go by quickly.

New users also have a smaller personal message inbox limit and are rate limited when sending PMs to other users.


Other suggestions
  • Use Google, books, or other definitive sources. There is a lot of information out there.
  • Don't make people guess at what you are trying to say; we are not mind readers. Be clear and concise.
  • Spelling and grammar are not rated, but they do make a post easier to read.
See more
See less

Kaypro 16/2 "check keyboard" error

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Kaypro 16/2 "check keyboard" error

    So I won a Kaypro 16/2 at a local auction. It seems to boot to DOS, but always gives a "check keyboard" error. Someone told me it was bad capacitors in the keyboard logic. The capacitors used in the keybaord logic are marked "641" and I assume they are 640pf, which is an odd size that I cannot find anywhere. I'm hoping that's not the problem. Any other ideas? I really want to get this working!
    Thanks

    #2
    Welcome to these forums.

    I see you have a related thread at [here], which I will also quote from.

    Originally posted by Thunderbird 98
    At first I thought it was the keyboard itself, but now I know that there is something wrong with the keyboard logic on the processor board.
    How do you know that the problem is the 'processor' board, and not the keyboard? To determine that (using no test equipment), you would have had to have used a 'known working' keyboard.

    Originally posted by Thunderbird 98
    I found a schematic of the 16/2 which I've attached below.
    Based on that schematic, the keyboard interface logic on the 'processor' board is part of the 8255 chip, plus what you see at [here], plus a decoupling cap for each chip. Any of those components could be faulty (assuming the 'processor' board contains the fault). A bad solder joint on the connector is also a possibility.

    Originally posted by Thunderbird 98
    Someone told me it was bad capacitors in the keyboard logic.
    Presumably they included the word "might" or "may". If not, how do they know the problem cause?

    Originally posted by Thunderbird 98
    The capacitors used in the keyboard logic ...
    * According to the partial circuit diagram that I pointed to earlier, C6, C7, and C8, are 47 pF. Likely to be of ceramic type.
    * According to the partial circuit diagram that I pointed to earlier, C9 is 10 uF. Likely to be of tantalum or aluminium electrolytic type.
    * A decoupling cap for each chip.

    Originally posted by Thunderbird 98
    ... are marked "641" and I assume they are 640pf, ...
    See how in the photo, each is located at the end of a chip. C31, for example, is the decoupling cap for the pictured 74LS175.

    They appear to be type ceramic of value 640 pf.

    Originally posted by Thunderbird 98
    ... which is an odd size that I cannot find anywhere.
    I cannot see how an open-circuit failure of a decoupling cap could cause an always-appearing "check keyboard" error. In my opinion, at worst, maybe the occasional "check keyboard" error.

    Originally posted by Thunderbird 98
    Any other ideas? I really want to get this working!
    What test equipment do you have?

    Comment


      #3
      With testing equipment, all I have is a multimeter.
      I assumed that the keyboard was fine, but it could be broken...

      Comment


        #4
        Originally posted by Thunderbird 98 View Post
        With testing equipment, all I have is a multimeter.
        I assumed that the keyboard was fine, but it could be broken...
        I am unfamiliar with the Kaypro 16/2. I assume that "check keyboard" is a result of the computer's power-on self test (POST) sending a signal to the keyboard, and not seeing the expected signal back from the keyboard. If that is the case, then I see the possibilities as:
        * Faulty keyboard
        * Faulty processor board
        * Faulty cable that runs between J1 on the processor board and the DIN connector at the rear of the computer.
        * Aforementioned cable not connected properly to the J1 connector on the processor board. Re-seat the plug on J1, and ensure it is plugged on correctly.

        Do a thorough visual inspection.

        It would be good if you can find someone local that has a working Kaypro 16/2, and trying their (known working) keyboard. That would quickly rule out/in half of the keyboard related circuitry. Maybe someone here knows of a different keyboard that is known to work with the Kaypro 16/2.

        With a multimeter, you have the ability to see logic high and logic low levels within the processor board's keyboard interface circuitry. But a question becomes, "What are the normal levels expected to be seen on the various pins?" That is not always straightforward. For example, I found that in the IBM XT, certain failure modes of the XT's keyboard interface circuitry can result in the POST putting the 8255 chip's pins into unexpected states (including a case where the 8255's PB6 pin was constantly alternating).

        You could gain some confidence in the processor board's keyboard interface circuitry, by finding someone else online who has a working Kaypro 16/2, and doing logic high/low comparisons between the two computers. But that could be wasted effort because the keyboard is what is at fault.

        Comment


          #5
          Apparently the 16/2 isn't very common, but I know someone who is knowledgeable on IBM PC stuff.
          Thanks for the help!

          Comment

          Working...
          X