Module 8: Telemetry & Data — RC Tuner Training

Lesson 1 of 4

📡 RaceBox Micro — Your Data Source

GPS + accelerometer + gyro. Records everything your car does at up to 50Hz.

RaceBox Micro is a small data logger that attaches to your car (or you hold it). It records:

• GPS: Position, speed, distance (10Hz)
• 3-axis accelerometer: G-forces, cornering, braking (50Hz)
• Gyroscope: Yaw rate — how fast the car rotates (50Hz)

The RaceBox app on your phone shows real-time data. After the session, export to CSV and import into RC Tuner for advanced analysis.

What you can learn: Exact apex speeds, braking zones, corner entry/exit speeds, consistency between laps, where you're leaving time.

What RaceBox shows you

Speed Profile

Top speed per straight
Minimum corner speed
Braking rate (deceleration)
Acceleration out of corners
Consistency between laps

G-Force Data

Lateral G (cornering force)
Longitudinal G (braking/accel)
Corner entry vs exit G
Braking grip limit
Rotation rate analysis

💡 RaceBox affiliate

RC Tuner partners with RaceBox. If you don't have one yet, check the RC Tuner shop for current pricing and affiliate links. A RaceBox Micro is the entry point for data-driven tuning.

Lesson 2 of 4

📥 Importing Telemetry Data

Get your RaceBox CSV into RC Tuner. One file per session. Link it to your setup.

After your race session, open the RaceBox app → Export → Share as CSV. Then in RC Tuner:

1. Go to your session/setup page
2. Tap "Import Telemetry"
3. Select the CSV file from your phone
4. RC Tuner parses and links it to your setup

The data is now associated with that exact car/setup/track combination. Future reference, comparison, and improvement tracking.

Import checklist

RaceBox CSV exported from app Essential

Use the Share/Export function. CSV format is required — not VBO or other formats.

Session tagged with track, date, and car Essential

So future you knows what conditions generated this data. RC Tuner can auto-tag.

Telemetry linked to current setup Essential

Link to the exact setup that was loaded in the car. So you can compare setups later.

Fastest lap and representative lap marked Recommended

Mark your fastest lap and one representative lap. The rest are less important for analysis.

💡 Data size

A typical 5-minute practice session generates ~500KB of CSV data. RC Tuner stores it efficiently. Even after 50 sessions you'll use minimal cloud storage.

Lesson 3 of 4

📊 Lap Analysis — Finding Where the Time Is

Compare laps, find corner-by-corner differences, and identify EXACTLY where you're losing time.

The lap analysis tool overlays two laps (or best vs average) and highlights where the differences are. Think F1 telemetry, just simpler.

What to look for:

• Speed delta: Where is one lap faster? (straight? corner exit?)
• Braking point: Where are you braking too early or too late?
• Apex speed: Are you carrying speed through corners consistently?
• Exit speed: Where does the car accelerate hardest? (grip = better exit)

Lap comparison — what to analyze

✓ Best laps are consistent with each other

If your top 3 laps all follow the same speed/G pattern, your setup is working. You're driving to the limit repeatable.

⚠ High variance = setup or driver inconsistency

If lap 1 is fast but lap 2-5 are slow, you're overdriving. Setup might be aggressive or tire/temp dependent. Dial back.

🔺 Speed drop mid-session = tire temp issue

If laps progressively slow down through a run, tires are overheating. Try harder compound or check gearing (motor too hot = slower).

🎯 Single corner costing 0.3s = big target

If one specific corner is consistently slower than others, focus setup changes there. It's your biggest gain opportunity.

💡 The speed trap

Top speed doesn't tell the whole story. A fast straight with poor corner exit means you're losing time BETWEEN corners. The goal is consistency through the entire lap, not peak speed.

Lesson 4 of 4

🎯 Data-Driven Tuning Decisions

Combine quantitative data with qualitative feel. The best tuning uses both.

Data doesn't replace driving feel — it AUGMENTS it. When you FEEL something is off, data confirms or contradicts it.

The feedback loop:

1. Drive and note your feel (pushes here, loose there)
2. Check data — does it confirm your feeling?
3. If data confirms: make the setup change the Quick Tune suggests
4. If data contradicts: you may be misreading the car's behavior (training opportunity!)
5. Drive again, check data, iterate

Over time, your feel and data converge. You'll feel the car, predict the data, and verify it — building your internal model of how RC cars work.

Common data → setup correlations

Data: Slow minimum speed in Turn 3

→ Entry too aggressive (understeering at corner-in) or too much trail-braking. Try later braking point OR softer front spring for better bite.

Data: Exit speed 5% slower than competitor

→ Grip issue on exit. Check rear camber for less grip, or rear diff too loose, or rear tire compound not matched to track temp.

Data: High variance between laps

→ Driver is inconsistent OR setup is too aggressive (tire temp sensitive, or handling at the limit). Dial back aggression: softer spring or less camber.

Data: Progressive speed loss through run

→ Tire temp overheating OR motor overheating. Try harder tire compound OR adjust gearing (higher FDR).

💡 Building your data library

Every session with telemetry makes you faster next visit. RC Tuner stores your data linked to track + setup. Over time, you'll have a complete library of "what works here" — your personal racing database.

The top RC racers in the world all use data. Telemetry separates the feel-based tuners from the engineering-based tuners. You now have the full toolset.

🏎️ RC Tuner

📡 Telemetry & Data Analysis

📡 RaceBox Micro — Your Data Source

What RaceBox shows you

📥 Importing Telemetry Data

Import checklist

📊 Lap Analysis — Finding Where the Time Is

Lap comparison — what to analyze

Quick check

🎯 Data-Driven Tuning Decisions

Common data → setup correlations

Final module check

🎓 Course Complete!