No, HORIZONS uses right-handed coordinate system, Orbiter uses left-handed one. Need to swap Y and Z coordinates for correct conversion.
BEGIN_ENVIRONMENT
System Sol
Date MJD 56329
END_ENVIRONMENT
BEGIN_CAMERA
TARGET Asteroid 2012 DA14
MODE Extern
POS 43.93 -109.04 -10.91...
16:25 UTC? But real maneuver started at T+0:31 (15:33UTC) and finished at T+0:39 (15:41 UTC).
Excellent time fit! :)
---------- Post added at 10:29 PM ---------- Previous post was at 08:33 PM ----------
Yes. I get dV >3900 m/s with plane change too
BEGIN_DESC
Contains the latest simulation...
You can get correct eject trajectory for MSL from HORIZONS system
http://ssd.jpl.nasa.gov/?horizons
http://orbiter-forum.com/showthread.php?p=317913&postcount=190
Just for fun, Orbiter MJD/RPOS/RVEL from HORIZONS state vectors for MSL:
BEGIN_ENVIRONMENT
System Sol
Date MJD 55891.661261574
END_ENVIRONMENT
BEGIN_SHIPS
MSL:DeltaGlider
STATUS Orbiting Earth
RPOS 5.578081991138332E+06 -6.906871560268437E+06 2.695492584292812E+06
RVEL...
BTW, IMFD does very simple work while we searching launch window for optimal transfer. We choose eject time and intercept time - so IMFD have position and velocity of initial point (planet), position and velocity of target point. All math - it's to find elliptical orbit through this 2 points...
Can someone explain why rotation of DG in this scenario slowdowns in Orbiter and stops after few days (at x1000)? Orbiter v111105, all realism and perturbation check-boxes switched on. Is it real physical effect or bug of the Orbiter?
BEGIN_DESC
Contains the latest simulation state.
END_DESC...
dgatsoulis
No. It's not a fault at all. The problem is not in parameters of Orbiter. With all (realistic or not) parameters TransX makes (in my hands) huge error in calculation of single-burn trajectory from Moon to Mars. As I said, "it's difficult for me to calculate precise and optimal burn...
For example, I find in TransX this solution: MJD 52007.654, prograde velocity 1614 m/s, Cl. App. (rough) ~1.5M
Scenario:
BEGIN_DESC
Contains the latest simulation state.
END_DESC
BEGIN_ENVIRONMENT
System Sol
Date MJD 52007.6519094714
END_ENVIRONMENT
BEGIN_FOCUS
Ship 1
END_FOCUS...
I tried April 6-8 too. The idea was to look solution near this configurations (for saving maximum energy):
May configuration just looked better ;). But I faulted with DV every time.
I think, there is good simple single-burn solution at May, 5-7. Something like this:
But it's difficult for me to calculate precise and optimal burn using TransX or IMFD :(
Latest version for Orbiter2010 here:
http://orbiter-forum.com/showthread.php?t=1387
BTW. Mayby, for Deep Impact its really better to take di_finalenc_nav_v3_to06048.bsp as Horizons do, but not di_finalenc_nav_v3.bsp as I did.
ftp://naif.jpl.nasa.gov/pub/naif/DEEPIMPACT/kernels/spk/aareadme.txt...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.