Binder and additional hardware support

I'm a web programmer by trade I run my own business.  I don't know Lua but it seems easy enough to pick up, I write other scripting languages all day so... mostly php/javascript/bash.

That said I would really appreciate some help pointing me in the right direction, I just bought this keyboard and would like to make Binder work with it's macro keys:

ASUS 90YH0084-B2UA00 STRIX TACTIC PRO Gaming Keyboard
 

I bought it because it's a mechanical keyboard great for both gaming and programming with a ton of macro keys.

I don't really want to buy a logitech keyboard on top of that... and I'm a programmer so...

What will I need to enable this keyboard's compatibility or is that even possible without a ton of work?

If I understand it correctly (if not, Iryoku will surely correct me), you need to run this file, then press the buttons on your new device that you want to be recognized by Binder, then post the log file it produces somewhere we can get to it.

This file, actually. Otherwise do what arcon said.

Great thank you!  I'll run it as soon as I have my keyboard in a few days.

Ok guys I have the logs.  When I posted it was mid shipment, so sorry for the delay.

Here's the m1 to m13 log I think:

device[038609BF].log

\\?\HID#VID_195D&PID_2039&MI_02&Col02#7&101ff523&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030}
Type:		HID
Vendor ID:	195D
Product ID:	2039
Usage Page:	FF01
Usage:		FF00
Input Reports:	1
    ID: 02 [ V 56 Bits ]
Feat. Reports:	0

Data: 0208195D20390101
Data: 0208195D20390100
Data: 0208195D20390201
Data: 0208195D20390200
Data: 0208195D20390301
Data: 0208195D20390300
Data: 0208195D20390401
Data: 0208195D20390400
Data: 0208195D20390501
Data: 0208195D20390500
Data: 0208195D20390601
Data: 0208195D20390600
Data: 0208195D20390701
Data: 0208195D20390700
Data: 0208195D20390801
Data: 0208195D20390800
Data: 0208195D20390901
Data: 0208195D20390900
Data: 0208195D20390A01
Data: 0208195D20390A00
Data: 0208195D20390B01
Data: 0208195D20390B00
Data: 0208195D20390C01
Data: 0208195D20390C00
Data: 0208195D20390D01
Data: 0208195D20390D00

These seem to be when I use the fn + f1 to fn + f8 keys for macros

device[859D1127].log

\\?\HID#VID_195D&PID_2039&MI_01&Col07#7&27e38168&0&0006#{884b96c3-56ef-11d1-bc8c-00a0c91405dd}
Type:		Raw Input [Keyboard]

Key: 0070 Msg: 0100 MC: 003B Flags: 0000 Extra: 00000000
Key: 0070 Msg: 0101 MC: 003B Flags: 0001 Extra: 00000000
Key: 0071 Msg: 0100 MC: 003C Flags: 0000 Extra: 00000000
Key: 0071 Msg: 0101 MC: 003C Flags: 0001 Extra: 00000000
Key: 0072 Msg: 0100 MC: 003D Flags: 0000 Extra: 00000000
Key: 0072 Msg: 0101 MC: 003D Flags: 0001 Extra: 00000000
Key: 0073 Msg: 0100 MC: 003E Flags: 0000 Extra: 00000000
Key: 0073 Msg: 0101 MC: 003E Flags: 0001 Extra: 00000000
Key: 0074 Msg: 0100 MC: 003F Flags: 0000 Extra: 00000000
Key: 0074 Msg: 0101 MC: 003F Flags: 0001 Extra: 00000000
Key: 0075 Msg: 0100 MC: 0040 Flags: 0000 Extra: 00000000
Key: 0075 Msg: 0101 MC: 0040 Flags: 0001 Extra: 00000000
Key: 0076 Msg: 0100 MC: 0041 Flags: 0000 Extra: 00000000
Key: 0076 Msg: 0101 MC: 0041 Flags: 0001 Extra: 00000000
Key: 0077 Msg: 0100 MC: 0042 Flags: 0000 Extra: 00000000
Key: 0077 Msg: 0101 MC: 0042 Flags: 0001 Extra: 00000000

Hmm, it looks like the M1-M13 keys should be very easy to implement, but the F1-F8 macro keys just look like the standard F1-F8 keys... are you sure you were using them correctly? Could you delete the logs and make a new set just for the F1-F8 macro keys? Please zip up all of the logs and post them all, we might be able to find something in one of the other logs.

Hmmm ya I had to toggle the keyboard to macro mode for those to work here's all the logs zipped up! thank you!

Are you sure you pressed the buttons when you used the F macro keys? The file for that in the zipped folder is empty, unlike the original file you posted above.

In the meantime, can you see if this file already works with the M keys? The alias structure is as follows:

alias strix_tactic_pro_<button> <command> // To register button presses
alias strix_tactic_pro_<button>_up <command> // To register button releases

Here <button> can go from 1 to 16 and <command> is a regular Windower command. You can test it out by writing this script:

alias strix_tactic_pro_1 input /echo 1
alias strix_tactic_pro_2 input /echo 2
alias strix_tactic_pro_3 input /echo 3
alias strix_tactic_pro_4 input /echo 4
alias strix_tactic_pro_5 input /echo 5
alias strix_tactic_pro_6 input /echo 6
alias strix_tactic_pro_7 input /echo 7
alias strix_tactic_pro_8 input /echo 8
alias strix_tactic_pro_9 input /echo 9
alias strix_tactic_pro_10 input /echo 10
alias strix_tactic_pro_11 input /echo 11
alias strix_tactic_pro_12 input /echo 12
alias strix_tactic_pro_13 input /echo 13
alias strix_tactic_pro_14 input /echo 14
alias strix_tactic_pro_15 input /echo 15
alias strix_tactic_pro_16 input /echo 16

Yes I hit them, this first time the macro wasn't hit and I was holding down FN as I thought that was how it worked.  But I read and you have to toggle macro mode on for them to function.  So it shows up different the second time due to that.

I downloaded the dll and replaced the one in the plugins folder.  Upon loading it says it found my keyboard but I tried for about 30 min to get the alias to echo and I couldn't do it.  I used listaliases to ensure the aliases are there, I also bound other keys and used other aliases.  I even did

bind 1 strix_tactic_pro_1

and it did echo 1 so I know the aliases work.

Just when I hit the m keys nothing happens, thank you so far!!  I have uploaded another set of logs just in case.  The m14 to m21 keys show up just like the other m keys when the macro mode is enabled.

I just got it to work!  The keys aren't totally in the right order tho.  I think what was wrong was I had to downgrade my software the new one wasn't working.  I'm using version 1.4

Even the f1 and f2 key worked in macro mode!   the only thing is, m1 echo's a 2, m2 echo's a 3, and so on all the way up the line.  There is no m1 that I can tell.

m16 through m21 are not working and actually crash POL if you hit them.  (it is f3 to f8).

Thanks so much :>

Ok, same link as above, can you try again?

Also, do you think I should name the buttons strix_tactic_pro_mx instead of just strix_tactic_pro_x?

Unfortunately old Binder.dll or new I can't get it to work I'm trying to trouble shoot.

I think the m would be nice and clear   even if it's a bit of extra typing.

Edit:I'll try rebooting and doing more troubleshooting tomorrow, I found out that if I switch to my programming profile where I have escape macro'd to m13, that it isn't doing anything in ffxi.  it's like the keys never make it to the game for some reason.  I can open up vim and use m13 and it works just fine though to cancel out of insert mode.

Edit2: tried reloading 3 different times with diff profiles, and I'm not even able to make ctrl + v do a paste at the moment and that was working earlier today   FPS also won't show up unless I manually put the fps_position somewhere I know I can find it.... Switch lighting works tho.

Edit 3: Got the escape key to work by going to hardware mode and hitting save and restarting windower.  Paste works now too.  Macro keys still dont work.

This is strange… and not just the Binder thing, all of it oO

Can you try with this file? I've made some minor changes. Also, I renamed it to "stp_mx" now. for x from 1 through 21.

Hmm... you say you're binding stuff to the M keys in the profiler for the keyboard, but you shouldn't be doing that. Make sure there's a completely blank/defaulted mode just for FFXI. Also, what's "hardware mode"? It sounds like it causes the keyboard to translate the macro keys itself rather than notifying the profiler and having it synthesize macros in software, is that about right? If that's the case hardware mode will almost certainly need to be off, so that there's something in the USB data stream for us to read.

I've been messing around for another 45 mins trying to get binder finder to see the key presses.  It just won't now no matter what I do.

I feel like now that profiles have been saved in hardware mode, software mode just doesn't work :/  I can't get it to do anything.  Getting super frustrated I might have to contact their support.  I tried creating new profiles that are completely blank, and I had only ever bound one key to test.  I also tried lots of other things like simply making a new profile for software mode, and tying it to launch a program.  Nothing.  Whatever is saved to the keyboard in the on board memory seems to take precedence on all three profiles now and there's no way to "reset" it.  Hopefully I don't have to send the board back :/

Edit: I can't get software mode to work at all I made a support ticket with ASUS.  I can make profiles I can select software mode, but it just stays in hardware mode and unless I save any profile changes to hardware mode they never take effect.  This also disables the ability to lauch programs via a macro key and some other features hardware mode can't do.

Thanks for your hard work so far   I'll get this resolved as soon as I can and get back to you.  I will also try my other computer later today to try to see if it is a software issue.  I honestly think it's their software tho I think it was rushed out the door.

Edit 2: WOW ok, it's definitely a software issue.  On my laptop.  I just installed it on my desktop and it worked exactly how it is supposed to.  I don't have ffxi installed there so I can't test binder.  But I'll resolve the software issue on my laptop and get back to you.

I got the software mode to work again by uninstall version 1.05 and reinstalling version 1.04 i don't know why but this method seems to make it work again.  The macros and program launcher works.  And the binderfinder works again. 

The two most recent versions aren't working in FFXI.  I can get the first one that worked working (the one that when you hit m1 it echo's 2).

I did make 2 sets of aliases for both formats.  So I have all bases covered.  I tested over and over using unload binder and load binder and have them with different names binder2 binder3 etc.

Binder2.dll is what works it was the one given to me on 1/6 and is 408KB.  It's still off by one and POL crashes on f3 and up.

Thanks!

Both it being off by one and POL crashing on F3 and higher make absolute sense with that version. It not working with the latest version is what's not making sense right now Did you make sure to use the correct format? The short version "stp" and prepending an "m" to the number: "alias stp_m15 input /echo foo" for example.

Oh I didn't have the new naming on the latest file.  I fixed that loaded it again and same thing tho   nothing when I hit the keys.  the 1/6 version still works when loaded tho.

On the latest version only 21 crashed POL!  So progress on that front at least   Thanks man.  Really appreciate all your work on this.

I attached the logs to see if there's any variation.

Ok, new file here. It should fix the crash, other than that there are no changes to the code yet, so it should technically still not work, but it should now output the alias it tried to call to the console, so it might give us a hint of what's not working right.