Difference between revisions of "Hauppauge WinTV-NOVA-T-USB2"

From LinuxTVWiki
Jump to navigation Jump to search
(New page: Probably you want to read Hauppauge WinTV-NOVA-T-CE-Stick)
 
 
(10 intermediate revisions by 6 users not shown)
Line 1: Line 1:
  +
[[Image:Hauppauge_WinTV-NOVA-T-USB2.jpg|thumb|250px|WinTV-Nova-T-USB2]]
Probably you want to read [[Hauppauge WinTV-NOVA-T-CE-Stick]]
 
  +
  +
A [[DVB-T]] [[DVB-T USB Devices|USB 2.0 device]] from [[Hauppauge]].
  +
  +
It is supported under Linux since kernel 2.6.12rc3.
  +
  +
==Overview/Features==
  +
These devices are clones of a DVB-T USB2.0 reference design made by [[DiBcom]]. There are actually a couple of different variants of the device, but all should be supported.
  +
  +
===Components Used===
  +
* [[DiB3000P|DiBcom 3000P]]
  +
  +
===Identification===
  +
* the older variant has a USB ID of: 9300 & 9301 (for cold and warm state)
  +
  +
It has a MAC address.
  +
  +
==Making it Work==
  +
  +
===Firmware===
  +
It requires the firmware file ''dvb-usb-nova-t-usb2-02.fw''.
  +
  +
There are at least two variants of this firmware:
  +
  +
* https://github.com/osmc/dvb-firmware-osmc/raw/master/dvb-usb-nova-t-usb2-02.fw, sha256 ''25c76ff894b70dfe81b392f469bdd80a7c7ff3292a45c242abbf63b59dcb02fb'', ''11023'' bytes, allows the remote control to work
  +
* http://steventoth.net/linux/nova-t-usb2/dvb-usb-nova-t-usb2-02.fw sha256, ''c87e2e78240e13649e8bdc42f94502699a4448cfa2ac9b137f1d9d70686f3faa'', ''7558'' bytes, does not allow remote control to work
  +
  +
===Drivers===
  +
The following drivers are needed for these devices:
  +
- dib3000mc.ko
  +
- dvb-usb.ko
  +
- dvb-usb-dibusb-common.ko
  +
- dvb-usb-dibusb-mc-common.kp
  +
- dvb-usb-nova-t-usb2.ko
  +
  +
===Remote Control===
  +
The remote control is supported by current Linux kernels together with the abovementioned firmware and drivers.
  +
  +
Event codes reported by ''evtest'' are as follows:
  +
  +
Event code 2 (KEY_1)
  +
Event code 3 (KEY_2)
  +
Event code 4 (KEY_3)
  +
Event code 5 (KEY_4)
  +
Event code 6 (KEY_5)
  +
Event code 7 (KEY_6)
  +
Event code 8 (KEY_7)
  +
Event code 9 (KEY_8)
  +
Event code 10 (KEY_9)
  +
Event code 11 (KEY_0)
  +
Event code 41 (KEY_GRAVE)
  +
Event code 55 (KEY_KPASTERISK)
  +
Event code 103 (KEY_UP)
  +
Event code 105 (KEY_LEFT)
  +
Event code 106 (KEY_RIGHT)
  +
Event code 108 (KEY_DOWN)
  +
Event code 113 (KEY_MUTE)
  +
Event code 114 (KEY_VOLUMEDOWN)
  +
Event code 115 (KEY_VOLUMEUP)
  +
Event code 116 (KEY_POWER)
  +
Event code 119 (KEY_PAUSE)
  +
Event code 128 (KEY_STOP)
  +
Event code 139 (KEY_MENU)
  +
Event code 158 (KEY_BACK)
  +
Event code 167 (KEY_RECORD)
  +
Event code 168 (KEY_REWIND)
  +
Event code 207 (KEY_PLAY)
  +
Event code 208 (KEY_FASTFORWARD)
  +
Event code 352 (KEY_OK)
  +
Event code 354 (KEY_GOTO)
  +
Event code 363 (KEY_CHANNEL)
  +
Event code 365 (KEY_EPG)
  +
Event code 377 (KEY_TV)
  +
Event code 385 (KEY_RADIO)
  +
Event code 392 (KEY_AUDIO)
  +
Event code 393 (KEY_VIDEO)
  +
Event code 398 (KEY_RED)
  +
Event code 399 (KEY_GREEN)
  +
Event code 400 (KEY_YELLOW)
  +
Event code 401 (KEY_BLUE)
  +
Event code 402 (KEY_CHANNELUP)
  +
Event code 403 (KEY_CHANNELDOWN)
  +
Event code 405 (KEY_LAST)
  +
Event code 407 (KEY_NEXT)
  +
Event code 442 (KEY_IMAGES)
  +
  +
The keys with event code above 255 are not recognized by X11. For a solution, refer to: [http://www.mythtv.org/wiki/Remapping_remote_control_key_codes_greater_than_255]
  +
  +
Do not try some other solution like LIRC, this one works easiest.
  +
  +
==External Links==
  +
* [https://www.hauppauge.co.uk/site/support/support_all.html?prod=54 Hauppauge WinTV-NOVA-T-USB2 support page]
  +
* [https://www.mythtv.org/wiki/Hauppauge_WinTV-USB2 MythTV WinTV-NOVA-T-USB2 page]
  +
  +
[[Category:DVB-T USB Devices]]

Latest revision as of 01:40, 5 August 2020

WinTV-Nova-T-USB2

A DVB-T USB 2.0 device from Hauppauge.

It is supported under Linux since kernel 2.6.12rc3.

Overview/Features

These devices are clones of a DVB-T USB2.0 reference design made by DiBcom. There are actually a couple of different variants of the device, but all should be supported.

Components Used

Identification

  • the older variant has a USB ID of: 9300 & 9301 (for cold and warm state)

It has a MAC address.

Making it Work

Firmware

It requires the firmware file dvb-usb-nova-t-usb2-02.fw.

There are at least two variants of this firmware:

Drivers

The following drivers are needed for these devices:

 - dib3000mc.ko
 - dvb-usb.ko
 - dvb-usb-dibusb-common.ko
 - dvb-usb-dibusb-mc-common.kp
 - dvb-usb-nova-t-usb2.ko

Remote Control

The remote control is supported by current Linux kernels together with the abovementioned firmware and drivers.

Event codes reported by evtest are as follows:

   Event code 2 (KEY_1)
   Event code 3 (KEY_2)
   Event code 4 (KEY_3)
   Event code 5 (KEY_4)
   Event code 6 (KEY_5)
   Event code 7 (KEY_6)
   Event code 8 (KEY_7)
   Event code 9 (KEY_8)
   Event code 10 (KEY_9)
   Event code 11 (KEY_0)
   Event code 41 (KEY_GRAVE)
   Event code 55 (KEY_KPASTERISK)
   Event code 103 (KEY_UP)
   Event code 105 (KEY_LEFT)
   Event code 106 (KEY_RIGHT)
   Event code 108 (KEY_DOWN)
   Event code 113 (KEY_MUTE)
   Event code 114 (KEY_VOLUMEDOWN)
   Event code 115 (KEY_VOLUMEUP)
   Event code 116 (KEY_POWER)
   Event code 119 (KEY_PAUSE)
   Event code 128 (KEY_STOP)
   Event code 139 (KEY_MENU)
   Event code 158 (KEY_BACK)
   Event code 167 (KEY_RECORD)
   Event code 168 (KEY_REWIND)
   Event code 207 (KEY_PLAY)
   Event code 208 (KEY_FASTFORWARD)
   Event code 352 (KEY_OK)
   Event code 354 (KEY_GOTO)
   Event code 363 (KEY_CHANNEL)
   Event code 365 (KEY_EPG)
   Event code 377 (KEY_TV)
   Event code 385 (KEY_RADIO)
   Event code 392 (KEY_AUDIO)
   Event code 393 (KEY_VIDEO)
   Event code 398 (KEY_RED)
   Event code 399 (KEY_GREEN)
   Event code 400 (KEY_YELLOW)
   Event code 401 (KEY_BLUE)
   Event code 402 (KEY_CHANNELUP)
   Event code 403 (KEY_CHANNELDOWN)
   Event code 405 (KEY_LAST)
   Event code 407 (KEY_NEXT)
   Event code 442 (KEY_IMAGES)

The keys with event code above 255 are not recognized by X11. For a solution, refer to: [1]

Do not try some other solution like LIRC, this one works easiest.

External Links