NCHawk Posted January 17, 2016 Share Posted January 17, 2016 Hi, Just received a Strafe RGB Cherry MX brown keyboard model number CH-9000092NA and at this point I have been working for days to get it working at a BASIC 104 key keyboard level. :(: This keyboard replaces a working 104 key keyboard with zero issues, I wanted to upgrade to the mechanical Cherry MX switches (purely a luxury in this case). From the beginning... Hooked up the keyboard, I'm using USB 2.0 ports so I used two ports per the instructions. The keyboard lit up. My issues do NOT, at this time, involve lighting, so I do NOT wish to discuss lighting unless it is connected to getting proper key operation, my issues deal with BASIC 104 key operation. Unless the Strafe comes preconfigured in some form or matter (I read no info stating so) then I presume the keyboard should, upon being hooked up, emulate WITHOUT fail a BASIC 104 key keyboard BEFORE the CUE software is implemented and customization of any keys (or lights) ensue. I installed SwitchHitter to test EVERY key and key press to ensure BASIC operation. Regardless of test compatibility the Strafe FAILED this test. :sigh!: These following keys FAILED to respond as expected; the F7, F9, F12, the FN and Windows keys would NOT register a BASIC key press when pressed MOMENTARILY (a SINGLE key press). I found by mistake that if I pressed AND held the F7, F9, and F12 keys SwitchHitter would finally register a CONTINUOUS key press AND would continue to report the key as being pressed even AFTER being released. :confused: The FN and Windows keys did NOT respond the same, they NEVER register a key press in SwitchHitter regardless of either a momentary press or being pressed continuously. I have screen shots to show this behavior. I experimented (played around) with these issues. I use this computer for flight simulation and gaming (it is my gaming computer :D: ). Never let it be said a flight simulator won't put computer hardware to the test. While using the flight simulator I tried the above function keys as implemented in the simulator. The F5 through F8 keys control the flaps in my case, so I tried them. The F5 key worked as expected, the F6 key worked as expected, the F7 key FAILED, the F8 key worked as expected. Now, let me point out some interesting particulars about the F7 and F9 key operation. The F7 key as stated above, during a SINGLE key press did NOT respond in the sim (just as it would NOT respond in the SwitchHitter test described above). When pressed and held the F7 key registered in SwitchHitter as being constantly pressed (even AFTER being released). In the sim the flaps dropped completely per this trait in SwitchHitter, the F7 key acts as if it is being HELD down. Again, in the sim the flaps are expected to drop INCREMENTALLY for each SINGLE key press but in this case the F7 FAILS to register a single key press and only registers, when held down, as a continuous key press, hence the flaps drop completely instead of incrementally in sim. Now, the F9 key just like the F7 key does NOT properly register a SINGLE key press in SwitchHitter but will register a continuous key press exactly like the F7 key AND similar to the F7 key the F9 key is used for a TrakkerIR function I use with the sim AND a momentary key press IS REGISTERED because a set of lights that indicate the TrakkerIR is “paused” change states AS EXPECTED :bigeyes: . So SwitchHitter does NOT register a momentary key press BUT my TrakkerIR does register an F9 key press (something unusual here?)???? :confused: Again if I press AND hold down the F9 key SwitchHitter will register the key as being constantly pressed even AFTER being released (just like the F7 key). It is difficult to determine if a "constant" data stream (key press) is being sent to the computer such as a "stuck key" due to key rollover on this keyboard. SwitchHitter does NOT report this as such (I don't see multiple F9's being streamed to the computer :ummmm: ). I have concentrated my efforts to resolve the Function key issues because it would probably resolve my BASIC keyboard operational problems other than the FN and Windows keys but I have NOT made progress in my efforts. Anyone have any ideas or answers concerning these observations? As for the FN and Windows keys. I finally loaded the CUE software and found in the “Profiles” and “Performance” panes a check mark for disabling the Function key WHEN the Windows Lock key was activated. This was checked by default and by coincidence the Windows Lock was activated (the FN key was disabled in this case) “out of the box”. It would be BETTER not to disable such keys by default as this is NOT readily explained and I noted in reading various posts where the confusion ensued with many, I believe it is part of the issue surrounding the media keys (which in fact I have similar issues but will reframe from addressing that here as my priority is the misbehaving function keys). Even though the Windows key does NOT register within SwitchHitter as noted, it to registered in the operating system (similar to the F9 key traits) as the Windows menus appear when it was pressed???? :confused: A final observation, I looked for a “default reset” for the keyboard since it is controlled by firmware and processors, thinking this might help but none was to be found. Is there such a bugger for this keyboard, a button to reset it to a “basic” configuration to eliminate ANY possible corruption? Bottom line, this keyboard out of the box is impressive BUTTTTT without resolving the BASIC 104 key operation will render it a useless piece of junk and it will have to be returned. This keyboard “out of the box” should perform just like the 104 key rubber membrane keyboard I have used for over 20 years (literally true) WITHOUT issue. I realize this keyboard is more complicated (and hence capable) and I'm not trying to be critical here but BEFORE any customization is started this keyboard should “act” like a 104 key keyboard and that said I'm looking for any answers to these issues from the Corsair community at large. :feedback: Thanks Link to comment Share on other sites More sharing options...
This topic is now archived and is closed to further replies.