Which BMW iDrive Do I Have? CIC, NBT, NBT EVO and MGU Explained
Almost every BMW question — can I get Apple CarPlay, why does it want an FSC code, will this map update work, can I activate ConnectedDrive — has the same first step: knowing which iDrive system your car actually has. Get that wrong and you buy the wrong map, the wrong code, or a feature your head unit cannot run. This guide shows you how to identify your system for certain (CIC, NBT, NBT EVO or MGU), what each one can and cannot do, and where to go next once you know.
If you would rather not guess, send us your VIN and we will tell you exactly which head unit is fitted and what it supports. Everything we activate — from FSC codes to coded features — is generated for your specific car, so this identification step is the one we do first every time.
Why the head unit matters so much
On a BMW, "iDrive" is not one thing — it is a family of head-unit generations, each with different hardware, different capabilities and different activation rules. A navigation map for one generation will not load on another. An FSC code is tied to the exact unit. Apple CarPlay only exists from a certain generation onward. Even the way features are switched on changes over time (older cars use FSC codes; newer ones use the SFA system — see SFA vs FSC explained). So before anything else, you identify the unit.
The four generations at a glance
| System | Years (approx.) | Look / clues | CarPlay |
|---|---|---|---|
| CIC | 2009–2013 | Rotary controller without a touchpad; older split-screen menu | No |
| NBT | 2013–2016 | Flatter menu tiles; controller may have a touchpad on later cars | Rarely / retrofit only |
| NBT EVO (ID5/ID6) | 2016–2018 | Tile-based "ID5/ID6" home screen; often touchscreen | Yes (activatable) |
| MGU (ID7/ID8) | 2018 onward | Large widescreen, "ID7/ID8" graphics, live cockpit | Yes (usually standard) |
These year ranges overlap at the edges because BMW rolled systems out model-by-model, so the year alone is a hint, not proof. Below are the reliable ways to know for sure.
How to identify your iDrive for certain
1. Look at the on-screen menu style
This is the fastest clue. CIC uses an older split layout with a rotary controller and no touchpad. NBT introduced flatter menu tiles. NBT EVO shows the tile-based ID5 or ID6 home screen and is often a touchscreen. MGU (ID7/ID8) has a large widescreen display with modern graphics and a fully digital instrument cluster. If your screen looks like a smartphone grid of large tiles and responds to touch, you are almost certainly on EVO or MGU.
2. Check the iDrive version number in the menu
Many cars show the interface generation in the settings or when browsing menus — ID4, ID5, ID6, ID7 or ID8. As a rough map: ID4 ≈ NBT, ID5/ID6 ≈ NBT EVO, ID7/ID8 ≈ MGU. This is one of the most dependable on-car checks.
3. Confirm by VIN
The only method that is 100% certain is decoding the VIN and reading the exact head-unit part fitted. Because two identical-looking cars can have different units depending on options and build date, this is what we do before generating any code or map. If you want certainty, this is it — and it takes us a minute.
CIC — the early system (≈2009–2013)
Found on E-series cars like the E90 3 Series, E60 5 Series, E70 X5 and the F10 in early build. Controlled by the rotary dial without a touchpad. CIC does navigation and BMW Professional features but predates Apple CarPlay entirely — no amount of coding adds CarPlay to a genuine CIC unit. What CIC owners most often need is a navigation map update, which triggers an FSC prompt: that is exactly the situation covered in why your BMW asks for an FSC code after a map update. CIC uses the FSC activation system.
NBT — the middle generation (≈2013–2016)
The step up from CIC: faster, flatter menus, and on later cars a touchpad on top of the rotary controller. Found across F30, F10, F15, F25 and similar. NBT still uses FSC codes for navigation and feature activation. Apple CarPlay is generally not available on standard NBT (some markets/retrofits aside), so if CarPlay is your goal, confirming NBT vs NBT EVO is the whole ballgame — see our Apple CarPlay activation guide.
NBT EVO — the CarPlay generation (≈2016–2018)
This is where Apple CarPlay arrives as an activatable feature, and where the ID5/ID6 tile interface appears. NBT EVO comes in sub-variants (often referred to as ID5 and ID6), and it is frequently a touchscreen. For most owners asking "can I get CarPlay?", the answer is yes if the car is NBT EVO. FSC codes still apply for navigation activation, and features like video in motion and full-screen CarPlay are commonly switched on here. If your home screen is a grid of tiles and the car is roughly 2016–2018, you are very likely on EVO.
MGU — the modern system (≈2018 onward)
The current generation, badged ID7 and its successors, with a large widescreen, a fully digital instrument cluster (Live Cockpit) and, on most cars, Apple CarPlay as standard. MGU moved feature activation toward the SFA system rather than classic FSC codes, and its coding is protected — which is why newer cars are best handled with the correct tooling rather than a phone app (background: NCD secure coding explained). MGU owners typically come to us for ConnectedDrive activation, digital display features and map handling rather than basic CarPlay.
Which system is in my model? (rough guide)
This is a starting point, not a guarantee — build date and options move cars between systems, so always confirm by VIN before buying. But for orientation:
| Model | Likely system by build date |
|---|---|
| E90/E91/E92 3 Series | CIC (2009–2012 facelift cars) |
| E60 5 Series, E70 X5, E71 X6 | CIC on later builds |
| F30/F31/F34 3 Series | NBT (2013–2016), NBT EVO on late builds |
| F10/F11 5 Series | NBT; CIC on early pre-facelift |
| F15 X5, F16 X6, F25 X3, F26 X4 | NBT, later NBT EVO |
| F20/F21 1 Series, F22 2 Series | NBT, NBT EVO after facelift |
| F48 X1, F39 X2, F45/F46 2 Series AT | NBT EVO |
| G20 3 Series, G30 5 Series (early) | NBT EVO or MGU depending on build |
| G-series 2019 onward, G20/G30 facelift, G01/G05 | MGU (ID7/ID8) |
Notice how many models span two systems — that is exactly why the year or model alone is never enough for a purchase decision. The VIN removes all doubt.
Can I upgrade my BMW to a newer iDrive?
This comes up constantly: "Can I turn my CIC into NBT, or my NBT into EVO to get CarPlay?" The honest answer is that jumping generations is a hardware retrofit, not a coding job — it means swapping the head unit and often related modules, then coding everything to match the VIN. It can be done, but it is a parts-and-labour project, not a quick activation, and it rarely makes financial sense purely for CarPlay.
What is a quick job is activating everything your existing unit already supports but has switched off — navigation, CarPlay on EVO, ConnectedDrive, video in motion, displays. That is where most owners actually get the win, without changing any hardware. Tell us your VIN and we will separate "already capable, just needs activating" from "would need a retrofit" so you do not spend on the wrong thing.
What you can do once you know your system
Identification is the gateway. Once you know the head unit, the right path is clear:
- Navigation maps and the FSC prompt — the map you need and whether you will need a code depends entirely on the generation: what a map update changes across CIC, NBT, NBT EVO and MGU.
- FSC codes — for CIC/NBT/EVO navigation and feature activation, generated for your VIN: FSC codes. Background reading: FSC codes explained.
- Apple CarPlay — available on EVO and MGU, activatable on EVO: CarPlay activation guide.
- ConnectedDrive / online services — lifetime activation for the newer units: Connected Package Professional.
- Coded comfort features — start-stop memory, video in motion, displays and more: BMW Feature Installer.
Common mistakes when identifying iDrive
- Going by year alone. BMW changed systems mid-model-year and per model. A 2016 car could be NBT or NBT EVO depending on build date and options.
- Assuming a touchscreen means the latest system. NBT EVO is often a touchscreen too — touch capability alone does not tell CIC/NBT/EVO/MGU apart.
- Buying a map or code before confirming. The map and the FSC are unit-specific. Buying for the wrong generation is the single most common wasted purchase — confirm by VIN first.
- Expecting CarPlay on CIC or standard NBT. The hardware simply predates it; coding cannot add what the unit was never built to run.
Frequently asked questions
What is the fastest way to tell which iDrive I have?
Look at the home screen. Older split menu with a rotary-only controller = CIC. Flat tiles, maybe a touchpad = NBT. A grid of large tiles (ID5/ID6), often touch = NBT EVO. A wide modern display with a fully digital cluster (ID7/ID8) = MGU. For certainty, decode the VIN.
Can I add Apple CarPlay to any BMW?
No. CarPlay is available on NBT EVO (activatable) and MGU (usually standard). Genuine CIC and standard NBT units predate it and cannot run it via coding.
Does my iDrive generation affect which navigation map I need?
Yes — completely. Each generation uses different map data, and loading the wrong one will fail. Identify the unit first, then get the matching map.
Why does my BMW ask for an FSC code?
CIC, NBT and NBT EVO use FSC codes to activate navigation (and some features). After a map update the car often asks for a fresh code tied to your VIN. We cover this fully in the FSC-after-map-update article linked above.
I still can't tell — can you check for me?
Yes. Send your VIN and we will confirm the exact head unit fitted and tell you precisely what it supports before you buy anything.
BMW is a trademark of its respective owner and is referenced here for identification only. TempaDrive is not affiliated with or endorsed by BMW.