Signal strength, but 0 level and 0 quality.
I was hoping to get some help after 2 days of no success...
First off, this is not my first dish install, but the first with new equipment. My old equipment took about 15 minutes to find and align the satellites. I now have the 630 receiver with the xKu LNB and 60 cm dish. I also have an old 421 and 401 receivers that I have used to try to help troubleshoot.
I am in an area that requires me to self install, so I don't have the option of giving up and seeking a pro.
My mast is plumb (within my ability to accurately drill holes in brick), I have a clear view of the satellite location (A tall tree is roughly 13 degrees below the satellite location). I am using RG6 cable (new, but not quad shield) with a run of about 35-40 feet between LNB and receiver -there is a grounding block where it enters the house. Two similar lines have been run for the two connections on the receiver.
I entered the EMM id as 4128 on the tuning screen, but it stayed red and the meter was pegged at 0. (initially, I was tuning on channel 299, but was later told by shaw that I needed to use 252 -in both cases, the meter stayed at 0). My old receiver picked up 20% signal when connected, but this was clearly noise, as the signal was the same in all directions.
I was directed to the diagnostic screen by shaw and saw SL=0 SQ=0 SS=37. this was with ballparking the alignment. The tech told me to use that screen to align, as it was a realtime feed from the LNB. With this screen, I could see the ss change with dish position and I was able to get up to about ss=56. SL and SQ stayed at 0. ECb NO is "N/A" if the information given to me by the tech is accurate (the diagnostic screen lacks a label for the value.)
The next call to tech support told me that I was on the right satellite, but I needed to get SL and SQ to over 70. In all of my careful attempts to align, these numbers were stable at 0. My wife saw them jump up once for a second, but we could never get them back. I was moving the dish in very small increments.
What steps should I take now? Could this be a hardware problem?
Thanks for any help,