TBS 6921 release date

[cody]

@cody:

Is it also possible to post a link to the blind scan tool if it is not "secret" of course I don't mind if there are errors or it is still a development version, I am sure users will be very interested in testing the BS function.

it's available on 6921/8921/5921 installation CDs and it's not a secret at all, but it can work only with the mentioned hardware and it checks for such hardware, the reason for that is because blind-scan is completely hardware feature and no any other hardware has chip capable to do DVB-S/DVB-S2 blind-scan. i'm really overloaded with work and that's why i didn't post screenshots yet, but i saw in TBS 8921 forum there are some posts with very comprehensive feedback and thus the user there can post screenshots and give you information from his experience as user or 8921 - after all we're forum community and we should help each other.

[BluetoothBG]

cody, thank you for your answer!

I feel kind of stupid about not checking the installation CD first, but I just installed the card (TBS6921) and downloaded the latest driver from the site... Later today I will see the CD and post some screenshots in this topic.

Thanks again for the great hardware and support!

[BluetoothBG]

Here are the screenshots:

[BlindFaith]

Could you explain, how the frequencies are calculated?

[BluetoothBG]

Honestly, I have no idea This is a scan on 0.8W and it shows different frequencies each time. Below are the results of two consecutive scans within 5 minutes with no modification of the input parameters.

Code: Select All Code

Carrier_Freq(KHz)   Symbol_Rate(KHz)   Oper_Mode
12221194         24499      DVBS-QPSK ,FEC 7/8
12252437         24499      DVBS-QPSK ,FEC 7/8
12362323         12891      DVBS-QPSK ,FEC 5/6
12576811         28000      DVBS-QPSK ,FEC 7/8
12615172         28000      DVBS-QPSK ,FEC 7/8
12653528         28000      DVBS-QPSK ,FEC 7/8
12691605         30000      DVBS2-8PSK ,FEC 3/4
12730232         28000      DVBS-QPSK ,FEC 5/6
12768578         28000      DVBS-QPSK ,FEC 7/8


Code: Select All Code

Carrier_Freq(KHz)   Symbol_Rate(KHz)   Oper_Mode
12096203         24499      DVBS-QPSK ,FEC 7/8
12127455         24499      DVBS-QPSK ,FEC 7/8
12221206         24499      DVBS-QPSK ,FEC 7/8
12252447         24499      DVBS-QPSK ,FEC 7/8
12326352         15000      DVBS2-8PSK ,FEC 5/6
12576821         28000      DVBS-QPSK ,FEC 7/8
12615182         28000      DVBS-QPSK ,FEC 7/8
12653548         28000      DVBS-QPSK ,FEC 7/8
12730249         28000      DVBS-QPSK ,FEC 5/6
12768595         28000      DVBS-QPSK ,FEC 7/8


I see that Geezerjem is asking the same question in his topic "New 8921 owner's progress, need help...." so I guess we will have to wait for cody to explain.

[starman345]

Thanks for those screenshots, helps me understand how the software works. So after blindscanning you click on "output channel info" and it brings up another screen or does it offer to export to a folder on your computer?
The frequencies make no sense to me either, hopefully Cody can shed some light on it? If we can't calculate the actual frequency there is no way to use the blind scanned channels in another dvb application.

[BlindFaith]

This is a scan on 0.8W and it shows different frequencies each time. Below are the results of two consecutive scans within 5 minutes with no modification of the input parameters.

..doesn't make much sense to me. I've compared it to my 1W_transponder_list but couldn't find a match. In particular the 30MS/s transponder should be in both scans. Maybe we should redefine the term blind scan?

[BluetoothBG]

@starman345:
You're welcome! Clicking on the "Output Channel Info" button brings up a "Save file as..." dialog which outputs the file on the second screenshot. In his topic Geezerjem has found a constant which helps turning the BS results into a real frequency, but they are still not suitable for me.

@BlindFaith:
Yes it is strange, given the fact that on each scan there are different results. I hope that Cody will give us a little more information but let's not forget that this feature is still very experimental and under development.

[BlindFaith]

@BluetoothBG,
Maybe @Cody uses the workload as an excuse cos he can't figure out himself what has been programmed in some chinese backyard

I've tried with the help of @ Geezerjem's example to find a match for your blind scan results:

Code: Select All Code

12128-850=11278(V)
12221-850=11371(V)
   -> 11403V,24500 missing!!
12362-850=11512(V)   -> 12890KS/s (Feed?)
12577-850=11727(V)
12615-850=11765(V)
12654-850=11804(V)
   -> 11842V,30000 missing!!         
12730-850=11880(V)
12769-850=11919(V)
__________________

13352-1950=11402(V)
13677-1950=11727(V)
13715-1950=11765(V)
13754-1950=11804(V)
13792-1950=11842(V)   -> 30000KS/s
13830-1950=11880(V)
13869-1950=11919(V)

These are existing transponders on 1W. The frequencies are rounded cos it makes no sense to use KHz with normal lnbs
There are 2 missing transponders at the 1st try. Surprisingly the results cover low and high band transponders. I have no clue whether there is a general formular. The conclusion is, that atm the tool seems pretty useless..

/edit
seems to be all low band because the low band reaches up to 11950MHz (satzf 2150)

[cody]

@BluetoothBG,
Maybe @Cody uses the workload as an excuse cos he can't figure out himself what has been programmed in some chinese backyard

the blind-scan code (inside the driver) that controls the blind-scan capable part of the hardware is developed by NXP in the United States and the tool currently only visualizes (without any further processing) the data received by that code and the hardware.

for me there is nothing unclear about the output, but it could be confusing at the moment for regular users:

"transponder frequency" (in MHz) = LNB LOF (in MHz) + carrier_ferquency (in MHz)

22 kHz ON means LOF2 should be used in the above equation and OFF means LOF1 should be used.

also, i'm not even obligated to excuse myself in any way, because writing in the forum is just voluntarily work and i do it only if and when i have spare time for it.

the output i believe seems inconsistent to you, because the carrier_ferquency is in kHz of your rounded it to MHz with precision of 1MHz then the numbers on the different scans will be the same and when it's in kHz the numbers are different, because that is the frequency offset add by the LNB, which varies in every moment.

basically, what i'm getting from your posts is what processing in the "raw" data received by the hardware has to be done in the tool in order to be user-friendly and useful.