No word yet on T19V health - should have had something by now ? I may have missed it - I just don't see any news on health
Quote from: soltasto on 07/22/2018 02:48 pmQuote from: eriblo on 07/22/2018 02:38 pmQuote from: soltasto on 07/22/2018 01:32 pm2018-059A/43562 (243 km x 17863 km x 27.00°) has a delta v to GTO of 2064.5751 m/s or it is in GTO-20652018-059B/43563 (242 km x 17860 km x 27.00°) has a delta v to GTO of 2064.7341 m/s or it is in GTO-2065according to my C/C++ program based on this.What parameters did you use? I get 2277 m/s using that approach (which seems to agree with this online implementation)...? BTW, doing a third of a degree of the inclination change in the first apogee raising burn saves ~4 m/s.I used the TLE data along with the program written by LouScheffer. I literally "translated" that program.This is the program, it should compile with GCC using C++11:...Unfortunately, that program is only correct for synchronous or greater. It does not account for the perigee burn to raise the apogee, gets the wrong sign for circularization if the apogee is below GEO, and will do the inclination reduction at the wrong burn if sub-sync. So the numbers from this program will be wrong for the sub-sync case, which this is. Sorry, it should check for that and either do it right, or at least give a message, rather than silently doing it wrong.
Quote from: eriblo on 07/22/2018 02:38 pmQuote from: soltasto on 07/22/2018 01:32 pm2018-059A/43562 (243 km x 17863 km x 27.00°) has a delta v to GTO of 2064.5751 m/s or it is in GTO-20652018-059B/43563 (242 km x 17860 km x 27.00°) has a delta v to GTO of 2064.7341 m/s or it is in GTO-2065according to my C/C++ program based on this.What parameters did you use? I get 2277 m/s using that approach (which seems to agree with this online implementation)...? BTW, doing a third of a degree of the inclination change in the first apogee raising burn saves ~4 m/s.I used the TLE data along with the program written by LouScheffer. I literally "translated" that program.This is the program, it should compile with GCC using C++11:...
Quote from: soltasto on 07/22/2018 01:32 pm2018-059A/43562 (243 km x 17863 km x 27.00°) has a delta v to GTO of 2064.5751 m/s or it is in GTO-20652018-059B/43563 (242 km x 17860 km x 27.00°) has a delta v to GTO of 2064.7341 m/s or it is in GTO-2065according to my C/C++ program based on this.What parameters did you use? I get 2277 m/s using that approach (which seems to agree with this online implementation)...? BTW, doing a third of a degree of the inclination change in the first apogee raising burn saves ~4 m/s.
2018-059A/43562 (243 km x 17863 km x 27.00°) has a delta v to GTO of 2064.5751 m/s or it is in GTO-20652018-059B/43563 (242 km x 17860 km x 27.00°) has a delta v to GTO of 2064.7341 m/s or it is in GTO-2065according to my C/C++ program based on this.
Quote from: LouScheffer on 07/22/2018 03:30 pmQuote from: soltasto on 07/22/2018 02:48 pmQuote from: eriblo on 07/22/2018 02:38 pmQuote from: soltasto on 07/22/2018 01:32 pm2018-059A/43562 (243 km x 17863 km x 27.00°) has a delta v to GTO of 2064.5751 m/s or it is in GTO-20652018-059B/43563 (242 km x 17860 km x 27.00°) has a delta v to GTO of 2064.7341 m/s or it is in GTO-2065according to my C/C++ program based on this.What parameters did you use? I get 2277 m/s using that approach (which seems to agree with this online implementation)...? BTW, doing a third of a degree of the inclination change in the first apogee raising burn saves ~4 m/s.I used the TLE data along with the program written by LouScheffer. I literally "translated" that program.This is the program, it should compile with GCC using C++11:...Unfortunately, that program is only correct for synchronous or greater. It does not account for the perigee burn to raise the apogee, gets the wrong sign for circularization if the apogee is below GEO, and will do the inclination reduction at the wrong burn if sub-sync. So the numbers from this program will be wrong for the sub-sync case, which this is. Sorry, it should check for that and either do it right, or at least give a message, rather than silently doing it wrong.Running solasto's implementation doesn't give any errors but I think it spits out a perigee speed that is lower than the apogee speed after the first burn and a corresponding negative delta v. This could be taken as a warning
Since TerreStar 1 was the previous record holder for largest commercial spacecraft to GEO and launched by Ariane Space to a geosynchronous transfer orbit, I am curious how the delta v compares to Telstar 19. Does anyone know the delta v for TerreStar 1?
Quote from: LouScheffer on 07/22/2018 06:08 amFirst stage cutoff was at 8170 km/hr = 2270 m/s.This is exactly what we've seen on previous GTO with recovery missions. So no big performance boost for block 5.You don't consider the fact that they did this with a payload in excess of SEVEN TONS, as significant?
First stage cutoff was at 8170 km/hr = 2270 m/s.This is exactly what we've seen on previous GTO with recovery missions. So no big performance boost for block 5.
GTO-2275 @7075kg ...
I decided to rewrite the code from scratch to fix the issue and to write it in good C++, but I decided to also add a feature that finds the most efficient way to GEO. So now it will also scrub some of the inclination at perigee, just as much to reduce the total delta v budget.Here is the github repository: https://github.com/AleLovesio/delta-v-to-GTO (The source files are in the source folder)I also uploaded the files here as txts since the cpp and h extensions are not allowed even if in the end they are just text files.
Quote from: SpaceGoo on 07/22/2018 04:26 pmSince TerreStar 1 was the previous record holder for largest commercial spacecraft to GEO and launched by Ariane Space to a geosynchronous transfer orbit, I am curious how the delta v compares to Telstar 19. Does anyone know the delta v for TerreStar 1?Terrestar 1 was a standard GTO from Kourou, so GEO-1500 m/s.
Quote from: Sam Ho on 07/22/2018 05:30 pmQuote from: SpaceGoo on 07/22/2018 04:26 pmSince TerreStar 1 was the previous record holder for largest commercial spacecraft to GEO and launched by Ariane Space to a geosynchronous transfer orbit, I am curious how the delta v compares to Telstar 19. Does anyone know the delta v for TerreStar 1?Terrestar 1 was a standard GTO from Kourou, so GEO-1500 m/s.Thanks. I thought it would be interesting to compare Terrestar 1 to Telstar 19 since they have equivalent mass and SpaceX landed the first stage. A recurring argument recently is that SpaceX is wasting fuel on reuse versus getting the satellite at or nearer to GEO.
A recurring argument recently is that SpaceX is wasting fuel on reuse versus getting the satellite at or nearer to GEO.
Quote from: SpaceGoo on 07/23/2018 02:35 am A recurring argument recently is that SpaceX is wasting fuel on reuse versus getting the satellite at or nearer to GEO.Fuel is cheap. Spacecraft are expensive.
Quote from: soltasto on 07/22/2018 09:03 pmI decided to rewrite the code from scratch to fix the issue and to write it in good C++, but I decided to also add a feature that finds the most efficient way to GEO. So now it will also scrub some of the inclination at perigee, just as much to reduce the total delta v budget.Here is the github repository: https://github.com/AleLovesio/delta-v-to-GTO (The source files are in the source folder)I also uploaded the files here as txts since the cpp and h extensions are not allowed even if in the end they are just text files.Could you compare with JCSAT-16? It's a close match telemetry-wise, but the final orbit from F9 was 184 km × 35,912 km × 20.85°.
Quote from: SpaceGoo on 07/23/2018 02:35 amA recurring argument recently is that SpaceX is wasting fuel on reuse versus getting the satellite at or nearer to GEO.Just a note on wasting fuel: if the satellite bus is large enough to hold a sizeable amount of fuel for orbit raising (understood the be about 3mt for Telstar 19V), it is way more efficient due to less overall mass to let the satellite raise itself to the final orbit than have the second stage do the job partially. It is just a tradeoff between the reduced cost of a reusable launch into a low-energy orbit or paying more for an expendable launch and gaining some additional years of in-orbit operations.