diff options
| author | Mauro Carvalho Chehab <mchehab@s-opensource.com> | 2017-03-07 09:18:08 -0300 |
|---|---|---|
| committer | Mauro Carvalho Chehab <mchehab@s-opensource.com> | 2017-10-03 08:43:17 -0300 |
| commit | a3224435f02b1ee4ea1942bef2459236af82e390 (patch) | |
| tree | fc89b5f5ae2077b064ac1ac7c8b4513099147102 /isdb-t/br-rn-PocoBranco | |
| parent | 38edecd2e19e9097e5a61fa1408147f3ced8e9b1 (diff) | |
| download | dtv-scan-tables-a3224435f02b1ee4ea1942bef2459236af82e390.tar.gz | |
Intelsat34-55.5W: add a Ku-Band transponder
According with http://www.satbeams.com/satellites?id=2641, Intelsat 34
has:
"22 C-band channels to provide services to to North and South America and
Europe and 18 Ku-band channels to provide services to Mexico, Central
America, Brazil, the Caribbean, Europe, a portion of the United States,
and the northern part of the Atlantic Ocean. It will serve the role
originally intended for Intelsat 27 that was lost at launch failure and
will replace Intelsat 805 and Galaxy 11 at 304.5 degrees East longitude
position."
Currently, we have only C-band frequencies for this satellite.
Add Ku-bands as used currently in South America.
The transponders that were obtained from Vivo TV package
matches the ones at:
http://www.portaleds.com/satelites/listar.php?sat=3045
with a difference of 1-2 MHz.
The LNBf I have is not capable of tuning the two IP data channels
there, but I'm adding it, anyway, as it could be useful for someone.
Signed-off-by: Mauro Carvalho Chehab <mchehab@s-opensource.com>
Diffstat (limited to 'isdb-t/br-rn-PocoBranco')
0 files changed, 0 insertions, 0 deletions