Official website: qwertykeys.com Official Discord: discord.gg/owlab Official Instagram: @owlab_official

<aside> 💡 CLICK THE SMALL TRIANGLE TO EXPAND THE CONTENT INSIDE

</aside>

Table of Contents

Important

<aside> 💡 1. Testing Please make sure your PCB work as suggested in section 2.2 before building. Parts damaged during installation, such as the hotswap sockets, are not eligible for replacements. In case of defects, please raise a ticket in our discord server or reach out to [email protected].

2. FN key The key on top of the right arrow is FN or MO(1) - it will not register like other keys unless you turn on the TEST MATRIX Keychron has a very helpful page to help understand the function of VIA.

3. VIAL Link 65 wired PCB is now compatible with VIAL. Please consult section 4 to flash the new firmware to make your Link 65 plug-and-play with VIAL.

4. VIA - VIA (usevia.app) ****As of now, customers still need to load the .json file settings - show design tab - design - turn off v3 definitions - load draft definition) if they wish to edit the wired keymap in VIA - we are waiting for VIA to approve our Pull Requests.

Please note that as we encourage the use of VIAL software. Some functions such as macros may not be fully functional in VIA due to their incompatibility with each other.

</aside>

<aside> ‼️ **PLEASE DO NOT ROLL YOUR PCB for any purpose - malfunction caused by mishandling may not be repairable.

Please use screw-in stabilizers - adjust clip-in ones would damage the ribbon cables/**

</aside>

<aside> ‼️ For HOTSWAP PCB, Always support your socket firmly from the back (S area) while you’re installing switches. Failure to do so can result in your hotswap socket being pushed off its pad on the PCB (X), rendering it unusable. Based on your soldering knowledge, you may attempt fixing it at your own discretion. Owlab and all of our vendors will not replace parts damaged by customers with mishandling.

Hotswap PCB that is no-longer functioning because of the socket issue

Hotswap PCB that is no-longer functioning because of the socket issue

</aside>

1. Content check

2. Preparation

3. Build

4. Firmware & Troubleshoot