Tonight & The Rest of the Echostar X Moving Schedule

[RBBrittain]

110 readings from Little Rock, AR 72205, 5:54 to approx. 6:05 AM (522 tuner #1, Dish500):

01 93
02 0
03 102
04 0
05 92 (CONUS TP for LR locals until 1/06)
06 90 (Spotbeam)
07 87
08 0
09 90
10 0
11 90
12 78 (Spotbeam)
13 86
14 77
15 84
16 100
17 86
18 103 (New spotbeam for LR locals)
19 88
20 82 (CONUS TP for LR locals 1/06-4/06)
21 91
22 100
23 0
24 99
25 55 (Spotbeam)
26 0
27 100
29 100
31 101

Notes: I live just north of a tall building; I understand my signal barely clears that building. I've had some rain-fade problems in the past, and they did seem to be worse with LR locals the last few months. (The readings above at TP 20 vs. TP 5, our old CONUS TP before January, seem to suggest why.)

Though there was no rain at the time I took these readings, it was raining here heavily just before 5 AM; however, the reading on LR locals near the end of the storm (when I turned it on) was 77-78. At that time, I was clearly receiving all the locals, including the 3 formerly on 148 & 129 (KVTN, KKAP & KYPX--though KYPX was just a test pattern). This seems to be a good sign for reducing rain-fade problems here.

Edit: PQ seems to be significantly improved as well. E*'s PQ problems became obvious to me when I recently switched from a 13" RF-only set to a 27" HDTV; but for example, KTHV (CBS) on E* is just slightly lower PQ than its OTA HD signal (VHF), and comparable to its OTA analog signal (also VHF) after accounting for local OTA interference. KLRT (Fox, UHF for both HD & analog), the other major station that comes in strongly here, is comparable even though its source material (infomercial) is poorer.

 

[Derwin0]

Did anybody notice the gap between tonight and May 5th? That's a couple of weeks break and I wonder why they just don't continue with the moves. Just an observation.

More than likely they expect the spat with Directv over the three TP's to be resolved by then.

 

[BrettTRay]

It's interesting that I received no reading on TP's 7,13, 17 on the 301 but the 522 does. I checked these TP's on both tuners of the 522. I rechecked the 522 after getting the 6:40 AM readings on the 301

I checked on two different receivers after a post by joblo on dbstalk that implied that my readings on TP 3 were false due to a software error. If the readings on TP 3 are false then the software on both receivers is faulty.

Software error???? Thats hilarious!!!! The reason your not getting a signal on TP's 7,13,17 is because those are 8psk transponders instead of QPSK. The 301 doesn't have a chip/tuner that can decode 8PSK signals while the 522 (Broadcom BCM4500) does. Don't worry your not missing any channels on your 301 because it can't "see" 8PSK signals, these transponders are what the HD channels are on.

 

[BrettTRay]

Gadsden, AL 110W

Here's my readings from Gadsden, AL for 110W using a Dish500 for 110 and 119, Dish300 for 61.5 hooked into DP34 switch going to a 411 receiver.
Also, its pretty overcast outside but I don't think its having any effect on the signal

110W
TP1 - 104
TP2 - (Spotbeam) 0
TP3 - 113
TP4 - (Spotbeam) 0
TP5 - 101
TP6 - (Spotbeam) 70
TP7 - 100
TP8 - (Spotbeam) 0
TP9 - 100
TP10 - (Spotbeam) 0
TP11 - 103
TP12 - (Spotbeam) 46
TP13 - 96
TP14 - 102
TP15 - 97
TP16 - 114
TP17 - 100
TP18 - (Spotbeam) 100
TP19 - 102
TP20 - (Spotbeam) 66
TP21 - 102
TP22 - 110
TP23 - (Spotbeam) 77
TP24 - 110
TP25 - (Spotbeam) 0
TP26 - (Spotbeam) 0
TP27 - (Spotbeam) 110
TP29 - 114
Tp31 - 113

 

[guffy1]

Can someone please try and help me understand this transponder chart on the Echostar knowledge site?

I dont understand how to figure out which locals are on what transponder? For example Detoit locals are listed as on transponeder 26s13? What does this mean?

I was assuming maybe this meant they were split between 26 and 13, but then I saw Boise and saw they are listed as 25s41, and theres no transponder 41 at all that Im aware of..

Totally confused over here. Any help appreciated!

 

[RBBrittain]

I dont understand how to figure out which locals are on what transponder? For example Detoit locals are listed as on transponeder 26s13? What does this mean?

"26s13" means transponder (frequency) 26, spotbeam 13. Spotbeam satellites like E*10 can reuse the same frequency (TP #) on different spotbeams as long as they don't overlap. So for example, you can only receive Detroit locals if you're in the footprint of E*10 spotbeam 13; if you are, they come in on TP 26.

 

[murf]

Moved my locals to spotbeam 26 and am having all kinds of problems with my 622. Signal keeps droping out every 2 minutes or so. SF dma. All I have to do is touch the dvr button and it comes back. This crap is getting old fast.

 

[i4tas]

"26s13" means transponder (frequency) 26, spotbeam 13. Spotbeam satellites like E*10 can reuse the same frequency (TP #) on different spotbeams as long as they don't overlap. So for example, you can only receive Detroit locals if you're in the footprint of E*10 spotbeam 13; if you are, they come in on TP 26.

I saw on a spotbeam map on DBS Talk where two spotbeams using same transponder overlap. What happens then? how does that work if you are in that area?

 

[BFG]

I think in that case the channels on that tp will be in both spots

 

[UpAllNight]

I saw on a spotbeam map on DBS Talk where two spotbeams using same transponder overlap. What happens then? how does that work if you are in that area?

No 'legitimate' customer would be affected.
As long as the second spotbeam does not overlap the 'DMA' area of the other spotbeam, there will be no problem. You have to think along the lines of a DMA's 'footprint' first, rather than a spotbeams footprint first.

Hope I explained that clear enough.

The customer's DMA in the 'overlapped' area you refer to... will be serviced by another spotbeam and/or TP.

 

[g1van3]

I Still don't quite understand all of the info about E*10. When we lose certain locals from sat 110 do we just do a tp scan of 110 to find them on E*10? Some of the locals such as Springfield went blank on my channel list. Is there a certain place to look for them again or have they moved to another spotbeam which is unavailable to me? Thanks for any info.

 

[sikma]

I sense a post coming down from "Ice"

 

[RBBrittain]

I Still don't quite understand all of the info about E*10. When we lose certain locals from sat 110 do we just do a tp scan of 110 to find them on E*10? Some of the locals such as Springfield went blank on my channel list. Is there a certain place to look for them again or have they moved to another spotbeam which is unavailable to me? Thanks for any info.

I don't know if (a) you're scanning from a FTA receiver, (b) you're in a fringe area of the Springfield DMA, or (c) you "moved" to Springfield. I don't know about (a), but if you were subscribed to Springfield locals, they should have appeared automatically; the new Little Rock spotbeam did on mine (before I switched to Comcast).

If you're (b), call E* and let them know you're out of the new spotbeam; if you're also outside Springfield's Grade B contours (likely), you may now be eligible for distant locals instead. (SHVERA has specific language allowing distant locals in this particular situation.) If you're (c), call E* and "move" somewhere else; you're not in the Springfield spotbeam and never will be.

 

[russ222]

i have a ?..THEY MOVED THE MINEAPOLIS LOCALS TODAY..NOW I CANT SEEM TO GET THEM CALLED DISH ,,THEY WHERE LOST AS TO WHY ,,I HAVE DISH 500 FOR 110/119 IT SHOWS UP IN PROGRAM GUIDE BUT JUST KEEPS TELLING ME ITS LOOKING FOR SAT..EVERTHING ELSE WORKS ON THE 110 BUT MY LOCALS..ANY IDEAS..

 

[btbrossard]

i have a ?..THEY MOVED THE MINEAPOLIS LOCALS TODAY..NOW I CANT SEEM TO GET THEM CALLED DISH ,,THEY WHERE LOST AS TO WHY ,,I HAVE DISH 500 FOR 110/119 IT SHOWS UP IN PROGRAM GUIDE BUT JUST KEEPS TELLING ME ITS LOOKING FOR SAT..EVERTHING ELSE WORKS ON THE 110 BUT MY LOCALS..ANY IDEAS..

That's hard to read...

Are you in one of the following 8 counties:

Burnette, WI
Washburn, WI
Polk, WI
Barron, WI
St. Croix, WI
Dunn, WI
Pierce, WI
Pepin, WI

If you are, you should not be having a problem with your locals. If you're slightly further away from Minneapolis (out of the DMA), you may be out of luck now that there on SpotBeam.

 

[Voyager6]

Readings for 110W from Zip 21921, SD105, 522 DVR, DPP44 7:30pm

TP 1 104
TP 2 112
TP 3 85
TP 4 57 SPOT
TP 5 100
TP 6 113
TP 7 97
TP 8 113
TP 9 100
TP 10 99
TP 11 99
TP 12 100 SPOT
TP 13 95
TP 14 110
TP 15 93
TP 16 114
TP 17 97
TP 18 98 SPOT
TP 19 98
TP 20 101 SPOT
TP 21 103
TP 22 111
TP 23 57 SPOT *Baltimore, MD Locals*
TP 24 106
TP 25 81 SPOT
TP 26 96 SPOT
TP 27 0
TP 29 0
TP 31 70 SPOT

 

[jrbdmb]

I have to say that it's kinda sucks that subs like Voyager6 are getting a signal stength of 57 on the spotbeam that carries their own locals.

 

[bostonpro]

I checked the excel list and I don't see the Quad Cities(davenport - IA / moline, rock island - IL) on there. Are these going to move also or what? Any feed back would be great.

 

[Wdam33]

OK, I've been doing some checking on my locals (Louisville, KY) since they moved over to the new spot beam on Echo X. Here are my readings on my 301.

Old (before switch):
119 TP 11 : 120
110 TP 11 : 103

110 TP 4 (Spot beam locals): 125

Now (after switch):
119 TP 11: 120
110 TP 11: 104
110 TP 4 (Spot beam locals): 75

I assume that Louisville is 4S10 on Echo X. That number seems low to me for a spot beam. Plus, now when a heavy rain comes, we loose the locals...which never happened before. I went and checked connections and the dish (D500) is in fine shape. I don't believe its out of alignment since 119 TP 11 is 120 which its been since installation. Now, judging the spotbeam maps over at EKB, the spot is centered down in South Central KY near the KY/TN border (Just SW of London, KY). My location is just SW of Louisville, with the edge of the spotbeam about 50 miles to my NW.

Thoughts?

-Mark

 

[Pepper]

So... anybody have an idea when WEIQ 42 in the Mobile, AL DMA will be moved to 110? It's the only channel in the market still on 105. Would really like to disconnect the 105 and use that input for something else.

EDIT: never mind, it moved some time in the past few days.