Anyone with a trackball that has a PS/2 cord use a mouse hack?

[YT]

I have a Betson Trackball with a PS/2 cord and would like to try a mouse hack to solve my backspin problems. I was wondering if anyone has used a mouse hack with a trackball that has a PS/2 cord for output. All my searches seemed to deal with trackballs that have the original output cords not PS/2. My question is, can I cut the end of the PS/2 cord off and soder the inner cables to the mouse PCB or do I have to unplug the whole harness (from inside the trackball) and make my own harness to get the mouse hack to work?

Thanx In Advance,

YT

[leapinlew]

Maybe try the booster kit from Groovy Game Gear?

http://groovygamegear.com/webstore/index.php?main_page=product_info&cPath=74&products_id=217

[BobA]

The PS2 cord means that there is already an interface in your trackball.  You would have to bypass it to perform a mouse hack connection but it would probably work about the same as it does now with the interface.  Try a new encoder wheel as leapinlew suggested instead.

[ahofle]

Isn't backspin caused when the optics controller can't keep up with the encoder wheel data?  I would think a wheel with more holes (booster kit) would be worse.

[YT]

I did get the booster kit from GGG and it helps a little, but I still have backspin issues. Should I start from scratch (new encoders and wiring harness or new trackball) or is this can this mouse hack work?

[BobA]

I have done several mouse hacks with a Betson TB unit.  Some mice work great and some do not.  It is really a trial and error hack because you do not know how well the mouse will work until you finish it.   I have found that the simpler the mouse the better my results have been.  Get a cheap PS/2 mouse and give it a try.  You will have to bypass or disconnect your existing PS/2 controller.

http://www.members.shaw.ca/bakaye/tballhack.htm

[u_rebelscum]

Isn't backspin caused when the optics controller can't keep up with the encoder wheel data?  I would think a wheel with more holes (booster kit) would be worse.

There are many possible sources of backspin, as it's caused by whatever the biggest bootleneck may be for each hookup:

• Optical sensors (very rare actually, unless see next)
• Improper match of tooth/gap spacing and sensor spacing
• Optical PCB circuit (if any, and more likely with worn solder or components than the chip speed)
• Communication protocol (IE: serial more likely than USB, slow poll rate more likely than fast)
• Motherboard I/O buffer (most MBs are fine, but a very few just suck)
• OS and OS mouse driver (IME, fights with protocol as biggest bottleneck)
• Application (if doesn't poll enough)
• mouse speed & "enhanced precision" settings in mouse controller

While more teeth might cause the second bottleneck, and contribute to anything downstream, it probably won't have any effect at all to the back spin.