Author Topic: TMK PS/2 to USB keyboard converter  (Read 119998 times)

0 Members and 1 Guest are viewing this topic.

Offline youxiaojie

  • Posts: 31
Re: PS/2 to USB keyboard converter for Teensy with mousekeys and NKRO
« Reply #200 on: Tue, 29 January 2019, 15:05:44 »
keymaps[][MATRIX_ROWS][MATRIX_COLS] = {
   Is it a printer? And for a simplified example, int p[][3][4] means?
Or a 3D matrix?
answer: this is a 3d matrix, the first division means keyboard layers, auto defined when matrix initialized.
eg int 3dmatix[][3][4]={{{0,1,2,3},{4,5,6,7},{8,9,10,11}},{{20,21,22,23},{24,25,26,27},{28,29,30,31}}}; initialized a 3d matix, the first division is caculated here is 2,so 3d matrix[2][3][4].
and we can define a pointer int *p[3][4]=3dmatrix[0];
« Last Edit: Sun, 17 March 2019, 13:26:36 by youxiaojie »

Offline youxiaojie

  • Posts: 31
Re: PS/2 to USB keyboard converter for Teensy with mousekeys and NKRO
« Reply #201 on: Fri, 01 February 2019, 11:44:50 »
dear friend I see config.h and find:
/* matrix size */
#define MATRIX_ROWS 32  // keycode bit: 3-0
#define MATRIX_COLS 8   // keycode bit: 6-4

I feel it should be

/* matrix size */
#define MATRIX_ROWS 32  // keycode bit: 7-4
#define MATRIX_COLS 8   // keycode bit: 3-0
Am I right? Is keycode scancode?

Offline brentward

  • Posts: 8
Re: PS/2 to USB keyboard converter for Teensy with mousekeys and NKRO
« Reply #202 on: Wed, 27 March 2019, 17:07:26 »
I'm having the same issue using a Teensy 2.0 with an IBM Model M. I have mine connected in the same way and I've tried to use pull up resistors also, but it flashes when I plug it in then doesn't work.

I'm using a Mac and it shows up in System Information but sometimes it gives a message that it is using too much power so it is being shut off.

I've tried modifying the tsk_core/protocol/lufa/descriptor.c file to increase .MaxPowerConsumption in the ConfigurationDescriptor to USB_CONFIG_POWER_MA(500), but that didn't solve the issue. I've confirmed that now in System Information it recognizes that the device is requesting 500 mA.

From what I can tell 500 mA should be more than enough to power the Model M, so I'm guessing I have something wired wrong. I've even tried swapping out the Teensy with a Arduino Pro Micro that I know is working (it is currently functioning in a ABD to USB converter) and both of them behave the same.

Does anyone have any suggestions as to why it would shut off right after the lights turn on in the keyboard power up test?

Alright, I think I'm missing something or I did something wrong. I've got a Dell AT101W PS/2 board that I'm wiring up a Teensy 2.0 with the default TMK PS2-USB Converter Rev.1 firmware.

I've got Vcc connected to +5v, GND connected to ground, PD0 connected to Data, and PD1 connected to Clock.

When I connect the USB connector to it, all the LEDs light up for like half a second and then they all go off. After that the teensy shows in device manager as a keyboard, but nothing on the keyboard works.

Do I have the lines backwards or am I using the wrong firmware or something? I tried putting a 4.7k resistor on the data and clock lines connecting to Vcc but still nothing.

Any ideas would be greatly appreciated.

Offline hasu

  • Thread Starter
  • Posts: 2880
  • Location: Tokyo, Japan
  • @tmk
    • tmk keyboard firmware project
Re: TMK PS/2 to USB keyboard converter
« Reply #203 on: Wed, 27 March 2019, 18:57:16 »
I think computer(USB host) doesn't measure real current device draws, it just knows it from MaxPowerConsumption value. And resettable fuse would be used to protect USB port from accidental short circuit and overcurrent.

I suppose there are two scenarios for the problem:

1) Resettable fuse is tripped with short circuit.
2) Computer shudowns device(or just warns, perhaps) if sum of MaxPowerConsumption values(of all connected devices) exceeds power budget of USB port.
3) or other hardware/firmware errors

Decreasing MaxPowerConsumption value may mitigate the problem if it is caused from case 2.
But I guess iffy wiring is more likely and it makes accidental short circuit occasionally?
TMK products:HHKB Alt  ⌨ConvertersAlps64FC660C AltFC980C Alt

Offline brentward

  • Posts: 8
Re: TMK PS/2 to USB keyboard converter
« Reply #204 on: Thu, 28 March 2019, 10:35:32 »
Thanks for replying. I have new info about the issue.

Iíve figured out that if I plug in the converter without the PS2 port plugged into it but then plug it in after waiting more than about 3 seconds but less than about 8 seconds it works perfectly. Since it works in this way consistenty and doesnít shut off or fail Iím thinking the wiring isnít the issue.

Would there be a way to delay powering up the VCC pin for 5 seconds after the Teensy starts? I tried adding a sleep(5) in the main function in main.cpp before the keyboard init function but that didnít do the trick.

More about my configuration: it has the clock on PD1 data on PD0 both with 1k pull up resistors. The tmk build is rev2 with the only change from default being changing the MCU to atmega32u4.

Offline hasu

  • Thread Starter
  • Posts: 2880
  • Location: Tokyo, Japan
  • @tmk
    • tmk keyboard firmware project
Re: TMK PS/2 to USB keyboard converter
« Reply #205 on: Thu, 28 March 2019, 19:16:32 »
Interesting.

Did you get any dialog or something on your OS?

I'd try some to know where the issue is located in keyobard, converter and firmware.
0) Plugin the converter without keyboard and see if you still have same issue.
1) Try Soarer's firmware and see if you still have same issue with it.
2) If you have other PS/2 keyboard and check the converter itself works well.

TMK products:HHKB Alt  ⌨ConvertersAlps64FC660C AltFC980C Alt

Offline JosefM

  • Posts: 4
Re: TMK PS/2 to USB keyboard converter
« Reply #206 on: Tue, 02 April 2019, 12:38:15 »
Hi,
I'm totally new to AVR, and I'm not understanding how to build the files (I need it for a Teensy 2.0++).
I tried to install WinAVR on Windows, but building failed because the paths in the various files are in Unix format (for example the last lines in Makefile are
Code: [Select]
include $(TMK_DIR)/protocol.mk
include $(TMK_DIR)/protocol/lufa.mk
include $(TMK_DIR)/common.mk
include $(TMK_DIR)/rules.mk
)

I tried to install cross-avr-gcc7 on a SuSE Linux machine (965.7 MiB), but, when compiling, I got many errors about missing files. I eventually copied all the content of the avr\include folder from my WinAVR installation to tmk_keyboard/tmk_core/common folder downloaded from github: no file was replaced/overwritten, and the errors about missing files disappeared, but now I've the following

Code: [Select]
avr-gcc (Linux) 7.3.1 20180323 [gcc-7-branch revision 258812]
Copyright (C) 2017 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.


mkdir -p obj_ps2_usb/protocol/lufa
Compiling C: ../../tmk_core/protocol/lufa/lufa.c
avr-gcc -c -mmcu=atmega32u2 -gdwarf-2 -DF_CPU=16000000UL -DSUSPEND_MODE_STANDBY -DBOOTLOADER_SIZE=4096 -DPS2_USE_INT -DF_USB=16000000UL -DARCH=ARCH_AVR8 -DUSB_DEVICE_ONLY -DUSE_FLASH_DESCRIPTORS -DUSE_STATIC_OPTIONS="(USB_DEVICE_OPT_FULLSPEED | USB_OPT_REG_ENABLED | USB_OPT_AUTO_PLL)" -DFIXED_CONTROL_ENDPOINT_SIZE=8  -DFIXED_NUM_CONFIGURATIONS=1 -DNO_LIMITED_CONTROLLER_CONNECT -DPROTOCOL_LUFA -DEXTRAKEY_ENABLE -DCONSOLE_ENABLE -DCOMMAND_ENABLE -DNKRO_ENABLE -DVERSION=494faeb4-dirty -Os -funsigned-char -funsigned-bitfields -ffunction-s
ections -fdata-sections -fno-inline-small-functions -fpack-struct -fshort-enums -fno-strict-aliasing -Wall -Wstrict-prototypes -Wa,-adhlns=obj_ps2_usb/protocol/lufa/lufa.lst -I. -I../../tmk_core -I../../tmk_core/protocol -I../../tmk_core/protocol/lufa -I../../tmk_core/protocol/lufa/LUFA-git -I../../tmk_core/common -std=gnu99 -include config.h -MMD -MP -MF .dep/obj_ps2_usb_protocol_lufa_lufa.o.d  ../../tmk_core/protocol/lufa/lufa.c -o obj_ps2_usb/protocol/lufa/lufa.o
In file included from ../../tmk_core/protocol/lufa/LUFA-git/LUFA/Drivers/USB/../../Common/Common.h:96:0,
                 from ../../tmk_core/protocol/lufa/LUFA-git/LUFA/Drivers/USB/USB.h:382,
                 from ../../tmk_core/protocol/lufa/descriptor.h:47,
                 from ../../tmk_core/common/report.h:83,
                 from ../../tmk_core/protocol/lufa/lufa.c:39:
../../tmk_core/protocol/lufa/lufa.c: In function 'EVENT_USB_Device_Connect':
../../tmk_core/common/avr/pgmspace.h:249:46: error: variable '__c' must be const in order to be put into read-only section by means of '__attribute__((progmem))'
 # define PSTR(s) (__extension__({static char __c[] PROGMEM = (s); &__c[0];}))
                                              ^
../../tmk_core/common/print.h:41:27: note: in expansion of macro 'PSTR'
 #define print(s)    xputs(PSTR(s))
                           ^~~~
../../tmk_core/protocol/lufa/lufa.c:221:5: note: in expansion of macro 'print'
     print("[C]");
     ^~~~~
../../tmk_core/protocol/lufa/lufa.c: In function 'EVENT_USB_Device_Disconnect':
../../tmk_core/common/avr/pgmspace.h:249:46: error: variable '__c' must be const in order to be put into read-only section by means of '__attribute__((progmem))'
 # define PSTR(s) (__extension__({static char __c[] PROGMEM = (s); &__c[0];}))
                                              ^
../../tmk_core/common/print.h:41:27: note: in expansion of macro 'PSTR'
 #define print(s)    xputs(PSTR(s))
                           ^~~~
../../tmk_core/protocol/lufa/lufa.c:232:5: note: in expansion of macro 'print'
     print("[D]");
     ^~~~~
../../tmk_core/protocol/lufa/lufa.c: In function 'setup_mcu':
../../tmk_core/protocol/lufa/lufa.c:609:5: warning: implicit declaration of function 'clock_prescale_set' [-Wimplicit-function-declaration]
     clock_prescale_set(clock_div_1);
     ^~~~~~~~~~~~~~~~~~
../../tmk_core/protocol/lufa/lufa.c:609:24: error: 'clock_div_1' undeclared (first use in this function)
     clock_prescale_set(clock_div_1);
                        ^~~~~~~~~~~
../../tmk_core/protocol/lufa/lufa.c:609:24: note: each undeclared identifier is reported only once for each function it appears in
In file included from ../../tmk_core/protocol/lufa/LUFA-git/LUFA/Drivers/USB/../../Common/Common.h:96:0,
                 from ../../tmk_core/protocol/lufa/LUFA-git/LUFA/Drivers/USB/USB.h:382,
                 from ../../tmk_core/protocol/lufa/descriptor.h:47,
                 from ../../tmk_core/common/report.h:83,
                 from ../../tmk_core/protocol/lufa/lufa.c:39:
../../tmk_core/protocol/lufa/lufa.c: In function 'main':

I suspect the problem is because I copied the files from WinAVR, which seems to be 9 years old.
Could I compile the project using Atmel Studio? I'm installing it right now

EDIT: I installed Atmel Studio: I couldn't open a project (I assume it's not been developed using such IDE), but, after copying its own .h files, the project "seems" to compile without errors... it creates a folder named obj_ps2_usb, but it doesn't contain any hex files.
Unfortunately, like I said, I'm new to AVR ĶCUs: I've been using other ĶCUs (you know: the old PICs), but I've always used their IDE (on Windows), and I've always been writing my codes in Assembly, rarely using external libraries... I assume what I lack the more is a basic knowledge on how to compile a program on Unix-like machines...
« Last Edit: Tue, 02 April 2019, 13:08:29 by JosefM »

Offline hasu

  • Thread Starter
  • Posts: 2880
  • Location: Tokyo, Japan
  • @tmk
    • tmk keyboard firmware project
Re: TMK PS/2 to USB keyboard converter
« Reply #207 on: Tue, 02 April 2019, 19:18:47 »
TMK products:HHKB Alt  ⌨ConvertersAlps64FC660C AltFC980C Alt

Offline JosefM

  • Posts: 4
Re: TMK PS/2 to USB keyboard converter
« Reply #208 on: Wed, 03 April 2019, 00:16:39 »
JosefM,
See this wiki entry.
https://github.com/tmk/tmk_keyboard/wiki#build-firmware

Thank you: I had checked just the instructions on the OP of this thread. I see now that, had I followed the last link in that post, I'd have found the instructions.
I'll try it tomorrow

Offline JosefM

  • Posts: 4
Re: TMK PS/2 to USB keyboard converter: compiling for Teensy 2.0++
« Reply #209 on: Wed, 03 April 2019, 23:07:49 »
I tried the VM+Ubuntu method, but it was giving me the same errors as the SuSE machine did.
I eventually managed to compile it on SuSE (copying the aforementioned .h files from Atmel Studio installation), but only if setting
Code: [Select]
MCU ?= atmega32u2in the Makefile. Using
Code: [Select]
MCU ?= at90usb1286(the MCU on the Teensy 2.0++) it wasn't working.
I eventually modified config.h appending " || defined(__AVR_AT90USB1286__)" at the end of line 64, which now looks like
Code: [Select]
#if defined(__AVR_ATmega16U4__) || defined(__AVR_ATmega32U4__) || defined(__AVR_ATmega32U2__) || defined(__AVR_AT90USB1286__)
The lines modified in Makefile are
Code: [Select]
MCU ?= at90usb1286

BOOTLOADER_SIZE ?= 1024

CONSOLE_ENABLE ?= no # Console for debug(+400)

The second line is because of the size of the bootloader in the Teensy, while the third is to disable debugging codes, which may be used for sniffing what I type, bypassing what both the OS and the firewall do for preventing that behavior (which is why I'm not using Soarer's code, even though I bought the Teensy explicitly for that, as suggested on Deskthority.net)

After doing all of that, the program is now running on the Teensy 2.0++.
Too bad the USB keyboard protocol doesn't support many of the advanced features of this keyboard :(
I may evaluate modifying the firmware in the keyboard to send a break code every time a key is repeated, but it may cause problems with many programs.


Why so many input devices?
« Last Edit: Wed, 03 April 2019, 23:48:40 by JosefM »

Offline hasu

  • Thread Starter
  • Posts: 2880
  • Location: Tokyo, Japan
  • @tmk
    • tmk keyboard firmware project
Re: TMK PS/2 to USB keyboard converter
« Reply #210 on: Thu, 04 April 2019, 00:14:51 »
Why so many input devices?

They are used for NKRO, mouse emulation and media keys.

TMK products:HHKB Alt  ⌨ConvertersAlps64FC660C AltFC980C Alt

Offline JosefM

  • Posts: 4
Re: TMK PS/2 to USB keyboard converter
« Reply #211 on: Thu, 04 April 2019, 00:58:03 »
Why so many input devices?

They are used for NKRO, mouse emulation and media keys.

Yes, it came to my mind later: I found it back and was right gonna modify my post adding this video (go to 2'48")

Offline wsr80913

  • Posts: 2
Re: TMK PS/2 to USB keyboard converter
« Reply #212 on: Sun, 07 April 2019, 17:17:10 »
I have a model M13 keyboard, and an Alps Glidepoint keyboard.  They have two PS/2 connectors, one for the trackpoint, and one for the keyboard.  They work well with a simple glop-top active converter, but I like being able to program things/remap keys in a device-independent way.

I ran around in circles for a bit, then realized TMK supports ps/2 mice.  I built a PS2_USE_INT PS2_MOUSE_ENABLE version, and it works, although it seems to stutter a bit.

I poked about trying to get PS2_USE_USART to work, read that the useful pins are limited - PD5 is an LED on a Pro Micro, which is what I'm working on right now - and thought I'd ask:

Is USART limited to just PD5 & PD2?

is a 32u4 fast enough to convert PS/2 keyboard and mouse on the same chip?

And renaming PS2_DATA_BIT & PS2_CLOCK_BIT for the second set of pins looks like it should work.

Offline hasu

  • Thread Starter
  • Posts: 2880
  • Location: Tokyo, Japan
  • @tmk
    • tmk keyboard firmware project
Re: TMK PS/2 to USB keyboard converter
« Reply #213 on: Sun, 07 April 2019, 17:48:00 »
I have a model M13 keyboard, and an Alps Glidepoint keyboard.  They have two PS/2 connectors, one for the trackpoint, and one for the keyboard.  They work well with a simple glop-top active converter, but I like being able to program things/remap keys in a device-independent way.

I ran around in circles for a bit, then realized TMK supports ps/2 mice.  I built a PS2_USE_INT PS2_MOUSE_ENABLE version, and it works, although it seems to stutter a bit.

I poked about trying to get PS2_USE_USART to work, read that the useful pins are limited - PD5 is an LED on a Pro Micro, which is what I'm working on right now - and thought I'd ask:

Is USART limited to just PD5 & PD2?

is a 32u4 fast enough to convert PS/2 keyboard and mouse on the same chip?

And renaming PS2_DATA_BIT & PS2_CLOCK_BIT for the second set of pins looks like it should work.

Yes, pins for USART is fixed and not configurable with Atmega32u4.
I think so but current TMK firmware doesn't support PS/2 keyboard and mouse at same time basically. Problem is that you can't create two instances of PS2_USE_INT, you will have to refactor PS/2 protocol codes.

It may work with configuring like PS2_USE_INT for keyboard and PS2_USE_USART for mouse, but I'm not sure.
TMK products:HHKB Alt  ⌨ConvertersAlps64FC660C AltFC980C Alt

Offline brentward

  • Posts: 8
Re: TMK PS/2 to USB keyboard converter
« Reply #214 on: Mon, 08 April 2019, 13:14:21 »
Sorry it took so long to reply to this, I was out of town.

0) When I plug in the converter with no keyboard there is no indication that there is any issue.
1) I loaded up Soarer's firmware and the keyboard works fine on it without hot swapping
2) I have no other PS/2 keyboards to try, but the same Teensy works perfectly fine when loaded with the Soarer firmware, and also when wiring it to an ADB port and loading the TMK add_to_usb converter, so it seems like the converter hardware is fine.

I've seen Chyrosan22 on youtube indicate very similar behavior on an OmniKey ULTRA in this video:
He indicated that it was caused by a bad capacitor and when he replaced it the behavior was fixed. My multimeter doesn't have a specific setting for testing capacitors but do you think replacing the two electrolytic capacitors on the controller would be worthwhile?

I'm not very familiar with Soarer's converter; I know how to modify TMK to do what I want so I'd like to get it working. But I'm assuming I can get my custom layers in Soarer's converter working. I haven't looked at the source code yet so I don't know what it includes.

Interesting.

Did you get any dialog or something on your OS?

I'd try some to know where the issue is located in keyobard, converter and firmware.
0) Plugin the converter without keyboard and see if you still have same issue.
1) Try Soarer's firmware and see if you still have same issue with it.
2) If you have other PS/2 keyboard and check the converter itself works well.

Offline hasu

  • Thread Starter
  • Posts: 2880
  • Location: Tokyo, Japan
  • @tmk
    • tmk keyboard firmware project
Re: TMK PS/2 to USB keyboard converter
« Reply #215 on: Wed, 10 April 2019, 22:36:27 »
I think the "drawing too much power" error basically indicates there is something wrong on hardware.

From the tests your converter hardware has no problem, so I think the keyobard is root cause fo your problem.
Yes, capacitors is what you have to check at first. IBM Model M2 is infamous for its bad capacitors but I haven't heard this on Model M so far. Though, I think checking/Replacing capacitors on your keyboard is still worthwhile.
TMK products:HHKB Alt  ⌨ConvertersAlps64FC660C AltFC980C Alt

Offline brentward

  • Posts: 8
Re: TMK PS/2 to USB keyboard converter
« Reply #216 on: Thu, 11 April 2019, 17:29:27 »
I pulled the caps the other night and some new ones came today while I was at work. Tonight I'll solder the new caps into the controller. I'll let you know how it goes.

Thanks for the help!

Offline brentward

  • Posts: 8
Re: TMK PS/2 to USB keyboard converter
« Reply #217 on: Fri, 12 April 2019, 13:59:49 »
I replaced the 2 electrolytic capacitors and I'm still having issues. Interestingly, now it works when I plug it straight in (without hot swapping) sometimes, but not every time... weird.

This is making me wonder why it works fine on Soarer's firmware but has intermittent issues on the TMK firmware. I want to stick with TMK because of the ACTION_LAYER_TAP_KEY ability which it doesn't seem like Soarer's firmware supports.

Do you know enough about how Soarer's converter to think of why it would work in this case but not TMK?

Offline brentward

  • Posts: 8
Re: TMK PS/2 to USB keyboard converter
« Reply #218 on: Fri, 12 April 2019, 14:08:37 »
I just rebuilt the firmware after changing the lufa/descriptor.c to:
Code: [Select]
.MaxPowerConsumption    = USB_CONFIG_POWER_MA(250) and now it seems to be working 100% successfully.

I tested with the setting at a few different values, 125 mA, 200 mA, and 250 mA. At 125 the frequency of success on plugin it straight in was about the same as default. At 200 it seemed to work about 2 out of 3 times. At 250 I haven't had any failures so far..

My speculation is that MacOS was disabling the port when the device drew more power than it said it should be drawing. Now with the new capacitors it is drawing less power but still more than the 100 mA that the the TMK code has set as the default.

Thoughts?
« Last Edit: Fri, 12 April 2019, 14:19:57 by brentward »

Offline hasu

  • Thread Starter
  • Posts: 2880
  • Location: Tokyo, Japan
  • @tmk
    • tmk keyboard firmware project
Re: TMK PS/2 to USB keyboard converter
« Reply #219 on: Sat, 13 April 2019, 22:23:37 »
Hmm, Soarer's conveter declares 100mA in its descriptor as well. I'm not sure if it is really the cause.
https://github.com/tmk/tmk_keyboard/wiki/Soarer's-Converter-Descriptor
TMK products:HHKB Alt  ⌨ConvertersAlps64FC660C AltFC980C Alt

Offline brentward

  • Posts: 8
Re: TMK PS/2 to USB keyboard converter
« Reply #220 on: Sun, 14 April 2019, 16:12:53 »
Yeah, I guess that isn't the difference that is making Soarer's firmware working.

I've discovered that the TMK firmware with the descriptor set to 250 mA (or even 500 mA) isn't as reliable as I thought. I tried using it on my older (late 2010) MacBook Pro and on a new Raspberry Pi 3 B+ and it doesn't work on them reliably. On the older MBP it works when hot swapping but not when plugged straight in. On the Raspberry Pi it doesn't work at all.

With Soarer's firmware it works on both the older MBP and the Raspberry Pi.

Now I'm back to wondering why it works fine with Soarer's converter but not TMK. I'm hoping I can get the TMK firmware to work reliably. Could it be a difference in how they are booting up?

Would it be possible put a delay in the VCC on the controller coming on?

Offline hasu

  • Thread Starter
  • Posts: 2880
  • Location: Tokyo, Japan
  • @tmk
    • tmk keyboard firmware project
Re: TMK PS/2 to USB keyboard converter
« Reply #221 on: Mon, 15 April 2019, 04:10:02 »
On the older MBP did you get error message or something?
Raspberry Pi says something in log file when the converter fails?

You can get debug info with hid_listen tool on both Soarer's and TMK. You may find some clue there.
https://www.pjrc.com/teensy/hid_listen.html

I guess keyboard initialization timing/method or something may cause the difference.

No you can't controll VCC line from firmware.

And what is your keyboard model exactly?
TMK products:HHKB Alt  ⌨ConvertersAlps64FC660C AltFC980C Alt

Offline _GMK_

  • not affiliated with GMK
  • Posts: 197
Re: TMK PS/2 to USB keyboard converter
« Reply #222 on: Mon, 15 April 2019, 06:13:44 »
Works perfectly with cherry g80-8000. Thanks for designing this  :thumb:
Maybe I'll buy one for home too. Any hardware update planned?

Offline brentward

  • Posts: 8
Re: TMK PS/2 to USB keyboard converter
« Reply #223 on: Mon, 15 April 2019, 14:30:14 »
There was no message from the MBP when it fails. Initially I was getting messages that the USB port was turned off because the device was using too much power but I haven't got that message in a while.

I'll take a look at the logs on the Raspberry Pi and I'll also look at the debug for both versions when I get hime and I'll update this thread.

The keyboard is a 1397735 manufactured on 12 Aug 1994. It is a version that has a thick coiled detachable SDL to PS/2 cable. The controller looks like this one:
https://clickykeyboards.com/product/model-m-internal-keyboard-controller-logic-board-with-sdl-port/