Echostar 16 at 61.5W

[whatchel1]

Yep, it's switch bleed if it isn't saying locked with the name.

-- "Sensorly or it didn't happen!"

Any rough ETA of when we will have tp to spotbeam info? Like I getting a whopping signal level off tp 25 of 3 to 5 just curious as to where it is really pointed.

 

[Jim5506]

I'm getting locks on 11 spotbeam TP's on 61.5:

TP 18 - Locked - Echostar 61.5 West - 72
TP 19 - Locked - Echostar 61.5 West - 64
TP 20 - Locked - Echostar 61.5 West - 79
TP 21 - Locked - Echostar 61.5 West - 71
TP 22 - Locked - Echostar 61.5 West - 42
TP 24 - Locked - Echostar 61.5 West - 43
TP 27 - Locked - Echostar 61.5 West - 36
TP 28 - Locked - Name not Acquired! - 64
TP 29 - Locked - Echostar 61.5 West - 35
TP 30 - Locked - Echostar 61.5 West - 67
TP 32 - Locked - Echostar 61.5 West - 28

18,19,20 21 and 22 take almost a minute to finally lock and display the satellite, but they do finally lock with the satellite name.

 

[whatchel1]

This is w/ my 1m
18- 78
19- 70
20-84
21-80
22-50
23- 1 (I've seen a whopping 4 on it)
24- 59
25- 9
26- 0
27- 52
28- 69 (name not acquired)
29- 45
30- 75
31- 0
32- 36
The 1 & "name not acquired" don't switch to spot. It seems like they all take forever to lock. Much slower than other sats.

 

[dare2be]

Here's what I got in my corner of the country:

18 - 48 (name not acquired)
19 - 0
20 - 36 (name not acquired)
21 - 0
22 - 36 (spotbeam)
23 - 0
24 - 46 (spotbeam)
25 - 0
26 - 8 (name not acquired) (spotbeam)
27 - 0
28 - 14 (spotbeam)
29 - 0
30 - 36 (name not acquired)
31 - 0
32 - 41 (spotbeam)

Locking took well over a minute for each one, and I waited 3 minutes on the ones that had 0 signal. I then went back to 18 because I couldn't remember if I had a spotbeam the first time, and I couldn't get a signal on 18 even after waiting for more than 3 minutes.

 

[nelson61]

Any rough ETA of when we will have tp to spotbeam info? Like I getting a whopping signal level off tp 25 of 3 to 5 just curious as to where it is really pointed.

Don't know where you are but here is the reuse table for TP 25. While you are waiting for the uplink and List update, you can look at the spots on the Satmaps to see which spots in your area have 25.

SP03	12573.92	R	25
SP06	12573.92	R	25
SP07	12573.92	R	25
SP10	12573.92	R	25
SP12	12573.92	R	25
SP14	12573.92	R	25
SP16	12573.92	R	25
SP17	12573.92	R	25
SP20	12573.92	R	25
SP23	12573.92	R	25
SP25	12573.92	R	25
SP70	12573.92	R	25

 

[dbs2000]

I double check and strangely this is what I get tp 18 Locked name not acquired signal 55.
I really dont know what the receiver is seeing.

You are getting spillover from another orbital slot.

 

[dbs2000]

Don't know where you are but here is the reuse table for TP 25. While you are waiting for the uplink and List update, you can look at the spots on the Satmaps to see which spots in your area have 25.

SP03	12573.92	R	25
SP06	12573.92	R	25
SP07	12573.92	R	25
SP10	12573.92	R	25
SP12	12573.92	R	25
SP14	12573.92	R	25
SP16	12573.92	R	25
SP17	12573.92	R	25
SP20	12573.92	R	25
SP23	12573.92	R	25
SP25	12573.92	R	25
SP70	12573.92	R	25

Does that mean that sweet SP70 is on TP 25?????

 

[whatchel1]

You are getting spillover from another orbital slot.

It isn't spill over from another slot. He is getting it threw his switch.

 

[digiblur]

Any rough ETA of when we will have tp to spotbeam info? Like I getting a whopping signal level off tp 25 of 3 to 5 just curious as to where it is really pointed.

No ETA, been gone all weekend. Anyone else is more than welcome to help reverse engineer this stuff though.

Sent from my little Note2

 

[whatchel1]

Does that mean that sweet SP70 is on TP 25?????

It was mostly meant for me. There are 71 spot beams on E-16 of which we are talking about tp 25. In this one he is talking about these different sets of spotbeams. We have talked via PM since this reply. This link should be Sat Maps sp 71. You can look at all the sp on Sat Maps. http://satmaps.satelliteguys.us/home/echostar-16-61-5w-sp71-san-francisco SP 70 is for your area. http://satmaps.satelliteguys.us/home/echostar-16-61-5w-sp70-puerto-rico

 

[Zaxcom]

When does the spotbeam for Charlotte, NC get switched on?

 

[Dah-Henny]

When does the spotbeam for Charlotte, NC get switched on?

Here:

These for the 24th

Atlanta- GA
Baltimore- MD
Buffalo- NY
Charlotte- NC
Chattanooga- TN
Cleveland, OH
Detroit- MI
Flint/Saginaw- MI
Grand Rapids- MI
Green Bay- WI
Greensboro- NC
Jefferson City - Columbia
Knoxville- TN
Lansing- MI
Lincoln, NE
Norfolk- VA
Philadelphia- PA
Pittsburgh- PA
Richmond- VA
Rochester- NY
Savannah- GA
South Bend- IN
St. Louis- MO
Tampa- FL
Traverse City- MI

 

[LuisEduardoP]

I wonder why Cuba has two spotbeams? Are these for future use or is Dishing beaming signals into Cuba now?

Same case for México, ES 16 has two spotbeams: SP21 & 26.

 

[Chris36]

Did more locals get move last night to E 16 I thought it was the 22nd and 24 this week?

 

[HDRoberts]

Hmm, don't see an uplink report. Either a problem, delay, or Scott needs to kick the uplink PC again.

 

[dare2be]

I'm rooting for problem

 

[nelson61]

Did more locals get move last night to E 16 I thought it was the 22nd and 24 this week?

They had planned 21st and 23rd but no changes occurred on 21st. Might see it all tonight or might be still tuning up their previous changes.

 

[TheKrell]

They had planned 21st and 23rd but no changes occurred on 21st. Might see it all tonight or might be still tuning up their previous changes.

Or, they might have done it surreptitiously during the night by keeping the same TIDs on E16. Who would know?

 

[dare2be]

1/24 and my conus locals are still active this morning. I'm sure now that I just jinxed it.

 

[RONZ]

Traverse City still on transponder 17