Skip to content

Welcome

Mihir Patel — Individual Datasheet
as part of
R6 Recon Amphibot (Amphibot V1)
for
Team 302

Submission: April, 03, 2026

Introduction

This datasheet documents the hardware and firmware plan for my individual subsystem: the Internet-based Two-way Wireless Communication module (ESP32 Gateway) for the Amphibot V1. Its purpose is to record clear, testable requirements, show the block-level hardware layout, list parts and interfaces, and explain how my work plugs into the team-level system (UART daisy-chain, power bus, and MQTT/Wi-Fi). This page is intended for teammates, instructors, and graders so they can quickly understand what I will build and how it integrates into the overall project.

Project Summary

The Amphibot V1 is a small, throwable amphibious exploration robot that streams live FPV video and telemetry to a remote operator while reporting a consolidated hazard score. My module provides the bi-directional Wi-Fi gateway between the robot and the operator's device. It will:

  • Host a reliable Wi-Fi connection and talk to an external MQTT broker (or local broker during demos).
  • Translate UART traffic from the onboard modular bus into MQTT topics (and vice versa).
  • Stream low-latency FPV video (target < 500 ms) to the operator app.
  • Implement safe fallback behaviors on connection loss (motor safe-stop command via UART).

This gateway is crucial for remote control, live telemetry, and demo display functions of the Amphibot.

My Contribution

I (Mihir Patel) own the Wireless Communication subsystem (ESP32). My responsibilities are:

  • Hardware: select and integrate the ESP32 module, the 3.3 V switching regulator, barrel jack and power-jumper circuitry, and the 2×4 IDC ribbon connector interface.
  • Firmware: implement Wi-Fi + MQTT client, MQTT↔UART packet bridge with CRC checking, reconnection and fail-safe behaviors, and a basic web/socket interface for debugging.
  • FPV stream handling: configure/stream camera video (ESP32-CAM or serial camera) and optimize to achieve target latency.
  • System integration: define and verify UART packet formats, work with teammates to map ribbon pins, and ensure safe behavior when the wireless link is lost.
  • Documentation & verification: supply the module datasheet, BOM, block diagram, and verification test log for integration.

Project Sections

You can navigate the main sections of this individual datasheet using the top menu or the links below. Each section documents a specific stage of the design and implementation of the Wireless Communication (ESP32) subsystem.

  • Project Requirements – Module-level requirements, thresholds, target goals, and stretch objectives

  • Block Diagram – Subsystem-level block diagram showing power domains, UART daisy-chain connections, ESP32 peripherals, and external interfaces.

  • Component Selection – Selected components and design rationale for the ESP32 wireless gateway.

  • Microcontroller Selection – ESP32 microcontroller selection criteria, comparisons, and rationale.

  • Power Budget – Power consumption analysis, supply requirements, and power domain design.

  • Bill of Materials (BOM) – Manufacturer part numbers, footprints, quantities, and estimated costs.

  • Schematic – Electrical schematics for the wireless communication module.

  • PCB Layout – PCB layout, routing decisions, and design considerations.

  • API – API documentation for the subsystem interface and communication details.

  • Reflection – Lessons learned, challenges faced, and design insights from this subsystem.