What signals can you "see" at 61.5?

[Smith P.]

Got that strange peak type of signal on tp7 starting 11:36am PDT.

Could someone with analog FTA receiver check it ?

 

[Smith P.]

OK

Sorry guys, I'm very skeptical - only two persons one from IL other from SC - nobody else and that is huge distance for one SB.

We need to have our resident on East Coast with Spectrum Analyzer !

 

[brownover]

Sorry guys, I'm very skeptical - only two persons one from IL other from SC - nobody else and that is huge distance for one SB.

We need to have our resident on East Coast with Spectrum Analyzer !

Ok, P Smith. I hooked my receiver straight to the 61.5 satellite. Here are results: Locked Echostar 61.5 tp 3 changed to spotbeam, signal 92. A lock is a lock is a lock. A green line is a green line is a green line. The receiver knows what it is seeing. And I live in NC, not SC almost in the heart of spotbeam 5.

 

[Smith P.]

That's third location, but again SA spectrogram would show real signal - a receiver could adjust frequency to next tp.
Or if someone with Sky-Walker USB card or DVBTech device could lock to the tp7 and using TSReader will post screen-shot.

 

[charlesrshell]

Ok, P Smith. I hooked my receiver straight to the 61.5 satellite. Here are results: Locked Echostar 61.5 tp 3 changed to spotbeam, signal 92. A lock is a lock is a lock. A green line is a green line is a green line. The receiver knows what it is seeing. And I live in NC, not SC almost in the heart of spotbeam 5.

How do you tell it changed to spotbeam?

 

[brownover]

How do you tell it changed to spotbeam?

When you change transponders with your remote, the word transponder will change to spotbeam almost immediately after the signal comes up.

 

[charlesrshell]

When you change transponders with your remote, the word transponder will change to spotbeam almost immediately after the signal comes up.

OK, thanks. Never have seen that before when check the TPs in Point Dish. Thanks again.

 

[brownover]

That's third location, but again SA spectrogram would show real signal - a receiver could adjust frequency to next tp.
Or if someone with Sky-Walker USB card or DVBTech device could lock to the tp7 and using TSReader will post screen-shot.

I have no signal from tp 4 and never have. tp 2 remains at the same strength it has always been.

 

[brownover]

OK, thanks. Never have seen that before when check the TPs in Point Dish. Thanks again.

If your locals are on a spotbeam and not conus, tune in one of your locals and then do point dish and you will see it.

 

[charlesrshell]

If your locals are on a spotbeam and not conus, tune in one of your locals and then do point dish and you will see it.

OK, thanks again. I tuned in a HD local and I guess it must be conus. It says TP11 on bird 118, Locked - EchoStar 118 West.

 

[charlesrshell]

If your locals are on a spotbeam and not conus, tune in one of your locals and then do point dish and you will see it.

Just tuned in a SD local and it is a Spotbeam 29 on bird 110.

 

[Hemi 6.1]

Just tuned in a SD local and it is a Spotbeam 29 on bird 110.

Whats on the 118 satellite? I see it listed in your signature

 

[charlesrshell]

Whats on the 118 satellite? I see it listed in your signature

As far as I know 118 has HD locals from St. Louis area.

 

[RandallA]

Whats on the 118 satellite? I see it listed in your signature

Internationals and some HD locals.

 

[TheKrell]

only two persons one from IL other from SC - nobody else and that is huge distance for one SB.

Huh? There are at least 3 of us. ncted and brownover, both (?) from NC not SC. And I'm in northern VA. Who is this person in IL? Agree that's a stretch for one spot. But us 3 are close enough IMHO. Can my Twinhan 1025 be used as a spectrum analyzer?

 

[ncted]

Huh? There are at least 3 of us. ncted and brownover, both (?) from NC not SC. And I'm in northern VA. Who is this person in IL? Agree that's a stretch for one spot. But us 3 are close enough IMHO. Can my Twinhan 1025 be used as a spectrum analyzer?

I am in NC. I had to mow the lawn when I got home, so I haven't been able to check the spotbeam again. Watching Charlie Chat now. Will post the screenshot when it is over.

Ted

 

[ncted]

Got bored with chat. See attached screenshot. Signal strength is lower than yesterday. Perhaps it is cross-talk afterall?

Ted

 

[TheKrell]

Signal strength is lower than yesterday. Perhaps it is cross-talk afterall?

I'm getting good signal strength on transponder 1 as well, and it clearly states "wrong satellite Echo 110" or something like that. Now that's crosstalk. I also get a highly variable signal stength on 3. I see it anywhere from 30 to 60, new scale.

When we get a lock on 61.5, I cannot imagine how it's crosstalk from another satellite. Now I suppose it could be crosstalk from a different transponder on 61.5, which also explains why brownover could still see "spotbeam" when directly connected. But then why don't we see "spotbeam" on any other transponders?

I think we've got a spot illuminating our territory, and the others are just green with envy.

 

[HokieEngineer]

Heres what can be seen in the Mid Atlantic, USA... Signal on TP1 and TP3 are new (I've been out of town for a week).

The PAT on TP1 is wierd, since it is a copy of a PAT from 110w:

PAT Version Number: 1
Transport Stream ID: 2542 (0x09ee)
NIT: 110.0W 12.384 GHz LHCP 21500 2/3 8PSK (DVB-DSNG/Turbo/DVB-S2), DVB-S

PMT PID 16 (0x0010) - Network 
PMT PID 33 (0x0021) - Program 6401 WPLG
PMT PID 33 (0x0021) - Program 6402 WFOR
PMT PID 33 (0x0021) - Program 6403 WTVJ
PMT PID 33 (0x0021) - Program 6404 WSVN

Its definitely on 61.5, confirmed with the spec analyzer. Not on 110w at all. In fact that spot on 110 is no where near my location. I think this is the reason people are seeing wierd things on their dish signal check screens. They have an incorrect table on 61.5.

PAT from TP3:

PAT Version Number: 2
Transport Stream ID: 1503 (0x05df)
NIT: 61.5W 12.253 GHz RHCP 21500 2/3 8PSK (DVB-DSNG/Turbo/DVB-S2), DVB-S

PMT PID 16 (0x0010) - Network 
PMT PID 33 (0x0021) - Program 5050 WTVD
PMT PID 33 (0x0021) - Program 5051 WRAL
PMT PID 33 (0x0021) - Program 5052 WNCN
PMT PID 33 (0x0021) - Program 5053 WRAZ

PAT from TP5: (Notice it is not a spotbeam TID)

PAT Version Number: 1
Transport Stream ID: 105 (0x0069)
NIT: 61.5W 12.282 GHz RHCP 21500 2/3 8PSK (DVB-DSNG/Turbo/DVB-S2), DVB-S

PMT PID 16 (0x0010) - Network 
PMT PID 33 (0x0021) - Program 6359 WJLA
PMT PID 33 (0x0021) - Program 6360 WUSA
PMT PID 33 (0x0021) - Program 6361 WRC
PMT PID 33 (0x0021) - Program 6362 WTTG

 

[necochino]

Is it possible that we are getting different reads for that wrong satellite on TP1 depending on software version? I have a 722 with 449 that shows the "110 wrong sat". I have two 622s with 448 that don't.