Fixing Blank DAB Station Logos
Discussion
Fixing Blank DAB Station Logos: A Case for Treating Them Like Map Updates
The problem
Since at least 2021, owners of Renault vehicles (Clio, Megane, Zoe, Arkana, Austral) and several other manufacturers' cars (Skoda, Jaguar, Porsche) have reported the same recurring complaint: DAB radio station logos showing as blank placeholder tiles instead of the station's branding. BBC stations tend to display correctly; commercial stations very often don't. The issue has been raised with manufacturers repeatedly, acknowledged as "known," and left unresolved for years across multiple model generations.
This isn't a minor cosmetic nuisance limited to one brand. It's an industry-wide pattern, which suggests the cause sits in how these systems are architected, not in any one company's incompetence.
Why it happens
Station logos can reach a receiver two ways: live over the DAB multiplex itself (via the MOT/SlideShow protocol), or via an internet-connected lookup (RadioDNS), using a shared logo standard (ETSI TS 102 818) that works for both. In practice, UK broadcasters make very limited use of live over-air logo broadcasting compared to countries like Germany or Norway. That means most in-car systems are actually relying on a locally stored lookup table baked into the head unit's firmware, matching each station's broadcast identifiers (Service ID, Ensemble ID, country code) to a logo image.
That table breaks every time a broadcaster reshuffles: stations move multiplexes, regional stations get rebranded under a national banner, new local DAB multiplexes launch. The identifiers shift, the old logo entry stops matching, and the receiver falls back to a blank tile. BBC logos survive because the BBC's identifiers have been stable for years. Commercial radio is a much faster-moving target, and nobody is maintaining the table to keep up.
Why it doesn't get fixed
Updating that table isn't technically hard, it's a small image file plus an index, but in most infotainment platforms it doesn't live as its own component. It's bundled inside the radio/DAB tuner module's firmware image, supplied by a third-party automotive electronics vendor. Because it isn't separated out, fixing it means re-certifying and re-releasing the same software image used for actual functional features, which carries disproportionate cost and risk for what amounts to a bitmap update. Low cost-to-fix-the-actual-thing, high cost-to-ship-the-fix: that mismatch is why it keeps losing the prioritisation fight, release after release.
The fix: treat logos like map data
Manufacturers already have a working template for exactly this problem: map data. Mapping content (road data, POIs) is deliberately built as a separate, versioned package from the core infotainment software, specifically so it can be refreshed independently without re-certifying anything that affects vehicle function. It exists because map providers built a commercial ecosystem around licensing map updates, which created the incentive to engineer that separation properly.
Station logos have never had an equivalent push behind them, so they never got architected the same way. There's no technical reason they couldn't be: a logo database is no riskier to update than a map tile set, arguably less so.
For future devices, this is straightforward: build the logo/service ID database as its own versioned content package from day one, ideally tied to a live RadioDNS lookup so it self-updates from broadcaster-supplied data rather than needing a human-maintained table at all.
For existing devices already on the road, a full fix is harder but not impossible. If the connectivity hardware used for maps or eCall already exists in the car, a software update could in principle decouple the logo table from the tuner firmware and route it through the same lightweight content-update channel used for maps, without touching anything safety- or function-critical. Whether a given manufacturer's existing platform is modular enough to do this without a full reflash depends on how tightly the original software was bundled, which varies by model and supplier, but it's an engineering decision, not a hard technical wall.
The problem
Since at least 2021, owners of Renault vehicles (Clio, Megane, Zoe, Arkana, Austral) and several other manufacturers' cars (Skoda, Jaguar, Porsche) have reported the same recurring complaint: DAB radio station logos showing as blank placeholder tiles instead of the station's branding. BBC stations tend to display correctly; commercial stations very often don't. The issue has been raised with manufacturers repeatedly, acknowledged as "known," and left unresolved for years across multiple model generations.
This isn't a minor cosmetic nuisance limited to one brand. It's an industry-wide pattern, which suggests the cause sits in how these systems are architected, not in any one company's incompetence.
Why it happens
Station logos can reach a receiver two ways: live over the DAB multiplex itself (via the MOT/SlideShow protocol), or via an internet-connected lookup (RadioDNS), using a shared logo standard (ETSI TS 102 818) that works for both. In practice, UK broadcasters make very limited use of live over-air logo broadcasting compared to countries like Germany or Norway. That means most in-car systems are actually relying on a locally stored lookup table baked into the head unit's firmware, matching each station's broadcast identifiers (Service ID, Ensemble ID, country code) to a logo image.
That table breaks every time a broadcaster reshuffles: stations move multiplexes, regional stations get rebranded under a national banner, new local DAB multiplexes launch. The identifiers shift, the old logo entry stops matching, and the receiver falls back to a blank tile. BBC logos survive because the BBC's identifiers have been stable for years. Commercial radio is a much faster-moving target, and nobody is maintaining the table to keep up.
Why it doesn't get fixed
Updating that table isn't technically hard, it's a small image file plus an index, but in most infotainment platforms it doesn't live as its own component. It's bundled inside the radio/DAB tuner module's firmware image, supplied by a third-party automotive electronics vendor. Because it isn't separated out, fixing it means re-certifying and re-releasing the same software image used for actual functional features, which carries disproportionate cost and risk for what amounts to a bitmap update. Low cost-to-fix-the-actual-thing, high cost-to-ship-the-fix: that mismatch is why it keeps losing the prioritisation fight, release after release.
The fix: treat logos like map data
Manufacturers already have a working template for exactly this problem: map data. Mapping content (road data, POIs) is deliberately built as a separate, versioned package from the core infotainment software, specifically so it can be refreshed independently without re-certifying anything that affects vehicle function. It exists because map providers built a commercial ecosystem around licensing map updates, which created the incentive to engineer that separation properly.
Station logos have never had an equivalent push behind them, so they never got architected the same way. There's no technical reason they couldn't be: a logo database is no riskier to update than a map tile set, arguably less so.
For future devices, this is straightforward: build the logo/service ID database as its own versioned content package from day one, ideally tied to a live RadioDNS lookup so it self-updates from broadcaster-supplied data rather than needing a human-maintained table at all.
For existing devices already on the road, a full fix is harder but not impossible. If the connectivity hardware used for maps or eCall already exists in the car, a software update could in principle decouple the logo table from the tuner firmware and route it through the same lightweight content-update channel used for maps, without touching anything safety- or function-critical. Whether a given manufacturer's existing platform is modular enough to do this without a full reflash depends on how tightly the original software was bundled, which varies by model and supplier, but it's an engineering decision, not a hard technical wall.
Gassing Station | In-Car Electronics | Top of Page | What's New | My Stuff