Week 17 — Applications and Implications, Project Development

Requirements

This assignment focuses on defining the scope, impact and development strategy of the final project. It requires documenting the project vision, planned fabrication processes, materials, costs, evaluation criteria and communication assets that summarize the project.

Project Development Status

Project Overview

What will it do?

GameLab Controller is a handheld embedded systems educational laboratory designed to help students learn electronics, programming and system integration through a compact and interactive device. The project combines several common embedded systems peripherals into one platform, reducing the need for external wiring during the first stages of learning.

The device allows users to interact with inputs, read sensor data, visualize information and control external outputs from a single controller-like interface. It includes a display, joystick, buttons, LEDs, an IMU motion sensor, power management and GPIO expansion ports connected to an ESP32-S3 microcontroller.

GameLab Controller as a portable embedded systems learning platform.

Problem Addressed

When beginners start learning embedded systems, the first obstacle is often not programming logic but hardware setup. Students must identify electronic components, understand pinouts, create temporary circuits, connect wires correctly and debug mistakes before they can test even a simple example.

These initial steps are important, but they can also slow down the learning process and create frustration. A wrong connection, missing resistor, loose jumper wire or incorrect power line can prevent the activity from working, even if the program logic is correct.

GameLab Controller addresses this by integrating the most common learning peripherals into a ready-to-use platform. This allows students to focus on concepts such as inputs and outputs, sensor reading, graphical interfaces, timing, communication protocols and interaction design.

Educational Purpose

The purpose of the project is not to replace electronics learning, but to provide a smoother entry point. By removing some of the initial wiring barriers, students can first understand how embedded systems behave and then progressively move toward deeper hardware design and circuit development.

The controller can be used as a teaching tool for workshops, introductory electronics courses and Fab Lab learning activities. Its gamepad-inspired shape makes the system familiar and approachable, while the internal architecture exposes students to real embedded systems concepts.

Main Integrated Functions

Expansion Capability

In addition to the integrated peripherals, the system includes two independent GPIO expansion ports. These ports expose ADC and touch-capable pins from the ESP32-S3, allowing users to connect external modules and extend the platform beyond the components built into the controller.

Possible external modules include buzzers, relays, LEDs, analog sensors, servos and motor drivers such as H-bridge modules. This makes the device useful not only as a fixed learning object, but also as a base platform for future experiments and small embedded systems projects.

Expected Use Scenario

A student can begin by programming simple examples such as turning LEDs on and off, reading button states or displaying text on the TFT screen. Later, the same platform can be used to explore analog input with the joystick, motion sensing with the IMU, graphical feedback, power management and external device control through the GPIO ports.

In this way, GameLab Controller acts as a bridge between beginner-friendly learning activities and more advanced embedded systems development. It integrates multiple Fab Academy skills into a single portable educational product: 2D and 3D design, electronics design, PCB fabrication, embedded programming, system integration and packaging.

Existing Solutions and References

Before defining the final architecture of the GameLab Controller, several existing educational and embedded systems platforms were analyzed. The goal was to understand how current solutions approach electronics education, identify their strengths and limitations, and determine which features could be adapted to support a more accessible learning experience.

The research focused on three main categories: traditional electronics starter kits, integrated educational development boards and portable learning devices inspired by gaming platforms. Each category contributed ideas that influenced the design decisions made throughout the project.

Traditional electronics starter kits based on Arduino and ESP32 boards.

Electronics Starter Kits

Platforms based on Arduino and ESP32 starter kits are among the most common tools used to introduce students to electronics and programming. These kits typically include sensors, LEDs, displays, buttons and communication modules that can be connected using breadboards and jumper wires.

Their greatest advantage is flexibility. Students can build a wide variety of circuits and learn how individual components interact. However, this flexibility often comes with a steep learning curve.

Beginners frequently encounter wiring mistakes, incorrect pin connections and power distribution issues that can delay learning and create frustration before programming concepts are fully understood.

Integrated Educational Platforms

Educational boards such as Micro:bit, M5Stack and similar platforms reduce hardware complexity by integrating sensors, displays and input devices directly into the board. This allows users to focus more on programming and experimentation rather than assembly.

These systems demonstrate the value of providing a ready-to-use environment where learners can immediately begin interacting with embedded systems concepts.

While these platforms offer excellent usability, many are designed as general-purpose development boards rather than dedicated educational laboratories that combine interaction, sensing and expansion in a controller-style format.

Integrated educational platforms inspired the concept of reducing wiring complexity through built-in peripherals.

Portable gaming and maker platforms influenced the physical format of the project.

Portable Learning and Gaming Devices

Platforms such as Gamebuino, PyGamer and other handheld development devices demonstrate how game-inspired interfaces can increase user engagement while introducing programming concepts through interactive experiences.

These devices inspired the idea of using a familiar game-controller form factor as a learning tool. A handheld design can make technology feel more approachable, especially for younger learners and students encountering embedded systems for the first time.

However, many of these platforms focus primarily on game development, whereas the objective of the GameLab Controller is broader: providing a complete embedded systems experimentation platform.

How GameLab Controller Differs

The GameLab Controller combines ideas from all three categories. Like a starter kit, it exposes students to real embedded systems concepts. Like integrated educational boards, it minimizes wiring complexity by providing built-in peripherals. Like portable gaming platforms, it uses a handheld format that encourages interaction and exploration.

The main difference is that the project was specifically designed as a portable embedded systems laboratory. Rather than focusing on a single application, the platform integrates sensing, visualization, user input, battery-powered operation and hardware expansion into a single device.

By combining these elements, the GameLab Controller aims to provide a more accessible pathway into embedded systems education while maintaining the flexibility required for experimentation, prototyping and future development.

Sources and Knowledge Base

The development of the GameLab Controller was supported by a combination of technical documentation, hardware references, software development tools and knowledge acquired throughout Fab Academy. Since the project integrates mechanical design, electronics, embedded programming and system integration, multiple sources of information were required during different stages of development.

Rather than relying on a single reference, the project was developed using an iterative workflow where component datasheets, design software, fabrication constraints and previous Fab Academy assignments were combined to guide engineering decisions and validate design choices.

Technical Documentation

The primary source of information for the electronic design was the technical documentation provided by component manufacturers. Datasheets were used to verify operating voltages, communication interfaces, electrical limitations and recommended implementation practices.

These documents were particularly important during the schematic design, PCB layout and firmware development stages, ensuring compatibility between all integrated subsystems.

• ESP32-S3 technical documentation and pinout references
• ADXL345 accelerometer datasheet and I²C communication guide
• 1.8" TFT display controller documentation
• HW-373 battery charging module documentation
• Boost converter module specifications
• NeoPixel LED communication reference

Datasheets and technical references used during the electronic design and programming stages. Click the image to access the official ESP32-S3 DevKitC-1 documentation from Espressif.

CAD (SolidWorks), electronics (EasyEDA) and programming (Arduino IDE) tools used throughout the project.

Design and Development Tools

Several software tools were used to transform the initial concept into a functional prototype. Each tool contributed to a specific aspect of the development process, from mechanical modeling to electronics design and firmware implementation.

• SolidWorks for 3D CAD modeling and assembly validation
• EasyEDA for schematic capture and PCB design
• Arduino IDE for ESP32-S3 firmware development
• GitHub for project documentation and version control
• Fab Academy website infrastructure for documentation

These tools enabled rapid iteration and helped maintain consistency between the mechanical, electrical and software subsystems.

Community and Open-Source Resources

Additional support was obtained from the open-source hardware and maker communities. Examples, tutorials and implementation references helped validate hardware configurations, communication protocols and software libraries used throughout the project.

Community-generated content was particularly useful when integrating the ESP32-S3, TFT display and ADXL345 sensor, as these components are widely used within the embedded systems ecosystem and benefit from extensive publicly available documentation and example projects.

Knowledge Consolidation

Beyond the individual references, the most important source was the combination of all acquired knowledge into a single engineering workflow. The project required balancing mechanical constraints, electrical design, fabrication limitations and educational objectives simultaneously.

As a result, the GameLab Controller became not only a final project but also a demonstration of how the different disciplines explored during Fab Academy can be integrated into a cohesive and functional product.

Scope of the Project

The scope of the GameLab Controller was defined as the design and development of a portable embedded systems educational laboratory. The project focuses on integrating the most common learning peripherals into a single handheld device, allowing students to explore embedded programming, sensor interaction, visual feedback and hardware expansion without starting from disconnected electronic modules.

The project does not aim to replace advanced electronics prototyping, but to provide an accessible entry point for learning. Its purpose is to simplify the first interaction with embedded systems while still allowing expansion through external GPIO ports.

The project began with a simple hand-drawn sketch used to explore the overall concept and identify the key functionalities required for the platform. At this stage, the objective was not to define dimensions or technical details, but to visualize how the different educational features could coexist within a single handheld device.

Initial hand-drawn concept sketch of the GameLab Controller. This early design helped define the overall form factor, component distribution and educational objectives before moving to CAD modeling and electronics development.

What will I design?

Project Boundaries

To keep the project achievable within the Fab Academy schedule, the first version of the GameLab Controller focuses on the controller platform itself. The core objective is to demonstrate a complete integration of mechanical packaging, custom electronics, embedded programming and educational interaction.

Final Scope Statement

The final scope of the project is to create an independently operable handheld embedded systems learning platform that integrates 2D and 3D design, additive fabrication, electronics design and production, embedded programming, system integration and packaging into one complete Fab Academy final project.

Materials, Components and Bill of Materials

The GameLab Controller combines electronic components, fabricated parts and commercial modules. The following tables summarize the function of each main component and the estimated cost of the materials used for the project.

Main Components and Function

Bill of Materials

Processes and Fabrication Methods

The GameLab Controller was developed using a combination of digital design, electronic fabrication, additive manufacturing and embedded programming processes. The project integrates multiple skills acquired throughout Fab Academy and demonstrates how different fabrication workflows can be combined to create a complete embedded systems product.

Rather than relying on commercially available solutions, most of the mechanical and electronic subsystems were designed and fabricated specifically for the project. The following sections summarize the main processes used during development.

Computer-Aided Design

The development process started with the creation of conceptual sketches and CAD models. SolidWorks was used to design the controller enclosure, define internal component placement and validate assembly constraints.

The CAD workflow made it possible to evaluate ergonomics, battery placement, PCB clearances and accessibility before manufacturing the physical parts.

Electronics Design

The electronic architecture was developed in EasyEDA. Schematics were created to integrate the ESP32-S3, TFT display, IMU sensor, battery management system, LEDs and expansion ports.

PCB layouts were optimized to fit within the available fabrication constraints, ultimately resulting in two interconnected custom boards.

Electronics Production

The custom PCBs were fabricated from FR-1 copper boards using the PCB production workflow developed during Fab Academy. After milling, all electronic components were soldered and electrically tested.

This process produced the main PCB and the secondary button and GPIO expansion board used in the final assembly.

Additive Manufacturing

The enclosure was manufactured using FDM 3D printing with PLA filament. The housing and top cover were printed separately and later assembled to create the final controller body.

Additive manufacturing enabled rapid prototyping and made it possible to iterate the mechanical design before final assembly.

Embedded Programming

Firmware was developed using the Arduino framework for ESP32-S3. The software integrates all hardware peripherals, including the display, joystick, buttons, LEDs and accelerometer.

The programming stage transformed the fabricated hardware into an interactive educational platform capable of demonstrating embedded systems concepts.

System Integration and Packaging

The final stage consisted of assembling the electronic subsystems, battery, wiring and enclosure into a complete product. Mechanical and electrical integration were validated through both virtual assemblies and physical testing.

The resulting device combines sensing, visualization, user interaction, embedded programming and expansion capabilities into a single portable educational platform.

Development Timeline

The GameLab Controller will be developed following an incremental workflow that combines mechanical design, electronics development, fabrication, programming and system integration. The objective is to progressively transform the initial concept into a fully functional embedded systems educational platform while maintaining continuous validation throughout the development process.

The proposed timeline prioritizes early definition of the architecture and component selection, followed by fabrication and iterative testing. This strategy reduces integration risks and ensures enough time for debugging, optimization and documentation before the final presentation.

Planned Development Phases

Planned roadmap describing the expected development stages of the GameLab Controller from concept definition to final delivery.

Development Strategy

The project will follow an iterative development methodology. Instead of waiting until all subsystems are completed, each stage will be validated as soon as possible to identify design issues early and reduce integration risks.

A minimum viable version of the platform will be prioritized first, ensuring that the controller can operate with its core functions before additional features and refinements are introduced.

This approach is expected to improve project reliability while providing enough flexibility to accommodate modifications that may arise during the fabrication and testing stages.

Challenges and Open Questions

Before fabrication began, several design questions needed to be answered in order to transform the initial concept into a functional educational platform. These questions influenced the mechanical design, electronic architecture and user experience of the GameLab Controller.

Expected Outcome

Answering these questions throughout the development process will help ensure that the GameLab Controller achieves its goal of becoming a portable embedded systems laboratory that is ergonomic, reliable, educational and suitable for long-term use in learning environments.

Evaluation Plan

The success of the GameLab Controller will be evaluated from three main perspectives: technical functionality, system integration and educational usability. This ensures that the project is not only able to operate correctly, but also fulfills its purpose as a learning platform for embedded systems.

Success Criteria

If these criteria are met, the project can be considered successful because it will demonstrate a complete integration of digital fabrication, electronics design, embedded programming and educational product design.

Final Presentation Assets

As part of the Fab Academy final project requirements, a summary slide and a short presentation video were prepared to communicate the purpose, development process and final outcome of the GameLab Controller.

These assets provide a concise overview of the project and are intended to showcase the most important aspects of the design, fabrication, electronics, programming and system integration process.

Presentation Slide

Final project summary slide prepared according to Fab Academy presentation requirements.

Presentation Video

Short project demonstration video showing the main features and functionality of the GameLab Controller.

Both files are located in the root directory of the project and are linked according to the Fab Academy final presentation requirements.

Reflection

Defining the scope and implications of the GameLab Controller was an important step in transforming an initial idea into a realistic and achievable final project. This process required balancing educational objectives, technical complexity, fabrication constraints and available development time.

One of the most valuable lessons learned during the planning stage was the importance of clearly defining the purpose of the project before making technical decisions. Rather than starting from a specific sensor, display or microcontroller, the development process began by identifying a real educational challenge: reducing the barriers students face when learning embedded systems for the first time.

This objective influenced every design decision throughout the project. Component selection, enclosure design, user interaction and expansion capabilities were all chosen to create a platform that simplifies learning while still exposing students to real embedded systems concepts.

Another important aspect was understanding how different Fab Academy topics could be combined into a single product. The project became an opportunity to integrate CAD design, electronics production, additive manufacturing, embedded programming and system integration into a cohesive educational device rather than treating each skill independently.

Looking forward, future versions of the GameLab Controller could include additional educational modules, custom-designed input devices and more advanced communication features. However, the current scope successfully demonstrates the feasibility of creating a portable embedded systems laboratory that supports experimentation, learning and future expansion.

Overall, this stage reinforced the importance of project planning and systems thinking. Defining clear objectives, identifying constraints and establishing evaluation criteria provided a strong foundation for the successful development of the final project.

Downloads

All downloadable resources required to reproduce the GameLab Controller are stored directly within this GitLab repository. The files include the mechanical design, PCB manufacturing files, source code, printing assets, and documentation developed throughout the project.

All downloadable resources are included directly in the GitLab repository, ensuring long-term accessibility and compliance with Fab Academy documentation guidelines.