I’ve now got two aging decommissioned, but working, 722s that I could add to the top of the pile of an asteroid bullseye target.
MPEG2 Western Arc shutoff
- Thread starter RTCDude
- Start date
- Latest activity Latest activity:
- Replies 438
- Views 55K
Nothing of interest, if anything. Everything available to the common subscriber is off from a national channel perspective. And based off of other reports, the last channels that were on spotbeams were to have been removed over the past 2 days. So I assume at this point there is nothing left.
As of today - there is nothing left on 129 and it is being removed from backend systems in an hour or so.
129 no longer shows up under my "Point Dish" option on the VIP211k nor on the Check Switch screen. It is GONE!!!
I can also verify that 129 is also gone from the Dish Diagnostics screen on H3s. Thank you for your service 129, but I’m not really that sad to see you go.
Interesting that 118 is gone. My VIP211k still has 118. My VIP211k has 61.5, 72, 105, 110, 118, 119, 121, 148.
Why 148 is there is beyond me - I am pretty sure that isn't used... Does Dish still use 105, 121, or 148?
So we’ve now reached the main conclusion of this thread, little did I realize when I posted the “end of July” rumor back in April this would be such an active thread with 360+ posts. It’s been an interesting 4 month ride
I’d like to give a special shout-out to Zippyfrog for all of his excellent work keeping track of the channel movements, and to JoshM for all the helpful insight he he was able pass on. And to all the other contributors that made this thread one of the more entertaining threads (at least to me) in a very long time.
And oh yes, a shout-out to Dish for pulling off this challenging transition.
Now that 129 content has finally sunset, maybe we could move on to speculating on what going to happen to the 129 satellite.
I’d like to give a special shout-out to Zippyfrog for all of his excellent work keeping track of the channel movements, and to JoshM for all the helpful insight he he was able pass on. And to all the other contributors that made this thread one of the more entertaining threads (at least to me) in a very long time.
And oh yes, a shout-out to Dish for pulling off this challenging transition.
Now that 129 content has finally sunset, maybe we could move on to speculating on what going to happen to the 129 satellite.
As far as I know, 105 and 121 are still there but being phased out, and 148 has been dead (quite literally) for more than a decade.
I do have the adequate equipment to aim for all three (linear SuperDish LNB for 105/121 and normal circular for 148), so I might give them a shot one day if I’m feeling bored, but I doubt I’ll see anything as 105/121 are supposed to be used for business packages and I don’t exactly own one lol.
I checked my switch status again. 110 & 119 is there. There is a third column but the satellite number is blank. Maybe that is my 118.
It is. We're currently troubleshooting that issue - your programming on 118 should work without issue...seems to be mostly a UI error.
You could disconnect the 129 feed then move the 118 feed from port 4 to 3 on your switch if you have it wired like I do (119/110/129/118). I also plan on removing the 129 side LNB off of my 1000+ to keep as a spare, and see if I can dial the other satellites in a little more, since I remember having to sacrifice like 10 points on 110 to get above 50 on 129, now I can do the opposite.
This seems to be the correct current workaround while we determine if we need to create a fix in software.
Check Status gets stuck at 60% since it can not determine the Satellite Signal Status with 129 gone.
Also Test Signal under Send Status doesn’t work since 129 was removed.
I suspect that Dish will address these diagnostics with a software update.
This is on a Hopper3 receiver running H355 software.
For those of us who fought for LOS on that damnable low orbit, distant bird for so many years, may she Rest in Peace! But she will NOT be missed!
Do you have PTAT enabled? I have hit that 60% issue before during a check status test. After a lot of troubleshooting, discovered it was because PTAT was recording. Even if you disable PTAT now it still will not work because PTAT is already doing its thing. Try performing a check status in the morning and see how goes it, unless you already have PTAT not enabled.
