Tbs tuner and crazyscan - probably not a pc card issue

deeptho said:
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
Click to expand...
si2183 chip and av201x chip info was found in the logfile.

Sorted out my correct commands, built neumo-blindscan for TBS6522 verticals on 27.5W. Drew a chart.

Horror of horrors, it's plagued with 50 MHz spikes :eek:

blindscan-.png

I'll do a Horizontal in due course to see if it displays similar effects.
 
LLew, you seem to ignore my requests for the precise model number, which is the main useful piece of info.

Can you also check if the problem occurs if you replace --spectrum-method fft with
--spectrum-method sweep
 
deeptho said:
LLew, you seem to ignore my requests for the precise model number, which is the main useful piece of info.

Can you also check if the problem occurs if you replace --spectrum-method fft with
--spectrum-method sweep
Click to expand...
Can you check the log please deeptho? I'm not too sure what I'm looking for. Must be the hot weather slowing my neurons.
 

Attachments

Llew said:
Can you check the log please deeptho? I'm not too sure what I'm looking for. Must be the hot weather slowing my neurons.
Click to expand...
I found what I needed, but the info is just the same as for tbs6504. The card could be different in some other way.

The "sweep" version would be of interest. I also needthe /tmp/spectrum.....dat files for each of the two scans (fft and sweep)
 
deeptho said:
I found what I needed, but the info is just the same as for tbs6504. The card could be different in some other way.

The "sweep" version would be of interest. I also needthe /tmp/spectrum.....dat files for each of the two scans (fft and sweep)
Click to expand...
Sweep version for 14W deeptho. Same problem as with fft.

14W H Sweep.png

Spectrum data file for both versions, fft and sweep. Perhaps your card chips see them differently?
 

Attachments

It seems sweep was not implemented. So this test brings no useful information.

Can you check the output of
Code: 
md5sum /lib/firmware/dvb-demod-si2183-b60-01.f

Mine reads:
3e6b89b319a733c3b672a61cdded0e67 /lib/firmware/dvb-demod-si2183-b60-01.fw
 
deeptho said:
It seems sweep was not implemented. So this test brings no useful information.

Can you check the output of
Code: 
md5sum /lib/firmware/dvb-demod-si2183-b60-01.f

Mine reads:
3e6b89b319a733c3b672a61cdded0e67 /lib/firmware/dvb-demod-si2183-b60-01.fw
Click to expand...
It's the same deeptho.

I used this for sweep -

./neumo-blindscan -c spectrum -U 0 -a 0 --frontend 1 -p 3 --spectrum-method sweep --spectral-resolution 2000

Perhaps I should have had a different resolution frequency for the TBS6522?
 
Llew,

there must be something different on that card. After all it is not a TBS6504.
In doubt resolution matters (and I think it is hard coded, because there is no real way toi change it
and documentation is lacking).

It is potentially fixablle by discarding part of the spectrum, which will slow down the scan. Spending time on that
only makes sense if this problem is not just due to a minor fault on your specific card, but rather a result of the
card's design.

So it would be good to know if other users of this card have similar results.
 
deeptho said:
Llew,

there must be something different on that card. After all it is not a TBS6504.
In doubt resolution matters (and I think it is hard coded, because there is no real way toi change it
and documentation is lacking).

It is potentially fixablle by discarding part of the spectrum, which will slow down the scan. Spending time on that
only makes sense if this problem is not just due to a minor fault on your specific card, but rather a result of the
card's design.

So it would be good to know if other users of this card have similar results.
Click to expand...
The comparison tests which I did earlier in the thread with my cards showed the TBS6522 performed well against the TBS6903X and TBS5927, finding as many locked channels as with the 6903X, so all is not lost. It just makes the displayed spectrum untidy (to say the least).

I'll do some more testing with the card in neumoDVB (different satellites, frequency bands).
 
Crazyscan v. 1.0.2.181-committed , from 21.07.2023
 
New build StreamReaderEx BDA Tuner v.1.2.5.158 from 27.08.2023,
 
StreamReaderEx BDA
Released today,12.01,2024, but it is not specified which version it is and what improvements/bug fixes it brought for TBS cards.

I appreciate every time @CrazyCat gives us the possibility to use his app, but now even more so when we find out that the city he lives in is under Russian bombardment.
May the Lord above watch over you :-respekt
 
1.2.5.165
Initial support for GX1133-based TBS devices like 5930 lite (5931) and 6902 v3 (not tested)
Features similar to TAS210x-based devices, but true support for MIS/PLS support.

Some important features still not implemented (like ISI list detection in BLScan/BLScan2).
PLS not tested on real transponder like 5W (RAI, Mediaset and etc)
 
StreamReaderExEx-BDA.rar-v.1.2.5.169, from 23.01.2024.
 
CrazyScan2, new build 1.0.2.187 in 15.02.2024
-added new cable standards J83B (some like cable ATSC) and ISDB-C
 
Back
Top