With neumoDVB (and Crazyscan) on satellites

[satesco]

Eutelsat 12 West G @ 12.5° W

I scanned Eutelsat 12 West G with neumoDVB (and Crazyscan) using the 6909x card on the first visit to 12.5W.
Unlike the Windows app, neumoDVB also found and locked two muxes (11191 V,17143 and 11209 V,17142) that were not detected by Crazyscan.

 

[satesco]

I've encountered situations when, with 6909x/(6903x) cards, the frequencies in the upper band were copied from 10950-11200 HV both under Windows and Linux.
This time, it happened the same: at 60.0E, Crazyscan (Windows) and neumoDVB (Linux) found the same frequencies from the lower band to the upper band.
I wonder if this situation is a problem with the IBU lnb used, a bug in the applications/drivers used, or a card construction error.
Why does this error occur?

 

[satesco]

Express-103 @ 96.5° E

Even though these low positions on the arc can only be reached by those with an unobstructed opening and, of course, if they are interested, I think it is worth posting what I am getting at 96.5E in my area.
As usual, neumodVB finds more spikers even with a stid135(6909x) card than with Crazyscan, but the bottom line is that they both lock about the same number of muxes.
This is not an advantage for those looking for TV/radio programs, but they are targets for dxers and all satellites with only Data muxes.

 

[satesco]

Hispasat 30W-5 / Hispasat 30W-6 @ 30° W

Some kind of signal and muxes update to 30.0W with the tbs6909x after a year and a half(#35) since the last scan with neumoDVB and Crazyscan:

 

[satesco]

I don't know how those who installed the neumoDVB and driver for the 6903x/6909x cards work, but I wish that the speed of searching and locking the signal and muxes with neumoDVB would be optimized in such a way that it finds them on auto search.

Often after a scan like this, I am forced to manually scan some transponders that were not found and locked to auto. The cards mentioned at the beginning are known to scan slowly under Windows, so those who want to use this feature have found the neumoDVB app a great tool in many ways. Among others, the fastest scanning for a DVB card, even more so for the two with chipStid135.

I don't know what is the search algorithm set for these cards, but I have the impression that at the search speed, some transponders are missed in the scan. neumoDVB doesn't have a way to set the search steps for the user to choose, like we have Crazyscan under Windows.

On this occasion, I wish @deeptho, the creator of this unique and excellent application, a warm wish for the end of the year: "Happy New Year 2025!", and for the next year to succeed to realize the projects he has in the works, but above all, full health!

 

[satesco]

Yamal 401 @ 90° E

Again at 90.0E after a year and a half since the last visit(#24), now with the 6909x card.
neumoDVB locked the two sub-band muxes faster,10844 H,36000,32/45,S2X/32APSK and 10924 H,36000,4/5,16APSK.

As can be seen from the spectra of both applications, neumoDVB retains everything in its path, even muxes unlock and noise, while Crazyscan retains only the frequencies it locks.

10800-11360 H and 11300-11700 H, with the 6909x card search and locked in 4 min 18s,
10800-11200 V and 11200-11700 V, with the 6909x card search and locked in 6 min 1s.
12500-12750 H and 12500-12750 V, in 1 min, 20s

 

[satesco]

Express-AM6 @ 53° E

Again, at 53.0E after a year and a half, this time with the 6909x card with the same updated neumoDVB and Crazyscan apps:

 

[satesco]

[td]


[/td]​

Türksat 3A / Türksat 4A / Türksat 5B @ 42° E

With neumoDVB(the 6909x card) and 1.10m antenna at 42.0E after Turksat 5B was activated{
10950-11200 HV,
11200-11700 HV,
11700-12500 H,
11700-12500 V,
12500-12750 HV

 

[satesco]

Türksat 3A / Türksat 4A / Türksat 5B / Türksat 6A @ 42° E

From time to time, an update of the satellites to different positions is necessary, especially if another satellite(6A) has been added to the existing fleet.
That's why I scanned at 42.0E all operational Türksat satellites at this position.

As usual, I used the neumoDVB (Linux) and Crazyscan (Win 11) app and the 6909x card.
Both apps can lock muxes with low symbol rate of 400 KS at 11027-11030 with blindscan all(neumoDV and manually with Crazyscan, but to succeed you need strong signal.

 

[satesco]

Thaicom 8 @ 78.5° E

For those interested in STID135 (6903x/6909x) cards, I am posting the results of scans using neumoDVB with 6903x (Linux) and CrazyScan with 6909x (Windows 11) at 78.5°E.

 

[satesco]

Chinasat 12 @ 87.5° E

Scanned with card 6903x on Chinasat 12 at 87.5E with neumoDVB and Crazyscan.

 

[moonbase]

Chinasat 12 @ 87.5° E

Scanned with card 6903x on Chinasat 12 at 87.5E with neumoDVB and Crazyscan.

@satesco

Can you please confirm if you used RF mode or FFT mode for your Crazy Scan spectrum ? It looks like it is an FFT mode scan ?
If it was an FFT mode scan, are the spectral peaks that correctly aligned with the vertical frequency markers ? It is not easy to be 100% sure due to the scan width.

I found that with a TBS6904-SE card using Crazy Scan in FFT mode, the vertical markers for frequencies were not aligned with the spectral peaks.
Perhaps this issue is resolved with the TBS6903-X card?

 

[satesco]

The same thing happens with both cards with FFTScan, but with Crazyscan, this is more evident on the weak signal.
I chose a satellite with an uneven signal in my area to compare the two blind modes.
Here is what the same signal looks like when read by Crazyscan with version 1.0.2.189, and then the same signal with 6902se (the same demod as 6904se) scanned with FFT and RFscan.

 

[moonbase]

@satesco

Thank you for your reply and the spectra.
It looks like the 69042E and 6904SE have the vertical frequency marker further away from the peak centre that the 6909-X ?

As it is, the FFT mode in CrazyScan is not fit for purpose with a 6904SE card. The output is useless.

 

[satesco]

For those interested in STID135 (6903x/6909x) cards, I am posting the results of scans using neumoDVB with 6903x (Linux) and CrazyScan with 6909x (Windows 11) at 78.5°E.

After the two muxes moved(11479 H and 11520 H) to new slots, they were scanned with 6903x. I'm also adding a Crazyscan spectrum with 6983.