Spotbeams on 61.5

whatchel1

SatelliteGuys Master
Original poster
Sep 30, 2006
9,098
51
Great High Plains
I looking at the tps on 61.5 and no longer feel that the list has them correct for the spotbeams. I recently moved (for real) to a town in NW TX. Well the tps go as follows:
01 spotbeam 59
02 transponder 36
03 spotbeam 48
04 transponder 50
05 transponder 62
06 transponder 52
07 transponder 69
08 transponder 56
09 transponder 00
10 transponder 50
11 transponder 00
12 transponder 00
13 transponder 43
14 transponder 61
15 spotbeam 43
16 transponder 47
17 transponder 00
18 transponder 00
19 transponder 65
20 transponder 49
21 transponder 56
22 transponder 39
23 transponder 39
24 transponder 66
25 transponder 43
26 transponder 52
27 transponder 51
28 transponder 55
29 transponder 51
30 transponder 38
31 transponder 51
32 transponder 48
Since I'm not using anything special just a single feed dish 500 the list spotbeams should not be giving me this kind of signal levels. Also tp 05 should be listed as a spotbeam but isn't, as I've noted above it list it as a tp. I do plan on "moving " soon and want to pick up the Dallas Locals and I will use a larger dish (.9 meter) than I have now. But need to know that I will be able to pick them up before I contact E* to switch to the new location. I think that the spotbeam map is not correct and that Dallas's spotbeam is 16 not 17 on tp 15. It also looks like tp 05 is now a Conus rather than a spotbeam. I'm sure that the tps that show goose eggs are true spotbeams that don't point in my direction.
 
If TP 5 was now a CONUS beam you'd have a ton of pissed of customers who lost their locals. When checking signals on 61.5, throw out any that do not lock as those are bleed over from the receiver scanning for LNB drift.

TheList is not done by hand, it's all done by the transponder/channel tables automatically from the dishnetwork stream itself.

And it's always been known the maps are not correct. The maps are what the FCC has on file before Dish bought the satellite, they have since tilted the satellite causing the beams to shift northeast a bit. We're just spoiled with the other beam maps of E10 & Ciel-2 being right on the money.

I think you might be right on the Spotbeam 16 for that TID, as SB17 is not capable of transmitting on TP15.
 
All are locked

If TP 5 was now a CONUS beam you'd have a ton of pissed of customers who lost their locals. When checking signals on 61.5, throw out any that do not lock as those are bleed over from the receiver scanning for LNB drift.

TheList is not done by hand, it's all done by the transponder/channel tables automatically from the dishnetwork stream itself.

And it's always been known the maps are not correct. The maps are what the FCC has on file before Dish bought the satellite, they have since tilted the satellite causing the beams to shift northeast a bit. We're just spoiled with the other beam maps of E10 & Ciel-2 being right on the money.

I think you might be right on the Spotbeam 16 for that TID, as SB17 is not capable of transmitting on TP15.

All that have signal level show to be lock. Now tp 4 , 5, & 6 say locked name not acquired. I listed the goose eggs just to show all tps on the location. So I don't see anything to indicate the figures are on correct. 5 is the one that is most curious of the bunch why does it not indicate spotbeam w/ signal lock (as I said name not acquired)? I knew 61.5 was not as exact as the other sats but some of the info is just way off buy what I'm seeing on the SS here at my house.
 
All that have signal level show to be lock. Now tp 4 , 5, & 6 say locked name not acquired. I listed the goose eggs just to show all tps on the location. So I don't see anything to indicate the figures are on correct. 5 is the one that is most curious of the bunch why does it not indicate spotbeam w/ signal lock (as I said name not acquired)? I knew 61.5 was not as exact as the other sats but some of the info is just way off buy what I'm seeing on the SS here at my house.

If you don't see locked with a name of the satellite of 61.5, then consider it a zero.

Your TP 5 is some bleed over since it does not show a lock with the name of the satellite.
 
It's not a spot beam signal unless it locks solid and the word "Transponder" changes to the word "Spotbeam". Otherwise, it could be a spot beam signal too weak to lock as a spot or just bleedover. You'll only be able to ID spot beams for which you are actually in the footprint.
 
I updated the TID of the Dallas HD locals to the correct SB now. TheList should be correct now. Thanks for the heads up. Gets confusing with the weird uplinks they use for 61.5.
 
Can anyone estimate how much this spot beam has moved to the NE? Is it actually NE or more ENE or NNE? Thanks in advance for any educated guesses.

http://www.satelliteguys.us/thelist/index.php?search=dn61&sub=true&sort=&order=&beamMap=E12_SB13.jpg


If you want to know whether you are in its footprint, go to your point dish screen on your receiver, Menu 6 1 1, change the Satellite to 61.5 and change the Transponder to 13. If you are within the footprint, you will get a lock and the word "Transponder" will change to "Spotbeam".
 
If you want to know whether you are in its footprint, go to your point dish screen on your receiver, Menu 6 1 1, change the Satellite to 61.5 and change the Transponder to 13. If you are within the footprint, you will get a lock and the word "Transponder" will change to "Spotbeam".

Spotbeam 13 does not have a transponder 13. Spotbeam 13 is only transmitting on the transponder 3 frequency.
 
If you want to know whether you are in its footprint, go to your point dish screen on your receiver, Menu 6 1 1, change the Satellite to 61.5 and change the Transponder to 13. If you are within the footprint, you will get a lock and the word "Transponder" will change to "Spotbeam".

Software wouldn't allow an edit so replace "change the Transponder to 13" with "change the Transponder to 3".
 
Here are my numbers from approximately the same location as the OP;

01 63 - SB
02 48 - T
03 52 - SB
04 61 - L - NNA
05 75 - L - NNA
06 64 - L - NNA
07 75 - SB
08 65 - T
09 00 - NL - NNA
10 60 - T
11 00 - NL - NNA
12 00 - NL - NNA
13 50 - NL - NNA
14 70 - T
15 52 - SB
16 58 - T
17 00 - NL - NNA
18 00 - NL - NNA
19 72 - T
20 57 - T
21 60 - T
22 48 - T
23 50 - L - NNA
24 77 - T
25 50 - T
26 62 - L - NNA
27 58 - T
28 64 - L - NNA
29 56 - T
30 40 - T
31 57 - T
32 56 - T

Using a Dish 500 with a DP Twin.
 
If you want to know whether you are in its footprint, go to your point dish screen on your receiver, Menu 6 1 1, change the Satellite to 61.5 and change the Transponder to 13. If you are within the footprint, you will get a lock and the word "Transponder" will change to "Spotbeam".

I understand this. I don't have a dish pointed at 61.5. I'm on 110 119 129.

If the 61.5 spots moved say, 100 miles ENE, I probably could get that spot beam without much trouble, maybe a 30" dish would do it. If they only moved 25 miles or the movement was more to the NNE, I'd probably need at least a 2m dish if I could get it at all.

Any guesses on how much they moved? I thought someone was collecting signal strength and location data to figure that out.
 
Last edited:
I understand this. I don't have a dish pointed at 61.5. I'm on 110 119 129.

If the 61.5 spots moved say, 100 miles ENE, I probably could get that spot beam without much trouble, maybe a 30" dish would do it. If they only moved 25 miles or the movement was more to the NNE, I'd probably need at least a 2m dish if I could get it at all.

Any guesses on how much they moved? I thought someone was collecting signal strength and location data to figure that out.

I just remember them being somewhat north and east of the original FCC filings based on the DMAs they are spotting. I don't recall a precise movement estimate. Maybe Digi or Nelson61 know.
 

Users Who Are Viewing This Thread (Total: 0, Members: 0, Guests: 0)

Who Read This Thread (Total Members: 1)

Top