Ciel 2 Tracking

[JohnH]

Now about 80 kilometers higher and slowed down. 129.03 approx.

CIEL-2
1 33453U 08063A   09027.70000000  .00000014  00000-0  00000+0 0   759
2 33453 000.0500 208.8710 0009758 268.3460 132.6310 01.00685362   501

 

[JohnL]

Wait, 128.99, stop, stop, STOP!!!!!!!!!!

"Whoooa Dragon Whoooaa, When i say whoooa I MEAN Whooa, Dragons iss so stuupid", Yosemite Sam

John

 

[JohnL]

Is there some information about which transponders they will use for CONUS beam, and if those are going to be in HD or SD?

Asterix,

Ciel_2 can only use transponders 1-16 in Conus mode, and 16-32 in Spotbeam mode. 129 will only be used for HD in Conus mode. Dish could use some of the spotbeams for local into local SD, but I doubt much in any SD will be loaded onto Ciel_2

John

 

[HDRoberts]

Asterix,

Ciel_2 can only use transponders 1-16 in Conus mode, and 16-32 in Spotbeam mode. 129 will only be used for HD in Conus mode. Dish could use some of the spotbeams for local into local SD, but I doubt much in any SD will be loaded onto Ciel_2

John

As in my post, other way around. 1-17 spot, 17-32 CONUS (17 switchable)

 

[jacmyoung]

As in my post, other way around. 1-17 spot, 17-32 CONUS (17 switchable)

If so then maybe if we can see the signal strength go up much higher on 17-32 it maybe an indication the new bird is alive?

 

[HDRoberts]

If so then maybe if we can see the signal strength go up much higher on 17-32 it maybe an indication the new bird is alive?

Yes. I also earlier posted the dead E5 TPs. If signal shows up there, regardless of strength, we know it's Ciel-2.

 

[theoak]

Now about 80 kilometers higher and slowed down. 129.03 approx.

CIEL-2
1 33453U 08063A   09027.70000000  .00000014  00000-0  00000+0 0   759
2 33453 000.0500 208.8710 0009758 268.3460 132.6310 01.00685362   501

Where did you get the new TLE?

 

[nelson61]

Now about 80 kilometers higher and slowed down. 129.03 approx.

CIEL-2
1 33453U 08063A   09027.70000000  .00000014  00000-0  00000+0 0   759
2 33453 000.0500 208.8710 0009758 268.3460 132.6310 01.00685362   501

That's about 11 AM Central Time

The Apogee/Perigee spread has jumped from a few km to 80 km. This TLE was probably taken during the powered movement.

 

[navychop]

February 1st is only 5 days away. They better get a move on if they want to beat the deadline for the price increase.

I don't think they do. I think they don't want to add anything till after Jan is over.

 

[theoak]

The drift rate slowed down to around 1.4 degrees per day ... so definitely some "slowing" (gaining altitude) has occurred.

 

[nelson61]

Now about 80 kilometers higher and slowed down. 129.03 approx.

CIEL-2
1 33453U 08063A   09027.70000000  .00000014  00000-0  00000+0 0   759
2 33453 000.0500 208.8710 0009758 268.3460 132.6310 01.00685362   501

Perigee/Apogee of 35630/35712


For Reference:

Echostar 5 is parked at 128.77W with Perigee/Apogee of 35774/35797

 

[kstuart]

Asterix,

Ciel_2 can only use transponders 1-16 in Conus mode, and 16-32 in Spotbeam mode. 129 will only be used for HD in Conus mode. Dish could use some of the spotbeams for local into local SD, but I doubt much in any SD will be loaded onto Ciel_2

Actually, plenty of SD has to move from EchoStar 5 to Ciel-2. There are roughly about a dozen SD local markets on 129, like Dayton, Ohio.

There are also FCC-mandated public interest channels that are CONUS and SD.

 

[M Sparks]

Won't they have to do a software update anyway? I know on the Point Dish screen, you can't tune into those dead transponders..it just skips them.

 

[RandallA]

Won't they have to do a software update anyway? I know on the Point Dish screen, you can't tune into those dead transponders..it just skips them.

I think they already updated the tables, they just need to turn them on. No need to do a software update.

 

[M Sparks]

I'm guessing they won't meet the 2/1 deadline for the price increase...

I still don't get why people keep saying this. February bills are already out.

I can't check mine right now, because I get the "Unable to logon to system due to technical difficulties. Please try again." 95% of the time. But I did look at it a week ago, and there was no increase.

 

[digiblur]

Won't they have to do a software update anyway? I know on the Point Dish screen, you can't tune into those dead transponders..it just skips them.

No, the transponder list in your point dish screen is driven by the uplink tables. So if a TP is removed it will be removed from your point dish screen. Even though it might still be transmitting but with no video streams. There used to be a few of these around between 61.5 and 129. Not sure if there are now.

 

[nelson61]

Don't know when it is going to happen but Digiblur and the upload gang better have a few bottles of glucosamine available and start some finger limbering exercises. Going to be a bunch of ediiting going on.

 

[M Sparks]

I think they already updated the tables, they just need to turn them on. No need to do a software update.

Hmmm. I guess I always assumed it was "wired" into the software. But now I see that if I try to "point" at 148 or 121, it lets me run through all 32 transponders, since I'm not getting a signal from them.

EDIT thanks to Digiblur too. Learn something new every day.

 

[jacmyoung]

Late last night I tried to check the signal strength on the 129, all 32 of them had signals in green, identified as "129 West", none were "dead".

Signal strength however varied. Some in the low 30's others as high as 50.

BTW I used my 625.

 

[Bradtothebone]

Perigee/Apogee of 35630/35712


For Reference:

Echostar 5 is parked at 128.77W with Perigee/Apogee of 35774/35797

To raise a circular orbit, wouldn't you have to make one burn at perigee (to raise the apogee) and then another 12 hours later (at apogee) to raise the perigee?

In reality, this may be a series of smaller burns, but I think you save the most fuel by making them at apogee/perigee. Please correct me if I'm wrong.

Brad