OHM Falcon9R

[OrbitHangar]

Author: brianj

The SpaceX "Falcon9 V1.1 Reusable" launcher. Historical and test launch scenarios.
Launcher features optional Ascent-to-Orbit autopilot and 1st Stage Auto-Flyback-EDL, etc.
Payload "attachment" by editing scenario, or in-sim by payload name input.
Optional Star48BV kick motor. No Fairing, Dragon Adaptor or Custom Adaptor Mesh options. Also includes SLC40 and SLC4E launchpads, Recovery Barge and Landing Pad. Installation instructions and operation notes in Doc/Falcon9R/ folder.

UPDATE: 03 March 2015 Added Grid-Fins to 1st stage, adjusted landing autopilot, misc.cosmetic changes.

UPDATE: 12 June 2015 Fixed "payload mass not added when adding payload in-sim" bug.

REQUIREMENTS:
CRS3 / CRS4 / CRS5 Launch Scenarios require:
"Dragon Update" by Donamy
http: //www.orbithangar.com/searchid.php?ID=5775

Special thanks to Iron Rain, Glider, Loru, Donamy, Fred18, Barry



DOWNLOAD

 

[Kyle]

Looks solid giving it a test flight! I'll try it out further after the Orbcomm launch today.

 

[BrianJ]

Thanks Kyle.
The visuals on this one aren't as cool as Glider's, but I think the performance is closer to the current V1.1 specs.

I'd like to have some more info about the 1st stage flyback burn sequence.The autopilot puts it on a minimum energy trajectory to the target, but it hits the atmosphere pretty hard at 25km alt. on the way down. I'm wondering if there is a braking burn before that? What is the max deceleration the 1st stage can stand? Also, is there any lateral/horizontal targeting during the final powered descent? Hmm. Plenty of ideas to try out on this one.

Here's a pic from todays OG-2 launch

 

[Pipcard]

So much accuracy! Now that this has been proven, this may not be so far-fetched...

 

[Kyle]

As promised, I gave this a thorough (as possible) run down.

+The autopilot is excellent, even better than the last one.

+Enjoying the new detail to the RCS jets on the 1st stage, definitely adds to the realism.

+very stable second stage with a very accurate autopilot. CRS-3's orbital altitude, for example, is virtually dead on at 313x333 kilometers after engine cutoff and separation.

+descent stage of the flight is very solid, AP holds it steady right until touchdown.

-seems to be a conflict between with the CRS-3 payload, no CTD but the attachment points are off for the payloads.

Everything looks solid from my end. Would love to see a Falcon Heavy variant of this one day!

 

[BrianJ]

-seems to be a conflict between with the CRS-3 payload, no CTD but the attachment points are off for the payloads.

Everything looks solid from my end. Would love to see a Falcon Heavy variant of this one day!

Many thanks! I'll ask Don how to straighten out the CRS-3 attachment point.

Falcon9R Heavy is definitely on the list.

Cheers,
BrianJ

 

[Donamy]

Dowwnloading this should fix it.
[ame="http://www.orbithangar.com/searchid.php?ID=6561"]HRSFG update[/ame]

 

[rcullan]

First off, this is a FANTASTIC addon. Thanks so much Brian.

I have run into one problem, and it may be me. But I have attempted the CRS3 mission to get all the way to the ISS and I have looked through the documentation and I cannot find out how to release Dragon's docking port fairing for the CRS3 mission. The commands shown in the original documentation dosen't seem to work after the dragon 1 & 2 updates. I can get the grappling port to deploy, but not the fairing covering the ISS docking port. Any suggestions?

I love the EDL sequence on the booster stage, how did you guys come about this landing approach? It works in orbiter but I am curious as to how realistic it is. My gut tells me that going over -1000m/s VS at 25k altitude would tear apart a nearly empty booster stage.

 

[IronRain]

Just had my change to try this and again: great work Brian!
Many of my missions will get a ride atop of this beauty!

 

[Interceptor]

Great update,the landing autopilot runs very smooth,I can't wait to see future versions,thanks for making this.

 

[Donamy]

First off, this is a FANTASTIC addon. Thanks so much Brian.

I have run into one problem, and it may be me. But I have attempted the CRS3 mission to get all the way to the ISS and I have looked through the documentation and I cannot find out how to release Dragon's docking port fairing for the CRS3 mission. The commands shown in the original documentation dosen't seem to work after the dragon 1 & 2 updates. I can get the grappling port to deploy, but not the fairing covering the ISS docking port. Any suggestions?

I love the EDL sequence on the booster stage, how did you guys come about this landing approach? It works in orbiter but I am curious as to how realistic it is. My gut tells me that going over -1000m/s VS at 25k altitude would tear apart a nearly empty booster stage.

You have to focus on the Dragontrunk, then press J to jettison the nosecone and J two more times to jettison the fairings.

 

[NextBigLeap]

Im having some trouble getting the CRS-3 scenario to work, can anyone help? here is the log
**** Orbiter.log
Build Aug 30 2010 [v.100830]
Timer precision: 5.70181e-007 sec
Found 0 joystick(s)
Devices enumerated: 4
Devices accepted: 3
==> RGB Emulation
==> Direct3D HAL
==> Direct3D HAL (Intel(R) HD Graphics)
Module AtlantisConfig.dll .... [Build 100830, API 100830]
Module AtmConfig.dll ......... [Build 100830, API 100830]
Module DGConfigurator.dll .... [Build 100830, API 100830]
Module OrbiterSound.dll ...... [Build 121120, API 100830]
Module uap.dll ............... [Build 110613, API 100830]
---------------------------------------------------------------
>>> WARNING: Obsolete API function used: oapiRegisterMFDMode
At least one active module is accessing an obsolete interface function.
Addons which rely on obsolete functions may not be compatible with
future versions of Orbiter.
---------------------------------------------------------------
Module LunarTransferMFD.dll .. [Build 100621, API 100603]
Module InterMFD55.dll ........ [Build 100826, API 100704]
Module HCLV_MFD.dll .......... [Build 130722, API 100830]
Module CRT.dll ............... [Build 131123, API 100830]
Module ScnEditor.dll ......... [Build 100830, API 100830]
Module TransX.dll ............ [Build 140503, API 100830]
Module Rcontrol.dll .......... [Build 100830, API 100830]
Module GPCMFD.dll ............ [Build 111222, API 100830]
Module GPCMFD.dll ............ [Build 111222, API 100830]
Module RPOP.dll .............. [Build 111124, API 100830]
Module UnivPTG.dll ........... [Build 110305, API 100830]

**** Creating simulation session
DirectDraw interface OK
Direct3D interface OK
Graphics: Viewport: Window 1360 x 739 x 32
Graphics: Hardware T&L capability: No
Graphics: Z-buffer depth: 32 bit
Graphics: Active lights supported: -1
Loading 15382 records from star database
Module Sun.dll ............... [Build 100830, API 100830]
VSOP87(E) Sun: Precision 1e-006, Terms 554/6634
Module Mercury.dll ........... [Build 100830, API 100830]
VSOP87(B) Mercury: Precision 1e-005, Terms 167/7123
Module Venus.dll ............. [Build 100830, API 100830]
Module VenusAtm2006.dll ...... [Build 100830, API 100830]
VSOP87(B) Venus: Precision 1e-005, Terms 79/1710
Module Earth.dll ............. [Build 100830, API 100830]
Module EarthAtmJ71G.dll ...... [Build 100830, API 100830]
VSOP87(B) Earth: Precision 1e-008, Terms 2564/2564
Module Moon.dll .............. [Build 100830, API 100830]
ELP82: Precision 1e-005, Terms 116/829
Module Mars.dll .............. [Build 100830, API 100830]
Module MarsAtm2006.dll ....... [Build 100830, API 100830]
VSOP87(B) Mars: Precision 1e-005, Terms 405/6400
Module Phobos.dll ............ [Build ******, API 060425]
Module Deimos.dll ............ [Build ******, API 060425]
Module Galsat.dll ............ [Build 100217, API 100215]
Module Jupiter.dll ........... [Build 100830, API 100830]
VSOP87(B) Jupiter: Precision 1e-006, Terms 1624/3625
Module Io.dll ................ [Build 100217, API 100215]
Module Europa.dll ............ [Build 100217, API 100215]
Module Ganymede.dll .......... [Build 100217, API 100215]
Module Callisto.dll .......... [Build 100217, API 100215]
Module Satsat.dll ............ [Build 100215, API 100212]
Module Saturn.dll ............ [Build 100830, API 100830]
VSOP87(B) Saturn: Precision 1e-006, Terms 2904/6365
Module Mimas.dll ............. [Build 100215, API 100212]
SATSAT Mimas: Terms 113
Module Enceladus.dll ......... [Build 100215, API 100212]
SATSAT Enceladus: Terms 33
Module Tethys.dll ............ [Build 100215, API 100212]
SATSAT Tethys: Terms 101
Module Dione.dll ............. [Build 100215, API 100212]
SATSAT Dione: Terms 59
Module Rhea.dll .............. [Build 100215, API 100212]
SATSAT Rhea: Terms 68
Module Titan.dll ............. [Build 100215, API 100212]
SATSAT Titan: Terms 100
Module Iapetus.dll ........... [Build 100215, API 100212]
SATSAT Iapetus: Terms 605
Module Uranus.dll ............ [Build 100830, API 100830]
VSOP87(B) Uranus: Precision 1e-006, Terms 1827/5269
Module Miranda.dll ........... [Build ******, API 060425]
Module Ariel.dll ............. [Build ******, API 060425]
Module Umbriel.dll ........... [Build ******, API 060425]
Module Titania.dll ........... [Build ******, API 060425]
Module Oberon.dll ............ [Build ******, API 060425]
Module Neptune.dll ........... [Build 100830, API 100830]
VSOP87(B) Neptune: Precision 1e-006, Terms 391/2024
Finished initialising world
Module LPad.dll .............. [Build 110918, API 100830]
Module Spacecraft3.dll ....... [Build ******, API 050206]
---------------------------------------------------------------
>>> WARNING: Obsolete API function used: VESSEL::SetBankMomentScale
At least one active module is accessing an obsolete interface function.
Addons which rely on obsolete functions may not be compatible with
future versions of Orbiter.
---------------------------------------------------------------
Module f9.dll ................ [Build 140713, API 100830]

 

[BrianJ]

Hi guys,
thanks for the kind words. Always nice to know other folks find my add-on experiments interesting. I'll try and update the add-on on OH with the correct CRS-3 attachment point(thanks Don) and better documentation soon.

I love the EDL sequence on the booster stage, how did you guys come about this landing approach? It works in orbiter but I am curious as to how realistic it is. My gut tells me that going over -1000m/s VS at 25k altitude would tear apart a nearly empty booster stage.

Yes, that's my feeling too.

Not much info on the web about the Flyback-EDL sequence, so I'm making it up as I go along.

The first version simply made the flyback burn to change the horizontal velocity to intercept the target, but with the very high 1st stage Apa. (due to the steep ascent profile) the reentry velocity was even greater than it is with this version.

The current version uses a "minimum energy ballistic trajectory" to intercept the target, which is more fuel efficient and reduces the reentry load, but as you observe, the reentry is still very rough (110 m/s^2 max. deceleration).

My initial reasoning was to conserve fuel by using aerobraking as much as possible. However, I think that making an extra burn between 40-30km alt. won't cost that much more fuel, and possibly reduce the final targeting/landing burn below 15km. So I think I may try that next.

There may also be horizontal/lateral targeting component to the final landing burn, too. So I'm going to see if I can make that work. But it will be more expensive fuel wise. Possibly quite a lot more expensive if you want to hover and translate sideways.

So, plenty of ideas I can play about with. If I can get the 1st stage to land back on the pad (within a few meters), I'll be happy!

Cheers,
Brian

 

[rcullan]

Brian,
Thanks for the insight into your approach, it certainly works extremely well.

There is some information on the web about SpaceX's approach to EDL on the booster stage. From what I have read it is a three burn operation.

1st burn, quickly after stage separation to kill the stage's horizontal velocity
2nd burn, a descent rate control burn to minimize heating
3rd burn, final descent and approach

I absolutely concur with your thoughts about an intermediary burn at a mid range altitude to control the vertical descent rate. They do have a heat shield on the backside of the rocket to withstand some heating. But I have not found any data relative to this searching around.

If you decide to implement and test, please let me know. I would love to be a beta tester!

Here is where I got my info from, specifically read about the CRS3 mission here:
http://www.spacelaunchreport.com/falcon9v1-1.html

F9-9 was also the first Falcon 9 v1.1 equipped with landing legs. Plans called for the legs to be deployed shortly before the first stage reached the Atlantic Ocean during a second reentry test. After stage separation, the first stage would turn around and three of the first stage Merlin 1D engines would reignited to eliminate most of the stage horizontal velocity, allowing the stage to fall nearly straight down through the atmosphere at low enough velocity to survive reentry. SpaceX called this a "reentry burn". As the stage approached the Atlantic Ocean off the northern Florida coast, the center Merlin 1D would reignite for a third and final "landing burn" designed to scrub vertical velocity. The four landing legs would deploy 10 seconds after the start of the burn to simulate the process of an actual landing on land. At the conclusion of this test the stage would drop into the ocean. Recovery of the stage is unlikely, and is unnecessary for a successful test.

Thanks again, great addon.

---------- Post added at 10:49 PM ---------- Previous post was at 10:48 PM ----------

Im having some trouble getting the CRS-3 scenario to work, can anyone help?

There are two dragon updates on OH, it wasnt clear in the links because it only showed dragon update #1. Did you get #2 as well? if not this may solve your problem.

Also try downloading the latest Spacecraft3.dll
This version worked for me here: http://users.swing.be/vinka/

 

[BrianJ]

Im having some trouble getting the CRS-3 scenario to work, can anyone help?

Hi, sorry I must have missed your post previously.
I'm assuming you get a CTD when you try to run the scenario?

As rcullan suggests, it might be an outdated version of spacecraft3.dll causing a problem. Try the most recent version.

Also, try disabling all non-essential modules except transx and maybe scenario_editor.dll, its just possible there's a conflict with something.

This line from your .log makes me wonder....

Graphics: Active lights supported: -1

I know the "LPad" launchpad vessel has an extra light source coded in, so try deleting the "LPad" vessel entry from the scenario.
(On second thought, the "LPad" is in all the scenarios, so it probably isn't that).

Hope that helps. try updating spacecraft3.dll first, though.

Cheers,
Brian

 

[NextBigLeap]

I thought it was spacecraft3 too but it was up to date. I took the two secondary payloads out of the scenario and it works, thank you for the reply.

 

[Kyle]

FWIW, LC-13 is the Cape Canaveral RTLS site for Falcon 9 first stage. SLC-4W is the RTLS site for VAFB.

 

[Cosmic Penguin]

I have just tested this add-on several times. Great job! :thumbup:

Several comments that might be useful for a version 1.1 ():

1. I would be grateful if the 2 second hold down after engine ignition is simulated.
2. How about an option to fly the rocket without legs (just like it did today)? That option can be hard coded to automatically mean that no fly-back target is selected.
3. Can the fairing separation time be changed?
4. I found the 2nd stage RCS very hard to use during coast phase - one slightly harder strike on the keyboard and the RCS fuel would suddenly drop to zero. Maybe the controls can be set less reactive?
5. Is there anyway to add sound packs to the add-on?

Thanks! :tiphat:

 

[BrianJ]

I have just tested this add-on several times. Great job! :thumbup:

Several comments that might be useful for a version 1.1 ():

1. I would be grateful if the 2 second hold down after engine ignition is simulated.
2. How about an option to fly the rocket without legs (just like it did today)? That option can be hard coded to automatically mean that no fly-back target is selected.
3. Can the fairing separation time be changed?
4. I found the 2nd stage RCS very hard to use during coast phase - one slightly harder strike on the keyboard and the RCS fuel would suddenly drop to zero. Maybe the controls can be set less reactive?
5. Is there anyway to add sound packs to the add-on?

Thanks! :tiphat:

Hey, thanks! Suggestions always welcome....

1. Most easily done with an attachment point on the launch pad - if I get around to making a pad, I'll bear it in mind.
2. The legs are the interesting bit! :lol: For completeness sake, I guess I'll make a version with no legs, but it's not top of the list (F9H first, I think).
3. Yes. You have a specific timing in mind? Or it could be keyed to atmospheric pressure...
4. I know - I did exactly that yesterday while trying out the AsiaSat launch. I made up the RCS configuration, since I have no info to work on. It's really only useful for roll (pitch/yaw by main engine gimbal) but it is tricky if you want to line up for a second burn. I'll try to think of something - maybe just add another couple of RCS motors.
5. Not quite sure what you want sound-wise. Countdown and callouts for staging and MECO wouldn't be too much hassle - if someone can make the required .wav's .

I'm still tweaking the 1st stage flyback stuff. Attached to this post is the latest .dll for the 1st stage(if anyone wants to try it). The Auto Flyback-EDL sequence now includes a reentry burn between 100km-20km alt(usually 70km-20km) in addition to the descent and landing burns from 15km. It requires an extra ~10000kg fuel reserve but cuts reentry load to more acceptable levels. Targeting is more reliable but still needs refinement. Also, I've removed the interstage jettison option.

Thanks again for the input, I'll see what I can do

 

[Kyle]

You've done outstanding work on this one so far. Well done.