Hi Patrick, Thank you for replying. In answer to your questions: > Are you sure it is a driver problem? No but given the very same device on the very same antenna system works ok under Windows it seemed like a good place to start. > If the BER stays at this value it could also mean that the channel-configuration is wrong. > Are you using a channels.conf which has all parameters set, or are you doing a channel-scan-like tune (all values are set to AUTO). I have attached a copy of the channels.conf file I have been using. It was generated by hand based because the scan and w_scan commands would time out for all stations except C31. The information was obtained from a variety of sources on the internet but mostly from http://igorfuna.com/dvb-t/australia/ I am located in Melbourne Australia. Looking in the file you can see that most paramaters are defined except for inversion which is left as auto. > There are usually some adaptations board-designing companies do to improve > reception quality (adding external LNAs and things like that) that are of > course handled by the Window-driver, because it is created by the > manufacturer and not by the Linux-driver, because (in this case) the driver > was released by the chip-manufacturer. I agree this could be the case and indeed changing the force_lna_activation module parameter seemed to do nothing which would make me suspect that the lna control GPIO on this device is not that same as what is implemented in the driver. Challenge is there seems to be no information around about the DIB7000 or the MT2266 otherwise I would just trace the connections manually using device pinouts. > Is the device toggling between FE_HAS_LOCK and no FE_HAS_LOCK or does it > stay constantly at The device stays constantly on FE LOCK after the initial tune. Attached are brief snapshots of tuning using tzap for the different frequencies. Whilst this only shows a few seconds worth of data, the output is more or less the same over an extended period. > Please try whether you can achieve the BER lowering by moving the antenna or > using a better one. If this helps, it really means that the windows-driver > does something more the board. Not really practical to move the antenna its up on a mast and indeed as the existing analogue stations are still transmitting from the same tower I know that I have a good signal with no multipath. Other TV sets with digital tuners on the same antenna also report excellent signal levels. > I doubt that the chip-driver needs to be changed, more likely the GPIOs of > the dib0700 (in dib0700_core.c) or of the dib7000 are used to turn on or off > a frequency switch or a LNA. Yes, I suspect that you are right. Challenge is that without any documentation on the devices you are flying blind to reverse engineer the design. > Good point, what are the frequencies you're tuning ? The frequencies I have been tuning are listed below but also of interest is that they all use 64QAM whereas the station that works uses QPSK which to me says this is a signal problem and as you state above, probably tied in with a LNA as QPSK is more robust in comparison to 64QAM which is why it has probably been used by C31 as they don't have the need for the higher throughput and have a more modest transmission power compared to the others. So they get more bang for their buck but have the down side of only a single SD stream. C31 557.625 MHz QPSK Works ok. ABC 226.5 MHz 64QAM Doesn't work 7 177.5 MHz 64QAM Doesn't work 9 191.625 MHz 64QAM Doesn't work 10 219.5 MHz 64QAM Doesn't work SBS 536.625 Mhz 64QAM Doesn't work Happy to hear your or anyone else's thoughts. Regards Pete > From: pboettcher@xxxxxxxxxxxxxx > To: peter_tilley13@xxxxxxxxxxx; linux-media@xxxxxxxxxxxxxxx > Subject: Re: Dib7000/mt2266 help > Date: Sat, 12 Mar 2011 16:47:40 +0100 > > Hi Peter, > > (adding back the list to CC) > > On Saturday 12 March 2011 11:48:38 Peter Tilley wrote: > > Hi Patrick, > > My sincerest apologies for coming to you directly but I have tried the > > Linux mailing list and received no response and noticed you seem to have > > been heavily involved with much of the Dibcom driver development. > > > > I have an issue with a dual tuner which is sold under the brand of Kaiser > > Baas KBA01004 but identifies itself as 1164:1e8c which is a Yaun device > > and this device seems to have already been included in the driver files. > > > > It loads ok and reports not problems. It tunes ok and reports FE lock on > > all channels however on all but one channel upon receiving FE lock the > > BER stays at 1ffff instead of dropping to a low number which would > > indicate I am not getting viterbi. > > > > The device is fitted with pairs of MT2266 and DIB7000 which I have > > positive identified by opening the USB stick. > > > > am more than happy to try and work this out myself however the amount of > > detail around in support of the Linux drivers is extremely low and a > > search for manufacturers data sheets finds next to nothing. There > > seems to be lots of what I would call "magic numbers" in the drivers and > > little to determine what they are doing. > > Are you sure it is a driver problem? > > If the BER stays at this value it could also mean that the channel- > configuration is wrong. > > Are you using a channels.conf which has all parameters set, or are you doing > a channel-scan-like tune (all values are set to AUTO). > > > My question to you is are you able to offer either any pointers to solve > > the problem or help me find detailed information about the devices so I > > can help myself. > > > > I should point out that the device works perfectly under windows on the > > same antenna and indeed I have even successfully extracted the firmware > > from the supplied windows driver, renamed it so it loads and the problem > > still remains. > > There are usually some adaptations board-designing companies do to improve > reception quality (adding external LNAs and things like that) that are of > course handled by the Window-driver, because it is created by the > manufacturer and not by the Linux-driver, because (in this case) the driver > was released by the chip-manufacturer. > > Is the device toggling between FE_HAS_LOCK and no FE_HAS_LOCK or does it > stay constantly at > > Please try whether you can achieve the BER lowering by moving the antenna or > using a better one. If this helps, it really means that the windows-driver > does something more the board. > > I doubt that the chip-driver needs to be changed, more likely the GPIOs of > the dib0700 (in dib0700_core.c) or of the dib7000 are used to turn on or off > a frequency switch or a LNA. > > Good point, what are the frequencies you're tuning ? > > regards, > > -- > Patrick > http://www.kernellabs.com/ > -- > To unsubscribe from this list: send the line "unsubscribe linux-media" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html
peter@Garage2:~/.tzap$ tzap c31 using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0' reading channels from file '/home/peter/.tzap/channels.conf' tuning to 557625000 Hz video pid 0x0065, audio pid 0x0066 status 0e | signal ffff | snr 006a | ber 001fffff | unc 00000000 | status 1e | signal ffff | snr 0031 | ber 00000000 | unc 00000000 | FE_HAS_LOCK status 1e | signal ffff | snr 007b | ber 00000000 | unc 00000000 | FE_HAS_LOCK status 1e | signal ffff | snr 0040 | ber 00000000 | unc 00000000 | FE_HAS_LOCK status 1e | signal ffff | snr 0027 | ber 00000000 | unc 00000000 | FE_HAS_LOCK peter@Garage2:~/.tzap$ tzap "SBS Digital 1" using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0' reading channels from file '/home/peter/.tzap/channels.conf' tuning to 536625000 Hz video pid 0x00a1, audio pid 0x0051 status 02 | signal ffff | snr 002b | ber 001fffff | unc 00000000 | status 1a | signal ffff | snr 0024 | ber 001fffff | unc 00000000 | FE_HAS_LOCK status 1a | signal ffff | snr 0020 | ber 001fffff | unc 00000000 | FE_HAS_LOCK status 1a | signal ffff | snr 0019 | ber 001fffff | unc 00000009 | FE_HAS_LOCK peter@Garage2:~/.tzap$ tzap "Ten Digital 1" using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0' reading channels from file '/home/peter/.tzap/channels.conf' tuning to 219500000 Hz video pid 0x0200, audio pid 0x028a status 02 | signal ffff | snr 001c | ber 001fffff | unc 00000000 | status 1a | signal ffff | snr 0017 | ber 001fffff | unc 0000000b | FE_HAS_LOCK status 1a | signal ffff | snr 000e | ber 001fffff | unc 00000000 | FE_HAS_LOCK status 1a | signal ffff | snr 0008 | ber 001fffff | unc 00000000 | FE_HAS_LOCK status 1a | signal ffff | snr 0006 | ber 001fffff | unc 00000000 | FE_HAS_LOCK peter@Garage2:~/.tzap$ tzap "Nine Digital" using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0' reading channels from file '/home/peter/.tzap/channels.conf' tuning to 191625000 Hz video pid 0x0207, audio pid 0x02d0 status 02 | signal ffff | snr 0012 | ber 001fffff | unc 00000000 | status 1a | signal ffff | snr 0012 | ber 001fffff | unc 00000000 | FE_HAS_LOCK status 1a | signal ffff | snr 000d | ber 001fffff | unc 00000000 | FE_HAS_LOCK status 1a | signal ffff | snr 0009 | ber 001fffff | unc 00000000 | FE_HAS_LOCK status 1a | signal ffff | snr 0006 | ber 001fffff | unc 00000000 | FE_HAS_LOCK status 1a | signal ffff | snr 0004 | ber 001fffff | unc 00000000 | FE_HAS_LOCK peter@Garage2:~/.tzap$ tzap "7 Digital" using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0' reading channels from file '/home/peter/.tzap/channels.conf' tuning to 177500000 Hz video pid 0x0301, audio pid 0x0302 status 0a | signal ffff | snr 001c | ber 001fffff | unc 00000000 | status 1a | signal ffff | snr 0017 | ber 001fffff | unc 00000000 | FE_HAS_LOCK status 1a | signal ffff | snr 0010 | ber 001fffff | unc 00000008 | FE_HAS_LOCK status 1a | signal ffff | snr 000f | ber 001fffff | unc 00000000 | FE_HAS_LOCK status 1a | signal ffff | snr 000e | ber 001fffff | unc 00000000 | FE_HAS_LOCK peter@Garage2:~/.tzap$ tzap "ABC HDTV" using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0' reading channels from file '/home/peter/.tzap/channels.conf' tuning to 226500000 Hz video pid 0x090a, audio pid 0x0000 status 0a | signal ffff | snr 001c | ber 001fffff | unc 00000000 | status 1a | signal ffff | snr 000f | ber 001fffff | unc 00000000 | FE_HAS_LOCK status 1a | signal ffff | snr 0008 | ber 001fffff | unc 00000000 | FE_HAS_LOCK status 1a | signal ffff | snr 0008 | ber 001fffff | unc 00000000 | FE_HAS_LOCK
ABC HDTV:226500000:INVERSION_AUTO:BANDWIDTH_7_MHZ:FEC_3_4:FEC_3_4:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_16:HIERARCHY_NONE:2314:0:560 ABC TV Melbourne:226500000:INVERSION_AUTO:BANDWIDTH_7_MHZ:FEC_3_4:FEC_3_4:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_16:HIERARCHY_NONE:512:650:561 ABC2:226500000:INVERSION_AUTO:BANDWIDTH_7_MHZ:FEC_3_4:FEC_3_4:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_16:HIERARCHY_NONE:2307:2308:562 ABC TV:226500000:INVERSION_AUTO:BANDWIDTH_7_MHZ:FEC_3_4:FEC_3_4:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_16:HIERARCHY_NONE:512:650:563 ABC DiG Radio:226500000:INVERSION_AUTO:BANDWIDTH_7_MHZ:FEC_3_4:FEC_3_4:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_16:HIERARCHY_NONE:0:2317:566 ABC DiG Jazz:226500000:INVERSION_AUTO:BANDWIDTH_7_MHZ:FEC_3_4:FEC_3_4:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_16:HIERARCHY_NONE:0:2318:567 7 Digital:177500000:INVERSION_AUTO:BANDWIDTH_7_MHZ:FEC_2_3:FEC_2_3:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_16:HIERARCHY_NONE:769:770:1328 7 Digital 1:177500000:INVERSION_AUTO:BANDWIDTH_7_MHZ:FEC_2_3:FEC_2_3:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_16:HIERARCHY_NONE:769:770:1329 7 Digital 2:177500000:INVERSION_AUTO:BANDWIDTH_7_MHZ:FEC_2_3:FEC_2_3:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_16:HIERARCHY_NONE:769:770:1330 7 Digital 3:177500000:INVERSION_AUTO:BANDWIDTH_7_MHZ:FEC_2_3:FEC_2_3:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_16:HIERARCHY_NONE:769:770:1331 7 HD Digital:177500000:INVERSION_AUTO:BANDWIDTH_7_MHZ:FEC_2_3:FEC_2_3:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_16:HIERARCHY_NONE:833:0:1332 7 Guide:177500000:INVERSION_AUTO:BANDWIDTH_7_MHZ:FEC_2_3:FEC_2_3:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_16:HIERARCHY_NONE:865:866:1334 Nine Digital:191625000:INVERSION_AUTO:BANDWIDTH_7_MHZ:FEC_3_4:FEC_3_4:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_16:HIERARCHY_NONE:519:720:1072 Nine Digital HD:191625000:INVERSION_AUTO:BANDWIDTH_7_MHZ:FEC_3_4:FEC_3_4:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_16:HIERARCHY_NONE:512:0:1073 Nine Guide:191625000:INVERSION_AUTO:BANDWIDTH_7_MHZ:FEC_3_4:FEC_3_4:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_16:HIERARCHY_NONE:517:700:1074 TEN Digital:219500000:INVERSION_AUTO:BANDWIDTH_7_MHZ:FEC_3_4:FEC_1_2:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_16:HIERARCHY_NONE:512:650:1585 TEN Digital 1:219500000:INVERSION_AUTO:BANDWIDTH_7_MHZ:FEC_3_4:FEC_1_2:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_16:HIERARCHY_NONE:512:650:1586 TEN Digital 2:219500000:INVERSION_AUTO:BANDWIDTH_7_MHZ:FEC_3_4:FEC_1_2:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_16:HIERARCHY_NONE:512:650:1587 TEN Digital 3:219500000:INVERSION_AUTO:BANDWIDTH_7_MHZ:FEC_3_4:FEC_1_2:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_16:HIERARCHY_NONE:512:650:1588 TEN Digital:219500000:INVERSION_AUTO:BANDWIDTH_7_MHZ:FEC_3_4:FEC_1_2:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_16:HIERARCHY_NONE:512:650:1589 TEN Guide:219500000:INVERSION_AUTO:BANDWIDTH_7_MHZ:FEC_3_4:FEC_1_2:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_16:HIERARCHY_NONE:513:660:1591 TEN HD:219500000:INVERSION_AUTO:BANDWIDTH_7_MHZ:FEC_3_4:FEC_1_2:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_16:HIERARCHY_NONE:514:0:1592 TEN Guide:219500000:INVERSION_AUTO:BANDWIDTH_7_MHZ:FEC_3_4:FEC_1_2:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_16:HIERARCHY_NONE:513:660:1593 SBS HD:536625000:INVERSION_AUTO:BANDWIDTH_7_MHZ:FEC_2_3:FEC_2_3:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_8:HIERARCHY_NONE:102:103:784 SBS DIGITAL 1:536625000:INVERSION_AUTO:BANDWIDTH_7_MHZ:FEC_2_3:FEC_2_3:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_8:HIERARCHY_NONE:161:81:785 SBS DIGITAL 2:536625000:INVERSION_AUTO:BANDWIDTH_7_MHZ:FEC_2_3:FEC_2_3:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_8:HIERARCHY_NONE:162:83:786 SBS EPG:536625000:INVERSION_AUTO:BANDWIDTH_7_MHZ:FEC_2_3:FEC_2_3:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_8:HIERARCHY_NONE:163:85:787 SBS RADIO 1:536625000:INVERSION_AUTO:BANDWIDTH_7_MHZ:FEC_2_3:FEC_2_3:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_8:HIERARCHY_NONE:0:201:798 SBS RADIO 2:536625000:INVERSION_AUTO:BANDWIDTH_7_MHZ:FEC_2_3:FEC_2_3:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_8:HIERARCHY_NONE:0:202:799 SBS HD:536500000:INVERSION_AUTO:BANDWIDTH_7_MHZ:FEC_2_3:FEC_2_3:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_8:HIERARCHY_NONE:102:103:784 SBS DIGITAL 1:536500000:INVERSION_AUTO:BANDWIDTH_7_MHZ:FEC_2_3:FEC_2_3:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_8:HIERARCHY_NONE:161:81:785 SBS DIGITAL 2:536500000:INVERSION_AUTO:BANDWIDTH_7_MHZ:FEC_2_3:FEC_2_3:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_8:HIERARCHY_NONE:162:83:786 SBS EPG:536500000:INVERSION_AUTO:BANDWIDTH_7_MHZ:FEC_2_3:FEC_2_3:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_8:HIERARCHY_NONE:163:85:787 SBS RADIO 1:536500000:INVERSION_AUTO:BANDWIDTH_7_MHZ:FEC_2_3:FEC_2_3:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_8:HIERARCHY_NONE:0:201:798 SBS RADIO 2:536500000:INVERSION_AUTO:BANDWIDTH_7_MHZ:FEC_2_3:FEC_2_3:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_8:HIERARCHY_NONE:0:202:799 C31:557625000:INVERSION_AUTO:BANDWIDTH_7_MHZ:FEC_3_4:FEC_NONE:QPSK:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_16:HIERARCHY_NONE:101:102:3585
