You are browsing as a guest. Sign up (or log in) to start making projects!

Rishaan's RGB LED Micropad

Hardware
  • 1 Devlogs
  • 8 Total hours

The RGB micro is a 2 key macropad with a joystick, an OLED Display, and one RGB LED - giving the user multiple ways to change an LED to any color and brightness they want! This serves as the first PCB I have created and is a great introductory project to develop PCB, CAD, and firmware skills for engineering! I created this project to develop these skills and enhance my engineering skills and knowledge. I have used RGBs and their is a color game called hues and cues, and this LED allows you to access a pallet just like the game, but in real life! You can view more about this hackpad here: https://github.com/Rishaan-Dukhande/Micropad_RGB

Ship #1

I created my first micropad. It is an RGB LED controller. You can use the joystick and buttons to change the color and brightness of the LED. For advanced users, they can even change the saturation of the color, which is used to make a variety of even more colors on the color wheel. Through this project, I was able to learn PCB Design and foster my engineering passion. A few of the greatest challenges I faced were creating a case that fits the exact dimensions and components of the PCB and creating a PCB for the first time in general. I strongly encourage creating your own micropad with your own modifications!

  • 1 devlog
  • 8h build
  • 5.00x multiplier
  • 41 Stardust
Video of Project → See source code →
Open comments for this post

8h 12m 47s logged

Devlog 1 - Schematic Design

Since this was my first time creating a PCB, I took a lot of time to learn. Then I placed the following components in the schematic and wired them together:

    1. XIAO SAMD21
    1. 3 RGB LEDs
    1. Joystick module
    1. OLED screen
    1. Two tactile buttons

I decided to use connectors for the OLED screen and the joystick module for the wiring in the schematic.

Each RGB LED requires 3 resistors, so I added them to each column of pins (Red, Green, and Blue) and connected them to analog pins 2, 3, and 6.

Note: At this stage in time, I had no clue that I needed to use timelapse.

#Devlog 2 - First PCB Layout

Note from doing: This takes 2hrs for beginners, but watching the KiCad tutorial really helps!


3D visualization of PCB layout

In this session, I laid out all of the components from the schematic and imported them into the PCB editor.

First, I laid out all components onto the PCB in the design I wanted (shown in the picture above)

Next, I added a GND copper pour so I don’t have to route GND pins of every component.

Furthermore, I routed the PCB connections between the XIAO board and each component on the PCB.

Key Learnings

Vias

I learned that “vias” can be used to change the copper paths cut into the PCB from the front of the board to back of the board (2-layer PCBs).

Copper pours

Additionally, I learned that you can add copper pours (GND or 3V3) so that you don’t have to route some pins.

In this case, it was helpful because I did not have to wire the GND pin of every component, which would have added up to at least 7 extra wires.

Devlog #6 - Add OLED screen and joystick CAD models to fullCase design (Fusion360)

In this session, I added the CAD models of the OLED screen and joystick to create a file with the full CAD!

Tasks

Edited the PCB

I had to add the CAD of the OLED and joystick as footprints for the connectors in the PCB. The purpose of this is for the CAD import to fusion for the full CAD with the PCB and case. (This is not needed for the PCB manufacturing as only the connector holes are necessary on the PCB.

Import the PCB into CAD

I added the PCB into the CAD folder by importing it as a new file and inserting a derive. This is where most of the issues arose

Download and push to Git

I downloaded the full cad as a step file and pushed it to git for reviewers to see. I also took images which will be added to the Git Repo README in the next journal.

Issues

Height of case

Originally, the case was to tall and the LED, OLED screen, and buttons were not easy to use. These were the following solutions:

-1) Reduce the height of the
-2) Now the joystick didn’t git, so I made the hole bigger and added the wall (seen in @Joystick issue)

Joystick

-1) There was not a big enough hole for the joystick, so I had to pull out a joystick module and measure it with a caliper. I readjusted the opening on the top of the case to fit this.
-2) I added walls to the side of the joystick opening so the inner module could not be seen - for cleaner appearnce.

Key Learnings

CAD takes time, but it is easier if everything is measured before actually starting. This will reduce the time it takes and prevent errors - but never feel afraid of CAD!

1
0
17

Delete project?

Are you sure you want to permanently delete this project? This action cannot be undone.

All devlogs, followers, and associated data will be removed.

Followers

Loading…