Echostar has filed FCC ground station applications to begin service using Echostar 16 on or about January 14. Echostar 16 Narrative
When the bulk of the 77CONUS markets moved over to 61.5 months ago, I was curious why some of them stayed on 77W. Then when the E16 SatMaps got posted I noticed that those markets that stayed on 77W were not on the list of spots on E16, so I figured the ones still on 77W would stay as CONUS. My perturbation is why those markets, and not the one I want?Yeah, I understand they aren't necessarily labled by that exact city. However, assuming transponder space this is what I'm looking at for the current markets on the 77 location.
I do definitely see what you're getting at about Cincinnati and a couple others. Lexington, KY in particular. Will be interesting.
When the bulk of the 77CONUS markets moved over to 61.5 months ago, I was curious why some of them stayed on 77W. Then when the E16 SatMaps got posted I noticed that those markets that stayed on 77W were not on the list of spots on E16, so I figured the ones still on 77W would stay as CONUS. My perturbation is why those markets, and not the one I want?
The spots only have numbers in the filings (example : spot 05). I add a geographical name of some city close to the center of the beam to make it easier to find which of the 70+ beams you want to look at in detail. So, the name is somewhat meaningless (except for identification of general geographic area of each beam) and has no correlation to what market is served by the spot. Any city in the beam (typically spot center out to -8 dbw) might or might not get service. Again, the entire nation is essentially covered by EchoStar 16 spots.When the bulk of the 77CONUS markets moved over to 61.5 months ago, I was curious why some of them stayed on 77W. Then when the E16 SatMaps got posted I noticed that those markets that stayed on 77W were not on the list of spots on E16, so I figured the ones still on 77W would stay as CONUS. My perturbation is why those markets, and not the one I want?
The spots only have numbers in the filings (example : spot 05). I add a geographical name of some city close to the center of the beam to make it easier to find which of the 70+ beams you want to look at in detail. So, the name is somewhat meaningless (except for identification of general geographic area of each beam) and has no correlation to what market is served by the spot. Any city in the beam (typically spot center out to -8 dbw) might or might not get service. Again, the entire nation is essentially covered by EchoStar 16 spots.
Except why some markets weren't moved from 77W to 61.5W in prep for this new sat. Capacity?That answers all the questions then.
Except why some markets weren't moved from 77W to 61.5W in prep for this new sat. Capacity?
Figuring out the TIDs is going to be fun.
-- "Sensorly or it didn't happen!"
Except why some markets weren't moved from 77W to 61.5W in prep for this new sat. Capacity?
There have been some requests for more information on the transponders and beams for EchoStar 16. I excerpted the Transponder/Frequency/Beam data from the FCC file and sorted it three ways so one can find answers more rapidly. It shows assignements and reuse of the various transponders. For those transponders showing both Conus and spot beam use, only one or the other can be used at one time to avoid interference.
Echostar has filed FCC ground station applications to begin service using Echostar 16 on or about January 14. Echostar 16 Narrative
Echostar is asking for short term authority to communicate (uplink/downlink) with E16 at the 61.5 location until they can submit the final paperwork (with the data they received from testing) for full time authority.Could you provide info as to what is this request for. I though they would start transfer on the 14th???
Will do today.Thanks for the table Nelson. Is there a map anywhere that shows all the spot beams on one image? Similar to what we've had in the past for the other sats. Just curious as it'd be nice to look at them all together.