1
Circuit & PCB
Selected components under budget/size/power constraints. Designed circuit schematics, took the boards from pcb layout to fabrication and assembly.
ORBIT — MODULAR PRODUCTIVITY HUB
Control what revolves around you.
Orbit is a modular desk controller / productivity hub that explores physical controls, swappable input modules, and intuitive UI for tactile digital workflows.
LOADING MODEL…
01 / Overview
What is Orbit?
A modular productivity console designed to reduce distractions.
- Orbit provides dedicated physical controls for common digital interactions without pulling users into software menus.
- A central display offers quick-glance information, allowing users to stay aware without breaking focus.
- Swappable modules such as a dial and macropad adapt the device to different workflows and applications.
- The system combines physical input, embedded UI, and modular hardware into a single productivity-focused workspace tool.
Why Orbit?
Because small distractions add up.
- Checking notifications, switching windows, and searching through menus create micro-distractions that interrupt focus and reduce productivity.
- Most productivity tools live entirely in software, competing for attention on the same screen where work happens.
- Orbit explores whether dedicated physical controls can make interactions faster, more intentional, and less disruptive.
- By moving common actions to a purpose-built interface, users can stay focused on their primary task while still accessing essential tools.
02 / My Contribution
My contribution.
Orbit was a senior design project (SDP) built by a team. My work spanned the electronics, system design, mechanics, and software — this is what I specifically owned.
2
System architecture & I²C hot-swap
Defined the I²C event architecture linking ESP32-S3 modules to the Raspberry Pi host, including hot-swap attach-detach behavior under test.
3
CAD, 3D print, materials
Designed enclosures in Fusion 360 from PCB STEP files, 3D-printed using various materials like PLA for cases, PC for translucent underglow base and SLA resin for the keycaps.
4
Embedded software
Wrote ESP32-S3 module firmware to collect various user inputs(switches and encoders) and host-side event routing for Macropad and Dial modules in C/C++.
5
Integration, assembly, testing
Assembled and bench-tested modules, debugging the I²C bus, pogo-pin communication with a logic analyzer and scope and measured power draw of modules.
6
BOM, budget, documentation
Generated BOMs from PCB layouts, tracked budget against component choices, documented build decisions in the GitHub repository, recorded weekly meeting notes with faculty advisor.
03 / System Architecture
From module input to host action.
Modules read inputs and emit events over I²C; the host owns profiles, UI state, and output actions.
System architecture (Hardware Flowchart)
04 / Modules
What is Core, dial, and Macro.
Orbit separates processing from interaction: the core handles coordination and decision-making, while each module captures physical input and sends it back through a shared interface.
Core Module
Core Module
The brain of Orbit.
Runs the interface, manages connected modules, and keeps every interaction fast, synchronized, and context-aware.
Processing
Runs Orbit's UI, application logic, and profile management.
Module Coordination
Detects connected modules and routes every input to the correct action.
Context Awareness
Updates every module based on the active application and workflow.
Connectivity
Communicates with external services, devices, and FocusMode.
Expandable Architecture
Keeps peripheral modules lightweight while allowing new modules to be added without redesigning the system.
Dial Module
Dial Module
Continuous control without hunting through menus.
Designed for adjustments that benefit from precision and muscle memory.
Precision Navigation
Scroll through long documents, timelines, and code naturally.
Fine Adjustment
Control volume, brightness, zoom, brush size, and other continuous values.
Quick Glance
Integrated display provides contextual information without switching windows.
Application Profiles
The same dial performs different actions depending on the active application.
One-Handed Interaction
Frequently used controls stay within reach while your other hand remains on the keyboard or mouse.
Macropad Module
Macropad Module
Dedicated shortcuts for repetitive work.
Frequently used actions become physical buttons instead of keyboard shortcuts you have to remember.
Single-Press Actions
Launch macros, shortcuts, and automations instantly.
Contextual Layouts
Key mappings automatically change with the active application.
Visual Feedback
Display shows the current profile and available shortcut layer.
Workflow Acceleration
Reduce repetitive clicking and menu navigation during everyday work.
Custom Profiles
Create layouts optimized for productivity, creative software, development, or media control.
07 / Timeline
From concept to capstone.
How I took Orbit from an early product idea to a working modular system — defining the experience, selecting the architecture, building the hardware, and learning through each prototype.
STAGE / 01
Defining the Product
- Challenge
- Turn the problem of digital distractions into a focused and buildable product concept.
- What I did
- Sketched interaction ideas, created early CAD blockouts, reviewed comparable productivity tools, and gathered feedback from teammates, peers, and faculty.
- Outcome / Learning
- Narrowed the concept into a modular console built around dedicated physical controls, quick-glance feedback, and adaptable workflows.
1 / 3STAGE / 02
Proving the Architecture
- Challenge
- Choose a system architecture and components that could support modular input, embedded interfaces, and future expansion within the project constraints.
- What I did
- Evaluated components against size, power, cost, availability, communication, and integration requirements, then breadboarded the major devices and tested them with early firmware.
- Outcome / Learning
- Validated the core hardware choices and exposed integration risks before committing them to custom PCBs.
PROVING THE ARCHITECTURE
Breadboard test photo
STAGE / 03
Designing the Electronics
- Challenge
- Translate the tested architecture into reliable circuits for the core and input modules.
- What I did
- Read component datasheets, created and verified symbols and footprints, designed the schematics, and defined power, communication, input, and test connections.
- Outcome / Learning
- Produced an implementation-ready electrical design with reusable interfaces across the module set.
DESIGNING THE ELECTRONICS
Schematic capture
STAGE / 04
Building Manufacturable Boards
- Challenge
- Turn the schematics into compact boards that could be assembled, tested, and integrated into the mechanical system.
- What I did
- Placed and routed the PCBs around functional zones, connector alignment, ground planes, edge constraints, and test access; generated BOM and manufacturing files.
- Outcome / Learning
- Assembled boards through a mix of hand assembly, service-assisted production, and NeoDen pick-and-place and reflow, gaining experience across the full PCB build process.
STAGE / 05
Integrating Hardware and Form
- Challenge
- Create compact enclosures that protected the electronics while making each module comfortable and visually cohesive.
- What I did
- Imported PCB STEP models into Fusion 360, designed around the assembled boards, and iterated printed parts to resolve connector alignment, clearances, and interaction tolerances.
- Outcome / Learning
- Refined the physical system through fit testing, including resin-printed keycaps, a translucent underglow base, and the dial cap slip fit.
STAGE / 06
Bringing the System Online
- Challenge
- Make independently designed boards, firmware, connectors, and interfaces work as one reliable system.
- What I did
- Checked power and continuity, inspected signals with an oscilloscope and logic analyzer, traced pogo-pin bus failures, and isolated issues between hardware and firmware.
- Outcome / Learning
- Resolved communication and integration problems, improved the debug workflow, and brought the modules into a functional end-to-end prototype.
STAGE / 07
Testing the Product in Public
- Challenge
- Determine whether people could quickly understand Orbit, see its value, and interact with the system as intended.
- What I did
- Presented the working prototype to faculty, students, engineers, and community reviewers, demonstrated the modules, and collected questions and feedback.
- Outcome / Learning
- The response validated the modular productivity concept, identified priorities for the next iteration, and earned Faculty Choice — Third Place at the UMass ECE Senior Design Project Demo Day.
08 / Demo Day
Feedback & recognition.
Orbit was shown at the senior design demo day to faculty, peers, and the community. Below is real audience feedback alongside the recognition it received.
I wish I had this on my desk. During meetings or deep work, I get distracting emails all the time, and it is hard to tell what actually needs my attention.
I would use this in my dorm all the time. One Instagram notification can turn into scrolling, so having a physical device that keeps me focused makes a lot of sense.
The design looks professionally manufactured. I honestly could not tell it was 3D printed because the finish and form factor felt so refined.
This fits the way I like to work. I like having quick controls and a dedicated setup for staying productive instead of digging through apps.
I would get this for my kid. It feels like it could help students stay organized and avoid getting pulled into social media while trying to work.
The tactile feel is what makes it interesting. Most productivity tools are just software, but this gives you a physical sense of control.
Faculty Choice — Third Place, UMass ECE Senior Design Project Demo Day.
