Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
This is the same basic principle as getting two spacecraft close enough to dock, except that instead of using it to get closer, you're using it to position the two craft further away.
I know about the altitude, the problem is that space isnt 2D so if i manage to get the altitude/speed exact the same, there is stil the problem about the third axis.
And thats where I'm stuck now, i managed to get them rellatively close to each other in matters of speed/altitude but I'm correcting "up" and "down" all the time which leads to wrong movements on other points of the orbit.
The satellites should not be on a rondevou point but kind of delayed on their orbit so that they build a ring of satellites when all is done. Can engineering redux rondevou this? I have this mod installed and every satellite has a flight computer on stuck on them..
Does someone have a tutorial on the hand for such a problem solved with engineering redux or mechjeb so I could watch it in action?
for this you need to point your sattelite at normal which is the pink markers on your navbal, then you need to thrust at the ascending/descending nodes which is were your orbits cross
again you need to pay attention to the phase angle of your two sattelites, for example i have 3 sattelites in kerbinsync orbit with each sattelite being 120 degrees apart from each other so they cover every longitute of kerbin
I put my com sat in kerbostationnary orbit, which is at 2.868.750,7 km high from Kerbin (no need to be so precise :D, and the speed is 1009 m/s, but dont worry about, as ure speed and altitude is link, if u made a circular orbit at 2868k ure speed will be close to), by this way, they dont move relatively too each other. Perso, i put one above KSC, and the two other 90° each side (they cant link KSC, but are link to the first one)
One mod i use before was Kdata, help for that cauz it indicate when ure at Geostationnary position. if u dont want, u can have an indication wiz ure period time, which have to be closest possible from 6h as Kerbin period.
U will need RCS, or small engine for be precise, and as always, prograde pt at periapsis increase Apophis altitude, retrograde decrease; and the opposite, prograde at apophis increase periapsis altitude when retrograde lower that point.
The difficult part is not to go to kerbostationnary orbit, but putting ure sat at the good place relatively to Kerbin, for that, remember that when u lower ure altitude, u go faster than an higher target (and "go to" if she front of u) and if u up ure orbit, u will go slower than ure target, enable her to meet u (even if ure target is a position relative to another sattelite)
Heres my short range com ring 4 example
http://steamcommunity.com/sharedfiles/filedetails/?id=293010636
one thing to note is that they changed the rotation period of kerbin recently down to 6 hours so kerbin stationary orbit is now 2863.33 km
for situtations like that i would recommend a knot orbit (the orbit used for GPS) which requires about 6 satelites
My problem is only getting the orbit of, lets say five, satellites as equal as possible. I startet a communication array mission before and it looked great in first time, but after some time they where much to asynchron to keep the distance i need to cover all of kerbin.
In 255km this happens alot faster then in geostationary as the planet blocks sight very soon.
Wasn't geostationary around 2.868km instead of 2.868.750km?
*edit*
Is there a tutorial about the tools and kind of this issue in the web? Havn't found one yet which explains my problem, only a few for getting the correct altitude for geostationary.. as mentiont altitude is not THAT big problem its more altitude in connection with angle..
Check http://wiki.kerbalspaceprogram.com/wiki/Main_Page
and http://forum.kerbalspaceprogram.com/forum.php
that one is the site of creator of KSP, wiz all community life, some more experienced than me can maybe give u an answer
"one thing to note is that they changed the rotation period of kerbin recently down to 6 hours so kerbin stationary orbit is now 2863.33 km"
Ty Istaitsu, i didnt know that affetc kerbostannionary altitude, will check my sat 4 correction
http://steamcommunity.com/sharedfiles/filedetails/?id=227399379&searchtext=remote+tech+2
This is the best tutorial i can think of off the top of my head, the information i think you want is in the "Setting up your first network" section.
Otherwise my only other advise is to match apoapsis, periapsis, and semi major axis as best you can and bring an ion thruster or RCS thrusters to correct the position every 60-ish orbits
*edit*
also the altitude for a stationary orbit is determined by the rotation period (or solar day) of a body in question. kerbin's day is 6 hours so you would need to have an altitude of about 2563.33lm (don't remember the exact altitude to the meter) for an orbital period of 6 hours
I have a good amount of fuel in tanks that function as the satellites body and a very effizient kw rockets engine on my satellite setup, should give me enough capability to make all maneuvers that would be nessasary for a while