Need Help 4p4c to usb G10 1080

[Trypsta]

Hello all,

I came across an old keyboard that a friend of mine was planning to convert from a 4p4c connector to USB but was never able to get around to it.

I do have a few questions I hope to get answered. I am very new to the world of electronics so I have provided an image of my thought process.
Please let me know if I am wrong. The image is also suggesting that I already flashed the required software to the Teensy and that it is what I think the end configuration would look like. (see end of post)

Keyboard Model: G10 1080
Cherry Branded
G80-1080 HAU /13

Questions
How do I know which wire is which? I do have a multi meter and I was able to trace 2 points back but I don't see any labels of what those points are on the board.
The 4 wires from the keyboard pcb should connect to the Teensy.. then mini usb from the teensy connects to the PC. At that point the keyboard should be functional given that the appropriate firmware is loaded. Is this correct?

Please let me know if I need to provide additional info.

[nevin]

Need a little more info. What brand is the keyboard labeled under. I see the cherry on the circuit board and the model formatting match up to typical cherry but i'm not seeing a g10-1080. I found a g80-1080.

Depending on what the board is will determine how you convert it. There's many boards that use that connector and a bunch of different protocols as well.

Take a look at some of soarers work

Soarer's wyse converter
https://geekhack.org/index.php?topic=52597.0

Another thread
https://geekhack.org/index.php?topic=17458.msg1164429#msg1164429

- find out what brand & verify model #
- find out what protocol it's running
- then you can figure out what conversion options are available.


Sent from my SM-G900V using Tapatalk

[Trypsta]

Thanks for the quick response.

Cherry Branded
G80-1080 HAU /13

The keyboard in the second thread looks identical to the one I have.
Reading through the post a member suggested to find which wires connect to power/ground and to find those on smaller logic chips, Pins 14 and 7.  The image is broken so I'm not sure what he is referring to?

I did use a multi meter and found that the bottom two wires on the keyboard (circled top right back side of pcb) is connected to the + - circled on the left.
(going off memory as the keyboard is at my workplace). Is the method I am using correct? Just want to know if I am on the right path.
 
I have done some soldering before but in my past experiences there would be labels such as VCC,GND, TX, RX etc. In this case I don't see any of those labels but this is the first keyboard I have attempted to work on. 

 

[SixtyLife]

some of my g80-1813 dolch boards have 4p4c connectors at the end but speak PS/2.

something like this might be worth trying if you want to be less invasive:
http://imgur.com/a/oqUEG

[Tactile]

The pinout of the voltage regulator should be of help to you. You should be able to trace ground and 5V from there.

[Trypsta]

Thanks for the clarification.

Ground - Green Wire
Power - White Wire

So i think the next step is connecting the four wires to the teensy.
White wire will be soldered to VCC
Green wire to the GND
which pin does the blue and red wire need to be connected to? One of the threads linked stated PD0 PD1 but I don't see that on the teensy board.
Is it PINS 7 and 8 RX TX?

Once I do get the two wires connected.. I should be able to connect to the computer with USB and run the logic analyzer to figure out which format the data is in correct?

[Tactile]

PD0 stands for [P]ort D0. The "Port" is just assumed 'cause you are always connecting to a port so, on the board, the "P" is just left off.

Translation: if someone tells you to connect to "PD0" (meaning [P]ort D0) look for a label of "D0" on the board.

[Trypsta]

Alright so I finally got the soldering all done but the minute I plug it into my computer via usb I hear a constant beep sound (maybe a short somewhere?).
It does recognize in device manager as Soarer's keyboard so I know the teensy is good but the keyboard is not functional (with exception of beep sound).
I also tried swapping the data and clock wires on the teensy from D0 to D1 and vice versa and still had the same results.

Any ideas what the problem could be or what my next steps should be?

 

[Tactile]

Have look at this post.

[Trypsta]

Alright so this is what I got. Since i did get some info back should mean my wiring is correct right? Is it just the wrong firmware flashed onto the teensy?

Waiting for device:
Listening:

Device disconnected.
Waiting for new device:...
Listening:
wEE

remaining: FFFC


Keyboard ID: 0000
Code Set: 1
Mode: PC/XT

R05

[invariance]

What firmware did you load onto the teensy?


Sent from my iPhone using Tapatalk

[Trypsta]

The firmware uploaded is
Soarer_at2usb_v1.12_atmega32U4

Do I need to buy a converter or something along with the teensy?
I'm a bit confused how this works.  According to HID listen this keyboard (seen below) is communicating using XT. Is the Teensy converting XT to USB or do I have to buy an XT to USB converter as well?

 
Waiting for device:
Listening:

Device disconnected.
Waiting for new device:...
Listening:
wEE

remaining: FFFC


Keyboard ID: 0000
Code Set: 1
Mode: PC/XT

[Trypsta]

Okay just an update..
So.. I either toasted my keyboard or i need to redo my connections.
Any thoughts?

Troubleshooting steps:
**Plugged Keyboard in with HID_LISTEN running. Would hear a continuous single beep no response.
Waiting for device:.........
Listening:
wEE

remaining: FFFC

Keyboard ID: 0000
Code Set: 1
Mode: PC/XT

R05

**Swapped Ground and 5V momentarily plugged in
Got the same response as previously.

**Flipped Ground and 5V back to what it originally was. Now I don't hear a continuous beep but when I press the keys I get R06.
No lights are on capslock or numlock. But teensy does light up each time i hit a key.

Keyboard ID: 0000
Code Set: 1
Mode: PC/XT


R06 R06 R06
R06 R06 R06
R06 R06 R06 R06 R06 R06
R06 R06 R06 R06 R06 R06
R06 R06 R06
R06 R06 R06
R06 R06 R06
R06 R06 R06
R06 R06 R06 R06 R06 R06 R06 R06 R06 R06 R06 R06 R06 R06 R06 R06 R06 R06 R06 R06 R06 R06 R06 R06 R06 R06 R06 R06 R06 R06 R06 R06 R06
R06 R06 R06
R06 R06 R06 R06 R06 R06 R06 R06
R06 R06 R06 R06 R06 R06 R06 R06 R06
R06 R06 R06 R06 R06 R06 R06 R06 R06 R06 R06 R06

**Unplugged the USB and replugged
Now I don't hear the continuous beep but I'm not getting any responses either no R06 or R05.
but the caps lock key and numlock key is lit up.

[invariance]

I don't know if this will help but....
From here

R04 is a clock error - the converter has missed one edge of the clock signal, usually because of a short spike. I haven't seen this one other than when powering up, so I'm not sure why it's happening here.
R05 is a timeout error - the converter started receiving clock from the board, but didn't receive enough for a full code.
R06, the start bit error - the converter read a start bit, but it was incorrect. (Data should be high for XT, low for the rest).

...and someone else had the same model and Soarer wondered if it used a similar (or even the same) protocol as the Wyse 1316.  There was no indication if this was determined but that would be worth a shot to load on Soarer's Wyse Converter and see if it works.


When I was looking for the post I happened to go back a page and came across Hellmark's woes with a different board, but might be worth a read too.