Posts by hvdh

    I think we're dealing with 72 MHz transponders, hence testing doubles:
    Nr.1 centered 10743H, testing with 10724H and 10762H
    Nr.2 centered 10825H, testing with 10806H and 10844H
    Nr.3 centered 10907H, testing with 10888H and 10926H (wait for it)!

    Thanks satesco , my guess it's Turkey beam since the dB's are not great even at your location!

    qwer, DVB-S 5/6 also showed up here in the scan, but no lock as expected.


    Edit: next pair is up with DVB-S 5/6 30000: 10806H and 10844H.

    Looks like they keep it operational while relocating!


    Waiting for first TLE's of yesterday's Atlas 5 launch, with two USSF satellites.
    The WFOV (Wide Field Of View) Testbed satellite will augument the SBIRS series, and will also be part of a successive infrared early warning satellite series.

    Hard to unravel what is going on here, is it DVB-S or something else?

    Entering Strannik's Freq. and SR parameters on Dr.HD F16 often gives high dB readings (up to 17 dB), but never a lock.

    With TBS-5927 and CrazyScan, manual entry (no blindscan) crashes CrazyScan.

    At 3 June, AMC-14 started to move slowly from 18.0°E to the West, now at 17.55°E, it will probably hold at 17.5°E soon.
    Maybe this is to reduce the short-term interference to Astra at 19.2°E, that I mention in this topic before?
    In any case for me (without elevation control), it should be a bit easier to get some 12.2...12.5 GHz signals, since Eutelsat at 16°E doesn't use that range.
    Chart below shows the West movement since 1 June.

    Hi Satesco, 97.9°E Chinasat 11 has high band (12.25...12.75 GHz).

    But Express-103 may also have high band, though probably not with just 20 Ku transponders.

    My site changed URL over a year ago, you can find it here in the top menu "Satellites lists".

    Hm, so I´just start from position 47.7°E (or 47.6°E? :26.) a scan in upper band B circular left range (using band C LNB). No changes.

    hvdh, it looks like these ones are not from Nemesis...?

    Well, earlier in this topic Feedsat could separate between 47.6°E Al Yah 2 and 47.7°E Nemesis 1.

    So either Nemesis 1 is still at 47.7°E and the visual observations of the drifting satellite (now near 58°E) are of another satellite, or everything in this topic has been 47.6°E Al Yah 2 all along!

    Here is a link to the ITU information on 42E. It looks like there may be an upper Ku allocation on 5B. Most information says it will have Ku and Ka but there are applications for many other bands. The Milsat frequencies are consistent with some published information.

    hvdh Does this ITU data refer to the orbital slot or the satellite (Turksat 42E-H)?

    Turksat-42E-H probably refers to Turksat 5B, but others like Turksat-42E-G may as well.
    I don't know why so often there are multiple names listed at ITU referring to one satellite ultimately.

    Capitan_Uncino may understand better, if I'm not mistaken he has more access to the data on the ITU site.

    SBIRS-Geo 2 (incl. 1.7°) is at 20.7°E now, has moved a little bit from 20.6°E a while ago.


    SBIRS-Geo 1 (incl. 1.8°) is at 66.2°E since 2019.


    SBIRS-Geo 5 (incl. 7.7°) is at about 8.6°E, and has just arrived here after a 5-month journey from testing location 145.5°W.

    Note the high inclination, maybe this is to detect infrared events (launches) a little bit further North?

    I think 11386 H and 11414 H come from 61.95°E Intelsat 39.

    This satellite also has transponders in the 11.2...11.45 GHz range (72 MHz at 11405 MHz).

    I get a "no locked" of over 9 dB on 11414 H.


    No peak whatsoever at 11291 V, maybe that's really from 62.8°E ?