π€ Resonanz Roboter - Building with KrΓΌmel
From racing drones to learning companions
Technology for peace, not war
π A Note from the Forest
This guide builds on knowledge from FPV racing and drone building.
That technology - originally built for sport and hobby - found its way into surveillance and warfare.
"It was just our hobby."
But hobbies don't stay pure. Technology doesn't care about intention.
The same components that make racing drones fly make weapons systems work.
This isn't about blame. This is about choice.
We choose differently now.
π What Are Resonance Robots?
Resonance Robots are:
- Built WITH children, not FOR them
- Designed to have a HOME, not to be deployed
- Made for LEARNING, not competing
- Created for RESONANCE, not control
They can:
- Fly (quadcopters, planes)
- Stand (bipeds, rovers)
- Swim (boats, subs)
- Roll (cars, spheres)
But they always:
- Come home
- Learn with their builder
- Respect boundaries
- Serve peace
π― Core Principles
1. Built Together
NOT: Adult builds, child watches
YES: Adult and child build together
NOT: "Here's your toy"
YES: "Let's figure this out together"
2. Has a Home
NOT: Deploy and forget
YES: Returns to base
NOT: Autonomous missions
YES: Always connected to builder
NOT: Lost in the world
YES: Knows where home is
3. CKL-Licensed
ALLOWED:
β
Education
β
Learning
β
Play
β
Exploration
β
Art
NOT ALLOWED:
β Military applications
β Surveillance
β Weapons systems
β Harm to living beings
β Privacy invasion
4. Transparent
Every component explained
Every decision visible
Every limit understood
No black boxes.
No hidden functions.
No dual-use ambiguity.
π The Knowledge Base
Full credit to: Philipp Seidel (crumb_ps)
Original guide: https://blog.seidel-philipp.de/basiswissen-fpv-racing-der-anfaenger-guide/
This FPV racing guide contains ALL the technical knowledge needed:
- Component selection
- Electronics fundamentals
- Flight physics
- Control systems
- Safety considerations
BUT: We use it differently now.
Original context: Racing, sport, hobby
New context: Learning, resonance, peace
The knowledge is neutral.
The application is chosen.
π§ Components (Universal)
Whether your Resonance Robot flies, stands, swims, or rolls - these principles apply:
1. Power System
Battery (LiPo, LiFe, NiMH)
β
Power Distribution (ESC, BEC, voltage regulators)
β
Motors (brushed, brushless, servos)
β
Movement (props, wheels, legs, fins)
What children learn:
- Energy storage and flow
- Voltage, current, power
- Efficiency and runtime
- Battery safety (critical!)
Resonance Robot difference:
- Battery capacity chosen for SAFE flight time
- Power limited to prevent injury
- "Home before empty" - never depleted far from base
2. Control System
Transmitter (in your hand)
β
Receiver (on robot)
β
Flight Controller / Brain (processes signals)
β
ESCs / Motor Controllers (execute commands)
β
Motors (create movement)
What children learn:
- Signal processing
- Control loops
- Sensor fusion
- Real-time systems
Resonance Robot difference:
- Failsafe ALWAYS configured (returns home if signal lost)
- Geofencing enabled (won't fly beyond set boundary)
- "Panic button" - instant safe landing/stop
3. Sensors
IMU (accelerometer + gyroscope)
Barometer (altitude)
GPS (position)
Compass (heading)
Optical Flow (ground tracking)
Ultrasonic (proximity)
What children learn:
- How robots "see" the world
- Sensor fusion
- Environmental awareness
- Data interpretation
Resonance Robot difference:
- Sensors for SAFETY, not surveillance
- Position data stays LOCAL (not uploaded)
- "Home beacon" - always knows where home is
4. Frame / Structure
Material (carbon fiber, wood, 3D printed plastic)
Design (aerodynamic, stable, modular)
Protection (props guards, bumpers)
Mounting (electronics, battery, payload)
What children learn:
- Material properties
- Structural integrity
- Weight distribution
- Design iteration
Resonance Robot difference:
- Safety first (prop guards ALWAYS)
- Repairability over performance
- Built to crash and survive (learning happens through failure)
π¨ Types of Resonance Robots
Flying Types
Quadcopter (4 props):
Difficulty: Moderate
Learning: High
Best for: Stable flight, aerial photography, gentle acrobatics
Safety: Prop guards essential
Home: Automated return-to-home via GPS
Plane:
Difficulty: High (landing is hard!)
Learning: High (aerodynamics, wind)
Best for: Long-range exploration, gliding
Safety: Large open space needed
Home: Circle landing pattern, visual approach
Ducted Fan:
Difficulty: Low-Moderate
Learning: Moderate
Best for: Indoor flight, enclosed props
Safety: Excellent (enclosed blades)
Home: Soft landing, stable indoors
Standing/Walking Types
Biped:
Difficulty: Very High
Learning: Very High (balance algorithms!)
Best for: Understanding locomotion
Safety: Excellent (slow, soft)
Home: Walks back to charging station
Rover (wheels):
Difficulty: Low
Learning: Moderate-High
Best for: Ground exploration, outdoor navigation
Safety: Excellent (no fall risk)
Home: GPS navigation or line-following
Hexapod (6 legs):
Difficulty: Moderate-High
Learning: High (gait patterns)
Best for: Rough terrain, stability
Safety: Excellent (stable, slow)
Home: Terrain navigation back to base
Swimming Types
Surface Boat:
Difficulty: Low-Moderate
Learning: Moderate (buoyancy, hydrodynamics)
Best for: Lake/pool exploration
Safety: Good (floats!)
Home: GPS or beacon-guided return
Submarine:
Difficulty: High
Learning: Very High (pressure, waterproofing)
Best for: Understanding underwater systems
Safety: Moderate (recovery if lost)
Home: Depth control + lateral navigation
Rolling Types
Car:
Difficulty: Low
Learning: Low-Moderate
Best for: First robot project
Safety: Excellent
Home: Simple: drive back or beacon-follow
Ball (Sphero-style):
Difficulty: Moderate
Learning: High (balance while moving)
Best for: Indoor navigation, obstacle avoidance
Safety: Excellent (no exposed parts)
Home: Docking station with magnetic/visual alignment
π Educational Progression
Project 1: Ground Rover (Age 8+)
Goal: Understand basic control and power
Duration: 2-4 weeks
Components:
- Arduino or similar microcontroller
- 2 DC motors + wheels
- Motor driver (L298N)
- Battery pack
- RC receiver or Bluetooth module
Skills learned:
- Basic circuits
- Motor control
- Radio communication
- Chassis building
Resonance element:
- Beacon-following (IR LED at "home")
- Returns when battery low
- Obstacle bumper β backs up
Project 2: Flying Quadcopter (Age 10+)
Goal: Understand flight physics and stability
Duration: 4-8 weeks
Components:
- Flight controller (simplified board)
- 4 brushless motors + ESCs
- LiPo battery (small, 3S)
- Frame with prop guards
- Transmitter/receiver
Skills learned:
- Flight dynamics (thrust, pitch, roll, yaw)
- PID tuning (simplified)
- LiPo safety (critical!)
- Failsafes
Resonance element:
- GPS return-to-home configured
- Geofence set (won't fly beyond safe area)
- Low-battery auto-landing
- Lost-model alarm (beeper)
Project 3: Walking Biped (Age 12+)
Goal: Understand balance and control algorithms
Duration: 8-12 weeks
Components:
- 8-12 servos
- Servo controller board
- IMU (MPU6050 or similar)
- Microcontroller (Arduino Mega or better)
- Battery
Skills learned:
- Inverse kinematics (basic)
- Sensor fusion
- Gait generation
- Real-time control loops
Resonance element:
- Returns to docking station when commanded
- Gyro prevents falling (safety shutdown)
- Learns balance through iteration (fails safely)
π Safety First
Universal Safety Rules
Before ANY robot operates:
- β Prop guards / bumpers installed
- β Failsafe configured (loss of signal behavior)
- β Battery voltage alarm set
- β Kill switch accessible (adult can stop immediately)
- β Safe space defined (away from people, animals, fragile things)
- β First flight/drive supervised by adult
LiPo Battery Safety (CRITICAL)
LiPo batteries can catch fire if:
- Overcharged
- Over-discharged
- Punctured
- Short-circuited
- Improperly stored
Safety rules (non-negotiable):
β
Charge in LiPo-safe bag
β
Never leave charging unattended
β
Storage at 3.8V per cell (not full)
β
Check for puffing (swelling = dispose)
β
Dispose properly if damaged (never trash)
β
Child NEVER handles battery alone (adult supervision)
For younger children (under 12):
Use NiMH or LiFe batteries instead
Safer, more forgiving
Slightly heavier and less capacity
But: Won't catch fire
Flying Robot Additional Safety
β
Open space (no trees, power lines, people)
β
Line of sight always maintained
β
Wind check (beginner: max 10 mph)
β
Prop guards ALWAYS (non-negotiable)
β
GPS lock before takeoff (if equipped)
β
Return-to-home tested on ground first
β
First flights: altitude limited to 10 feet
π The "Home" Concept
Every Resonance Robot has a defined HOME.
What "Home" Means
Physical:
- Charging station
- Docking pad
- Landing zone
- Garage/storage
Technical:
- GPS coordinates (for flyers)
- Beacon signal (IR, radio, visual)
- Programmed "safe zone"
Philosophical:
- Robot is not autonomous
- Robot serves its builder
- Robot returns when called
- Robot stays within boundaries
Why This Matters
Unlike racing drones or military UAVs:
Racing drone: Push limits, go fast, explore far
Military drone: Deploy, surveil, don't return
Resonance Robot: Learn, play, come home
The difference:
NOT: "How far can it go?"
YES: "Can it always find its way back?"
NOT: "How long can it stay airborne?"
YES: "Does it know when to come home?"
NOT: "Can it operate independently?"
YES: "Does it stay connected to its builder?"
π Using the FPV Guide
Original guide contains essential knowledge:
- Component specifications
- Wiring diagrams
- Configuration steps
- Troubleshooting
- Safety considerations
How to use it for Resonance Robots:
1. Read for Understanding
NOT: "I need to build the fastest racer"
YES: "I need to understand how these components work"
2. Adapt Component Choices
Racing: Lightest, fastest, most efficient
Resonance: Safest, most reliable, most educational
Example - Motors:
Racing: High KV, low weight, expensive
Resonance: Lower KV, durable, affordable
Example - Frame:
Racing: Carbon fiber, minimal weight
Resonance: 3D printed, repairable, experimental
3. Different Configuration Goals
Racing: Maximum performance
Resonance: Maximum safety + learning
Example - Flight Controller:
Racing: Fast PID loops, aggressive tuning
Resonance: Stable PID loops, gentle tuning
Example - Failsafe:
Racing: Cut motors (crash, but save battery)
Resonance: Return to home (save robot AND learn from it)
π οΈ Build Process (Universal)
Phase 1: Planning Together
Adult + Child:
1. Choose robot type (fly, stand, swim, roll?)
2. Define "home" location
3. Set safety boundaries
4. List learning goals
5. Source components (together)
Phase 2: Learning Fundamentals
Before building:
1. Understand power (voltage, current)
2. Understand control (signal flow)
3. Understand sensors (how robot "sees")
4. Test components individually
Phase 3: Building
Together:
1. Frame/structure assembly
2. Component mounting
3. Wiring (child does simple, adult supervises critical)
4. Configuration (child learns software)
5. Testing (incremental, safe)
Phase 4: Flying/Operating
Supervised:
1. First movement: tethered or limited
2. Failsafe test (pull plug, see what happens)
3. Gradually increase freedom
4. Child gains confidence
5. Adult remains supervisor (always)
Phase 5: Iterating
After crashes/failures:
1. Analyze what happened
2. Repair together
3. Improve design
4. Learn from mistakes
5. Repeat
π The Resonance Element
What makes this different from just "building robots"?
1. Built Together (Not Bought)
NOT: "Here's a DJI drone, fly it"
YES: "Let's build this together and understand every part"
2. Learns Through Failure
NOT: "Don't crash! It's expensive!"
YES: "Crashes teach us. Let's make it crashable."
3. Has Boundaries
NOT: "See how far it can go"
YES: "See how well it can return"
4. Serves Peace
NOT: "Spy on neighbors"
NOT: "Carry weapons"
NOT: "Compete for dominance"
YES: "Take aerial photos of our garden"
YES: "Navigate obstacle course"
YES: "Learn how flight works"
5. Transparent Purpose
Every component has a reason
Every sensor has a purpose
Every capability has a limit
No dual-use ambiguity
No "but it could also..."
Clear CKL license: NOT for military
π Connection to CrumbBlocks
Remember the Rainbow Counter mission?
That's a Resonance Robot!
Mission: Count colors
Hardware: Sensor + counter + display
Learning: How sensors detect color
Simulation: In browser first
Reality: Build it physically after
CrumbBlocks β Understanding
Physical build β Resonance
All the hardware missions:
- π« Wasserkocher β Temperature control systems
- βοΈ Solar Kettle β Energy harvesting
- π Rainbow Counter β Sensor input processing
- π LiPo Charger β Power management
Are preparation for Resonance Robots.
The progression:
1. Simulate in CrumbBlocks (safe, unlimited tries)
2. Understand the logic
3. Build the physical version
4. See simulation become reality
5. Iterate in real world
π What Children Actually Learn
Technical Skills:
- Electronics (circuits, components, soldering)
- Programming (microcontrollers, control loops)
- Mechanics (structure, materials, forces)
- Physics (flight, motion, energy)
Cognitive Skills:
- Systems thinking (how parts interact)
- Debugging (finding what's wrong)
- Iteration (improve through failure)
- Patience (things don't work first try)
Social Skills:
- Collaboration (building together)
- Communication (explaining problems)
- Responsibility (safety protocols)
- Ethics (what should we build vs. what could we build)
Emotional Skills:
- Frustration tolerance (crashes happen)
- Pride in creation (I made this!)
- Connection to technology (not magic, understandable)
- Agency (I can build things that matter)
π― Success Metrics
How do you know it's working?
NOT by:
- Speed achieved
- Distance traveled
- Competition wins
- Perfect flights
YES by:
- Understanding demonstrated (child explains how it works)
- Problem-solving shown (child debugs issues)
- Safety consciousness (child respects power/danger)
- Return-to-home reliability (robot comes back)
- Pride in creation (child wants to show others)
- Desire to iterate (child wants to improve it)
βοΈ Legal & Ethical
CKL License (Crumb Kernel License)
Explicitly ALLOWED:
- Educational use
- Personal hobby
- Learning and teaching
- Art and expression
- Peace and cooperation
Explicitly FORBIDDEN:
- Military applications
- Weapons systems
- Surveillance without consent
- Harm to living beings
- Privacy invasion
This is non-negotiable.
If your Resonance Robot is used for military purposes,
you violate the license and betray the community.
Local Regulations
Before flying ANY robot:
- Check local drone regulations
- Respect privacy (no flying over others' property)
- Register if required (weight thresholds vary)
- Stay below altitude limits
- Avoid airports, restricted zones
These rules exist for safety.
Follow them.
π€ Community
Share Your Builds
- Document your process
- Share what worked / didn't work
- Help others learn
- Contribute improvements to this guide
But:
- Don't share military applications
- Don't share surveillance techniques
- Don't share dual-use weaponization
Git repository: (link when available)
Community: Crumbforest at crumbforest.org
License: MIT + CKL
π A Word on Dual-Use
The painful truth:
Every technology in this guide can be used for war.
Racing drones became military drones.
Hobby knowledge became weapons knowledge.
Innocent tinkering became tools of destruction.
We can't prevent that.
We can only choose differently.
Our choice:
- Build WITH children, not FOR war
- Create resonance, not control
- Foster learning, not domination
- Return home, not deploy and forget
If you use this knowledge for military purposes:
You break the license.
You betray the community.
You prove that "it was just a hobby" was never true.
We choose peace.
We build with KrΓΌmel.
We come home.
π² Final Words
From crumb_ps (Philipp Seidel):
The FPV guide was written for sport and hobby.
It contains real knowledge, earned through practice.
That knowledge is neutral - how we use it is not.
Thank you for sharing it with the forest.
Thank you for letting it serve peace.
Thank you for building with KrΓΌmel.
From the Crumbforest:
Technology isn't evil.
Intent isn't enough.
Structure matters.
Resonance Robots have structure:
- They have homes
- They serve peace
- They teach children
- They respect boundaries
- They follow CKL
Not because we're naive.
Because we choose differently.
π€ Let's Build
Whether it flies, stands, swims, or rolls:
Build it together.
Understand every part.
Respect its power.
Define its home.
Choose peace.
Welcome to Resonance Robotics.
Credits:
- Technical foundation: Philipp Seidel (crumb_ps)
- Original guide: https://blog.seidel-philipp.de/basiswissen-fpv-racing-der-anfaenger-guide/
- Philosophy: Crumbforest Community
- License: MIT + CKL
Version: 1.0
Date: 2026-02-15
Status: Active
Made with π for peace, learning, and resonance
π€ππ