No Very Low SR Lock with latest Drivers

[satesco]

Your signal is a little bit better than mine

Signal is really better from the moment when I installed the 1.0.1.8 driver.In fact, as I said on another topic, is a potentiation of signal from software since 1.0.1.7 driver version was lunched.This occurred at the request of users who wanted to increase quality signal !?!But the effect is paradoxical, on the one hand, we have a better signal, apparently, on the other hand has consequences when we scan with TBS BlindScan.And because many users complained that this tool scans slowly compared with CrazyCat's BS ,a compromise was made to software that has a negative effect when scanning with TBS 6925 BlindScan.This time it scans faster than before{betatesters time} but efficiency has dropped considerably.TBS BlindScan now scan quickly but he loses more data in the search for frequencies.For this reason transponders with low s.r. must be searched by hand, because blindscan do not find them at overall scanning.But even when you scan manual can not be sure that you lock signal.And here this is where other factors involved not related to software card, but the characteristics of the reception facility that we have{a big dish,a good lnb,etc and the absence of a conflict between drivers in PC,or registry problems,and who knows}.And precisely for these personal characteristics results may not be valid for all users regardless of operating system tbs6925 card is working.Each update driver solve a problem, but it seems that create others,and one of them is these low sr.!All these reasons and others that appear in the update of drivers, I do say that somehow we are all without want some sort of betatesters.For this reason the engineers of this card should eliminate any bugs that still exist in their updated drivers.And I must admit that is not easy task;for example when changing channels with low SR{this 334} with a larger one{over 1000 ks} is slower and lasts longer.
I do not know what is the solution for each case, but manufacturers of this card have to work hard on it for us to benefit fully and without the hassle of news that brings this card to changing market of this type of products.
Beginning made by CrazyCat's software, which forced the Chinese to adapt the product to users needs.But the great challenge for TBS6925 card will come when other producers{ProfRevolution,Omicom,etc} of Dvbs PC Card will launch their products...
I am allowed to give a more elaborate and probably wrong answer,but the experience I had with this card for almost six months forced me to make these observations.Not be bad that others do the same.I hope to be understood correctly by manufacturers and users alike.And I would enjoy if you, Derrick, which know how it works these types of pc card to intervene if you think it deserves.Thanks.

[Derrick]

Each update driver solve a problem, but it seems that create others,and one of them is these low sr.!

..it seems that some manufacturers create more new problems than they solve In this case I don't understand that 1.0.1.11 has been officially released while still under investigation

» Sun Sep 18, 2011 2:28 am
Hi

We will have a check too.

Does TBS left hand know what the right hand is doing?

[DVB]

About signal increase:

In fact there were no changes in signal between any driver version. Look at CrazyScan - I got with both 1.0.1.7 and 1.0.1.11 in CrazyScan the same levels of RF Level & Signal/Noise.Percent values that You are seeing in AltDVB or any other DVB app are just counted in other way, but still from the same RF Level & the same Signal/Noise ratio. Crazycat made for AltDVB special BDA2 device interface where You can swith to other way of showing signal strength & quality (by LevelsType option). This is just counting method and have no impact on receiving. On 1.0.1.7 and 1.0.1.11 I got the same levels if I switch to LevelsType=1 in BDA2 device interface, so drivers didn't made any changes for signal reception.

Only thing that could have impact on low SR blindscanning was speed up of locking (probably by increasing of speed of I2C communication).

If solution for this is to decrease I2C speed - In my opinion low SR's below 1000 KS/s are not worth to do that. Blindscan done for 10E, 7E etc. with new drivers and old drivers for transmissions above 1000 KS/s works the same, it didn't missed any channel for me.

The only reasonable way is to try fix low SR's without touching speed. Why? Speed of locking with drivers below 1.0.1.7 was just bad, very bad. In compare with Prof7301 locking & Blindscan speed was slower in TBS6925 (and it was even slower than in TBS6925 V1). For me that was not acceptable. Fixes from drivers 1.0.1.9 and higher finally made speed of locking just what it should be.

PS: Drivers 1.0.1.9 had bug with locking (sometimes signal is present, but stream is not available), use 1.0.1.11.

[Derrick]

In my opinion low SR's below 1000 KS/s are not worth to do that.

If that's the company's policy I'd recommend to purchase much cheaper cards from other manufacturers. Btw. this is not about blind scan but about locking of VLSR carriers as such.

[DVB]

But I'm not from TBS - that's my private opinion as user.

If card must work nearly two times slower (!) just to give ability to BS few low SR transmissions of radio channels - it is just not worth that (as these transmissions still can be received, just maybe not blindscanned).

If any future drivers update will decrease speed to old possibilities, I won't update drivers anymore and stay with 1.0.1.11, which is blazin' fast and in BLScan from crazycat catch everything that TBS6925 catched in BLScan before.

Maybe there is way to fix low SR's without touching speed? If no - because of my previous experiences with other DVB cards & TBS6925 V1 I'm going to stay with latest "fast" release.

User sotos65 showed screenshots that locking is possible with 1.0.1.11, I also can correctly receive low SR transmissions at 1.0.1.11 (checked at 8W at 12,748H), so VLSR carries locking works here. I'm reading this topis and I see that it is only about BS problem, only with TBS BS Tool. If I'm wrong - please clear where the problem lies - what cannot be received anymore? At what app?

[Derrick]

If any future drivers update will decrease speed to old possibilities, I won't update drivers anymore and stay with 1.0.1.11

I'm not talking about blind scan but about the locking capabilty of VLSR_carriers which is lost with 1.0.1.11. These carries of <500kbaud were never found by blind scan.

Talking about blind scan speed. A test with Easy BlindScan (crazyscan engine ) doesn't show significant differences between the different drivers. A Prof7500 is as fast or even faster though it locks VLSR_carriers better and more reliable than TBS2965. So what is your point?

Code: Select All Code


TBS6925 Driver_V1.0.1.11

21:39:12.171:   Easy BlindScan 2.0.0.4 [Copyright © Cjcr-Software 2011]
21:39:12.171:   .NET Framework Environment: 2.0.50727.42
21:39:12.171:   BLScan - BlindScan tool 1.0.0.682-commited [Copyright (C) 2010-2011 CrazyCat <crazycat69@narod.ru>]
21:39:12.171:   StreamReaderEx for BDA Tuners 1.0.6.682 [Copyright (C) 2010-2011 CrazyCat <crazycat69@narod.ru>]
21:39:12.171:   OS: Windows XP
21:39:12.265:   Profile loaded (16E)
21:39:12.359:   Load done.
21:39:31.187:   --> Starting BLScan (profiles\16E.ini)
21:39:31.187:      DVBCard: TBS 6925 DVBS/S2 Tuner, SatID: 0160
21:39:31.187:         Scan Range 0: 10980-11080 Mhz, 1000-10000 Ks, Horizontal, Steps: 2 Mhz.
21:39:31.187:         Scan Range 1: 12550-12750 Mhz, 1000-10000 Ks, Vertical, Steps: 2 Mhz.
21:41:01.593:      Transponders found: 13, total scan time: 88.485s
21:41:01.593:   <-- BLScan = OK. Time running: 00:01:22, N-TP: 13


Prof7500 DRiver_V2.0.0.5

22:01:44.750:   Easy BlindScan 2.0.0.4 [Copyright © Cjcr-Software 2011]
22:01:44.750:   .NET Framework Environment: 2.0.50727.42
22:01:44.750:   BLScan - BlindScan tool 1.0.0.682-commited [Copyright (C) 2010-2011 CrazyCat <crazycat69@narod.ru>]
22:01:44.750:   StreamReaderEx for BDA Tuners 1.0.6.682 [Copyright (C) 2010-2011 CrazyCat <crazycat69@narod.ru>]
22:01:44.750:   OS: Windows XP
22:01:44.843:   Profile loaded (16E)
22:01:44.859:   Load done.
22:01:47.171:   --> Starting BLScan (profiles\16E.ini)
22:01:47.171:      DVBCard: Prof 7500 DVBS Tuner, SatID: 0160
22:01:47.171:         Scan Range 0: 10980-11080 Mhz, 1000-10000 Ks, Horizontal, Steps: 2 Mhz.
22:01:47.171:         Scan Range 1: 12550-12750 Mhz, 1000-10000 Ks, Vertical, Steps: 2 Mhz.
22:02:58.406:      Transponders found: 14, total scan time: 69.719s
22:02:58.406:   <-- BLScan = OK. Time running: 00:01:05, N-TP: 14

TBS6925Driver_V1.0.1.8

22:13:54.921:   Easy BlindScan 2.0.0.4 [Copyright © Cjcr-Software 2011]
22:13:54.921:   .NET Framework Environment: 2.0.50727.42
22:13:54.921:   BLScan - BlindScan tool 1.0.0.682-commited [Copyright (C) 2010-2011 CrazyCat <crazycat69@narod.ru>]
22:13:54.921:   StreamReaderEx for BDA Tuners 1.0.6.682 [Copyright (C) 2010-2011 CrazyCat <crazycat69@narod.ru>]
22:13:54.921:   OS: Windows XP
22:13:55.015:   Profile loaded (16E)
22:13:55.031:   Load done.
22:13:59.031:   --> Starting BLScan (profiles\16E.ini)
22:13:59.031:      DVBCard: TBS 6925 DVBS/S2 Tuner, SatID: 0160
22:13:59.031:         Scan Range 0: 10980-11080 Mhz, 1000-10000 Ks, Horizontal, Steps: 2 Mhz.
22:13:59.031:         Scan Range 1: 12550-12750 Mhz, 1000-10000 Ks, Vertical, Steps: 2 Mhz.
22:15:42.953:      Transponders found: 12, total scan time: 102.484s
22:15:42.953:   <-- BLScan = OK. Time running: 00:01:35, N-TP: 12

22:18:19.921:   --> Starting BLScan (profiles\16E.ini)
22:18:19.937:      DVBCard: TBS 6925 DVBS/S2 Tuner, SatID: 0160
22:18:19.937:         Scan Range 0: 10980-11080 Mhz, 1000-10000 Ks, Horizontal, Steps: 2 Mhz.
22:18:19.937:         Scan Range 1: 12550-12750 Mhz, 1000-10000 Ks, Vertical, Steps: 2 Mhz.
22:20:00.531:      Transponders found: 13, total scan time: 99.157s
22:20:00.531:   <-- BLScan = OK. Time running: 00:01:31, N-TP: 13


[DVB]

VLSR carriers are still lockable with 1.0.1.11 drivers - look at sotos65 screenshot with 331 KS/s SR.

Speed: differences in CrazyScan between 1.0.1.7 and 1.0.1.11 are gigantic at that is my point. Spectrum analyzer works much faster, every lock of IQScan is faster and also any relock between any two frequencies with any DVB app. That can be easily feeled when working with any DVB app.

In fact now I completely don't understand where is the problem.

VLSR carriers were lockable at 1.0.1.7 and are still lockable at 1.0.1.11
Blindscan of SR < 500 KS/s didn't work at 1.0.1.7 and still not work at 1.0.1.11 (I assumed that it worked as topic started about complain that TBS BS Tool have some problems)

[Derrick]

look at sotos65 screenshot with 331 KS/s SR.

maybe he was just lucky and/or he has a better S/N than I have Further he confirms the issue as does @Tempo.

With my setup, V1.0.1.11 provides 0% locks for 334kbaud compared to 100% with V1.0.1.8 and Prof7500 (locking is more reliable).

@DVB you want a fast driver. I prefer a reliable driver. Let TBS make their homework to provide a fast and reliable driver

[steven]

Hi DVB and Derrick

Thanks for your interest in our card,about the speed maybe i need give you some explain,
If the speed is slow the driver have more time to search TP so the Low SR can be locked.
and if the speed is quick maybe some Low SR TP will be lost.
and the V1.0.1.12 driver the only difference with V1.0.1.11 is the speed.
V1.0.1.11 quickly
V1.0.1.12 slowly
so if you want the quick speed you can use V1.0.1.11,and if you want a reliable driver you can use V1.0.1.12.
here is the V1.0.1.12 driver linker: just need you test Derrick have Confirmed that it is ok,just need more test.
if it is ok ,we will publish it.
http://hotfile.com/dl/130146255/74432e3 ... 2.rar.html

Thanks

[Derrick]

yes, reliable locks of VLSR carriers with V1.0.1.12

Even direct tuning with tsreader is possible, though it will result in a long time out, if not successful. But this will be only a concern for users, who are trying to receive vlsr Blind scan speed is still reasonably fast.