Need some info from Logitech G13 and G19, and newer X-Keys devices

[Lax]

Okay so I've been waiting a few days for someone to show up with one of these devices. There was a week or two where tons of people came in asking about the G13 and then I haven't seen anyone in weeks

Anyway here's the deal. Copy of post from my forums:

Okay, anyone with a G13 or G19 (or any other currently unsupported device) I have a new program that can collect the data required to support these and other devices.

http://www.lavishsoft.com/downloads/...ttonTester.exe

To use it:
1. Make sure the device is plugged in and operational
2. Run Lavish.ButtonTester.exe. It will open a DOS window to show its output.
3. When it says "Waiting for input..." it is ready for you to start hitting buttons on the device
4. Press each button in an order that makes some sort of sense -- the program is going to tell you some numbers, in the order your buttons are pressed. If you hit a button and do not see anything happen, the device may be emulating a keyboard at the hardware level, which means it either needs to be reconfigured, or it will not work. Otherwise, you should see output like this:

050D-0815 v210 (Unnamed Device): Button 1 at bit 72

5. Get me the complete list
6. Wait for me to add support for the device

That's about it. As far as device configuration and not producing output, here's an example. The output example I gave is with a Nostromo Speedpad n52 (not n52te). The n52 by default emulates the keyboard, and to show up as buttons on the device instead of keyboard buttons, each button had to be configured as a "DI Button" (Direct Input Button). With a Logitech G15 keyboard, each button must be "Unassigned" (via the Logitech Keyboard Profiler), so I would expect the same from a G13 or G19.

Soooo if anyone with a G13, G19, X-Keys with new firmware (older firmware is natively supported), or pretty much any USB input device that currently is not supported by Inner Space wants to provide this info, I can add support.

Edit: You do not need to be an IS user to provide this info

[lazygirl]

I am not an IS user (anymore, used it briefly for.. other purposes..). But I am willing to help out with my new USB (hush! I don't PVP!) x-keys.

When I tried to run the software however, I got the following message:
The procedure entry point CancelIOEx could not be located in the dynamic library KERNEL32.dll

[Lax]

Aha. Apparently the test program requires Vista or later. I will correct that and put up a new version of it later today, thanks for pointing that out

[Lax]

Updated the download and added a new link in case your browser wants to keep the original cached: http://www.lavishsoft.com/downloads/...nTester.XP.exe

thanks

[laguy]

My G19 is supposed to arrive on Monday 6/22 and I will attempt to create the file for you ASAP.

[Kuroshiro]

This is everything I've found so far. I'm sorry about the joystick, it's a bit tricky to get a consistent read out of it, since it seems your program only prints out on first detection. If you have more specific programs you'd like me to test with, I'd be happy to.

G1-G22

046D-C21C v103 (G13): Button 1 at bit 24
046D-C21C v103 (G13): Button 2 at bit 25
046D-C21C v103 (G13): Button 3 at bit 26
046D-C21C v103 (G13): Button 4 at bit 27
046D-C21C v103 (G13): Button 5 at bit 28
046D-C21C v103 (G13): Button 6 at bit 29
046D-C21C v103 (G13): Button 7 at bit 30
046D-C21C v103 (G13): Button 8 at bit 31
046D-C21C v103 (G13): Button 9 at bit 32
046D-C21C v103 (G13): Button 10 at bit 33
046D-C21C v103 (G13): Button 11 at bit 34
046D-C21C v103 (G13): Button 12 at bit 35
046D-C21C v103 (G13): Button 13 at bit 36
046D-C21C v103 (G13): Button 14 at bit 37
046D-C21C v103 (G13): Button 15 at bit 38
046D-C21C v103 (G13): Button 16 at bit 39
046D-C21C v103 (G13): Button 17 at bit 40
046D-C21C v103 (G13): Button 18 at bit 41
046D-C21C v103 (G13): Button 19 at bit 42
046D-C21C v103 (G13): Button 20 at bit 43
046D-C21C v103 (G13): Button 21 at bit 44
046D-C21C v103 (G13): Button 22 at bit 45

Button to left of stick (G23)
046D-C21C v103 (G13): Button 23 at bit 57

Button to bottom of stick (G24)
046D-C21C v103 (G13): Button 24 at bit 58

Fiddling with the stick, including pressing down on it (I think 59 is pushing down):

046D-C21C v103 (G13): Button 1 at bit 17
046D-C21C v103 (G13): Button 2 at bit 8
046D-C21C v103 (G13): Button 3 at bit 16
046D-C21C v103 (G13): Button 4 at bit 9
046D-C21C v103 (G13): Button 5 at bit 59
046D-C21C v103 (G13): Button 6 at bit 63
046D-C21C v103 (G13): Button 7 at bit 18
046D-C21C v103 (G13): Button 8 at bit 10
046D-C21C v103 (G13): Button 9 at bit 11
046D-C21C v103 (G13): Button 10 at bit 19
046D-C21C v103 (G13): Button 11 at bit 20

M1-M3
046D-C21C v103 (G13): Button 14 at bit 53
046D-C21C v103 (G13): Button 12 at bit 54
046D-C21C v103 (G13): Button 13 at bit 55

4 buttons under the LCD
046D-C21C v103 (G13): Button 4 at bit 49
046D-C21C v103 (G13): Button 1 at bit 50
046D-C21C v103 (G13): Button 2 at bit 51
046D-C21C v103 (G13): Button 3 at bit 52

LCD Plugin Toggle
046D-C21C v103 (G13): Button 5 at bit 48

[Lax]

This is everything I've found so far. I'm sorry about the joystick, it's a bit tricky to get a consistent read out of it, since it seems your program only prints out on first detection. If you have more specific programs you'd like me to test with, I'd be happy to.

Well, the program is only designed to handle buttons and just assumes everything you're touching is a button at the moment :P NP though, your info is very thorough and gives me all the info I should need to support the G13, thank you

[Lax]

I take that back, you seem to have missed MR, but I'm going to assume it's 56

[Kuroshiro]

I take that back, you seem to have missed MR, but I'm going to assume it's 56

Whups! Just confirmed MR is indeed 56. Sorry about that. Also, pushing down on the joystick is 59.

[Lax]

G13 support is now tested and functional in Inner Space build 5011 (buttons only -- including joystick press, but not joystick movement, which can still be configured via the logitech profiler). Still need someone with a G19.

X-keys device support should be functional for any new X-keys USB devices as of build 5011, but I don't have confirmation on that. Older X-keys USB devices were already supported.