The satellite is in inclined orbit, you would need a second motor (or two LNBs) to get continuous coverage.Thanks, I have only LNB for Ku Band. I wanted to prepare for eventual feeds
If your enigma receiver has a blind scan (not all do) you can see which frequencies are found from the search, data ones will be rejected once the search for receivable bouquets is underway.Thanks for the information. Is it possible to scan the transponder of a data channel on a enigma 2 receiver and check if the signal is available?
Does anyone know of some app (android) that can also scan frequencies on a enigma 2 receiver? I mean something like the SignalMeter app for example, but additionally with the transponder scan functionality.
Man, I didn't realise that 5G caused issues elsewhere on the arc. Thought it was just the deep western side...@11° West C-band, RHC here - North Nottinghamshire. - 2.2mtr PF / Circ poloriser / Norsat lnb.
** 5G interference present at this frequency causing problems.
3662 RHC. 10806. 1/2.
..........................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................
View attachment 152212
If you have a suitable e2 receiver:Thanks for the information. Is it possible to scan the transponder of a data channel on a enigma 2 receiver and check if the signal is available?
Does anyone know of some app (android) that can also scan frequencies on a enigma 2 receiver? I mean something like the SignalMeter app for example, but additionally with the transponder scan functionality.
<sat name="ExpressAM44 (11.0W)" flags="2" position="-110">
<transponder frequency="10981000" symbol_rate="45000000" polarization="1" fec_inner="0" system="1" modulation="0"/><!-- short/c/mis0 -->
<transponder frequency="10985590" symbol_rate="28405800" polarization="0" fec_inner="0" system="1" modulation="0"/><!-- short/t/s -->
<transponder frequency="11030000" symbol_rate="20060000" polarization="0" fec_inner="0" system="1" modulation="0"/><!-- short/c/mis0 -->
<transponder frequency="11060000" symbol_rate="9500000" polarization="0" fec_inner="0" system="1" modulation="0"/><!-- short/c/mis0 -->
<transponder frequency="11106250" symbol_rate="49090000" polarization="1" fec_inner="0" system="1" modulation="0"/><!-- long/t/s -->
<transponder frequency="11168750" symbol_rate="49090900" polarization="0" fec_inner="0" system="1" modulation="0"/><!-- -->
<transponder frequency="11173000" symbol_rate="7500000" polarization="1" fec_inner="0" system="1" modulation="0"/><!-- short/c/mis0 -->
<transponder frequency="11461000" symbol_rate="3100000" polarization="1" fec_inner="0" system="1" modulation="0"/><!-- ? -->
<transponder frequency="11494700" symbol_rate="24545000" polarization="1" fec_inner="0" system="1" modulation="0"/><!-- long/t/s -->
<transponder frequency="11543750" symbol_rate="49000000" polarization="0" fec_inner="0" system="1" modulation="0"/><!-- long/t/s -->
<transponder frequency="11584000" symbol_rate="7531000" polarization="0" fec_inner="1" system="0" modulation="1"/>
<transponder frequency="11608000" symbol_rate="1000000" polarization="1" fec_inner="0" system="1" modulation="0"/><!-- ? -->
<transponder frequency="11616000" symbol_rate="14400000" polarization="0" fec_inner="2" system="1" modulation="2"/><!-- feed -->
<transponder frequency="11668750" symbol_rate="49091000" polarization="0" fec_inner="0" system="1" modulation="0"/><!-- long/t/s -->
<transponder frequency="11668750" symbol_rate="49091000" polarization="1" fec_inner="0" system="1" modulation="0"/><!-- -->
</sat>
Man, I didn't realise that 5G caused issues elsewhere on the arc. Thought it was just the deep western side...