Pinnacle Input Devices Driver

Windows 10 Drivers The correct latest drivers of the compaitble devices are rather hidden on the Pinnacle site and don’t mention Windows 10 – but they do work. Don’t try to use anything that Windows offers you. 14.0.0.166 (64 bits) can be downloaded from Pinnacle HERE, or my mirror HERE. These Miro and Pinnacle cards were the original PCTV series, produced from December 1997 onwards. They are based on the Bt848 chip (Also see Bttv devices (bt848, bt878)). The PCTV Pro model includes an FM radio chip. These cards feature: TV input: RF connector for a PAL/NTSC/SECAM. To Pinnacle Video Transfer and turned on, any connected USB device, for. Example, your iPod®, is also powered or charged. For this to work properly, the. Connected USB device must also support this function. Note that you may require special device-specific USB cables. These cables are not included in the box contents.

Apr 27, 2012 Hardware drivers for Pinnacle / Dazzle. Studio video devices Note: The files contained in this package are hardware drivers only. Beside the driver, a compatible version of Studio is required. . Drivers for interfacing USB connected programs. Most products (8100s, 8200s, 8400s). If you have installed the drivers with a previous version of the installer, you will need to uninstall the drivers. To do this, go to Control Panel, Programs and Features, then uninstall both of the Microsoft Driver Kit - FTDI entries.

Pinnacle PCTV HD Card (800i)

A hybrid ATSCPCI card from Pinnacle.

Drivers are now included in the mainline kernel

1Overview/Features
2Making it Work
- 2.4Audio

Overview/Features

A hybrid device that supports analog, ATSC (8-VSB) and digital cable (QAM) TV sources. The card also supports analog A/V inputs, and has an IR remote control input.

It appears that it may be also being sold as the Yuan PG583Q. Yuan lists two models (PG583 and PG583Q) -- simply a wild guess, but perhaps the former uses a XC3028 (not QAM capable) and the later XC5000 (QAM capable) ?? The Yuan boards also have a connector of sorts on the back portion of the PCB that is not present on the Pinnacle board.

Components Used

800i's components

Xceive XC5000 (tuner & analog IF demodulator) [1]
Samsung S5H1409 (digital demodulator) [2]
Conexant CX23883 (A/V decoder & PCI bridge) [3]
Cirrus 5340 CZZ (audio ADC) [4]
Atmel ATMLH726 (8-pin eeprom)

Identification

PCI subsytem ID is: 11bd:0051

Output of lspci -vvnn:

Making it Work

Firmware

You MUST have the firmware for the XC5000 tuner installed for the 800i to function properly. Note the firmware directory may differ with some distros; consult your distro's documentation for the appropriate location)

If using Linux kernel 2.6.31 or you are using the latest http://linuxtv.org/hg/v4l-dvb tree:

If you are using an older kernel than 2.6.31 and not using the latest v4l-dvb code:

Drivers

Full support for the device is now in the mainline v4l-dvb repo. Both analog and digital TV are supported, and the remote control should also function properly now.

To download the latest v4l-dvb tree, simply select the bz2 or gz link on the top left of the page, then build them via running 'make' followed by 'make install'. More thorough downloading/building instructions can be found here.

Be sure to restart your computer before attempting to use the card.

Sample kernel output

Audio

OSS

The audio output of the card can be accessed through OSS typically via /dev/dsp1, however that number can of course vary with your system's configuration.

ALSA

Linux distributions have begun to leave out OSS support in their default kernel. Ubuntu as of 10.10 is an example of this.

The kernel module to enable ALSA support is cx88-alsa.

Once the appropriate module is loaded you should see this output from 'arecord -l' (note this sample is from a system with two identical cards installed):

Note the card names CX8801, and CX8801_1 for the two cards in the example system. Use the following for the ALSA device:

Card 1) ALSA:default:CARD=CX8801Card 2) ALSA:default:CARD=CX8801_1

Remote Control Support

The card uses the CX2388x's standard IR interface, and, it is fully supported now via the linux input layer. You may use LIRC with the input device driver option. See the 'Remote Controllers' article for more details on how to configure LIRC with remote controls that use the linux input layer.

External Links

Retrieved from 'https://www.linuxtv.org/wiki/index.php?title=Pinnacle_PCTV_HD_Card_(800i)&oldid=30855'

-->

Human Interface Devices (HID) is a device class definition to replace PS/2-style connectors with a generic USB driver to support HID devices such as keyboards, mice, game controllers, etc. Prior to HID, devices could only utilize strictly-defined protocols for mice and keyboards. Hardware innovation required either overloading data in an existing protocol or creating non-standard hardware with its own specialized driver. HID provided support for these “boot mode” devices while adding support for hardware innovation through extensible, standardized and easily-programmable interfaces.

HID devices today include a broad range of devices such as alphanumeric displays, bar code readers, volume controls on speakers/headsets, auxiliary displays, sensors and many others. Many hardware vendors also use HID for their proprietary devices.

HID began with USB but was designed to be bus-agnostic. It was designed for low latency, low bandwidth devices but with flexibility to specify the rate in the underlying transport. The specification for HID over USB was ratified by the USB-IF in 1996 and support over additional transports followed soon after. Details on currently supported transports can be found in HID Transports Supported in Windows. 3rd-party, vendor-specific transports are also allowed via custom transport drivers.

HID Concepts

HID consists of two fundamental concepts, a Report Descriptor, and Reports. Reports are the actual data that is exchanged between a device and a software client. The Report Descriptor describes the format and meaning the data that the device supports.

Reports

Applications and HID devices exchange data through Reports. There are three Report types: Input Reports, Output Reports, and Feature Reports.

Report Type	Description
Input Report	Data sent from the HID device to the application, typically when the state of a control changes.
Output Report	Data sent from the application to the HID device, for example to the LEDs on a keyboard.
Feature Report	Data that can be manually read and/or written, and are typically related to configuration information.

Each Top Level Collection defined in a Report Descriptor can contain zero (0) or more reports of each type.

Usage Tables

The USB-IF working group publishes HID Usage Tables that are part of the Report Descriptors that describe what HID devices are allowed to do. These HID Usage Tables contain a list with descriptions of Usages, which describe the intended meaning and use of a particular item described in the Report Descriptor. For example, a Usage is defined for the left button of a mouse. The Report Descriptor can define where in a Report an application can find the current state of the mouse’s left button. The Usage Tables are broken up into several name spaces, called Usage Pages. Each Usage Page describes a set of related Usages to help organize the document. The combination of a Usage Page and Usage define the Usage ID that uniquely identifies a specific Usage in the Usage Tables.