625 in northern VA. I am now reading "spotbeam" on all odd transponders from 1 to 15. Transponder 3 seems normal. Transponder 13 signal strength went down to 75, but still shows anomalous ID behavior as above.
625 in northern VA. I am now reading "spotbeam" on all odd transponders from 1 to 15. Transponder 3 seems normal. Transponder 13 signal strength went down to 75, but still shows anomalous ID behavior as above.
Can you explain how I can lock onto 8 spotbeam transponders from northern VA? I thought I was only going to get 2. I suppose that, if everybody gets 2 spotbeams, then I'm seeing my own plus 3 adjacent DMAs.Without any tables yet I don't what signal this is, maybe a test signal from the Jackson, MS uplink since that is the beam I'm under.
Can you explain how I can lock onto 8 spotbeam transponders from northern VA? I thought I was only going to get 2. I suppose that, if everybody gets 2 spotbeams, then I'm seeing my own plus 3 adjacent DMAs.
Guessing here: the spotbeams actually overlap quite a lot, and different transponders are used in adjacent DMAs so as not to interfere with each other. But DMAs farther away, such as your transponder 9, must carry a completely different set of channels than my transponder 9, even though they're transmitting on the same frequencies.
Actually I wasn't thinking that way, but I see that I mis-typed, making it look as though I did. I should have said "if everybody gets 2 spotbeam transponders..." Anyhow, I apologise in advance to anybody who gets offended by my professorial know-it-all attitude evidenced below.You're thinking of one spotbeam equals one transponder frequency.
I would replace the bold word to Lockheed or that company who design and build the sat !<...> If anybody can lock more than 8 spotbeam transponders, then Dish is wasting bandwidth. I have gained a new respect for Dish's engineers. They're pretty damn smart.
I was looking on my 722. I'll check the 625 tonight.
Ted, next time provide model and SW version.
Sorry, the 722 is running L4.49 and the 625 is running L4.64.
Ted
Slightly off-topic, but my 625 now says software version L463, and it shows Previous Software as L464. Was there a problem with L464 that would explain the downgrade?
Thanks,
Ted