LNB Drift Detected

[charlesrshell]

HipKat what is LNB Drift? Here is a pic of my LNB Drift Detected screen (Diagnostics, Status, Issues) from my Hopper 3. Does the 0s mean my LNBs are OK? Thanks.

 

[pattykay]

It is a software bug that has been there for at least the last couple of versions. I see the same thing on my Hopper Duo, and several other people have reported it, too. For now, it is best to just ignore it, unless you are actually having problems with your satellite reception.

 

[Tony S]

what is LNB Drift? Here is a pic of my LNB Drift Detected screen (Diagnostics, Status, Issues) from my Hopper 3. Does the 0s mean my LNBs are OK? Thanks.

LNB drift is a shift in the oscillator frequency which prevents the LNB from properly tuning to a transponder. Dish receivers can make up for a small amount of LNB drift, but when it gets too high, the receiver cannot compensate, and the channel you are trying to tune to will cut out.

Many years ago I actually had LNB drift. It was related to heat. It was summer, and during the day when the LNB heated up, the drift would increase to the point where the channels would cut out. At night, when the LNB cooled off, the channels would return.

If I remember right, my receiver (which was a 722 or 722K) was able to compensate for a drift of about 7 or 8. When it was higher than that, the channels would cut out. Once I replaced the LNB, the drift went to zero and was not affected by heat.

Since your LNB drift is shown as zero, I don't think that you really have any LNB drift, it is just that software bug that everyone keeps referring to.

 

[charlesrshell]

LNB drift is a shift in the oscillator frequency which prevents the LNB from properly tuning to a transponder. Dish receivers can make up for a small amount of LNB drift, but when it gets too high, the receiver cannot compensate, and the channel you are trying to tune to will cut out.

Many years ago I actually had LNB drift. It was related to heat. It was summer, and during the day when the LNB heated up, the drift would increase to the point where the channels would cut out. At night, when the LNB cooled off, the channels would return.

If I remember right, my receiver (which was a 722 or 722K) was able to compensate for a drift of about 7 or 8. When it was higher than that, the channels would cut out. Once I replaced the LNB, the drift went to zero and was not affected by heat.

Since your LNB drift is shown as zero, I don't think that you really have any LNB drift, it is just that software bug that everyone keeps referring to.

Thanks Tony S

 

[Bobby]

If your Check Status screen says No Issues Found when you run it, I wouldn't concern myself with it.

 

[pattykay]

If your Check Status screen says No Issues Found when you run it, I wouldn't concern myself with it.

I agree. If the Check Status results say No Issues Found, then you would have to be really obsessive-compulsive to go ahead and click the Issues button anyway, to actually see this bug. Having said that, I have actually done that so many times. Perhaps if the results say No Issues Found, the software should just automatically gray out the Issues button. That would fix this problem for sure.

 

[AntiMoz]

The LNB drift warning is a software issue with the H3. There is at least one other thread here discussing it. It was not fixed in the most recent SW update released on 1/12/21.

Replacing LNB due to LNB Drift

My Hopper3 is reporting LNB drift as an issue. My dish is pole mounted and easily accessible. Is there any reason why I cant replace the Hybrid EA LNB myself without having a service call? It seems like a simple and straightforward swap.

www.satelliteguys.us

 

[pattykay]

The LNB drift warning is a software issue with the H3. There is at least one other thread here discussing it. It was not fixed in the most recent SW update released on 1/12/21.

Replacing LNB due to LNB Drift

My Hopper3 is reporting LNB drift as an issue. My dish is pole mounted and easily accessible. Is there any reason why I cant replace the Hybrid EA LNB myself without having a service call? It seems like a simple and straightforward swap.

www.satelliteguys.us

From that thread:

This false error will be fixed in the next software release scheduled for the beginning of December 2020.

So apparently it was fixed in the December software release, and then broken again in the January software release.

 

[charlesrshell]

From that thread:

So apparently it was fixed in the December software release, and then broken again in the January software release.

I never got a LNB drift error. I was just inquiring what the readings met.

 

[HipKat]

From that thread:

So apparently it was fixed in the December software release, and then broken again in the January software release.

Or more likely never fixed in the first place

 

[pattykay]

Or more likely never fixed in the first place

True. I was simply judging by the fact that there were no posts in that other thread in December. Then, all of a sudden, immediately after a new software update in January, this issue gets revived again in a new thread.

 

[pattykay]

True. I was simply judging by the fact that there were no posts in that other thread in December. Then, all of a sudden, immediately after a new software update in January, this issue gets revived again in a new thread.

Whoops, never mind. I just double-checked, and the last two posts in the other thread were from late December.

 

[AntiMoz]

Or more likely never fixed in the first place

Never fixed in the first place.

 

[pattykay]

Never fixed in the first place.

Still, with a gap of almost a month between posts (late November to late December) in the other thread, and then another gap of almost a month before this thread was started, this issue must not be that common. Either that, or it is just that very few people would bother to go looking for it, to actually find it.

 

[HipKat]

Still, with a gap of almost a month between posts (late November to late December) in the other thread, and then another gap of almost a month before this thread was started, this issue must not be that common. Either that, or it is just that very few people would bother to go looking for it, to actually find it.

A lot of techs are reporting it on our Tech Portal and I want to thank Tony S for that great info. I pasted the relevant info for other techs to take note of (With a credit of "Copied from another forum")

 

[Techlady]

It is a software bug that has been there for at least the last couple of versions. I see the same thing on my Hopper Duo, and several other people have reported it, too. For now, it is best to just ignore it, unless you are actually having problems with your satellite reception.

I'm having 2- to 3-minute dropouts of the video as often as every 10 minutes. Then it stops for as long as a week. Then it starts again in the afternoon, usually on Saturday (weird, right?). I had to threatened to cancel to get them to come out. I know things are tough for them, but after 20 years I think they need to give me service.

 

[MikeD-C05]

I'm having 2- to 3-minute dropouts of the video as often as every 10 minutes. Then it stops for as long as a week. Then it starts again in the afternoon, usually on Saturday (weird, right?). I had to threatened to cancel to get them to come out. I know things are tough for them, but after 20 years I think they need to give me service.

Call DISH and tell them that. There are other alternatives to DISH now and you should say you are looking at quitting their service unless they fix your problems. You can even push the phone button for cancellation and someone will come on the line and work with you to keep you. Might even get some freebies for your trouble or some money off your bill for a year.