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

AT2XT keyboard converter

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

    #46
    Originally posted by acadiel View Post
    Any suggestions to where I can start figuring out what's going on?
    Member schnurzel came up with some alternative firmware for the converter's PIC chip. It maybe the answer. Available at [here].

    You will need a device that can program the firmware into the 12F629 PIC chip. Alternatively, some of the people/companies at [here] could supply a programmed 12F629 for you.

    Comment


      #47
      Originally posted by modem7 View Post
      Member schnurzel came up with some alternative firmware for the converter's PIC chip. It maybe the answer. Available at [here].

      You will need a device that can program the firmware into the 12F629 PIC chip. Alternatively, some of the people/companies at [here] could supply a programmed 12F629 for you.
      Thanks!

      My 844USB can program those - I'll give it a try.

      Comment


        #48
        Originally posted by modem7 View Post
        Member schnurzel came up with some alternative firmware for the converter's PIC chip. It maybe the answer. Available at [here].

        You will need a device that can program the firmware into the 12F629 PIC chip. Alternatively, some of the people/companies at [here] could supply a programmed 12F629 for you.
        I've got the chips and programmer, but I'm a bit stuck at what I need to care about at this screen... have any guidance? Thanks!

        options_pic.png

        Comment


          #49
          Originally posted by acadiel View Post
          I've got the chips and programmer, but I'm a bit stuck at what I need to care about at this screen... have any guidance? Thanks!
          I am unfamiliar with that programmer, but the operation should be as simple as read in the HEX file, then program the chip.

          Comment


            #50
            You want to check the "User program" and "Configuration" boxes. Leave the rest alone, particularly OSCCAL, which is set at the factory.

            Comment


              #51
              I am having an odd bug/issue with my AT2XT.
              I am using Sergey's Micro8088 and the AT2XT that is part of the design.
              Most everything seems to be working correctly except...

              Shift + arrow keys.
              If I use the numpad, shift+arrow keys work as expected in edit.com and other text editors to highlight text.
              If I use the inverted T arrow keys, shift+arrow key acts as if shift is not being held and the cursor moves with no highlighting.

              I am setup to convert my CF card to a virtual disk image and back, all of that works reliably. So using the exact same drive image & utilities, shift + inverted T arrows works as expected in VirtualBox, so I'm left pointing fingers at the AT2XT.

              Is this a known issue, is this something I missed in configuration?

              Thank you.

              Comment


                #52
                I found references to this problem online. The only suggestion was to upgrade from 0.94 to 0.1d. I've tried that with no change to the shift + inverted T arrow keys behavior.

                I may be expecting behavior that can't happen or otherwise misunderstand AT2XT, as I have a key scanning program which shows some odd behaviour of the shift key pressing itself when using the inverted T arrow keys, so I'm guessing the AT2XT is translating the arrow keys into num pad arrow presses depending if Numlock is on or not.
                Last edited by TheDrip; October 24, 2020, 02:26 PM.

                Comment


                  #53
                  Originally posted by modem7 View Post
                  Member schnurzel came up with some alternative firmware for the converter's PIC chip. It maybe the answer. Available at [here].

                  You will need a device that can program the firmware into the 12F629 PIC chip. Alternatively, some of the people/companies at [here] could supply a programmed 12F629 for you.
                  The alternate firmware above worked great with my Tandy 1000 SL/E.

                  Just wanted to let everyone to know - try that firmware if you have a Tandy 1000 SL/TL/RL/RLX system.

                  Comment


                    #54
                    Originally posted by Chuck(G) View Post
                    You want to check the "User program" and "Configuration" boxes. Leave the rest alone, particularly OSCCAL, which is set at the factory.
                    I checked those two boxes and it worked great. Thanks!

                    Comment


                      #55
                      Originally posted by deathshadow View Post
                      This guy:
                      http://www.kbdbabel.org/

                      Has done several strange keyboards to AT converters, including PC/XT. I agree with @Stone it's not the most useful of directions to my mind, but it has been done. If anything the simpler protocols are easier to read than AT, making such conversion actually simpler to implement than the other direction.

                      It's one of the sources I've been using for information -- and what led me to question the PC/XT timing info I was seeing as the math on his charts:

                      http://www.kbdbabel.org/signaling/index.html

                      ... don't seem to add up right, and are inconsistent with how most clocked protocols have a delay to compensate for rise/fall time.
                      Wow this is nice. I have seen some old keyboards at my friend's home and they were really amazing. If you want I can share some of the images of it with you.

                      Comment


                        #56
                        does anybody know working HEX for XT Zenith Z-150 keyboard (XT "black label" version)

                        here is written more about it ... but my knowledge does not allow me to modify the code

                        https://deskthority.net/viewtopic.ph...art=30#p354189

                        Comment


                          #57
                          does anybody has a working HEX for "Zenith Z-150 XT(black label)" keyboard

                          it has different signals
                          I found info about it

                          This is a "normal" XT keystroke with the DATA line held normally low, and CLK normally high. When ready to send a code, 10 CLK falling edges are sent: 2 start bits, 8 data bits, for a total of 10 bits:

                          Image

                          This is a keystroke from the Z-150. The DATA line is held normally high (opposite). When ready to send a code, only 9 CLK falling edges are sent for a total of 9 bits. I'm guessing there is only 1 start bit.
                          the text is taken from here , also there a pictures from logic analyzer

                          https://deskthority.net/viewtopic.ph...art=30#p354189

                          Comment

                          Working...
                          X