Week 17: Applications and Implications
In this week, we analyzed the project in retrospect and evaluated whether its current approach could successfully answer and solve the main development questions proposed at the beginning of the project.
Before starting
This process helped define the technical scope of KINGER, identify missing subsystems, validate the feasibility of the architecture, and organize the workflow required for the final implementation.Questions
What will it do?
KINGER is a modular AI assistant designed to function as an interactive roommate and smart desktop companion.
The system combines a Raspberry Pi 5 and a XIAO ESP32-C6 microcontroller to provide local artificial intelligence processing, voice interaction, LED feedback, and hardware control.
The assistant is capable of:
- Listening to voice commands through digital microphones
- Converting speech into text locally
- Processing requests using a local AI model through Ollama
- Generating voice responses through a speaker system
- Providing visual feedback using NeoPixel LEDs
- Managing operating modes through UART communication
- Switching into a high-performance Minecraft server mode when requested
Who's done what beforehand?
Several existing open source and commercial technologies inspired the development of KINGER:
- Commercial smart assistants such as Alexa and Google Home
- Open source voice assistants running on Raspberry Pi systems
- ESP32 based IoT interaction systems developed throughout Fab Academy
- Local AI execution frameworks such as Ollama
- Community projects involving NeoPixels, UART communication, and I2S audio devices
However, KINGER aims to combine these systems into a fully customizable and modular assistant with local AI processing and experimental interaction design.
What sources will you use?
- Raspberry Pi official documentation
- XIAO ESP32-C3 documentation
- INMP441 microphone datasheets
- MAX98357A amplifier datasheets
- NeoPixel documentation by Adafruit
- Arduino and PlatformIO documentation
- Ollama local AI framework documentation
- Fab Academy classes and examples
What will you design?
- Custom PCB for peripheral control and UART communication
- 3D printed modular body inspired by Kinger from The Amazing Digital Circus
- Integrated cooling structure for Raspberry Pi airflow
- Audio input/output system using I2S devices
What materials and components will be used, how much will they cost, and where will they come from?
| Item | Details | Qty | Unit Price ($) | Source / Link |
|---|---|---|---|---|
| Raspberry Pi 5 | Main AI processing unit | 1 | $95 | Official Raspberry Pi distributor |
| XIAO ESP32-C3 | Peripheral control microcontroller | 1 | $8 | Seeed Studio |
| INMP441 | Digital I2S microphones | 2 | $4 | Amazon / AliExpress |
| MAX98357A | I2S audio amplifier | 1 | $5 | Amazon / AliExpress |
| Speaker | Audio output system | 1 | $6 | Electronics supplier |
| NeoPixel Ring | 16 RGB LEDs feedback system | 1 | $10 | Adafruit / Amazon |
| LDR | Ambient light sensing | 1 | $1 | Local electronics store |
| Push Buttons | Volume and mode controls | 3 | $0.50 | Local electronics store |
| Battery Pack | NeoPixel and speaker power | 1 | $12 | Amazon |
| 3D Printed Parts | External shell and modular structure | 1 set | $20 | Fab Lab Puebla |
What parts and systems will be made?
- Custom PCB for peripheral management
- UART communication bridge between Raspberry Pi and ESP32
- AI voice interaction pipeline
- 3D printed enclosure and modular body structure
- Audio subsystem with microphones and amplifier
- Software interface for system scheduling and documentation
What processes will be used?
- 3D modeling using Blender and CAD software
- 3D printing for enclosure fabrication
- PCB design using KiCad
- Embedded programming using Arduino IDE and Python
- UART and I2S communication implementation
- Laser cutting and electronic assembly
- Local AI integration and software optimization
What questions need to be answered?
- Can local AI run efficiently alongside a Minecraft server?
- How stable is the UART communication under continuous operation?
- Will the cooling system maintain safe operating temperatures?
- How accurate will the speech recognition system be in real environments?
- Can the modular enclosure provide enough acoustic quality for microphones and speakers?
- How responsive will the interaction system feel to the user?
How will it be evaluated?
The project will be considered successful if it meets the following operational criteria:
- Voice Recognition: The microphones correctly capture voice commands and convert them into text locally.
- AI Processing: The Raspberry Pi successfully processes prompts using Ollama without relying on cloud services.
- Audio Response: The MAX98357A amplifier and speaker reproduce generated responses clearly and consistently.
- UART Communication: The ESP32 and Raspberry Pi exchange commands and feedback reliably in real time.
- Visual Feedback: The NeoPixel ring correctly represents the internal state of the assistant.
- Performance Mode: KINGER successfully switches into Minecraft server mode, reallocating resources for stable server execution.
- Thermal Stability: The enclosure ventilation system prevents overheating during prolonged operation.
- Modularity: Components can be replaced or upgraded without redesigning the entire system.