Inverted Electric-ice trackball y axis?

[clnilsen]

Well, I'm FINALLY closing in on getting my cp done after about 2 years of this project. 

Anyway, I have an electric-ice trackball installed, and one issue I have is in plain windows XP (haven't even gotten to Mame) is that the Y axis seems to be inverted!?!?

At first I thought I had the trackball rotated 90, but there is no direction that I could orient the trackball to get it to roll up = mouse up on screen and roll right = mouse right on screen. I don't believe it's simple as switching board locations.

I don't mind too much if I have to attack this with a soldering iron - although I suspect that is a solution - but for what I paid on these I hope not! I was also thinking that it may be possible to change the settings in XP (I couldn't find the place though), but I don't want to bugger up any other mice I may connect. I do connect to my arcade machine via Remote Desktop/vnc so I don't want to have to invert my mouse in that situation.

Could there be a jumper on the bottom I can change? Anyone else have this issue or ideas?

For reference, on the y axis the molex plug is wired:

Top
------Blue-> Board
------Red-> Board
------Black-> Board
------Brown-> Board
Bottom

[RandyT]

I don't know how this one got by me.  I'm usually pretty thorough when testing these.

The manufacturer of the trackball apparently played a nasty trick on us and screwed up the wiring on the molex.  Luckily, there is a simple fix.

Pull the molex connector off of the Y Axis board and carefully remove the blue and brown connections by putting a little pressure on the spring loaded barbs that lock them in place and pulling gently.  Then just swap those two wires around to where they are supposed to be and everything will be fine.

If you have any other issues, especially of this type, please drop an email.  It's usually much quicker than waiting for an answer in the forums.

RandyT

[clnilsen]

Great news!

I was hoping I wasn't going crazy. I'll definitely try that tonight!

[clnilsen]

Update:

This fixed the problem! Woot!