Ciel-2 Signal Monitoring

Toggle sidebar
RandallA said:
Thanks, that's what I thought. If we compare the signal strengths to E11 (spotbeams) for example, these seem kind of low still.
Click to expand...

I think you meant E10 for the beams as E11 is CONUS. You do have to remember though. Ciel-2 is handling the CONUS and spotbeams at 129. At 110, you have E10 doing all the spotbeam work with E11 doing all the CONUS work. With that said I'm impressed by the work of Ciel-2.

Smith said:
Tp2 has TID 4002, signal 58% [8 dB] on 1m dish.

Tp5 - 4205:

Tp8 4208:

Tp10 4210:

Tp13 4213:

Tp15 4215:
Click to expand...

I see someone ran into the TSReader bug again ;) Never trust the station call letters shown for HD local spotbeams unless they are the older ones in the 6xxx range. I don't think they are reusing SIDs in that range.

4002 - 2 s 17 - Reno, NV
4205 - 5 s 16 - Paradise/Redding CA
4208 - 8 s 32 - Fresno
4210 - 10 s 32 - Bakersfield
4213 - 13 s 32 - Salinas
4215 - 15 s 32 - Santa Barbara
 
California is a big state with big markets. They have to have a lot of spots to be able to carry every little station in HD. While they are only required to carry the big 4 right now, in a couple years they will have to carry every full power channel that wants carriage. In markets like LA and SF that is a ton of stations. Dish does not have another spot beam satellite for the WA in time for this deadline, they have to do it with Ciel-2.
 
Looks like tp5 returned to E5 at 3:14pm 2/11 - see that gap after 3:04pm 2/11, signal show same jitter as before Ciel-2 now.

I can see the tp5 mux with 53% SQ and 95% SS.

Getting discrepancy between NIT and PMTs and PIDs:

Network Name: EchoStar 129 West
Network ID: 4104 (0x1008)
Transport Stream ID: 405 (0x0195)
Original Network ID: 4104 (0x1008) Version: 4
Descriptor: Linkage Descriptor
Transport Stream ID: 421 (0x01a5) 129.0W 12.516 R 20000 5/6 QPSK, DVB-S
Original Network ID: 4104 (0x1008)
Service ID: 0
Linkage Type: transport stream containing complete Network/Bouquet SI
Descriptor: Network Name Descriptor
DVB-S Orbital Position: 129.0W
Frequency: 12.282 GHz
Modulation: QPSK, DVB-S
Polarity: RHCP
Symbol Rate: 20000 MSps
FEC: 5/6
Current Network: True
Descriptor: Service List Descriptor
Service: 6801 (UPSD) user defined (0x9a)

PMTs:
PAT Version Number: 2
Transport Stream ID: 405 (0x0195)
NIT: 129.0W 12.282 GHz RHCP 20000 5/6 QPSK, DVB-S

PMT PID 16 (0x0010) - Network
PMT PID 33 (0x0021) - Program 7190 KCAU
PMT PID 33 (0x0021) - Program 7191 KMEG
PMT PID 33 (0x0021) - Program 7192 KTIV
PMT PID 33 (0x0021) - Program 7193 KPTH
PMT PID 33 (0x0021) - Program 7195 KSIN
PMT PID 33 (0x0021) - Program 7196 KXNE
PMT PID 33 (0x0021) - Program 7425 WDTN
PMT PID 33 (0x0021) - Program 7426 WHIO
PMT PID 33 (0x0021) - Program 7427 WKEF
PMT PID 33 (0x0021) - Program 7428 WRGT
PMT PID 33 (0x0021) - Program 7429 WBDT
PMT PID 33 (0x0021) - Program 7431 WPTD


PIDs - practically null packets [92+%] and System tables.

Scan taken between 7:43am 2/11 and 8:05am 2/12.
 

Attachments

  • 129W_24hrs_2-12-9.jpg
    129W_24hrs_2-12-9.jpg
    137.6 KB · Views: 157
Just check on that picture after that spot at 3:04pm, then look for same tp5 on old scans. By other reports it looks as a CONUS tpn with old parameters now.
 
I am all set to test the Hawaii spotbeam with a 24" dish/dp lnb/dpp44/722 setup. I currently have have a 30" on 119 and 39" on 110.

Am I correct in thinking that the 24" dish won't be able to see anything at 129 until channels are first uplinked and then turned on?

Ready, waiting and hungry :hungry:
 
I lost four days BLSA's graph due a storm - power outage happened yesterday.
Got only last 8 hours: 11:43pm 2/17 to 7:31am 2/18; last night that tp5 [TID 405] did lost signal for 5 second after 12:20:53 am and still running on E5.
 

Attachments

  • 129W_24hrs_2-17-9.jpg
    129W_24hrs_2-17-9.jpg
    45.2 KB · Views: 137
I wonder why they are keeping E5 active. I wonder if some channels need to go to a different uplink center or something, and they are hold E5 there with them until the fiber link is done..

Edit: well after looking at the list it looks like there are not any channels on TP5 available to subs. A mystery why they are keeping E5 there unless they want more overlap and testing on C2...
 
Ciel-2 spot beams

They're really moving these around, pinpointing them on their intended areas. The 50 beams are MUCH tighter than those from EchoStar 10. Check the satbeams site to see what their intended coverage areas are.
In Northern California (Sierra foothills), I'm getting 5 spotbeams (2, 8, 10, 14 and 16), but 2 (8 and 10) are very weak. My son in the Bay Area sees 5 (2, 8, 10, 13 and 15). All are strong. We are only 150 miles apart.
Transponders 5, 7 and 9 do not show up on either of our receivers as spotbeams. Can anyone confirm that they are still coming from E5?
 
MikeD-C05 said:
I thought that DISH wanted to move this Echostar 5 sat to 148 to keep the sat slot there. Didn't they ask to move it back last month?
Click to expand...

Not really "back" since it has never been there, but yes they did ask to move it to 148w. IIRC permission was granted with the stipulation that a 4 day notice be given prior to discontinuing service at 129w. That may have been business days. Holiday and what have you the time may be about up.
 
RandallA said:
E5 doesn't have Spotbeams. I haven't checked lately so I'll check those 5 that your son can get in the Bay Area.
Click to expand...

Correct. Since the menu doesn't show them as spotbeams but identifies Tp 5, 7 and 9 as belonging to 129, that's what makes me think that they are still coming from E5.
 

Users Who Are Viewing This Thread (Total: 0, Members: 0, Guests: 0)

Who Read This Thread (Total Members: 1)

Share this page

Share this page
Top