XT/AT/PS2/Terminal to USB Converter with NKRO

[alaricljs]

My D820 and e6410 both have opposite side USB ports, I was under the impression that 6xx series were quite similar to the 8xx.

[Soarer]

Actually, on the D800 (A11 BIOS) it seems to work OK from a cold boot, but not on restart :-/

Doesn't seem like a power issue, but I could try an external powered hub to be sure.

[Soarer]

Hmm... so on this Dell actually all devices are showing up. Strangely, the scinfo command manages to get info so the config pipes are (sort of*) working, and as I said, LED output seems fine too. But there is no input to hid_listen, even though it connects.

* USBlyzer reports the scinfo output request as successful, but not the input response. Even though scinfo gets and displays a response!

[Soarer]

I not sure that this D800 has the quite same problem as those other Dells. On this one, my converter only stopped working if I pressed F2 (or any key) before the BIOS had turned on the USB, or after it had turned it off and before Windows had turned it back on. (I think!). There is an A13 BIOS I could upgrade to and test.

I have managed to fix that bug though - the converter was getting stuck trying to wake up the PC when it was already awake. There's a couple of USB commands that I wasn't handling which enable and disable remote wakeup, so I've added handlers for them which fixed it. I've also reset a couple of internal state tracking flags when the USB connection is reset, as a precaution, since if they are wrong it could prevent any output from the converter.

Here's a new version with those fixes. I doubt it, but there is a slim chance it might fix the Dells and Ubuntu 12.

[ Attachment Invalid Or Does Not Exist ] 52483[/ATTACH]

[fohat.digs]

I don't know about anybody else's Ubuntu 12.04 problem, but mine was fixed immediately after I booted up using a (Dell) PS2 keyboard and then plugging in the F/Teensy "hot" to the USB port.

I had read about that from other people, but I never had to do it before, it had always worked for me right away.

[Soarer]

I don't know about anybody else's Ubuntu 12.04 problem, but mine was fixed immediately after I booted up using a (Dell) PS2 keyboard and then plugging in the F/Teensy "hot" to the USB port.

I had read about that from other people, but I never had to do it before, it had always worked for me right away.

Interesting... that actually makes it more similar to the Dell laptops' problem, in that something's going wrong during boot that can be worked-around by connecting the Teensy later. Or do you mean it now works through bootup, now that you've done that once?

[fohat.digs]

Yes, I think that it just had to recognize the USB device once, smooth sailing after that.

[Soarer]

Ah good. Just these pesky Dells to deal with now then! :-D

[AKIMbO]

Hey guys I need a little help with my teensy install.  I'm converting an XT to usb.  I want to wire the AT cable directly to the teensy and keep everything internally within the XT chasis.

I know I wire these 4 cables to GND, VCC, PF0 (clock), and PF1 (data).  But which wire colors correspond to those pins?
This is what I'm looking at when I open my XT.

[Soarer]

Brown = Vcc
Red = Ground
White = Data
Black = Clock

:-)

[AKIMbO]

Brown = Vcc
Red = Ground
White = Data
Black = Clock

:-)

Thank you so much Soarer.  I was pulling my hair out and second guessing myself with these wire colors.  I would have soldered them all wrong.  I`m typing this up right now on my XT.  Thanks for the guide, your help, and the awesome coding!

[Soarer]

Thank you so much Soarer.  I was pulling my hair out and second guessing myself with these wire colors.  I would have soldered them all wrong.  I`m typing this up right now on my XT.  Thanks for the guide, your help, and the awesome coding!

Haha, yeah, IBM (and Cherry) sure did pick some unintuitive colours! Good to hear of another success :-)

[Paranoid]

Hi everyone. I'm also trying to convert XT to USB (IBM model F), but when I wire it like mentioned above I don't get any result (doesn't seem to connect at all) and the teensy gets really hot! Any idea's why this is happening? I've tried v0.996 and v1.0.

[Soarer]

Hi everyone. I'm also trying to convert XT to USB (IBM model F), but when I wire it like mentioned above I don't get any result (doesn't seem to connect at all) and the teensy gets really hot! Any idea's why this is happening? I've tried v0.996 and v1.0.

Ouch, that doesn't sound good at all - the Teensy shouldn't even be warm :-(

Where the wire colours on the same pins as in akimbo's pic?
Might you have (or had) a short circuit between any wires?
If you disconnect the teensy from the keyboard, does it still get hot?

[Paranoid]

The wire colours are in the same order as in the picture (brown-red-white-black) with the tip of the connector facing upwards.
Could be that when I was testing it at first some wire pins might have touched, but now I soldered the wires so a short circuit now shouldn't exist.
If I connect only the teensy it doesn't get hot and I can still program it.

Does it matter where you connect the VCC and GRND? Because there are connections at the USB port and on the other side of the teensy board.. (I've tried both btw after the teensy wouldn't do anything)

[Soarer]

Either Vcc and GND are fine. Hate to say it, but I think somehow the Teensy has died :-( There was someone else who had a short happen, a bit more dramatic... thread.

[Paranoid]

Damn that would suck! I also can connect it to my computer and run and load the LED blinking program like the guy in your link. But I did do something before, that you mentioned in that post, when I was trying to find the correct wires (and apparantly measured it wrong the first time):
"I don't know what dies (if anything) if you apply +5V and GND swapped over - and I'm not about to try it! " - So I did actually switch GRND and VCC..
Stupid that I can't test something else to see if it works! Is there any way PJRC has a return policy or would it mean that I have to buy another one? I can't seem to find anything on their website.

[Soarer]

Reversing Vcc and GND is more likely to damage the keyboard than the Teensy, and I'm not sure if it would explain why the Teensy gets hot. (The power comes straight from the USB port, so it doesn't pass through the chip).

You said measure... does that mean you have a multimeter?

A basic test for the Teensy would be to load my firmware (any version), and measure the voltage on the clock and data pins (with no keyboard connected) - they should show 5V, if not, the chip is damaged. Then connect both clock and data to ground - it shouldn't get hot, if it does the chip is damaged.

A basic test for the XT keyboard is similar, but first I'd measure the current the keyboard is taking when connected (just to power; leave the clock and data lines disconnected). It should be between 100mA and 125mA. Then measure the clock and data line voltages - clock should show 5V, and data should show 0V. Then I'd go back to measuring the current the keyboard is taking, and short the clock and data lines to GND - the current should increase, but only by a few mA. (If you can't read the current or aren't comfortable with that, then it's still worth testing the voltages on the clock and data lines).

[Paranoid]

Yes, I do have a multimeter

I did the test that you asked. Let me sum it up:
Basic test for teensy:
 - voltage on clock and data pins with no keyboard connected: both 5V
 - clock and data to ground: the teensy (or usb cable for that matter) does not get hot

Basic test for the keyboard:
 - Current of the keyboard (only with power): 0,024A = 24mA
 - Data and clock voltage: both 0V, power dropped to 0,8V
 - Current of the keyboard (clock and data to grnd): 0,097 - 0,1A = 100mA
 - Data and clock voltage: both 0,02V, power also 0,8V
In all these cases the teensy and cable get hot.

I would say that there is something wrong with the keyboard then?

[Soarer]

I dunno... something doesn't quite add up :-)

I don't see how the Teensy would get hot when just power and ground are connected to the keyboard, and the keyboard is only drawing 24mA!

And not sure how enough current is flowing (somewhere) that the cable can get hot, without the computer just switching off the port and giving a warning.

I'm reluctant to ask you to do too many tests, since it getting hot could damage something more!

So, I'll have to think for a while :-)

Just to check - I'm imagining measuring the current goes something like this:

[Paranoid]

yes that's exactly how I did the current measurement. Maybe there's something wrong with the circuit board on the keyboard.
I'll see tomorrow evening if I can connect the teensy to another keyboard (with XT or AT) that doesn't work through a passive converter. If that works I'll probably know more.
Thanks for the help so far!

[REVENGE]

You could double check the wire config by using a multimeter and testing for continuity between the known XT pin-outs and the contacts on the internal connector.

[Paranoid]

Hi Revenge,
I checked that in the beginning. The VCC, ground and data were correct, only the clock was on pin 3 instead of pin 1. Don't really know if that's a bad thing.
But I connected the teensy either directly on the circuit board pins or through the cut wires of the connector.

[Soarer]

The VCC, ground and data were correct, only the clock was on pin 3 instead of pin 1. Don't really know if that's a bad thing.

I think that means you were reading the pinout diagram backwards - it's drawn looking looking into a socket, so you need to mirror it when looking into a plug.

[Paranoid]

hehe, that would explain why I got the grnd and vcc wrong the first try ^^ the pins and wires are correct then.

*update: so I hooked up my Cherry G80-0779H (that doesn't work through a passive converter) to the teensy and it works! With v0.996 it wouldn't work (just tried it real quick), but with v1.0 it does work
So the teensy isn't broken hooray!

Less hooray is that there is something wrong with the model F.. any clues as what could cause this?
There doesn't seem to be anything slighty burned on the circuit board. Although that doesn't really tell us anything. (the white stuff is from the sticky thing that's covering the board)
[ Attachment Invalid Or Does Not Exist ] 53572[/ATTACH] [ Attachment Invalid Or Does Not Exist ] 53573[/ATTACH] [ Attachment Invalid Or Does Not Exist ] 53574[/ATTACH] [ Attachment Invalid Or Does Not Exist ] 53575[/ATTACH] [ Attachment Invalid Or Does Not Exist ] 53576[/ATTACH] [ Attachment Invalid Or Does Not Exist ] 53577[/ATTACH]

[Soarer]

Sorry, I missed the update :-)

I'm still puzzled why the teensy and cable get hot, with the keyboard apparently only taking 24mA of current... that doesn't make any sense!

If it wasn't for that, I would agree that the keyboard has been damaged.

[Parak]

For my second F122 refurbishment, I took some of these that I had lying around and four pin headers with the posts removed bent slightly at the end:

[ Attachment Invalid Or Does Not Exist ] 53798[/ATTACH]

Apply shrinkwrap:

[ Attachment Invalid Or Does Not Exist ] 53799[/ATTACH]

Now that I think about it, this would have been better if I soldered the pins from the back instead. Oh well.

[Soarer]

That's pretty neat :-)

Put the pins on the back you mean? But then you'd have bits sticking out on both sides!

[Parak]

It would have looked a bit neater as the d0/d1 pins could have been flush, but then I guess there also would have been a slight worry with the teensy being all covered up by the heatshrink and the button being possibly permapressed..

[fohat.digs]

I am probably just dense or incompetent, but here are 2 questions:

1. How to I get to the original article and instructions? I can get this thread, but not the article itself. I want to re-read the instructions from the beginning.

2. Can multiple Teensies be run simultaneously?

I have an F-122 with internal Teensy that I cut, wired, and installed last year, and have been running flawlessly since, including surviving a format and upgrade from XP to 7 with no additional work on my part (Wow!).

Now I have a new keyboard Teensy which I want to install in an outboard box with a socket to accept original cables. I would also like to upgrade to the latest firmware/software "just because" it seems to make sense.

First, if 2 Teensies are plugged in via USB, will my computer be confused? Should I use a conventional keyboard while setting up the new Teensy?

Second, what is involved in upgrading from 0.997 or whatever to 1.02?

Thanks!