For in‑vehicle and portable digital broadcast products, DAB+ certification is a common compliance requirement for Europe, Australia, and the UK. Testing follows ETSI DAB/DAB+ specifications – access channels differ by country – but core documents are largely similar.

Many projects are delayed due to missing documents – samples arrive at the lab but documentation is incomplete – repeated submissions waste shipping costs and lab slots – directly affecting delivery timelines.

1. First, Confirm Your Access Path

·Europe: CE‑RED – DAB/DAB+ receiver performance testing under EN 303 345.

·Australia: RCM via ACMA.

·UK: UKCA registration via Ofcom.

Label and registration rules differ – performance test reports are partially reusable – but the full set cannot be directly reused across markets.

Lock in target markets at project definition – don't wait until samples are ready – avoiding report format mismatches. For multi‑market projects, prepare one core document set – supplement market‑specific files.

Under CE‑RED, DAB receivers are unintentional emitters – using self‑declaration – no Notified Body required.

Prepare label templates separately per market – CE, RCM, and UKCA mark proportions differ. For multi‑market shared‑housing products, plan label layout early – avoiding overlaps – preventing last‑minute issues and port holds.

  2. Application Form and Entity Details

Complete the application form – specifying product model, brand, manufacturer, and factory.

·For Australian exports: a local responsible entity is required.

·Model naming must be consistent – spec sheet, test report, label, and user manual must all match – mismatches cause rejection.

DoC:

·EU: manufacturer or EU representative can sign.

·Australia RCM: must be signed by an Australian local responsible entity.

Local representative authorisation validity must cover the full certification period – avoid the certificate being issued after the authorisation expires.

Before submission, do an internal check – catching address and contact errors. Prepare authorisation documents per local requirements – allow sufficient time for notarisation.

  3. Product Specifications – Write Thoroughly

Spec sheet must clearly state:

·Operating bands (Band III or L‑band).

·Modulation, receiver sensitivity, audio coding (AAC/HE‑AAC).

·Output parameters, antenna type.

For dual‑mode DAB/DAB+ products, specify both.

The spec sheet is the review baseline – vague parameters lead labs to assume the strictest conditions – increasing failure risk.

·In‑vehicle products: specify operating voltage range.

·Portable products: specify power supply and battery parameters.

Use a core spec sheet + difference pages – listing market‑specific differences separately. Update document versions with hardware changes – keeping documentation aligned with physical firmware.

  4. Circuit and Software/Hardware Documents

Provide:

·Block diagram.

·RF section schematics.

·PCB layout diagrams: retain internally – not mandatory for submission.

·Firmware version statement – specifying the actual flashed version.

·Critical component list – RF chip and crystal models.

BOM and component list must match.

Track firmware versions during R&D – ensure sample firmware matches documentation. If component substitutions occur, provide supporting evidence. Do an internal pre‑review before submission – catching design‑document inconsistencies early – reducing revisions.

  5. User Manual and Label Artwork

User manual:

·Operating instructions, supported band range.

·Target‑market language versions: English for Australia – multi‑language recommended for Europe.

·Functional descriptions must not exceed the certified band/capability scope.

Label artwork:

·Model, trademark, and certification mark positions.

·Follow mark‑size proportion rules strictly.

·Finalise vector files early – apply labels to samples – verify artwork matches physical samples.

Don't finalise manuals/labels just before shipping – rush jobs cause printing errors – leading to customs holds.

  6. Test Reports – The Key Item

·Performance testing: EN 303 345 – receiver sensitivity, adjacent‑channel selectivity, blocking, spurious.

·EMC: EN 301 489 series.

DAB+ receivers are unintentional radiators – no RF transmit testing.

·EU self‑declaration: lab with ISO 17025 accreditation is sufficient.

·Australia RCM: additional local lab‑accreditation requirements.

Confirm reports use current effective standard versions – cover all claimed bands and modes. Report versions must match the application. Before submission, check test coverage – supplement missing items.

  7. Samples and Declaration Documents

·Typically: 1 main test sample + 1 backup – both matching mass‑production hardware/software.

·DoC: list referenced standards. As a receiver, no band‑transmission declaration required.

Do not use engineering samples – firmware must match documentation. Include antennas, power supplies, cables, and other accessories. Mark the model number on the outer packaging – consistent with application documents. Keep an unboxing record – avoiding disputes over shipping damage.

  8. Document Organisation and Timeline

Create a separate folder per model – with consistent versioning and naming. Before submission, do a pre‑review – checking model consistency, standard‑version validity, and test‑report completeness.

DAB+ projects have many small documents – pre‑review reduces revision cycles. Archive all source files – derivative models can reuse templates. Create a submission checklist – confirming each item. After certification, maintain a tracker – hardware changes require compliance re‑assessment – reducing future rework.

For DAB+ certification documents, contact BlueAsia at 13534225140 (King) or email king.guo@cblueasia.com.