Application and Implications
Final Project: BattleBot – Animal-Inspired 15kg Combat Robot
What will it do?
This project is a 15 kg wireless-controlled battle robot designed for combat competitions. It combines animal behavior with sci-fi aesthetics — think of it like a mechanical scorpion in a battle arena! The robot features a fast-striking weapon system, tough armor, powerful wheels, and remote control via the ESP32 and Blynk app. The idea is to make something agile, durable, and a little intimidating on the battlefield.
Who has done what beforehand?
Before starting, I looked into: - Combat robots from BattleBots and Robowars India. - Mechanisms used in bots like "Tombstone" (rotating weapons) and "Minotaur" (drum spinner). - Other Fab Academy students who made RC vehicles or robotic arms. This helped me understand common structures, what fails during battles, and how to make repairs easier.
Building the First AUTONOMOUS BattleBot!
What will you design?
I designed everything from scratch: - Chassis (CNC-cut aluminum design) - Polycarbonate armor layout - 3D printed internal mounts - Weapon mechanism inspired by a mantis strike - Modular electronics layout - Remote control interface (via Blynk app + ESP32)
What parts and systems will be made?
- CNC-machined chassis for strength and modularity.
- 3D-printed mounts and internal supports for quick assembly.
- Polycarbonate armor for protection.
- Weapon assembly: high-speed motor, custom 3D printed housing.
- Electronics bay with kill switch, LiPo battery, ESCs, and ESP32.
- Wireless control interface using Blynk app for real-time movement and weapon activation.
What materials and components will be used? Where will they come from?
Project Cost Breakdown
| Category | Component/Material | Approximate Cost (INR) |
|---|---|---|
| Mechanical | CNC-cut Aluminum Sheets | ₹2,000 |
| Polycarbonate Sheets | ₹800 | |
| PLA/ABS Filament (3D Printing) | ₹600 | |
| Electronics | 2x High-Torque DC Motors | ₹4,000 |
| 1x High-Speed Weapon Motor | ₹1,500 | |
| 2x Electronic Speed Controllers (ESCs) | ₹2,500 | |
| ESP32 Microcontroller Board | ₹400 | |
| LiPo Battery (3-cell, 11.1V) | ₹3,000 | |
| Voltage Regulator | ₹300 | |
| Manual Kill Switch | ₹200 | |
| Miscellaneous | Bolts, Nuts, Wires, Connectors | ₹1,000 |
| Safety Gear (e.g., Gloves, Goggles) | ₹500 | |
| Total | ₹16,800 |
Sources: Most parts were sourced locally from electronics and mechanical suppliers in Lamington Road (Mumbai) and some 3D printing filament from online stores like Robu.in.
What processes will be used?
- CNC Milling for chassis parts.
- 3D Printing for custom mounts, weapon casing.
- Laser Cutting for quick jigs and templates, panel
- Soldering & Assembly for electronics.
- ESP32 programming using Arduino IDE.
- App-based control using Blynk.
What questions need to be answered?
- Will the weapon motor deliver enough impact force without stalling?
- Can the ESP32 maintain stable communication during aggressive movement?
- Will overheating be an issue for the ESCs?
How will it be evaluated?
- Mobility: Smooth and responsive movement using the remote.
- Weapon system: Successfully activates and performs a strike.
- Wireless control: Reliable communication via app.
- Durability: Stays intact during simulated mini battles.
- Safety: Quick shutdown via kill switch, no exposed wiring.
What tasks have been completed?
- Designed and tested the aluminum frame.
- Tested individual motor + ESC + battery systems.
- Programmed basic movement + weapon activation via Blynk app.
- Created early prototypes of armor layout.
What tasks remain?
- Final assembly of all components into the body.
- Fine-tuning weapon motor alignment.
- Stress testing the complete system.
- Creating final documentation and video.
- Interior Layout for electronic
What has worked and what hasn’t?
Worked well: - ESP32 and Blynk control was surprisingly responsive. - 3D-printed mounts saved a lot of space and wiring mess.
Didn’t work: - Initial material was heavy load — had to replace. - App occasionally disconnected; fixed with voltage regulation.
What questions still need to be resolved?
- Should I add failsafes for when signal is lost?
- Do I need additional cooling for motors during longer fights?
- Should I upgrade from polycarbonate to carbon fiber sheets in future?
What will happen when?
What have you learned?
This project taught me how different skills — CAD, machining, electronics, programming, and even app design — all come together in one tight package. I made mistakes (lots of them!), but each one taught me more about design thinking, iterative testing, and resilience. It’s been chaotic, exciting, and super satisfying seeing it come to lif