bpkdasbaum, Thanks and I added a section for the FJ Gear US-108 8 port sync KM in the 3rd post from the top.Originally Posted by bpkdasbaum
Thanks for the idea and I combined them (please let me now if it can be further improved).
If you have any new results please do NOT go back and update the above post and rather post them to the end of thread as seeing new posts is how I know new results are needing to be added...
soon update my experience, got from aliexpress shuOne 8x and a new entry MT-WiKi 8x, same aimos keys combo .
so can do some test for
shuone
aimos 4x and 8x
MT-WiKi 8x
anyone noticed issues with ctrl or shift combo not working?
or maybe it s depends by kb used?
After a number of unhelpful back and forth emails with Koolertron support, I believe I have accidentally figured out how to do proper key up key down macros with the Koolertron. All of my email exchanges gave me the sense that the person on the other end simultaneously thought I was an idiot while also assuming I knew some baseline knowledge about how the device works. It kind of drove me nuts.
This applies to the AIMOS 4 port and AIMOS 8 port.
Anyway, I say I discovered this accidentally because no where in the manual or in my emails with support did it ever become clear where the numbers for a key up/down "key value" should come from. When I specifically asked support this question I got this in response:
The parameter after the Keydown command is the row and column number of the key. To use the keyboard to enter the number, you can enter this parameter .
In retrospect this makes total sense. However at no point did this person say "use the row/column key position on the physical device". Hence my comment about "baseline knowledge" I mentioned earlier.
Last night I happened to notice the top of the pop up window you get when assigning a key type to a key. This is when I remembered the cryptic mention of "row and column number of the key". Seeing this finally made everything click into place for me:
As it turns out the "key value" part of macros refers to the physical key position on the device. The 44 key unit has 6 rows of keys with 8 columns of keys. So the top left key is key value 11. The last key in the top row is 18. Keys that take up multiple spots seem to be referenced by the first location they occupy. In my image below the black CTRL key is Key 51 and occupies spot 51 and 61. The "window" key in the bottom row is key 62.
To create a proper direct port swap macro on the Koolertron 44 key unit you'd need to bind one key for NUM* and five keys for NUM1 through NUM5. You'd probably want these out of the way because the macros themselves also need to be bound to keys.
Then you'd need to bind the macro for each PC swap key to 5 additional keys. You'd end up having to dedicated 11 keys up to attain a single button port switch for 1 through 5.
Here is one example of how that might look if the top row dedicated key 3 through 8 to the macros assignments. I'm not showing those keys but instead showing a macro that should swap to the port for PC1. Key 12 is NUM*, Key 21 is NUM1.
Given that you can turn sync on (NUM*+NUM0) with a single key in burst configuration mode, I'd recommend that so you can save a key if you do create direct port swap macros.
In closing, I have not actually tested these exact configuration. I did test a number of other macros that behave in a similar way. I do not want to dedicate 11 keys to direct port swapping on a keypad. I'm generally not turning off keyboard sync in combat with my current setup.
Last edited by Wootenblatz : 12-03-2020 at 11:13 PM Reason: Fixing Aimos sync hot key
Additional testing I've done:
Red Dragon K588-RGB: TenKeyless KB (named "Broadsword") - General device notes:
- There is no dedicated software for this keyboard but I was able to use the K587RGB-Pro software.
- G key macros recorded in hardware seem to store the key was pressed, as opposed to the output of that key. By that I mean a G key set to NUM* will play back as the USB HID value for NUM* and not just *.
GOOD - ShuOne: use the REC button to assign G keys to Sync On and direct port swapping. Direct swapping works with both of the ShuOne's WINKEY+# and ALT+# port swapping options. I used this keyboard for at least 3 weeks with my ShuOne and it was great.
OK- AIMOS 4+8: The device works and you can use the K587 software to record macros to the G-keys (not the case for all Red Dragon keyboards). The lack of a numpad means hardware recording of the AIMOS sync/swapping shortcuts requires software macros. Software macros stored on a G key played back unreliable for me. While I did not test the rebind approach I ended up using for the K586, it may work better (see below). If you do not care about recording AIMOS hot keys to the G-keys, you might consider this GOOD instead of OK.
Red Dragon K586RGB-Pro: Full size keyboard (named "Brahma Pro") with a similar layout to the 588 - General device notes:
- Dedicated software available but you cannot record software macros to the G keys
- Hardware macros seem to store the output of the key pressed instead of the USB HID value for the key pressed. A G key bound to NUM* will play back as *. NUM5 plays back as 5 and not NUM5. I could not find any resources for if this was a hardware limitation or some kind of toggle.
- Software macros bound to non-G keys play back by USB HID value and not output of the key. This keyboard seems to behave in the opposite fashion compared to the K588. Honestly, it baffles me they're so different.
(out of the box) OK - ShuOne and AIMOS 4+8: The device works as a keyboard. Pressing KM sync command hotkeys manually results in the proper behavior on the device. However, recording a KM sync hot key on a G key via a macro recorded in hardware mode did not work for me. For instance on the AIMOS a G key bound to NUM*+NUM2 would play back as *2 and the AIMOS would stay on port 1. NUM*+NUM0 would play back as *0 and Sync would stay off. This is what I am referring to with all of my "USB HID value vs output of key" talk is about above.
(minor macro rebinding) GOOD - AIMOS4+8, probably the ShuOne as well. I have this working great with the following changes:
- Create a hardware macro that maps the G1 to F1, G2 to F2, G3 to F3, G4 to F4 and G5 to F5
- In software record the port swap command for your KM sync to each of the Function keys. For example, F1 has a macro that issues NUM*+NUM1
- Pick one other "Regular" key to add a software macro to for Sync On. I used INS but any non-G key will do. You can bind this key to any of the G6 through G10 keys if you want.
Essentially you're turning the G keys into into function keys and then using function keys for macros. It works great so far. As I noted above this method may work for the 588 and the AIMOS but I did not test it.
Hey all. Like everyone else, I have set about running hardware mulktiboxing. I want to share my experience with the ShuOne switch and the Steelseries Apex Pro keyboard.
I wanted to use macro to easily press sync on and off. Unfortunately it was not possible to record Scroll Lock + Scroll Lock + 0 in the software program in windows 10.
I tried to record macro but when I pressed Scroll Lock it only recorded when I released the scroll button, ie up arrow. It should record the down arrow when I pressed the button and the up arrow when I released the button. But unfortunately it did not, it only recorded the up button which led to me not being able to record the macro to have sync on and off.
After 5 hours I figured out how to get around this problem.
This is how:
1. Press and hold ALT
2. Now press the Scroll Lock x2 +0
3. Release the Alt Button
4. Remove the Alt keys inside the macro.
5. Enjoy
Hope this helps. Will show with pictures below with the Steelseries own software for macros..
Picture 1: How it did look when i tried to record macro.
Picture 2: Workaround to make the macro work with ALT pressed
Picture 3: Now remove the Alt buttons, right click on it and remove so it looks like this
Sorry for my english.
Regards
The initial post at the top of the thread has been updated with everything up to this post. Thanks for submissions thus far and please post to the end of this thread any corrections or new submissions (or if I missed something above). Please link to original sources if from other threads/sites and I will try to include the links in the summary.
some update, reverting some of my initial impressions about Logitech 502 hero (and probably also for older 502).
after more testing can confirm Logitech 502 Hero works GOOD with AIMOS 8 ports (and probably with 4 ports version too):
- setup profile macro(s)/keybinds inside Logitech Hub software with mouse direcly connected on pc;
- in my tests i ve used macros like *+0,*+1 etc followed *+F9/*+F10. these macros with first combo change active pc and with second switch relative/absolute mouse state on AIMOS.
- lock profile, and then activate this profile on onboard memory . i removed all other profile leaving just this one.
add here manual for Logitech Hub usage.
- modern logitech items supports a powerful lua scripting with good API for complex tasks.
- i ve spent some time programming a loop sequence: bad news, these scripts looks like not working while mouse is working with onboard memory only outside Logitech Hub software.
- quit logitech hub and connect mouse directly to AIMOS and it now can sends input to AIMOS switch, repeat after enable memory onboad with that profile active.
- suggest to disable other onboard profiles to make possible use more buttons normally used for logitech profiles switch tasks.
after setup, used to levelling a team 50-51. make AIMOS switching flawless.
tested a bit AIMOS 8 ports in combo with another branded/called MTVIKI 8 ports, it uses same combo and has similar functionality.
my MT-VIKI has some defective usb cables, for the rest it works similar ot AIMOS
not sure if it s same chip, but about AIMOS OS shows as ASX68004 (its chip signature).
https://www.asix.com.tw/en/product/M...VM_SoC/AX68004
for MT-VIKI is generic composite usb controller.
use this post to ask a question about ShuOne:
weird fact, after some tests on PID mine cant be controlled anymore, tryed to reset, nothing. it seems now cant interact with any keyboard or keypad.
try to be clearer: looks like the commands sent to ShuOne bypass it and reach pc/s, no chance to get working anymore ScrollLock+ScrollLock+N etc etc.
i bought mine on aliexpress from china.
anyone got similar issue or has possible solution?
nvm!
solved with scrllock+scrllock+K and then scrolllockx2+R
Last edited by Prega : 12-14-2020 at 02:06 AM
Today tested Corsair K95 Platinum: worksGOOD with AIMOS 8p.
hardware macros working perfectly.
The initial post at the top of the thread has been updated with everything up to this post. Thanks for submissions thus far and please post to the end of this thread any corrections or new submissions (or if I missed something above). Please link to original sources if from other threads/sites and I will try to include the links in the summary.
today tryed to play with Corsair K95 platinum and ShuOne 8p. total failure.
simply, It s a BAD.
keyboard is powered, but no inputs bypass the km sync.
note: KB works if connected to aimos 8p connected to shuone, in this setup macros worked. to switch shuone ports too.
but after some testing in pc this chain produces unwanted output when used to send switch combos to shuone.
Posting Rules
Reply With Quote
Connect With Us