It didn't, it just detected a deteriorating condition. They made the threshold which triggers the error message slightly less than that which would trigger complete signal failure, which explains why they worked before but not now.
Official 622 L4.01 Discussion Thread
- Thread starter Scott Greczkowski
- Start date
- Latest activity Latest activity:
- Replies 546
- Views 84K
I have a lnb drift for 129. It is currently at -7.85. According to one CSR tech, if it goes beyond -8.00 or +8.00, they will have to send a serviceman to determine if it needs replacement. If it reaches -10.00 or +10.00, the lnb will fail.
Another tech told me the lnb drift was due to a low signal on 129 and wanted to set up a service call (at my expense) to realign the dish. Since my signal is actually good for 129 (67 - 93 depending on transponder), I declined the service call. He also told me that the 9 second channel changes I was experiencing were due to the low signal on 129 (I just read today in this forum that the 9 second channel changes were for the MPEG4 channels only. Why don't the Dish techs know these things?)
Bottom line is -- I don't think any of the techs know what an lnb drift is. So why does Dish program the 622 to detect a problem when they are unprepared to deal with the problem?
I guess I'll just wait for the lnb to fail when the drift reaches -10.00 and tell Dish to send me a new lnb replacement, because I'm not paying for a service call to install it. That's when the fun should start...
I think the LNB drift stat is worthless when it comes to 129. It's not the LNB that's drifting, it's the fubar satellite. 
NightRyder
NightRyder
Like recording anything from 129 and not being able to watch it because an LOS locks up/reboots the box? That'd be a nice fix.
The update came through for me overnight in Rancho Cucamonga.
So far everything seeks to work OK, tho I haven't really given it a full workout.
I don't use OTA.
So far everything seeks to work OK, tho I haven't really given it a full workout.
I don't use OTA.
Update should have gone out to everyone with a 622.. Make sure both tuners of your 622 are off.. And wait.. Don't keep turning it on to look.. Can take a while for the update to begin. Update went out as late as this morning sometime. It may have missed your overnight reboot If you started watching TV this morning before the update got to your box.
L4.03 arrived sometime overnight and things seem to work well. Still checking stuff and will test recording something off the 129 sat to see if they've fixed that, but so far, typical functions seem ok.
4.03 --- Argh!
I was a fortunate one who had no problems with 4.01. Unfortunately 4.03 is looking to be more problematic. The first show I played with 4.03 suffered from the audio gap bug. This is where every ten seconds or so audio disappears for a second. A soft reboot appeared to fix this.
This morning I tried to play a program while one was recording. (Both were SD programs.) The 622 screen suddenly went black and the unit went dead. It didn't respond to holding the power button. I pulled the power for a bit and then restarted. It did play while recording then but these problems with the latest software is distressing.
How is it that for each thing that they fix in a version several more seem to break?
I was a fortunate one who had no problems with 4.01. Unfortunately 4.03 is looking to be more problematic. The first show I played with 4.03 suffered from the audio gap bug. This is where every ten seconds or so audio disappears for a second. A soft reboot appeared to fix this.
This morning I tried to play a program while one was recording. (Both were SD programs.) The 622 screen suddenly went black and the unit went dead. It didn't respond to holding the power button. I pulled the power for a bit and then restarted. It did play while recording then but these problems with the latest software is distressing.
How is it that for each thing that they fix in a version several more seem to break?
Can't they just go back to 3.66???
Tried recording a program off 129 last night. At one point, during a loss-of-signal, the box rebooted. So, 4.03 is worse than 4.01.
Did 4.03 fix anything at all?
Tried recording a program off 129 last night. At one point, during a loss-of-signal, the box rebooted. So, 4.03 is worse than 4.01.
Did 4.03 fix anything at all?
