Thread: HVR-2200 not picking up all channels

I'm using Mythbuntu 9.10 and I've just brought a HVR-2200 dual digital/dual analogue card.

I've followed the tutorial here: Hauppauge WinTV-HVR-2200 - LinuxTVWiki to get it to a working state. My problem now is it's not picking up all the channels in my area. I've tested my setup with a USB tuner which gets all the channels without a problem.

This is using the scan function of the mythtv backend.



I tried to run w_scan to see if I could find more channels (specifically SBS & channel NINE in Victoria, Australia), it failed with this error:
$ w_scan -c au
w_scan version 20090808 (compiled for DVB API 5.0)
using settings for AUSTRALIA
DVB aerial
DVB-T AU
frontend_type DVB-T, channellist 3
output format vdr-1.6
Info: using DVB adapter auto detection.
/dev/dvb/adapter1/frontend0 -> DVB-T "NXP TDA10048HN DVB-T": good
/dev/dvb/adapter2/frontend0 -> DVB-T "NXP TDA10048HN DVB-T": good
Using DVB-T frontend (adapter /dev/dvb/adapter1/frontend0)
-_-_-_-_ Getting frontend capabilities-_-_-_-_
Using DVB API 5.1
frontend NXP TDA10048HN DVB-T supports
INVERSION_AUTO
QAM_AUTO
TRANSMISSION_MODE_AUTO
GUARD_INTERVAL_AUTO
HIERARCHY_AUTO
FEC_AUTO
-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_
Scanning 7MHz frequencies...
177500: (time: 00:00) set_frontend:1690: FATAL: unsupported DVB API Version 5.1


Am I heading down the right track here? Is there something wrong with my w_scan command? Is there a better tool to use to find and build my channels into channels.conf?

Where does w_scan come from? Looks like an API error with that utility rather than a driver issue. Did w_scan work with the USB tuner?

scan from the dvb-apps package works fine for me. See my post on this card:http://www.mythtvtalk.com/forum/hard...html#post46347 I compiled from source - although there is a dvb-apps package for Fedora it doesn't seem to work properly for me.

This is the command I use and the start of the output here in the Mother Country...

Code:

[root@localhost dvb-t]# scan ./uk-CrystalPalace -o zap
scanning ./uk-CrystalPalace
using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
initial transponder 505833000 0 3 9 1 0 0 0
initial transponder 481833000 0 2 9 3 0 0 0
initial transponder 561833000 0 2 9 3 0 0 0
initial transponder 529833000 0 3 9 1 0 0 0
initial transponder 578167000 0 3 9 1 0 0 0
initial transponder 537833000 0 3 9 1 0 0 0
>>> tune to: 505833000:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_3_4:FEC_AUTO:QAM_16:TRANSMISSION_MODE_2K:GUARD_INTERVAL_1_32:HIERARCHY_NONE
0x0000 0x10ff: pmt_pid 0x10ff BBC -- BBC THREE (running)
0x0000 0x117f: pmt_pid 0x117f BBC -- BBC Red Button (running)
0x0000 0x123f: pmt_pid 0x123f BBC -- CBBC Channel (running)
0x0000 0x113f: pmt_pid 0x113f BBC -- BBC NEWS (running)
0x0000 0x1084: pmt_pid 0x1084 BBC -- BBC TWO (running)
0x0000 0x1044: pmt_pid 0x1044 BBC -- BBC ONE (running)

See how this works out.

Andrew

Dear Map7,

I just installed Mythbuntu 9.10 and I have a Hauppauge WinTV-HVR-1200. It actually works out of the box, but when I scan the channels via the MythTv menu, it will identify SEVEN and sometimes ABC. The scan always produces different results.
I manually entered the following transports:



# T freq bw fec_hi fec_lo mod guard-interval hierarchy

# ABC
T 226500000 7MHz 3/4 NONE QAM-Auto 8k NONE

# Seven
T 177500000 7MHz 2/3 NONE QAM-Auto 8k NONE

# Nine
T 191625000 7MHz 3/4 NONE QAM-Auto 8k NONE

# Ten
T 219500000 7MHz 3/4 NONE QAM-Auto 8k NONE

# SBS
T 585625000 7MHz 2/3 NONE QAM-Auto 8k NONE




Then I scanned the transports and it identified them properly. I went back to the MythTv frontend and when I changed the channel to these newly identified channels, it would just scan them for a while and a picture never appears.




Should I try to fix the card such as you have done (Hauppauge WinTV-HVR-1200 - LinuxTVWiki)?

or

Might anyone have a tip on how to scan properly for channels and MythTv in Brisbane, Australia.

Furthermore, this is not a faulty device, it works perfectly in windows vista ultimate 32-bit.


Cheers,
Rocko262c

I would first try what AndyW mentioned as this worked for me. If you look in the /usr/share/dvb/dvb-t directory you should find a frequency table for your area. Use this with scan as AndyW suggested to make your channels.conf and then import it into Mythtv.

Originally Posted by map7

I would first try what AndyW mentioned as this worked for me. If you look in the /usr/share/dvb/dvb-t directory you should find a frequency table for your area. Use this with scan as AndyW suggested to make your channels.conf and then import it into Mythtv.

Thanks for your response Map7, but that is the the frequency table is for my area (Brisbane, Australia) and that is why the channel number identification was properly identified, but for some reason, the channels won't tune in.

My card works fine in windows and I have another generic USB DVB-T tuner that gets all of the channels in my house in windows. Unfortunately, this tuner isn't supported in Linux. By the way it is looking, the Hauppauge Hauppauge WinTV-HVR-1200 is supposedly supported by the new kernel, but nobody can get it to work. Lots of people also can't get it to work on windows.

Frustrated,
Rocko

Rocko this is starting to get off topic and looks like it's more specific problems to do with the HVR-1200.

Anyway, what kernel are you running?

You should upgrade the firmware as per the site:
Hauppauge WinTV-HVR-1200 - LinuxTVWiki

Maybe it's a firmware bug and it might of been fixed in the latest version.

Otherwise maybe try using w_scan, it didn't work for me but w_scan allows you to scan all frequencies and can create a channels.conf file.

Map7,
Unfortunatley, the fix as per the (Hauppauge WinTV-HVR-1200 - LinuxTVWiki) site, this method didn't work either. I even downloaded the latest drivers from the Hauppauge site and ran the script "extract.sh" (after changing the file names in the script for the appropriate zip and rom files) and it didn't work.

Again, I am running the latest kernal (2.6.31).

I will try w_scan. Again, I can scan the channels and get the proper channel identification, but when I go back to my front-end and try to view them, I can't view them. I change the channel to e.g. GO! and a message appears saying:

signal 99%|S/N 2.4dB|BE 42|(LMs) Partial Lock

So honestly, I am not sure if the scan worked or not to find the actual channel. I know the scan can pick up the name of the channel, but not the actuall viewing channel.


Any thoughts about installing Mythbuntu 8.04 and installing the firmware my self as per (Hauppauge WinTV-HVR-1200 - LinuxTVWiki)?

Thanks again for helping!!
Frustrated,
Rocko

Map7:

I would check which version of w_scan you're using.
I suggest you try getting the latest version from the author directly:
w_scan – edafe.org

The download link on that page is outdated (and broken) so here is the correct link to the latest version, from the authors german only webpage.
Download w_scan

Try the pre-compiled version included in the archive first. It worked for me, but I'm using an HVR-1600 card.

Rocko262c: I am not familiar with w_scan and don't have a HVR-1200 for testing. However the output you posted looks like poor signal quality. "BE" (bit error rate) should hardly deviate from zeo, and "Partial lock" probably means what it says. The description of tzap output on the LinuxTV wiki is probably relevany here too.

Check your DVB antenna & coax cabling. If other TVs in the house are OK check the connection to the tuner card (I had a similar problem once due to a dodgy cable from a splitter). If the same tuner works OK on windows then there is a driver and/or scan utility problem.. The HVR-1200 entry on LinuxTV says "You may need to scan with a +166KHz or +167KHz offset in order to detect channels properly" - check that out, as you may be slightly off-centre with the channels.

Hey Everyone,
Thanks for your replies!!! I solved the problem! I will write a longer how-to post this weekend when I have time. Basically, i believe that the firmware in the new kernel works for the Hauppauge WinTV-HVR-1200! I took the list of stations and scanned the frequencies above entering the data next to them. I increased the scan time to 30 seconds. For some reason, editing the transports doesn't seem to work.
Cheers,
Rocko