Got a tip from a very knowledgeable person, win9x enable FIFO buffers by default on COM ports that could cause input delays with mice... so I disabled the option in advanced settings and now there is no 1/3 of a sec delay in movement. Real ps2 port is still better , I think now it's just a matter of sampling.

feipoa maybe you can test this with the raritan adapter and win3x? Disable FIFO buffers and see if it works better

It's me or this actually are really easy and cheap to find?

^ that adapter works only with mice that support BOTH serial and ps2 protocols, if the mouse is a ps2-only one then this adapter is useless - same case with usb->ps2 adapters.

i'm going to order another batch of pcbs.
so i have soon a few avaible (2 months +/-)
groupbuy of parts possible.

The PCB has little Changes:
- Mouse can switched on/off via Firmware over Transistor.
- Bootloader Support for Firmware Update over Serialport. ( Firmware Update working under Win9x/XP/7/8/9/Linux ((DOS not yet working, issues with FreeBasic DOS Version and TinySafeBoot Software )
- 8Mhz SMD Crystal.

I'm interested. Could you fill me in what the PCB/parts cost is?

I can also take a couple I guess 😀

Hi,

A Kit will cost ~10 Euro + Shipping to your Country. (Origin: Germany)
MCU preprogrammed with Bootloader and Firmware.

I'm not making profit with this stuff, so everything will take a bit time to happen.
i will ask you to pay when the pcbs arrive in few weeks/1-3 months

i'm a bit short on money 😀 so ordering stuff is delayed.

Thanks

Matthias

Is it possible for someone with Eagle already installed to post the schematic as picture/pdf, thank you?

I'm also interested in a couple of units - assembled or just the PCBs + parts (I'm no stranger to soldering).

Yeah man, put me down for 3.

PCBs will soon arrive.. Please Patience.

This Adapter will not WORK with KVM Switches.

matze79 wrote:

This Adapter will not WORK with KVM Switches.

How do you know this and which KVM's have you tested? Is there a way to circumvent this issue?

i have various reports from other users, having problems getting this working togehter with Many KVM Switches.
I also tested few myself, eg. D-Link DU2 has huge latency moving Mouse cursor and behaves badly using the Adapter.

Fixing this will require writing a entire new firmware which is more dynamic, i tried modify it to get it working with my KVM, which results into other devices are not working anymore (but works for my kvm..)
i don't seem to be able to fix all this issues currently, i tried a few things but my knowledge is limited and learning is still in progress.

It works fine with many mouses and i use it daily on my 486 and 286 systems.

This is unfortunate. I was planning on using a KVM with my 3x486 and 1x386 setup, whereby the 386 only has a serial port for the mouse. Perhaps the crummy tracking quality I noticed with 4 other protocal converters is due to the KVM. I do not recall now if I tried these adapters without the KVM, however it does seem unlike me not to. I do hope you are able to find a means of circumventing this issue. Keep up the good work.

I could take a look. But is there a place to find the latest source code and schematics in non-Eagle format like PDF or picture?

If Windows detects a mouse during serial enumeration, I think it does not enable the UART FIFO. But if the mouse is not connected when Windows does serial enumeration at boot, then usually you can't use the mouse until reboot.

Obsolete

Its version with bootloader support, mouse will powered up after bootloader, so there is a small time window for firmware upgrade over rs232.
also added crystal for more stability.

Original Firmware can found at Simon Augustins Page, my files are not free of copyright infringment and nescience.
Link is above in the ZIP file (readme.txt). Its Public Domain.

You already added a fix: (not included in simons ZIP, you should apply youre right, it really could destroy a mouse, kits i send out already fixed this.)
void ps2_gohi(int pin) //gohi and golo were tested working fine.
{
pinMode(pin, INPUT);
digitalWrite(pin, HIGH);
}

i also have PCBs laying around for a while.. maybe when i have some more time i will order missing parts and then some kits will be avaible..
i use mine since over 1 year now with a Logitech M-SBF96 with no Issues.

I'm almost happy with it, i never thinked i get it this far. i'm not a electric engineer 😀

Definitely interested once a kit is out, great work as always matze79!
I am also using the old adapter with M-SBF96 mice, never had an issue.

matze79 wrote:

Its version with bootloader support, mouse will powered up after bootloader, so there is a small time window for firmware upgrade over rs232.
also added crystal for more stability.

Did you get the DOS software working? Need help with it? Or is it an issue if you can upgrade with a modern PC (and USB serial port for example)?

matze79 wrote:

You already added a fix: (not included in simons ZIP, you should apply youre right, it really could destroy a mouse, kits i send […]
Show full quote

You already added a fix: (not included in simons ZIP, you should apply youre right, it really could destroy a mouse, kits i send out already fixed this.)
void ps2_gohi(int pin) //gohi and golo were tested working fine.
{
pinMode(pin, INPUT);
digitalWrite(pin, HIGH);
}

That looks good. I don't know if it was intentional, but the clock and data wires on your schematic have no pull-up resistors, but that code does turns on the AVR built-in weak pull-ups (when direction is input, and data is high). I think some incompatibilities with some mice or KVM switches could be solved by real pull-up resistors, I think 10k is used on host side and 2k on the device side but something around there should work.

I suggest you consider also the transistor a bit. In a KVM situation that routes a VGA monitor and PS2 mouse, most likely the KVM connects the VGA ground to PS2 ground internally, so even if the transistor is turned off, both sides of it are already at ground potential, and any current flowing on PS2 cable from your adapter to KVM, the return path for the current is through VGA cable. But for a direct mouse connection, it looks it's handy to reset the mouse by turning the power off.

And with the 1k base resistor, it may or may not turn the transistor on hard enough, so it's possible that there is too much voltage drop for some mice, at least for those that consume a fair amount of current (say, over 100mA). Fortunately this is easy to measure with a multimeter, try it 😀 Some KVMs might also try to power from PS2 5V supply.

matze79 wrote:

I'm almost happy with it, i never thinked i get it this far. i'm not a electric engineer 😀

Well in that case, I think that is pretty impressive. You have many details done the way they should be done 😀

Did you get the DOS software working? Need help with it? Or is it an issue if you can upgrade with a modern PC (and USB serial port for example)?

The DOS Version is compiled by FreeBasic for DOS which has some issues with its libaries (RS232) and also long filenames (works only well on DOS 7.1 and FreeDOS)

Any modern Computer will work, and you're fine with Linux or Windows from 9x upwards.
Also a USB2Serial Converter will work.
The tinysafeboot software will do its job.

Maybe a better way is to add a Jumper for Bootloader mode and remove the Transistor, so there is no voltage drop occuring.

i will try it with some pullups on the pcb.

thanks again for your suggestions.
i always try to get better and learn more 😀

if i add resistors i will need extra transistors to pull the line down on need,
i think i will add this to my perfboard version and try it with a few "little" code changes.

As stated here: http://www.computer-engineering.org/ps2protocol/

Data = high, Clock = high: Idle state.
Data = high, Clock = low: Communication Inhibited.
Data = low, Clock = high: Host Request-to-Send