BMW Tire Pressure and Temperature Display: RDC Coding Guide

On BMWs with direct tire pressure monitoring, the RDC sensor inside each wheel measures pressure and temperature together. The pressure usually shows from the factory; coding opens the extended per-wheel view with the temperature column where the software supports it. This guide covers the hardware check, the steps and the limits of the display. OBDThink is an independent BMW coding and diagnostics app and is not affiliated with BMW AG. What Does the RDC System Measure and How Does It Work? A battery-powered RDC sensor sits inside each rim; it measures the pressure and the air temperature inside the tire and radios both to the car. The receiver collects the values, the control logic compares them with thresholds, and the vehicle status menu in iDrive draws the readable numbers. The counterpart of the direct system is indirect monitoring: the method called RPA compares wheel speed differences and knows no absolute values. Display coding is meaningful only on cars with real sensor data; on an RPA car no coding can produce a number. Feature: per-wheel pressure and temperature display System: RDC, direct tire pressure monitoring Module: the tire menu in the head unit; the RDC control unit itself is not modified Requires: factory RDC wheel sensors Not possible: absolute values on RPA cars without sensors Way back: hide the display again, or restore the backup The quick tell is the values themselves: if the vehicle status screen lists a pressure number per wheel, the car has RDC; if the tire entry only offers a reset, the system is RPA. Which Models Carry the RDC Hardware? The hardware depends on the equipment package and the market; one example of a body can carry sensors while another does not. Coverage is therefore confirmed with the menu in the car rather than with a list. The summary below gathers the cases people ask about most. • In F30 and F10 cars, RDC is standard or optional depending on the market; sensor-equipped examples are candidates for the full display. • In G20 and G05 generation cars, RDC is standard and iDrive already shows pressure, on most software versions the temperature too, per wheel; display coding usually has little left to add there. • E90-era cars carry RDC as an option in many markets and as standard where regulation required it; the display is simpler and covered in a separate guide. • Cars carrying only RPA watch speed differences; with no sensors to deliver numbers, display coding produces nothing. • Sensor batteries run out over the years; a dying sensor first leaves dashes on the screen, then a fault entry. • Winter and summer wheel sets both need sensors; with a sensorless set mounted, the display stays empty. How Do You Tell Your Car Has RDC? The most reliable check sits in the car and takes a minute. Open the vehicle status section in iDrive: if the tire pressure entry lists a value per wheel, the sensors are present. If you only see a reset option for the tire indicator, the car runs the indirect system. • Open the vehicle status menu: a per-wheel value list marks the direct system, a lone reset button marks the indirect one. • An OBDThink scan may show a separate RDC entry on older cars; on newer ones the receiver sits inside another control unit, so a missing entry proves nothing and the menu check decides. • A tire shop confirms sensor presence in seconds with a trigger tool, without removing the wheel. • Compatible retrofit sensors can be learned by the system; the learning completes over a short drive. • Because equipment lists vary by market, trust the menu check rather than the model year. How Do You Enable the Full Display with OBDThink? The coding makes the menu draw the data it already collects as a complete list. The app reads the relevant entries, switches the display option on and refreshes the unit; the tire menu then lists pressure per wheel, and on supporting software the temperature as well. • 1. Stop the car on level ground, keep the ignition on and plug the adapter in. • 2. Finish the scan and confirm the RDC entry shows in the module list. • 3. Pull a backup of the current coding and drop a copy into cloud storage. • 4. Locate the tire display entry in the feature list. • 5. Select the full display and wait for the write to finish. • 6. Allow the unit to refresh through an ignition cycle. • 7. Open the vehicle status menu and see the per-wheel values listed. • 8. Take a short loop; watch the values come alive as the sensors wake. IF the menu shows only a reset button THEN the car carries RPA and no coding can produce values IF pressure shows but temperature does not THEN the unit software does not open that column IF dashes replace numbers after a wheel change THEN compatible sensors relearn over a short drive; with missing or incompatible sensors the dashes stay and a fault follows The fastest verification is a short loop: the sensors wake once the wheels turn, and the menu values come alive within a few minutes. Seeing dashes on a car parked for a long time is normal. How Do You Revert the Display? The way back is switching the display option to the factory view. With a backup, OBDThink restores the file and the unit returns to the exact state captured at backup time; without one, the same entry is switched to the factory value. The monitoring keeps running in both cases. • Restore the backup; the other entries return to their backup-time state along with the display. • For the single entry, switch the tire display option back to the factory value. • Verify with an ignition cycle that the menu shows the factory view again. • The warning thresholds are independent of the coding; they stay the same after the revert. • Archive the revert log as proof of the last coding state in case the car changes hands. After the revert, the extended columns no longer appear in the menu: the tire screen returns to the factory view, while the monitoring and its warnings keep working without any interruption. What Problems Show Up With the RDC Display? The most common picture is dashes after a wheel change: until the new sensors introduce themselves to the receiver, the menu cannot show values. That is not a fault; a few minutes of driving completes the learning and the numbers arrive on their own. The second group is incompatible spare parts: a retrofit sensor that misses the protocol may never be learned. The third is known behaviour; a dealer update can return the display to the factory view, and the coding is applied again. The display is comfort, not a substitute for tire care: if you see pressure dropping fast, stop somewhere safe and check the tire physically. Pressure measured on cold tires is the reference value. Which Questions Come Up Most? Questions gather mostly on four topics: sensorless cars, the temperature column, sensor batteries and the warning system. The short answers below rest on the fact that the display only draws data that already exists. • Does coding show values on a sensorless car? No; RPA only watches speed differences, and there is no data to build an absolute number from. • Is temperature shown on every car? Not everywhere; the column depends on the unit software, and some versions list pressure only. • What happens when a sensor battery dies? The wheel turns to dashes first, then a fault entry follows; the battery is replaced with the sensor. • Do the warning thresholds change? They stay put; the coding only opens the display, and the monitoring and warning logic stays at the factory setting. Confirm the RDC hardware with the menu check first, take the backup and open the full display; after a short loop, every wheel's pressure — and where supported, its temperature — sits in front of you. Make a habit of comparing the values on cold tires, and the screen becomes a quiet helper that protects tire life and fuel.