Reply to thread

Message

<blockquote data-quote="Bobben_no" data-source="post: 1157410" data-attributes="member: 339576">I have now tried a tbs6909 V2 card stid135-blindscan.&nbsp; It blindscans incredibily fast by using all eight adapters. But I notice that random transponders is not identified by the blindscan.&nbsp;&nbsp; I got the same problem when using only one adapter on TBS6909X V2 or using tbs6903x v1.2.I can see the same behaviour on many different satellite positions like 28E,13E,19E etc.&nbsp; but for those positions I have a diseqc switch that is causing distorted spectrum which I assume can make it harder to identify the spectrum peaks. For the 1-west satellite position I use no diseqc and the spectrum looks quite clean. See attached jpg from 1-WEST which shows spectrum and two random transponders not identified during that spesific scan.&nbsp; Btw. the blindscan is insane fast and completes in only 2 minutes for both pol and full L-band!I can tune to those transponders missed by blindscan by using tsduck and SNR is around 12dB which should be more than enough.&nbsp; It also works in tsduck even if I deliberately set incorrect parameters for symbolrate,FEC,delivery system.&nbsp; I assume that means that the blindscan driver is able to identify those transponders without any problem.[CODE]stid135-blindscan -c blindscan --fft-size 256 --search-range 10000 -U0 -C0 -a 4 5 6 7 8 9 10 11 --rf-in=0 -pBOTH -s 10650000 -e 12750000 --spectral-resolution 100[/CODE]Extract from the horisontal peaks_rf0_H.txt file shows those two transponders is not detected as peaks:[CODE]..11784.600000 2770000011822.800000 2910000011861.300000 2770000011899.100000 2690000011937.800000 2790000012014.600000 2950000012091.400000 2670000012129.000000 27100000..[/CODE]I get the same behaviour when I try with my TBS6903X- V1.2 card.Is there some settings I can change to improve this ? Is there some logs you need ?</blockquote>

[QUOTE="Bobben_no, post: 1157410, member: 339576"] I have now tried a tbs6909 V2 card stid135-blindscan. It blindscans incredibily fast by using all eight adapters. But I notice that random transponders is not identified by the blindscan. I got the same problem when using only one adapter on TBS6909X V2 or using tbs6903x v1.2. I can see the same behaviour on many different satellite positions like 28E,13E,19E etc. but for those positions I have a diseqc switch that is causing distorted spectrum which I assume can make it harder to identify the spectrum peaks. For the 1-west satellite position I use no diseqc and the spectrum looks quite clean. See attached jpg from 1-WEST which shows spectrum and two random transponders not identified during that spesific scan. Btw. the blindscan is insane fast and completes in only 2 minutes for both pol and full L-band! I can tune to those transponders missed by blindscan by using tsduck and SNR is around 12dB which should be more than enough. It also works in tsduck even if I deliberately set incorrect parameters for symbolrate,FEC,delivery system. I assume that means that the blindscan driver is able to identify those transponders without any problem. [CODE]stid135-blindscan -c blindscan --fft-size 256 --search-range 10000 -U0 -C0 -a 4 5 6 7 8 9 10 11 --rf-in=0 -pBOTH -s 10650000 -e 12750000 --spectral-resolution 100[/CODE] Extract from the horisontal peaks_rf0_H.txt file shows those two transponders is not detected as peaks: [CODE] . . 11784.600000 27700000 11822.800000 29100000 11861.300000 27700000 11899.100000 26900000 11937.800000 27900000 12014.600000 29500000 12091.400000 26700000 12129.000000 27100000 . . [/CODE] I get the same behaviour when I try with my TBS6903X- V1.2 card. Is there some settings I can change to improve this ? Is there some logs you need ? [/QUOTE]

Verification