Blindscan on linux with tbs cards

I would like to believe I have correctly updated the drivers for neumo-drivers(!?!) on Ubuntu 24.04 and Kernel 6.17.3.
On this occasion, I am also providing the bug_report.sh requested by our colleague to check whether their installation is correct.

On this occasion, I also updated neumodvb. That is the first time two versions are mentioned simultaneously during an update of neumoDVB. To what extent versions 2.1 and 2.2 are the ones I tested neumodVB with remains to be seen by @deeptho himself.

Satesco,
?? There are no versions 2.1 and 2.2
Your driver installation seems to be successful (latest version)

I still have reservations about this new version, which I tested with four DVB cards (6909se, 6983, 6902se, 6590), and it corresponds to the one mentioned by @deeptho. I have had so many surprises in this regard over time, thinking that I was updating the announced version, only to find that it was something completely different.

I chose to test 6909x with neumoDVB on a satellite at 96.5E, with low elevation and an uneven signal. The result is as expected, i.e., good.
I tested the other TBS cards on a satellite with a DTH signal.

The best result of this test, as is natural, is with the 6909x card, because, as is already known, @deeptho invested time and considerable creative intelligence to make it perform well and highlight the extraordinary capabilities of the STiD135 chip. That leads me to believe that the new driver version for Neumo-drivers is also the result of this endeavour.

Regarding the tbs6983 card, I had a little hope that blindscan would improve and yield better results. Unfortunately, of the cards tested, the 6983 disappoints me. I would say "again," but I know this is an unfair judgment on my part because @deeptho does not have this card, and that it is from an older generation. The strange thing is that, although he is right, cards with the STV091X chip are also the most widely used by both amateurs and professionals alike.
The drivers have not changed, so there will be no change in performance (not better/not worse). What you describe about 6983 is not
an issue with the stv chip but with the tuner chip.

And the stv091x cards are nice, but impossible to buy.


With the 6902se (6904se) card, you can achieve good results with the latest version of neumoDVB, even though some demodulator functions are not supported. Blindscan is fantastic, just like on Windows.
These cards are supported to what is possible: No constellation display.

Maybe another search algorithm would give better results on blindscan for the 6590 card on Linux. I'm not sure about that.

I added a test neumoDVB with USB 5927. Excellent.

I presented the tests of four tbs cards to get feedback from @deeptho on the installation of neumo-drivers and neumoDVB, whether the new neumo drivers are installed correctly, and whether the tests with neumodVB are the latest versions.
There are probably other users in my situation who are asking the same questions.
Installation is correct. :->
 
LLew
So my bug_report.sh has already paid off: it shows that you have not actually upgraded the drivers, or not recompiled them or not re-installed them.

The demod is cxd28203. saa716x is also needed.
Another install of neumo-drivers, and bug_report shows my 6220 (line 1584 saa716x), and cxd28203 (line2368)

Unfortunately still no TBS6220 in neumodvb's frontends, but adapters all present in /dev/dvb. So no T/T2 mux scanning possible.

Maybe my new distro CachyOS is showing ageism towards my ancient TBS6220? (feeble joke)
 

Attachments

Another install of neumo-drivers, and bug_report shows my 6220 (line 1584 saa716x), and cxd28203 (line2368)

Unfortunately still no TBS6220 in neumodvb's frontends, but adapters all present in /dev/dvb. So no T/T2 mux scanning possible.

Maybe my new distro CachyOS is showing ageism towards my ancient TBS6220? (feeble joke)
This is a weird problem. I have added some extra code to the drivers to find the problem and perhasp fix it. So you will need to
completely update the drivers (git pull), recompile, reinstall, reboot and run bug_report.sh
 
This is a weird problem. I have added some extra code to the drivers to find the problem and perhasp fix it. So you will need to
completely update the drivers (git pull), recompile, reinstall, reboot and run bug_report.sh
That's done the trick deeptho. Thanks.

Finds my Sony and August T/T2 USB sticks too (same demod). Spoiled for choice, but don't need to trail cable around the PC for them with a working 6220.

Shame not to have a live TV screen (blank window), just ts streaming. Doesn't even toggle overlay for signal info. Perhaps one day ArchLinux will include a software repository update for the distros, or whatever is required to allow live TV.

Found TBS6220+.webpDVB-T Muxes.webpCachyos screens.webp
 

Attachments

That's done the trick deeptho. Thanks.

Finds my Sony and August T/T2 USB sticks too (same demod). Spoiled for choice, but don't need to trail cable around the PC for them with a working 6220.

Shame not to have a live TV screen (blank window), just ts streaming. Doesn't even toggle overlay for signal info. Perhaps one day ArchLinux will include a software repository update for the distros, or whatever is required to allow live TV.

View attachment 167192View attachment 167191View attachment 167190
Did you install Mate-desktop? Maybe that fixes it. It will also goive you back menus and in general a better user interface.
 
I tried to update Blindscan. I used to get pull to fetch the updated files, but when I ran "make," I got errors 1 and 2.
It is marked in red in the screenshot.
What do you think needs to be corrected to eliminate the error?

And another question: are your drivers (neumo-drivers) compatible with the Cesbo Astra or only TBS drivers?
I can't find any card installed on Cesbo for settings.
Thanks :)
 

Attachments

  • error 1_2026-02-07_10-35.webp
    error 1_2026-02-07_10-35.webp
    67.5 KB · Views: 26
Did you install Mate-desktop? Maybe that fixes it. It will also goive you back menus and in general a better user interface.

I have installed Mate previously in other ArchLinux OS's, and live screen was always blank in each of them. Installing it in Cashyos makes no difference. It's a Black Hole where nothing enters or exits.
 
I tried to update Blindscan. I used to get pull to fetch the updated files, but when I ran "make," I got errors 1 and 2.
It is marked in red in the screenshot.
What do you think needs to be corrected to eliminate the error?
Satesco,
that is difficult to say. You basically want me to guess. Maybe it is something ubuntu specific or maybe you exectuted one of the steps wrongly.
I would advise starting from scratch: remove blindscan (NOT THE DRIVERS) and fiollow the instructions.


And another question: are your drivers (neumo-drivers) compatible with the Cesbo Astra or only TBS drivers?
I can't find any card installed on Cesbo for settings.
Thanks :)
I have never succeeded in running Cesbo Astra. The drivers should work with any software.
 
Satesco,
that is difficult to say. You basically want me to guess. Maybe it is something ubuntu specific or maybe you exectuted one of the steps wrongly.
I would advise starting from scratch: remove blindscan (NOT THE DRIVERS) and fiollow the instructions.

...
I tried installing (new) Blindscan, as you recommended.

Same result as the first time, then via "git pull," with the same error, underlined (see file)

Here are the commands I ran to install Blindscan fresh.
If I did the steps/commands wrong, please let me know. Thanks :)

cd blindscan
mkdir build
cd build
cmake ..
make
 

Attachments

Satesco,

this must be something ubuntu specific (or specific to your pc). I have created a small change now. Maybe it will help.
 
After a lot of frustration with non-working tools, and poor/incomplete information on this forum, I managed to make some progress on dvb-nip support. The details are explained in the documentation: blindscan/doc/dvb-nip.md at master · deeptho/blindscan,
but here are some screensshots for
12227V @13.0E

mpv-shot0003.webp


tamazight.webpmpv-shot0002.webp
 

Attachments

  • mpv-shot0001.webp
    mpv-shot0001.webp
    11.3 KB · Views: 8
Satesco,

this must be something ubuntu specific (or specific to your pc). I have created a small change now. Maybe it will help.
The modification to Blindscan had a good effect. :Y

A first test with stid135-blindscan shows that blindscan works.
At least that's how it seems.

I didn't run any more tests to determine whether "One or more frontends cannot use rf_in=0" is really an error (last paragraph).
What do you say?

at@ubu:~$ stid135-blindscan -cblindscan -a 0 1 2 3 4 5 6 7 --rf-in=0
log4cxx: Could not read configuration file [/usr/bin/../../config/stid135-blindscan.xml]. IO Exception : status code = 2(No such file or directory)
2026-02-08 21:43:40,124 /home/sat/blindscan/src/logger.cc:80
STARTING
2026-02-08 21:43:40,124 /home/sat/blindscan/src/logger.cc:80
STARTING

adapter_no=0 1 2 3 4 5 6 7
rf_in=0
frontend=0
start-freq=-1
end-freq=-1
step-freq=6000
pol=3
pls_codes[5]={ 4202496, 2048, 98139136, 134216704, 80015360, }
diseqc=UC: U=-1 C=-1
2026-02-08 21:43:40,125 /home/sat/blindscan/src/common.cc:53
Neumo dvbapi detected; version=2.0
2026-02-08 21:43:40,125 /home/sat/blindscan/src/common.cc:53
Neumo dvbapi detected; version=2.0
2026-02-08 21:43:40,125 /home/sat/blindscan/src/common.cc:63
DRIVERS: GIT-REV=921c9bd GIT-TAG= GIT-BRANCH=deepthought
2026-02-08 21:43:40,125 /home/sat/blindscan/src/common.cc:63
DRIVERS: GIT-REV=921c9bd GIT-TAG= GIT-BRANCH=deepthought
2026-02-08 21:43:40,125 /home/sat/blindscan/src/common.cc:75
Blindscan drivers found
2026-02-08 21:43:40,125 /home/sat/blindscan/src/common.cc:75
Blindscan drivers found
=======================================
Blindscan using the following adapters:
A0 TBS 6902SE RF_IN=0 FFT=Yes SWEEP=Yes
A1 RF_IN=0 FFT=No SWEEP=Yes
A2 RF_IN=0 FFT=No SWEEP=Yes
Error: One or more frontends cannot use rf_in=0
 
To take full advantage of Neumo-tune, I should configure the neumo-tune.xml file. Unfortunately, something is missing in the configuration: every time I try to lock the signal on a mux, it shows as not locked(0).

I assume this is due to the message in lg4XX that says: "Could not read configuration file [/usr/bin/../../config/neumo-tune.xml"
In the previous message, I was told that "IO Exception: status code = 2(No such file or directory)"
So I invariably get the same message when I scan with Neumo-tune: "Could not read..."

How can I correct this issue for Neumo-tune?

Otherwise, sti135-blindscan works fine.
I haven't tried Neumo-DMX yet, because I'm waiting to fix my problem with Neumo-Tune.

Any advice is welcome. Thanks. :)
 

Attachments

  • Tests with neumo-tune.zip
    Tests with neumo-tune.zip
    140.1 KB · Views: 0
  • neumo-tune-config file_nolock_2026-02-09_11-38.webp
    neumo-tune-config file_nolock_2026-02-09_11-38.webp
    31 KB · Views: 16
To take full advantage of Neumo-tune, I should configure the neumo-tune.xml file. Unfortunately, something is missing in the configuration: every time I try to lock the signal on a mux, it shows as not locked(0).
No you shouldn't.

I assume this is due to the message in lg4XX that says: "Could not read configuration file [/usr/bin/../../config/neumo-tune.xml"

That just means that you disregarded the advice "I advise against installing this software. Instead just run it from where it has been compiled, e.g. ~/blindscan/build/src/neumo-tune The reason for this advice is that sometimes users have an old version installed and then run a newversion from within the compile tree, leading to endless confusion when reporting bugs.

If you wish to ignore this advice, then remove all installed versions and start with a cleanbuild, before reporting bugs.
"

In the previous message, I was told that "IO Exception: status code = 2(No such file or directory)"
So I invariably get the same message when I scan with Neumo-tune: "Could not read..."

How can I correct this issue for Neumo-tune?

Otherwise, sti135-blindscan works fine.
Not according to "Error: One or more frontends cannot use rf_in=0"


I haven't tried Neumo-DMX yet, because I'm waiting to fix my problem with Neumo-Tune.

Any advice is welcome. Thanks. :)
Best to remove the version that you installed and please check that you are using the correct adapters.
 
...

Best to remove the version that you installed and please check that you are using the correct adapters.
After a new Blindscan installation, test with neumo-tune at 1.0W for NRK DAB+ with the 6909x card.

Compared to the old signal command: neumo-tune -ctune -A blind -a 8 -r 0 -dU -U2 -s 171 -f 10716000 -pV -S 5400,
I changed it slightly to this:
neumo-tune -a 8 --rf-in=2 --frequency=10717000 --symbol-rate=5400 --pol=V.
I removed the switch from the command because I no longer use it.
The Eti-tools command remained the same as before:dvbsnoop -adapter 8 -s ts -tsraw -b | ./bbframe-tools/pts2bbf | bbfedi2eti -dst-ip 239.199.2.1 -dst-port 1234 | dablin_gtk.
This DAB works well with both commands without any problems.

There is probably something missing if the stid135-blindscan command only reads 3 adapters and no 6909x(?!), although I ran these tests with this card.
sat@ubu:~$ ~/blindscan/build/src/stid135-blindscan -cblindscan -a 0 1 2 3 4 5 6 7 --rf-in=0
adapter_no=0 1 2 3 4 5 6 7
rf_in=0
frontend=0
start-freq=-1
end-freq=-1
step-freq=6000
pol=3
pls_codes[5]={ 4202496, 2048, 98139136, 134216704, 80015360, }
diseqc=UC: U=-1 C=-1
=======================================
Blindscan using the following adapters:
A0 TBS 6902SE RF_IN=0 FFT=Yes SWEEP=Yes
A1 RF_IN=0 FFT=No SWEEP=Yes
A2 RF_IN=0 FFT=No SWEEP=Yes
Error: One or more frontends cannot use rf_in=0

I tried the DVB-NIP stream on 12227 V at 13.0E, now that it has support, but although neumo-tune locked my signal, something is missing(plugin?) in the neumo-dmx command, as I get an error related to NIP. (I installed tsduck)
sat@ubu:~/blindscan/build/src$ ./neumo-tune -a 8 --rf-in=2 -U 8 --frequency=12227000 --symbol-rate=27500 --pol=V
adapter=8
rf_in=2
frontend=0
freq=12227000
pol=2
pls_codes[5]={ 4202496, 2048, 98139136, 134216704, 80015360, }
diseqc=UC: U=8 C=-1
Name of card: TurboSight TBS 6909x
Name of adapter: A8 TBS 6909X
Name of frontend: TurboSight TBS 6909x
Tuning
==========================
DEBUG main - Tuning to DVBS1/2 12227V
DEBUG main - select rf_in=2
DEBUG main - Succesfully set MASTER rf_input=2
BLIND TUNE search-range=10000
FE_GET_EVENT: stat=543, timedout=0 locked=1
FE_READ_STATUS: stat=543, signal=1 carrier=1 viterbi=1 sync=1 timedout=0 locked=1
^C

sat@ubu:~/blindscan/build/src$ ./neumo-dmx -a 8 | tsresync | tsp -P nip --service=17702 --log-fdt -O drop
* Error: nip.so: cannot open shared object file: No such file or directory
* Error: processor plugin nip not found
 

Attachments

  • NRL DAB+_neumo-tune+dvbnoop=ok_2026-02-11_11-53.webp
    NRL DAB+_neumo-tune+dvbnoop=ok_2026-02-11_11-53.webp
    167.5 KB · Views: 26
Last edited:
As it says in the documentation: "This files in this carroussel can be received using neumo-dmx and a recent version of tsuck". You did not install a recent version, it seems.
 
As it says in the documentation: "This files in this carroussel can be received using neumo-dmx and a recent version of tsuck". You did not install a recent version, it seems.
Great, @deeptho, the NIP-DVB-IBC stream is working as documentation says. :-clap

Indeed, after updating TSDuck, the NIP-IBS stream started working. We captured only three video files, and I played them simultaneously.
Thanks :Y
 

Attachments

  • 12227 V,27500_DVB_NIP_IBC_2026-02-13_00-39.webp
    12227 V,27500_DVB_NIP_IBC_2026-02-13_00-39.webp
    238 KB · Views: 27
Test with @deeptho's driver for Cesbo Astra using the 6909x card.
 

Attachments

  • Cesbo_Astra_6909x_19.2E_2026-02-13_12-14.webp
    Cesbo_Astra_6909x_19.2E_2026-02-13_12-14.webp
    118.2 KB · Views: 29
After succeeding with 12227 V and updating blindscan, I tried to run DVB-NIP (Inverto) at 11353 V, 27500.5/6 with the same command for neumo-dmx, but with pid 2060 (which this mux has), but (with service=2060), the files are not downloaded. Instead, using PID, I obtained some information (see photo) showing that it appears to show metadata.

Perhaps a different approach to the console commands could yield better results. What do you think?

I tested this mux with VMA TS Analyser and, as you can see, the streams have started and are running.

Maybe the same approach should be taken for DVB-NIP-VV on 12380 V, 27500, 3/4, 8PSK at 13.0E(?)

Perhaps the same approach should be taken for DVB-NIP-VV on 12380 V, 27500, 3/4, 8PSK at 13.0E(?).
That is, only if you are still interested in such streams after the success with NIP(Q.E.D) at 12227 V.
 

Attachments

  • 11353 V-Rai_2026-02-13_18-47-14.webp
    11353 V-Rai_2026-02-13_18-47-14.webp
    180.8 KB · Views: 16
  • 11353 V-Pid-2060_2026-02-13_18-17-54.webp
    11353 V-Pid-2060_2026-02-13_18-17-54.webp
    99.3 KB · Views: 18
  • 13.0E_11535 V,27500_Inverto_pid-2026_2026-02-15_12-40.webp
    13.0E_11535 V,27500_Inverto_pid-2026_2026-02-15_12-40.webp
    176.5 KB · Views: 18
  • 11353 V-locked.webp
    11353 V-locked.webp
    44.7 KB · Views: 13
Last edited:
This works for me on that mux

Code:
neumo-dmx -a 8 | tsresync | tsp -P nip -p 300 --log-fdt --save-dvb-gw /tmp/xxx -O drop

Also: From our screen shot, you still seem to run some half installed version. So expect some other problems....

This stream also has a pdf document.

1.webp


mpv-shot0007.webpmpv-shot0006.webpmpv-shot0005.webp


mpv-shot0004.webp
 
Back
Top