JoeHill11 / xbox360wirelesschatpad

Automatically exported from code.google.com/p/xbox360wirelesschatpad
0 stars 0 forks source link

ERROR: Controller 1 Connection Timeout. Try Again. #18

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Run Chatpad app after running steps to install necessary software.

What version of the product are you using? On what operating system?

Revision 20, Windows 7

I also cannot calibrate the vJoy joystick in the control panel applet.

Just wondering what things to try to get this working.

Original issue reported on code.google.com by teleng...@gmail.com on 25 Nov 2013 at 12:28

GoogleCodeExporter commented 9 years ago
I followed the instructions to the letter.  I'm not ruling out I did something 
wrong though.  Anything I can look at, debug logs, etc?

Original comment by teleng...@gmail.com on 25 Nov 2013 at 12:29

GoogleCodeExporter commented 9 years ago
I did manage to get it working.  Some combination of sync'ing up the receiver 
and gamepad and then running the app got it working.  

I primarily will be running this on a settop box to replace the cideko (which 
I've gone through two of, they are great, but durability is horrible, and they 
are $100 a pop).

Is there a command line arg to automatically connect without having to press 
the connect button?  Launching the app and keeping it running is no issue, but 
I have no means to press the button.  

Also, it seems you have to hit the Guide button to connect also, I have an xbox 
360 so that will probably be turning on, I'll have to unplug that when using 
the settop.

Nice work on the driver, I've been waiting for someone to do this for a very 
long time.  Is there a way to send you donations?

Original comment by teleng...@gmail.com on 25 Nov 2013 at 1:40

GoogleCodeExporter commented 9 years ago
I'm glad to hear you've gotten everything working.

I'm looking into an auto-connect option, but for now you can use the following 
workaround.

1. Launch the application and connect as normal.
2. Leave the application running and disconnect the controller when necessary 
by removing the battery pack.
3. Upon pressing the GUIDE button on the controller, everything should 
reconnect.

I've been using this method for the last few months with great results.

Original comment by ksbarnes@skyag.net on 23 Dec 2013 at 9:08

GoogleCodeExporter commented 9 years ago
Hi there!

I ended up modifying the app to do the auto connect (and spin waiting) via
a command line flag.  I've also made some other changes for use w/ my
settop box (function keys) and also am using the inputmanager dll which
I've modified to correctly send scan codes.  A particular emulator I use
(VICE) needs to have scan codes.

Thanks so much for this work, I'm glad to be able to use a NICE gamepad w/
my setup and have the ability to type when necessary.

Original comment by teleng...@gmail.com on 2 Jan 2014 at 7:05