Beiträge von satesco

    -The setting for lnb C is on the "LNB type" column, where you choose the lnb used(Ku, C, and Ka).
    I have underlined in my table in the screenshot. Also, on that table, you can choose the polarity: Left or Right.
    It is enough to choose "C" in the column that the neumoDVB finds the local oscillator for the C band by itself.

    -I'm not sure, but it seems that when the system (Dragon or Ubuntu?) is installed, its resolution doesn't correspond to the monitor's resolution. If this is true, it means the installed kernel is incompatible with the graphics card driver. If this is the case, try changing it with the graphics utility or graphics card driver.

    Hi Sergey,

    @deepthou has made some notable changes especially to the driver for stid135 cards and has updated neumoDVB to version 1.7. He has reported that he has detected a bug that he will fix. He has probably removed this bug.
    I say that you should post your driver and neumoDVB issues on the English forum, although we have a dedicated topic here too, but I guess deeptho would not have time to visit those forums where his application is discussed.
    The English forum is where he concentrates most of his time because that's where he launched his application and where people who have problems look for his answers.

    So I can't say for sure what problems those who install them have.
    Maybe soon I will install them myself, after I upgrade to the stable Ubuntu 24.04 LTS. :3:
    .
    .

    11566 H,31427,1/2 ,S2-Data, (on Flysat),

    12539 H,31428,1/4, S2-Data, new,

    12577 H,31428,1/2, S2-Data, new,

    12616 H, 31426, 1/4, S2-Data, (on Flysat),

    12654 H,31428,1/4, S2-Data (on Flysat),

    12692 H,31428, 8/9, 16APSK- Data, new,

    12731 H,31428, 1/4, S2-Data, new.

    10834 V, 31428, 13/18, (S2X)/16APSK-Data (on Flysat),

    10873 V, 31428,13/18,(S2X)/16APSK- Data, new,

    10992 V, 32724,23/36,(S2X)/16APSK-Data (on Flysat),

    11219 H,31428,7/9, (S2X)/32APSK,0.05- Data, new,

    11278 V,30000,11/15,(S2X)/32APSK,-Data, (on Flysat),

    11317 V,31427,32/45,(S2X)/32APSK-Data (on Flysat),

    11334 H,31427, 25/36,(S2X),(S2X)/16APSK,0.05-Data(on Flysat),

    12558 H,31428, 13/18,(S2X)/16APSK,0.05- Data (on Flysat),

    12588 V,15713, 2/3,S2X/16APSK-Data, new,

    Two muxes were found and locked only with cards 6909x with neumoDVB:

    11191 V,17143,5/9, S2X-Data, new,

    11209 V,17142,28/45, S2X-Data, new.

    11282 V,1090,1/2,S2-GS, new.

    The trees in the direction of the antenna are blocking my 40.5W position.

    It's still good that I can pick up a few transponders, and why not, satellite news like this one.


    satesco hope that with this driver card will work without crashes and freezes

    I want the same thing, but I'm surprised you have crashes and freezes with the 6903x card. I haven't had such problems.
    I still don't know how the new driver behaves, as I haven't installed it yet. :3:

    It is a "battle with the windmills" for those with small antennas to lock the Paksat C-band. But as the saying goes, the attempt never dies in this case.

    I, for example, have locked two muxes, de Data. It's a start, at least, to maintain the illusion that it's possible one day...

    I tried two 5G LNBs, Mediastar 5G and Titanium C138:

    I scanned the satellite only from 4000 MHz because of the strong signal at 40.0E. However, I tried to find a better directivity (oh là là là) on my small antenna. :3:

    It's a pity that this Blagovest has no TV/Radio programs; it would have interested even those with antennas smaller than mine, especially as it is a central satellite for many parts of Europe. :3:

    Errata: on spectrum, It reads 12.0 East and not West!

    It was a real surprise to lock and be able to run the T2-MI stream on 3750 H (intermittently).

    I didn't think I would be able to receive it in the 3700 MHz part of the band since the antenna is small, but even worse, using an LNB without anti-interference is the most area-prone.

    The problem in this case was the antenna size and less interference, although it affected signal stability.
    Of course, to run the T2-Mi stream smoothly, you need at least 9 / 10 dB, or my 1.50m antenna barely got over 7 dB.

    The easiest to run was the Radio stream on PID 174.

    With the neumoDVB, it's pretty much the same; I didn't get a clear picture.

    I'm probably a bit masochistic for receiving such a T2-MI stream with the small antenna, but it's still a small success.:3: