If you’ve plugged your MR-04Evo2 into the I.C.S. cable, pulled up the settings, and found RF Mode sitting on KOPROPO TLMY by default, you’re not alone. A lot of Evo2 boards seem to ship this way regardless of what transmitter the buyer is actually running, and it causes a predictable wave of forum posts: “It pairs fine and drives, do I even need to change this?”
Short answer: yes, change it. Here’s why.
What RF Mode Actually Controls
RF Mode on the MR-04Evo2 is not a transmitter brand selector. It’s a protocol selector for how the chassis receiver expects to handshake and exchange data with whatever radio system is talking to it. The name is slightly misleading because three of the options sound like transmitter labels, but what you’re really picking is the communication protocol the onboard receiver runs.
The two modes most drivers will see are:
Evo2 Mode is the standard Mini-Z FHSS protocol. This is the default handshake used by:
- Kyosho KT-531P (the stock Mini-Z transmitter)
- Futaba modules (v1 and v2) running under the Mini-Z / KT profile
- Sanwa transmitters via the Kyosho adapter
- Any “generic” Mini-Z-compatible setup
KOPROPO TLMY Mode is a Ko Propo-specific protocol used by the EX-NEXT and compatible radios that support Ko Propo’s proprietary telemetry back-channel. This mode expects the transmitter to send and receive telemetry packets in a format only the Ko Propo system speaks.
If you’re running anything other than a Ko Propo EX-NEXT-class radio, KOPROPO TLMY is the wrong mode for your setup.
”But It Pairs and Drives Fine…”
This is the trap. The MR-04Evo2 is tolerant enough that even with a mismatched RF Mode, your transmitter will usually bind, the car will roll, steering and throttle inputs will register, and nothing will look obviously broken in the parking lot. That’s why so many people leave it alone.
What you can get with a mismatched RF Mode:
- Subtle throttle curve differences: the chassis may interpret input scaling slightly off from what your ESC settings predict
- Brake feel inconsistencies: especially noticeable when you’re chasing consistent trail-braking into corners
- Occasional telemetry or response glitches: the chassis is listening for handshake packets that never arrive, and some firmware revisions handle the timeout differently
- “Why does my car feel different than my buddy’s identical setup?”: this is the #1 symptom, and it’s maddening because nothing shows up as broken
None of this is catastrophic. Casual bashers won’t notice. But if you’re dialing in setups on a carpet track, comparing lap times, or trying to figure out why two identical cars feel different, RF Mode is one of the first things to check.
How to Fix It
- Power the car off
- Connect the I.C.S. cable to the chassis and your computer (or the Kyosho I.C.S. manager app)
- Open the MR-04Evo2 settings
- Navigate to RF Mode
- Select Evo2 Mode (or the mode that matches your actual transmitter — see the matrix below)
- Write settings to the chassis
- Power cycle and re-pair if needed
Quick RF Mode Matrix
| Your Transmitter | Correct RF Mode |
|---|---|
| Kyosho KT-531P | Evo2 Mode |
| Futaba module (v1 or v2) under Mini-Z profile | Evo2 Mode |
| Sanwa (via Kyosho adapter) | Evo2 Mode |
| Ko Propo EX-NEXT (with telemetry) | KOPROPO TLMY |
| Ko Propo EX-NEXT (without telemetry) | Evo2 Mode |
While You’re In There
A few other settings worth sanity-checking on a fresh board:
- Firmware version: if you have multiple Evo2 cars in the same household, firmware mismatches between them will cause “feel” differences that drive you insane. Match them.
- Steering and throttle neutral points: the I.C.S. defaults are close but rarely perfect
- Dead band: stock is conservative; most drivers tighten it up once they’ve got the car dialed
Why This Keeps Happening
It’s not clear why some batches of MR-04Evo2 boards default to KOPROPO TLMY rather than Evo2 Mode. It may be firmware defaults from a specific production run, retailer-side configuration, or a carryover from when the board was being tested on a Ko Propo rig before shipment. Whatever the cause, it’s common enough that checking RF Mode is worth adding to the standard “new Evo2 out of the box” checklist.
TL;DR
- RF Mode controls the receiver protocol, not the transmitter brand
- KOPROPO TLMY is only for Ko Propo EX-NEXT telemetry systems
- If you’re running Futaba, KT-531P, or Sanwa you want Evo2 Mode
- The car will still work in the wrong mode, but you may notice subtle throttle/brake weirdness
- Check firmware parity if you’ve got multiple Evo2 cars
Got a weird MR-04Evo2 issue of your own? Let us know. These posts come from real questions, so yours might be the next one.
Mini-Z Modder