strafe rgb Key Issues with new Strafe RGB

[NCHawk]

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

[NCHawk]

Hi all,

 

I took the time to uninstall the CUE software and unplug the keyboard and plug it back up. No particular reason as I have no idea if that would help or not. All issues remain BUT one, the Windows key does register as a key press in SwitchHitter at this time. The Windows key was operational as reported prior, it just didn't register within SwitchHitter as a key press like the FN key. Also one MUST take notice of which WINDOW has "focus". Anyone who has been around computers understands what I'm talking about. If you have multiple windows open (as in multitasking) then you MUST put "focus" on the window that keys are to act on. Focus is not why the Windows key started working in my case, the only difference in this case is that I uninstalled the CUE software and unplugged the keyboard for a few minutes as stated. I'm still concerned I can NOT get the keyboard to return to a "default state as noted when I unpacked the keyboard and first plugged it in (when it showed red lighting and showed a hardware profile within the CUE software). I say this because the lighting scheme that displayed when I plugged the keyboard back in was one I had saved to the keyboard when exploring it's various options. Makes me wonder what "other" settings are being stored in the keyboard I'm not aware of possibly causing my issues? :ummmm:

 

EDIT: When I pulled this keyboard straight from the box and first plugged it in and installed the CUE software it did download a firmware update of some sort from Corsair's server. I wanted to try and download it AGAIN after my experience with my issues and tweaking this and that to return the keyboard to it's "pure" default settings but the server download is automated and recognizes the current firmware and rejects the update. There is a window to load a "file" and "force" a burn of the firmware but no file is to be found and I have read where others have tried to resolve this issue without luck. It might be something for Corsair to consider, to allow people the ability to flash the firmware to achieve a "pure" default state on the keyboard since the keyboard does NOT seem to come with that capability.

[NCHawk]

Okay, last update before I take my thoughts with me into the twilight zone (going to bed). I removed the Strafe RGB keyboard from my gaming computer and put it on my "other" computer. It is a Gigabyte EP45-UD3P with the same Intel Dual Core Q9550 processor only this system is still operating with Windows XP SP3 (this is my productivity computer). When the system powered up the keyboard, as expected, displayed the saved hardware profile for the lighting. I did NOT load the CUE software as I seem to remember it does NOT qualify for use on XP? Anyway, I did load SwitchHitter and I tested the keyboard on this system. ALL keys registered and worked as would be expected except the FN key. :D: So, it looks as if the keyboard is most likely operating properly and the issues reside with the Windows 7 Pro operating system on my gaming computer. :sigh!: So would anyone have any suggestions on how to isolate the issues described on my gaming computer? Any help would be greatly appreciated, thanks!

[Inheritance]

try using just one USB 2.0 port.

[NCHawk]

Thanks for the suggestion as I had NOT tried that because I'm using USB 2.0 ports and the instructions state I should use both ports in such a case. Regardless, the result was a no-go. The issue persists even on one port. After I tried the keyboard last night on a different computer (my Windows XP productivity computer) and found the keyboard to be pretty much fully functional, except for the fact I couldn't load the CUE software on the Windows XP OS, it dawned on me to try something else which is telling...

 

On the gaming computer (the one that has the keyboard issues described) I have removable hard drives setup in a RAID so I can run different operating systems on the same computer. This allows me to run older XP games without the fuss of trying to run them on a Windows 7 Pro system. It just didn't dawn on me to try my other RAID drives with a Windows XP OS on the gaming computer to see if the symptoms would change. So I tried it and found out that the EXACT problem persists. So at this point I'm inclined to believe there is some sort of hardware issue at play. The motherboard is an ASUS Rampage formula, FULLY updated with current drivers for the Intel chipset so I have no reason to doubt the USB 2.0 ports would be faulty straight off the motherboard, and I have swapped between ports (I have used different sets of ports straight from the motherboard). Unless there is some sort of BIOS setting causing a problem I don't know where to look next :ummmm: If it were plausible that a USB 3.0 card might solve the problem I would be willing to spring the cash for one but would like to get opinions on that before I start peeling out more cash to get this to work. BTW, the power supply in my system is a Corsair TX850W, which should be more than plenty for this system. Also, just to be clear on the EXACT issues still present, I have everything working as expected except for the following keys which consistently do NOT operate as expected: the F7, F9, and F12 keys, and the FN (Function) key. These still operate exactly as describe in my previous posts. Still need help. Thanks!

[Inheritance]

i would think its either a bios setting issue. or a USB driver/port issue. Do you know if any of the usb ports are controlled by a 3rd party chip?

[NCHawk]

Hi all, unfortunately I believe this problem is quickly coming to a close. Circumstances are coming to light as I investigated this issue further. As of today I have determined the following...

 

Since the Strafe RGB pretty much worked on my Gigabyte motherboard (my "other" computer) I was convinced there was probably a hardware problem on my ASUS motherboard (my gaming computer). It made sense to me later AFTER finding out the things I will describe. Corsair advised me to return the Strafe for replacement as I had just purchased it BUT the board tested good on the Gigabyte computer so I was reluctant to start spending money on shipping things back and forth (I did get this board on sale). Regardless, I decided for now to put my older keyboard back in place. That is when I discovered things were not all they seemed to be. The issue reared it's ugly head using my older keyboard, the EXACT same problem AND to make matters worse that keyboard uses a PS/2 port (not good!). I went up on the ASUS site and found a BIOS update that dealt with a different function key issue and gave it a try, BIOS now updated BUT it did NOT resolve the problem. I have inquired at ASUS about the issue. So I believe my problem now becomes a question of whether my motherboard has bit the dust, because it certainly isn't two bad keyboards and it certainly isn't the operating system because I have tried two separate operating systems via my removable drives that allow me to operate on either Windows XP or Windows 7 Pro, both having the same EXACT problem. That is clearly pointing to a hardware issue on the motherboard.

 

So unless someone out there is a bright computer engineer and has any other ideas that might be tried short of breaking out the soldering iron I guess there is nothing else to wonder about. Thanks for ANY additional comments! Cheers, Iven

[NCHawk]

Unbelievable!

 

Only one other thing I had not tried up till this point and I wasn't holding my breath thinking it would make any difference BUT just the thought of having to change my motherboard out was making me sick, so...

 

I took my computer out to the woodshed (my shop) and put it to the compressor for a good cleaning. Cleaned out the dust, the dead lady bugs (they were bad this year) and probably some old crumbs from who knows what.

 

She is purring like a cat. All keys are working as expected with SwitchHitter giving everything a thumbs up. So lesson learned, start by cleaning everything up, doing a little preventive maintenance and maybe things won't act so weird!

 

Sure beats paying hundreds of dollars because of a spec of dust :eek:

[Corsair Henry]

Unbelievable!

 

Only one other thing I had not tried up till this point and I wasn't holding my breath thinking it would make any difference BUT just the thought of having to change my motherboard out was making me sick, so...

 

I took my computer out to the woodshed (my shop) and put it to the compressor for a good cleaning. Cleaned out the dust, the dead lady bugs (they were bad this year) and probably some old crumbs from who knows what.

 

She is purring like a cat. All keys are working as expected with SwitchHitter giving everything a thumbs up. So lesson learned, start by cleaning everything up, doing a little preventive maintenance and maybe things won't act so weird!

 

Sure beats paying hundreds of dollars because of a spec of dust :eek:

 

Wow! who would have thought a bit of dust can cause this much problems. Glad you have it resolved and kudos to you for sticking to your experiment that it's not the KB.