Build Your Own Arcade Controls Forum
Main => Main Forum => Topic started by: equlizer on October 17, 2011, 10:31:53 pm
-
WTF?? This just started happening a few days ago. I havnt done anything differently (that i know of) and im not running xpadder or anything. When i press button 9, its gone and winxp thinks its disconnected. Im using the 2 player Xin-mo dual arcade controller and its happening on the player 1 side.
EDIT: Bypassed the problem by wiring up button 10 to it instead, but im still wondering what caused that :banghead:
-
I might not be much help but....
is this happening when youre in a frontend or game ... or just in windows itself?
I guess just test it in each senario..start with windows..perhaps open a text document and press away...if it doesnt happen there...then move open up your front end...try there...then go back to notepad and see if you can type...then a game...and repeat.
either
1) bad encoder
2) some program causing your problems (bad .ini file??)
3) try loading default map to your encoder(if you can)..then start over...
-
Its a windows/computer thing. Going into test controllers and pressing that button I hear the "dun dun" sound which disconnects the xin-mo. If i hold it down, it stays "unplugged" Pressing that button at anytime, just unplugs/plugs in the xin-mo.
Every other wire/button on the xin-mo works great when plugged in, its just that 1 button on the player 1 side :angry:
-
anyone? :dunno
-
I've never used this product, but if a simulated button press is disconnecting your USB device, this could very well be due to a ground short. Double check your wiring for any nicks or inadvertant touching. Also possible this problem is on your encoder board (check the traces).
-Evan
-
WTF?? This just started happening a few days ago. I havnt done anything differently (that i know of) and im not running xpadder or anything. When i press button 9, its gone and winxp thinks its disconnected. Im using the 2 player Xin-mo dual arcade controller and its happening on the player 1 side.
I'm guessing this was not purchased from us, as I haven't seen any emails from you about the issue. If it was, you should contact me and I'm sure I can fix the issue for you.
These are an inexpensive interface and tend to have poor QC coming from the factory. Based on my experience with them, it's possible that a couple of the pins on the CPU have a solder blob connecting them. As the input lines are held high and then grounded to indicate a button press, if input 10's pin on the CPU is right next to a power pin, then grounding the input will also short out the power to the controller, and cause what you are seeing. A little flux and touch with a hot soldering iron will usually separate them. I've had to fix 2 of these units for solder issues so far before shipping them, as they had bad solder joints on the power and wouldn't even show up when plugged in. Needless to say, we plug in every one of them before shipping now, to make sure our customers don't end up with a DOA.
RandyT
-
will give that a try today! The strange thing is that it worked up until last week :dizzy:
-
will give that a try today! The strange thing is that it worked up until last week :dizzy:
If that's the case, then follow the earlier advice and check your wiring very carefully. Also make sure that there is nothing conductive under the PCB where you have it mounted. But still check the CPU on the board. Something conductive (piece of wire, metal shaving, etc...) could have fallen onto it and be shorting something.
It is possible too that the CPU itself could have developed an internal short between the input and the power, as these are usually tied to power through a weak pull-up resistor. If that resistor shorted internally, it could pull the power down enough to trigger a reset. But usually these will burn open instead, so it seems unlikely.
RandyT
-
I know this is an old topic..
But did you ever figure out this issue? I'm having the same problem with button 9 disconnecting the xin mo..
-
Mine did that before. Used a different wire for that button and all was fine. So it's a bad ground, wire, or loose connection.
-
i tried a new ground wire, new ground terminal on the xin mo, new button wire, new button...
it has to be a short on the pcb itself....
it's going back for replacement.