Re: DiB3000MC rewritten and MT2060 is ready to go into main

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 30 Jul, matthieu castet wrote:
> Hi,
> 
> matthieu castet wrote:
>> Patrick Boettcher wrote:
>> 
>>> Hi,
>>>
>>>
>>> I tried with a Yuan-device and with the reference design from DiBcom. 
>>> It was OK (for a device with mt2060). Maybe the mt2060 needs some 
>>> stabilization after setting the frequency...
>>>
>>> Can you try putting a msleep(50) or even 100 at the end of the 
>>> mt2060_set_params function.
>> 
>> I doesn't help.
>> 
>> I have put a sample of what I get with the new driver here : 
>> http://castet.matthieu.free.fr/broken/T-8442-1-273 (old driver give me 
>> http://castet.matthieu.free.fr/broken/T-8442-1-273.ok)
>> 
> I ported your signal strength mod and the signal value is completly 
> different :
> with the old driver I get 50%
> with the new one 5%.
> 
>

I also see that the signal strength is reduced with the new driver, only
in my case I still have a good reception, on the contrary this may even have
participated to avoid another problem (described my other answer of this
thread). With the new driver the tzap commands gives me:

tuning to 714167000 Hz
video pid 0x0078, audio pid 0x0082
status 07 | signal b962 | snr 0000 | ber 001fffff | unc 00000000 | 
status 1f | signal b977 | snr 0000 | ber 00000000 | unc 00000005 | FE_HAS_LOCK
status 1f | signal b96a | snr 0000 | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status 1f | signal b971 | snr 0000 | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status 1f | signal b97b | snr 0000 | ber 00000070 | unc 00000000 | FE_HAS_LOCK
status 1f | signal b97c | snr 0000 | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status 1f | signal b977 | snr 0000 | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status 1f | signal b987 | snr 0000 | ber 00000000 | unc 00000000 | FE_HAS_LOCK

where the signal strenght of b987 corresponds to roughly 70% and
normally I have a perfect reception 100% (also according to another TNT-Tuner, 
a Thomson DTI 1001). The old driver gave me:

tuning to 714167000 Hz
video pid 0x0078, audio pid 0x0082
status 03 | signal bb17 | snr 0000 | ber 001fffff | unc 0000ffff | 
status 1f | signal ba37 | snr 0000 | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status 1f | signal 0000 | snr ffff | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status 1f | signal 0000 | snr ffff | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status 1f | signal 0000 | snr ffff | ber 00000000 | unc 00000000 | FE_HAS_LOCK

and I think the signal "0000" is in reality 100% and I am convinced that my
reception is indeed 100% (an external amplified antenna) despite the fact 
that I use a T-peace in the antenna connection (which is normally not very good). 

Even without the T-peace and the new driver I get:

tuning to 714167000 Hz
video pid 0x0078, audio pid 0x0082
status 07 | signal bc20 | snr 0000 | ber 001fffff | unc 00000000 | 
status 1f | signal bc2e | snr 0000 | ber 00000000 | unc 00000001 | FE_HAS_LOCK
status 1f | signal bc23 | snr 0000 | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status 1f | signal bc26 | snr 0000 | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status 1f | signal bc29 | snr 0000 | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status 1f | signal bc34 | snr 0000 | ber 00000000 | unc 00000000 | FE_HAS_LOCK

and this is only slightly higher than (bc20 to b970) in the case with T-peace.

In any case I have always a good reception, there is not the slightest
quality problem for the video. 


I do not know which case is "correct" and what this all means but I
believe there are two issus:

1) There is a different, quite lower resulting signal strength in the
   new driver, I would think that this is not real and a bug, but I am
   certainly not sure of this. 

2) There is likely another bug (certainly in the old driver and may be
   also in the new one ???) concerning the case when the signal is very
   strong giving "0000" and in my case this creates the problem which I
   described earlier that I need to get a 2nd lock immediately after a
   first one for the video flux to start (for example by stop/play in
   VLC or use of tzap with the option "-x" before starting VLC). In my
   impression the first issue may have accidentally solved the problem
   for the second one (because there is no longer a 100% signal
   strength). 


Hopefully, this information may give some hint to understand what is
happening.

Greetings, Klaus.

_______________________________________________

linux-dvb@xxxxxxxxxxx
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

[Index of Archives]     [Linux Media]     [Video 4 Linux]     [Asterisk]     [Samba]     [Xorg]     [Xfree86]     [Linux USB]

  Powered by Linux