Lab & Experiment Notebook
Welcome to my open workbench. Not everything I do starts as a structured project—this page tracks my ongoing hardware experiments, conversion scripts, reverse-engineering learning notes, playful breadboard builds, and the technical questions I am currently investigating.
Current Experiments
Multi-Buzzer MIDI Playback & Display Sync
Testing how two active buzzers and one passive buzzer behave together on a breadboard alongside a 1.3-inch AMOLED screen, a rotary encoder, two buttons, and two LEDs as part of my MIDI Breadboard Instrument.
RC Input & Vehicle Control Logic
Exploring how physical inputs on my Multi-Functional RC Controller and control logic for my RC and Autonomous Vehicle can be organized cleanly across hardware and software.
Hardware Experiments
Circuit Analysis & Breadboard Prototyping
Connecting classroom circuit analysis concepts to real breadboard setups—watching how physical components, buttons, encoders, buzzers, and indicator LEDs behave in practice.
Physical Computing Interfaces
Experimenting with tactile hardware inputs (rotary encoders and push buttons) and compact displays (such as a 1.3-inch AMOLED screen) to make embedded builds interactive without relying on a PC screen.
Software and Conversion Tools
MIDI-to-C Code Conversion Script
A custom script I wrote that takes MIDI data and converts it into C code for my breadboard instrument. It bridges higher-level musical data with low-level C arrays that the hardware can play directly.
C Programming & Future Language Exploration
Practicing C programming for embedded systems now, while preparing to study Assembly for deeper low-level understanding and expanding my toolkit with C++, Python, and Rust.
Reverse-Engineering Learning
I am learning reverse engineering and experimenting with reverse-engineering tools because I am interested in understanding how software and systems work internally.
- Tools I have experimented with: Cheat Engine, Ghidra, and x64dbg.
- What I tried: Investigating and configuring aspects of online game mechanics.
- Honest reflection: In some of these experiments, I used code generated with the help of AI tools and realized I did not yet understand every line of the underlying code. That realization motivated me to study C, memory concepts, and future Assembly systematically so I can read and verify what happens under the hood myself.
Unfinished or Playful Builds
I believe some of the best learning happens when building things that are unusual, playful, or simply fun. Playing MIDI melodies across two active buzzers and one passive buzzer on a breadboard started from that exact spirit—combining music, C code, and electronics just to see how far a breadboard setup can go.
Questions I Am Currently Investigating
How do C constructs map to Assembly and hardware?
As I study C programming and prepare to learn Assembly, how do compiled functions, memory layouts, and hardware registers look when inspected inside tools like Ghidra or x64dbg?
How can we use AI tools without losing deep system understanding?
What foundational knowledge across electronics, firmware, and software is essential so a builder can guide AI effectively, spot subtle bugs, and stay fully responsible for the system?