Broadcast Receiver Testing Overview

Note This content applies to the Windows Logo Kit (WLK). For the latest information using the new Windows Hardware Certification Kit (HCK), see Windows HCK User's Guide on the Windows Hardware Dev Center.

The procedures presented in this section outline the process for testing your Broadcast Receiver for the Windows Logo and Additional Qualifications Logo programs. These procedures use the Microsoft Windows Logo Kit (WLK) and Driver Test Manager (DTM). The terminology in the next table is used.

Table 1: Terminology and Abbreviation

Term Meaning

AQ

Additional Qualifications

BDA

Broadcast Driver Architecture

NTSC

National Television Systems Committee

ATSC

Advanced Television Systems Committee

PAL

Phase Alternating Line

SECAM

Sequential Color Avec (with) Memory

DVB

Digital Video Broadcasting

QAM

Quadrature Amplitude modulation

CA

Conditional Access

CAS

Conditional Access Source

DUT

Device Under Test

PBDA

Protected Broadcast Driver Architecture

Tuner capabilities

One of hybrid, combo, single

Form Factor

PCI, PCIe, USB

Broadcast receiver card

TV tuner card

To qualify for one of the Logo programs, you must run all of the tests that the DTM identifies as required for that Logo for that device. If your product provides bus-specific support, you must run the appropriate bus-specific tests in addition to the standard tests.

Note You must use the latest version of the WDK to compile your driver in order for it to pass testing and obtain a logo

Using the Test Procedure Help Topics

The Broadcast Receiver Testing Overview Topic is divided into the following types of topics:

Broadcast Receiver Testing Overview:

The overview topics describe the hardware, software, and tester knowledge requirements.

Preparing for Broadcast Receiver Testing:

The preparing topics describe how to configure the system or systems for Windows Logo testing and for Additional Qualifications testing.

Running the Broadcast Receiver Tests:

The running topics describe how to run to run the tests for your device or system.

Troubleshooting Broadcast Receiver Testing:

This section describes any troubleshooting steps to take if you run into problems.

Broadcast Receiver Tests

Documentation for the individual tests is in the Streaming Media and Broadcast Tests section. The tests that you need to run depend upon the capabilities of the device or system being tested, and the Logo for which you want your device to qualify.

Run time: Depending upon the test you are running, 5 minutes to 6 hours per test.

Hardware requirements

See the test description for each Broadcast Receiver test for hardware requirements.

Software requirements

See the test description for each Broadcast Receiver test for software requirements.

Tester knowledge requirements

Broadcast Receivers are TV tuner cards. These cards include analog receivers, digital receivers, combination (combo), or hybrid cards.

Testing for Broadcast Receivers covers the following analog broadcast receivers:

  • NTSC

  • NTSC_M_J

  • PAL

  • SECAM

Testing for Broadcast Receivers covers the following digital broadcast receivers:

  • ATSC

  • DVB-C

  • DVB-S

  • DVB-T

  • ISDB-T

  • ISDB-S

  • Proprietary

  • QAM

Hybrid tuner cards fall into both categories. You must receive Windows Logos for the analog and digital sides by specifying a Device Interface property. The next figure shows the logical representation of a Hybrid and a Combo tuner to the operating system.

The above figure does not refer to a tuner's internal architecture. Instead, it refers to the logical representation of the tuner device to the Windows operating system via device interfaces.

The correct method to distinguish a combo tuner from a hybrid tuner is to include a new device interface property called a TunerInstanceId in the driver INF file. This in turn, adds a registry key when the driver is installed. Windows uses the combination of the tuner's ContainerId and TunerInstanceId to determine compatibility between the analog and digital filters.

The important parts of the device's installation file (INF file) are highlighted in bold below to illustrate how to correctly add the device interface property to the INF file.

Adding the Analog TV Interface:

AddInterface={a799a800-a46d-11d0-a18c-00a02401dcd4},%TunerReferenceGuid%,NTSC_Interface,

The TunerInstanceID is the only change you need to make in the INF file for your device. The value must be a DWORD. Note that the value of 0 is reserved for system use. Also note that the values must be the different for Combo tuners, as noted below:

[NTSC_Interface]
AddReg=NTSC_Interface.AddReg

[NTSC_Interface.AddReg]
HKR,,CLSID,,%CLSID_CTVTunerFilter%
HKR,,FriendlyName,,%TunerFriendlyName%
;add tunerInstanceID entry
HKR,,TunerInstanceID,0x00010001,10 ;Note this value

;In the corresponding ATSC tuner filter do the following
;Digital BDA tuner filter
AddInterface={71985F48-1CA1-11d3-9CC8-00C04F7971E0},%BDATuneReferenceGuid%,BDATUNE_Interface,


[BDATUNE_Interface]
AddReg=BDATUNE_Interface.AddReg

[BDATUNE_Interface.AddReg]
HKR,,CLSID,,%Proxy.CLSID%; {17CCA71B-ECD7-11D0-B908-00A0C9223196}
HKR,,FriendlyName,,%BDATuneFriendlyName%
;add tunerInstanceID entry
HKR,,TunerInstanceID,0x00010001,11 ;Note this value is different

The next figure shows the logical representation of a Dual Hybrid tuner card to the operating system.

Notes:

  • The TunerInstanceId device interface property is a registry key setting required for Windows compatibility with hybrid tuners that have previously shipped. The TunerInstanceId device interface property is a qualifier used to match an analog tuner filter to its corresponding digital tuner filter on the same tuner. You can then configure Windows Media Center to use one tuner or the other, but not both tuners.

  • You can set TunerInstanceId to be any value between 1 and 0xffffffff.

  • Do not set TunerInstanceId to anything less than 1, which is reserved for system use. If a TunerInstanceId is not present in the INF file for a hybrid tuner that has already shipped, then Windows automatically uses a value of 0.

  • All combo tuners should also use the TunerInstanceId device interface property registry key to ensure compatibility with future versions of Windows Media Center. In the currently released version of Windows Media Center (Vista), this registry key has no effect because Vista does not support both PAL and DVB at the same time.

Windows Logo and Additional Qualifications Programs:

The Windows Logo program tests the tuner card and driver for an initial set of qualifications independent of Windows Media Center. The Additional Qualifications Logo program tests the tuner and driver for Microsoft Windows Media Center specific qualifications.

Program Contents:

The Broadcast Receiver Logo programs test common functionality in addition to specific tuner card tests. The tuner card must pass all of the functionality tests required for a Logo to receive a Windows Logo for the tuner card.

The Broadcast Receiver program includes the following tests:

  • Device Fundamental Tests

  • Broadcast Receiver Tests

  • CardBus Tests

The tests depend upon the capabilities of the device or system that you are testing. To see the complete list of tests that might be required for your device, see Broadcast Receiver Tests.

Broadcast Receiver Tests: The tests depend upon the capabilities of the device or system that you are testing. To see the complete list of tests that might be required for your device, see Broadcast Receiver Tests.

Protected Broadcast Driver Architecture:

You can use a Protected Broadcast Driver Architecture (PBDA) device and/or driver to extend the Media Center First Run experience. In doing this, you must meet the requirements set forth in the document available at Developing Protected Broadcast Drivers in Windows.

Build date: 9/14/2012