Click to view our Accessibility Statement or contact us with accessibility-related questions
hodyhong
6
Oct 3, 2017
I have got my kits a few days ago. Everything is fine until I have put everything together realise that the screws come with the kits are shorter (or the holes on the aluminum base are too big? ) I had to use my drill press to countersink the holes on the plate in order to close the keyboard properly. Another issue I have encountered is that there might be some issue with the key mapping. I have got the default mapping, for the middle layer, keys shift +";:" have become "+*" should be ":"".
For the lower layer, keys for "yuiop" have become "&'()0", should be "^&*()" keys for "jkl;:" have become "=~`{}", should be "_+{}|"
For the raise layer keys for "jkl;:" have become "-^@[]", should be "-=[]\"
I have refreshed the firmware with default, basic and other keymaps, same issue still occur. I have check my solder work they look fine too. Have anyone encountered similar issue or am I missing something?
Libbum
55
Oct 4, 2017
hodyhongWhat locale is your computer set to? If it's not en_US then things are going to be different.
hodyhong
6
Oct 4, 2017
LibbumYe, it is US alright. That's why I'm a bit confused.
Libbum
55
Oct 4, 2017
hodyhongHmmm, that is confusing. If you've re-flashed to default then that should fix any possibility of the wrong keymap installed on the board.
If all your keys are working, just displaying the wrong thing then doubtful it's the hardware side. Has to be configuration. What OS are you using?
hodyhong
6
Oct 4, 2017
LibbumI am using OSX Sierra. Everything is latest. I did refresh it to default or even to the basic layout. Same issue with the errors. I am not sure. Could it be the PCB has the wrong wire connected? Maybe I should hook it up with another computer and test it. It is just odd.
Libbum
55
Oct 4, 2017
hodyhongNo, it's not the hardware. You say that keys for "jkl;:" have become "=~`{}", which means your jkl;: keys are correctly connected and interfaced correctly with the computer. It's just the mapping to the alternate keys are off - which is entirely through software and configuration.
Testing on another machine is a good idea. Sorry, I'm not too involved with OSX though, so hopefully someone else can assist there. If the backend of the os works similar to most linux distributions these days though, it'd be useful to see the output of these commands:
locale setxkbmap -print -verbose 10
hodyhong
6
Oct 4, 2017
Libbumactually, the ":" should be "'" by default. So there is a fault there too. Interestingly though, I run locale in the terminal and the it returns the following
LANG="en_AU.UTF-8" LC_COLLATE="en_AU.UTF-8" LC_CTYPE="en_AU.UTF-8" LC_MESSAGES="en_AU.UTF-8" LC_MONETARY="en_AU.UTF-8" LC_NUMERIC="en_AU.UTF-8" LC_TIME="en_AU.UTF-8" LC_ALL=
Which means the locale is actually AU English instead of US. I got to investigate this. I would think it will be the same as the US English (and it displays in the system preferences as US).
Libbum
55
Oct 4, 2017
hodyhongHmm OK. Yeah, en_AU is not an issue (I use it myself). so that's not the problem. Keyboards in Aus are the same as keyboards in the US in terms of layout. So if you have a standard qwerty board and it's working fine with your machine I'd be fairly confident that your layout would be set to US (since there is no official Australian layout).
I don't know what the best option for you is from here. If it were me I'd just go in and swap the keys in the firmware. But perhaps contacting support here at massdrop, ask at the qmk issue tracker (https://github.com/qmk/qmk_firmware/issues) or the OLKB reddit thread (https://www.reddit.com/r/olkb/) might help you out without having to modify things directly.
hodyhong
6
Oct 4, 2017
LibbumThanks for your help mate. I did post in all the places already. So far haven't heard back. I guess I can attempt to program them to the "correct" way. It is just very frustrating with the imperfection. The worse, I can't even type underscore at all with this keyboard? So how can I program that! I guess it is part of the process.
Libbum
55
Oct 4, 2017
hodyhongGood luck! I hope someone else has a better idea of the issue. I saw (after I posted) that Jack has responded to you on the reddit thread. Hopefully he has the answer.
hodyhong
6
Oct 4, 2017
LibbumNo luck so far. There are speculation on the OS language, but it is fine. I need to test this keyboard on a PC somewhere. Appreciate all the helps and comments.
hodyhong
6
Oct 8, 2017
LibbumI finally got this resolved! Apparently Mac OSX has this set up progress for new keyboard, and it is for identifying your keyboard. Initially I couldn't get it to recognize my keyboard, it will some how select for you. I researched quite a few keyboard layouts online for different languages and realise my layout was set to Japanese for some reason! Now I have to go through the identifying process and at the end select US 101 keys and everything is back to normal! It was Mac OSX after all. Hope this is helpful for anyone who may encounter this issue.
PRODUCTS YOU MAY LIKE
Trending Posts in Mechanical Keyboards