Low-cost fully macro-capable mechanical keyboard Cooler Master ‘CK550 V2’
The short version: The Cooler Master CK550 V2 mechanical keyboard is fully capable of macros, including mouse operations (e.g., right-click) and cancelling macros in progress. Though non real-time macros and mouse operations in macros are only possible by using the Windows-based configuration software, not by defining on the fly (unlike, e.g., high-end Ducky keyboards). A showstopper may also be the limit of about 200 key actions (roughly 100 keys) per macro, which prevents using longer macros (it may sound like a lot, but modifier keys are also counted, and several of my longest (and heavily-used) macros couldn’t fit within the limit).
The number of macros is probably limited as well, to 20 macros. So it can’t really be used as a separate macro keyboard, only (effectively) as a macro pad.
It has the feature of control of the timing of key and mouse actions, and this is normally only found in very high-end (commercial) keyboards. In particular, many other keyboards with macro capability only have real-time recording (macros are played back with the exact same timing there were recorded with, and this is too slow for any serious use).
However, like for Rapoo keyboards, it is let down by awful, awful documentation and software (for instance, wiping out configuration without any warning). The software also weirdly insists on updating both itself and the keyboard’s firmware to the latest version (it will not work at all if not everything is updated; though a workaround may be possible (blocking ‘renew.exe’ in the Windows firewall)). And if the update process fails in any way, it is not possible to operate the software. It also seems to require Windows to run on real hardware; a virtual machine does not work (see Appendix D).
After the horrible setup phase for macros and colours, I have tried to use the keyboard as the daily driver for several weeks on Linux without any major problems. The only one was a non-working Windows key; see below for details.
The keyboard
I found it on sale for very cheap for EUR 25 (incl. VAT). Usually there is a reason for such low prices, for instance, flaws or quality problems, like Rapoo mechanical keyboards. Or they are about to launch a new model or series of keyboards and want to clear out stock of the old one.
I have tested model CK-550-GKTR1-ND and it is likely covered by CK550 V2. “R” in ‘CK-550-GKTR1-ND’ is for a red (linear) switch, likely a clone of Cherry MX Red. They describe it as “TTC Mechanical Switch” and it is likely what “T” refers to in ‘CK-550-GKTR1-ND’. TTC is for Titan Tactile. And ND is likely for “Nordic” (Nordic switch layout). The previous series, just CK550, had different model numbers, e.g., CK-550-GKGR1 (probably “R” for “red” and “G” for “Gateron“). Despite the close name, CK550 and CK550 V2 use different configuration software.
The switches are probably TTC Golden Red v3 (43 g) or TTC Silent Red v2 (45 g), both 1.8 mm actuation distance. See e.g. TTC Switches Review and Complete Guide
Profiles
There are four completely independent keyboard “profiles” (configurations). Each profile has macros, key assignments (either simple key actions or macros), and individually settable RGB key colours. The keyboard lock state (none/Windows key lock/full keyboard lock) is also per profile (independent of each other, not a global state).
The four profiles are activated by Fn + 1, Fn + 2, Fn + 3, and Fn + 4, respectively. They are marked on the keys as “P1”, “P2”, “P3”, and “P4”, respectively.
Holding down the Fn key will make the current profile blink in white, for example, “4”.
Macros
Macros can be defined in two ways: “on the fly” (on the keyboard itself) and through the MasterPlus+ software. But the two types of macros can not be mixed and matched. In effect, a keyboard profile either has to use all “on the fly” macros or all software-defined macros.
It is not possible to read out the defined on the fly macros in the software; the software is complete blind to them.
Software-defined macros can be exported to text files (JSON) and this allows copying macros between profiles. But it is the entire set that is exported (it is not possible to export a subset). And any existing macros in the profile it is imported into will be wiped out without any warning… (See Gotcha 4 below.)
Note: The software completely wipes out any existing on the fly macros for a profile if any macro definition is done in the software (see Gotcha 2 below). This was also noted in this video (at 21 min 36 secs. For a slightly different keyboard).
On the fly macros
The setup of macros on the keyboard itself (not in the software), called on the fly macros, is not intuitive. The leaflet says “Fn + F11 Record Macro” and leaves it at that. After the (real-time) recording, stop and save the macro with Fn + Prt Sc (one of options for executing a macro). It then shows the currently defined macros, including the one just defined. But it stays in this special mode (until it times out after about 30 seconds), and it isn’t clear how the mode can be exited.
There isn’t any obvious way on the web site to get to the required information. Instead, a web search turned up MasterKeys Pro S/M/L – Quick Macro Recording Guide. The mentioned keyboard models don’t quite match CK550 V2, and it is written in broken English, but “Fn + Esc to save and exit” seems to work. There is also TastyPC’s excellent coverage in a video, from 15 min 15 secs (also for another Cooler Master keyboard, but it seems close enough).
In any case, the full procedure for CK550 V2 is:
- Fn + F11. All keys turn blue. Unless some macros are already defined (they will be red). We call this mode “blue mode”.
- Press the key to define the macro for.
- Start pressing the keys for the macro. The recording is in real-time, though the initial time before the first key press is not included in the macro (thus no stress!). Note: It must be more than one letter key. For example, KK or Ctrl + K are OK, whereas the single key K will be silently discarded, leaving the macro key undefined (not changed). Though, for example, a single tap on the Shift key is accepted (it is not known why there is a difference; perhaps a modifier key is always accepted, even if it is just a single tap on it).
- Press Fn + Prt Sc to stop the recording and save the macro (the other two options are Fn + ScrLk (“Infinite Macro Loop”; repeat the macro indefinitely (until the macro key is pressed again)) and Fn + Pause (“Repeat Macro”; repeat the macro while the macro key is held down), but there aren’t any real use for them outside of gaming). Fn + Esc during recording will stop recording and discard the macro; nothing will be saved or changed. The same if it times out after 30 seconds (Fn + ScrLk must be pressed for anything to be saved). Note: The delay between the last key press and Fn + Prt Sc will be part of the macro, but since the keyboard is not blocked while playing back the macro, it will be as if it is not recorded (thus no stress!); it is only important for the repeat modes (see below).
- It is now back in blue mode. A new macro can be recorded, using step 2-4. Or exit this mode by Fn + Esc (or wait for timeout (30 seconds)).
Note that it is a real-time macro; it is only as fast as one can activate the keys…
Note: The other two modes for a macro, Fn + ScrLk and Fn + Pause, are usually only useful for games (though there are occasionally automation scenarios where it is useful to repeat a macro, for example, loading a lot of content on a web page with infinite scroll). For the former, it can nominally only be stopped if pressing the same macro key or if a new macro is started (thus the macro cancelling workaround described below also works in that case). Also, since the delay before Fn + ScrLk is recorded, it is not useful for fast repeating (use the configuration software instead for defining such a macro).
Each “profile” has its own set of macros, so this could be used as a sort of mode. E.g., if the keys on the numeric key are normally repurposed as a macro pad, switching to another profile can provide the normal numeric keypad (though modes are problematic). Or there could be different set of macros in different profiles for different tasks.
To see which keys are defined as macro keys (for the current profile), enter the delete macro mode by Fn + F12. The defined keys have a red background colour and the rest don’t have any background colour. Exit by Fn + Esc. Alternatively, start with the procedure for recording with Fn + F11. Exit by Fn + Esc.
To delete a macro key (in the current profile), enter the delete macro mode by Fn + F12, press the macro key, and exit by Fn + Esc.
Here is a video demonstration for another keyboard for defining, using, and deleting an on the fly macro, but it seems to be the same as the CK550 V2 (there isn’t any real audio; mute the sound to avoid the irritating music):
MasterKeys Pro – On the fly Macro
Software-defined macros
That is, defined using MasterPlus+. Once the updates are done, etc., and MasterPlus+ actually starts, it is fairly intuitive to use. Macros are created by giving them a name, recording and then the timing can be adjusted. The macros are then assigned a key in another tab.
But see Gotcha 1, Gotcha 2, Gotcha 3, Gotcha 4, Gotcha 5, and Gotcha 6 below.
Mouse actions in macros
It is possible to include mouse actions (for example, to use in a macro that opens the link under the cursor on a page in a web browser).
But these can only be added by using the accompanying software (unlike Ducky). During macro recording, some mouse actions can be recorded, like left and right click. It is a hidden feature; it isn’t documented anywhere.
Alt + Tab in macros
Disclaimer: It is not known what happens if a messed up JSON file is imported. Be careful. Before importing, double and triple check. In any case, always make a backup of the current macros (by Export) before making any change to macros.
During recording of a macro, Alt + Tab will be picked up by Windows and MasterPlus+ will not see it… The workaround is to manipulate exported files with the macro definitions:
- Record Alt + F8 (usually harmless). Give the macro a descriptive name (needed for locating it in the exported file)
- Export. This will save the current macro definitions to a text file (in JSON format), with file extension .json. Give it a descriptive name. Note: this will export all macros
- As a backup, make a copy of the JSON file, e.g., by appending “_backup”
- Manipulate one of the two JSON files to use Tab (keycode 15) instead of F8 (keycode 64). Any text editor will do, e.g., Notepad on Windows.
Note 1: On Windows, the file extensions may have been hidden. And if opening from within Notepad, it will only show “*.txt” files by default.
Note 2: Don’t be fooled by one of the first lines containing the macro name (near “currentMacroName”). The actual definitions are further down; the macro name field is after the key codes.
Note 3: The field for the key code is “key”, and there are usually two to change, one for key press (near “event”: 1) and another for key release (near “event”: 0)
- Import the manipulated JSON file into the current profile. Note: this will wipe out any existing macros in the current profile, so be extra careful (see Gotcha 4 below)—there is still time before the import to make a backup (by exporting to a (fresh/new)) new file, if not already done.
Macros are limited to less than 100 keys
The maximum, at least when recording in the software, is 198 key actions, which usually translates to 99 keys (press and release). It is not known if the same limit applies to imported macro files (JSON format) and on the keyboard itself.
This is a severe limit. I have some heavily-used longer macros which are longer than this. Some of them includes typing out long strings of text, but there are some that don’t; they just do a lot in one step.
Regrets…
Once a macro has started there doesn’t seem to be a way to stop it. On some other keyboards, e.g. Ducky, with a macro capability, pressing any key will terminate the macro.
However, I found a way to cancel a macro in progress. See section “Cancelling a macro in progress” below.
Special macro features
The used keys in a macro blinks when the macro is executing. Neat!
Firmware update
As of 2023-01, a firmware update (from version ‘0320’ to ‘0400’) to the keyboard itself is offered.
RGB brightness
Pressing Fn + F8 once brings a bit of a scare… All light goes off, including in the macro modes and the Num Lock LED! It is still possible to define macros, but it is completely blind. Pressing Fn + F8 once brings the panic level one notch down (brings about dim light).
Using Fn + F8, there are five levels for all keys (incl. completely off), so the easiest way to get the highest brightness (the default) is to press Fn + F8 until the light go off and then press Fn + F8 four times.
Note that in all but the highest brightness the keys are blinking while in the macro modes…
More mode scares
Main modes, sub modes, etc.
Fn + F5 switches between 21 RGB lighting /modes of which some make the keyboard go completely dark unless a key is pressed. The easiest way to find back to the default (steady light with the same colour for all keys) is to press Fn + F5 until the game mode (by default, fixed colours for keys close to ASDW (is four times Fn + F5 from the default). Otherwise, it is the mode where you have set key colours individually) and then press 17 times.
Fn + F1 switches the current colour (or off) for the current lighting mode (if it applies to the mode). If Fn + F1 changes the colour to off then it will look like the current mode is broken… (if current colour applies to the mode).
For instructions on how to set the colour on the fly for individual keys, see section “Hidden features” below.
Reset one or all ‘profiles’
The leaflet says to use Fn + R to reset the current profile to the default (it is to factory defaults, “Static” mode and violet (red level 7, green level 2, and blue level 10 (highest)), but it doesn’t do anything. The trick is to hold the key combination for 5 seconds… The leaflet is way too terse. The 5 seconds is essential information for the user. Here are instructions for another keyboard model, but at least option 2 (the one described here) works.
All RGB settings, lighting modes, and macros will be reset to the default. The acknowledgment from the keyboard is blinking in white at about 1 Hz until the “E” key is lifted. After that, the light will be a steady bright violet (lighting mode Static) for all four “profiles” and all macros will be cleared.
Similarly, hold Fn + E for 5 seconds to reset all four profiles. It even works in the macro modes. The current profile will be set to the first one (corresponding to Fn + 1).
For some other Cooler Master keyboards, holding Fn + Right Alt for 5 seconds during powering up does the same as the Fn + E procedure. It is not known if this works for CK550 V2.
Key colours
The colour for all keys in the default mode is changed by Fn + F1 (but there are 20 other modes; see near “More mode scares”). There are eight possible settings (seven different colours and off. Warning: a thick Swedish accent…) – red, orange, dark yellow, green, blue, cyan, and violet (but not the same violet as the default). Or with more control by Fn + F2, Fn + F3, and Fn + F4, for the relative weight of red, green, and blues, respectively.
There are 10 levels for each, thus a total of 1000 colours. Thus to get the highest brightness for a colour, press until it goes off, and then press nine times.
In “reactive” lighting modes, some keys light up when a key is pressed. In these modes, both the colour for the key that lights up (called foreground colour) and the colour for the keyboard at rest (when none of the keys are pressed), called background colour (off (no RGB light) by default in those reactive modes), can be set. Note: On each key on the keyboard, there is still only one colour at a time; foreground colour and background colour is a concept for the entire keyboard. The current mode (for change) is indicated when holding the Fn key down; by default, that will be F6 that is blinking (foreground colour). In addition, if neither F6 nor F7 is blinking, then it means foreground colour does not apply in the current lighting mode (see Appendix C for details).
Which one is active can be set with Fn + F6 and Fn + F7, to foreground colour and background colour, respectively. If the mode does not change to background colour by Fn + F7, then it means background colour is not supported in that lighting mode.
Software
The software, MasterPlus+, is bloatware (320 MB download and 900 MB installed) and only runs on Windows. It is not known if it can be brought to work on a virtual machine set up under Linux (like for the software for Rapoo V700RGB and Rapoo V500 ). I couldn’t get it to work (I tried for a long time); it would exit during the software update process or just exit without saying anything, even after the firmware updating was bootstrapped by doing it on a real hardware Windows system first.
Here is what it is supposed to look like for macros (at 16 min 37 secs).
Gotchas
Gotcha 1 – 6 are for the software. The rest are for using the keyboard directly or otherwise.
Gotcha 1: Changes to macros are immediately saved to the keyboard, so don’t make any mistakes…
Gotcha 2: *** Destruction ***: Any change to macros for the current profile (or all profiles???) using the software clears all (destroys) all manual setup (on-the-fly) macros without warning… Manual setup macros are those set up on the keyboard itself. Manual setup macros are also completely invisible to the software; it is not possible to somehow import them into the software-setup ones (you have to start over all over again).
Is there any warning? No, of course not. It is Cooler Master (Rapoo is not much better). Can we trust Cooler Master to protect our data and our time? No, we can not.
Gotcha 3: Export of macros does not work on the selection, but it exports all macros. Thus, import also imports all macros, not just one.
Gotcha 4: *** Destruction ***: Import of macros into the current active profile overwrites all the existing ones (adding to was expected, especially if the macro names were different), without any warning, destroying definitions. Or in other words, it deletes all existing macro definitions before it adds the ones from the import file.
Is there any warning? No, of course not. It is Cooler Master (Rapoo is not much better). Can we trust Cooler Master to protect our data and our time? No, we can not.
Mitigation: Export macros for the current profile to a file as a backup before doing any imports.
Thus it is not possible to add a few macro definitions (and thus there isn’t any way to transfer macro definitions between profiles, except wholesale import). The best way is probably to designate one of the profiles to contain all definitions for all profiles, import to other profile, and then selectively delete unneeded macros in those profiles (to save space)…
Gotcha 5: Be default, the program does not exit when closed by clicking in the upper right (goes to the tray instead). This is confusing as then nothing happens if the program is attempted started again from the menus or from shortcuts. This can be turned off in the preferences to the right (“Minimize to tray on close”).
Gotcha 6: Using the software, Alt + Tab can’t be part of a macro as Windows intercepts it (is not recorded)—though there is a way to make it work described in section Alt + Tab in macros. And the software does not allow deleting only a key press or a key release (otherwise, say, Alt + F6 and Tab could be recorded and then the F6 part deleted in postprocessing). It does work with manually defined macros (on the keyboard itself), but they can’t be combined with macros defined in the software. See gotcha 2.
Gotcha 7: Pressing Fn + F9 will disable the Windows key. See “Non-working Windows key and context menu key” below for details.
Gotcha 8: Accidentally pressing Fn + F8 will apparently disable the keyboard RGB light.
Mitigation: Press Fn + F8 four times to get it back to the original state.
Gotcha 9: Accidentally pressing Fn + F1 may cause all light to go off (because there are seven colours and off).
Mitigation: Press Fn + F1 at least once to get some colour.
Gotcha 10: Accidentally pressing Fn + F5 may cause all light to go off (because it enters into a mode where only a key press will cause light). Or conversely, a light show will go off…
Mitigation: Press Fn + F5 a number of times to get back to the original mode. Nominally, that would 20 times if Fn + F5 was only pressed once. See near “More mode scares” for more.
Gotcha 11: Entering macro modes (Fn + F11 and Fn + F12) will not come with any visual indication if the current lighting mode is static (the default) and the colour has been set to blue (except that all three LEDs (Num Lock, etc.) comes on).
Mitigation: Escape the macro mode by Fn + Esc, choose another lighting mode by Fn + F5, so that entering and exiting macro modes will come with a clear visual indication.
Model used in the software
In most software of this kind, the definitions are stored on the computer and then (deliberately, under user control) transferred (written) to the keyboard. This software is different.
Everything is stored on the keyboard; there aren’t any definitions on the PC side (though the macros definitions can be exported (see below)). When MasterPlus+ starts, it reads the definitions on the keyboard while the program displays “initializing”. This can be seen as blinking of the four keys 1, 2, 3, and 4, in turn for the four profiles. And when a new profile to selected to be the active one, the RGB lighting changes as if manually selecting a profile on the keyboard with Fn + 1, etc.
Another way to think about it is that the software operates directly on the keyboard. Thus any change is applied immediately to the keyboard’s configuration. There isn’t any deliberate save action by the user (but also the risk of inadvertently change something).
It even works the other way around: When changing profile on the keyboard itself (with Fn + 1, Fn + 2, etc.), the software is automatically kept in sync. This can even be used as a shortcut, so it is not necessary to switch to the “PROFILES” tab in the software to change the active profile… Neat!
Macros can be explicitly exported as files (and backed up) and imported to another profile (or another keyboard). But this is not the case for colour settings and key assignments. Thus those stay locked inside the keyboard and must be done all over again when resetting one or all profiles (or for another keyboard).
Can we trust Cooler Master to protect our time? No, we can not. It is Cooler Master. The model used by other vendors are better in this regard: the configuration is stored on the computer and any number of keyboards can be configured. It is usually also possible to find the files where they are stored and thus transfer the settings to another computer (though Rapoo wipes out all definitions without warning if uninstalling the software).
Changes are made instantly to the keyboard and there isn’t any undo. It is advised to use exporting macro as a sort of undo (this is not possible to colour definitions); before doing anything, first save the current definitions (to be able to revert back if something goes wrong).
Hidden features
Hidden by virtue of the terse and incomplete documentation…
Mouse actions are actually supported in macros!
For instance, right click, left click and scroll (mouse wheel in the middle of a standard mouse).
This works by doing mouse actions, say right-click, while recording a macro. The recorded mouse actions will actually be executed when the macro is played back.
This makes it possible, e.g., to have a macro key which opens the link under the cursor on a web page (in a web browser), a very common operation.
Cancelling a macro in progress
Macros in progress are not cancelled when any key is pressed on the keyboard (like, e.g., Ducky keyboards), but we can take advantage of the fact that starting a macro will cancel the one in progress.
Thus, define a macro in the software, say, by name “cancelMacro”, record a tap on the Shift key (a harmless operation), and assign it to a key, say, “8”, on the numeric keypad. This will now effectively be the cancel macro key! It can be done similarly for on-the-fly macros.
It is possible to set the colour for each key on the keyboard itself!!
That is, it is not necessary to use the software to use any colour on any key independently. In the leaflet, it is cryptically called “Record LED backlight” and there isn’t any other information.
For this to work, it is necessary first to change the lighting mode to “Custom” (see below).
- By Fn + F5, change to the steady mode (if not already) where all keys are of the same colour. See also Appendix C.
- Press Fn + F5 four times. It should now be in the mode where (by default) keys “A”, “S”, “D”, “W” are red and some other keys in the left half of the keyboard also have a colour. All other keys are (by default) off.
- Press Fn + F10 to enter the mode for key colour changes. Let us call it paint mode.
- Set the current “paint” colour. Use Fn + F1 (to get one of the seven standard colours), Fn + F2 (red), Fn + F3 (green), and Fn + F4 (blue) as described previously. The Fn key will take that colour. This is the colour to “paint” with.
- Press one or more keys to “paint” them with the current colour. It toggles; if a key is already the current colour, then it is set to off.
- Repeat step 4 and 5 to set different keys to different colours. Note that changing to another colour saves the definitions permanently for the currently set keys. This was also noticed by ‘TastyPC’ in this very thorough video (and without any irritating background music) for a similar keyboard (from 13 min 18 secs)
- When done, to save the definitions, press Fn + the key for the current profile, e.g. “3”. This will also exit paint mode. Alternatively, change to another colour and wait 30 seconds… (for the timeout of the paint mode). The Fn key will go dark (blank/off) when exiting paint mode.
Note: Setting the colour for the key corresponding to the current profile, for example “3” for profile 3, has to be done blind as it is always off or bright white while in paint mode to indicate what the current profile is…
Bypassing the configuration software for the firmware update
For example, as the insistence on updating itself may fail. Or reverting to a previous firmware version (if the old firmware version has been saved off in time (as the method here only get the latest)).
Or for reflashing with the same version. E.g., if the keyboard has gone into some weird mode and the only way out is to reflash (the normal configuration software will not do it because it is the same version).
Get a standalone firmware updater from here (a direct download URL (CK550V2_FW_0436_0488_4.00_202110081032.exe.zip. Version 4.00, 2021-10-08T1032). Released 2021-10-08. MD5 hash value as of 2023-11: 4B0C33126D6B205694A937F4C07111AE). Though it isn’t clear if the firmware covers both ISO and US keyboard layouts. Or if there is separate firmware for each.
Note that the URL scheme extends to some other keyboards’ firmware supported by MasterPlus+:
- CK530 V2. A direct download URL (CK530V2_FW_0437_0491_4.00_202110061642.exe.zip. Version 4.00, 2021-10-06T1642).
- But not CK720 and CK721.
However, here is a directory of downloadable software and firmware for Cooler Master products. The text on that page are all in Chinese, but click on the downarrows to get a list for each category. For instance, the firmware for keyboards are in the fifth column (orange colour), with 111 items as of 2023-11-16. See Appendix E for further details.
A dump of a Cooler Master Portal installation (about 70 MB), with possible firmware in there (it is not known how safe this is). It is probably a Cooler Master Portal (not MasterPlus+) installation for CK550 (not CK550 V2). It is from a Reddit post. There is also an FWupdate.exe file which should be able to run independently from Cooler Master Portal. It is not known if it works for CK550 V2 (but there is the link above for that).
Blues
Non-working Windows key and context menu key
Other keyboards connected at the same time worked without any problems. Reconnecting the keyboard, changing USB ports, and changing operating system did not change it.
Reason: inadvertently pressing Fn + F9 (e.g., it is close to Fn + F10 for setting the colours on the keyboard) will invoke the Windows lock key feature.
Resolution: press Fn + F9 two times. Only pressing once will lock the entire keyboard… As there are three modes: 1) normal, 2) locked Windows key, and 3) locked entire keyboard. In the last two modes, exceptions are: 1) Fn + F9 to get back to normal mode 2) resetting the current keyboard profile by pressing Fn + R for 5 second (this will wipe out all keys colours, macros, and key mappings), and change to another keyboard profile).
It locks both Windows keys, even if, for example, the right Windows key has been remapped to a macro, say, to use the right Windows key as the context menu key.
There isn’t any clear indication that the keyboard is in one of these two unusual modes (unlike Caps Lock, Num Lock and Scroll Lock). This must cause endless confusion (and returned keyboards). The only indication of the mode is that F9 is blinking if the Fn key held down while the keyboard is in one of the lock modes. In:
- Normal mode (1): F9 is not blinking. Change to the next mode by Fn + F9.
- Window key lock mode (2): F9 is blinking in red. Change to the next mode by Fn + F9.
- Entire keyboard lock mode (3): F9 is blinking in blue. Change to the next mode by Fn + F9.
Thus, a more robust way to get back to normal mode is to hold the Fn key down and press F9 until F9 stops blinking.
This is way too subtle of an indication. The user is required to know that the Fn key must be held down. And two other keys are blinking at the same time (key “3” and key “F6” (depending on the lighting mode)), drawing attention away from key “F9”. And because a lock mode is unusual, key “F9” is normally not blinking when the Fn key is held down. And this mode indication is not documented anywhere.
Ringing sound
The whole keyboard rings for several seconds if buttoning out a key (in contrast to the actually keypress). This is especially noticeable when using the arrow keys, even after dampening with O-rings.
It isn’t specific to this keyboard. Thomas notices something similar for another floating key design (at 07 min 42). Even expensive keyboards have this annoying problem (hallo, Corsair!).
Conclusion
After the truly atrocious setup phase caused by missing or bad documentation and very badly-designed software, the much cheaper CK550 V2 turned out to nearly rival a high-end keyboard like Ducky Shine 7. I have now used it for many weeks as the daily driver (incl. heavy use of macro keys) without many problems.
The only real problem is the missing media keys. For example, to smash the mute button, especially for the very irritating, unbearable non-topical (not related in any way to the content), and **** way **** too loud so-called “background music” most creators of videos about mechanical keyboards think they are compelled to add throughout the video. Having to also use a modifier key (Fn) to mute (Fn + Del) doesn’t fly for such a commonly-used operation. Most of the keys on the numeric pad were already occupied by macro keys, so I repurposed the Pause button for mute, ScrLk for volume up, and Ins for volume down, though this isn’t ideal as the latter two are not on a straight vertical or horizontal line.
CK550 V2 is fully macro-capable, rivalling many very high-end (expensive) mechanical keyboards, incl. fully autonomous operation (for example, execution of macros is not dependent on any software installed on the operating system and this also works on Linux). Though the full functionality does require using Windows-based software for the configuration; after that, it is fully autonomous and works fine under Linux.
This capability (though not documented anywhere) includes incorporating mouse operations into macros. In this respect, it is better than the Rapoo V700RGB which is supposed to have it, but it is broken to the extent that it is unusable. It works in the Rapoo V500, but it is crippled by the missing numpad (to repurpose those as macro keys) and is thus only suitable as a pure macro keyboard (a macro keyboard in addition to the main keyboard).
For fast operation of macros it is required to install Windows software to adjust pauses in macros (the only way for any serious use of macro keys, especially the shorter ones). The definition of macros directly on the CK550 V2 keyboard only supports real-time recording, in contrast to, e.g. Ducky Shine 7, where the pause length can be defined for each keypress directly on the keyboard.
The Windows software could only be installed and operated on Windows running on real hardware (at least it couldn’t under Windows 10 Home on VirtualBox under Linux, in contrast to the Rapoo software), though it is bloatware (more than 300 MB download, nearly 900 MB installed (in folder C:\Program Files (x86)\CoolerMaster\MasterPlus. nearly 2,000 files and nearly 300 folders), and running weird Windows services (process ‘RENEW.exe’ (for checking for firmware updates? That phones home?)) in the background).
Another con is a missing context menu key (AKA menu key or application key); it ought to be possible to reassign some keys, e.g., assign the right Windows key to the context menu key or even rearrange the keys (so the context menu key is in the same physical position as on other keyboards; this is possible on many of the Ducky keyboards). A workaround is to use Shift + F10 or reassign the Windows key to a macro as was demonstrated in this blog post (but that leaves it in a different physical position compared to standard keyboards).
Another con, as mentioned, is the missing media keys (or a volume bar).
Another con is the atrocious software design, violating even the most basic of usability guidelines.
Appendix A: MasterPlus+ versions
Cooler Master is not very forthcoming providing information and download options for old versions of the MasterPlus+ software. This is essential for troubleshooting. For instance, a new version might have broken something, and a workaround could be to install a slightly older version than the current newest.
Here an annotated list of MasterPlus+ versions is to appear, including direct download URLs, date information, and other information.
Appendix B: Detailed information about the CK550 V2 keyboard
The CK550 V2 was released before 2021-08-01 and probably before 2021-04-02. Version 1.6.0 of the software supposedly supports it.
Some later versions: 1.6.1 and 1.6.5
The CK550 (not CK550 V2) was released before 2018-09-07.
YouTube:
- Cooler Master CK550 – Everything About This Keyboard Is Good. Published 2018-09-07. Note 1: This is the CK550, not the CK550 V2 described in this blog post (reinforced by mentioning the switches being Gateron). Note 2: This is an example of superficial review where only the glossy surface is looked at, not how much the PC software for the keyboard sucks.
04 min 43 secs: Demo of some of the 18 different lighting modes - A sound test. Another sound test (04 min 06 secs – 05 min 15 secs). Of the red (linear) switch in CK550 V2.
The 18 RGB modes in CK550 (21 in CK550 V2) are: steady mode (the default), Reactive Fade (05 min 13 secs), Custom (editable with software), Stars, ????, Colour Cycle, Breathing, Ripple, Reactive Punch (06 min 15 secs), Heartbeat, Fireball, Circle Spectrum, ????, Water Ripple, Rainbow Wave, Crosshair, and ????.
Physical characteristics
Text on the box
Note 1: Case is not the exact same (for readability)
Note 2: The claim of 16.7 million colors by setting them on the fly is not true. Only 1000 colors are available (using the Windows software is required to be able to use of 16.7 million colors)
Front: “Cooler Master. Make it yours. Mechanical RED RGB linear (sticker). CK550v2. Full RGB mechanical gaming keyboard and wrist rest. RGB 16.7 million colors. Make your gaming experience.”
Sides (includes some repeats from the front, but not listed here): “Pan Nordic keyboard layout” (sticker). CK-550-GKTR1-ND. EAN outside of U.S. and Canada 479512102022. Gaming keyboard. For more information, please visit www.coolermaster.com”
Back (includes some repeats from the front, but not listed here): “Mechanical switches: Durable mechanical switches rated for 50 million+ keypresses. RGB backlighting: Per-key LEDs with multiple lighting modes and effects to highlight all your dominating killstreaks” (!)
Further on the back: “Wrist rest: Low-friction cloth to keep you comfortable during long gaming sessions. 460x95x15 mm. Brushed aluminium design: Curved top plate, floating keycaps, and minimalistic design built with functionality in mind.”
Further on the back: “On-the-fly adjustment of settings: Utilize function combos to adjust settings on the fly or map 16.7 million colors and fine-tune macros in software. Hassle-free software: Map 16.7 million colors to any key, customize lighting modes, and fine tune [sic] macros. Package contents: CK550 V2 keyboard. Wrist rest. Quick start guide. System requirements: Windows 7. Windows 8.1. Windows 10.”
There is a small screenshot of the software, with the tab for colours active.
USB
The USB vendor ID is 2516 (hexadecimal) and the USB product ID is 0145 (hexadecimal).
PCB information
Printed on the PCB: in four lines, “CK550 V2 MO”, “Masterkeys_DIP_RGB105K” (no spaces), “Rev: 0.2 CK8856 RGB MO”, and “2021-04-30”.
There is an unoccupied five-pin connector near the microcontroller. Presumably it is a programming connector, likely with signals such as “SWDIO”, “SWCLK”, “GND”, and “V3.3”.
There are also two unoccupied jumpers, “SEL1” and “SEL2”. Presumably it is for telling the microcontroller about the variant of the keyboard, e.g., ISO vs. ANSI and perhaps RGB LEDs vs. white LEDs. Or could one of them be for putting the microcontroller into bootloader mode?
Appendix C: List of lighting modes
Notes:
- Custom is the only mode in which each key’s colour can be set to an arbitrary colour. It is the only real mode for most users (after getting past the demo phase), but it is important to know about the other modes as it is easy to accidentally change to another mode.
- Static is the default mode (e.g., as purchased and after resetting the current profile). As mode “Reactive fade” is similar, a robust way to get back to Static is to find mode “Breathing” (it is similar (but distinct) to Static (with a white colour)—the brightness varies (but the colour doesn’t)), and then press Fn + F5 13 times.
- Multilayer and Multizone requires setup with the software; they can not be set up on the fly. All colours for these two modes are off by default.
- The current versions of the keyboard firmware (e.g., version “0400”) have 21 RGB lighting modes, but some previous versions (e.g., version “0320”), had 18 RGB lighting modes, including what seems to be the missing, by some, Snake game mode (demo/explanation)… (the mode after Water ripple)
- Here is a demo of most of the modes (for another keyboard and the order is slightly different. There isn’t any audio of value, so the sound can be muted (and the very irritating background music avoided))
Switch to the next lighting mode by pressing Fn + F5.
- Static
- Rainbow wave
- Crosshair (by default, no lighting (blank) unless a key is pressed). The default colour is white, but it can be changed by the normal colour selection (Fn + F1/F2/F3/F4) when F6 is blinking with Fn held down.
- Reactive fade (similar to Static (by default, blue keys), but not when keys are pressed). The default colour is white (for the pressed keys), but it can be changed by the normal colour selection (Fn + F1/F2/F3/F4) when F6 is blinking with Fn held down. The blue (background) colour can be changed by switching to background colour mode with Fn + F7 and then use the normal colour selection (Fn + F1/F2/F3/F4).
- Custom (the only mode with individually settable key colours). Foreground colour does not apply in this mode (F6 is not blinking when Fn is held down.)
- Stars
- Snowing
- Colour cycle (different colours, at the same brightness)
- Breathing (varying brightness, in the same colour). The default colour is white, but it can be changed by the normal colour selection (Fn + F1/F2/F3/F4).
- Ripple (by default, no lighting (blank) unless a key is pressed). The default colour is white, but it can be changed by the normal colour selection (Fn + F1/F2/F3/F4).
- Reactive punch (by default, no lighting (blank) unless a key is pressed). The default colour is white, but it can be changed by the normal colour selection (Fn + F1/F2/F3/F4).
- Heartbeat (by default, no lighting (blank) unless a key is pressed). The default colour is white, but it can be changed by the normal colour selection (Fn + F1/F2/F3/F4).
- Fireball. Explanation/demo. (by default, no lighting (blank) unless a key is pressed). The default colour is white, but it can be changed by the normal colour selection (Fn + F1/F2/F3/F4).
- Circle spectrum
- Reactive tornado
- Water ripple (by default, no lighting (blank) unless a key is pressed). The default colour is white, but it can be changed by the normal colour selection (Fn + F1/F2/F3/F4).
- Off. Foreground colour does not apply in this mode (F6 is not blinking when Fn is held down.). Note: On a keyboard with an earlier version of the firmware, the keyboard appears to be in a weird mode: five keys in a column or row blinking in red and blue. And a single key in steady green… But it is not a weird mode; it is the snake game mode!
- Rain
- Multilayer (by default, no lighting (blank)). Foreground colour does not apply in this mode (F6 is not blinking when Fn is held down.)
- Multizone (by default, no lighting (blank)). Foreground colour does not apply in this mode (F6 is not blinking when Fn is held down.)
- System status. Foreground colour does not apply in this mode (F6 is not blinking when Fn is held down.)
Appendix D: Virtual machine attempt
Like for Rapoo, it was attempted to run the configuration software under Windows 10 Home under VirtualBox under Linux.
USB for the keyboard must be allowed through. Instructions for VirtualBox and the freely available Windows 10 Home:
- KKKK
- EEEE
- AAAAAAAAAA GGGGG
Launching the software is seemingly blocked by a firmware update dialog, “NEW UPDATES ARE AWAILABLE, CK550V2 Firmware”, which is not possible to dismiss except pressing “Install” (not even with Alt + F4)… (or killing either process MasterPlusApp.exe or RENEW.exe). This is bad software design. There is an “Install” checkbox, but it isn’t at all clear when it is checked!!! This is also bad software design. One state is grey and the other is violet (the default)… Grey is probably off. For this option, it blocks with a dialog, “Please select install device”. So it seems it really, really, really, insists on updating the firmware…
If the application is started without an Internet connection it just hangs. MasterPlusApp.exe is started, but nothing is shown. After a few minutes it exits. This is even more bad software design.
If the CK550 V2 keyboard is not connected, the application just quits, without saying anything. This is scandalous!!!
When the updater is indirectly started by launching MasterPlus+, it seems to get confused by the presence of more than one keyboard; the OK button is dimmed. But even if only the CK550 V2 is connected, and the OK button is active, nothing really happens when pressed. The keyboard light switches completely off, but that is it. Fortunately the keyboard isn’t bricked by this process (so it probably hangs early in this process). Note however that the keyboard (for unknown reasons) must be disconnected for at least 10 seconds for it to come back to normal…
It was also tried to run the software with full administrative rights, but the result was the same.
This was tried with version 1.8.7 (current as of 2023-01-10).
This was tried at the same time:
- Reset all profiles by holding Fn + E for 5 seconds
- Disconnected all USB devices except a USB mouse
- Ran ‘MasterPlus+’ as administrator (from a shortcut on the desktop). The executable was ‘MasterPlusApp.exe’.
Process ‘MasterPlusApp.exe’ launched ‘RENEW.exe’ to display “New updates are available” which in turn launched ‘CK550V2_FW_0436… .exe’ after clicking “Install” (observed in Process Explorer). Note: “Install” can not be invoked with the keyboard. At this point the USB mouse can be disconnected. After pressing Enter (equivalent to clicking “OK”), all lights went out and not much else happened. Both CPU% and page delta for the ‘CK550V2_FW_0436… .exe’ process was at zero.
The USB mouse was reinserted and used to kill the ‘CK550V2_FW_0436… .exe’ process. Then the keyboard was repowered with a 10 second power off time (yes, for unknown reasons 10 seconds was necessary. For example, 8 seconds wasn’t enough), and the USB mouse was disconnected again. The RENEW.exe window was killed in Process Explorer (not dismissed with OK).
During installation of MasterPlus+, it shows “VC++ 2015 Redistributables”.
Differences between the two Windows 10 systems:
Acer has Visual Studio 2012 installed and thus probably different from the virtual one.
Gotcha 1: USB device version
In the USB passthrough settings in VirtualBox, the field “Revision” should be cleared. This is a VirtualBox thing, independent of the Cooler Master software.
For example, the field may contain “320” (for version 3.20) initially (the version of the keyboard as seen from the USB side at the time the USB filter was created), but if the keyboard is later upgraded or another CK500 V2 keyboard is used, the version may be “400” instead and will not match “320”.
The keyboard will still be able to be used for typing, but for advanced stuff, like upgrading firmware, it will be invisible to the Cooler Master configuration software.
If field “Revision” is made empty, it will match any revision number.
Appendix E: List of standalone Cooler Master keyboard firmware
As of 2023-11-16, from the directory (fifth item (orange colour); click on the down icon in it (on the right) to get the list):
- SK653 FW v1.03.00 (‘SK653_FW_0466_3.00_202106031032.zip’. MD5: TBD)
- SK653 BT FW (‘SK653_FW_0466_BT_v46_202103221044_rebuildForVid.zip’. MD5: TBD)
- SK653 BT FW v0.47 (‘SK653_FW_0466_BT_v47_202111121340_rebuildForVid.zip’. MD5: TBD)
- SK653 MCU FW (‘SK653_FW_0466_2.00_202105171338.zip’. MD5: TBD)
- SK653 FW v4.00 (‘SK653_FW_0466_4.00_202110181820.zip’. MD5: TBD)
- SK653 FW v4.03 (‘SK653_FW_0466_4.03_202111181116.zip’. MD5: TBD)
- SK652 FW
- SK652 FW v3.00
- CK351
- SK651
- SK631
- MP860
- MM310 MCU FW 0.10
- MM310 MCU FW 0.11
- MM310 MCU FW 1.00
- MM310 MCU FW 2.00
- MM310 MCU FW 3.00
- MM310 MCU FW 4.00
- MM311 MCU FW_V1.3.3_1.4.6
- MM311 MCU FW_V1.3.4_1.4.7
- MM311 MCU FW_V1.4.0_1.5.1
- MM311 MCU FW_V1.4.2_1.5.4
- MM831
- MM830
- MM71x. Is a subfolder, e.g. with MM710_MM711_FW_0393_402_5.01_202109131347.zip
- MM71x FW v5.00
- MM71X FW v5.01
- MM712 MCU FW_V2.3.8_1.4.7
- MM712 MCU FW_V2.5.0_1.5.1
- MM712 MCU FW_V2.5.6_1.5.2
- MM712 MCU FW_V2.6.0_1.5.4
- MM712 MCU FW_V2.6.2_1.5.5
- MM720
- MM720 FW v3.00
- MM720 FW v4.00
- MM720 FW v4.01
- MM720 FW v5.00
- MM720 FW v5.01
- MM720 FW v6.00
- MM720 FW v7.00
- MM730 FW v3.00
- MM730
- MM730 FW v2.00
- MM730 FW v3.01
- MM730 FW v4.00
- MM730 FW v5.00
- MM730 FW v6.00
- MM730 FW v7.00
- MM731 MCU FW 2.0.7_1.2.5
- MM731 MCU FW 2.0.8_1.2.6
- MM731 MCU FW 2.0.9_1.2.7
- MM731 MCU FW 2.0.9_1.2.8
- MM731 MCU FW 2.1.4_1.3.0
- MM731 MCU FW 2.2.7_1.4.1
- MM731 MCU FW 2.3.0_1.4.2
- MM731 MCU FW 2.3.1_1.4.3
- MM731 MCU FW_V2.3.2_1.4.4
- MM731 MCU FW_V2.3.3_1.4.5
- MM731 MCU FW_V2.3.4_1.4.6
- MM731 MCU FW_V2.3.8_1.4.7
- MM731 MCU FW_V2.5.1_1.5.1
- MM731 MCU FW_V2.5.6_1.5.2
- MM731 MCU FW_V2.5.7_1.5.3
- MM731 MCU FW_V2.6.0_1.5.4
- MK850
- MH752
- GS750
- ControlPad5.0
- ControlPad7.0
- CK530
- CK530 V2 FW v3.00
- CK530 V2 FW v4.00 (‘CK530V2_FW_0437_0491_4.00_202110061642.zip’. MD5: 76D31DFA8ED24491D81B99B46A15C634)
- CK550 (‘CK550V2_436_2.00_US_EU.zip’. MD5: 4CA2D50C2808E3A1A4FF35BE71321CD2). Though the file name suggests it is for keyboard ‘CK550 V2’, not the original ‘CK550’ keyboard (CK550 is from a previous generation of keyboards, e.g. with other types of switches (Gateron)). There may be an error in the directory.
- CK550 V2 Rev
- CK550 V2 FW v4.00 (‘CK550V2_FW_0436_0488_4.00_202110081032.zip’. As of 2024-01-29: 1688883 bytes. MD5 4B0C33126D6B205694A937F4C07111AE)
- SK620 Black FW v1.00
- SK620 White FW v1.00
- SK622 SpaceGrey v6.00
- SK622 SpaceGrey BT FW v0.47
- SK622 Silver BT FW v0.47
- SK622 SpaceGrey FW v7.00
- SK622 SpaceGrey FW v7.02 (‘SK622_Black_FW_0435_7.02_202111181124.zip’. MD5: 2E9FC316DA2C328650DC0A4FB1A4E4A2)
- SK622 Silver FW V6.00
- SK622 Silver FW v7.00
- SK622 Silver FW v7.02 (‘SK622_Silver_FW_0442_7.02_202111181124.zip’. MD5: 5D3E0DC59BD879F6E77366AEE735C0A2)
- CK720 MCU FW V0.11
- CK720 MCU FW V1.00
- CK720 MCU FW V1.02
- CK721 MCU FW v0.5.8
- CK721 Dongle FW v1.1.5
- CK721 BT FW v1.1.3
- CK721 BT FW v1.1.8
- CK721 Dongle FW v1.1.9
- CK721 DONGLE FW V1.2.2
- CK721 DONGLE FW V1.2.6
- CK721 DONGLE FW V1.2.7
- CK721 MCU FW v0.6.4
- CK721 MCU FW V0.75
- CK721 MCU FW V0.84
- CK721 MCU FW V0.85
- CK721 MCU FW V0.88
- CK721 MCU FW V0.89
- CK721 MCU FW V0.93
- CK721 MCU FW V0.94
- MK721_FW_V0.85
- MK721 MCU FW V0.88
- MK721 MCU FW V0.89
- MK721 MCU FW V0.93
- MK721 MCU FW V0.94
- MK721 DONGLE FW V1.2.6
- MK721 DONGLE FW V1.2.7
Appendix F: A look inside
This can be important after having poured coffee into the keyboard… E.g., for inspection and possible cleanup.
Or for looking into the feasibility of repurposing the keyboard with QMK. It may or may not be possible to disable or remove the existing microcontroller and replace it with a microcontroller. Though it is expected that the keyboard matrix is not close to square and thus something like an Arduino Micro will not do (it requires a 10 x 11 keyboard matrix for a fill-size keyboard).
Opening the keyboard
There are a number of small screws in the top plate, hidden under the keycaps.
There are 18 screws (self-threading/self-tapping) on the top plate, hidden under these key pairs (in-between the two keys). For the main part: F1/F2, F6/F7, F10/F11, PrtSc/Pause, Tab, E/R, U/I, Å/^, End/PgDn, Caps/Shift (left), under the spacebar (two screws), Context/Ctrl (right), and arrow down/arrow right. For the numeric keypad part: */–, +/Enter, and Del/Enter. Thus it is only necessary to remove those key caps, not all keys (though that could be an occasion to clean the keyboard…).
The 19th screw is under the warranty sticker (with the text “Do not remove”) under the left foot as seen from the top (under the Esc key). It is of a different type than the other 18 (a machining screw).
USB connector
Pin Colour Signal --------------------------- 1 Blue GND/Chassis 2 Black GND/Chassis 3 White D- Approx 0.1 V 4 Green D+ Approx 3.0 V 5 Red Vcc Only 4.52 V
Leave a Reply