search

JoeHill11 / xbox360wirelesschatpad

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

Chatpad lights up, doesn't respond to input #2

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
This happens on Win7 64-bit:
Installed everything according to the instructions.
The gamepad works fine for the most part, but the chatpad does nothing except 
light up.

If there's any additional information I can provide to solve this, please let 
me know.

Original issue reported on code.google.com by revolver...@gmail.com on 5 Jul 2013 at 6:09

GoogleCodeExporter commented 9 years ago 
Having the same issue under Win8 64-Bit.
GamePad Works Fine. Chatpad just lights up when keys pressed.

Ryan's drive the Chatpad works fine, but GamePad input has many issues.

Original comment by byte...@geekonym.com on 5 Jul 2013 at 2:55

GoogleCodeExporter commented 9 years ago 
Repeated from Issue #1 by Yamishi

"Got everything installed, neat and tidy, but the chatpad still won't really 
work. I got it to type a lower-case r, by pressing the button repeatedly, but 
it won't recognize any more button presses. So I know that it is, at least, 
getting the signal, but it won't catch the keypresses (other than that one)."

Original comment by ksbarnes@skyag.net on 5 Jul 2013 at 5:41

GoogleCodeExporter commented 9 years ago 
Having problems reproducing this on either my Windows XP 32bit or Windows 7 
64bit machines, so this may be a bit of an ordeal to debug and fix...but I'm up 
to the challenge if ya'll are.

Please try downloading the latest Issue Debug Build with the following link:
https://xbox360wirelesschatpad.googlecode.com/svn/trunk/Issue%20Debugging%20Buil
d.exe

Place that file into the same directory where you extracted the application ZIP 
file and try using it instead of the original application exe.

The only thing I can think of right now is that some key data is being ignored 
for optimization purposes. That build has a couple of optimizations disabled, 
but no redundant data is being thrown away.

Please report back if the problem is fixed, or if there is any additional 
information you have. Also, note if the application window shows any ERRORs or 
WARNINGs.

Original comment by ksbarnes@skyag.net on 5 Jul 2013 at 6:50

GoogleCodeExporter commented 9 years ago 
Same problem happens with the debugging build.

Not sure if it's related, but occasionally when closing both versions of the 
program it hangs for a little bit and I get a "WindowsFormsApplication1 has 
stopped working" error. Here are the error details:

Problem signature:
  Problem Event Name:   CLR20r3
  Problem Signature 01: issue debugging build.exe
  Problem Signature 02: 1.0.0.0
  Problem Signature 03: 51d711c1
  Problem Signature 04: mscorlib
  Problem Signature 05: 4.0.30319.18047
  Problem Signature 06: 51552f0a
  Problem Signature 07: 1364
  Problem Signature 08: 13
  Problem Signature 09: System.ObjectDisposedException
  OS Version:   6.1.7601.2.1.0.256.1
  Locale ID:    4105
  Additional Information 1: 0a9e
  Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
  Additional Information 3: 0a9e
  Additional Information 4: 0a9e372d3b4ad19135b953a78882e789

Original comment by revolver...@gmail.com on 5 Jul 2013 at 8:20

GoogleCodeExporter commented 9 years ago 
Hmm, not sure why the application error is happening; it could be related.

I think we're going to have to be a little more archaic in figuring this one 
out. I've updated the issue debug build to output raw chatpad data. Please 
download it and follow the instructions below:

https://xbox360wirelesschatpad.googlecode.com/svn/trunk/Issue%20Debugging%20Buil
d.exe

1. Connect your controller like normal.
2. At this point, you should start seeing a bunch of "Chatpad Data:" messages, 
note a reply if you don't
3. Once the messages are flowing, Select the chatpad test area and press the 
following sequence of keys on the chatpad: "1 2 3 4 5"
4. After you've entered the sequence, manually remove the battery from your 
xbox 360 controller, this should cause a disconnect message.
5. Copy the entire log window into a new file and attach it in your reply.

Original comment by ksbarnes@skyag.net on 5 Jul 2013 at 9:35

GoogleCodeExporter commented 9 years ago 
Here's the log file

Original comment by revolver...@gmail.com on 5 Jul 2013 at 9:45

Attachments:

GoogleCodeExporter commented 9 years ago 
So the data is not where I'm expecting it to be, though the status data is 
there.

A few questions...

1. Are you using official Xbox 360 Receiver, Controller, and Chatpad?
2. Does the chat work on an Xbox 360? (If you have one available)

Also another round of data gathering, download the latest Issue Debugging Build 
and follow below instructions, note that the directions are slightly different:

https://xbox360wirelesschatpad.googlecode.com/svn/trunk/Issue%20Debugging%20Buil
d.exe

1. Connect your controller like normal.
2. Select the Chatpad Test area and enter the sequence "1 2 3 4 5".
3. Close the application.
4. Attach "debugLog.txt" to your reply, it should be located in the same 
directory as the executable.

Original comment by ksbarnes@skyag.net on 5 Jul 2013 at 10:16

GoogleCodeExporter commented 9 years ago 
1: Yes, everything is official
2: I don't have a 360, but this chatpad did of work with Ryan B's chatpad 
driver if that helps.

Original comment by revolver...@gmail.com on 5 Jul 2013 at 10:23

Attachments:

GoogleCodeExporter commented 9 years ago 
Ok, data is still not where I'd like it to be; it's very interesting. I've 
updated the debug build again to pull a slightly different log. If Ryan's build 
works, this should at least find the data. Same instructions, duplicated below. 
Also, if you up to something a little more live, feel free to join me in IRC 
chat http://webchat.freenode.net at Channel #skyagchannel.

Download the latest Issue Debugging Build and follow below instructions, note 
that the directions are slightly different:

https://xbox360wirelesschatpad.googlecode.com/svn/trunk/Issue%20Debugging%20Buil
d.exe

1. Connect your controller like normal.
2. Select the Chatpad Test area and enter the sequence "1 2 3 4 5".
3. Close the application.
4. Attach "debugLog.txt" to your reply, it should be located in the same 
directory as the executable.

Original comment by ksbarnes@skyag.net on 5 Jul 2013 at 10:44

GoogleCodeExporter commented 9 years ago 
Here you go, another debug log

Original comment by revolver...@gmail.com on 5 Jul 2013 at 11:15

Attachments:

GoogleCodeExporter commented 9 years ago 
Ugh, this is frustrating. It's simply not there. Try the latest again, this 
will have ALL the data coming from the receiver, was hoping not to resort to 
this, a lot of data to parse through.

If I can't find it here, the only other thing I can think of is that Ryan and 
my keep-alive commands are working differently, but that seems like a stretch.

https://xbox360wirelesschatpad.googlecode.com/svn/trunk/Issue%20Debugging%20Buil
d.exe

1. Connect your controller like normal.
2. Select the Chatpad Test area and enter the sequence "1 2 3 4 5".
3. Close the application.
4. Attach "debugLog.txt" to your reply, it should be located in the same 
directory as the executable.

Original comment by ksbarnes@skyag.net on 5 Jul 2013 at 11:26

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
Here's another one.

Original comment by revolver...@gmail.com on 6 Jul 2013 at 12:11

Attachments:

GoogleCodeExporter commented 9 years ago 
Still not there, the only thing I can think of is initialization/keep alive 
differences. I've added some additional commands that Ryan had, hopefully this 
magically fixes things...though it's not ideal as I don't know where those 
commands came from.

Try the latest issue debug build, same procedure, "1 2 3 4 5", and post your 
log.
https://xbox360wirelesschatpad.googlecode.com/svn/trunk/Issue%20Debugging%20Buil
d.exe

Original comment by ksbarnes@skyag.net on 6 Jul 2013 at 12:23

GoogleCodeExporter commented 9 years ago 
Alright, something definitely worked. With this new debugging build I'm getting 
an occasional response, but it's irregular and I have to keep pressing at the 
keys to get anything.

Original comment by revolver...@gmail.com on 6 Jul 2013 at 12:39

Attachments:

GoogleCodeExporter commented 9 years ago 
That's great news, though unfortunate as I don't really know why those commands 
helped. I've done some tweaking, hoping that they're just being called too 
frequently.

Try the latest issue debug build, same procedure, "1 2 3 4 5", and post your 
log.
https://xbox360wirelesschatpad.googlecode.com/svn/trunk/Issue%20Debugging%20Buil
d.exe

Original comment by ksbarnes@skyag.net on 6 Jul 2013 at 2:03

GoogleCodeExporter commented 9 years ago 
Alright, tried the new build, but this time no response from the chatpad at 
all, just the lights.

Original comment by revolver...@gmail.com on 6 Jul 2013 at 4:03

Attachments:

GoogleCodeExporter commented 9 years ago 
A few more tweaks. I wish I could re-produce your problem on my end...

Try the latest issue debug build, same procedure, "1 2 3 4 5", and post your 
log.
https://xbox360wirelesschatpad.googlecode.com/svn/trunk/Issue%20Debugging%20Buil
d.exe

Original comment by ksbarnes@skyag.net on 6 Jul 2013 at 3:48

GoogleCodeExporter commented 9 years ago

Original comment by revolver...@gmail.com on 6 Jul 2013 at 8:08

Attachments:

GoogleCodeExporter commented 9 years ago 
Although I haven't run any debugging yet, I would like to add that with my 
issue, the gamepad button-presses (e.g. ABXY) sometimes didn't register, or 
when I tapped a button, my PC thought I was holding the button down. Also, 
dunno if this is because of vJoy or whatever, but all of my buttons were 
mis-mapped in my games (e.g. start menu was brought up with RB rather than 
Start button). Ultimately, that's a small issue, since I can just re-map my 
buttons, but I thought it was strange nonetheless.

Thanks so much for your efforts, this is definitely the closest I've seen 
anyone get on this issue! :D

Original comment by yami...@gmail.com on 7 Jul 2013 at 12:02

GoogleCodeExporter commented 9 years ago 
Just an update, with good news. I've been able to (I think) replicate the issue 
on a different Xbox 360 controller of mine. Same problem, chatpad lights up but 
no keystrokes happening. Now that I have the same issue, I should be able to 
debug a little more robustly and fix it.. *crosses fingers*

Original comment by ksbarnes@skyag.net on 7 Jul 2013 at 3:04

GoogleCodeExporter commented 9 years ago 
Great news! I discovered an error in the keep-alive timer that was causing 
keep-alive commands to go out at the thread rate without delay. Fixing this, 
and tweaking a few other device commands, I've been able to successfully get a 
previously un-responsive chatpad to work properly.

To all with this problem, please try the latest Issue Debugging Build at the 
following location:

https://xbox360wirelesschatpad.googlecode.com/svn/trunk/Issue%20Debugging%20Buil
d.exe

Please report back if it works and if it doesn't attach the associated 
debugLog.txt that will exist in the executable directory.

BIG NOTE: If it does work, understand that this build is very in-efficient and 
creates a file that will continue to grow in size as long as you run the 
program, no bounds. As soon as I here some success stories, I'll release a new 
version of the main application as quick as possible.

Original comment by ksbarnes@skyag.net on 7 Jul 2013 at 4:14

GoogleCodeExporter commented 9 years ago 
Now it works perfectly, and as an aside, I've noticed the gamepad is a lot more 
responsive compared to the previous builds, although there is still an 
occasional problem when pressing multiple buttons.

Original comment by revolver...@gmail.com on 7 Jul 2013 at 9:49

GoogleCodeExporter commented 9 years ago 
Perfect, as you're the original reporter, I'll consider this issue closed. 
Please download the latest version of the full application at the following:

https://xbox360wirelesschatpad.googlecode.com/svn/trunk/Xbox%20360%20Wireless%20
Chatpad.zip

Regarding the multiple buttons, could you open a new issue with a bit more of a 
description on what you're seeing and maybe a scenario I can try to reproduce.

To all others, if you're continuing to experience the problem, please create a 
new Issue and include your Operating System and .NET Framework version.

Original comment by ksbarnes@skyag.net on 7 Jul 2013 at 10:27