#PLUG KEYBOARD INTO LAPTOP DRIVER#
#PLUG KEYBOARD INTO LAPTOP CODE#
#PLUG KEYBOARD INTO LAPTOP PC#

There are two very different types of converters you might be dealing with in this situation.

Have some PS/2 to USB converters, and I know they are very 'moody', often only working with keyboards they were shipped with, and sometimes not even that. The upshot of this is that it isn't trivial. But I don't know of any 'How To' guide for this.

#PLUG KEYBOARD INTO LAPTOP PC#

I have heard of people trying to achieve this feat by putting a Raspberry Pi or Arduino between the keyboard and PC as a protocol converter.

#PLUG KEYBOARD INTO LAPTOP CODE#

The byte sent represents the scan code of the pressed key or a response to a command.ДЇ5 Restore default settings and wait for enable The baud rate is roughly 2000 bits per second. The data format is 1 start bit, followed by 8 data bits. When the keyboard has a byte to send to the computer (a keystroke), it shifts 9 bits out to the data line (RxD) with nine clock pulses on the CLK line. The protocol is summarised as (taken from this description): You may be able to then redirect COM1 to STDIN.

#PLUG KEYBOARD INTO LAPTOP DRIVER#

You then write a keyboard driver for your new PC that converts the data stream from the old keyboard. The keyboard will then appear to the PC as being on a standard COM port. I would suggest: Use a USB-RS232 adaptor and wire the DIN plug to a DB25 or DB9 RS232. The IBM DIN and PS/2 sockets have pins as below:ДЈ: Reserved (in practice, usually a reset line) Also, the protocol chip may be in the PS/2 plug!ДЄlthough the pinouts are not too bad. Writing a USB driver on your new PC to bypass the USB protocol is probably impossible as the USB ports are likely to be driven by a dedicated chip.Д¬utting the PS/2 connector off your USB-PS/2 adaptor and soldering the wires directly to the DIN plug - in the hope that the voltage loss is reduced and so the flakiness you describe goes away is very risky. PS/2 to USB converters, and other USB converters, usually have a small embedded processor that handles the protocol. A USB keyboard will respond, the XT keyboard will not. The host computer will interrogate a USB device using a Setup Token Packet. There is a defined USB protocol to which peripherals such as keyboards must comply. Your core problem will lie in the communications protocols. I suspect with adaptor upon adaptor you are either losing voltage and therefore connectivity or the protocol is getting confused.

The cable for the physical connection and the driver for the communications protocol. that you haven't connected + from the miniDIN to a - on the DIN) One last thing If you're going to make an adapter yourself, you should not connect the same colored cables from the DIN cable to the same colored cables from the miniDIN cable Always verify what cables you're connecting to what pins and double check if the polarization is OK (ie. The second adapter should be a passive one You can either make one yourself ( working schematic on the last picture) or buy one like the picture below online. If you have one lying around, you can always try it - your PC will be fine even if the keyboard won't work with this one. The first one should be a USB to PS/2 (miniDIN) adapter This one needs to be an active adapter, such as this one:ДЄvoid using weird smaller adapters like the one below - they probably won't work because they're designed for motherboards that have a PS/2 host, which allows them to be passive (motherboard will be in charge of changing D+ and D- from the USB port to Clock and Data signal from PS/2). The easiest (PnP) approach is definely using two adapters.

Plug keyboard into laptop