At 0512 this morning, transponder 15 on 61.5 went to 0. Everything else seem fine. Anyone else experiencing this?
For several months, I've noticed that at 5:12 every morning, my 622 switches to channel 101 on its own.
I'm pretty regimented in my morning routine. Around midnight, I tune the 622 to 005-00 (KXAS, my local NBC affiliate) so that when I turn on the TV in the morning, it'll already be on the channel I like for my morning news. I wake up at 5:00. I turn on the TV & 622 at 5:02 and the receiver is obviously on channel 5. While I'm in the restroom brushing my teeth, I listen to the news. At 5:12, I hear the channel 101 loop. It's easy enough to resolve. I can even hit recall to bring it back to channel 5, or manually dial it in, or navigate to it via the guide. For the remainder of the day, no problems.
I'd just assumed that this behavior was a nuisance bug since several software versions have passed. I figured it had something to do with the program guide update and subsequent reboot at 3:00 a.m. I'd also assumed it had something to do with elapsed time since turning on the receiver. As opposed to being related to 5:12 a.m. Perhaps it does it 10 minutes after being turned on for the first time every morning? Perhaps it has something to do with channel 005-00 itself?
On weekends, I'm not so regimented, so I haven't been able to determine if it's repeated....until this morning...
On Friday nights, I go to sleep watching the 722 (as opposed to the 622). I don't turn off the receiver at midnight, but rather it shuts itself down due to inactivity while I'm sleeping. This morning, I woke earlier than usual and turned on the TV/receiver at 4:50 a.m. This time I was using the 722. This time I was watching a different channel (HDNET)---in fact I'd surfed a little bit, even swapping tuners, until settling on HDNET.
While making my coffee at 5:12 a.m. on the nose, the channel switches to channel 101. WTF???
The variables:
- It happened on a different receiver (722)
- It happened from a different channel
- It happened after interacting with the receiver (changing channels) before it automatically switched
- It happened after swapping tuners
Both receivers are going to the same TV. I'm using a DP33. I have a Dish 500 with DP twin pointed at 110/119 and a Dish 500 with DP single pointed at 61.5 (as has been my configuration for years).
It seems this is probably related to my switch, but I find it odd that it only happens at 5:12 a.m.
My closest neighbor is more than 300 yards away and obscured by thick forest.
Transponder 15 has nothing on it . It is always 0...
Transponder 15 has nothing on it . It is always 0. At least till the new sat launches today and goes in service.
...15 is fine here...
I see that your 722k was stopping a recording, but was it automatically tuning to 101?...But the information about the 5:15 in the morning is still valid.
Now, it's miraculously back on with a signal strength of 50 which is about average for me. (I've been compulsively checking since my 1000.4 was installed 2 weeks ago).
Come on E-XV!
Since TP 15 is a spotbeam transponder, Echostar 15 will not help anything with the spotbeams problems you might be having. E12 will still provide spotbeam service at 61.5.
I usually have problems around 11:30 pm every night with TP 15 going in and out. I don't stay up any later so I'm not sure how long the problem lasts but everything is OK in the morning. I am on the fringe of the spotbeam so I don't know if that causes the problem but everything is fine up until then.At 0512 this morning, transponder 15 on 61.5 went to 0. Everything else seem fine. Anyone else experiencing this?
I see that your 722k was stopping a recording, but was it automatically tuning to 101?
It's just been almost amusing that at 0512 every morning, mine would automatically tune to 101 with the exception of a few times in which it would just go black for a few seconds. Then this morning, it actually loses signal. There was no "acquiring satellite" message, just "signal lost" followed by the locals placeholder.
For years, I've just assumed my 622 was possessed until I discovered it happens on my 722 as well. And now this. Weird.!sadroll
We use cookies and similar technologies for the following purposes:
Do you accept cookies and these technologies?
We use cookies and similar technologies for the following purposes:
Do you accept cookies and these technologies?