Project

General

Profile

search usb dual DVB-T tuner compatible with raspbian & tvheadend on Rpi4

Added by Samquad Samquad over 3 years ago

Hello
I have a Pi4 with a pi hat TV single tuner and i need 2 tuner.
I have tried other usb tuner which I cannot get to work with TvHeadend. I asked for help on the forum but no one answered.
Where can we find the list of USB dual DVB-T tuners compatible with TvHeadend?
hauppauge wintv-duet dual dvb-t receiver seems not compatible with Tvheadend

Thank you


Replies (15)

RE: search usb dual DVB-T tuner compatible with raspbian & tvheadend on Rpi4 - Added by Lloyd Adams over 3 years ago

Hi

I've been using Pi4 with Tvheadend and Hauppauge dual tuner for just over a year now. This is the tuner I used: "Hauppauge 01663 WinTV Watch One Freeview HD". (https://www.amazon.co.uk/gp/product/B07C7YNWJ1/ref=ppx_yo_dt_b_search_asin_title?ie=UTF8&psc=1)

Works really well. Boot from SD. Two HDDs RAID1, and the one dual tuner. I was going to use two tuners, but never got around to buying the 2nd.

The key might be the firmware. Try looking at this page to start with: https://www.linuxtv.org/wiki/index.php/Hauppauge_WinTV-dualHD

RE: search usb dual DVB-T tuner compatible with raspbian & tvheadend on Rpi4 - Added by Samquad Samquad over 3 years ago

Hi

I have this Hauppauge tuner: [[https://www.linuxtv.org/wiki/index.php/Hauppauge_WinTV-Duet-HD-Stick]]

While doing some research I came across this link [[https://discourse.osmc.tv/t/hauppauge-wintv-duet-dual-dvb-t-receiver/77574/22]]

It seems that my problem with this hauppauge WinTV Duet HD which cannot find any channel, could come from the version of Tvheadend installed on my RPI under raspbian.

I am using the official Tvheadend repository on raspbian with command line:

sudo apt-get install tvheadend

Before doing anything, do you recommend another deposit that would be more up to date?

RE: search usb dual DVB-T tuner compatible with raspbian & tvheadend on Rpi4 - Added by Lloyd Adams over 3 years ago

Looking back at my notes, I originally installed according to this link: https://dirtyoptics.com/raspberry-pi-tv-server-using-tvheadend/

But I am running 4.3-1857~g221c29b40 (2019-11-28T21:26:27+0000), which I may have got from here: https://phillw.net/mark/incoming/deb_packages/tvheadend/

Sorry but my memory is bit vague.

I think the tuner needs to have firmware loaded at boot. Do you see the firmware being loaded in dmesg?

RE: search usb dual DVB-T tuner compatible with raspbian & tvheadend on Rpi4 - Added by Samquad Samquad over 3 years ago

Thank you Lloyd

I just prepared an RPI3 under raspbian with Tvheadend 4.3-1857 ((the link you gave me)

My dual tuner is recognized but the scan does not find any channel.

Dmesg return:

[    8.379893] dib0700: firmware started successfully.
[    8.895057] dvb-usb: found a 'Hauppauge Nova-TD Stick (52009)' in warm state.
[    8.895845] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
[    8.897251] dvbdev: DVB: registering new adapter (Hauppauge Nova-TD Stick (52009))
[    8.897314] usb 1-1.3: media controller created
[    8.900774] dvbdev: dvb_create_media_entity: media entity 'dvb-demux' registered.
[    9.310717] usb 1-1.3: DVB: registering adapter 0 frontend 0 (DiBcom 7000PC)...
[    9.310772] dvbdev: dvb_create_media_entity: media entity 'DiBcom 7000PC' registered.
[    9.581443] dib0070: DiB0070: successfully identified
[    9.583836] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
[    9.597278] dvbdev: DVB: registering new adapter (Hauppauge Nova-TD Stick (52009))
[    9.597323] usb 1-1.3: media controller created
[    9.601248] dvbdev: dvb_create_media_entity: media entity 'dvb-demux' registered.
[    9.867516] usb 1-1.3: DVB: registering adapter 1 frontend 0 (DiBcom 7000PC)...
[    9.867570] dvbdev: dvb_create_media_entity: media entity 'DiBcom 7000PC' registered.
[   10.020826] random: crng init done
[   10.020847] random: 7 urandom warning(s) missed due to ratelimiting
[   10.121339] dib0070: DiB0070: successfully identified
[   10.124290] Registered IR keymap rc-dib0700-rc5
[   10.132454] rc rc0: Hauppauge Nova-TD Stick (52009) as /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.3/rc/rc0
[   10.133345] rc rc0: lirc_dev: driver dib0700 registered at minor = 0, scancode receiver, no transmitter
[   10.134724] input: Hauppauge Nova-TD Stick (52009) as /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.3/rc/rc0/input0
[   10.135518] dvb-usb: schedule remote query interval to 50 msecs.
[   10.135544] dvb-usb: Hauppauge Nova-TD Stick (52009) successfully initialized and connected.
[   10.136020] usbcore: registered new interface driver dvb_usb_dib0700
[  

RE: search usb dual DVB-T tuner compatible with raspbian & tvheadend on Rpi4 - Added by Lloyd Adams over 3 years ago

Does tvh find the adaptors, networks and muxes?

RE: search usb dual DVB-T tuner compatible with raspbian & tvheadend on Rpi4 - Added by Lloyd Adams over 3 years ago

Getting out of my depth I'm afraid. Have you tried to turn on debug for modules linuxdvb and mpegts?

I did spot this thread (https://discourse.osmc.tv/t/hauppauge-nova-td-muxes-scan-fail/72534/3), which had this as the last post:

To get mine working, I also had to alter /etc/modprobe.d/options.conf (which didn’t exist)
Create the lines:
options dvb_usb disable-rc-polling=1
options dvb_usb_dib0700 force_lna_activation=1
And then reboot - scanned fine after that.

Also, that looks like a lot of muxes. I don't know where you are located, but did you load one of the predefined sets?

RE: search usb dual DVB-T tuner compatible with raspbian & tvheadend on Rpi4 - Added by Samquad Samquad over 3 years ago

I live in France.
I don't know how to activate debug mode for linuxdvb and mpegts modules.
I added the 2 lines in "/etc/modprobe.d/options.conf" file I created but the scan finds nothing.

RE: search usb dual DVB-T tuner compatible with raspbian & tvheadend on Rpi4 - Added by Lloyd Adams over 3 years ago

Debug mode - Under Debugging tab, enter mpegts,linuxdvb in the debug subsystems box, either give it a file to output, or select to output to syslog, and hit apply.

I'd then force a rescan on the network and see if the debug output gives any clues.

RE: search usb dual DVB-T tuner compatible with raspbian & tvheadend on Rpi4 - Added by Samquad Samquad over 3 years ago

Thank you Lloyd.

Here is the list of frequencies used by the nearest dvbt-t transmitter

C 29 = 538 Mhz
C 47 = 682 Mhz
C 26 = 514 Mhz
C 31 = 554 Mhz
C 44 = 658 Mhz
C 23 = 490 Mhz

I have attached the log debbug file recorded during the force scan

Can you analyze the log on these frequencies?

thanks

tvheadend.log (77.6 KB) tvheadend.log log filtering 'mpegts,linuxdvb'

RE: search usb dual DVB-T tuner compatible with raspbian & tvheadend on Rpi4 - Added by Lloyd Adams over 3 years ago

Nothing obvious in the log. Can you post the output from dmesg |egrep "firmware|dvb|frontend|usb"

Have you tried the receiver with any other software, such as under Windows?

And have you tried any of the test software, such as https://www.linuxtv.org/wiki/index.php/Testing_your_DVB_device ?

RE: search usb dual DVB-T tuner compatible with raspbian & tvheadend on Rpi4 - Added by Samquad Samquad over 3 years ago

dmesg |egrep "firmware|dvb|frontend|usb" return

[    0.080131] raspberrypi-firmware soc:firmware: Attached to firmware from 2021-01-27T22:26:53, variant start
[    0.090148] raspberrypi-firmware soc:firmware: Firmware hash is 99d9a48302e4553cff3688692bb7e9ac760a03fa
[    0.142130] usbcore: registered new interface driver usbfs
[    0.142196] usbcore: registered new interface driver hub
[    0.142267] usbcore: registered new device driver usb
[    2.021404] usbcore: registered new interface driver lan78xx
[    2.021472] usbcore: registered new interface driver smsc95xx
[    2.951132] dwc_otg 3f980000.usb: DWC OTG Controller
[    2.951171] dwc_otg 3f980000.usb: new USB bus registered, assigned bus number 1
[    2.951224] dwc_otg 3f980000.usb: irq 89, io mem 0x00000000
[    2.951675] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.10
[    2.951693] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    2.951708] usb usb1: Product: DWC OTG Controller
[    2.951723] usb usb1: Manufacturer: Linux 5.10.11-v7+ dwc_otg_hcd
[    2.951738] usb usb1: SerialNumber: 3f980000.usb
[    2.954130] usbcore: registered new interface driver usb-storage
[    2.962434] usbcore: registered new interface driver usbhid
[    2.962446] usbhid: USB HID core driver
[    3.374499] usb 1-1: new high-speed USB device number 2 using dwc_otg
[    3.614887] usb 1-1: New USB device found, idVendor=0424, idProduct=9514, bcdDevice= 2.00
[    3.614913] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[    3.934481] usb 1-1.1: new high-speed USB device number 3 using dwc_otg
[    4.064861] usb 1-1.1: New USB device found, idVendor=0424, idProduct=ec00, bcdDevice= 2.00
[    4.064887] usb 1-1.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[    4.184854] smsc95xx 1-1.1:1.0 eth0: register 'smsc95xx' at usb-3f980000.usb-1.1, smsc95xx USB 2.0 Ethernet, b8:27:eb:1a:39:ce
[    4.494585] usb 1-1.3: new high-speed USB device number 4 using dwc_otg
[    4.635355] usb 1-1.3: New USB device found, idVendor=2040, idProduct=5200, bcdDevice= 0.01
[    4.635381] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[    4.635398] usb 1-1.3: Product: NovaT 500Stick
[    4.635413] usb 1-1.3: Manufacturer: Hauppauge
[    4.635429] usb 1-1.3: SerialNumber: 4035345063
[    7.966191] dvb-usb: found a 'Hauppauge Nova-TD Stick (52009)' in cold state, will try to load a firmware
[    7.983102] dvb-usb: downloading firmware from file 'dvb-usb-dib0700-1.20.fw'
[    8.028506] usbcore: registered new interface driver brcmfmac
[    8.057103] brcmfmac mmc1:0001:1: Direct firmware load for brcm/brcmfmac43430-sdio.raspberrypi,3-model-b.txt failed with error -2
[    8.197838] dib0700: firmware started successfully.
[    8.715482] dvb-usb: found a 'Hauppauge Nova-TD Stick (52009)' in warm state.
[    8.716051] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
[    8.716993] dvbdev: DVB: registering new adapter (Hauppauge Nova-TD Stick (52009))
[    8.717029] usb 1-1.3: media controller created
[    8.720228] dvbdev: dvb_create_media_entity: media entity 'dvb-demux' registered.
[    9.175911] usb 1-1.3: DVB: registering adapter 0 frontend 0 (DiBcom 7000PC)...
[    9.175986] dvbdev: dvb_create_media_entity: media entity 'DiBcom 7000PC' registered.
[    9.496119] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
[    9.497654] dvbdev: DVB: registering new adapter (Hauppauge Nova-TD Stick (52009))
[    9.497846] usb 1-1.3: media controller created
[    9.501815] dvbdev: dvb_create_media_entity: media entity 'dvb-demux' registered.
[    9.732981] usb 1-1.3: DVB: registering adapter 1 frontend 0 (DiBcom 7000PC)...
[    9.733042] dvbdev: dvb_create_media_entity: media entity 'DiBcom 7000PC' registered.
[   10.023689] dvb-usb: Hauppauge Nova-TD Stick (52009) successfully initialized and connected.
[   10.024091] usbcore: registered new interface driver dvb_usb_dib0700
[   12.458734] SMSC LAN8700 usb-001:003:01: attached PHY driver [SMSC LAN8700] (mii_bus:phy_addr=usb-001:003:01, irq=POLL)
[   12.691875] usb 1-1.3: DVB: adapter 1 frontend 0 frequency 0 out of range (45000000..860000000)
[   12.765747] usb 1-1.3: DVB: adapter 0 frontend 0 frequency 0 out of range (45000000..860000000)
pi@raspberrypi:~ $ 

The usb DVB-T device works on a server in VM under Proxmox (debian) with Plex server --> it's under linux.

(personally I don't want to use Plex but Tvheadend which is more suitable for my use)

My usb DVB-T device also worked perfectly on my Vu+Duo Twin Linux Receiver under enigma that I had a few years ago and that I sold.

It seems complicated for me to do the tests with dvb-apps. I installed it but then I don't know what to do...

RE: search usb dual DVB-T tuner compatible with raspbian & tvheadend on Rpi4 - Added by Samquad Samquad over 3 years ago

dmesg |egrep "firmware|dvb|frontend|usb" return

[    0.080131] raspberrypi-firmware soc:firmware: Attached to firmware from 2021-01-27T22:26:53, variant start
[    0.090148] raspberrypi-firmware soc:firmware: Firmware hash is 99d9a48302e4553cff3688692bb7e9ac760a03fa
[    0.142130] usbcore: registered new interface driver usbfs
[    0.142196] usbcore: registered new interface driver hub
[    0.142267] usbcore: registered new device driver usb
[    2.021404] usbcore: registered new interface driver lan78xx
[    2.021472] usbcore: registered new interface driver smsc95xx
[    2.951132] dwc_otg 3f980000.usb: DWC OTG Controller
[    2.951171] dwc_otg 3f980000.usb: new USB bus registered, assigned bus number 1
[    2.951224] dwc_otg 3f980000.usb: irq 89, io mem 0x00000000
[    2.951675] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.10
[    2.951693] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    2.951708] usb usb1: Product: DWC OTG Controller
[    2.951723] usb usb1: Manufacturer: Linux 5.10.11-v7+ dwc_otg_hcd
[    2.951738] usb usb1: SerialNumber: 3f980000.usb
[    2.954130] usbcore: registered new interface driver usb-storage
[    2.962434] usbcore: registered new interface driver usbhid
[    2.962446] usbhid: USB HID core driver
[    3.374499] usb 1-1: new high-speed USB device number 2 using dwc_otg
[    3.614887] usb 1-1: New USB device found, idVendor=0424, idProduct=9514, bcdDevice= 2.00
[    3.614913] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[    3.934481] usb 1-1.1: new high-speed USB device number 3 using dwc_otg
[    4.064861] usb 1-1.1: New USB device found, idVendor=0424, idProduct=ec00, bcdDevice= 2.00
[    4.064887] usb 1-1.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[    4.184854] smsc95xx 1-1.1:1.0 eth0: register 'smsc95xx' at usb-3f980000.usb-1.1, smsc95xx USB 2.0 Ethernet, b8:27:eb:1a:39:ce
[    4.494585] usb 1-1.3: new high-speed USB device number 4 using dwc_otg
[    4.635355] usb 1-1.3: New USB device found, idVendor=2040, idProduct=5200, bcdDevice= 0.01
[    4.635381] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[    4.635398] usb 1-1.3: Product: NovaT 500Stick
[    4.635413] usb 1-1.3: Manufacturer: Hauppauge
[    4.635429] usb 1-1.3: SerialNumber: 4035345063
[    7.966191] dvb-usb: found a 'Hauppauge Nova-TD Stick (52009)' in cold state, will try to load a firmware
[    7.983102] dvb-usb: downloading firmware from file 'dvb-usb-dib0700-1.20.fw'
[    8.028506] usbcore: registered new interface driver brcmfmac
[    8.057103] brcmfmac mmc1:0001:1: Direct firmware load for brcm/brcmfmac43430-sdio.raspberrypi,3-model-b.txt failed with error -2
[    8.197838] dib0700: firmware started successfully.
[    8.715482] dvb-usb: found a 'Hauppauge Nova-TD Stick (52009)' in warm state.
[    8.716051] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
[    8.716993] dvbdev: DVB: registering new adapter (Hauppauge Nova-TD Stick (52009))
[    8.717029] usb 1-1.3: media controller created
[    8.720228] dvbdev: dvb_create_media_entity: media entity 'dvb-demux' registered.
[    9.175911] usb 1-1.3: DVB: registering adapter 0 frontend 0 (DiBcom 7000PC)...
[    9.175986] dvbdev: dvb_create_media_entity: media entity 'DiBcom 7000PC' registered.
[    9.496119] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
[    9.497654] dvbdev: DVB: registering new adapter (Hauppauge Nova-TD Stick (52009))
[    9.497846] usb 1-1.3: media controller created
[    9.501815] dvbdev: dvb_create_media_entity: media entity 'dvb-demux' registered.
[    9.732981] usb 1-1.3: DVB: registering adapter 1 frontend 0 (DiBcom 7000PC)...
[    9.733042] dvbdev: dvb_create_media_entity: media entity 'DiBcom 7000PC' registered.
[   10.023689] dvb-usb: Hauppauge Nova-TD Stick (52009) successfully initialized and connected.
[   10.024091] usbcore: registered new interface driver dvb_usb_dib0700
[   12.458734] SMSC LAN8700 usb-001:003:01: attached PHY driver [SMSC LAN8700] (mii_bus:phy_addr=usb-001:003:01, irq=POLL)
[   12.691875] usb 1-1.3: DVB: adapter 1 frontend 0 frequency 0 out of range (45000000..860000000)
[   12.765747] usb 1-1.3: DVB: adapter 0 frontend 0 frequency 0 out of range (45000000..860000000)
pi@raspberrypi:~ $ 

The usb DVB-T device works on a server in VM under Proxmox (debian) with Plex server --> it's under linux.

(personally I don't want to use Plex but Tvheadend which is more suitable for my use)

My usb DVB-T device also worked perfectly on my Vu+Duo Twin Linux Receiver under enigma that I had a few years ago and that I sold.

It seems complicated for me to do the tests with dvb-apps. I installed it but then I don't know what to do...

RE: search usb dual DVB-T tuner compatible with raspbian & tvheadend on Rpi4 - Added by Lloyd Adams over 3 years ago

Grab w_scan from https://www.gen2vdr.de/wirbel/w_scan_cpp/archiv/archiv.html and build that. Then scan and see what it finds. Try w_scan -ft -c FR. (You'll need to stop TVH first.) This should list all muxes and services the adaptor can find. Then run w_scan -ft -c FR -x as this a lot of the info required to create a mux in TVH.

Then delete all the muxes you have and add one, using the information you have just created, plus look here: https://git.linuxtv.org/dtv-scan-tables.git/tree/dvb-t/fr-All
I did notice that the guard interval that you had set was different to what is published on linuxtv. I think you can leave some values to AUTO - worth having a read of this: https://www.raspberrypi.org/forums/viewtopic.php?t=227563

RE: search usb dual DVB-T tuner compatible with raspbian & tvheadend on Rpi4 - Added by Samquad Samquad over 3 years ago

Thank you Lloyd!

To complete my testing, I took the time to install Plex server on a RPI3 under rapsbian for testing the tuner.
I confirm that Plex manages this tuner it has found all the channels.

I installed W_scan as you advised me to do
W_scan seems to find all 32 channels and that's positive!

Now I have to delete all muxes to recreate them with the right information,I have to read in detail to see how to do it...

The log attachments

    (1-15/15)