USB-to-Sun Keyboard Adapter using Arduino Micro

It's my firm belief that the best keyboard in history is the Sun Type 5 UNIX Layout. It big, heavy, chunky, blocky, and feels wonderful to me. What's more? It's the UNIX keyboard and the first keyboard I ever fell in love with. Sadly, the Sun Type 5 only works with Sun workstations.

The Type 6 keyboard was available with USB, and thats the keyboard I use every day, but it was sleaked down from the chunky glory that was the Type 5. The Type 7 was something of a middle-ground, the blocky figure of the Type 5 but it was made with cheap plastics and lacked the heaft of the Type 5.

So, for the last 10+ years I've had a dream of converting Sun Type 5 to USB so I can live the dream. Commercially available adapters have been on the market forever, but they typically cost $150+, outside of my budget. Some adventurous souls have created their own adapters, but they seemed overly complicated given the task. What I really wanted was to create my own, simple, affordable adapter.

Last month I came across an Adafruit tutorial that rekindled my old desire: USB NeXT Keyboard with an Arduino Micro. The links provided happened to include the pin-out of the Sun Type 4/5/6 keyboards and some pointers on how to build the adapter. So I found the right plug on Mouser and on New Years Eve got to hacking on it. New Years day I had a working Sun Type 5 on my MacBook!

How to Build

You will require:

An Arduino based on the Atmel 32u4 chip, these are required by the Arduino Mouse & Keyboard libraries which you'll need for the Arduino to act as a keyboard adapter
A USB Type A to USB Micro B cable to attach the Arduino to your computer
An MD-80PL100 Mini-Din 8a (female) panel connector
A Sun Type 5 Keyboard! (UNIX Layout preferably!)

The Sun keyboard uses a Mini-Din 8a connector. Thanks to Alexander Kurz you can find the Sun Type 4/5/6 Pinout on kbdbabel.org:

You'll notice that they keyboard has its own Vcc +5v & Ground as well as a "from keyboard" and "to keyboard". You also have 3 more wires providing Vcc +5V & Ground plus a single read line for the mouse! (We'll ignore the mouse for now).

Lets connect to our Arduino! If you buy the MD-80PL100 I recommended above (PDF datasheet]), the write mapping will be:

Keyboard Kable	Arduino Micro
Pin 2 (Black)	GND
Pin 8 (Red)	+5V
Pin 6 (Blue)	D14 (Serial RX)
Pin 5 (Brown)	D15 (Serial TX)

Wire it up and then you just need to upload the sketch!

Packaging Ideas

If you are just playing around with a Sun keyboard, build it on a breadboard and then reclaim the parts for other projects.... but if you want to build a perminant solution, read on.

There are several ways you can package this solution. As of January 2017 there are no Arduiono Micro's sold without headers. The knock-off Micro's on Amazon all have bad reviews, so I'm avoiding them. You can either de-solder the headers on a genuine Micro or use snips to clip off the leads for packaging.

One idea is to follow Adafruits favorite pattern and use an Altiods tin like they did for their NeXT Keyboard adapter.

Another option is to perminantly build this adapter into a Sun keyboard. If you open the case of the keyboard you'll find the circuit board on one side but a lot of extra room on the other. Using non-conductive epoxy or foam tape (such as 3M VHB Tape RP32) you could mount the Arduino right inside, exposing only the USB cable. If you do this and are willing to damage the keyboard perminantly, you could cut off the cable and splice (or de-solder it completely), connecting directly to the Arduino bypassing the Mini-Din connector completely!

How the Keyboard and Software Works

This solution is gloriously simple! The simplicity is thanks to the capabilities of the Arduino hardware/software and the cleverness of Sun engineers.

The Sun Keyboard is actually a 1200 baud serial device. Seriuosly. That sounds odd but is actually wonderful because the Arduino can easily interface with it using the Serial Library. We can also use the Arduino Keyboard/Mouse Library to write to the computer. Therefore, all we need to do is read from the serial output of the keyboard, translate each key from the Sun scancode to the ASCII equivilent and then write the ASCII to our computer as keyboard input!

By using the Arduino Serial Monitor and a simple sketch to listen, we can see what they keyboard is sending. Press "a" on the keyboard and we get the following (decimal) output to the monitor:

77
-51
127

After some playing around, you'll realize that the 3 values send by the keyboard have 3 meanings represending different actions:

77: 77 is the code representing the "a" key being pressed down
-51: This indicates the key being released (key up), but which key? Add this value to 128 to determine the key! 128-51=77, so the "a" key is being released. Clever right!?!
127: This code is sent when no other key is being pressed, it is the "all clear" message.

You can verify this all by pressing and holding "a", then pressing and holding "b", then "c", and then release each key one at a time. You'll clearly see the key downs, key ups, and releases.

It just so happens that these map perfectly to our Arduino library!

In SunKeyboard-to-USB/sun_keyboard_map.h I created an array mapping the Sun scancode (as the array index) to the equivilent ASCII charactor. You'll notice several keys map to "0" because they aren't supported by the Keyboard library (or PC's for that matter). By messing with this array you can re-map keys as you wish (such as making Caps Locks Control for PC Layout).

Once you have the Sun to ASCII map worked out, everything is simple! We listen on Serial for input. If we get a number between 1 and 126 we look it up in the array and then pass the result (ASCII) to Keyboard.press(). If we get a number less than 0 we know this is a key-up event, so we add to 128 to find the key which we then lookup in the array and pass to Keyboard.release(). Finally, if we get 127 as input, we know that no keys are being pressed, so we send Keyboard.releaseAll()!

Couldn't be simpler.

LED Control & Sending Commands to the Keyboard

Commands can be sent on the serial line to the keyboard. Because they aren't emitted from the keyboard its harder to discover them through trial-and-error, thankfully in my search I finally found the document I needed from the beginning: The SPARC International: SPARC Keyboard Specification. Contained within are the pinouts, the scancodes, and most importantly the serial commands! On page 17 of the PDF you'll find the serial protocal and the commands you can send:

0x01: Reset
0x02: Bell On
0x03: Bell Off
0x0A: Keyboard Click On
0x0B: Keyboard Click Off
0x0E: LED Command
0x0F: Layout Command

The Bell is simply a loud computer speaker sound. Normally it should only be used in short bursts (like the one your PC makes when it turns on) by sending 0x02, then delay 100ms, then send 0x03 to turn off. Once turned on it will make a solid tone until you turn it off.

The Keyboard Click is something you may remember from the old WYSE & HP Terminal days. When enabled you will get a little "chirp" sound every time you press a key. It brings back nostalgia for about 10 seconds and then is incredibly annoying.

I'm not using the Layout command because I found the scan codes for both PC & UNIX layouts are the same, so I don't currently see a need for this.

The Reset seemed promising but ultimately I found little utility in it. I experimented with sending it during keyboard setup in my Arduino code, but it seemed to have no utility.

The LED Command is the important one. You must send 2 bytes, the first is the LED Command 0x0E and the second is a 4-bit bitmask which determines which of the 4 LED's are on or off:

                   0000 All off
                   0001 Numlock         == 1
                   0010 Compose         == 2
                   0100 Scroll          == 4
                   1000 Caps Lock       == 8

Serial.write() can only pass a single value, so using 2 in sequence was hit or miss, so instead I created a 2 byte array, the first element is the LED Command 0x0E and the second is the value of the bitmask. Then I can pass that array to Serial.write as a single unit. Rather than manipulate the mask via bitwise operators and make the code most complex I instead stuck with the poor-mans method of simply adding or subtracting the decimal values to the mask. So to enable Caps lock, add 8 to the mask, to turn off, subtract 8. The effect of this is that you must keep the state of the LEDs in your controller, and therefore I re-initialize the LEDs on each load in setup() to a known state.

I found that on my Mac & Linux systems when Caps Lock is pressed the OS handles translation of keys for me, so I don't need to alter the scan code interpretations. However, the Keyboard Modifiers do not include a mapping for Number lock... howerver after digging I found the extended ASCII scan codes elsewhere to provide mapping. I may add Number Lock in the future, but for now it is simply fixed for simplicity.

Modifications to the original source

Ported to a PlatformIO project
uses the HID-Project a HID Library
Hardcoded to support Mac OS X Multimedia and special Keys
- You can press the "copy" key to copy a thing and the "paste" key to paste it
- Implemented are the follow Keys: Undo, Copy, Paste, Cut, Open, Help and find, The Props key works like Meta+,
Caps Lock is completely diabled and works like the control key
The Keyboard only beeps on power on

What doesn't work (yet)

Scroll Lock and Compose don't function by design; there is no practical use for them and don't see a reason to add the 10 lines of logic
Pause and Print Screen does not have any function on macos
Power Button is ignored, but could be easily Implemented
The passthrough mouse is currenlty not implemenmted and may be added in the future

Acknowledgements

Ben Rockwood for the project and his implementation
Arduino.cc
Adafruit
Alexander Kurz's awesome Keyboard Pin-outs

License

0x6e3078/SunType5_ArduinoAdapter

ErrorLooks like something went wrong!

About

Resources

License

Uh oh!

Stars

Watchers

Forks

Releases

Packages 0

Languages

Error
Looks like something went wrong!

Packages