To negotiate the best possible price for our customers, we agree to hide prices prior to logging in.
234 requests
Product Description
For keyboards in the popular 65% layout category, the competition is fierce. Entering the space with a convincing bid for the crown is Kezewa’s new Enter67 Keyboard Kit Read More
Share:
You Might Also Like
Angry Miao AM RGB 65 Mechanical Keyboard
$449
Drop + Oblotzky SA Oblivion V2 Custom Keycap Set
$20
CAPXXX Alert PBT Keycap Set
$35
Drop + MiTo GMK Serenity Custom Keycap Set
$99
Piifox Star Moon Translucent PBT Keycap Set
$50
Drop + MiTo DCD Banana Keycap Set
$25
The Eye Key Dragon Stars of Antarctica Artisan Keycap
Hey everyone, pretty excited about this particular launch. We've been working with the designers of the Enter67 for a few months to bring this to you.
I personally love this kit for a few reasons:
It sounds pretty amazing, the stock parts the kit ship with really help with that.
It feels really good - I really like the default polycarbonate plate, it's definitely pretty flexxy but with the different foams installed that is dampened a bit - the combination is excellent.
The gasket mechanism is great, it's super easy to put on and take off and fit really well in the case. It's also easy to swap on and off if you are trying new plate materials and builds.
The whole kit once built is nice and hefty, 65% layouts are one of my favorites and aesthetically it's just an excellent board.
Do check out the typing test we have posted on the page, I think this is one of the most affordable and excellent keyboard kits I've seen recently.
Looking forward to everyone's thoughts, comments and reviews once you get your hands on it. I think you'll find it as excellent as I did.
Hi everyone,
As many of You I've got "weird" PCB in my enter67 kit. One that has double caps lock support, side caps lock led placement and no VIA support.
Compiling default VIA firmware for this PCB enables VIA but disables RGB.
Solution form @Alliex is also not optimal as it uses RGBLIGHT (underglow RGB functionality) instead of RGB_MATRIX for per key RGB.
Because of above I was forced to write my own flavor of QMK firmware for this PCB.
Features:
VIA support.
Proper RGB_MATRIX implementation with all effects enabled.
Caps Lock indicato.
Link to source code on GitHub: enter67-rgbmatrix-VIA
If You want to try it out You can use QMK WSL with my qmk-firmware fork.
NoobensBarrichelloGood call! Thanks for updating and tagging me. I'm still learning the quirks of QMK/KMK/VIA/VIAL :)
I finally figured out to use RGBMATRIX while debugging a different keyboard (MF17) and haven't gone back to update this kb yet (to self: this is my reminder to do so)
----------------------------------------------------------------------------------------------------
However, for anyone wanting to use RGBLIGHT for doing a pseudo-'per-key' lighting based on layers, using the config.h in my other post, you can do something like this in your keymap.c:
const rgblight_segment_t PROGMEM my_fist_layer[] = RGBLIGHT_LAYER_SEGMENTS(
{1, 10, HSV_GREEN},
{13, 1, HSV_ORANGE},
{45, 1, HSV_RED},
{46, 2, HSV_BLUE},
{48, 2, HSV_PURPLE},
{50, 2, HSV_MAGENTA}
);
const rgblight_segment_t PROGMEM my_second_layer[] = RGBLIGHT_LAYER_SEGMENTS(
{1, 10, HSV_GOLD},
{25, 1, HSV_SPRINGGREEN},
{39, 1, HSV_TURQUOISE},
{53, 1, HSV_ORANGE}
);
//Later layers take precedence
const rgblight_segment_t* const PROGMEM my_rgb_layers[] = RGBLIGHT_LAYERS_LIST(
my_first_layer,
my_second_layer
);
void keyboard_post_init_user(void) {
// Enable the LED layers
rgblight_layers = my_rgb_layers;
}
layer_state_t layer_state_set_user(layer_state_t state) {
rgblight_set_layer_state(0, layer_state_cmp(state, 1));
rgblight_set_layer_state(1, layer_state_cmp(state, 2));
return state;
}
AlliexMy implementation for sure is not ideal. I also never worked with QMK in cases other than changing keymap.
But I'm looking more and more into QMK and ZMK (First time hearing about KMK!)
If someone is skilled in QMK then I would be glad for PRs with improvements!
At the end the goal is to get this keyboard working as advertised for everyones benefit. :)
So. As couple people already mentioned here. The board is decent although it doesn't work with VIA from the get go. However I've managed to flash new firmware on it with via compatiblity and rgb. The issue is that since then the ESC key RGB LED doesn't work correctly when board is in it's default state. If someone knows something about resolving this issue I would be thankful.
I don't know where the best place to put this, but it's not too bad to get this working with QMK/VIA and RGB. TLDR: The main thing you need to do is to create a profile with either VIA and/or RGB enabled from the community-sourced QMK keyboard for enter67 (which has neither by default, but does have a profile for VIA with no RGB). The RGB data pin is B15, and I think there are 69 LEDs (nice). n.b - I found this easiest to do through QMK WSL and also broke my copy of QMK MSYS in the process.
The keyboard supports bootmagic by default, so hold ESC when you plug in USB to enter the bootloader for QMK Toolbox or to flash otherwise.
You can use QMK WSL to set things up as you like, but I copied the 'via' profile to a new <username> profile and made a few edits.
Example rules.mk in my <username> keymap directory inside the enter67 keyboard directory (\\wsl.localhost\QMK\home\qmk\qmk_firmware\keyboards\enter67\keymaps\<username>\rules.mk):
BOOTMAGIC_ENABLE = yes # Enable Bootmagic Lite
VIA_ENABLE = yes
BACKLIGHT_ENABLE = no # Enable keyboard backlight functionality
RGBLIGHT_ENABLE = yes # Enable keyboard RGB underglow
ENCODER_ENABLE = no
Example config.h (same directory):
#define WS2812_DI_PIN B15
#define RGBLED_NUM 69
#define RGBLIGHT_LAYERS 2
#define RGBLIGHT_DEFAULT_MODE RGBLIGHT_MODE_RAINBOW_SWIRL
#define RGBLIGHT_DEFAULT_HUE 201
#define RGBLIGHT_EFFECT_CHRISTMAS
#define RGBLIGHT_EFFECT_RAINBOW_MOOD
#define RGBLIGHT_EFFECT_RAINBOW_SWIRL
#define RGBLIGHT_EFFECT_SNAKE
#define RGBLIGHT_HUE_STEP 8
#define RGBLIGHT_SAT_STEP 8
Then you can use the RGB keycodes on a layer or whatever you'd like. https://docs.qmk.fm/#/feature_rgblight
I hope this is helpful! Let me know if I left something out or should post elsewhere. :)
Replacement pcb socket for caps lock is upside down. also the replacement pcb usb-c daughter board and associated wire is different than the original
Still works just found it odd ¯\_(ツ)_/¯
FirstTimeKeebUserI have the revision with the upside-down caps-lock socket. I was able to get it working with VIA by grabbing the latest QMK, following the documentation, building with `qmk compile -kb enter67 -km via` and flashing the resulting firmware. No code changes were necessary. (Hold ESC while plugging in to get into DFU mode.)
For those wondering, the right ALT key is by default mapped as a layer switch, which is why it doesn't appear to work in a key tester.
I don't want the RGB, so I have not tried anything with that, but others have reported that flashing new default firmware will disable the LEDs
I just finished building my Enter67. No problems with it other than that when i try to configure it through VIA, after clicking Authorize Device and Enter67, the site doesnt update and i am unable to configure it. The key tester works fine tho. Could not find any firmware to flash it with or factory reset combination. Any work arounds?
Try JSON in this link and see if it works for you.
Right click and click save link as if you don't want to open it like it's a text file.
[MODERATOR NOTE]
Removed JSON link for now - reviewing issue with Kezewa.
Just in case, this is the V1 Enter67, not the V2. The V1 is $170 on Kezewa.com (probably because its in stock), while the V2 is on preorder for $139. The V1 only has gasket mounting, while the V2 also offers the option for a top mount. The USB-C cutout on the V1 is on the left, while on the V2 the connection is centered. The V2 also offers a choice of tri-mode PCB or wired PCB as well as thickness (1.2 or 1.6 mm), and with or without flex cuts; V1 only offers wired. Drop should have made the distinction with the product listing.
In our last email, we shared that the new ship date would be end of September 2023. Unfortunately, we're experiencing an extended delay and now expect to ship mid-November 2023.