Welcome to DBSTalk

Welcome to DBSTalk. Our community covers all aspects of video delivery solutions including: Direct Broadcast Satellite (DBS), Cable Television, and Internet Protocol Television (IPTV). We also have forums to discuss popular television programs, home theater equipment, and internet streaming service providers. Members of our community include experts who can help you solve technical problems, industry professionals, company representatives, and novices who are here to learn.

Like most online communities you must register to view or post in our community. Sign-up is a free and simple process that requires minimal information. Be a part of our community by signing in or creating an account. The Digital Bit Stream starts here!

Any chance to compare with gct's table and present a difference only ?

Actually its somewhat confusing P. Smith;

The JSON responses over IP outlined in the SHEF document MD-0359 (latest edition I have) return data that is different in a number of respects from the hex string returns from the MD-0058 STB functionality document gct's data is based upon.

which data are you talking about? the VPID/APIDs? I just gave the decimal version whereas it looks like the spreadsheet carries hex values

Oh! ... duh. :imwith:

So the SHEF JSON returns do give the same data format as the MD-0058. Good to see and makes a lot more sense. Sorry I didn't notice those were simply the decimal equivalents of the Hex data you converted the various values to.

I just realized what I can't find out is which satellite/transponder a given NET/TID is on...

You know gct use to list the various Network TID ranges used by the specific host satellite(s) of a channel on the decoder map of the his spreadsheet, but stop publishing them a good while ago.

Looks to me like no one takes care of that site. I think they should import the relevant information to this site and shut that site down. I see tons of spam, and old posts from years ago. Doesn't look very active or current.

Looks to me like no one takes care of that site. I think they should import the relevant information to this site and shut that site down. I see tons of spam, and old posts from years ago. Doesn't look very active or current.

Some people think that SPAM is delicious.

"He that is good for making excuses is seldom good for anything else."

My LIL channels (network 591) are shown as being on 103S, TPN 6. The signal strength display on my receiver shows N/A for that Tpn. Is there an error in the transponder map, or an error in the receiver software?

My LIL channels (network 591) are shown as being on 103S, TPN 6. The signal strength display on my receiver shows N/A for that Tpn. Is there an error in the transponder map, or an error in the receiver software?

tomspeer,

Please try this procedure, detailed in a post earlier in this very same thread.

That's why we still need the "rules" for the LiLs, complex and "ugly" as they may be, to trace the TIDs given in the hex string for the spotbeam locals to the actual host satellite(s) and transponder.

Unfortunately, you are mistaken about "actual". All the tpn## what you see on your STB's screen are fictitious numbers [1-32].They are created by FW routine from TID/Net numbers just for easy communication between customers and CSR.

Unfortunately, you are mistaken about "actual". All the tpn## what you see on your STB's screen are fictitious numbers [1-32].They are created by FW routine from TID/Net numbers just for easy communication between customers and CSR.

Unfortunately, you are mistaken about "actual". All the tpn## what you see on your STB's screen are fictitious numbers [1-32].They are created by FW routine from TID/Net numbers just for easy communication between customers and CSR.

In DTV system tables and SW, only Net# and TID# are matter.

As to the rules: see camera3 site.

P Smith: Thank you for that. The thing I am trying to get to is: When I want to see how good my signals are for my locals, I look at gct's transponder map to see where they are, then check the signal level screen on the set-top box. I can see the actual signal level from the SHEF command, and it corresponds to the values I see on transponders 4, 21, and 22 of satellite 103S. jamieh and I, and others of us in the Greenville, NC Market see transponder 6 in the transponder map spreadsheet, and on the STB, it shows up as N/A. The SHEF command responses for local channels 7,9,12,14 and 15, give the Transponder ID as 0x26 (38 decimal), on Net 14 (0x0e).

So I am suggesting at this point that there is something astray in those LIL rules.