Question How to generate orbit for planet and moon

[zonta]

Hi guys i would like to make two moon for a planet but the two moon are in each other i would like to know how you generate the elispe orbit and also why there module of the same name of the planet for the sol system example : what is the use of moon.dll for the moon into the system?

 

[Loru]

read API guide pdf

 

[zonta]

read API guide pdf

And where is that guide?

 

[Loru]

OrbiterSDK/Doc/API_guide.pdf

 

[zonta]

OrbiterSDK/Doc/API_guide.pdf

I don't have this into my orbiter folder

 

[Loru]

If you're using 2006 p1 edition you'll have to download orbiter SDK package
Should be in main orbiter folder in 2010 edition

 

[zonta]

If you're using 2006 p1 edition you'll have to download orbiter SDK package
Should be in main orbiter folder in 2010 edition

Ok Thanks Loru.

One more what are the use of the .dat file into data folder of the moon?

 

[orb]

One more what are the use of the .dat file into data folder of the moon?

Do you mean the ELP82.dat ([ame=http://en.wikipedia.org/wiki/Ephemeris]Ephemerides[/ame] Lunaire Parisienne 1982), or "VSOP87B.dat" (Variations Seculaires des Orbites Planetaires) and "ephem_e15.dat" for other bodies?

Those files contain parameters of positions of planets and moons of Solar system.

The "VSOP87B.dat":

The VSOP87 files contain the VSOP87 analytical solutions of the motion
of the planets Mercury, Venus, Earth, Mars, Jupiter, Saturn, Uranus, Neptune and Earth-Moon Barycenter.

There are six different versions of the theory VSOP87 which may be recognized by the type of coordinates and the reference frame.

The main version VSOP87 consists of the series in elliptic elements as in the case of previous solution VSOP82 and the other versions VSOP87 are built in rectangular variables (versions A,C,E) or spherical variables (versions B,D).

The reference frame is defined by the dynamical equinox and ecliptic J2000 for the main version VSOP87 and the versions A, B, E, and by the dynamical equinox and ecliptic of the date for the versions C and D.​

Orbiter uses version B of VSOP87.

The "ephem_e15.dat" is a file containing the J2000 parameters for the Galilean satellites.

"ELP82.dat" contains parameters for Lunar [ame=http://en.wikipedia.org/wiki/Ephemeris]ephemerides[/ame].

---------- Post added at 12:30 ---------- Previous post was at 12:05 ----------

And I forgot about "tass17.dat" file, which contains ephermides for Saturnian moons, form theory of high precision of the motion of the main Saturnian satellites, and theory of motion and ephemerides of Hyperion.

 

[zonta]

Do you mean the ELP82.dat (Ephemerides Lunaire Parisienne 1982), or "VSOP87B.dat" (Variations Seculaires des Orbites Planetaires) and "ephem_e15.dat" for other bodies?

Those files contain parameters of positions of planets and moons of Solar system.

The "VSOP87B.dat":

Orbiter uses version B of VSOP87.

The "ephem_e15.dat" is a file containing the J2000 parameters for the Galilean satellites.

"ELP82.dat" contains parameters for Lunar ephemerides.

---------- Post added at 12:30 ---------- Previous post was at 12:05 ----------

And I forgot about "tass17.dat" file, which contains ephermides for Saturnian moons, form theory of high precision of the motion of the main Saturnian satellites, and theory of motion and ephemerides of Hyperion.

Thanks orb and if i want to make some moon i need those type of data file? so how i can make that kind of file? Is there a software or its hardcoded by hand and brain?

 

[orb]

Thanks orb and if i want to make some moon i need those type of data file? so how i can make that kind of file? Is there a software or its hardcoded by hand and brain?

For some fictional moon, or for a moon you can't obtain real ephermides, you don't need that type of data, or even a CELBODY dll module for it, which would read that data. You simply specify all parameters of the orbit of the moon (or a planet) in its configuration file.

If you have real ephermides for a body you want to add to Orbiter, you can create a module that reads that data, but it isn't required for the moon or planet to work correctly in Orbiter.

Those data files, provided for planets and moons of Sol, are used to make sure that position of a body at a given time is almost the same as the real one.

 

[zonta]

For some fictional moon, or for a moon you can't obtain real ephermides, you don't need that type of data, or even a CELBODY dll module for it, which would read that data. You simply specify all parameters of the orbit of the moon (or a planet) in its configuration file.

If you have real ephermides for a body you want to add to Orbiter, you can create a module that reads that data, but it isn't required for the moon or planet to work correctly in Orbiter.

Those data files, provided for planets and moons of Sol, are used to make sure that position of a body at a given time is almost the same as the real one.

Ok Thanks orb i tried to make a moon without it but its works but i see through the moon and i hit some surface. Whats the mean of this?

 

[orb]

but i see through the moon and i hit some surface. Whats the mean of this?

I don't know. Maybe some parameter is incorrect. If you post a configuration file, I could take a look at it.

 

[zonta]

I don't know. Maybe some parameter is incorrect. If you post a configuration file, I could take a look at it.

Ok i found that i was missing the par to define the orbit into the cfg file but i will write you up what i got inside


; === Configuration file for moon Gamma(Earth) ===
Name = Gamma
Module = Gamma
ErrorLimit = 1e-5

Need to be defined yet.
; === Orbital Parameters ===
Epoch =
SemiMajorAxis =
Eccentricity =
Inclination =
LongAscNode =
LongPerihelion =
MeanLongitude =

; === Physical Parameters ===
Mass = 7.0e+22
Size = 0.5e6 ; mean radius
SidRotPeriod = 1209600 ; = 14 days
SidRotOffset = 0.65049 ; rotation offset at J2000.0
Obliquity = 0.05692024985275 ; rad(1.5424167)
LAN = 0 ; ascending node of equator - CHECK!

; === Visualisation Parameters ===
MaxPatchResolution = 8 ; highest sphere patch level

; === Fixed surface observation points ===

 

[orb]

Module = Gamma

If you didn't create a DLL file for that moon, named Gamma.dll, remove or comment out that "Module" line, and try to define some orbital parameters.

 

[zonta]

If you didn't create a DLL file for that moon, named Gamma.dll, remove or comment out that "Module" line, and try to define some orbital parameters.

Here :

; === Configuration file for moon Gamma(Earth) ===
Name = Gamma
ErrorLimit = 1e-5

; === Orbital Parameters ===
Epoch = 2000.0
SemiMajorAxis = 193400e+3
Eccentricity = 0.2
Inclination = 0.1
LongAscNode = 281.74
LongPerihelion = 153.72
MeanLongitude = 329.29

; === Physical Parameters ===
Mass = 7.347664e+22
Size = 1.738e6 ; mean radius
SidRotPeriod = 1209600 ; = 14 days
SidRotOffset = 0.65049 ; rotation offset at J2000.0
Obliquity = 0.05692024985275 ; rad(1.5424167)
LAN = 0 ; ascending node of equator - CHECK!

; === Visualisation Parameters ===
MaxPatchResolution = 8 ; highest sphere patch level

; === Fixed surface observation points ===

And its make this with the moon (from target menu in the DeltaGlider)

And also i can see the texture now

 

[martins]

Looks like this went wrong. Please read carefully Doc/OrbiterConfig.pdf, chapter 2.3 ("Planets"). This will tell you the meaning of the various parameters in the configuration file. In particular, you will have to set the "EllipticOrbit" and "HasElements" entries. Also you can remove the "ErrorLimit" entry, since this is a custom parameter only used by the Vsop and some other modules based on perturbation series solutions.

 

[zonta]

Looks like this went wrong. Please read carefully Doc/OrbiterConfig.pdf, chapter 2.3 ("Planets"). This will tell you the meaning of the various parameters in the configuration file. In particular, you will have to set the "EllipticOrbit" and "HasElements" entries. Also you can remove the "ErrorLimit" entry, since this is a custom parameter only used by the Vsop and some other modules based on perturbation series solutions.

Sorry marins i don't have this doc into my sdk/doc folder.
and its not in the orbiter/doc either

Where i can take a copy of this?

 

[martins]

If you are using Orbiter 2010, then this information is in $orbiterroot/Doc/OrbiterConfig.pdf.

If you are using Orbiter 2006, then it is in the "Configuration" section of $orbiterroot/Doc/Orbiter.pdf.

 

[zonta]

If you are using Orbiter 2010, then this information is in $orbiterroot/Doc/OrbiterConfig.pdf.

If you are using Orbiter 2006, then it is in the "Configuration" section of $orbiterroot/Doc/Orbiter.pdf.

Hey thanks Martins its works now all its was missing is :

HasElements = TRUE

Thanks again.