only seeing even tp on 105

[TuxCoder]

I've had 105 problems since literally the day I got 2.01 (522) but I'm not sure it is the new software version. After the guy came and "fixed" it by replacing my switch and cutting off my ground wires, reception is crummy at best. At the moment, I cannot get any of my locals (Tp 15). Then I just noticed I can't get any signal on ANY of the odd numbered transponders. On the even numbered ones, I only get about 43-45 out of 125.

Could this be maybe a problem in the LNB? I should note my 110 & 119 sat connections have no problem moving between even/odd transponders and show consistent values. 110 gets 100/125 on both even and odd, and 119 gets 85/125 on even & odd.

I also notice that my skew on the dish looks to be about 112 when the point dish screen says it should be 113. The elevation on the dish is 41 (if I'm reading it right) but the screen says it should be 39.

Please help!

 

[TuxCoder]

whoa

I am now getting occasional signal blips (of 41 or so) on Tp 15 so I tuned to one of my locals to see if it could come in. It barely does, blocking and completely stopping every couple of seconds and resuming several seconds later--to be expected with only a 41/125 signal strength.

The cool thing is... some times it starts moving again, except... it's Angel One! It's like my receiver has ADHD and likes some kind of Christian rock video on that channel. It keeps switching back and forth randomly. I'd love some kind of explanation for that one. The local in question is 7426 (WHIO 7 Dayton).

 

[markav]

Tuxcoder, I'm becoming more and more convinced that this is a 2.01 problem. There is someone on the other Dish forum that describes the problem almost exactly as you have. And as you know from the other thread, I'm basically having the same problem also. Incidentally, I've seen it suggested that 2.02, which has already started to come online according to a source on the other forum, might solve the problem

One of my questions now is... what are the set of circumstances that started to set this off several days after getting 2.01? This happened to me almost a week after getting 2.01.

I'm tempted to erase ALL of my saved programs, reset to factory defaults, and see what happens.

 

[markav]

Well, I'm disappointed to report that I got my 2.02 update last night, and the problem still exists.