Originally Posted by lkrupp
For those either affected by or monitoring the recent DISH satellite 118 move and the loss of some local HD channels (mainly KTVI and KSDK) I find that today I have the two channels back without having a technician out. However, the signal level on Sat 118 transponder 18 is a mere 24. It WAS 0 since Monday 4/30. Transponder 11 is now 64 and WAS 57. So either they jacked up the signal or moved the satellite a little. With a signal level of 24 I'm probably on the edge and any sort of cloud cover will probably knock me out. Still, I do have all my local HD channels back. This makes a good case for me to get off my duff and install an OTA antenna.
A friend who also lost his local HD channels and has a visit scheduled for 5/8 was called by a DISH technician and asked a bunch of questions. The DISH guy said they had thousands of reports since the new 118 was moved and were trying to nail down whether they had thousands of misaligned dishes or some other problem. I'm guessing it's a little of both.
I suppose it's quite possible an antenna aiming issue. When you consider the "book" on aiming the 118° FSB LNB on the 500+ or 1000+ is simply peaking the dish on to 119°, and the first time technicians did any sort of mass install of these units in STL was when the HD locals went up on 118°, it's certainly a consideration.
OTOH, it is a bit odd, when you consider how many subscribers lost the signal from Tp18 after the move, most did not lose any signal at all.
That, coupled with, I have to think the "Dish Installer" saying there were "thousands of reports" is somewhat embellished, when you consider the entire national subscriber base of Dish (what...13-14m?), reduced by their subscriber base here in St. Louis, and then further reduced by the St Louis subscribers who have a MPEG4 receiver, and subscribe to the HD locals. In my conversations with Dish Engineering, I don't think the issue is quite that widespread.
Personally, I believe it is some sort of transmission issue, on Dish's end, which they will identify and fix, without the need of individual service calls to subscribers.
EDIT: I posted a question about this issue on DBSTalk on the 3rd....no replies, and there are plenty of STL members who read DBS.