If this can't be fixed by firmware or driver, the lower demodulation limit rate of 1MSps of the TDA10071 is just for the data sheet but not true for the TBS tv card.
Poor Performance
29 posts
• Page 2 of 3 • 1, 2, 3
Re: Poor Performance
by Derrick » Sun Feb 06, 2011 9:51 pm
Same situation for DVB-S and very low SR. But the culprit can't be the digital demodulator. A look at the 2 screenshots shows, that though there are lot of "missing" or unknown ts_packets there is a lock because at least some mpeg packets and SI tables are received correctly. The correct mux rate of the example after demodulation is 2,19Mbps. The TBS card streams almost 15Mbps! If there is a lock, the output of the demodulator has to be be synchronized with the IQ-signals received from the tuner. That means the card is leaking meaningless data (or duplicating real data). This has to originate from other parts of the hardware but not from the frontend.
If this can't be fixed by firmware or driver, the lower demodulation limit rate of 1MSps of the TDA10071 is just for the data sheet but not true for the TBS tv card.
If this can't be fixed by firmware or driver, the lower demodulation limit rate of 1MSps of the TDA10071 is just for the data sheet but not true for the TBS tv card.
- Derrick
- Posts: 91
- Joined: Sun Jul 04, 2010 6:49 pm
Re: Poor Performance
by cody » Mon Feb 07, 2011 5:20 am
we have enough signal generators/modulators in our lab too and we should be able to make in-depth investigation. actually, we did tested low/high symbol rate, but i know the results from the TBS 6921 (the PCI-Express card) and maybe there are some timing issues or something else wrong in the driver with data transfer for the PCI card (TBS 8921).
anyway, i'm suggesting to start investigating your problems with the "frequency problem" - as i mentioned i will prepare and post here special debug driver for Windows that will give the same detailed signal statistic as the Linux driver. also, i'm still not excluding the possibility that there is fault on your card - especially if we can't reproduce the same problem on the same signals as you did.
so, please, give me several more days to prepare the special test driver for collecting statistics about your signal.
anyway, i'm suggesting to start investigating your problems with the "frequency problem" - as i mentioned i will prepare and post here special debug driver for Windows that will give the same detailed signal statistic as the Linux driver. also, i'm still not excluding the possibility that there is fault on your card - especially if we can't reproduce the same problem on the same signals as you did.
so, please, give me several more days to prepare the special test driver for collecting statistics about your signal.
- cody
- Posts: 627
- Joined: Tue Apr 13, 2010 11:20 pm
Re: Poor Performance
by cody » Mon Feb 14, 2011 6:58 am
ok, i'm ready with the test driver for a few days, but i can't find time to post it here and give some explanation for the testing process. anyway, i hope sometime tomorrow i will put it here.
- cody
- Posts: 627
- Joined: Tue Apr 13, 2010 11:20 pm
Re: Poor Performance
by cody » Wed Feb 16, 2011 8:10 am
first of all the driver that outputs debug information containing the advanced signal statistics is here:
http://www.fileserve.com/file/aDwZt9F
after it's installed, in order to collect and view the debug information you need Microsoft tool called "DebugView" that is available for download here:
http://technet.microsoft.com/en-us/sysinternals/bb896647
then extract the files from "DebugView.zip" to some folder, right click on "Dbgview.exe" and choose "Run as administrator" (in case you're using Vista/Win7, that's not needed for WinXP) and make sure in "Capture" menu everything is checked except "Log boot".
so, after all of the above is set when you acquire signal lock you will see the advanced signal statistics in the DebugView window and something similar to:
* for DVB-S2 signal:
* for DVB-S signal:
please, note that information is taken directly from the demodulator/tuner and it's the real statistic of the actually locked signal and it could be different than what is set in application software like TranEdit, etc - it actually gives you what is the signal. BTW, "CTL" is of course abbreviation from "Carrier Track Loop".
so, back to what you reported - for example on Turksat 42E about transponder 11048V with SR of 2400 kSps. in fact measurement showed that the actual frequency is 11049 (and not 11048) and so using 11048 you already added "-1 MHz" frequency offset. anyway, please, lock with the above driver and that will give us information for the actual frequency offset in your setup.
another thing that i need to mention about measuring how much time it takes to lock (for debug purposes): TranEdit is not very good for that, because it sends "tune request" and then "data transfer request". so, TranEdit waits until the data are actually coming to the application and thus doesn't give clear idea how time much it actually took to acquire a lock, because it could be the delay is added during the "data transfer", i.e. because of some data buffering. so, one good way to test real time for acquiring lock is with AltDVB and with using "Signal test" button which sends only "tune request" and thus measure the real time for signal lock acquisition:
http://www.imagebam.com/image/ae4cdf119687144
BTW, for very low symbol rates i added such measurement to the above debug driver too, e.g. it prints "lock loop X", where X is some number and if for example after "lock loop 13" lock is acquired that means it took between 12*5=60 and 13*5=65 milliseconds.
http://www.fileserve.com/file/aDwZt9F
after it's installed, in order to collect and view the debug information you need Microsoft tool called "DebugView" that is available for download here:
http://technet.microsoft.com/en-us/sysinternals/bb896647
then extract the files from "DebugView.zip" to some folder, right click on "Dbgview.exe" and choose "Run as administrator" (in case you're using Vista/Win7, that's not needed for WinXP) and make sure in "Capture" menu everything is checked except "Log boot".
so, after all of the above is set when you acquire signal lock you will see the advanced signal statistics in the DebugView window and something similar to:
* for DVB-S2 signal:
- Code: Select All Code
00000000 0.00000000 =====CODY DEBUG INFO STARTS HERE=====
00000001 0.00000038
00000002 0.00045007 tbs8921fe: Current Modulation is 8PSK
00000003 0.00045206 tbs8921fe: Current Mode Code is 3/4
00000004 0.00178048 tbs8921fe: Current Tuner PLL Frequency is 1084004 kHz
00000005 0.00460529 tbs8921fe: Current Demod CTL Frequency is 1163 kHz
00000007 0.00549043 tbs8921fe: Current Symbol Rate Offset is 2 kSps
00000008 0.00593572 tbs8921fe: INVERSION -> OFF
00000009 0.00638013 tbs8921fe: PILOT -> OFF
00000010 0.00638160
00000011 0.00638207 =====CODY DEBUG INFO ENDS HERE=====
* for DVB-S signal:
- Code: Select All Code
00000000 0.00000000 =====CODY DEBUG INFO STARTS HERE=====
00000001 0.00000037
00000002 0.00044869 tbs8921fe: Current Modulation is QPSK
00000003 0.00045062 tbs8921fe: Current Mode Code is 5/6
00000004 0.00178528 tbs8921fe: Current Tuner PLL Frequency is 1300566 kHz
00000005 0.00416283 tbs8921fe: Current Demod CTL Frequency is -982 kHz
00000007 0.00504651 tbs8921fe: Current Symbol Rate Offset is 0 kSps
00000008 0.00548788 tbs8921fe: INVERSION -> OFF
00000009 0.00548932
00000010 0.00548972 =====CODY DEBUG INFO ENDS HERE=====
please, note that information is taken directly from the demodulator/tuner and it's the real statistic of the actually locked signal and it could be different than what is set in application software like TranEdit, etc - it actually gives you what is the signal. BTW, "CTL" is of course abbreviation from "Carrier Track Loop".
so, back to what you reported - for example on Turksat 42E about transponder 11048V with SR of 2400 kSps. in fact measurement showed that the actual frequency is 11049 (and not 11048) and so using 11048 you already added "-1 MHz" frequency offset. anyway, please, lock with the above driver and that will give us information for the actual frequency offset in your setup.
another thing that i need to mention about measuring how much time it takes to lock (for debug purposes): TranEdit is not very good for that, because it sends "tune request" and then "data transfer request". so, TranEdit waits until the data are actually coming to the application and thus doesn't give clear idea how time much it actually took to acquire a lock, because it could be the delay is added during the "data transfer", i.e. because of some data buffering. so, one good way to test real time for acquiring lock is with AltDVB and with using "Signal test" button which sends only "tune request" and thus measure the real time for signal lock acquisition:
http://www.imagebam.com/image/ae4cdf119687144
BTW, for very low symbol rates i added such measurement to the above debug driver too, e.g. it prints "lock loop X", where X is some number and if for example after "lock loop 13" lock is acquired that means it took between 12*5=60 and 13*5=65 milliseconds.
- cody
- Posts: 627
- Joined: Tue Apr 13, 2010 11:20 pm
Re: Poor Performance
by Derrick » Wed Feb 16, 2011 8:18 am
Thanks @Cody, I will test it tomorrow.
But for a change here's a positive result with the current driver
On 1W there's a polish radio packet on a very narrow band carrier. DVB-S2, 1005, 8psk, 3/4 (the modulation parameters are calculated backwards from the mux rate) With the TBS 8921 I have absolut stable reception
(my TeVii shows a lot of missing packets)
But for a change here's a positive result with the current driver
On 1W there's a polish radio packet on a very narrow band carrier. DVB-S2, 1005, 8psk, 3/4 (the modulation parameters are calculated backwards from the mux rate) With the TBS 8921 I have absolut stable reception
(my TeVii shows a lot of missing packets)- Derrick
- Posts: 91
- Joined: Sun Jul 04, 2010 6:49 pm
Re: Poor Performance
by cody » Wed Feb 16, 2011 8:22 am
it's good to hear that. in our opinion DVB-S2 demodulator on 5921/6921/8921 is very capable, but it could take us some time to improve the drivers for some extreme cases like the one on which you're testing. i really hope for understanding of the more advanced users, because the truth is no other company use such new chips as we do, which apparently hides a lot of risks with hitting on problems that no one else hit before, greater time to develop mature drivers, etc.
- cody
- Posts: 627
- Joined: Tue Apr 13, 2010 11:20 pm
Re: Poor Performance
by Derrick » Thu Feb 17, 2011 7:51 am
Ok, I've installed the debug driver and Dbgview. Works like a charme After fiddling with different satellites and transponders I managed to put together a suitable test environment. As long as a narrow band carrier is located in an empty spectrum, the frontend will lock eventually. The frequency has to be set sharp, which gives the impression of good selectivity. But if carriers are spaced closely together a very poor selectivity is revealed.
As a test case I took 3 carriers on 10E. It's a mean test cos all have the same modulation parameters: DVB-S, 2532, 3/4. From my transedit 0100.ini:
.
.
7=11171,H,2532,34,0,|02.04: TandbergTV
8=11175,H,2532,34,0,|02.04: Service Provider
9=11178,H,2532,34,0,|02.04: TandbergTV
.
.
As testapplication I took AltDVB. None of these transponders locked with the TBS 8921 within the longest possible time out in a signal test:
TeVii locked very fast on all 3:
Then I created a test.ini with dummy transponders spaced in 1 MHz steps together with the real carriers (all same parameters).
TBS signal scan:
At 1st glance the result doesn't seem bad at all. There's apparently just a small frequency offset. But the debug log shows the real story:
The card does not tune on the correct frequencies. When it tunes the Carrier Track Loop is far outside the center. The log only shows the result but not the reason. I guess you hardware eng. has to dig deep
Here's how it should look like (TeVii) It also shows that the TBS hits are not even on neighbour transponders. The correct order of channel names is: PAYAM TV, AL-FORAT, BELADI TV) It's even worse than I thought
After fiddling with different satellites and transponders I managed to put together a suitable test environment. As long as a narrow band carrier is located in an empty spectrum, the frontend will lock eventually. The frequency has to be set sharp, which gives the impression of good selectivity. But if carriers are spaced closely together a very poor selectivity is revealed.As a test case I took 3 carriers on 10E. It's a mean test cos all have the same modulation parameters: DVB-S, 2532, 3/4. From my transedit 0100.ini:
.
.
7=11171,H,2532,34,0,|02.04: TandbergTV
8=11175,H,2532,34,0,|02.04: Service Provider
9=11178,H,2532,34,0,|02.04: TandbergTV
.
.
As testapplication I took AltDVB. None of these transponders locked with the TBS 8921 within the longest possible time out in a signal test:
TeVii locked very fast on all 3:
Then I created a test.ini with dummy transponders spaced in 1 MHz steps together with the real carriers (all same parameters).
TBS signal scan:
At 1st glance the result doesn't seem bad at all. There's apparently just a small frequency offset. But the debug log shows the real story:
- Code: Select All Code
00000000 0.00000000 [136] DiSEqC len=4
00000001 0.00002150 [136]
00000002 0.00004525 [136] DiSEqC e0
00000003 0.00006575 [136]
00000004 0.00008830 [136] DiSEqC 10
00000005 0.00010841 [136]
00000006 0.00013103 [136] DiSEqC 38
00000007 0.00015108 [136]
00000008 0.00017344 [136] DiSEqC fe
00000009 0.00019347 [136]
00000010 0.13280767 [136] BDA2: DVBS_Turbosight_DiSEqC: sent DISEQC_MESSAGE_PARAMS
00000011 0.13282831 [136]
00000012 0.13306823 [136] BDA2: CDVBNetworkProviderFilter.DoDVBSTuning: put_Range 0xffffffff
00000013 0.13308978 [136]
00000014 25.13992500 [136] BDA2: CDVBNetworkProviderFilter.DoDVBSTuning: put_Range 0xffffffff
00000015 25.13994408 [136]
00000016 50.14337158 [136] BDA2: CDVBNetworkProviderFilter.DoDVBSTuning: put_Range 0xffffffff
00000017 50.14339447 [136]
00000018 50.85371780 =====CODY DEBUG INFO STARTS HERE=====
00000019 50.85371780
00000020 50.85385513 tbs8921fe: Current Modulation is QPSK
00000021 50.85385513 tbs8921fe: Current Mode Code is 3/4
00000022 50.85426712 tbs8921fe: Current Tuner PLL Frequency is 1421997 kHz
00000023 50.85528564 tbs8921fe: Current Demod CTL Frequency is 2979 kHz
00000024 50.85556030 tbs8921fe: Current Symbol Rate Offset is 0 kSps
00000025 50.85569763 tbs8921fe: INVERSION -> OFF
00000026 50.85569763
00000027 50.85570145 =====CODY DEBUG INFO ENDS HERE=====
00000028 50.85570145
00000029 50.87337875 =====CODY DEBUG INFO STARTS HERE=====
00000030 50.87337875
00000031 50.87351608 tbs8921fe: Current Modulation is QPSK
00000032 50.87351990 tbs8921fe: Current Mode Code is 3/4
00000033 50.87392807 tbs8921fe: Current Tuner PLL Frequency is 1421997 kHz
00000034 50.87481308 tbs8921fe: Current Demod CTL Frequency is 2979 kHz
00000035 50.87508392 tbs8921fe: Current Symbol Rate Offset is 0 kSps
00000036 50.87522125 tbs8921fe: INVERSION -> OFF
00000037 50.87522125
00000038 50.87522507 =====CODY DEBUG INFO ENDS HERE=====
00000039 50.87522507
00000040 51.17988586 =====CODY DEBUG INFO STARTS HERE=====
00000041 51.17988586
00000042 51.18002319 tbs8921fe: Current Modulation is QPSK
00000043 51.18002701 tbs8921fe: Current Mode Code is 3/4
00000044 51.18043518 tbs8921fe: Current Tuner PLL Frequency is 1421997 kHz
00000045 51.18132019 tbs8921fe: Current Demod CTL Frequency is 2982 kHz
00000046 51.18159103 tbs8921fe: Current Symbol Rate Offset is 0 kSps
00000047 51.18173218 tbs8921fe: INVERSION -> OFF
00000048 51.18173218
00000049 51.18173218 =====CODY DEBUG INFO ENDS HERE=====
00000050 51.18173218
00000051 51.48751068 =====CODY DEBUG INFO STARTS HERE=====
00000052 51.48751068
00000053 51.48764801 tbs8921fe: Current Modulation is QPSK
00000054 51.48765182 tbs8921fe: Current Mode Code is 3/4
00000055 51.48806000 tbs8921fe: Current Tuner PLL Frequency is 1421997 kHz
00000056 51.48894119 tbs8921fe: Current Demod CTL Frequency is 2980 kHz
00000057 51.48921585 tbs8921fe: Current Symbol Rate Offset is 0 kSps
00000058 51.48934555 tbs8921fe: INVERSION -> OFF
00000059 51.48934937
00000060 51.48934937 =====CODY DEBUG INFO ENDS HERE=====
00000061 51.48934937
00000062 51.80015182 =====CODY DEBUG INFO STARTS HERE=====
00000063 51.80015182
00000064 51.80029297 tbs8921fe: Current Modulation is QPSK
00000065 51.80029297 tbs8921fe: Current Mode Code is 3/4
00000066 51.80070877 tbs8921fe: Current Tuner PLL Frequency is 1421997 kHz
00000067 51.80159378 tbs8921fe: Current Demod CTL Frequency is 2982 kHz
00000068 51.80186462 tbs8921fe: Current Symbol Rate Offset is 0 kSps
00000069 51.80200195 tbs8921fe: INVERSION -> OFF
00000070 51.80200195
00000071 51.80200195 =====CODY DEBUG INFO ENDS HERE=====
00000072 51.80200195
00000073 52.11251450 =====CODY DEBUG INFO STARTS HERE=====
00000074 52.11251450
00000075 52.11265182 tbs8921fe: Current Modulation is QPSK
00000076 52.11265564 tbs8921fe: Current Mode Code is 3/4
00000077 52.11306763 tbs8921fe: Current Tuner PLL Frequency is 1421997 kHz
00000078 52.11408615 tbs8921fe: Current Demod CTL Frequency is 2980 kHz
00000079 52.11436081 tbs8921fe: Current Symbol Rate Offset is 0 kSps
00000080 52.11449814 tbs8921fe: INVERSION -> OFF
00000081 52.11449814
00000082 52.11449814 =====CODY DEBUG INFO ENDS HERE=====
00000083 52.11449814
00000084 52.42698669 =====CODY DEBUG INFO STARTS HERE=====
00000085 52.42698669
00000086 52.42712402 tbs8921fe: Current Modulation is QPSK
00000087 52.42712784 tbs8921fe: Current Mode Code is 3/4
00000088 52.42753601 tbs8921fe: Current Tuner PLL Frequency is 1421997 kHz
00000089 52.42854691 tbs8921fe: Current Demod CTL Frequency is 2982 kHz
00000090 52.42882156 tbs8921fe: Current Symbol Rate Offset is 0 kSps
00000091 52.42895889 tbs8921fe: INVERSION -> OFF
00000092 52.42896271
00000093 52.42896271 =====CODY DEBUG INFO ENDS HERE=====
00000094 52.42896271
00000095 52.73935318 =====CODY DEBUG INFO STARTS HERE=====
00000096 52.73935318
00000097 52.73949051 tbs8921fe: Current Modulation is QPSK
00000098 52.73949432 tbs8921fe: Current Mode Code is 3/4
00000099 52.73990250 tbs8921fe: Current Tuner PLL Frequency is 1421997 kHz
00000100 52.74078369 tbs8921fe: Current Demod CTL Frequency is 2981 kHz
00000101 52.74105835 tbs8921fe: Current Symbol Rate Offset is 0 kSps
00000102 52.74119568 tbs8921fe: INVERSION -> OFF
00000103 52.74119568
00000104 52.74119568 =====CODY DEBUG INFO ENDS HERE=====
00000105 52.74119568
00000106 53.05213165 =====CODY DEBUG INFO STARTS HERE=====
00000107 53.05213165
00000108 53.05226898 tbs8921fe: Current Modulation is QPSK
00000109 53.05227280 tbs8921fe: Current Mode Code is 3/4
00000110 53.05267334 tbs8921fe: Current Tuner PLL Frequency is 1421997 kHz
00000111 53.05396271 tbs8921fe: Current Demod CTL Frequency is 2980 kHz
00000112 53.05423355 tbs8921fe: Current Symbol Rate Offset is 0 kSps
00000113 53.05437088 tbs8921fe: INVERSION -> OFF
00000114 53.05437088
00000115 53.05437469 =====CODY DEBUG INFO ENDS HERE=====
00000116 53.05437469
00000117 53.36740875 =====CODY DEBUG INFO STARTS HERE=====
00000118 53.36740875
00000119 53.36754990 tbs8921fe: Current Modulation is QPSK
00000120 53.36754990 tbs8921fe: Current Mode Code is 3/4
00000121 53.36796188 tbs8921fe: Current Tuner PLL Frequency is 1421997 kHz
00000122 53.36911774 tbs8921fe: Current Demod CTL Frequency is 2982 kHz
00000123 53.36939240 tbs8921fe: Current Symbol Rate Offset is 0 kSps
00000124 53.36952591 tbs8921fe: INVERSION -> OFF
00000125 53.36952972
00000126 53.36952972 =====CODY DEBUG INFO ENDS HERE=====
00000127 53.36952972
00000128 53.62459183 [136] BDA2: CDVBNetworkProviderFilter.DoDVBSTuning: put_Range 0xffffffff
00000129 53.62461472 [136]
00000130 78.62918091 [136] BDA2: CDVBNetworkProviderFilter.DoDVBSTuning: put_Range 0xffffffff
00000131 78.62919617 [136]
00000132 78.98818207 =====CODY DEBUG INFO STARTS HERE=====
00000133 78.98818207
00000134 78.98831940 tbs8921fe: Current Modulation is QPSK
00000135 78.98832703 tbs8921fe: Current Mode Code is 3/4
00000136 78.98873901 tbs8921fe: Current Tuner PLL Frequency is 1423997 kHz
00000137 78.98975372 tbs8921fe: Current Demod CTL Frequency is -2594 kHz
00000138 78.99002838 tbs8921fe: Current Symbol Rate Offset is 0 kSps
00000139 78.99016571 tbs8921fe: INVERSION -> OFF
00000140 78.99016571
00000141 78.99016571 =====CODY DEBUG INFO ENDS HERE=====
00000142 78.99016571
00000143 79.24000549 =====CODY DEBUG INFO STARTS HERE=====
00000144 79.24001312
00000145 79.24015045 tbs8921fe: Current Modulation is QPSK
00000146 79.24015045 tbs8921fe: Current Mode Code is 3/4
00000147 79.24056244 tbs8921fe: Current Tuner PLL Frequency is 1423997 kHz
00000148 79.24143982 tbs8921fe: Current Demod CTL Frequency is -2596 kHz
00000149 79.24171448 tbs8921fe: Current Symbol Rate Offset is 0 kSps
00000150 79.24185181 tbs8921fe: INVERSION -> OFF
00000151 79.24185181
00000152 79.24185181 =====CODY DEBUG INFO ENDS HERE=====
00000153 79.24185181
00000154 79.55265045 =====CODY DEBUG INFO STARTS HERE=====
00000155 79.55265045
00000156 79.55279541 tbs8921fe: Current Modulation is QPSK
00000157 79.55279541 tbs8921fe: Current Mode Code is 3/4
00000158 79.55319977 tbs8921fe: Current Tuner PLL Frequency is 1423997 kHz
00000159 79.55435944 tbs8921fe: Current Demod CTL Frequency is -2593 kHz
00000160 79.55463409 tbs8921fe: Current Symbol Rate Offset is 0 kSps
00000161 79.55476379 tbs8921fe: INVERSION -> OFF
00000162 79.55476379
00000163 79.55476379 =====CODY DEBUG INFO ENDS HERE=====
00000164 79.55476379
00000165 79.86012268 =====CODY DEBUG INFO STARTS HERE=====
00000166 79.86012268
00000167 79.86026001 tbs8921fe: Current Modulation is QPSK
00000168 79.86026001 tbs8921fe: Current Mode Code is 3/4
00000169 79.86067200 tbs8921fe: Current Tuner PLL Frequency is 1423997 kHz
00000170 79.86183167 tbs8921fe: Current Demod CTL Frequency is -2595 kHz
00000171 79.86210632 tbs8921fe: Current Symbol Rate Offset is 0 kSps
00000172 79.86224365 tbs8921fe: INVERSION -> OFF
00000173 79.86224365
00000174 79.86224365 =====CODY DEBUG INFO ENDS HERE=====
00000175 79.86224365
00000176 80.17250061 =====CODY DEBUG INFO STARTS HERE=====
00000177 80.17250061
00000178 80.17264557 tbs8921fe: Current Modulation is QPSK
00000179 80.17264557 tbs8921fe: Current Mode Code is 3/4
00000180 80.17305756 tbs8921fe: Current Tuner PLL Frequency is 1423997 kHz
00000181 80.17378998 tbs8921fe: Current Demod CTL Frequency is -2594 kHz
00000182 80.17406464 tbs8921fe: Current Symbol Rate Offset is 0 kSps
00000183 80.17419434 tbs8921fe: INVERSION -> OFF
00000184 80.17419434
00000185 80.17419434 =====CODY DEBUG INFO ENDS HERE=====
00000186 80.17419434
00000187 80.48513794 =====CODY DEBUG INFO STARTS HERE=====
00000188 80.48514557
00000189 80.48528290 tbs8921fe: Current Modulation is QPSK
00000190 80.48528290 tbs8921fe: Current Mode Code is 3/4
00000191 80.48569489 tbs8921fe: Current Tuner PLL Frequency is 1423997 kHz
00000192 80.48672485 tbs8921fe: Current Demod CTL Frequency is -2591 kHz
00000193 80.48699951 tbs8921fe: Current Symbol Rate Offset is 0 kSps
00000194 80.48713684 tbs8921fe: INVERSION -> OFF
00000195 80.48713684
00000196 80.48713684 =====CODY DEBUG INFO ENDS HERE=====
00000197 80.48713684
00000198 80.56707764 [136] BDA2: CDVBNetworkProviderFilter.DoDVBSTuning: put_Range 0xffffffff
00000199 80.56710052 [136]
00000200 105.57640839 [136] BDA2: CDVBNetworkProviderFilter.DoDVBSTuning: put_Range 0xffffffff
00000201 105.57642365 [136]
00000202 130.58204651 [136] BDA2: CDVBNetworkProviderFilter.DoDVBSTuning: put_Range 0xffffffff
00000203 130.58207703 [136]
00000204 132.67475891 =====CODY DEBUG INFO STARTS HERE=====
00000205 132.67475891
00000206 132.67489624 tbs8921fe: Current Modulation is QPSK
00000207 132.67491150 tbs8921fe: Current Mode Code is 3/4
00000208 132.67532349 tbs8921fe: Current Tuner PLL Frequency is 1427003 kHz
00000209 132.67633057 tbs8921fe: Current Demod CTL Frequency is -2027 kHz
00000210 132.67660522 tbs8921fe: Current Symbol Rate Offset is 0 kSps
00000211 132.67674255 tbs8921fe: INVERSION -> OFF
00000212 132.67674255
00000213 132.67674255 =====CODY DEBUG INFO ENDS HERE=====
00000214 132.67674255
00000215 132.82905579 =====CODY DEBUG INFO STARTS HERE=====
00000216 132.82905579
00000217 132.82919312 tbs8921fe: Current Modulation is QPSK
00000218 132.82919312 tbs8921fe: Current Mode Code is 3/4
00000219 132.82963562 tbs8921fe: Current Tuner PLL Frequency is 1427003 kHz
00000220 132.83065796 tbs8921fe: Current Demod CTL Frequency is -2027 kHz
00000221 132.83093262 tbs8921fe: Current Symbol Rate Offset is 0 kSps
00000222 132.83106995 tbs8921fe: INVERSION -> OFF
00000223 132.83106995
00000224 132.83106995 =====CODY DEBUG INFO ENDS HERE=====
00000225 132.83106995
00000226 133.13543701 =====CODY DEBUG INFO STARTS HERE=====
00000227 133.13543701
00000228 133.13557434 tbs8921fe: Current Modulation is QPSK
00000229 133.13557434 tbs8921fe: Current Mode Code is 3/4
00000230 133.13598633 tbs8921fe: Current Tuner PLL Frequency is 1427003 kHz
00000231 133.13687134 tbs8921fe: Current Demod CTL Frequency is -2025 kHz
00000232 133.13714600 tbs8921fe: Current Symbol Rate Offset is 0 kSps
00000233 133.13728333 tbs8921fe: INVERSION -> OFF
00000234 133.13728333
00000235 133.13728333 =====CODY DEBUG INFO ENDS HERE=====
00000236 133.13728333
00000237 133.44989014 =====CODY DEBUG INFO STARTS HERE=====
00000238 133.44989014
00000239 133.45002747 tbs8921fe: Current Modulation is QPSK
00000240 133.45004272 tbs8921fe: Current Mode Code is 3/4
00000241 133.45045471 tbs8921fe: Current Tuner PLL Frequency is 1427003 kHz
00000242 133.45133972 tbs8921fe: Current Demod CTL Frequency is -2026 kHz
00000243 133.45159912 tbs8921fe: Current Symbol Rate Offset is 0 kSps
00000244 133.45173645 tbs8921fe: INVERSION -> OFF
00000245 133.45173645
00000246 133.45173645 =====CODY DEBUG INFO ENDS HERE=====
00000247 133.45173645
00000248 133.76351929 =====CODY DEBUG INFO STARTS HERE=====
00000249 133.76351929
00000250 133.76365662 tbs8921fe: Current Modulation is QPSK
00000251 133.76365662 tbs8921fe: Current Mode Code is 3/4
00000252 133.76406860 tbs8921fe: Current Tuner PLL Frequency is 1427003 kHz
00000253 133.76495361 tbs8921fe: Current Demod CTL Frequency is -2024 kHz
00000254 133.76522827 tbs8921fe: Current Symbol Rate Offset is 0 kSps
00000255 133.76536560 tbs8921fe: INVERSION -> OFF
00000256 133.76538086
00000257 133.76538086 =====CODY DEBUG INFO ENDS HERE=====
00000258 133.76538086
00000259 134.07603455 =====CODY DEBUG INFO STARTS HERE=====
00000260 134.07603455
00000261 134.07617188 tbs8921fe: Current Modulation is QPSK
00000262 134.07617188 tbs8921fe: Current Mode Code is 3/4
00000263 134.07658386 tbs8921fe: Current Tuner PLL Frequency is 1427003 kHz
00000264 134.07746887 tbs8921fe: Current Demod CTL Frequency is -2026 kHz
00000265 134.07774353 tbs8921fe: Current Symbol Rate Offset is 0 kSps
00000266 134.07788086 tbs8921fe: INVERSION -> OFF
00000267 134.07788086
00000268 134.07788086 =====CODY DEBUG INFO ENDS HERE=====
00000269 134.07788086
00000270 134.38851929 =====CODY DEBUG INFO STARTS HERE=====
00000271 134.38851929
00000272 134.38865662 tbs8921fe: Current Modulation is QPSK
00000273 134.38865662 tbs8921fe: Current Mode Code is 3/4
00000274 134.38905334 tbs8921fe: Current Tuner PLL Frequency is 1427003 kHz
00000275 134.39019775 tbs8921fe: Current Demod CTL Frequency is -2025 kHz
00000276 134.39047241 tbs8921fe: Current Symbol Rate Offset is 0 kSps
00000277 134.39060974 tbs8921fe: INVERSION -> OFF
00000278 134.39060974
00000279 134.39060974 =====CODY DEBUG INFO ENDS HERE=====
00000280 134.39060974
00000281 134.70101929 =====CODY DEBUG INFO STARTS HERE=====
00000282 134.70101929
00000283 134.70115662 tbs8921fe: Current Modulation is QPSK
00000284 134.70115662 tbs8921fe: Current Mode Code is 3/4
00000285 134.70156860 tbs8921fe: Current Tuner PLL Frequency is 1427003 kHz
00000286 134.70259094 tbs8921fe: Current Demod CTL Frequency is -2025 kHz
00000287 134.70285034 tbs8921fe: Current Symbol Rate Offset is 0 kSps
00000288 134.70298767 tbs8921fe: INVERSION -> OFF
00000289 134.70298767
00000290 134.70298767 =====CODY DEBUG INFO ENDS HERE=====
00000291 134.70298767
00000292 135.01339722 =====CODY DEBUG INFO STARTS HERE=====
00000293 135.01339722
00000294 135.01353455 tbs8921fe: Current Modulation is QPSK
00000295 135.01353455 tbs8921fe: Current Mode Code is 3/4
00000296 135.01394653 tbs8921fe: Current Tuner PLL Frequency is 1427003 kHz
00000297 135.01483154 tbs8921fe: Current Demod CTL Frequency is -2026 kHz
00000298 135.01510620 tbs8921fe: Current Symbol Rate Offset is 0 kSps
00000299 135.01524353 tbs8921fe: INVERSION -> OFF
00000300 135.01524353
00000301 135.01524353 =====CODY DEBUG INFO ENDS HERE=====
00000302 135.01524353
00000303 135.32604980 =====CODY DEBUG INFO STARTS HERE=====
00000304 135.32604980
00000305 135.32618713 tbs8921fe: Current Modulation is QPSK
00000306 135.32620239 tbs8921fe: Current Mode Code is 3/4
00000307 135.32659912 tbs8921fe: Current Tuner PLL Frequency is 1427003 kHz
00000308 135.32762146 tbs8921fe: Current Demod CTL Frequency is -2024 kHz
00000309 135.32789612 tbs8921fe: Current Symbol Rate Offset is 0 kSps
00000310 135.32803345 tbs8921fe: INVERSION -> OFF
00000311 135.32803345
00000312 135.32803345 =====CODY DEBUG INFO ENDS HERE=====
00000313 135.32803345
00000314 135.63856506 =====CODY DEBUG INFO STARTS HERE=====
00000315 135.63856506
00000316 135.63870239 tbs8921fe: Current Modulation is QPSK
00000317 135.63870239 tbs8921fe: Current Mode Code is 3/4
00000318 135.63911438 tbs8921fe: Current Tuner PLL Frequency is 1427003 kHz
00000319 135.64013672 tbs8921fe: Current Demod CTL Frequency is -2026 kHz
00000320 135.64041138 tbs8921fe: Current Symbol Rate Offset is 0 kSps
00000321 135.64054871 tbs8921fe: INVERSION -> OFF
00000322 135.64054871
00000323 135.64054871 =====CODY DEBUG INFO ENDS HERE=====
00000324 135.64054871
00000325 135.92503357 [136] BDA2: CDVBNetworkProviderFilter.DoDVBSTuning: put_Range 0xffffffff
00000326 135.92504883 [136]
00000327 160.93009949 [136] BDA2: CDVBNetworkProviderFilter.DoDVBSTuning: put_Range 0xffffffff
00000328 160.93011475 [136]
00000329 185.93461609 [136] BDA2: CDVBNetworkProviderFilter.DoDVBSTuning: put_Range 0xffffffff
00000330 185.93463135 [136]
The card does not tune on the correct frequencies. When it tunes the Carrier Track Loop is far outside the center. The log only shows the result but not the reason. I guess you hardware eng. has to dig deep
Here's how it should look like (TeVii) It also shows that the TBS hits are not even on neighbour transponders. The correct order of channel names is: PAYAM TV, AL-FORAT, BELADI TV) It's even worse than I thought
- Derrick
- Posts: 91
- Joined: Sun Jul 04, 2010 6:49 pm
Re: Poor Performance
by cody » Sun Feb 20, 2011 10:26 pm
Derrick, sorry that i wasn't able to answer you earlier, but we're preparing for CeBIT 2011 and there is almost no time left.
let me comment:
please, note that "Carrier Track Loop" is not equal to "frequency offset" and exactly the contrary - it tries to compensate in case there is frequency offset added by something in your environment like LNB, etc. also, it seems you need to change the frequency exactly to lower the frequency offset and it to become in the range of auto-frequency-acquisition. so, what i'm trying to say is that it seems only when for example you use 11177MHz the CTL is something small like -2 MHz to be inside the auto-frequency-acquisition and your 8921 to be actually able to acquire lock. i think i should find way to modify the driver to report CTL every few milliseconds even when there is no lock to confirm that using anything else in this case than 11177MHz results in huge CTL offset. in any case it's still seem to me like something in your environment is causing frequency offset and i'm not saying that to blame it's fault of someone else - it's just how it looks to me at the moment and i will do everything possible to find the objective answer what it is.
i can't quite agree with this:
or more specifically why you think transponder frequencies on which your TBS 8921 card acquired lock are not the correct one considering the possibility there is some frequency offset in your environment. how can be sure that how the TeVii hardware handle the frequency offset is correct? maybe, i'm missing your point, but at least without test with at least another LNB (if nothing else different) and/or equipment that reports frequency offset (i.e. something else that report similar information as the debug output i added to 8921 driver) you can't be sure what is right and what not. i understand 8921 works weird for you compared to the TeVii card, but that doesn't give any objective technical answers or again maybe i'm missing your point and we think in a different aspect. anyway, i will test myself on the 3 transponders from 10E you gave as example here. please, if you find something else in the mean time let me know - in any case we should be able to fix what's wrong as soon as we actually confirmed there is something wrong in the general case and not something triggered by a particular environment. also, i want to apologize in advance in case there is delay in my answers until CeBIT 2011 is over.
let me comment:
When it tunes the Carrier Track Loop is far outside the center
please, note that "Carrier Track Loop" is not equal to "frequency offset" and exactly the contrary - it tries to compensate in case there is frequency offset added by something in your environment like LNB, etc. also, it seems you need to change the frequency exactly to lower the frequency offset and it to become in the range of auto-frequency-acquisition. so, what i'm trying to say is that it seems only when for example you use 11177MHz the CTL is something small like -2 MHz to be inside the auto-frequency-acquisition and your 8921 to be actually able to acquire lock. i think i should find way to modify the driver to report CTL every few milliseconds even when there is no lock to confirm that using anything else in this case than 11177MHz results in huge CTL offset. in any case it's still seem to me like something in your environment is causing frequency offset and i'm not saying that to blame it's fault of someone else - it's just how it looks to me at the moment and i will do everything possible to find the objective answer what it is.
i can't quite agree with this:
Here's how it should look like (TeVii) It also shows that the TBS hits are not even on neighbour transponders. The correct order of channel names is: PAYAM TV, AL-FORAT, BELADI TV)
or more specifically why you think transponder frequencies on which your TBS 8921 card acquired lock are not the correct one considering the possibility there is some frequency offset in your environment. how can be sure that how the TeVii hardware handle the frequency offset is correct? maybe, i'm missing your point, but at least without test with at least another LNB (if nothing else different) and/or equipment that reports frequency offset (i.e. something else that report similar information as the debug output i added to 8921 driver) you can't be sure what is right and what not. i understand 8921 works weird for you compared to the TeVii card, but that doesn't give any objective technical answers or again maybe i'm missing your point and we think in a different aspect. anyway, i will test myself on the 3 transponders from 10E you gave as example here. please, if you find something else in the mean time let me know - in any case we should be able to fix what's wrong as soon as we actually confirmed there is something wrong in the general case and not something triggered by a particular environment. also, i want to apologize in advance in case there is delay in my answers until CeBIT 2011 is over.
- cody
- Posts: 627
- Joined: Tue Apr 13, 2010 11:20 pm
Re: Poor Performance
by Derrick » Mon Feb 21, 2011 1:53 am
cody Wrote:..considering the possibility there is some frequency offset in your environment.
.....cut the crap. Of course there will be a measurable offset in my environment but how can it be possible that the offset is +2982 kHz and at the same time -2596 kHz in a small band of less than 10MHz? I have also 2 STBs that lock in the same order as the TeVii and there are also transponder lists readily available.
The problem is that frequency acquisition is not working properly in a densely populated frequency spectrum. When there is energy close to the wanted carrier the tuner will lock onto the wrong frequency. The proof is shown above in the huge CTL deviation of almost +-3MHz from the nominal frequency.
cody Wrote:..anyway, i will test myself on the 3 transponders from 10E you gave as example here.
..that you should have done long time instead of not taking me seriously
- Derrick
- Posts: 91
- Joined: Sun Jul 04, 2010 6:49 pm
Re: Poor Performance
by Derrick » Mon Feb 21, 2011 5:20 am
cody Wrote:i can't quite agree with this:Here's how it should look like (TeVii) It also shows that the TBS hits are not even on neighbour transponders. The correct order of channel names is: PAYAM TV, AL-FORAT, BELADI TV)
or more specifically why you think transponder frequencies on which your TBS 8921 card acquired lock are not the correct one considering the possibility there is some frequency offset in your environment. how can be sure that how the TeVii hardware handle the frequency offset is correct? maybe, i'm missing your point, but at least without test with at least another LNB (if nothing else different) and/or equipment ..
here you are:
- Derrick
- Posts: 91
- Joined: Sun Jul 04, 2010 6:49 pm
29 posts
• Page 2 of 3 • 1, 2, 3
Who is online
Users browsing this forum: No registered users and 1 guest