TBS Universal & Signal Analyzer

**PantaSat** · May 30, 2026 at 10:52 PM

[RELEASE] TBS Universal Analyzer v4.0 & Integrated Signal Analyzer v1.6

I developed this software with the goal of fully exploiting the Blind Scan capabilities of TBS tuner cards, both new and legacy generations. The program has been thoroughly tested and optimized directly on a TBS 6983, but its architecture is ready to operate with all models supported by the StreamReader API.

🔍 WHAT THE SOFTWARE DOES (BLIND SCAN MODES)

The core strength of this tool is its flexibility in handling different types of Blind Scan depending on your hardware setup and current needs:

Blind Scan on Spectrum Peaks (Fast): You run the Spectrum Scan first. The software automatically detects the signal peaks (the "humps") and unlocks the Blind Scan button. At that point, the core launches a targeted BLScanEx routine (with a fixed 15 MHz range) exclusively on the detected peak frequencies. You get a lock and a populated transponder table in just a few seconds.
Linear Blind Scan without Spectrum (BLScanEx): If you prefer not to run a preliminary spectrum scan, simply check the BLSCAN NO SPECTRUM box. The system will scan the entire band step-by-step. I have implemented a Smart Skip algorithm: as soon as the card finds and locks a transponder, the software calculates its bandwidth based on the Symbol Rate and automatically skips past it. This prevents wasting time scanning the same carrier repeatedly.
Linear BLScan2 Scan (Full): By enabling the FORCE BLScan2 checkbox, the software executes the native segmented search (Low Band and High Band), tightening lock times across the entire band.

⚙️ HARDWARE COMPATIBILITY & TESTING

TBS 6983 and Classic Cards: This is the exact hardware used for all development testing, where the optimization routines (scan speed and skip handling) deliver their maximum performance.
TBS Series-X (6903x, 6909x, etc.): The software is fully prepared to work with these next-gen cards (utilizing FFTScan for ultra-fast spectrums). However, since I do not physically own any of these cards to run direct hardware tests, the results with Series-X will likely be the same as what you would get with other software currently in circulation. Without having the actual hardware on hand, this was the best I could do.

📺 SIGNAL ANALYZER & LIVE TELEMETRY

Double-clicking any transponder found in the table opens the built-in Signal Analyzer module. It operates as a single process sharing RAM with the main GUI, ensuring no double-tuning conflicts or interface freezes:

Ghost Lock Elimination: The demodulator is fully cleared on every frequency change to prevent the analyzer from staying anchored to the previous frequency.
Real PLS Management: Full support for selecting PLS codes and modes (Auto, Root, Gold, Combo).
Carrier Anchoring: The software forces a hardware lock (flag 0xFF) to stabilize the signal even before launching any external players.
Streaming & Process Watcher: Instant streaming output to VLC, TSReader, RAW UDP, or VMA Analyzer. The software checks every 3 seconds if the external player has been closed, immediately freeing up the tuner card without locking up the interface.

Below are a few videos showing the software in action:
Video 1
Video 2
Video 3
Video 4

🔗[DOWNLOAD] TBS Universal Analyzer v4.0 here

Developed by PantaSat 2026

femi · May 31, 2026 at 9:02 AM

1. Das Programm läuft nur (unverändert) in einem Unterverzeichnis von „C:\Feed_Scanner_Suite“. Andernfalls erhalten Sie beim Ausführen der .bat-Datei eine Fehlermeldung.

2. Das schwarze Fenster ist optisch ansprechender, das weiße jedoch deutlich besser sichtbar.

3. Wenn Sie den Tuner auswählen (in meinem Beispiel 6), springt das Programm zurück zum voreingestellten Tuner(2). Man muss die Tuner unbedingt zuvor in der Konfigurationsdatei (cfg) festlegen!

4. Wenn der Tuner nun korrekt konfiguriert und aktiv ist, sollte ein Scan möglich sein. Es werden jedoch nur für einen Bruchteil einer Sekunde vertikale Linien angezeigt und das war es.

1. The program will only run without modification in a subdirectory of "C:\Feed_Scanner_Suite"; otherwise, an error message will be received when executing the .bat file.

2. The black window is visually more appealing, but the white one is much more visible.

3. If you select the tuner (for my example 6) it jump back to default tuner(2). You must specify first the tuners in cfg!

4. If the tuner is now correctly configured and active, it should be possible to perform a scan. But only vertical lines appear for a fraction of a second, and that's it.

**stephan94** · May 31, 2026 at 9:33 AM

Guten Morgen ,

Bei mir funktioniert diese Programm einwandfrei , alles ohne Problem

**satesco** · May 31, 2026 at 11:06 AM

PantaSat explained above the purpose of TBS Universal Analyses. These are TBS cards from a Chinese manufacturer that are fully or partially supported by the CrazyCat library.

But because PantaSat wanted to take advantage of the blind-scan capabilities of TBS cards, he developed this app specifically for that purpose, making it a standalone application with features and functions implemented similarly to those of Frequency Tester.

I tested several of these TBS cards that I already have installed, with different models and capabilities. The first one I checked was a Stid135, 6909x card, which could not be scanned with the Frequency Tester Suite version, even though it is part of that suite.

I (blind) scanned part of the band at 19.2E with the 6909x using Universal Analyses, without enabling the Force BLScan2 function, because the app detected it as an FFT card.

The scanning time with this type of card is the same and performs largely as with Crazyscan, though it depends on the steps and signal strength. In addition, it has a feature I haven’t found in any other DVB app: the ability to force the signal to lock it with BLScan2, which I used for the tested cards.

The idea of a Signal Analysis utility in the Universal app is a good and necessary one. I say this because instantly checking a mux directly from the transponder list is a must for any user.
Maybe I don’t know how to use it properly yet, but I’m a bit confused by the fact that when the Signal Analysis window closes, the TBS Universal Analyses app closes automatically as well.

The X (close) button should belong solely to the utility, be independent, so we can analyse the signal or its parameters whenever we want, without affecting Universal Analyses.
Signal Analysis can indeed be launched separately from Universal to analyse a single mux.

I have also tried TBS Universal Analyses with other TBS cards installed in the computer. I haven’t had any problems with this app.

But of course, it still needs to be tested under other satellite reception conditions and in more challenging positions than Astra 19.2E, or another Central European satellite with its strong signal.

And there’s one more new feature: this time, the version he is offering is in English, not Italian, as for Tester

I appreciate that PantaSat managed to find a blind-scanning solution for the STID135 cards, given that he told us he doesn't have such devices, even though it still gives errors on the parameters it’s looking for and locks.

**stephan94** · May 31, 2026 at 1:37 PM

Wirklich ein sehr gutes Programm.

Kleine Anmerkung:

Wenn der Modus auf „Auto“ steht oder nicht gefunden wird, wird 64APSK angezeigt (Satesco hat das bereits erwähnt, allerdings in Bezug auf die Frequenz).

Im Moment finde ich keine Frequenzen mit niedrigem SR.

It really is a very good programme.

Just a quick note:

when the mode is set to ‘Auto’ or cannot be detected ,it displays 64APSK (Satesco has already pointed this out, but in relation to the frequency).

At the moment, I can’t seem to find any frequencies with a low SR.

**satesco** · May 31, 2026 at 4:10 PM

Since it’s now possible to perform a blind scan(auto) with the TBS Universal Analyser app on the 6909x card, I decided to compare (it's a must) the results with Crazyscan at 21.6E, a position where I receive signals from both the eastern and western beams, which have different signal strengths in my area.

**satesco** · May 31, 2026 at 5:40 PM

Perhaps a comparison test with an STV091X-based card (6983/69093, 5927)—which many users have—using the Crazyscan app and TBS Universal Analyser, also at 21.6E, would be more relevant. I used the Blindscan2 feature in both apps for the scan.

As I expected, CrazyCat seems to have outdone himself with his app by implementing BLScan2 (do you remember when he asked us back in 2015, if my memory serves me right?), especially if we want it to find muxes that can’t be locked!

After I enabled BLScan2, I recall the signal strength seemed to have improved slightly, making this STV091X-based card the best-performing one on the market for DVB-S2 reception! No other card or model can match it in this category!!!

In the PantaSat app, I enabled "Force BLscan2," which gave the best results compared to the others—Direct BLscan, Threshold, and BLScan No Spectrum.

However, PantaSat’s FeedScanner Suite app, with the BLScan2 (no lock) feature enabled, achieves the same performance with the tbs6983 card as Carzyscan does

But instead of adjectives or superlatives, it would be better for other users to scan and compare the PantaSat app with Crazycat’s app using these cards.

(I know it’s annoying to bring up an issue that’s already been discussed here, but I’m not sure what impression the washed-out red on a white background—as seen in FeedScanner Suite—will make. It seems to me that for such a high-performing app, it would be worth considering a different colour scheme or spectrum highlighting.)

**PantaSat** · May 31, 2026 at 5:45 PM

Subject: Request for streamreader.log from your 21.6°E test / Updates on Signal Analyzer

Hi satesco,

First of all, thanks for sharing your test results at 21.6°E comparing Crazyscan and the TBS Universal Analyser on the 6909x!

Looking at your results, I noticed some anomalies and longer scanning times than expected. To clearly understand what is happening under the hood, could you post or send me both the streamreader.log from the CrazyScan session and the one generated by my TBS Universal Analyser during that same test at 21.6°E?

I want to compare them line by line. I strongly suspect that my software might be sending incorrect or redundant commands to the DLL... which wouldn't be too surprising, given that I am navigating completely in the dark with these APIs! I want to check if the longer scan times depend on an overload of requests or some loop in the hardware resets. Your logs would be a massive help to get the code back on track.

I also want to let everyone know that I am currently reworking and applying fixes to the Signal Analyzer. I realized that, although it was working, it wasn't working properly yet. I think you have all figured it out by now: when I do things, I like to do them right, if I can.

Best regards, PantaSat

P.S. I must admit, I'm a bit of a failure when it comes to picking the spectrum colors!

femi · May 31, 2026 at 6:04 PM

HWControl=0 war die Ursache, dürfte passiert sein, als ich Voltboost abschaltete.

DM-Sat (16E) konnte ich nur erfassen, indem ich einen kleinen Ausschnitt wählte (12500-12750). Von Radio Gdansk (12589.0) nichts zu sehen.

The cause was HWControl=0, which likely happened when I switched off Voltboost.

I could only detect DM-Sat (16E) by selecting a small section (12500-12750). Radio Gdansk (12589.0) was nowhere to be seen.

**satesco** · May 31, 2026 at 6:18 PM

I hope I didn't miss any files for your analysis.

Universal test.zip

**stephan94** · May 31, 2026 at 7:29 PM

Here are some comparative results for Nilesat (7W)

Zoldar070 · May 31, 2026 at 10:52 PM

Thank you so much for your great work. I can't get this program to run; it just closes when I start it.

I think the directory C:\Feed_Scanner_Suite is correct

**PantaSat** · June 1, 2026 at 12:27 AM

Zoldar070
Hi! To install and run the program correctly, just placing the executable in the directory isn't enough; you need all the other required component files. Please follow these steps:

Read the guide: First of all, carefully read the detailed explanations available in this forum post: 👉 Feedscanner Suite Guide
Download the complete package: Download the ZIP archive containing all the necessary base files from this link: 👉 Download Feed_Scanner_Suite.zip
Installation and Paths: Once the complete package is extracted, please remember that all the apps created by me must be installed inside that folder. For this specific software, it must be located exactly in this directory path on your PC: 📁 C:\Feed_Scanner_Suite\TBS_Universal_Analyzer_4.0
DiSEqC Configuration: If you need to configure your DiSEqC switches, you can find the instructions in that same guide post. Alternatively, feel free to ask here about what you're struggling with, and some fellow users will guide you step by step!

PantaSat

Zoldar070 · June 1, 2026 at 1:16 AM

Quote from PantaSat

Zoldar070
Hi! To install and run the program correctly, just placing the executable in the directory isn't enough; you need all the other required component files. Please follow these steps:
Read the guide: First of all, carefully read the detailed explanations available in this forum post: 👉 Feedscanner Suite Guide
Download the complete package: Download the ZIP archive containing all the necessary base files from this link: 👉 Download Feed_Scanner_Suite.zip
Installation and Paths: Once the complete package is extracted, please remember that all the apps created by me must be installed inside that folder. For this specific software, it must be located exactly in this directory path on your PC: 📁 C:\Feed_Scanner_Suite\TBS_Universal_Analyzer_4.0
DiSEqC Configuration: If you need to configure your DiSEqC switches, you can find the instructions in that same guide post. Alternatively, feel free to ask here about what you're struggling with, and some fellow users will guide you step by step!

PantaSat

Thank you so much for the quick guide and for the excellent work. I'm impressed and eager to try all the options. Best regards.

**PantaSat** · June 1, 2026 at 9:11 AM

Hi Zoldar070,

Since you installed the complete Suite, I'm leaving you this notice because there is an important fix to make if you use a DiSEqC switch or motor in your setup.

The DiSEqC version you initially found inside the suite package was the old one, which worked poorly and created issues with switching commands, causing instability or missed frequency locks.

To fix everything and get the correct timings, you just need to delete the old DiSEqC folder and put the new one from the link below.

https://www.mediafire.com/file/6dtdeq7j6…DiSEqC.zip/file

femi · June 1, 2026 at 9:26 AM

PantaSat

Wenn ich so das Log-Fenster betrachte, verstehe ich ohnehin nicht, warum bei der Suche bei jeder Frequenz Diseqc gesendet wird.
Es reicht doch einmal, nämlich in Verbindung mit der Satellitenauswahl.
Oder interpretiere ich etwas falsch?

Looking at the log window, I don't understand why DiSEqC is being sent for every frequency during the search.
Surely it only needs to be sent once, in conjunction with the satellite selection.
Or am I misinterpreting something?

Guardando la finestra di log, non capisco perché DiSEqC venga inviato per ogni frequenza durante la ricerca.

Sicuramente dovrebbe essere inviato una sola volta, in concomitanza con la selezione del satellite.

O forse sto interpretando male qualcosa?

**PantaSat** · June 1, 2026 at 1:53 PM

femi

Hi! Thank you very much for raising this question and for your valuable feedback. You hit the nail on the head, and let me explain exactly what happened behind the scenes of the software.

I can confirm that the DiSEqC command is absolutely not necessary for every single frequency change or tuning. The correct logic of the protocol requires the DiSEqC command to be sent only at the beginning to set the satellite position (or LNB type), and subsequently, only when a band change (low/high) or a polarization change (V/H) occurs, allowing the LNB to properly switch its reception quadrant.

Unfortunately, since I do not use DiSEqC switches in my personal test setup (I am directly connected via dedicated cables), this redundancy completely slipped past me. Due to an oversight on my part, the DiSEqC invocation ended up inside the tight loop that increments the frequencies within certain scan functions. As a result, the program was firing the command at every single step, MHz by MHz, unnecessarily saturating the hardware bus.

I have already identified the critical points in the code and will remove the invocation from the internal loops, moving it exclusively to quadrant changes. This fix will be included in the next release.

Thank you again for your support in spotting this bug!

Best regards,

PantaSat

satdxer · June 1, 2026 at 2:56 PM

Has anyone tested, if the app works with the TBS 5925 usb card?

Zoldar070 · June 1, 2026 at 6:13 PM

Quote from satdxer

Has anyone tested, if the app works with the TBS 5925 usb card?

It works quite well in all options; here's a screenshot from DXSniper on the Hispasat 30w satellite.

**PantaSat** · June 2, 2026 at 4:15 PM

TBS Universal Analyzer v4.2 – Spectrum Optimization and Compatibility Testing

I am currently working on version 4.2 of the software. The main goal of this update is to optimize spectrum generation and improve peak detection, including the introduction of manual thresholding to filter out noise ripple.

I have completed full compatibility testing with the demodulator functions for the four cards I currently own

Below are the screenshots of the actual signal lock for each card:

TBS 6522

TBS 6983

TBS 5925

TBS 5922