*Help* Screw in stabilizers not fitting in Dropshift V2 keyboard
I'm trying to build a mechanical keyboard with screw in stabilizers, I've build some mechanical keyboards with click-in stabilizers, never with screw in. Somehow one of the pins of the metal top-part collides with the screw in stabilizer of the numpad "enter key". I already tried grinding of a bit of the pin that collides with the stabilizer, but unfortunately I can't make it fit/close properly. You can see that the pin of the toppart leaves a mark on the bottompart of the stabilizer, see picture 2. What am I missing? Using Durock V2 in a Dropshift fullsize V2. See pictures below, thanks in advance!
Apr 23, 2024
Unfortunately, I use a Macintosh. Online sources hint that it works with a Mac, but it's only outputting upper- and lowercase letters and layer 0 punctuation for me.
Using the Keyboard Setup Assistant it was unrecognized, and I chose ANSI (I also tried JIS and ISO, the only other two choices).
Basically, when I do Fn+<, Fn+>, and Fn+Shift I see the LED colors, but the keys still just produce layer 1 characters.
Any ideas?
Also, when the firmware changes, would I need to update from a PC, since the files on the maker's website are .exe?
Edit:
Even though I cannot get any control+[whatever] keys to work, control+spacebar works to pull up the text input mode, allowing me to be able to input Japanese (as long as I don't need anything not on layer 0.
Also, Alt+spacebar will pull up Spotlight search.
Also, the three extra programmable layers are transparent, so to speak, until you program them - they all act like the default layer. For example the left spacebar will remain as such until you tell it to be something different.
Dont forget on a Mac everything is Command + <key>, so in the case of the Core you’ll want to use the Windows logo key as your Command key.
You also are likely already in need of updating the firmware - I received mine and it was outdated, so the the functions did not entirely match the keycaps which are designed with the new firmware in mind. You are likely running 1.03 when 1.04.03 is out. You will need to use Windows to flash the keyboard, or a VM.
good luck!
I'm not sure what my firmware version was, but I flashed it from my wife's Windows laptop using the latest Core firmware downloaded from vortexgear.tw.
My wife's Windows machine didn't particularly force me to go through any installation procedure as on my Macintosh. I noticed that even on the Windows machine layers 1-3 were not any different than layer 0, as you said.
On the Macintosh I reinstalled using the Fn1+n key, rather than the > key, as the "left of left-shift" choice, and it allowed me to continue and finish the configuration. Where did you get that tip? It's not something I would have figured out by trial and error.
The contro[i.e., Win]+<letter> keys, like control+F for Find are now working.
As for layers 1-3, I had assumed that for the keys identified as having assigned values in the "layer description" diagrams in the manual the values were pre-programmed. For example, I assumed that the numbers 1 through 0 would already be working. But layer 1 (red LED) "a" produces "a," not "2." So the layer does seem to be transparent as you say.
But what I cannot figure out is how, for example, to program the "a" key to be "2" in layer 1 when programming step 4 in the manual is "Key in the contents and press Pn." The contents I want is "2," but since the key is not yet programmed to be "2" I cannot key it in. It's a chicken-and-egg problem. What am I missing?
Edit:
I just discovered that the Fn1 key accesses the numbers and other "red dye sub" stuff on the keys, while Fn1+Shift accesses the "green dye sub" stuff. I'm still experimenting to figure out how to access the "blue dye sub" stuff. Edit 2: It's the Fn key to get the blue. O.K., I think I can begin to use this thing for real now!
I'm handling Japanese input by using Win+spacebar to bring up the keyboard menu and spacing between U.S. and hiragana. This is fractionally slower than having dedicated keys for this as on Japanese keyboards, but I don't mind.