positioned at 17°E, result from 20°ELocked at
3886 V 27500 5/6
3966 V 27500 3/4
... a technical problem, sorry
positioned at 17°E, result from 20°ELocked at
3886 V 27500 5/6
3966 V 27500 3/4
... a technical problem, sorry
Nothing unusual I found on this satellite.Scanned with CS,IQmonitor and TBS Blindscan.
3797 L 1850 SRTV , new crazy parameters now, 8PSK 8/9
7db here,2m.
3797 L 1850 SRTV , new crazy parameters now, 8PSK 8/9
Thanks marval450 for this update - just my signal.
Hallo
auch meinerseits kann ich diese Transponder bekommen
und mit 9dB.
für 3787LZ 1850 habe ich leider ungefähr 4dB zu wenig.
Probably a new package from DalSat GLOBAL:
3801 L 4270 5/6 DVB-S
This package changed to:
3785 L 4270 3/4 DVB-S
Hallo ,
Ich bin erstaunt , dass mit nur 1,80m bei manchen Transponder nicht so grosse Unterschied in Vergleich mit einer 4,90m gibt.
IQMonitor pro 1020 hat sogar einen Transponder mit Radios gefunden ( 3854,324 H 1390 3/5 8PSK) die nicht mit 4,90 gefunden wurde.
Hello ,
I am surprised that with only 1.80m there is not such a big difference with some transponders compared to a 4.90m.
IQMonitor pro 1020 even found a transponder with radios (3854,324 H 1390 3/5 8PSK) that was not found with 4,90.
PS es gibt auch ein TV Programm : Espace TV
there is also a TV programme : Espace TV
Hello stephan94,
thanks for your scan.
Here are my current results in circular left on 4.9m, using Kaonsat LNB and AVComm Waveguide in manual scan:
3785 L 4270 3/4 DVB-S - 17.7dB (13.7dB over LM) in my last report above
3797 L 1850 8/9 DVB-S2 8PSK - 11.6dB (1.0dB over LM) ...problem for clear video
3827 L 1630 3/4 DVB-S2 QPSK - 16.0dB (12dB over LM)
3851 L 1262 2/3 DVB-S2 8PSK - 17.4dB (10.8dB over LM)
3853 L 1389 3/5 DVB-S2 8PSK - 13.3dB (7.8dB over LM)
3860 L 400 3/4 DVB-S - 14.6dB (10.6dB over LM)
3934 L 27500 7/8 DVB-S - 17.2dB (10.2dB over LM)
3797 L 1850 8/9 DVB-S2 8PSK - 11.6dB (1.0dB over LM) ...problem for clear video
Now with TBS 6925 (before with TBS 6903)... getting "ID"
I'm sorry, but after bringing to the same scale and comparing the spectra (or, more precisely, the parameters of the found transponders), very disappointing conclusions arise.
Which?
And you compare the blue transponders on the upper spectrum with the orange ones on the lower spectrum and, accordingly, the red ones at the top with the blue ones at the bottom ...
Write here - let's see if they match mine...
I have to make a clarification about neumoDVB, which I'd better make from the beginning. I should not compare its spectrum with Crazyscan and EBSpro or IQmonitor, because for these I used the 6983 cards, while for neumoDVB I used the 6903x card.
It is good to remember this, for reasons that seem obvious to me, the most important being that the DVB applications (Crazyscan, EBSpro, and IQmonitor) for Windows have been designed and, I would say, polished by CrazyCat, Christian, and Strannik to make the most of the extraordinary capabilities that the STV6120/STV0910 of this card has, which are enjoyed primarily by dxers, but also by other users.
For the 6903x card we still have to wait (I don't know how long) for someone to get the "steroids" out of this card. For now, only CrazyCat is trying under Windows to bring it to the same level of performance as the 6983, precisely because this card has high-class hdw support. But of course, many things for this card no longer depend on him.
Probably for the same reasons but with a different approach, the developer Deeptho has created special drivers for some DVB cards and its own application (neumoDVB) under Linux, hoping and in good part succeeding in exploiting the potential of 6903x/690x, using a different algorithm for searching and locking the signal, which resulted in a significant improvement of the card scanning time. On the other hand, it has managed to make the demod stid135 lock at a low symbol rate even below 500 kS/s, which Windows does not manage every time.
I won't go into details, but I mentioned these things because also at the level of the application interface (blindscan) there is a difference in graphics (and not only) between, say, IQmonitor (since Strannik mentioned it) under Windows and the one chosen by Deeptho for Linux.
Without going into details, I can answer Strannik's "disappointment" with the answer I received from Deeptho's developer when I asked him about the color that distinguishes polarities in his application, and the answer was: "Blue is used for the first graph, orange for the second, and so on. If there is only one graph it is blue."
I apologize for going on longer than I should have. I admit it's my fault that I shouldn't have posted the results for 6983 on Windows with 6903x on Linux obtained with the neumoDVB app.
Deeptho's neumoDVB app needs to be discussed/written about separately, especially for 6903x/6909x cards. But since the application is still in progress, I kept postponing writing; plus I am confused by some things, especially since I come from a Windows environment and have to learn many things in Linux
It's not about the interface, the color of the curves and other unprincipled things.
The point is not in the operating system, but in the fact that the results, namely blocking frequencies and symbol rates,
differ unacceptably strongly for different programs.
I am closely following the new software and sincerely wish its developer success in improving the driver for DVB-S2X cards,
so I hope that comparing the results with programs whose accuracy is beyond doubt will be useful for him.
Just a current scan, using TBS 6903 and CS.
Just my signal on 3858 L, appeared in last BS by satesco on 23.07.2022 above ->listed on FlySat by khaled Star on 31.07.2022.
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!