Hauppauge WinTV-NOVA-TD-Stick - Revision history

Angeld: /* Overview/Features */

2013-02-05T14:36:19Z

Overview/Features

← Older revision		Revision as of 14:36, 5 February 2013
Line 3:		Line 3:

	It is supported under Linux.		It is supported under Linux.
		+
		+	==Similar models==
		+
		+	Elgato EyeTV diversity is a clone of this usb stick

	==Overview/Features==		==Overview/Features==

Theli: /* A Comment on Possible Electromagnetic Interference (jarb1 at uk2 dot net) */

2012-12-07T07:04:46Z

A Comment on Possible Electromagnetic Interference (jarb1 at uk2 dot net)

← Older revision		Revision as of 07:04, 7 December 2012
Line 92:		Line 92:

	If Hauppauge read this, please retest these devices in a controlled environment under the CE EMC directive and delete this if you can not simulate.		If Hauppauge read this, please retest these devices in a controlled environment under the CE EMC directive and delete this if you can not simulate.
		+
		+	-- Jamesarbrown 12:01, 30 November 2008 (UTC)
		+
		+
		+	Thank you for the above description! I have a newer revision of this stick, but run into the same problem. The stick didn't work on two different PCs with two different operating systems.
		+	Then I've read your comment and connected the stick using the USB extension and used a better shielded cable and it started to work.
		+
		+	-- [[User:Theli\|Theli]] 08:04, 7 December 2012 (CET)

	== External links ==		== External links ==

Philpem: /* Specific to the model */

2010-12-10T17:48:58Z

Specific to the model

← Older revision		Revision as of 17:48, 10 December 2010
Line 68:		Line 68:

	At least two people have indicated on the mailing list ([http://linuxtv.org/pipermail/linux-dvb/2008-April/025309.html 8 April 2008] and [http://linuxtv.org/pipermail/linux-dvb/2008-April/025420.html 12 April 2008]) that trouble picking up reception on low power muxes can be helped by adding an attenuator. It is thought that this may be caused by the internal amplifier taking in to account the strongest muxes only. Weakening the overall signal appears to increase the amplification of all muxes, so improving reception.		At least two people have indicated on the mailing list ([http://linuxtv.org/pipermail/linux-dvb/2008-April/025309.html 8 April 2008] and [http://linuxtv.org/pipermail/linux-dvb/2008-April/025420.html 12 April 2008]) that trouble picking up reception on low power muxes can be helped by adding an attenuator. It is thought that this may be caused by the internal amplifier taking in to account the strongest muxes only. Weakening the overall signal appears to increase the amplification of all muxes, so improving reception.
		+
		+	==== Signal power ====
		+
		+	The Nova-TD-Stick (and to a lesser degree its "brother", the Nova-T-500) have a very limited dynamic range on the input connectors. This means that if you feed the TD-Stick with an extremely strong signal, you'll see the signal strength 'stick' at 100%, but the TD-Stick will never achieve a signal lock. This typically happens when using a masthead amplifier or distribution amplifier to feed multiple TVs from a single TV aerial. Ideally the masthead amplifier should be turned down to a very low setting, and if necessary followed with a 6dB or 12dB (as necessary) attenuator. Buy a few attenuators (3dB, 6dB, 12dB and 24dB are the common versions) and mix-and-match until you get something that works. As a general rule:
		+
		+	* If the signal strength is less than 25%, then your aerial isn't connected (or the signal is too weak for the TD-Stick to detect).
		+	* If the signal strength is 100% and you haven't got a channel lock (or the data appears to be corrupted -- unnamed channels, etc.), then the signal is too strong. Turn down the amplifier, or install an attenuator or two.
		+	* Full-sized TVs have much better tuners (typically wide dynamic range superheterodyne tuners) than the Microtune silicon tuners in the TD Stick. Bear in mind that your TV can probably handle overly weak or strong signals better than your TD-Stick.
		+	* If you know someone who owns a TV strength meter or spectrum analyser, ask to borrow it for an afternoon. A signal strength of between 60 and 75 dBuV (decibel-microvolts) measured at the antenna outlet is generally pretty close to optimum for TV receivers. Perhaps someone with a variable attenuator, a spectrum analyser and a TD-Stick could figure out the actual signal-lock range of the Microtune tuner in the TD-Stick (though this would be a largely academic exercise).
		+
		+	--[[User:Philpem\|Philpem]] 17:48, 10 December 2010 (UTC)

	==== A Comment on Possible Electromagnetic Interference (jarb1 at uk2 dot net) ====		==== A Comment on Possible Electromagnetic Interference (jarb1 at uk2 dot net) ====

Jimbley: /* Components Used */ Added Microtune MT2266 link

2009-06-02T21:21:57Z

Components Used: Added Microtune MT2266 link

← Older revision		Revision as of 21:21, 2 June 2009
Line 13:		Line 13:
	===Components Used===		===Components Used===

-	* 2× Microtune MT2266 tuners	+	* 2× [[Microtune MT2266]] tuners
	* Dibcom DiB7700P DVB-T demodulator ([http://dibcom.info/Website/site/eng_accueil_applicationsproducts_products_chipset.htm DiB7070P?] no such chip as 7700P!)		* Dibcom DiB7700P DVB-T demodulator ([http://dibcom.info/Website/site/eng_accueil_applicationsproducts_products_chipset.htm DiB7070P?] no such chip as 7700P!)

Jimbley: Added category: DVB-T USB Devices

2009-05-04T02:36:45Z

Added category: DVB-T USB Devices

← Older revision		Revision as of 02:36, 4 May 2009
Line 85:		Line 85:
	* [http://www.hauppauge.co.uk/site/products/data_novatdstick.html Hauppauge UK product page]		* [http://www.hauppauge.co.uk/site/products/data_novatdstick.html Hauppauge UK product page]

-	[[Category:DVB-T]]	+	[[Category:DVB-T USB Devices]]
-	~~[[Category:Hardware]]~~	+
-	~~[[Category:~~USB]]	+

Hlangos: /* Specific Remote control support */ removed information that is already in the template

2009-04-24T12:07:14Z

Specific Remote control support: removed information that is already in the template

← Older revision		Revision as of 12:07, 24 April 2009
Line 27:		Line 27:

	==== Specific Remote control support ====		==== Specific Remote control support ====
-
-	There is no need to compile and load any lirc modules; the remote is detected along with the tuner and is registered as a USB input device. If you are using udev or devfs then this means that the device should be linked to one of the /dev/input/event* device nodes and a simple rule will create a named symlink.

	If you do want to use lirc set it up to use the that device as ''DEVICE'' and ''devinput'' as ''DRIVER''. Then try one of the config files below.		If you do want to use lirc set it up to use the that device as ''DEVICE'' and ''devinput'' as ''DRIVER''. Then try one of the config files below.
Line 35:		Line 33:
	While key repeats are still buggy irrecord will fail if you obey its instructions and hold down an arbitrary key; instead, when you are told to hold an arbitrary key, press an arbitrary key repeatedly (the same one, not different ones each time) until irrecord reports that it has found the gap length.		While key repeats are still buggy irrecord will fail if you obey its instructions and hold down an arbitrary key; instead, when you are told to hold an arbitrary key, press an arbitrary key repeatedly (the same one, not different ones each time) until irrecord reports that it has found the gap length.

-	As long as the evdev module is loaded, the remote will be treated as a usb keyboard and this means that you can avoid using lirc. Many of the keys generate keycodes which are not mapped to anything, by default, in X; you can use xev to find the keycodes and xmodmap to map them to useful symbols. Unfortunately, some keys generate keycodes that X doesn't seem to recognise at all (on my set-up, at least) and the device does not support keymaps, or this would be easy to fix.

Hlangos: /* Specific Remote control support */ dunno if they are fixed in general. i get two for one button presses but that may be a problem of the terratec

2009-04-24T11:49:22Z

Specific Remote control support: dunno if they are fixed in general. i get two for one button presses but that may be a problem of the terratec

← Older revision		Revision as of 11:49, 24 April 2009
Line 33:		Line 33:
	If it doesn't work then you will need to use irrecord to generate a config file.		If it doesn't work then you will need to use irrecord to generate a config file.

-	While key repeats are still buggy ~~(2009-04-24)~~ irrecord will fail if you obey its instructions and hold down an arbitrary key; instead, when you are told to hold an arbitrary key, press an arbitrary key repeatedly (the same one, not different ones each time) until irrecord reports that it has found the gap length.	+	While key repeats are still buggy irrecord will fail if you obey its instructions and hold down an arbitrary key; instead, when you are told to hold an arbitrary key, press an arbitrary key repeatedly (the same one, not different ones each time) until irrecord reports that it has found the gap length.

	As long as the evdev module is loaded, the remote will be treated as a usb keyboard and this means that you can avoid using lirc. Many of the keys generate keycodes which are not mapped to anything, by default, in X; you can use xev to find the keycodes and xmodmap to map them to useful symbols. Unfortunately, some keys generate keycodes that X doesn't seem to recognise at all (on my set-up, at least) and the device does not support keymaps, or this would be easy to fix.		As long as the evdev module is loaded, the remote will be treated as a usb keyboard and this means that you can avoid using lirc. Many of the keys generate keycodes which are not mapped to anything, by default, in X; you can use xev to find the keycodes and xmodmap to map them to useful symbols. Unfortunately, some keys generate keycodes that X doesn't seem to recognise at all (on my set-up, at least) and the device does not support keymaps, or this would be easy to fix.
Line 45:		Line 45:
	{{RemoteControlSupport:TerraTecGrayOrange}}		{{RemoteControlSupport:TerraTecGrayOrange}}
	-->		-->
		+
	==== Sample kernel output ====		==== Sample kernel output ====

Hlangos: added the two possible remotes. that i stripped from the making-it-work template. could somebody who owns this device remove the one that does not apply here?

2009-04-24T10:47:20Z

added the two possible remotes. that i stripped from the making-it-work template. could somebody who owns this device remove the one that does not apply here?

← Older revision		Revision as of 10:47, 24 April 2009
Line 24:		Line 24:
	{{Making-it-work:dvb-usb-dib0700}}		{{Making-it-work:dvb-usb-dib0700}}

-	=== Specific Remote control support ===	+	=== Specific to the model ===
		+
		+	==== Specific Remote control support ====

	There is no need to compile and load any lirc modules; the remote is detected along with the tuner and is registered as a USB input device. If you are using udev or devfs then this means that the device should be linked to one of the /dev/input/event* device nodes and a simple rule will create a named symlink.		There is no need to compile and load any lirc modules; the remote is detected along with the tuner and is registered as a USB input device. If you are using udev or devfs then this means that the device should be linked to one of the /dev/input/event* device nodes and a simple rule will create a named symlink.

-	If you do want to use ~~lircd~~ then you will need to use irrecord to ~~generared~~ a config file ~~as the existing files do not match the Nova-TD remote~~. irrecord will fail if you obey its instructions and hold down an arbitrary key; instead, when you are told to hold an arbitrary key, press an arbitrary key repeatedly (the same one, not different ones each time) until irrecord reports that it has found the gap length.	+	If you do want to use lirc set it up to use the that device as ''DEVICE'' and ''devinput'' as ''DRIVER''. Then try one of the config files below.
		+	If it doesn't work then you will need to use irrecord to generate a config file.
		+
		+	While key repeats are still buggy (2009-04-24) irrecord will fail if you obey its instructions and hold down an arbitrary key; instead, when you are told to hold an arbitrary key, press an arbitrary key repeatedly (the same one, not different ones each time) until irrecord reports that it has found the gap length.

	As long as the evdev module is loaded, the remote will be treated as a usb keyboard and this means that you can avoid using lirc. Many of the keys generate keycodes which are not mapped to anything, by default, in X; you can use xev to find the keycodes and xmodmap to map them to useful symbols. Unfortunately, some keys generate keycodes that X doesn't seem to recognise at all (on my set-up, at least) and the device does not support keymaps, or this would be easy to fix.		As long as the evdev module is loaded, the remote will be treated as a usb keyboard and this means that you can avoid using lirc. Many of the keys generate keycodes which are not mapped to anything, by default, in X; you can use xev to find the keycodes and xmodmap to map them to useful symbols. Unfortunately, some keys generate keycodes that X doesn't seem to recognise at all (on my set-up, at least) and the device does not support keymaps, or this would be easy to fix.


-	=== Sample kernel output ===	+	{{RemoteControlSupport:HauppaugeSnowboard}}
		+	{{RemoteControlSupport:HauppaugeSilverA415-HPG-WE-A}}
		+	<!--
		+	{{RemoteControlSupport:HauppaugeSnowboard}}
		+	{{RemoteControlSupport:HauppaugeSilverA415-HPG-WE-A}}
		+	{{RemoteControlSupport:TerraTecGrayOrange}}
		+	-->
		+	==== Sample kernel output ====

	From 2.6.20-16-generic with drivers compiled from repository 4th Jan 07:		From 2.6.20-16-generic with drivers compiled from repository 4th Jan 07:
Line 49:		Line 61:
	[ 68.220812] dvb_usb_dib0700 2-4:1.0: resuming		[ 68.220812] dvb_usb_dib0700 2-4:1.0: resuming

-	=== Troubleshooting ===	+	==== Troubleshooting ====

	It seems, that there exist USB-problems with mainboards using an AMD690g chipset concerning USB-disconnects. This problem is described [http://209.85.165.104/search?q=cache:KWnzteJ-zZkJ:www.hauppauge.co.uk/board/archive/index.php%3Ft-14247.html+nova-td+amd+690g&hl=it&ct=clnk&cd=1 here] and on the [http://linuxtv.org/pipermail/linux-dvb/2008-March/024436.html linux-dvb Mailing list]. (Disable the remote sensor?) --[[User:Doc murke\|Doc murke]] 09:40, 13 March 2008 (CET)		It seems, that there exist USB-problems with mainboards using an AMD690g chipset concerning USB-disconnects. This problem is described [http://209.85.165.104/search?q=cache:KWnzteJ-zZkJ:www.hauppauge.co.uk/board/archive/index.php%3Ft-14247.html+nova-td+amd+690g&hl=it&ct=clnk&cd=1 here] and on the [http://linuxtv.org/pipermail/linux-dvb/2008-March/024436.html linux-dvb Mailing list]. (Disable the remote sensor?) --[[User:Doc murke\|Doc murke]] 09:40, 13 March 2008 (CET)
Line 55:		Line 67:
	This problem should be fixed now- see [http://www.linuxtv.org/pipermail/linux-dvb/2008-April/025150.html this information]. --[[User:Indulis\|Indulis]] 09:39, 24 July 2008 (CEST)		This problem should be fixed now- see [http://www.linuxtv.org/pipermail/linux-dvb/2008-April/025150.html this information]. --[[User:Indulis\|Indulis]] 09:39, 24 July 2008 (CEST)

-	=== Low power muxes ===	+	==== Low power muxes ====

	At least two people have indicated on the mailing list ([http://linuxtv.org/pipermail/linux-dvb/2008-April/025309.html 8 April 2008] and [http://linuxtv.org/pipermail/linux-dvb/2008-April/025420.html 12 April 2008]) that trouble picking up reception on low power muxes can be helped by adding an attenuator. It is thought that this may be caused by the internal amplifier taking in to account the strongest muxes only. Weakening the overall signal appears to increase the amplification of all muxes, so improving reception.		At least two people have indicated on the mailing list ([http://linuxtv.org/pipermail/linux-dvb/2008-April/025309.html 8 April 2008] and [http://linuxtv.org/pipermail/linux-dvb/2008-April/025420.html 12 April 2008]) that trouble picking up reception on low power muxes can be helped by adding an attenuator. It is thought that this may be caused by the internal amplifier taking in to account the strongest muxes only. Weakening the overall signal appears to increase the amplification of all muxes, so improving reception.

-	== A Comment on Possible Electromagnetic Interference (jarb1 at uk2 dot net) ==	+	==== A Comment on Possible Electromagnetic Interference (jarb1 at uk2 dot net) ====
	These devices appear to be susceptible to EM interference. This is in UK on DVB-T reception, 50Hz, 240VAC. Having two of these fed from coax Splitter into the back of a decent case (Silverstone LC04) it was found :-		These devices appear to be susceptible to EM interference. This is in UK on DVB-T reception, 50Hz, 240VAC. Having two of these fed from coax Splitter into the back of a decent case (Silverstone LC04) it was found :-

Jamesarbrown: EM Noise on Device

2008-11-30T12:01:20Z

EM Noise on Device

← Older revision		Revision as of 12:01, 30 November 2008
Line 58:		Line 58:

	At least two people have indicated on the mailing list ([http://linuxtv.org/pipermail/linux-dvb/2008-April/025309.html 8 April 2008] and [http://linuxtv.org/pipermail/linux-dvb/2008-April/025420.html 12 April 2008]) that trouble picking up reception on low power muxes can be helped by adding an attenuator. It is thought that this may be caused by the internal amplifier taking in to account the strongest muxes only. Weakening the overall signal appears to increase the amplification of all muxes, so improving reception.		At least two people have indicated on the mailing list ([http://linuxtv.org/pipermail/linux-dvb/2008-April/025309.html 8 April 2008] and [http://linuxtv.org/pipermail/linux-dvb/2008-April/025420.html 12 April 2008]) that trouble picking up reception on low power muxes can be helped by adding an attenuator. It is thought that this may be caused by the internal amplifier taking in to account the strongest muxes only. Weakening the overall signal appears to increase the amplification of all muxes, so improving reception.
		+
		+	== A Comment on Possible Electromagnetic Interference (jarb1 at uk2 dot net) ==
		+	These devices appear to be susceptible to EM interference. This is in UK on DVB-T reception, 50Hz, 240VAC. Having two of these fed from coax Splitter into the back of a decent case (Silverstone LC04) it was found :-
		+
		+	- Leave the device and Co-ax feeding the device anywhere near the case power leads etc and experience screen freezes, pixelation and sound stutter.
		+
		+	- Plugging directly into the case on the USB port directly below the ethernet port picked up noise (Presumably from the ethernet Unshielded Twisted Pair 100M). Coaxes on this test were well routed so strongly believe this is the device.
		+
		+	To solve, use the USB extension leads from the box to get the actual device away from the case and run the coaxial cable well away from the rest of your cables.
		+
		+	Once this was done a 100% perfect picture 100% of the time.
		+
		+	If Hauppauge read this, please retest these devices in a controlled environment under the CE EMC directive and delete this if you can not simulate.

	== External links ==		== External links ==

Dirks: /* Identification */ Another USB ID added

2008-10-27T19:05:07Z

Identification: Another USB ID added

← Older revision		Revision as of 19:05, 27 October 2008
Line 19:		Line 19:

	This device's USB ID is 2040:9580.		This device's USB ID is 2040:9580.
-	Additional information: I have bought a WinTV-NOVA-TD-Stick that has a different USB ID: 2040:5200.	+
		+	Additional information: I have bought a WinTV-NOVA-TD-Stick that has a different USB ID: 2040:5200. [[User:Dirks\|Dirks]] 20:05, 27 October 2008 (CET)

	{{Making-it-work:dvb-usb-dib0700}}		{{Making-it-work:dvb-usb-dib0700}}