Help with Optiwiz - Using TB twist 2 and trackball

[UncleMame]

Had unplugged my CP to change a button (unplugged the GP Wiz40, Track ball(connected to optiwiz) and the TB twist(connected to another small PCB).  When I replugged everything back in, the TB works, but only on the Y-axis, TB twist works on the x axis.  I have a feeling it is software related.  I removed all the devices and reinstalled them without any solution to it.  I dont see anywhere in the config to set or test the different axes.

Any help would be great.  BTW all connectors are properly connected/powered.

If this is software related, it makes me wonder why things would be so tempermental.

I really hadn't intended to need to use centipede as a trackball + spinner.......LOL

[RandyT]

Had unplugged my CP to change a button (unplugged the GP Wiz40, Track ball(connected to optiwiz) and the TB twist(connected to another small PCB).  When I replugged everything back in, the TB works, but only on the Y-axis, TB twist works on the x axis.  I have a feeling it is software related.  I removed all the devices and reinstalled them without any solution to it.  I dont see anywhere in the config to set or test the different axes.

Is this behavior observed at the desktop, or only within the software?    If only in the software, it's a configuration issue in that software.

[UncleMame]

This is within both for the windows desktop and any application that it uses(Mame, etc).  The interesting thing is that the TB will work in the Y Axis(but not the X axis)- Moves the mouse pointer in the Y axis only, while the Turbotwist 2 will move the pointer in the X direction.  I was wondering if maybe the way the USB mouse drivers assigned things, that the turbotwist is somehow "overriding" the trackball ?

It's odd - I just don't get it.  The only thing that was done was to unplug the USB connector to the optiwiz (all other connectors to the TB were kept as is), The same was done for the small PCB to the Turbotwist 2 and the GP wiz.  The latter two work fine on reconnecting, just the Optiwiz/Trackball don't. 

I need advice as how to troubleshoot this, as the components are no more than 5-6 weeks old.

Thanks

[RandyT]

Sounds like something may have taken a static hit when you were disconnecting / re-connecting things.   You can swap the axis cables on the Opti-Wiz, and see if the problem moves to the Y axis.  If it does, then the problem isn't with the Opti-Wiz.  Next, connect the wires to the Opti-Wiz the way they were originally, then swap the cables on the trackball's optical boards.  If moving the ball left and right causes the cursor to move up and down, but moving the ball up and down does nothing, then its a wiring problem.  If moving the ball left and right does nothing, but moving the ball up and down moves the cursor left and right, then one of the optical PCB's probably took a static discharge or power surge of some nature.

[UncleMame]

Update: I uninstalled and re-installed the drivers again and did a reboot, and the trackball works initially in windows in both axes, but upon entering the frontend/MAME it does it's fluky thing again - Interestingly enough when I exit the front end, the track ball is then is stuck in the Y-position, which is odd to me as I would assume windows would have the ultimate say as to how the mouse would work.  It apppears to me that the Optiwiz some how is "influenced" otherwise.

It seems to me that something is not compatable with the Opti-Wiz/software config issue and will need to tinker around with this more, or perhaps switch to an Optipac.

In regards to the static hit - I have built systems for 25 years and have always ensured that I'm discharged prior to touching any electronics and PCBs are housed within static resistant casings(as is the case on my machine).  The machine has a surge protector connected that is rated well above the necessary needs and the machine suffered no surge.  This appears to be a software incompatability/software configuration issue with the Optiwiz.

[RandyT]

This appears to be a software incompatability/software configuration issue with the Optiwiz.

There are a huge number of Opti-Wiz's being used out there, with no other similar reports of this type of issue.  It would not be any more "incompatible" than a standard USB HID mouse.  The only way this is possible, would be an application which "hooks" the Windows I/O stream, and discards an axis for some inexplicable reason.  The software cannot just "shut off" an axis on a hardware device which is not specifically designed to allow that type of functionality.  And if it does it to the Opti-Wiz, the same would happen on any other mouse / mouse device.  The Opti-Wiz is still sending the information (it has no choice but to) but something in some underlying software is ignoring it.

Are you using a piece of software to hook the GP-Wiz (and possibly the Mouse) to provide keystrokes, which is launched when you start your front-end, but which is not shut down when you exit?  This sounds like a possibility based on your description.

In regards to the static hit - I have built systems for 25 years...

You stated that the disconnection / handling of the device triggered the issue.  I can only offer advice based on the information given

What front-end? OS Version? I don't have any support requests from you in email.  That would probably be a good place to start.

RandyT

[UncleMame]

It's windows 7 running Mala.  And I actually did send you an email on 5/27(you might want to make sure your server received it).

No worries - I'm going to keep on tinkering with it, if I can't figure it out - I'll move to an OptiPac - I was thinking of switching out to an IPAC anyway, so I'll just get an Optipac when I order it.

Thanks anyway, though.

[RandyT]

It's windows 7 running Mala.  And I actually did send you an email on 5/27(you might want to make sure your server received it).

All support requests on that day were answered, and none were received matching this issue.  You might want to try sending it again.  You should really try to solve your software problem.  There's a high probability it will persist, even with a different interface.

I see you are using JoytoKey, which can be mapped to perform mouse functions.  Try exiting the software and/or check the configuration for hooks on the mouse device.  I'm guessing a configuration issue, or the software itself, is doing to the system what I described above.

[UncleMame]

I'm not trying to start a p*ssing contest, but feel free to look again - Here's my original Email pasted here.  It was sent later in the day, so it may be sitting in your inbox.  Again, no worries.

Randy
 
My trackball suddenly seemed to stop working for the x axis - The wheels themselves seem to be spinning and the optiwiz is correctly installed and connected properly.  I have a feeling there may be either a software issue or perhaps a connector problem.  The y-axis works fine, but just not the x-axis.  I uninstalled the driver and reinstalled it, with no change....I'm baffled.  Even when using the trackball in windows, it does not recognize the x-axis.
 
Any advice ?

Although I am usually up for a challenge I saw a thread with a similar problem from UncleT in the forum where he ran through lots of checks only to find out the pcb boards neded to be changed ("HELP: Trackball w/Optiwiz USB interface results in left/right not working")  I would certainly hope the TB PCBs didn't go bad this early.

I just don't have that much free time to fool around with it and am willing to risk $40 on the Optipac and be able to attach both my spinner and my trackball to one board, eliminating the need for another usb connection to the computer. (I originally thought you could do that with the Optiwiz, but found out otherwise).  Just my personal preference.

[RandyT]

Here's my original Email pasted here.  It was sent later in the day, so it may be sitting in your inbox.  Again, no worries.

Like I stated, never arrived.  Looked in all of my folders.  Ironically, I did receive questions yesterday concerning issues with competitors products, and the individual wanted to know if purchasing an Opti-Wiz would solve his issues .  Similar to you, his solution was in setting up his software correctly.

I just don't have that much free time to fool around with it and am willing to risk $40...

Ok, but I think you will find the answer to your issue in my last post.  The rule of thumb with any hardware of this nature is "if it works at the desktop, before you start loading software, it works."  Anything beyond that will be software / configuration issues.

RandyT

[UncleMame]

Well after fooling around with it some more, it seems that I have been able to isolate the problem a little better. 

Test 1: Connecting the purple/blue(technically the y axis connector) to the optiwiz on the x axis and y axis work fine. So I would assume that the optiwiz is sending out the correct signals for both x-axis and y-axis.

Test 2: Connecting the yellow/green connector to the optiwiz works neither on the x axis or y axis of the board.  This would lead me to believe there is either a problem with the power connector from the optiwiz to the PCB on the trackball or the PCB on the trackball itself.

Of note, On initial startup in windows, the trackball did work properly on two occasions(maybe it was in its death throws.... )  It's really odd (similar to uncleT's dilemma).

What do you suggest now Randy ?

[RandyT]

Well after fooling around with it some more, it seems that I have been able to isolate the problem a little better.  

This is why I suggest taking these things to email.  Looks like we are at a different juncture now, and all of the stuff prior will probably just be confusing to others looking for similar help.

Test 1: Connecting the purple/blue(technically the y axis connector) to the optiwiz on the x axis and y axis work fine. So I would assume that the optiwiz is sending out the correct signals for both x-axis and y-axis.

That would be correct.

Test 2: Connecting the yellow/green connector to the optiwiz works neither on the x axis or y axis of the board.  This would lead me to believe there is either a problem with the power connector from the optiwiz to the PCB on the trackball or the PCB on the trackball itself.

As I suggested in the second post of this thread, you now need to swap (with the power off) the purple and blue cable at the TB PCB, with the Yellow and Green.  If the Yellow and Green cable works, then the issue lies with the trackball PCB.  These trackballs use the same optical circuit as the HAPP trackballs, and I have seen it mentioned that pulling the power to these PCBs directly is not good for them.  Again, the reason for my "surge" comment earlier.

Of note, On initial startup in windows, the trackball did work properly on two occasions(maybe it was in its death throws.... )  It's really odd (similar to uncleT's dilemma).

What do you suggest now Randy ?

I suggest you email me .  The reason the situation sounds similar is because UncleT's trackball was from HAPP, and uses the same red board circuit. The circuit on these boards is rumored to be very performance oriented, but because it is more complex, it is more sensitive.

RandyT

[UncleMame]

I'll shoot you an email once I get a chance to fool with it some more.

The really baffling thing is this though: If the PCB board is shot(which I think is the likely case) - Why would it intermittently work?(every so often in windows, I would scroll the TB in the x-axis and it would run for a bit and then stop working)  I would figure if a board is shot, it is shot, no in-between.  But then again, UncleT had the same thing happen.  I'm certainly no expert on PCB design, so who knows.....

I didn't realize the TB3 is essentially running as a Happ(PCB wise).  It's just a shame to know the Happ PCBs are so fragile (I've been far more gentle with my CP PCBs than with any PCBs I've mounted to mainboards/slots) - kind of funny how a cabinet gets extra special care  .  

Just as a side note, the USB connectors were disconnected at the computer not directly at the PCB board(I don't know if this makes much difference in regards to your prior reference about the disconnect).