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/Lavish.ButtonTester.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/Lavish.ButtonTester.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.

[laguy]

Here is what I got from the G19.

G1-G12
046D-C229 v23 (G19 Gaming Keyboard (Macro interface)): Button 1 at bit 8
046D-C229 v23 (G19 Gaming Keyboard (Macro interface)): Button 2 at bit 14
046D-C229 v23 (G19 Gaming Keyboard (Macro interface)): Button 3 at bit 9
046D-C229 v23 (G19 Gaming Keyboard (Macro interface)): Button 4 at bit 15
046D-C229 v23 (G19 Gaming Keyboard (Macro interface)): Button 5 at bit 10
046D-C229 v23 (G19 Gaming Keyboard (Macro interface)): Button 6 at bit 16
046D-C229 v23 (G19 Gaming Keyboard (Macro interface)): Button 7 at bit 11
046D-C229 v23 (G19 Gaming Keyboard (Macro interface)): Button 8 at bit 17
046D-C229 v23 (G19 Gaming Keyboard (Macro interface)): Button 9 at bit 12
046D-C229 v23 (G19 Gaming Keyboard (Macro interface)): Button 10 at bit 18
046D-C229 v23 (G19 Gaming Keyboard (Macro interface)): Button 11 at bit 13
046D-C229 v23 (G19 Gaming Keyboard (Macro interface)): Button 12 at bit 19

m1-m3 and mr
046D-C229 v23 (G19 Gaming Keyboard (Macro interface)): Button 1 at bit 20
046D-C229 v23 (G19 Gaming Keyboard (Macro interface)): Button 2 at bit 21
046D-C229 v23 (G19 Gaming Keyboard (Macro interface)): Button 3 at bit 22
046D-C229 v23 (G19 Gaming Keyboard (Macro interface)): Button 4 at bit 23

color selector button
046D-C229 v23 (G19 Gaming Keyboard (Macro interface)): Button 1 at bit 27

4 buttons in top right of keyboard (appear to be used for video playback
button 1 is play/pause
button 2 is stop
button 3 is rewind
button 4 is fast forward
046D-C228 v110 (G19 Gaming Keyboard): Button 1 at bit 11
046D-C228 v110 (G19 Gaming Keyboard): Button 2 at bit 10
046D-C228 v110 (G19 Gaming Keyboard): Button 3 at bit 9
046D-C228 v110 (G19 Gaming Keyboard): Button 4 at bit 8

sound mute button
046D-C228 v110 (G19 Gaming Keyboard): Button 1 at bit 12

scrolling wheel (upper right of keyboard) scrolling down
046D-C228 v110 (G19 Gaming Keyboard): Button 1 at bit 14

scrolling wheel (upper right of keyboard) scrolling up
046D-C228 v110 (G19 Gaming Keyboard): Button 2 at bit 13

Joystick switch (only get data when I push the switch to the right)
046D-C228 v110 (G19 Gaming Keyboard): Button 1 at bit 8

There are several buttons such as menu and some scrolling arrows that allow you to config the LCD display a menu button, an ok button and some others that I haven't figured out yet that all seem to be related to the LCD screen but nothing shows up when I push those buttons.

Let me know if you need anything else.

[Lax]

Can you re-download the program and a couple of the buttons again -- one of the ones that said "Macro interface" and one that just said "G19 Gaming Keyboard". I added a little bit of info to each line, but it'd be the same for each one on the same device so I don't need you to redo all of them ;)

[laguy]

This is the new data. I went ahead and reloaded everything just to make sure I got them. I made a couple of corrections to what the buttons did since I had a chance to play around with the keyboard last night. The color button is really for turning off the lcd display and the key I thought was for joystick control turns off the keyboard button to return to windows while the game is running. Hope that helped.

G1-G12
046D-C229 v23 (65280,0,4)(G19 Gaming Keyboard (Macro interface)): Button 1 at bi
t 8
046D-C229 v23 (65280,0,4)(G19 Gaming Keyboard (Macro interface)): Button 2 at bi
t 14
046D-C229 v23 (65280,0,4)(G19 Gaming Keyboard (Macro interface)): Button 3 at bi
t 9
046D-C229 v23 (65280,0,4)(G19 Gaming Keyboard (Macro interface)): Button 4 at bi
t 15
046D-C229 v23 (65280,0,4)(G19 Gaming Keyboard (Macro interface)): Button 5 at bi
t 10
046D-C229 v23 (65280,0,4)(G19 Gaming Keyboard (Macro interface)): Button 6 at bi
t 16
046D-C229 v23 (65280,0,4)(G19 Gaming Keyboard (Macro interface)): Button 7 at bi
t 11
046D-C229 v23 (65280,0,4)(G19 Gaming Keyboard (Macro interface)): Button 8 at bi
t 17
046D-C229 v23 (65280,0,4)(G19 Gaming Keyboard (Macro interface)): Button 9 at bi
t 12
046D-C229 v23 (65280,0,4)(G19 Gaming Keyboard (Macro interface)): Button 10 at b
it 18
046D-C229 v23 (65280,0,4)(G19 Gaming Keyboard (Macro interface)): Button 11 at b
it 13
046D-C229 v23 (65280,0,4)(G19 Gaming Keyboard (Macro interface)): Button 12 at b
it 19

m1-m3 and mr
046D-C229 v23 (65280,0,4)(G19 Gaming Keyboard (Macro interface)): Button 1 at bi
t 20
046D-C229 v23 (65280,0,4)(G19 Gaming Keyboard (Macro interface)): Button 2 at bi
t 21
046D-C229 v23 (65280,0,4)(G19 Gaming Keyboard (Macro interface)): Button 3 at bi
t 22
046D-C229 v23 (65280,0,4)(G19 Gaming Keyboard (Macro interface)): Button 4 at bi
t 23

this turns off the lcd display (i thought it was somehow rela
046D-C229 v23 (65280,0,4)(G19 Gaming Keyboard (Macro interface)): Button 1 at bi
t 27

4 buttons in top right of keyboard (appear to be used for video playback
button 1 is play/pause
button 2 is stop
button 3 is rewind
button 4 is fast forward
046D-C228 v110 (12,1,2)(G19 Gaming Keyboard): Button 1 at bit 11
046D-C228 v110 (12,1,2)(G19 Gaming Keyboard): Button 2 at bit 10
046D-C228 v110 (12,1,2)(G19 Gaming Keyboard): Button 3 at bit 9
046D-C228 v110 (12,1,2)(G19 Gaming Keyboard): Button 4 at bit 8

sound mute button
046D-C228 v110 (12,1,2)(G19 Gaming Keyboard): Button 1 at bit 12

scrolling wheel (upper right of keyboard) scrolling down
046D-C228 v110 (12,1,2)(G19 Gaming Keyboard): Button 1 at bit 14

scrolling wheel (upper right of keyboard) scrolling up
046D-C228 v110 (12,1,2)(G19 Gaming Keyboard): Button 2 at bit 13

This is for turning off the keyboard button to return to the OS
046D-C228 v110 (65280,1,8 )(G19 Gaming Keyboard): Button 1 at bit 8 (had to insert a space after the 8 to keep the 8 paren from turning to a happy face)

[Lax]

G19 support should now be working in the Development build (5013) of Inner Space. If someone can test it and let me know, please see me in ISBoxer chat -- http://www.lavishsoft.com/chat/isboxer.php
To switch to the Development build, go to the IS Patcher window (select Patcher from the IS menu), check "Download development (test) builds", then close and re-start Inner Space. (To switch back later, follow the same process)

All of the buttons described in laguy's post, except for the "turning off the keyboard button to return to the OS" should be supported

[laguy]

I did some testing today on the G19 keyboard support and everything seemed to be working okay. I was able to select the G19-Gx keys from within ISBoxer with no problems, assigned them to some actions/macros and did some limited testing. I did not test the play/rewind/etc keys.

I should say that I am returning my G19 since it apparently is not going to work with my primary play CPU. Apparently there is a problem with some motherboards with the G19. What happens is when you boot it says it cannot find the keyboard. There are reports on both the ASUS forums and some with EVGA (which is what I have). This doesn't happen on every machine but my EVGA X58 MB certainly has the problem. The only workaround appears to be to have another keyboard plugged in during the boot sequence and then once the OS is running you can start using the G19. Not exactly what I was looking for. I am told it will take mods to the MB BIOS to fix the problem which I am guessing is not going to be a top priority for some motherboard manufacturers.

Other than that I really liked the feel of the keyboard and the WoW display was nice when I was in the game. I like Logitech hardware and was dissappointed that it didn't work. That is the problem with being an early adopter. Your mileage may vary.

Update: It appears the ASUS mb problem has been resolved with a bios update. EVGA x58 still has the problem.

[Lax]

Great, thanks for sharing your experience with it. I'll have to push this build live :)

[laguy]

Lax, I might have spoken to soon about the G19 working correctly. I ended up keeping my keyboard while I work with EVGA and Logitech in finding a solution. I have it working temporarily by installing a USB 1.1 hub to slow down the interface. For some reason that allows the keyboard to boot properly. I have been disconnecting the hub after my machine runs since I seldom reboot anyway.

On to the issue. This might just be operator error (probably). What I did in my initial testing was to assign keystrokes to the G1 - G12 keys to issue commands within WoW. In other words, I made G1 send Ctrl-Alt-F1 and then within ISBoxer made Ctrl-Alt-F1 perform some task such as executing a macro. I also setup some send text strings or just single chars to open the quest log (L), etc. All of these techniques worked great. What I guess I didn't test properly was just using the G19-G1 from within ISBoxer and then setting the Logitech Key Profiler to be enabled (the default appears to be that G1 sends F1, G2- F2.... At least, I don't seem to be able to get it to work now.

I have tried everything I can think of to make this unassigned key work but it never seems to pick up the commands. Any suggestions on what I might be doing wrong?

Thanks

[Lax]

Just had someone with a G19 that came to the ISBoxer chat room do some tests. Some of the G keys from the G19 info were out of order and I've corrected that. Otherwise, looks fine. IS build 5016 will go live with G19 support (and also X-Keys Desktop with new firmware)

To use G11, G15, or G19 properly with IS and ISBoxer: Unassign all keys in the Logitech Profiler, then close it.

[laguy]

I tested the new release with my G19 and it seems almost everything is working fine now. I unassigned the G keys within the Logitech G-series key profiler, set up some commands within Isboxer, then turned off the G-series profiler and they worked perfectly from WoW. The only thing I couldn't get working was the repeater profile option that lets you use the G15/G11 keyboard indicator lights. I tried using the MR,M2 and M3 keys in both key repeat and mouse repeat and none of them light up when I toggled key or mouse repeating. Might be I did something wrong or maybe you didn't hook that up for the G19. Not a big deal, but thought I would pass it along. Other than that, things look great.

Just a side note on how much I really love Isboxer and Inner Space. I have lots of chars at various levels, most 60+ and lots of different combinations of 5 char groups that I play. These tools have made it so easy to for me to switch chars around and be running with a completely different set of chars in just a few minutes. For example, I was leveling some shammy's to 60 using RAF the other day, decided to blast through 2 more since I had lots of time left on the RAF. I just added two more chars within Isboxer, replaced them in the slots of the old team and bam I was off and running. No more messing with individual config/macro files.

[moosejaw]

All 58 keys starting top left and going left to right. This is the newer firmware. The button numbers reset at the start of each row. You can call them 1-58 from top to bottom.
Product link ('http://www.xkeys.com/xkeys/xkpro.php') .



05F3-02A7 v330 <12,1,32><XKeys Pro >: Button 1 at bit 8
05F3-02A7 v330 <12,1,32><XKeys Pro >: Button 2 at bit 16
05F3-02A7 v330 <12,1,32><XKeys Pro >: Button 3 at bit 24
05F3-02A7 v330 <12,1,32><XKeys Pro >: Button 4 at bit 32
05F3-02A7 v330 <12,1,32><XKeys Pro >: Button 5 at bit 40
05F3-02A7 v330 <12,1,32><XKeys Pro >: Button 6 at bit 48
05F3-02A7 v330 <12,1,32><XKeys Pro >: Button 7 at bit 56
05F3-02A7 v330 <12,1,32><XKeys Pro >: Button 8 at bit 64
05F3-02A7 v330 <12,1,32><XKeys Pro >: Button 9 at bit 72
05F3-02A7 v330 <12,1,32><XKeys Pro >: Button 1 at bit 9
05F3-02A7 v330 <12,1,32><XKeys Pro >: Button 2 at bit 17
05F3-02A7 v330 <12,1,32><XKeys Pro >: Button 3 at bit 25
05F3-02A7 v330 <12,1,32><XKeys Pro >: Button 4 at bit 33
05F3-02A7 v330 <12,1,32><XKeys Pro >: Button 5 at bit 41
05F3-02A7 v330 <12,1,32><XKeys Pro >: Button 6 at bit 49
05F3-02A7 v330 <12,1,32><XKeys Pro >: Button 7 at bit 57
05F3-02A7 v330 <12,1,32><XKeys Pro >: Button 8 at bit 65
05F3-02A7 v330 <12,1,32><XKeys Pro >: Button 9 at bit 73
05F3-02A7 v330 <12,1,32><XKeys Pro >: Button 1 at bit 10
05F3-02A7 v330 <12,1,32><XKeys Pro >: Button 2 at bit 18
05F3-02A7 v330 <12,1,32><XKeys Pro >: Button 3 at bit 26
05F3-02A7 v330 <12,1,32><XKeys Pro >: Button 4 at bit 34
05F3-02A7 v330 <12,1,32><XKeys Pro >: Button 5 at bit 42
05F3-02A7 v330 <12,1,32><XKeys Pro >: Button 6 at bit 50
05F3-02A7 v330 <12,1,32><XKeys Pro >: Button 7 at bit 58
05F3-02A7 v330 <12,1,32><XKeys Pro >: Button 8 at bit 66
05F3-02A7 v330 <12,1,32><XKeys Pro >: Button 1 at bit 11
05F3-02A7 v330 <12,1,32><XKeys Pro >: Button 2 at bit 19
05F3-02A7 v330 <12,1,32><XKeys Pro >: Button 3 at bit 27
05F3-02A7 v330 <12,1,32><XKeys Pro >: Button 4 at bit 35
05F3-02A7 v330 <12,1,32><XKeys Pro >: Button 5 at bit 43
05F3-02A7 v330 <12,1,32><XKeys Pro >: Button 6 at bit 51
05F3-02A7 v330 <12,1,32><XKeys Pro >: Button 7 at bit 59
05F3-02A7 v330 <12,1,32><XKeys Pro >: Button 8 at bit 67
05F3-02A7 v330 <12,1,32><XKeys Pro >: Button 1 at bit 12
05F3-02A7 v330 <12,1,32><XKeys Pro >: Button 2 at bit 20
05F3-02A7 v330 <12,1,32><XKeys Pro >: Button 3 at bit 28
05F3-02A7 v330 <12,1,32><XKeys Pro >: Button 4 at bit 36
05F3-02A7 v330 <12,1,32><XKeys Pro >: Button 5 at bit 44
05F3-02A7 v330 <12,1,32><XKeys Pro >: Button 6 at bit 52
05F3-02A7 v330 <12,1,32><XKeys Pro >: Button 7 at bit 60
05F3-02A7 v330 <12,1,32><XKeys Pro >: Button 8 at bit 68
05F3-02A7 v330 <12,1,32><XKeys Pro >: Button 1 at bit 13
05F3-02A7 v330 <12,1,32><XKeys Pro >: Button 2 at bit 21
05F3-02A7 v330 <12,1,32><XKeys Pro >: Button 3 at bit 29
05F3-02A7 v330 <12,1,32><XKeys Pro >: Button 4 at bit 37
05F3-02A7 v330 <12,1,32><XKeys Pro >: Button 5 at bit 45
05F3-02A7 v330 <12,1,32><XKeys Pro >: Button 6 at bit 53
05F3-02A7 v330 <12,1,32><XKeys Pro >: Button 7 at bit 61
05F3-02A7 v330 <12,1,32><XKeys Pro >: Button 8 at bit 69
05F3-02A7 v330 <12,1,32><XKeys Pro >: Button 1 at bit 14
05F3-02A7 v330 <12,1,32><XKeys Pro >: Button 2 at bit 22
05F3-02A7 v330 <12,1,32><XKeys Pro >: Button 3 at bit 30
05F3-02A7 v330 <12,1,32><XKeys Pro >: Button 4 at bit 38
05F3-02A7 v330 <12,1,32><XKeys Pro >: Button 5 at bit 46
05F3-02A7 v330 <12,1,32><XKeys Pro >: Button 6 at bit 54
05F3-02A7 v330 <12,1,32><XKeys Pro >: Button 7 at bit 62
05F3-02A7 v330 <12,1,32><XKeys Pro >: Button 8 at bit 70

This is the programing switch on the side of the unit.
05F3-02A7 v330 <12,1,32><XKeys Pro >: Button 1 at bit 92

[moosejaw]

I have enclosed an Excel spreadsheet with the IS key assignments for the Xkeys pro 58 key with the newer firmware.

[Fizzler]

Here is my X-Key Pro. It differs from the previous page so perhaps I have the older firmware but looking at their website I want to say its the latest firmware. I will have to find out how to determine this. X-Keys MWII


Starting at the top left going left to right top to bottom.

Waiting for input...
05F3-02A7 v330 (12,1,32)(XKeys Pro ): Button 1 at bit 8
05F3-02A7 v330 (12,1,32)(XKeys Pro ): Button 2 at bit 16
05F3-02A7 v330 (12,1,32)(XKeys Pro ): Button 3 at bit 24
05F3-02A7 v330 (12,1,32)(XKeys Pro ): Button 4 at bit 32
05F3-02A7 v330 (12,1,32)(XKeys Pro ): Button 5 at bit 40
05F3-02A7 v330 (12,1,32)(XKeys Pro ): Button 6 at bit 48
05F3-02A7 v330 (12,1,32)(XKeys Pro ): Button 7 at bit 56
05F3-02A7 v330 (12,1,32)(XKeys Pro ): Button 8 at bit 64
05F3-02A7 v330 (12,1,32)(XKeys Pro ): Button 9 at bit 72
05F3-02A7 v330 (12,1,32)(XKeys Pro ): Button 10 at bit 9
05F3-02A7 v330 (12,1,32)(XKeys Pro ): Button 11 at bit 17
05F3-02A7 v330 (12,1,32)(XKeys Pro ): Button 12 at bit 25
05F3-02A7 v330 (12,1,32)(XKeys Pro ): Button 13 at bit 33
05F3-02A7 v330 (12,1,32)(XKeys Pro ): Button 14 at bit 41
05F3-02A7 v330 (12,1,32)(XKeys Pro ): Button 15 at bit 49
05F3-02A7 v330 (12,1,32)(XKeys Pro ): Button 16 at bit 57
05F3-02A7 v330 (12,1,32)(XKeys Pro ): Button 17 at bit 65
05F3-02A7 v330 (12,1,32)(XKeys Pro ): Button 18 at bit 73
05F3-02A7 v330 (12,1,32)(XKeys Pro ): Button 19 at bit 10
05F3-02A7 v330 (12,1,32)(XKeys Pro ): Button 20 at bit 18
05F3-02A7 v330 (12,1,32)(XKeys Pro ): Button 21 at bit 26
05F3-02A7 v330 (12,1,32)(XKeys Pro ): Button 22 at bit 34
05F3-02A7 v330 (12,1,32)(XKeys Pro ): Button 23 at bit 42
05F3-02A7 v330 (12,1,32)(XKeys Pro ): Button 24 at bit 50
05F3-02A7 v330 (12,1,32)(XKeys Pro ): Button 25 at bit 58
05F3-02A7 v330 (12,1,32)(XKeys Pro ): Button 26 at bit 66
05F3-02A7 v330 (12,1,32)(XKeys Pro ): Button 27 at bit 11
05F3-02A7 v330 (12,1,32)(XKeys Pro ): Button 28 at bit 19
05F3-02A7 v330 (12,1,32)(XKeys Pro ): Button 29 at bit 27
05F3-02A7 v330 (12,1,32)(XKeys Pro ): Button 30 at bit 35
05F3-02A7 v330 (12,1,32)(XKeys Pro ): Button 31 at bit 43
05F3-02A7 v330 (12,1,32)(XKeys Pro ): Button 32 at bit 51
05F3-02A7 v330 (12,1,32)(XKeys Pro ): Button 33 at bit 59
05F3-02A7 v330 (12,1,32)(XKeys Pro ): Button 34 at bit 67
05F3-02A7 v330 (12,1,32)(XKeys Pro ): Button 35 at bit 12
05F3-02A7 v330 (12,1,32)(XKeys Pro ): Button 36 at bit 20
05F3-02A7 v330 (12,1,32)(XKeys Pro ): Button 37 at bit 28
05F3-02A7 v330 (12,1,32)(XKeys Pro ): Button 38 at bit 36
05F3-02A7 v330 (12,1,32)(XKeys Pro ): Button 39 at bit 44
05F3-02A7 v330 (12,1,32)(XKeys Pro ): Button 40 at bit 52
05F3-02A7 v330 (12,1,32)(XKeys Pro ): Button 41 at bit 60
05F3-02A7 v330 (12,1,32)(XKeys Pro ): Button 42 at bit 68
05F3-02A7 v330 (12,1,32)(XKeys Pro ): Button 43 at bit 13
05F3-02A7 v330 (12,1,32)(XKeys Pro ): Button 44 at bit 21
05F3-02A7 v330 (12,1,32)(XKeys Pro ): Button 45 at bit 29
05F3-02A7 v330 (12,1,32)(XKeys Pro ): Button 46 at bit 37
05F3-02A7 v330 (12,1,32)(XKeys Pro ): Button 47 at bit 45
05F3-02A7 v330 (12,1,32)(XKeys Pro ): Button 48 at bit 53
05F3-02A7 v330 (12,1,32)(XKeys Pro ): Button 49 at bit 61
05F3-02A7 v330 (12,1,32)(XKeys Pro ): Button 50 at bit 69
05F3-02A7 v330 (12,1,32)(XKeys Pro ): Button 51 at bit 14
05F3-02A7 v330 (12,1,32)(XKeys Pro ): Button 52 at bit 22
05F3-02A7 v330 (12,1,32)(XKeys Pro ): Button 53 at bit 30
05F3-02A7 v330 (12,1,32)(XKeys Pro ): Button 54 at bit 38
05F3-02A7 v330 (12,1,32)(XKeys Pro ): Button 55 at bit 46
05F3-02A7 v330 (12,1,32)(XKeys Pro ): Button 56 at bit 54
05F3-02A7 v330 (12,1,32)(XKeys Pro ): Button 57 at bit 62
05F3-02A7 v330 (12,1,32)(XKeys Pro ): Button 58 at bit 70

Side Program Switch:
05F3-02A7 v330 (12,1,32)(XKeys Pro ): Button 1 at bit 92

[moosejaw]

That is the same data except for the button numbers. Otherwise it is the same data. Plug it in and set IS to use the developement build to see if it works.

[Solusek]

I have an X-keys button bar. Definitely new version (old ones cannot be programmed on Vista).

Xkeys Button Bar

First Row 1 – 14

05F3-0304 u320 (12,1,19)(Xkeys): Button 1 at bit 8
05E13-0304 u320 (12,1,19)(Xkeys): Button 2 at bit 9
05F3-0304 u320 (12,1,19)(Xkeys): Button 3 at bit 10
05E13-0304 u320 (12,1,19)(Xkeys): Button 4 at bit 11
05F3-0304 u320 (12,1,19)(Xkeys): Button 5 at bit 12
05E13-0304 u320 (12,1,19)(Xkeys): Button 6 at bit 13
05F3-0304 u320 (12,1,19)(Xkeys): Button 7 at bit 16
05E13-0304 u320 (12,1,19)(Xkeys): Button 8 at bit 17
05F3-0304 u320 (12,1,19)(Xkeys): Button 9 at bit 18
05E13-0304 u320 (12,1,19)(Xkeys): Button 10 at bit 19
05F3-0304 u320 (12,1,19)(Xkeys): Button 11 at bit 20
05E13-0304 u320 (12,1,19)(Xkeys): Button 12 at bit 21
05F3-0304 u320 (12,1,19)(Xkeys): Button 13 at bit 40
05E13-0304 u320 (12,1,19)(Xkeys): Button 14 at bit 41

Second Row 1 - 14

05F3-0304 u320 (12,1,19)(Xkeys): Button 15 at bit 24
05E13-0304 u320 (12,1,19)(Xkeys): Button 16 at bit 25
05F3-0304 u320 (12,1,19)(Xkeys): Button 17 at bit 26
05E13-0304 u320 (12,1,19)(Xkeys): Button 18 at bit 27
05F3-0304 u320 (12,1,19)(Xkeys): Button 19 at bit 28
05E13-0304 u320 (12,1,19)(Xkeys): Button 20 at bit 29
05F3-0304 u320 (12,1,19)(Xkeys): Button 21 at bit 32
05E13-0304 u320 (12,1,19)(Xkeys): Button 22 at bit 33
05F3-0304 u320 (12,1,19)(Xkeys): Button 23 at bit 34
05E13-0304 u320 (12,1,19)(Xkeys): Button 24 at bit 35
05F3-0304 u320 (12,1,19)(Xkeys): Button 25 at bit 36
05E13-0304 u320 (12,1,19)(Xkeys): Button 26 at bit 37
05F3-0304 u320 (12,1,19)(Xkeys): Button 27 at bit 42
05E13-0304 u320 (12,1,19)(Xkeys): Button 28 at bit 43

Up and down toggle
05F3-0304 u320 (12,1,19)(Xkeys): Button 29 at bit 44
05E13-0304 u320 (12,1,19)(Xkeys): Button 30 at bit 45

Up, Right, Down, Left keys
05F3-0304 u320 (12,1,19)(Xkeys): Button 31 at bit 48
05E13-0304 u320 (12,1,19)(Xkeys): Button 32 at bit 50
05F3-0304 u320 (12,1,19)(Xkeys): Button 33 at bit 51
55F3-0304 u320 (12,1,19)(Xkeys): Button 34 at bit 49

Now I have a question associated with this that I don’t see as a clear answer and I cannot experiment (Inner Space does not respond in any way to the box). Does Inner Space respond to the single key press of the actual button on the X-key bar or to the sequence that MacroWorks II generates?

I hope it is the latter. I tend to use X-Keys to spam certain keys to generate a “castsequence” of sorts. If it is still in cooldown or out of range, it goes on to the next. WoW’s own internal logic takes care of the rest. I also put delays in that does one thing, waits a period and then another.

[moosejaw]

IS will see the hardware keypress and work off of that if you prgram that key to do something with IS/ISboxer. You can still use the macroworks software and as long as you don't have that keycombo set up in a keymap it will pass to your active window. You can also enter that key combo into your keymap and have it sent to whichever windows you want, or don't want, by having the same combo as input and output of the keymap.

[daanji]

I have an X-Keys FootPedal SE.

I have program the buttons on the foot pedal with a baisc key stroke but IsBoxer doesn't appear to be able to see the key.

The foot pedal has 3 button (left, middle, and right).

Here is the information from your program:

Waiting for input...
05F3-0268 v320 (12,1,19)(Xkeys): Button 1 at bit 9
05F3-0268 v320 (12,1,19)(Xkeys): Button 2 at bit 10
05F3-0268 v320 (12,1,19)(Xkeys): Button 3 at bit 11

The funny thing is this worked fine with an older version of IsBoxer (about 6 months ago).

Not sure what is going wrong now.

When I press the foot pedal, the key strokes will appear in notepad or anywhere. IsBoxer does not see them.

[PIEAmber]

I know this is a bit of a delay, but I thought this might be useful.

If you're on Vista or 7 it might be a permissions issue. Are you using MacroWorks II or 3, or do you have it programmed in hardware mode? If you are using MacroWorks, you need to run it as an administrator in order to send into ISBoxer (or any software that has admin powers).

A reminder that X-keys questions can be sent to tech@piengineering.com and we will answer as promptly as possible. :)

Amber McCormick
Senior Technical Support Specialist
P.I. Engineering