OHM Chapman Modules v.3

OrbitHangar

Addon Comments
Joined
Apr 9, 2008
Messages
3,832
Reaction score
18
Points
0

Author: asbjos

This add-on adds proper C++ modules for the Chapman Probes by Piper. Most of the preferences are kept, but some are slightly changed. Some extra features are also added.

The add-on requires the Chapman Probe add-on by "Piper" and OrbiterSound 4.0 by DanSteph.
 
For full description and documentation, see the ChapmanModules.pdf located in the Doc\Addons\ folder.
 
This add-on also includes a laser texture by BrianJ from his ART add-on (distributed with his kind permission).
 
Thank you to "Piper" for his great work on the original Chapman Probes!

I hope you enjoy this add-on.

Update 24.12.13:
Changed:

  • Sun tracking for solar arrays.
  • More scenarios, includin launch scenarios.
Fixed:
  • Now possible to use multiple probes in same simulation.

Update 07.04.14:
Changed:

  • Removed particle streams so that you finally can timewarp while burning engines.
  • Shorter text on screen.
  • No engine sound for ion engines.
Fixed:
  • Debug string now works for other add-ons and removed for this add-on.
Made by "asbjos" / Asbjørn.

DOWNLOAD
 
This looks like some really nice work,and I would love to try it out,but the addon Ryan Walean's "Realistic Atlas V" isn't avaliable on OH anymore.
 
Thank you for the feedback!

I'm planning on releasing some launch scenarios, but in the meanwhile, if you have Themis-A or such an add-on installed and you are familiar with the Scenario Editor, you can play around with it.
 
As for the Realistic Atlas V by Ryan Walean, I recieved in a PM by someone on the forum (forgot their name right now) and. I could send it to you.
 
As for the Realistic Atlas V by Ryan Walean, I recieved in a PM by someone on the forum (forgot their name right now) and. I could send it to you.
Yes could you please send it to me that would be great,Ill PM you with my E-mail.Thanks
 
Thanks, I liked the Chapman Probes and this is a nice upgrade. I couldn't check yet: is it possible to have multiple probes of the same type in one scenario now without additional config editing and renaming?
 
Thanks, I liked the Chapman Probes and this is a nice upgrade. I couldn't check yet: is it possible to have multiple probes of the same type in one scenario now without additional config editing and renaming?

It should work, but I haven't checked it out.
 
So long as the author didn't use any global variables for important things or strange tricks, it should be as possible as multiple Deltagliders.

Glad to see this come to fruition, asbjos. Can't wait to try it out later today. :D
 
New update!

Now I have fixed the bug with multiple probes in a scenario. Now including automatic sun tracking for the solar arrays and more scenarios + some more fixes.

Merry christmas and happy orbiting! :cheers:
 
Thank you.

I've gone ahead and re-made the 2000 EH26 mission from Piper's original add-on using the Neptune-1 Fregat/Chapman modules. A guidance file is included for parking orbit. It was slightly modified from the default Neptune-1 guidance file.

Actually, two launch scenarios are included using two different and new launch windows in the 2030s. If you use the suggested intercept dates (IMFD), then you should automatically launch more or less into the proper plane.

- The first has a lower delta-V requirement to reach the asteroid, but you will make a fly-by at ~9km/s.

-The second mission lets you intercept the asteroid at only ~1km/s. This is within the capability of the Chapman probe to rendezvous and match the asteroid's velocity. However, the initial delta-V requirement is near the limit of the Neptune-1/Fregat launcher. This mission is intended for more advanced orbitnauts who can plan an escape using multiple perigee passes for improved efficiency.

Also, I've included config files for this add-on:
[ame="http://orbithangar.com/searchid.php?ID=6231"]Space Network Plugin[/ame]

This orients the simulated high gain antenna to match its orientation on the mesh.
(Basically aim the high gain antenna at Earth to "communicate".)

I think this adds something extra for those deep-space missions. :)


 

Attachments

Very beautiful addon, thank you asbjos. I have always been a fan of everything made by piper and this just makes it so much better.
 
For all Chapman lovers, notice that this has been updated a few days ago.

Asbjos, please keep us updated when you, well, update. The update was too easy to miss.

:cheers:
 
Thanks, I was going to start an Earth-Jupiter-Saturn flight with Chapman Outer and will use the updated version now.
 
Chapman Uranus Orbiter Mission

I've created a plan for a Chapman Uranus Orbiter Mission.

It requires Jarvis dll:
http://www.orbiter-forum.com/showthread.php?t=33258&highlight=Jarvis+dll+version

The challenge was to get a long trajectory out to Uranus that still allowed capture with Chapman's limited delta-V. I used the Trajectory Optimization Tool:
[ame="http://www.orbithangar.com/searchid.php?ID=5418"]Trajectory Optimization Tool v2.1[/ame]

This is what I ended up using:
Code:
#####################################################################                     
Starting optimization...                                                                  
Optimization finished in 208.0135 seconds with message: Average change in trajectory      
fitness function less than tolerance.                                                     
Results of the analysis are as follows:                                                   
The optimal departure from EARTH occurs at 6/12/2034 22:51:32 (C3=84.0993 km^2/s^2)       
The optimal flyby of JUPITER BARYCENTER occurs at 5/22/2036 23:21:13 (deltaV=0.00041244   
km/s, pass radius=1999309.839 km)                                                         
The optimal arrival at URANUS BARYCENTER occurs at 5/8/2048 10:27:60 (arrival             
velocity=3.9462 km/s)                                                                     
The optimal trip duration is 5078.4837 days.                                              
Generating report file...Done!                                                            
#####################################################################

TRAJECTORY OPTIMIZATION TOOL v2
Optimization Report - 04-Jul-2014 07:11:05
Flight Plan: EarthJupiterSaturnUranus2010s(2_4_4)
----------------------------------------------------------------


RESULTS
--------------------------------
OPTIMUM EARTH DEPARTURE DATE: 6/12/2034 22:51:32 - C3: 84.0993 km²/sec²
OPTIMUM JUPITER BARYCENTER SWINGBY DATE: 5/22/2036 23:21:13 - Powered Delta-V Required: 0.00041244 km/sec
OPTIMUM URANUS BARYCENTER ARRIVAL DATE: 5/8/2048 10:27:60 - Body-centric Arrival Velocity: 3.9462 km/sec

TOTAL COST: 183.9850840


ORBITAL ELEMENTS - J2000 Ecliptic Reference Frame
--------------------------------
LEG 1 (Number of Full Revolutions: 0)
-Semi-major Axis: 484345794.4380546 km
-Eccentricity: 0.6864920
-Inclination: 2.4627778 deg
-Long. of Ascending Node: 81.6747279 deg
-Argument of Periapse: 177.1514096 deg
-True Anomaly (start): 2.7423238 deg
-True Anomaly (end): 163.9345445 deg

LEG 2 (Number of Full Revolutions: 0)
-Semi-major Axis: 1808415117.3021986 km
-Eccentricity: 0.6809062
-Inclination: 1.0497905 deg
-Long. of Ascending Node: 112.2586888 deg
-Argument of Periapse: 245.6293451 deg
-True Anomaly (start): 64.8841278 deg
-True Anomaly (end): 161.4717982 deg



GENETIC ALGORITHM INFORMATION
--------------------------------
Termination Reason: Average change in trajectory fitness function less than tolerance. 
Number of Generations Computed: 51.0 
Number of Fitness Function Evaluations: 25873.0 
Random Number Generator Type: mt19937ar

Notice that it is Earth-Jupiter-Uranus. The Flight Plan is misnamed. There is no Saturn encounter in this plan.

Here is the ini file to use Chapman as payload on the Jarvis E:
Code:
MESHNAME= ChapmanOuter
;OFFSET= 0 0 41.510
OFFSET= 0 0 39.510
NAME= ChapmanOuter
MODULE= ChapmanModules\ChapmanOuter
SPEED=0 0 0.5
WEIGHT= 1814
VISIBLE=1
ADAPTER_MESHNAME=jarvis\adapterLBEH2
ADAPTER_OFFSET=0 0 37.105

Finally, here is the launch scenario:
Code:
BEGIN_DESC
Chapman Uranus Mission


The Canadian Space Agency has decided on a "low cost" basic science mission to one of the least studied and mysterious planets: Uranus. Rather than a Voyager style flyby, they intend to send the first probe to achieve Uranus orbit in order to study the Uranus system for several years. The plan calls for modifying the successful Chapman spacecraft bus to use an RTG power source. However, because the delta-V budget of the Chapman probe is only 2700 m/s, orbital insertion is only possible from an elliptical heliocentric transfer orbit with an apoapsis near Uranus' orbit. Including a Jupiter gravity assist, the transit time of such a trajectory is perhaps 15 or more years. Since the lifetime of the RTG power source is only 18 years, there simply isn't enough time for multiple encounters with inner planets and still allow for a multi-year science mission. Fortunately, the modular design of the Jarvis series of launch vehicles has brought down the launch cost such that a very heavy vehicle can be used where a medium vehicle would have been used formerly. Thus, the massive Jarvis-E is used to accelerate the tiny probe to the tremendous velocity necessary for a direct trans-Jovian insertion. 


The mission requires the Jarvis dll version. 


Launch is automatic to a 300 x 300 km parking orbit. You should then be approximately in the proper plane to use the third stage to perform the ejection burn to Jupiter. (Delta-V about 6600 m/s) It's okay to complete a full earth orbit if you need more time to setup the plan using your preferred MFD. Plan for a slingshot encounter with Jupiter on about May 22, 2036 with a pass radius of about 2Gm. Arrival at Uranus should occur sometime around 2048 or 2049. This mission takes about an hour or two of real time so have patience! 


Once you arrive at Uranus, you will only have enough delta-V to capture to an elliptical orbit; do not expect to reach a circular orbit. Try to leave enough fuel to allow some maneuvering later. Due to Uranus's famous tilt, you will approach a pole such that only high inclination orbits are possible. One idea is to target a 90 deg. equatorial inclination and set a periapsis radius corresponding to the orbital radius of Ariel or Umbriel. Then on orbital insertion, set an apoapsis radius corresponding to the orbit of either Titania or Oberon. This allows your perpendicular orbit to nearly intersect the orbits of two moons at your apoapsis and periapsis. It is then possible to set up a flybys of the moons. If fuel remains, other moons can be targeted. How many can you reach?  
END_DESC

BEGIN_ENVIRONMENT
  System Sol
  Date MJD 64125.805880
END_ENVIRONMENT

BEGIN_FOCUS
  Ship Jarvis_E
END_FOCUS

BEGIN_CAMERA
  TARGET Jarvis_E
  MODE Extern
  POS 4.00 -166.05 71.33
  TRACKMODE TargetRelative
  FOV 60.00
END_CAMERA

BEGIN_HUD
  TYPE Surface
END_HUD

BEGIN_MFD Left
  TYPE Orbit
  PROJ Ship
  FRAME Ecliptic
  REF Earth
END_MFD

BEGIN_MFD Right
  TYPE Surface
  SPDMODE 1
END_MFD

BEGIN_SHIPS
Jarvis_E:JARVIS/Jarvis_E
  STATUS Landed Earth
  AFCMODE 7
  PRPLEVEL 0:1.000000 1:1.000000 2:1.000000
  NAVFREQ 0 0 0 0
  XPDR 0
  FAIRINGON 1
  STAGE 0
  GLIMIT 5
  GTVACC 6
  TGT_APOGEE 300000
  TGT_PERIGEE 300000
  ;TGT_INC 30.0
  AP 1
  MET -180
  LAUNCH_SITE 2
  PAYLOAD_FILE Jarvis_E\Chapman.ini
END
END_SHIPS

BEGIN_ExtMFD
END

BEGIN_VesselParametersMFD
END

I could provide a post-Jupiter scenario if requested.


I had a lot of fun moon-hopping the Uranus system from a perpendicular orbital plane, which is a bit unique.

Screenshots:
Jupiter Encounter:


In Uranus Orbit:



An example of a Uranus polar orbit with apoapsis approximately intersecting the orbit of Oberon. The periapsis can be adjusted to intersect Umbriel's as well.


Oberon Encounter:


Umbriel Encounter:


Good luck! :hailprobe:
 
Last edited:
Almost forgot,

Here is IMFD setup a few minutes before TJI:

Code:
BEGIN_DESC
Contains the latest simulation state.
END_DESC

BEGIN_ENVIRONMENT
  System Sol
  Date MJD 64125.8234439997
END_ENVIRONMENT

BEGIN_FOCUS
  Ship Jarvis_E
END_FOCUS

BEGIN_CAMERA
  TARGET Jarvis_E
  MODE Cockpit
  FOV 60.00
END_CAMERA

BEGIN_HUD
  TYPE Surface
END_HUD

BEGIN_MFD Left
  TYPE User
  MODE Interplanetary
  Scenario Old2
  MapMFD V5
  Reference jupiter
  Target none
  Center jupiter
  Data 0 1 6.57574869782635e-008 0 1 1 1 0 1 0 0 0
  MassLimit 1e+020
  CMode 0
  Config 1 0 1 1 0 0
  ExtMode 2
  Periapis Earth
  END 
  CorMFD V4
  Reference Sun
  Target Jupiter
  Source Earth
  ActiveProg 1 1
  DataA 0 5 0 0 0 0
  DataB 1 1 64125.82344399967 0 0 1.095499588964489 0 64835.97306712963 0
  DVProg 0 0 0 1
  AdvConf 5.241223743738972 6.274458660919614 11589924665.23542 2 0
  Guidance 0
  END 
  EjectMFD V5
  Reference Auto
  Data 1 1 3 0 0 64125.83021823486 9111.08
  Guidance 1
  END 
  BaseAprMFD V2
  Reference Auto
  Target none
  Source none
  DataA 0 0 120000 0.10821 0.366519 1 1 64125.81292369833 64125.81292369833 0
  DataB 0 3 0 1 0 1
  END 
  SlingMFD V4
  Reference Auto
  Source none
  Data 0 1 1 3 0 1 64125.81292369833 0
  END 
  LaunchMFD V4
  Target None
  Data 0 1 1 3 0 1 0
  END 
  CF1_DataA 0 0
  CF1_DataB 0 10 120000 2 20 150000
  CF1_SecTgt 
  mfdShare -1
  mfdProgram 3
END_MFD

BEGIN_MFD Right
  TYPE User
  MODE Interplanetary
  Scenario Old2
  MapMFD V5
  Reference jupiter
  Target none
  Center jupiter
  Data 0 1 6.57574869782635e-008 0 1 1 1 0 1 0 0 0
  MassLimit 1e+020
  CMode 0
  Config 1 0 1 1 0 0
  ExtMode 2
  Periapis Earth
  END 
  CorMFD V4
  Reference Sun
  Target Jupiter
  Source Earth
  ActiveProg 1 1
  DataA 0 5 0 0 0 0
  DataB 1 1 64125.82344399967 0 0 1.095499588964489 0 64835.97306712963 0
  DVProg 0 0 0 1
  AdvConf 5.241223743738972 6.274458660919614 11589924665.23542 2 0
  Guidance 0
  END 
  EjectMFD V5
  Reference Auto
  Data 1 1 3 0 0 64125.83021823486 9111.08
  Guidance 1
  END 
  BaseAprMFD V2
  Reference Auto
  Target none
  Source none
  DataA 0 0 120000 0.10821 0.366519 1 1 64125.81292369833 64125.81292369833 0
  DataB 0 3 0 1 0 1
  END 
  SlingMFD V4
  Reference Auto
  Source none
  Data 0 1 1 3 0 1 64125.81292369833 0
  END 
  LaunchMFD V4
  Target None
  Data 0 1 1 3 0 1 0
  END 
  CF1_DataA 0 0
  CF1_DataB 0 10 120000 2 20 150000
  CF1_SecTgt 
  mfdShare 0
  mfdProgram 4
END_MFD

BEGIN_SHIPS
Jarvis_E:JARVIS/Jarvis_E
  STATUS Orbiting Earth
  RPOS -6570786.82 1107858.31 -295794.91
  RVEL 259.798 -534.742 -7711.191
  AROT 177.97 29.09 -101.29
  AFCMODE 7
  PRPLEVEL 0:1.000000
  NAVFREQ 0 0 0 0
  XPDR 0
  FAIRINGON 0
  STAGE 2
  PRPLEVEL 2:1.000000
  PLNUM 0
  GLIMIT 5.000000
  GTVACC 6.000000
  TGT_APOGEE 300000.000000
  TGT_PERIGEE 300000.000000
  TGT_INC 28.541900
  AP 100
  MET 410.394430
  PAYLOAD_FILE Jarvis_E\Chapman.ini
END
PadJa:JARVIS\PadJa
  STATUS Landed Earth
  POS -80.6312150 28.5419000
  HEADING 90.00
  AFCMODE 7
  PRPLEVEL 0:1.000000
  NAVFREQ 0 0 0 0
  XPDR 0
  ANIM_0 2 1.0000
  ANIM_1 2 1.0000
  ANIM_2 -2 0.0000
  ANIM_3 2 1.0000
END
Js2:JARVIS\Jarvis_s2
  STATUS Orbiting Earth
  RPOS -6570463.72 1107843.42 -295123.31
  RVEL 260.116 -534.779 -7710.900
  AROT 178.23 27.96 -101.16
  AFCMODE 7
  NAVFREQ 0 0 0 0
  XPDR 0
END
END_SHIPS

BEGIN_SpaceNetwork
END

BEGIN_ExtMFD
END

BEGIN_VistaBoost
END
 
In trend with several other add-on developers, I here have a version of Chapman Modules compatible with the latest Orbiter Beta (rev. 13), based on my latest Chapman Modules v.3:

https://dl.dropboxusercontent.com/u/101618424/ChapmanModules3Beta.zip

This build does not work with Orbiter 2010. It is not certain that this will work on future betas/versions of Orbiter.

For some reason, this add-on does not play well along with OrbiterSound on Orbiter Beta (the laser makes no sound when activated, no ambient sound in cockpit mode, ion engines make regular noise when burning engines, even though I have removed them), but it still flies.

As the normal version for Orbiter 2010, this add-on requires the [ame="http://orbithangar.com/searchid.php?ID=789"]Chapman Probe[/ame] add-on by "Piper" for meshes and textures.
 
Back
Top