deskthority

Maybe something like this?

The LED would be connected to 2 resistors, so it would glow dimly, until the switch makes a connection that bypasses one of the resistors so it can run at its maximum spec.

Trouble is, although that would change the current flowing through the LED, there isn't an easy ...

If you scan the rows and columns, you could illuminate any individual LED or set of LEDs. Perhaps have each key light when pressed, or backlight the entire board, and have the key extinguish when pressed.

Well, of course, but you'll be adding a fair amount of circuitry and/or specialised driver ...

For 'on all the time' you can wire to one of the two +5V pins on the Teensy and draw up to the USB limit (minus a bit for the Teensy); no need to extend and tap the USB cable itself.

Even 5mA per LED would be too much really (well, how many LEDs?). Aren't you still thinking about the mA rating ...

Yeah, well, they often just switch the LEDs with a FET that can take the current.

PWM and bigger resistors have the same effect - reducing average current, and reducing brightness. PWM might not be the best choice if peak current is still over the 500mA USB limit!

Don't forget, manufacturers shave ...

*Sigh*

Nothing in the Alps world is ever simple or able to be tidily tagged

Whatever, this is not a debate I'm willing to continue. If the answer to "Why not call it 'SGI Keyboards'?" is that SGI never actually made any, then you could just say so instead of posting childish insults.

No, I wasn't being sarcastic, it just seems the logical way to go if there is any uncertainty about the manufacturer. Are you certain that all these SGI Bigfoots are simply rebrands? Were the Granite Bigfoots made by Alps using SGI's special granite sauce plastic, or did SGI have them made ...

Of course it's "precious" - a decent layout, Alps switches, and PS/2 interface all combine to make it so.

Do you actually know that the Indigo² models (part numbers 9500820 and 9500829) are not PC compatible? Are they not in fact PS/2? The only difference that I know of is the colour. There's a ...

SGI Granite may well be a nickname and slightly ambiguous, but it's by far the most commonly known descriptor of that keyboard.
Why is that keyboard special? It just seems like a "precious snowflake" problem, that it has to be segregated because it's "pretty". It's not special for being PS/2, or ...

SGI Granite may well be a nickname and slightly ambiguous, but it's by far the most commonly known descriptor of that keyboard.

SGI Bigfoot? Enlightenment? No.

Now that we know of the nickname Bigfoot - for a group of (generally?) Alps based keyboards - then of course there should be a page that ...

Caps - ok for blanks

More symmetry:

Yeah, along the top row of pins, from left to right in that pic it's: nc, +5V, nc, GND, Data, Clock, nc.

So supporting a dozen or so keyboards with 8 different matrix layouts in one converter isn't enough for you?! :lol:

There are differences in the way WYSE / IBM / ADB drive the lines that make them fundamentally incompatible, and even without that, auto-identify might cause issues. A future Soarer ...

Hah, well, one reason I cross-posted my converter here was all the rollbacks on GH. I think I updated the thread there to "v1.0" about 3 or 4 times

Not the only reason by a long way of course

Introduction

This firmware for Teensy 2.0 etc. aims to convert all WYSE terminal keyboards which have a 4P4C connector, to USB.

See Wyse keyboard protocol (4P4C) for more information about the protocol and the models that use it.

(There's also a thread for this project on GH ).

Features

All ...

He did mention that he'd found a couple with your name on when he dug mine out, and asked if you were stilll around.

webwit wrote:Left shift plus cursor key releases shift.

... with SGI Granite and Dell AT101/102, IIRC.

The data signal could use any pin, but for my code the clock signal needs to be on an pin capable of generating interrupts on both low-high and high-low edges. So that's one of PD0..3 or PE6, on an ATmega32U4.

Sould be fine to connect that directly, and use something like "unstrobed -PB0 F1" in your config. ('-' because it will go low when pressed). You might need to adjust your debounce settings to suit it.

There's one big problem with that idea - I haven't released the source code yet, and no idea when I will!

You're gonna kick yourself This is Controller, not Converter!

Can't promise when anything KVM friendly will come along (pretty busy at the moment), but haven't forgotten about it. I guess we could try a test first that simply removes the NKRO/Media endpoint.

Pro Micro pinout with non-Arduino-weeny names...

Good news! Made contact and sorting out the shipping now

I might well take you up on that, thanks! Even if he ever does get back to me, I doubt he'll have good news. Sent him a PM on reddit also.

They're still only $25, apparently. What costs on these is mostly shipping and taxes

7bit, did you get your boards from that round?

Really?

So did she throw out the IBM boards while he sleeps on the sofa?

Has anyone heard from fossala at all since June? I emailed his paypal address a few days ago, but no reply.

He still owes me (and presumably others) IBM/Alps boards from the second round of him proxying them.

Not sure whether to be worried about him, or just annoyed that he wandered off!

Yeah, but... pretty colourful pictures

Right, I just tried installing Wine on Linux Mint 14 (nadia), and at first scla.exe didn't run due to missing MFC71.dll.
The solution is to run winetricks and install vcrun2003

I'd really like to have just the 'D', for the home row, in DCS, as well. Got far too many novelty F-row caps already!
Colours to match Dolch, or just black/white, not too fussed.