Intelsat 14 @ 45W

[Andrew K]

I'm curious if anyone else is getting Intelsat 14 located at 45W. I am currently receiving a weak signal of RASD TV on 11566 H SR 1852 in Ohio.

I am using a 76 cm dish with motor and the Openbox S10. I can't find a map that shows the American footprint of this satellite. Does anyone know what my signal is supposed to be in dBW?

 

[xtgold]

I tried 45w today but I have the wrong lnb for that low a tp(standard ku linear)
lyngsat has the footprint map

 

[carlospr43]

working fine and really strong here in the carribean on C Band

 

[Pixl]

I've got RASD scanned in with the same parameters you got, but no signal tonight. We have rain, sleet, and snow with black clouds, not a good night for Ku. And I'm using a 1.2m dish here in Michigan.
I do see a data TP at 11497 V 7592.

 

[xtgold]

I may aim my fixed dish at it tomorrow.

 

[cyberham]

...Does anyone know what my signal is supposed to be in dBW?

44.3dBw...90 cm dish should do where you are. I have correct LNB, but I see nothing here with a 1m dish since I'm outside the footprint.

 

[Andrew K]

Lyngsat maps didn't have a coverage map for this satellite, and I was curious what the signal was. This seems to be the cutoff point for my 76 cm dish. The picture on that channel is pixelated, and barely comes in. I'm sure a 90 cm dish would help to get it reliably, but I don't really care to watch anything on that. I was just wondering what the cutoff signal was for my dish.

 

[cyberham]

Lyngsat maps didn't have a coverage map for this satellite....

This is the coverage map for Intelsat 14 at 45W.

 

[xtgold]

you click on the us&europe&africa on the same line as the tp info for rasd tv

 

[xtgold]

I've got RASD scanned in with the same parameters you got, but no signal tonight. We have rain, sleet, and snow with black clouds, not a good night for Ku. And I'm using a 1.2m dish here in Michigan.
I do see a data TP at 11497 V 7592.

that is a good tp to aim with,but I get nothing else.
1meter dish in ct.

 

[xtgold]

A weird one.
I switched to the openbox and it found another data tp 11453H 2314
I entered that info manually on the coolsat and got a quality around 90%
If I change the H to V,quality jumps to 97%
I assume the openbox scanned the H tp's first and when it found the V same freq it ignored it.

 

[Andrew K]

This is the coverage map for Intelsat 14 at 45W.

View attachment 71817

It looks like the signal is mislabeled for North America. It shows the higher signal at the edge.

 

[xtgold]

On my fixed dish I marked the mounting pole with the 45w location.
I tried for 43w again and got nothing.

 

[xtgold]

It looks like the signal is mislabeled for North America. It shows the higher signal at the edge.

the coolsat was goosed to show a higher quality level for marketing purposes.
On another brand the quality would be 70%

 

[Andrew K]

It's not the signal on the receiver... If you look at that coverage footprint map a few posts before this, you'll notice that the signal is shown as better away from the North American epicenter, and that can't be right. The edge of the footprint cannot possibly have a better signal. Look at the map.

 

[Pixl]

We had clear skys last night, still no more RASD for me, had it earlier this summer. The data chs are still booming in on a 1.2m dish in Michigan

 

[Jim S.]

When I had a universal LNB on, all I ever got was RASD (barely, even with the motor tweaked for Hispasat reception), an encrypted porn channel, and one or two data transponders. When I optimized the system for the western end of the arc (yes, I know I should be able to get the whole thing, but I'm tired of messing with it, and Hispasat is getting into the trees anyway), RASD and the other channel disappeared entirely, and on a bad day even the data transponders wouldn't be there. This is on a 90cm dish in northcentral Pennsylvania.

 

[AcWxRadar]

Andrew and everyone,

There may be problems recently with footprint maps accurately displaying the EIRP values due to something google maps has done.

Read this from Satbeams:




News - Website
Wednesday, 09 November 2011 09:18

Dear all,

Many of you have reported that there is an issue with incorrect EIRP reported on the map. The issue is caused by the limitation of 125 dots per polygon that was introduced in Google Maps API V2 without any advanced notice. As a result all the most precious maps are reporting wrong values despite the fact that all the data is correct in our Database.

To eliminate this issue we need to urgently upgrade the footprints page to the latest Google maps API. As we need to port a lot of functionality, it will probably take some time until the issue is completely resolved.

We will keep on posting the updates on the issue.

Thank you very much for your understanding and passion!

This might affect any EIRP map that utilizes Google Maps, but I don't think that it should affect the map that was posted earlier (I don't think that is a Google Map item). I see the error in that map (the EIRP level is higher going outward from the concentrated area of the beam). You are right Andrew, that has to be a mistake.

RADAR

 

[Hindu55]

RASD TV changed frequency. I show them now on 11608 H 1851.

 

[cyberham]

...now on 11608 H 1851.

Nothing seen there in Nova Scotia.