Transponder & Band Plans

Discussion in 'DIRECTV Tips and Resources' started by tomspeer46, Jun 19, 2015.

  1. Jun 19, 2015 #1 of 120
    tomspeer46

    tomspeer46 Legend

    692
    84
    Nov 17, 2011
    Eastern NC...
    Transponder Tables

    Links to various tables and descriptions of the DirecTV satellite transponders:
    These are links to another site, because I can no longer upload .xlsx files to this forum.






    DirecTV Satellite Transponder/PID Channel Grids
    Transponder Channel (PID) count by type
    DirecTV Satellite Transponder Tables
    giving technical details of each transponder
    Spectrum Band Plans

    The above data are checked for changes weekly, normally on Wednesday, and updated accordingly.

    Explanation of TPN numbers: (Post #29)
    Transponder available data rates: (Post #30)
     
    Last edited by a moderator: Jan 24, 2019
    1 person likes this.
  2. Jun 19, 2015 #2 of 120
    tomspeer46

    tomspeer46 Legend

    692
    84
    Nov 17, 2011
    Eastern NC...
    DirecTV Satellite Transponder Tables

    This Excel workbook documents connections from uplink to downlink for the physical satellite transponders as documented in the FCC databases, with correlation to the TID and TPN used by the receiver software as documented in Gary Toma's TPN maps, combined with data collected each week on modulation, encoding and FEC ratios.
    The data is taken, where possible, from the FCC Schedule S filings for the satellites, and combined with data from our weekly data collection. and some manual entry. The location data for the beams were created to give an indication of the market served.

    I will try to update this as soon as I can, after we see any change in the transponder data in the weekly collection. It doesn't change often. The data is color coded to indicate its source according to the legend at the bottom of eash sheet.

    The data is presented as an Excel workbook, with tabs for each Satellite.

    The transponder table for D12 is well documented in the FCC database. It was built as a spare for both D10 and D11. It does contain information on transponders that are only used on D11. There are 13 transponders that share the same uplinks as another transponder, but are not used on D12. Those transponders, on the other hand are used on D11. The FCC data for D11 is taken from the data for D12 and D10.

    The data for D15 has been condensed from the FCC Schedule S data. To satisfy FCC filing requirements, DirecTV documented 6 transponders for each uplink frequency. Each of these groups of 6 represent only one transponder in the Satellite that has two possible input beams and 3 output beams. I have simplified this table by considering each frequency down converter as one transponder. The two uplink and three downlink beams are noted for each transponder.


    These tables are purposely only about the 36 MHz transponder channels, without reference to the data about what TV channels are carried on them. For that information, consult Gary's TPN maps.

    3/2/2016- corrected some downlink beam names for D15

    3/17/2016 D11 Transponder chart revised. All uplinks changed to agree with Schedule 43 of the LOA for D11, at this time, we have no information to show that this is not the present configuraion.

    3/31/2016. After much discussion and consideration, I am eliminating the geographic description of the beam locations. The beam names for all LIL spot beams reflect the names of the DMAs that are serviced by the beam (Primary DMA only, no "viruals"). For multi-City DMAs, it is just the first city of the DMA name that was used, sometimes abbreviated.. It has been difficult, in a few cases to get all of the DMA names in a reasonable length beam name. I am embarking on a project with Gary Toma, to match all of the Beam Footprint Library names to these new names. It will take some time to get that all updated.

    4/11/2016 The names have been updated again. We are converging on a solution.
    4/21/2016 Corrections to a few beam names. Noteworthy: Santa Barbara SD channels are not on D7S beam B06, They are are on D7S beam C38. This corrects an error I made when manually assigning Markets to beams.
    4/27/2016 Minor corrections to beam names.
    6/15/2016 Cleanup
    6/31/2016 Updated 4 transponders

    No further updates will be listed here, since DBStalk has made it difficult to maintain tabular technical data, and I cannot upload Excel spreadsheets. The link below will take you to the current data:

    Domestic Satellite Transponders (Current version)
     
    Last edited by a moderator: Jan 24, 2019
    1 person likes this.
  3. Jun 20, 2015 #3 of 120
    tomspeer46

    tomspeer46 Legend

    692
    84
    Nov 17, 2011
    Eastern NC...
    DirecTV Band Plans, Frequencies, TIDs and TPNs 12/30/2016

    Since I can no longer upload .xlsx files to this forum, please find this information on an external site: HERE

    I have added the Sky Mexico Band Plan to the US Domestic and Latin American Band Plans.
     
    Last edited by a moderator: Jan 24, 2019
    1 person likes this.
  4. Jun 20, 2015 #4 of 120
    slice1900

    slice1900 Well-Known Member

    10,127
    1,321
    Feb 14, 2013
    Iowa
    They probably don't bother to optimize stuff like that. Sort of like how Tivo left the SD Settings menu in place when all the other menus were updated to HD. It is rarely used, so not worth the effort. If they were going to optimize it, it would be better to have it show only the spot beams relevant to your market.


    Or start it up with the coax disconnected, which is probably easier to do for a test :)

    This was my theory for a workaround to the issue of H20s locking up when you try to access the signal strength screen. When it downloads satellite data upon startup there's something in the data since about late March / early April that its firmware doesn't know how to deal with. If you start it up without the coax, it doesn't download that info, and it can view satellite strength - useful for troubleshooting if it is receiving a signal, or if its SS screen was all you had to try to align a dish. The same might be true for H2x/HR2x that haven't been updated to have the 99ca screen, but it isn't really an issue since once they're updated they'd be fine.
     
  5. Jun 20, 2015 #5 of 120
    tomspeer46

    tomspeer46 Legend

    692
    84
    Nov 17, 2011
    Eastern NC...
    I tried the disconnected coax, but with it set to use a SWM LNB, it gets cranky about finding the SWM. My dish is accessible from the ground, so to test what happens, I just unclamped the LNB, and pointed it at the ground, without disturbing the dish alignment.
     
  6. Jun 20, 2015 #6 of 120
    inkahauts

    inkahauts Well-Known Member

    24,439
    1,383
    Nov 13, 2006
    In Los Angeles they have made it so we can not see every spot beam from 99 and 103. Granted they still let us see what I think may be Palm Springs and Santa Barbra.
     
  7. Jun 20, 2015 #7 of 120
    KyL416

    KyL416 Hall Of Fame

    5,391
    1,059
    Nov 10, 2005
    Tobyhanna, PA
    I see every TPN that's defined on my readout, the ones that don't reach my area at all read 0, while ones that I'm on the fringe of have lower numbers:
    For 99s
    TPN 1 (Johnstown, PA) - 71
    TPN 2 (nothing that reaches my area) - 0
    TPN 3 (Charlottesville, VA) - 42
    TPN 4 (Utica, NY) 97
    TPN 5 (nothing that reaches my area) - 0
    TPN 6 (nothing that reaches my area) - 0
    TPN 7 (nothing that reaches my area) - 0
    TPN 8 (Salisbury, MD) - 42
    TPNs 9-14 - N/A
    TPN 15 (nothing that reaches my area) - 0
    TPN 16 (New York, NY) - 95
    TPN 17 (nothing that reaches my area) - 0
    TPN 18 (nothing that reaches my area) - 0
    TPN 19 (Nothing I can find on the current sheet, perhaps another nearby market like Binghamton, NY or Elmira, NY is prepping to move here) - 91
    TPN 20 (New York, NY) - 95
    TPN 21 (Syracuse, NY) - 57
    TPN 22 (Burlington, VT) - 69
    TPN 23 (nothing that reaches my area) - 0
    TPN 24 (Providence, RI) - 31
    TPNs 25-32 - N/A

    For 103s
    TPN 1 - 0
    TPN 2 (Elmira, NY) - 96
    TPN 3 - 0
    TPN 4 (Binghamton, NY) - 95
    TPNs 5-14 - N/A
    TPN 15 (Philadelphia, PA) - 94
    TPN 16 (Harrisburg, PA) - 95
    TPN 17 (Hartford, CT) - 83
    TPN 18 (Albany, NY) - 89
    TPN 19 (Wilkes-Barre, PA) - 98
    TPN 20 (Baltimore, MD) - 97
    TPN 21 (Buffalo, NY) - 95
    TPN 22 (A mix of Buffalo, Rochester and Syracuse, NY) - 93
    TPN 23 (Philadelphia, PA) - 91
    TPN 24 (Philadelphia, PA) - 95
    TPNs 25-32 - N/A
     
  8. Jun 20, 2015 #8 of 120
    HoTat2

    HoTat2 Hall Of Fame

    7,781
    234
    Nov 16, 2005
    Los...
    Ok Tom;

    So after some more study on what you say and to take local markets served by SW2 as the example again. To determine the levels for ...

    TPN 5 - would be to sample the levels on xpndr frequencies assigned to TIDs 44, 52, and 60, for the average or possibly the highest level and then display this amount on TPN number 5.

    For TPN 6 - Samples TIDs 53, 45, and 61
    For TPN 7 - Samples TIDs 46, 52, and 64
    For TPN 8 - Samples TIDs 55 and 63

    ?

    Edited for erroneous TIDs initially ascribed to TPN 5

    Sent from my SGH-M819N using Tapatalk
     
  9. Jun 20, 2015 #9 of 120
    tomspeer46

    tomspeer46 Legend

    692
    84
    Nov 17, 2011
    Eastern NC...
    You can't see signals from spot beams that are not close to you. For instance, I receive no programming on 99s (Net 11) TPN 1-8 I am very close (25 miles) to two DMA's that get their locals on TPN 4 and 8 (this week, not last week). I see zeroes on tpn 1,2,3,5,6,7 and 100 on 4 and 8.
     
  10. Jun 20, 2015 #10 of 120
    HoTat2

    HoTat2 Hall Of Fame

    7,781
    234
    Nov 16, 2005
    Los...
    What inky means Tom is that in the LA market the receivers don't even let us see any low or 0 levels from nearby spotbeams of other markets beyond possibly Palm Springs and Santa Barbara on TPNs 19 and 21 on 99s

    Everything else on 99s and 103s reads "N/A" except for our own spotbeam TPNs 19, 21, and 22 on 103s

    Sent from my SGH-M819N using Tapatalk
     
  11. Jun 20, 2015 #11 of 120
    tomspeer46

    tomspeer46 Legend

    692
    84
    Nov 17, 2011
    Eastern NC...
    It is much worse than that. To get the readings for TPN 5 on the 99(s) display, the software has to measure the signal quality on each of the NET 11 TIDs assigned to tpn 5. So in your first example of TPN 5, it has to sample the signals on each of the frequencies and polarities from 99 W assigned to TPN 5. So it has to tune to and measure the quality of TIDs 4,12,20,36,44,52,60,68,76,and 92. It would not look at TID 62, since that is assigned to TPN 7.

    TPN 6 would be TIDs 5,13,21,37,53,61,69,and 77.

    On my 99s display I see a signal level of 100 on TPN 4. To get that, the software had to look at TIDs 3,11,19,35,51,67,75. That is every TID in my band plan chart assigned to Net 11 TPN 4, whether it is currently carrying programming or not. It would have found no signal on anything but TID 75 from D14, because that TID serves a DMA which is only 25 miles from where I am, and I am within the second contour (light blue) of the beam footprint.
     
  12. Jun 21, 2015 #12 of 120
    tomspeer46

    tomspeer46 Legend

    692
    84
    Nov 17, 2011
    Eastern NC...
    Wow! LA is specia!. Has this persisted through many software revisions? On a variety of models? Actually, you are lucky: The fact that it is displaying NA means that it is not wasting time trying to read all those other signals. For the rest of us, a 99s or 103s display takes a long time. When I start one of those, I usually find something else to do for a while.

    I wonder if this has something to do with being close to the LABC.
     
  13. Jun 21, 2015 #13 of 120
    HoTat2

    HoTat2 Hall Of Fame

    7,781
    234
    Nov 16, 2005
    Los...
    Yep;

    It's been that way for a long time now in LA on all receiver models I've seen and through many firmware versions. And yes I readily see the big difference in speed this way with the 99s and 103s screens displaying in maybe a couple of seconds after selection.

    On the other issue, thanks, understand it now. Thought perhaps the TID sampling for the SS screens would be limited just to the host satellite serving the locals of a market, but see that's not the case.

    Sent from my SGH-M819N using Tapatalk
     
  14. Jun 21, 2015 #14 of 120
    inkahauts

    inkahauts Well-Known Member

    24,439
    1,383
    Nov 13, 2006
    [​IMG]

    [​IMG]

    Yeah this is what I am talking about. We have had it this way for years. On all Hi Definition receivers that are current.

    I think they where testing it for a wide solution and then abandoned it for whatever reason. That's my personal guess. Maybe it was difficult to do it everywhere because of database sizing and such that may have to be stored on the units and if that would actually slow them down as much or more anyway. Who knows.

    Before this was happening we had all the zeros that took forever to show 0 just like everyone else still has today. We of course do have that issue still on 110.

    Realize that the signal strength screens used to take a LOT longer to populate especially the 99 and 103 and then several years ago around the time that they did this for the locals the process for all those screens increased in speed dramatically. I don't know for sure what they did but they changed what it was looking for I think so it'd be faster.
     
  15. Jun 21, 2015 #15 of 120
    tomspeer46

    tomspeer46 Legend

    692
    84
    Nov 17, 2011
    Eastern NC...
    Maybe they implemented that for Southern California because that is where the DTV engineers live. They made their displays faster.
     
    1 person likes this.
  16. Jun 21, 2015 #16 of 120
    tomspeer46

    tomspeer46 Legend

    692
    84
    Nov 17, 2011
    Eastern NC...
    Actually, I think it is just the Los Angeles area. I think Gary in San Diego sees all of the readings.
     
  17. Jun 21, 2015 #17 of 120
    tomspeer46

    tomspeer46 Legend

    692
    84
    Nov 17, 2011
    Eastern NC...
    Kyl416-

    Thanks for your SS readings. I live about 200 miles north of you, in Long Lake, NY. When I get a moment later, I will send you my readings to compare. I would suggest that the reading you are getting on 99s TPN 8 is Watertown,NY on beam B02, not Salisbury on beam B03. B02 should be much stronger at your location.
     
  18. Jun 21, 2015 #18 of 120
    mexican-bum

    mexican-bum "Jack Of All Trades, Master Of Some"

    841
    37
    Feb 25, 2006
    I am near tulsa oklahoma, here are my readings. My locals come off D11 TP 21 and 22 but have very strong signal also on 99s TP 1, seems like I don't remember that before....
     

    Attached Files:

  19. Jun 21, 2015 #19 of 120
    tomspeer46

    tomspeer46 Legend

    692
    84
    Nov 17, 2011
    Eastern NC...
    That is a big change. Last week, the only two TIDs on TP1 in the country were a long way from you. My guess is that they have fired up TID 0, transponder B18-1 on D14, which is aimed right at you.
     
  20. Jun 22, 2015 #20 of 120
    doctor j

    doctor j Hall Of Fame DBSTalk Club

    1,774
    64
    Jun 14, 2006
    Birmingham, Al.
    This made me check.
    Final report pending but I believe SW 2 is cleared of all LIL channels

    Doctor j
     

Share This Page

spam firewall