Your keyboard may not be working yet, but we'll walk you through fixing that.
How To Use A Multimeter
Many of the troubleshooting steps require checking continuity with a multimeter. If you are not familiar with how to do that this video will demonstrate on several different multimeters.
My Computer Doesn't See My Clueboard
Before assuming your Clueboard is at fault, check the basics:
- Unplug the USB cable from the computer and plug into a different port
- Unplug the USB cable from the Clueboard and plug it back in
- Try a different USB cable
- Try a different computer with each USB cable
- If none of these seem to help, you will have to do more in-depth investigation. Contact us at email@example.com and we'll help you from here.
My Linux Computer Doesn't See My Clueboard!
Use lspci to look for your Clueboard:
$ lspci | grep -e Clueboard -e ATm32U4DFU
You should have 1 entry here. If you have no entries there is a problem with your MCU and you should post a self thread or email firstname.lastname@example.org for further help.
- Clueboard - Your PCB is flashed correctly and the MCU is working. The problem lies elsewhere.
- ATm32U4DFU - Your PCB has not been flashed with the Clueboard firmware.
My Mac Doesn't See My Clueboard!
Use the following steps to open the list of USB devices plugged into your computer:
- Click the Apple Menu, About This Mac
- Click the "System Report..." button
- Select "USB" from the pane on the left
- Scroll through the list of devices. You will find one of two things:
- Clueboard - Your Clueboard is plugged in and the MCU is working. The problem lies with the switches.
- ATm32U4DFU - Your Clueboard does not have a firmware and needs to be flashed.
- Neither - There is a problem communicating with your MCU. Open a support ticket or email email@example.com for further help.
The Characters That Show Up Are Not What I Expect
There are many possible problems here:
- Firmware misconfiguration
- Operating system keyboard layout
- Short between GND, a row, and/or a column
Start by flashing the default firmware. This will rule out firmware misconfiguration. If the default firmware works correctly you should investigate the firmware you are trying to load.
If it's still not working right, check your operating system's language settings. If you have changed those to Dvorak, Colemak, or a regional input like AZERTY, you will get those layouts instead of the QWERTY labels on the keyboard PCB. This is normal, and you can either leave it in this mode if you wish to type in that layout, or you can change your layout back to US to match the PCB labels.
The last possibility is that you have shorted something. With the keyboard unplugged use a multimeter to check all connections:
- Place your clueboard bottom-side up. Use a box or something to make sure that no switches are pressed down.
- Place one probe on one of the LED- pins on the board (these pins are all connected to GND.)
- Touch the other probe to each switch pad. If you find that any pin is connected to GND you will have to locate where this connection has been made. Examine all of your solder joints near this row or column.
- If none of the pins are connected to GND, you will have to look for a short between rows and columns. The most thorough way to test is to check each switch pin one at a time. Essentially, you are going to repeat steps 3 and 4 only instead of touching GND, you will touch a particular row or column.
- Check each row against each column first, and then check each column against every other column.
- If you have made it this far and still haven't found the problem contact us at firstname.lastname@example.org and we'll help you out.