Tbs tuner and crazyscan - probably not a pc card issue

New StreamReaderEx BDA Tuner v.1.2.5.157 from 7.06.2023
 
TBS 6903X, 6909X support only FFTScan - so selection disabled and FFTScan always selected.


Could anyone please explain what the benefits are of FFTScan compared to RF Scan?
Looking at the FFTScan result earlier in this topic, the FFTScan yields spectra that look similar in style to those from the linux blind scan tool neumodvb?
 
Could anyone please explain what the benefits are of FFTScan compared to RF Scan?
Looking at the FFTScan result earlier in this topic, the FFTScan yields spectra that look similar in style to those from the linux blind scan tool neumodvb?
Yes, because both are fftscan. Linux version was first. Windows version exists for a long time as well, but was also worse in quality for a long time (perhaps fixed now)
 
Yes, because both are fftscan. Linux version was first. Windows version exists for a long time as well, but was also worse in quality for a long time (perhaps fixed now)


Any benefits with FFTScan compared to RF scan?
 
Water. TBS5927.
52 scanned, 21 locked.

TBS5927.png

Beer. TBS6903X.
106 scanned, 29 locked.

TBS6903X.png

Beer (real ale?) TBS6522.
75 scanned, 29 locked.

TBS6522.png

Some anomalies in the TBS 6903X and TBS6522 spectra using the fft engines. Some multiplicities of various frequencies.

Also, I still get 50MHz spikes in the centre of a scanned spectrum with the TBS6522. No idea what causes that.
 
Water. TBS5927.
52 scanned, 21 locked.

View attachment 150301

Beer. TBS6903X.
106 scanned, 29 locked.

View attachment 150302

Beer (real ale?) TBS6522.
75 scanned, 29 locked.

View attachment 150303

Some anomalies in the TBS 6903X and TBS6522 spectra using the fft engines. Some multiplicities of various frequencies.

Also, I still get 50MHz spikes in the centre of a scanned spectrum with the TBS6522. No idea what causes that.
To add to the discussion and to be absolutely sure, I performed an experiment:
1. open garage door to have clear view of the car
2. drink a beer (regular pils)
3. check if the car was driving: no.
4. check for cirosis: no.
Of course, it is dangerous to draw conclusions from only one experiment, so I tried a second stronger beer
called "La Chouffe". Same results.

I will try the water tomorrow.
 
Why do you consider those benefits?


I made a polite enquiry in post 82 of this topic asking about the benefits of FFTScan vs RF Scan.
It was you replied in the sarcastic tone comparing drinking beer to water, which did not address my question.

Now that I replied back in the same sarcastic tone it seems you are unable to take it and wish to proceed further down the route of ridicule.
If you cant take it back, dont dish it out in the first place.
 
Last edited:
Some anomalies in the TBS 6903X and TBS6522 spectra using the fft engines. Some multiplicities of various frequencies.
Here is my result with tbs6909x (should be similar to 69093x)
1.png

Also, I still get 50MHz spikes in the centre of a scanned spectrum with the TBS6522. No idea what causes that.
Strange indeed. Do these peaks stay at the same frequency if you change the range of the spectrum scan by 20MHz?
If their frequency changes also by 20Mhz then, then it is a driver problem. Otherwise it is probably some interference problem or problem with the card.
 
Here is my result with tbs6909x (should be similar to 69093x)
View attachment 150327


Strange indeed. Do these peaks stay at the same frequency if you change the range of the spectrum scan by 20MHz?
If their frequency changes also by 20Mhz then, then it is a driver problem. Otherwise it is probably some interference problem or problem with the card.
I did a spectrum scan shifted up 25MHz, and consequently the spikes also increase by 25Mhz. If it's a driver problem, can you explain that deeptho? I think I'm already updated with the latest drivers.

14W TBS6522 10925_to_11725.png
 
I did a spectrum scan shifted up 25MHz, and consequently the spikes also increase by 25Mhz. If it's a driver problem, can you explain that deeptho? I think I'm already updated with the latest drivers.

View attachment 150334

Still with TBS6522, a satellite scan with less obstructing transponders (27.5W) shows more clearly the spikes or pulses along the spectrum -

27.5W TBS6522.png
 
New StreamReaderEx BDA Tuner v.1.2.5.158 from 10.06.2023
New SR version with FFTScan, the transponder(s) does not match the spectra for 6902se and 6903x cards.
Also, Blindscan2 is greyed out for these two cards.
 

Attachments

  • tbs6902se_11.0W_3600-4200 LR_2023-06-11_22-18-27.png
    tbs6902se_11.0W_3600-4200 LR_2023-06-11_22-18-27.png
    114.2 KB · Views: 17
  • tbs6902se_11.0W_RFScan_2023-06-11_22-20-33.png
    tbs6902se_11.0W_RFScan_2023-06-11_22-20-33.png
    103.3 KB · Views: 14
  • 11.0W_3600-4200 LR_2023-06-11_22-11-20.png
    11.0W_3600-4200 LR_2023-06-11_22-11-20.png
    129.6 KB · Views: 19
Last edited:
Still with TBS6522, a satellite scan with less obstructing transponders (27.5W) shows more clearly the spikes or pulses along the spectrum -

View attachment 150344

The code was made for tbs6504, see for example:
Blindscan on linux with tbs cards

so there may be a difference in the version of the chips or in the firmware
version. Perhaps you can find out in the kernel logs which version it is. Look for a line containing
found a Silicon Labs Si21

It is also possible that something changed in neumodvb over time.
Can you grab a spectrum using the command line blindscan tools?
A command similar to :
Code:
~/blindscan/build/src/neumo-blindscan 
./neumo-blindscan -c spectrum -U 3 -p 3 --spectrum-method fft --spectral-resolution 100 --lnb-type C -a 1
 
Perhaps you can find out in the kernel logs which version it is. Look for a line containing
found a Silicon Labs Si21

log finds Silicon Labs si2183 and si2157, successfully attached.

Tried to do a scan with the TBS6522, but fails with voltage problem -

TBS6522 spectrum build problem.png

Might be as you suggest, a firmware compatibility issue?
 
first frontend - terrestrial/cable, second - satellite
 
log finds Silicon Labs si2183 and si2157, successfully attached.

Obviously, but what is important is the model number. So the other information appearing in the log file lines related to si2183 and av201x
Tried to do a scan with the TBS6522, but fails with voltage problem -

View attachment 150356

Might be as you suggest, a firmware compatibility issue?
No, you need tospecify the frontend with --frontend
 
No, you need tospecify the frontend with --frontend
I'm still having problems setting the commands correctly. I seem to be going backwards. It was so much easier when I had only the one tuner to deal with :-doh

-U is 0 (first port in my diseqc switch)
I try -a as 0 or 1, it makes no difference.
frontend 1 (dvb S/S2)
p 3 (H and V)

TBS6522 spectrum fails.png
 
I'm still having problems setting the commands correctly. I seem to be going backwards. It was so much easier when I had only the one tuner to deal with :-doh

-U is 0 (first port in my diseqc switch)
I try -a as 0 or 1, it makes no difference.
frontend 1 (dvb S/S2)
p 3 (H and V)

View attachment 150358
You have two dashes missing in the command.

In the mean time I doubkle checked the spectrum of tbs6504, which uses the same code. There are no spurious peaks there.

What you need to is report the lines in the kernel log which show the models of teh si2183 chip and av201x chip
 
Back
Top