Empowering children with custom ride-on car controls—without sacrificing safety or compatibility.
This project aims to design and build a dual-control wireless system for adapted ride-on cars used in GoBabyGo initiatives.
The system introduces a child-friendly controller (such as push buttons or a joystick) that can drive the vehicle—while preserving full override capabilities of the parent’s stock remote. Our solution is non-invasive, meaning it requires no modification to the car’s internal electronics or receiver.
We believe mobility and independence should be accessible to all children, especially those who benefit from adaptive technologies.
- ✨ Empowerment: Children gain agency through active control of their vehicle.
- 🧠 Safety: The original parent remote maintains full override capability at all times.
- 🔌 Compatibility: The system is designed to work alongside the stock controller and receiver—no internal rewiring or soldering required.
This approach extends the capabilities of existing GoBabyGo adaptations. While many systems only offer hardcoded forward motion, our dual-controller setup enables custom directional control—left, right, forward, and reverse—using adaptive buttons tailored for the child’s needs.
Our core design philosophy is non-invasive compatibility. Rather than replacing or modifying the car’s receiver, we aim to introduce a secondary controller that operates in harmony with the existing system.
Key steps:
-
RF Protocol Reverse Engineering
Capture and analyze the stock remote’s RF signals to understand modulation, framing, and command layout. -
Custom Controller Development
Build a programmable transmitter that:- Listens to and relays commands from the stock remote (preserving override)
- Injects its own commands from child-initiated inputs (e.g., buttons or joystick)
-
Mediation Software Logic
Design control logic that prioritizes safety by always deferring to the parent’s original remote if both attempt to control simultaneously.
This results in a child-safe, parent-controlled, and fully wireless dual input system.
Phase: RF reverse engineering and protocol decoding of produced by weelye.
| Item | Status | Modulation & Rate | Center Freq | Cadence (Hz) | Full Details |
|---|---|---|---|---|---|
| TX20 → RX23 (2.444 GHz) | ✅ Working emulated control | 2-FSK @ 250 kbps | 2.44388 GHz | ~83 Hz | RX23_TX20.md |
| TX1 → RX7 | ✅ Packet format decoded (replay WIP) | 2-FSK @ 1 Mbps | 2.433 GHz | ~81 Hz | RX7_TX1.md |
| TX20 → RX57 | ✅ Protocol Decoded | 2-FSK @ 250 kbps | 2.446 GHz | ~82.7 Hz | RX57_TX20.md |
| TX20/TX10 → RX75 | ✅ Protocol Decoded | 2-FSK @ 250 kbps | 2.453 GHz | ~83.0 Hz | RX75_TX20.md |
For full technical details, packet layouts, timing analysis, and verified captures, see:
👉 RX23 TX20 Analysis
👉 RX57 TX20 Analysis
👉 RX75 TX20 Analysis
👉 RX7 TX1 Analysis
We welcome help from hackers, engineers, makers, and families!
- Help analyze and document RF protocols of other ride-on car systems (weelye RX23, RX75, RX7 etc.)
- Share URH or HackRF captures of your remotes
- Confirm observed behavior with your specific models
- Suggest or prototype adaptive input devices (e.g., large push buttons, joysticks, assistive switches)
- Design low-power embedded transmitter boards (e.g., XN297L, nRF24L01, etc.)
- Help design and implement the software required
- Help implement physical enclosures, harnesses, or interface mounts
- Test across different car models and remotes
- Assist with documentation, photos, and video demos
- Connect with other GoBabyGo chapters for broader input and validation
