V's Portfolio

This was a group project for a 24-hour hackathon, and our category didn't have a specific goal outlined. Therefore, we decided to make our project modular to be applicable across other categories at the event. After discussions, we established several goals: low cost, embedded systems integration, RF targeting for both commercial and private applications, and creating something we would personally use. With these criteria in mind, we settled on developing a modular Heads-Up Display (HUD).

Having experience in aerospace and being a hobbyist rocketry enthusiast myself, I've encountered various HUDs. However, I always wished for them to be more modular, offering additional features without complications. I often felt constrained in my ability to playback data and found it cumbersome to add new sensors to the data stream, decode appropriately, decide whether to decode on board or after receiving, and handle data compression. Consequently, we set out to develop a modular HUD capable of real-time sensor stream updates, producing accurate data while minimizing bandwidth usage. We chose LoRa technology for its support of longer ranges, compatibility with RF compromises, low barrier of entry, and high modularity.

Utilizing these concepts, we developed our LoRaHUD prototype using ESP32s with peer-to-peer WiFi communication and a GUI to demonstrate proof of concept. Unfortunately, due to the 24-hour time constraint, we couldn't obtain the proper LoRa hardware or have a device ready with accurate sensors for testing. Nevertheless, this prototype confirmed we were on the right track, and we plan to continue working on it, with the aspiration of eventually open-sourcing it.

Check it out yourself here!

In high school, I enrolled in an engineering design course with the aim of refining my skills in product development and gaining a comprehensive understanding of the entire product development process. As part of this course, we participated in the NASA HUNCH competition, where I engaged in two projects within a single year. Alongside my regular coursework, I was actively involved in designing a washing machine tailored for space and developing a lunar landing simulation. My goal was to have both projects run on a single Raspberry Pi, optimizing both my code and hardware usage to minimize costs and maximize reusability. Creating low-cost, high-efficiency computing solutions was crucial for accomplishing more within the limited space available, particularly important in environments like the ISS.

Safety was a primary consideration in the initial design requirements. I was instructed to incorporate approximately three factors of safety into everything we developed. This directive led to the implementation of innovative solutions, including using exposed low-voltage DC wires to test for water bubbles in space, employing magnets to close circuits only when doors were shut and serve as a hardware kill switch for UV lights, and reading motor resistances to verify their proper functioning. The system was optimized to run self-sufficiently in the background, utilizing only about two cores for interrupt-based I/O, thus leaving plenty of computing power for my other project—the lunar landing simulation.

The lunar landing simulation aimed to replicate the scenario of a package being dropped from a rocket orbiting the moon. It utilized data collected from "sensors" (manually inputted for our test purposes) to generate a simulation approximating the landing location of a package, assuming no space debris interference. This project provided a hands-on learning experience and allowed me to apply theoretical concepts to real-world scenarios.

Check it out yourself here!

This was a project I embarked on during high school, a period when my interest in game development peaked. With my growing proficiency in Java over the years, I was thrilled when my teacher encouraged us to create our own games if we wanted to play them in her class. I took up the challenge eagerly. Despite building several games that ran adequately, I noticed an oddity: I was achieving over 100 fps in games that didn't even require 30 fps, and they were heavily taxing all available processing cores. This poor design made running the games on a Raspberry Pi impossible, despite their lightweight nature. It was a wake-up call for me.

Realizing that relying solely on computational power was not the solution, I decided to delve into the development of proper game engines. This decision marked a turning point and influenced several future projects, as I aimed to optimize resource usage and enhance my skills in creating more sophisticated games.

Key improvements included implementing:

• A target FPS system
• Dynamic sprite sheet loading
• Dynamic camera rendering
• Optomized graphics displaying
• Entity handler
• Game states
• Dedicated chat box's
• New UI layouts allowing for graphics plus objects
• Dedicated render and tick methods, for graphics and math respectively
• Chat logging system
• Camera control system
• Music triggering system

Ultimately, my ambition extended to creating a 3D graphics engine in C++. Unfortunately, due to restrictions on my school-issued computers, limitations in Java's library access, and the absence of floating-point sine/cosine operations, I couldn't realize this goal at the time. However, years later, I successfully applied my mathematical concepts using OpenGL for a plugin to a CAD software, demonstrating that perseverance pays off in the end!

After developing numerous video games using my game engine, I felt it was time for an upgrade, and the natural progression was towards multiplayer functionality. With limited knowledge about network programming and armed only with Java at the time, I began by creating basic applications centered around local servers. These applications were hosted from the same machine that the client ran on. Through this process, I delved into multithreading and server/client applications. Which I used to craft basic headless "chat rooms" to experiment with sending strings over the air. Eventually, I refined this system to facilitate the exchange of JSON data bidirectionally.

Despite my lack of expertise in cybersecurity at the time, this project served as a valuable learning opportunity. While the system lacked protection against injection exploits and relied on a generic demodulator, the experience laid the groundwork for future projects. Subsequently, when I ventured into cybersecurity, I found myself at an advantage. My understanding of web servers and familiarity with server/client exploits, gained through this series of projects, proved to be invaluable assets in my cybersecurity endeavors.

I've recently ventured into the InfoSec/Cybersecurity realm. While I'm not as proficient in this area as I am in others, I began participating in local DEF CON groups to broaden my knowledge and learn from more experienced individuals. Upon joining, I noticed a significant need for BSides events in the area. Having heard stories of prior attempts to establish BSides in Houston and recognizing the growing interest among younger attendees, I saw an opportunity to bolster cybersecurity in the Houston area. Personally, even though I've had an interest in the field for some time, it would have been beneficial to know about local groups sooner, but fortunately I stumbled upon them eventually.

Therefore, I'm actively working to unite the local universities in the Houston area to support and organize BSides events here. This initiative aims to create a student-run but experience-guided BSides platform. Hopefully, this effort will address the challenges encountered in previous years. For the inaugural event, I took the lead, hoping to spark more interest among university students.

As part of my personal goals for this event, I aim to incorporate badges. Badges are integral to events like BSides and DEF CON. They not only encourage people to learn more and design their own badges but also serve as a gateway for individuals interested in PCB development. Badges provide a tangible item for attendees to take home, practice with, and further develop their skills, potentially uncovering unintended exploits.

For the badge design, I envisioned a Capture The Flag (CTF) style badge for several reasons. Firstly, much of my knowledge in InfoSec comes from CTFs. Secondly, it provides a low-pressure means of encouraging attendees to explore various aspects of the event. By associating scores with skills, people are motivated to engage with different activities, thus fostering learning and exploration. The codes to increase stats aren't simply handed out; attendees must earn them themselves.

Considerable thought went into the badge design. E-Ink displays were chosen for their affordability, ease of use, and minimal power requirements. Customization options for names and images further incentivize attendees to learn and explore on their own, as they can personalize their badges to their liking. Overall, the badges were designed with a focus on learning new skills, community engagement, customization, and ease of access.

Check it out yourself!

I never received a formal education in electrical engineering, but it was always an interest of mine. So, I made sure to learn it on my own whenever I could. Despite lacking a formal education in EE, I often felt intimidated by the idea of designing a PCB. While schematics were easy enough for me, the concept of creating a PCB seemed much more daunting. I told myself that learning PCB design would be essential for embedded systems/product development, which was the driving force behind this project.

Since keyboards aren't overly complex, I thought it would be a good first project to challenge myself. I made a list of goals, some focused on aesthetics and others on mechanics, all intended to deepen my understanding of PCB design. I chose to build this project around the Atmega32-U4, a chip I was most familiar with. I deliberately avoided using a pre-made board because I wanted to learn how to utilize specific chips and read their documentation, which was crucial to me.

One of my goals was to consolidate all electronic components onto one area of the PCB. Ideally, I envisioned adding glass around the final product so that each electrical component driving the keyboard would be visible. This required grouping the electrical parts together in an aesthetically pleasing manner. While organizing diodes was straightforward, routing the traces proved more challenging. I had to learn to work with a 4-layer PCB and understand vias, all while assembling the chip with its correct parts and sourcing components that were in stock, as I was still learning PCB design for the first time.

I completed the first revision of the design in about 2 hours on Eagle CAD, only to discover that EagleCAD had a paywall barrier. This led me to explore KiCAD, which I still use to this day. KiCAD is not only free but also open-source, aligning with my preference for open-source software. Impressed with KiCAD's capabilities and armed with knowledge from my EagleCAD experience, rebuilding the design in KiCAD was much faster and easier, taking about half the time. I learned a lot about PCB design rules, simulation, and creating custom components and linking objects in KiCAD.

Unfortunately, I never got to print the PCB due to the high cost. While it may have been inexpensive for a mechanical keyboard PCB, acquiring all the switches and optimizing for a case that I would have to 3D print would have been significantly more expensive. However, the skills I developed from this project have served me well in later endeavors, such as rocketry, drones, badge design, and more.

Check it out yourself here!

For the longest time, I couldn't grasp the fascination with custom keyboards. Despite mastering proper typing techniques and gradually improving my WPM, I remained oblivious to the allure of mechanical keyboard switches. It wasn't until a visit to my local MicroCenter when I finally experienced the tactile sensation of a mechanical keyboard firsthand. Suddenly, everything clicked into place. The more I explored the world of mechanical keyboards, the more I realized the potential for customization and enhancing my typing experience.

Thus, I embarked on my first keyboard build journey. Although I've constructed many keyboards since then, none have surpassed the comfort and performance of my Dactyl Manuform, and I doubt any ever will. Its ergonomic design, swift keystrokes, and enduring durability have firmly established it as my favorite keyboard. Throughout the build process, I acquired a wealth of knowledge about keyboards. While I had prior experience with soldering, this project provided an opportunity to upgrade to a high-quality soldering iron. Learning to solder with precision was initially challenging, but it taught me valuable lessons about embedded systems, HID devices, soldering techniques, and the Atmega32-U4 microcontroller, among other things.

Upon completing and flashing my homemade keyboard for the first time, I was captivated by the sense of accomplishment. Despite encountering challenges and troubleshooting issues along the way, the satisfaction of typing on a keyboard I had personally crafted lingered with me through subsequent keyboard projects.

As my typing speed dramatically increased since the inception of this keyboard, I've found myself gravitating towards quieter switches to facilitate faster typing. While I appreciate the auditory feedback of clicky keyboards, typing speeds exceeding 120 WPM require more focus on each keystroke. Consequently, my future plans involve transitioning to linear switches, a change I've already implemented on three of my other keyboards. This project not only deepened my appreciation for embedded systems but also ignited my passion for product development.

As I delved deeper into electronics, I encountered limitations in advancing without specialized equipment. This realization prompted me to explore specialty equipment, leading me to discover various types of gear. Among them, I recognized the necessity for a modular Power Supply Unit (PSU). While high voltage wasn't essential, precise amperage control was a useful feature as I started using batteries more. Additionally, the capability for variable voltages opened doors to experimenting with precision devices.

After thorough research, I came across the "UCTRONICS Step Down Converter." Essentially, it's a variable output step-down converter topping around 50V, equipped with voltage and amperage control. Despite not being exceptionally powerful or clean (switch-state), it has worked for reliably to this day.

Anticipating future ventures into custom drones, I prioritized incorporating a variety of adapter types, foreseeing potential needs. Some adapters, such as USB, operate at standard voltages, making their inclusion relatively straightforward.

This project served as a pivotal stepping stone towards more complex endeavors. While it may seem modest, it holds significance as a critical device I heavily rely on. A poorly constructed device would have impeded my progress and even posed risks to my educational pursuits.

InfoSec/Cybersecurity has always intrigued me, but reading about the extraordinary exploits discovered within CPU silicon that required a 10,000 X-ray machine to reveal made me doubt my qualifications for the industry. However, with some encouragement from a friend, I decided to dive in and give it a try. Participating in my first Capture The Flag (CTF) event seemed like a great opportunity to immerse myself in the cyber world, and I'm glad I did. Surprisingly, our team ended up scoring in the top 5% globally and top 10 in America!

During the event, I encountered a few challenges. Despite making some small mistakes, I was pleased with our performance. For example, there was a problem related to an Oscilloscope that required some out-of-the-box thinking to solve. Having prior experience with Oscilloscopes from my personal projects, I tackled the issue and quickly realized there was missing information regarding the LED's reading direction. Another challenge involved identifying the origin of an image, which I recognized as Czech architecture and language, allowing me to swiftly locate the street name using reverse image search.

Although I excelled in reverse engineering and RF, I only managed to secure one flag in each category due to time constraints. "Radio Hijacking" was straightforward, requiring basic SDR knowledge to understand the spectographic view. Conversely, reverse engineering proved to be a bit more challenging. However, after familiarizing myself with tools like gdb, radare, and ghidra, deciphering flowcharts and identifying expected outputs became manageable, leading us to success in one set of answers.

Challenges solved by me include "Insanity Check", "Not Just Media", "Sir Scope", "Czech Where?", "Radio Hijacking", and "The Johnsons". Full Write up avaliable below.

Full Write Up avaliable here!

Upon entering college, one of my initial endeavors was joining my university's rocket team. Rocketry quickly became a passion, and I eagerly sought to expand my knowledge at every opportunity. In my first semester, I assumed a leadership role and became the head of the avionics group. Around the same time, the club's leader expressed interest in reviving our hobby rocketry team, distinct from our competition-focused rocket team. Despite my extensive theoretical knowledge of rockets, I hadn't yet launched my own rocket. Seeing this as a valuable learning opportunity, I eagerly volunteered to lead the effort.

The club aimed to design the cheapest rocket possible to create kits with the lowest barrier to entry. Taking this goal seriously, I meticulously researched and selected each component, ensuring they would function together effectively. After getting the rocket painted by a friend, it was ready for launch. With a total cost of under $20 (excluding essentials like the motor, parachute, and flame blanket), it became the most affordable rocket in the lineup, costing nearly one-third less than the next cheapest option.

All eyes were on me as we prepared for launch day, eager to see if the budget rocket would succeed. To our delight, not only did it launch successfully, but it performed flawlessly, one of only three rockets to do so that day and the easiest to recover. Following this triumph, I assumed the role of chief engineer for the hobby rocket team, passing on the skills I acquired from our group rocket and leading others to successful launches. While this launch may not have been the most challenging or unique, it was a critical success for our university's hobby rocketry team, demonstrating that affordability doesn't equate to inferior quality. By utilizing the right materials and understanding the underlying principles, we proved that effective rocketry doesn't necessarily require a significant financial investment. Today, the rocket remains intact and ready for launch, having sustained no damage during its inaugural flight.

Upon entering college, one of my initial endeavors was joining my university's rocket team. Rocketry quickly became a passion, and I eagerly sought to expand my knowledge at every opportunity. In my first semester, I assumed a leadership role and became the head of the avionics group. Around the same time, the club's leader expressed interest in reviving our hobby rocketry team, distinct from our competition-focused rocket team. Despite my extensive theoretical knowledge of rockets, I hadn't yet launched my own rocket. Seeing this as a valuable learning opportunity, I eagerly volunteered to lead the effort.

The club aimed to design the cheapest rocket possible to create kits with the lowest barrier to entry. Taking this goal seriously, I meticulously researched and selected each component, ensuring they would function together effectively. After getting the rocket painted by a friend, it was ready for launch. With a total cost of under $20 (excluding essentials like the motor, parachute, and flame blanket), it became the most affordable rocket in the lineup, costing nearly one-third less than the next cheapest option.

All eyes were on me as we prepared for launch day, eager to see if the budget rocket would succeed. To our delight, not only did it launch successfully, but it performed flawlessly, one of only three rockets to do so that day and the easiest to recover. Following this triumph, I assumed the role of chief engineer for the hobby rocket team, passing on the skills I acquired from our group rocket and leading others to successful launches. While this launch may not have been the most challenging or unique, it was a critical success for our university's hobby rocketry team, demonstrating that affordability doesn't equate to inferior quality. By utilizing the right materials and understanding the underlying principles, we proved that effective rocketry doesn't necessarily require a significant financial investment. Today, the rocket remains intact and ready for launch, having sustained no damage during its inaugural flight.

Upon starting college, I found myself presented with a unique opportunity: my university's rocket team was recruiting! After successfully passing an interview, I joined the team for avionics. With plenty of experience in embedded systems, this subteam felt like the best fit for me. In just a semester, I absorbed knowledge about the entire rocket, not just my subteam, which led me to become the subteam leader for avionics.

During my time as a subteam leader, I spearheaded the development of a fully custom avionics system, which included a ground station, flight computer, modular sensor system, and a dedicated telemetry team. While most of the work happened under my leadership, I had to step back during the production phase due to studying abroad. However, I personally aided in three successful launches with zero avionics issues. I also created various safety features, instruction sets, decoding guidelines, and testing procedures, which are still in use by the team today. After I left, our custom avionics system proved more successful than the paid-for system we initially used. The commercial system lost connection almost instantly, while ours worked flawlessly, ensuring smooth operations throughout the missions.

After a semester I had already established the hobby rocketry team and constructed my own personal rocket. After which I got to lead our teams avoincs in spaceport where we secured 1st place in Texas and 15th overall, ranking 6th in our category—the team's best performance ever, I also took on the role of webmaster for AIAA-UH. Later, by the end of the year, I played a pivotal role in revitalizing the UH HAM club.

Throughout my time, I contributed to restarting two dead clubs and aiding one club in reaching its peak, with avionics systems even surpassing the quality of the versions we initially purchased!