In parking orbit, how to stay out of nearby moon's SoI?Stabilizing your craft in orbitContract: recover lost...
Why did other German political parties disband so fast when Hitler was appointed chancellor?
Why was Lupin comfortable with saying Voldemort's name?
Can I write a book of my D&D game?
A starship is travelling at 0.9c and collides with a small rock. Will it leave a clean hole through, or will more happen?
What are "industrial chops"?
Advice for a new journal editor
kill -0 <PID> は何をするのでしょうか?
How long is the DnD Starter Set campaign?
Why did Democrats in the Senate oppose the Born-Alive Abortion Survivors Protection Act (2019 S.130)?
Bash Script Function Return True-False
How does Leonard in "Memento" remember reading and writing?
How old is the day of 24 equal hours?
How can my powered armor quickly replace its ceramic plates?
When can a QA tester start his job?
What is causing the chain skip after chain replacement?
How much mayhem could I cause as a sentient fish?
How did Ancient Greek 'πυρ' become English 'fire?'
Can a person refuse a presidential pardon?
In Linux what happens if 1000 files in a directory are moved to another location while another 300 files were added to the source directory?
Why would space fleets be aligned?
What is the wife of a henpecked husband called?
Graph with overlapping labels
Is a new Boolean field better than a null reference when a value can be meaningfully absent?
Looking for access to original paper for Category O
In parking orbit, how to stay out of nearby moon's SoI?
Stabilizing your craft in orbitContract: recover lost kerbals from orbitCriteria for completing the Orbit contractHow can I get a pod back from orbit when it's out of fuel?How do I space out satellites evenly in an orbit?How NOT to launch my Mac mini into orbit?Satellite exploding while in transfer orbitHow to achieve Kerbin orbit without using maneuver nodes?What's more fuel efficient, orbit or slingshot?Why geostationary orbit?
I parked a space station in Jool's equatorial orbit and inclinated a little to avoid collisions with Tylo or Laythe.
After a 5 year tourist contract mission near Duna, I opened the mission control to find my space station "in an escape trajectory away from the Sun". I know that either Tylo or Laythe must have slingshoted my station.
Question : How to be sure that my ship/station will not meet the SoI of a nearby moon ?
Vanilla/stock answer prefered but I have KER and MechJeb installed.
kerbal-space-program
add a comment |
I parked a space station in Jool's equatorial orbit and inclinated a little to avoid collisions with Tylo or Laythe.
After a 5 year tourist contract mission near Duna, I opened the mission control to find my space station "in an escape trajectory away from the Sun". I know that either Tylo or Laythe must have slingshoted my station.
Question : How to be sure that my ship/station will not meet the SoI of a nearby moon ?
Vanilla/stock answer prefered but I have KER and MechJeb installed.
kerbal-space-program
add a comment |
I parked a space station in Jool's equatorial orbit and inclinated a little to avoid collisions with Tylo or Laythe.
After a 5 year tourist contract mission near Duna, I opened the mission control to find my space station "in an escape trajectory away from the Sun". I know that either Tylo or Laythe must have slingshoted my station.
Question : How to be sure that my ship/station will not meet the SoI of a nearby moon ?
Vanilla/stock answer prefered but I have KER and MechJeb installed.
kerbal-space-program
I parked a space station in Jool's equatorial orbit and inclinated a little to avoid collisions with Tylo or Laythe.
After a 5 year tourist contract mission near Duna, I opened the mission control to find my space station "in an escape trajectory away from the Sun". I know that either Tylo or Laythe must have slingshoted my station.
Question : How to be sure that my ship/station will not meet the SoI of a nearby moon ?
Vanilla/stock answer prefered but I have KER and MechJeb installed.
kerbal-space-program
kerbal-space-program
asked Feb 22 at 12:26
GoufaliteGoufalite
26016
26016
add a comment |
add a comment |
3 Answers
3
active
oldest
votes
The most practical approach is to simply park in an orbit which does not intersect with the orbit of any of the moons.
A reasonable rule of thumb I use is to simply park halfway between them, maybe adjusting a bit towards the smaller moon.
If you want to be sure, though, you can look up the moon characteristics and calculate the safe altitudes. For example, taking Tylo and Vall, we can see that Vall has an apoapsis of 43.2Mm and a sphere of influence of 2.4Mm, and Tylo has a periapsis of 68.5Mm and a SoI of 10.9Mm. So an orbit around Jool with an Ap under 68.5-10.9=57.6Mm and Pe above 43.2+2.4=45.6Mm will not intersect any of the moons' orbits.
Alternatively, you can manage your orbital periods to make sure you don't encounter the moon.
The simplest example is to simply have your orbit period match the orbit period of the moon. E.g. if you parked on the other side of Jool from Tylo, and you took exactly the same amount of time to orbit Jool as Tylo, then neither of you would catch each other, and no encounters would happen.
There are more complicated alternatives, e.g. if you had an elliptic orbit with a period of exactly 1.5 (3/2) times Tylo's orbit, you would get into the same position every 2 orbits (2 ship orbits, 3 Tylo orbits), so as long as the match is exact and your positions do not drift, if you did not encounter Tylo in 2 orbits, you will not encounter Tylo.
If you want to get fancy, you can even exploit the fact that Laythe-Vall-Tylo have an orbital resonance of 1:2:4, and set up a safe elliptic orbit floating among all of them.
Both of these approaches are safe to use on the same orbital plane as the moon, but if your orbit is significantly inclined, you only need to worry about these things at the time your orbital plane crosses the orbital plane of the moon. Inclination alone will only slightly reduce your chances of an encounter, and does not offer significant protection, though.
thank you for the Ap-Pe approach, it's the most precise way, precise manoevers is not my cup of tea (I tried to put sattelites in a triangle and after a few years they where all together on the same side of the planet)
– Goufalite
yesterday
add a comment |
If you circularize your orbit, the chance of intercept is much lower. The more eccentric your orbit, the harder it is for you to tell if an intercept is likely.
New contributor
add a comment |
A practical way to make sure that your orbit will not (soon) intersect any other body's SOI is to use a dummy maneuver node:
Create a maneuver node anywhere along your (planned) parking orbit. Don't adjust any of the burn vectors, but leave the node Δv at 0 m/s.
Instead, right-click the center of the node to activate the +/- orbit buttons.
Click the + button and check if any unwanted encounters appear. If not, keep clicking the button several more times. If you don't see any after a few dozen clicks, you can be fairly sure that your orbit is likely to be stable.
Optionally, remove the node by clicking the X button when you're done.
What you're doing by clicking the + button is telling KSP that you want to stay in your parking orbit for one more full orbit before performing the (dummy) maneuver. Normally, KSP's maneuver planner only shows you encounters that happen less than one full orbit after the most recent planned maneuver, but by moving the maneuver forward, you can get it to show later encounters.
Incidentally, this trick of using zero Δv nodes is also quite useful when you do want to get an encounter. For example, I used it in this challenge mission to (partially) plan a ballistic trajectory that encounters all of Jool's moons.
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "41"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
noCode: true, onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fgaming.stackexchange.com%2fquestions%2f346882%2fin-parking-orbit-how-to-stay-out-of-nearby-moons-soi%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
3 Answers
3
active
oldest
votes
3 Answers
3
active
oldest
votes
active
oldest
votes
active
oldest
votes
The most practical approach is to simply park in an orbit which does not intersect with the orbit of any of the moons.
A reasonable rule of thumb I use is to simply park halfway between them, maybe adjusting a bit towards the smaller moon.
If you want to be sure, though, you can look up the moon characteristics and calculate the safe altitudes. For example, taking Tylo and Vall, we can see that Vall has an apoapsis of 43.2Mm and a sphere of influence of 2.4Mm, and Tylo has a periapsis of 68.5Mm and a SoI of 10.9Mm. So an orbit around Jool with an Ap under 68.5-10.9=57.6Mm and Pe above 43.2+2.4=45.6Mm will not intersect any of the moons' orbits.
Alternatively, you can manage your orbital periods to make sure you don't encounter the moon.
The simplest example is to simply have your orbit period match the orbit period of the moon. E.g. if you parked on the other side of Jool from Tylo, and you took exactly the same amount of time to orbit Jool as Tylo, then neither of you would catch each other, and no encounters would happen.
There are more complicated alternatives, e.g. if you had an elliptic orbit with a period of exactly 1.5 (3/2) times Tylo's orbit, you would get into the same position every 2 orbits (2 ship orbits, 3 Tylo orbits), so as long as the match is exact and your positions do not drift, if you did not encounter Tylo in 2 orbits, you will not encounter Tylo.
If you want to get fancy, you can even exploit the fact that Laythe-Vall-Tylo have an orbital resonance of 1:2:4, and set up a safe elliptic orbit floating among all of them.
Both of these approaches are safe to use on the same orbital plane as the moon, but if your orbit is significantly inclined, you only need to worry about these things at the time your orbital plane crosses the orbital plane of the moon. Inclination alone will only slightly reduce your chances of an encounter, and does not offer significant protection, though.
thank you for the Ap-Pe approach, it's the most precise way, precise manoevers is not my cup of tea (I tried to put sattelites in a triangle and after a few years they where all together on the same side of the planet)
– Goufalite
yesterday
add a comment |
The most practical approach is to simply park in an orbit which does not intersect with the orbit of any of the moons.
A reasonable rule of thumb I use is to simply park halfway between them, maybe adjusting a bit towards the smaller moon.
If you want to be sure, though, you can look up the moon characteristics and calculate the safe altitudes. For example, taking Tylo and Vall, we can see that Vall has an apoapsis of 43.2Mm and a sphere of influence of 2.4Mm, and Tylo has a periapsis of 68.5Mm and a SoI of 10.9Mm. So an orbit around Jool with an Ap under 68.5-10.9=57.6Mm and Pe above 43.2+2.4=45.6Mm will not intersect any of the moons' orbits.
Alternatively, you can manage your orbital periods to make sure you don't encounter the moon.
The simplest example is to simply have your orbit period match the orbit period of the moon. E.g. if you parked on the other side of Jool from Tylo, and you took exactly the same amount of time to orbit Jool as Tylo, then neither of you would catch each other, and no encounters would happen.
There are more complicated alternatives, e.g. if you had an elliptic orbit with a period of exactly 1.5 (3/2) times Tylo's orbit, you would get into the same position every 2 orbits (2 ship orbits, 3 Tylo orbits), so as long as the match is exact and your positions do not drift, if you did not encounter Tylo in 2 orbits, you will not encounter Tylo.
If you want to get fancy, you can even exploit the fact that Laythe-Vall-Tylo have an orbital resonance of 1:2:4, and set up a safe elliptic orbit floating among all of them.
Both of these approaches are safe to use on the same orbital plane as the moon, but if your orbit is significantly inclined, you only need to worry about these things at the time your orbital plane crosses the orbital plane of the moon. Inclination alone will only slightly reduce your chances of an encounter, and does not offer significant protection, though.
thank you for the Ap-Pe approach, it's the most precise way, precise manoevers is not my cup of tea (I tried to put sattelites in a triangle and after a few years they where all together on the same side of the planet)
– Goufalite
yesterday
add a comment |
The most practical approach is to simply park in an orbit which does not intersect with the orbit of any of the moons.
A reasonable rule of thumb I use is to simply park halfway between them, maybe adjusting a bit towards the smaller moon.
If you want to be sure, though, you can look up the moon characteristics and calculate the safe altitudes. For example, taking Tylo and Vall, we can see that Vall has an apoapsis of 43.2Mm and a sphere of influence of 2.4Mm, and Tylo has a periapsis of 68.5Mm and a SoI of 10.9Mm. So an orbit around Jool with an Ap under 68.5-10.9=57.6Mm and Pe above 43.2+2.4=45.6Mm will not intersect any of the moons' orbits.
Alternatively, you can manage your orbital periods to make sure you don't encounter the moon.
The simplest example is to simply have your orbit period match the orbit period of the moon. E.g. if you parked on the other side of Jool from Tylo, and you took exactly the same amount of time to orbit Jool as Tylo, then neither of you would catch each other, and no encounters would happen.
There are more complicated alternatives, e.g. if you had an elliptic orbit with a period of exactly 1.5 (3/2) times Tylo's orbit, you would get into the same position every 2 orbits (2 ship orbits, 3 Tylo orbits), so as long as the match is exact and your positions do not drift, if you did not encounter Tylo in 2 orbits, you will not encounter Tylo.
If you want to get fancy, you can even exploit the fact that Laythe-Vall-Tylo have an orbital resonance of 1:2:4, and set up a safe elliptic orbit floating among all of them.
Both of these approaches are safe to use on the same orbital plane as the moon, but if your orbit is significantly inclined, you only need to worry about these things at the time your orbital plane crosses the orbital plane of the moon. Inclination alone will only slightly reduce your chances of an encounter, and does not offer significant protection, though.
The most practical approach is to simply park in an orbit which does not intersect with the orbit of any of the moons.
A reasonable rule of thumb I use is to simply park halfway between them, maybe adjusting a bit towards the smaller moon.
If you want to be sure, though, you can look up the moon characteristics and calculate the safe altitudes. For example, taking Tylo and Vall, we can see that Vall has an apoapsis of 43.2Mm and a sphere of influence of 2.4Mm, and Tylo has a periapsis of 68.5Mm and a SoI of 10.9Mm. So an orbit around Jool with an Ap under 68.5-10.9=57.6Mm and Pe above 43.2+2.4=45.6Mm will not intersect any of the moons' orbits.
Alternatively, you can manage your orbital periods to make sure you don't encounter the moon.
The simplest example is to simply have your orbit period match the orbit period of the moon. E.g. if you parked on the other side of Jool from Tylo, and you took exactly the same amount of time to orbit Jool as Tylo, then neither of you would catch each other, and no encounters would happen.
There are more complicated alternatives, e.g. if you had an elliptic orbit with a period of exactly 1.5 (3/2) times Tylo's orbit, you would get into the same position every 2 orbits (2 ship orbits, 3 Tylo orbits), so as long as the match is exact and your positions do not drift, if you did not encounter Tylo in 2 orbits, you will not encounter Tylo.
If you want to get fancy, you can even exploit the fact that Laythe-Vall-Tylo have an orbital resonance of 1:2:4, and set up a safe elliptic orbit floating among all of them.
Both of these approaches are safe to use on the same orbital plane as the moon, but if your orbit is significantly inclined, you only need to worry about these things at the time your orbital plane crosses the orbital plane of the moon. Inclination alone will only slightly reduce your chances of an encounter, and does not offer significant protection, though.
answered Feb 22 at 18:05
GedasGedas
91137
91137
thank you for the Ap-Pe approach, it's the most precise way, precise manoevers is not my cup of tea (I tried to put sattelites in a triangle and after a few years they where all together on the same side of the planet)
– Goufalite
yesterday
add a comment |
thank you for the Ap-Pe approach, it's the most precise way, precise manoevers is not my cup of tea (I tried to put sattelites in a triangle and after a few years they where all together on the same side of the planet)
– Goufalite
yesterday
thank you for the Ap-Pe approach, it's the most precise way, precise manoevers is not my cup of tea (I tried to put sattelites in a triangle and after a few years they where all together on the same side of the planet)
– Goufalite
yesterday
thank you for the Ap-Pe approach, it's the most precise way, precise manoevers is not my cup of tea (I tried to put sattelites in a triangle and after a few years they where all together on the same side of the planet)
– Goufalite
yesterday
add a comment |
If you circularize your orbit, the chance of intercept is much lower. The more eccentric your orbit, the harder it is for you to tell if an intercept is likely.
New contributor
add a comment |
If you circularize your orbit, the chance of intercept is much lower. The more eccentric your orbit, the harder it is for you to tell if an intercept is likely.
New contributor
add a comment |
If you circularize your orbit, the chance of intercept is much lower. The more eccentric your orbit, the harder it is for you to tell if an intercept is likely.
New contributor
If you circularize your orbit, the chance of intercept is much lower. The more eccentric your orbit, the harder it is for you to tell if an intercept is likely.
New contributor
New contributor
answered Feb 22 at 18:29
Enrico CogliatiEnrico Cogliati
11
11
New contributor
New contributor
add a comment |
add a comment |
A practical way to make sure that your orbit will not (soon) intersect any other body's SOI is to use a dummy maneuver node:
Create a maneuver node anywhere along your (planned) parking orbit. Don't adjust any of the burn vectors, but leave the node Δv at 0 m/s.
Instead, right-click the center of the node to activate the +/- orbit buttons.
Click the + button and check if any unwanted encounters appear. If not, keep clicking the button several more times. If you don't see any after a few dozen clicks, you can be fairly sure that your orbit is likely to be stable.
Optionally, remove the node by clicking the X button when you're done.
What you're doing by clicking the + button is telling KSP that you want to stay in your parking orbit for one more full orbit before performing the (dummy) maneuver. Normally, KSP's maneuver planner only shows you encounters that happen less than one full orbit after the most recent planned maneuver, but by moving the maneuver forward, you can get it to show later encounters.
Incidentally, this trick of using zero Δv nodes is also quite useful when you do want to get an encounter. For example, I used it in this challenge mission to (partially) plan a ballistic trajectory that encounters all of Jool's moons.
add a comment |
A practical way to make sure that your orbit will not (soon) intersect any other body's SOI is to use a dummy maneuver node:
Create a maneuver node anywhere along your (planned) parking orbit. Don't adjust any of the burn vectors, but leave the node Δv at 0 m/s.
Instead, right-click the center of the node to activate the +/- orbit buttons.
Click the + button and check if any unwanted encounters appear. If not, keep clicking the button several more times. If you don't see any after a few dozen clicks, you can be fairly sure that your orbit is likely to be stable.
Optionally, remove the node by clicking the X button when you're done.
What you're doing by clicking the + button is telling KSP that you want to stay in your parking orbit for one more full orbit before performing the (dummy) maneuver. Normally, KSP's maneuver planner only shows you encounters that happen less than one full orbit after the most recent planned maneuver, but by moving the maneuver forward, you can get it to show later encounters.
Incidentally, this trick of using zero Δv nodes is also quite useful when you do want to get an encounter. For example, I used it in this challenge mission to (partially) plan a ballistic trajectory that encounters all of Jool's moons.
add a comment |
A practical way to make sure that your orbit will not (soon) intersect any other body's SOI is to use a dummy maneuver node:
Create a maneuver node anywhere along your (planned) parking orbit. Don't adjust any of the burn vectors, but leave the node Δv at 0 m/s.
Instead, right-click the center of the node to activate the +/- orbit buttons.
Click the + button and check if any unwanted encounters appear. If not, keep clicking the button several more times. If you don't see any after a few dozen clicks, you can be fairly sure that your orbit is likely to be stable.
Optionally, remove the node by clicking the X button when you're done.
What you're doing by clicking the + button is telling KSP that you want to stay in your parking orbit for one more full orbit before performing the (dummy) maneuver. Normally, KSP's maneuver planner only shows you encounters that happen less than one full orbit after the most recent planned maneuver, but by moving the maneuver forward, you can get it to show later encounters.
Incidentally, this trick of using zero Δv nodes is also quite useful when you do want to get an encounter. For example, I used it in this challenge mission to (partially) plan a ballistic trajectory that encounters all of Jool's moons.
A practical way to make sure that your orbit will not (soon) intersect any other body's SOI is to use a dummy maneuver node:
Create a maneuver node anywhere along your (planned) parking orbit. Don't adjust any of the burn vectors, but leave the node Δv at 0 m/s.
Instead, right-click the center of the node to activate the +/- orbit buttons.
Click the + button and check if any unwanted encounters appear. If not, keep clicking the button several more times. If you don't see any after a few dozen clicks, you can be fairly sure that your orbit is likely to be stable.
Optionally, remove the node by clicking the X button when you're done.
What you're doing by clicking the + button is telling KSP that you want to stay in your parking orbit for one more full orbit before performing the (dummy) maneuver. Normally, KSP's maneuver planner only shows you encounters that happen less than one full orbit after the most recent planned maneuver, but by moving the maneuver forward, you can get it to show later encounters.
Incidentally, this trick of using zero Δv nodes is also quite useful when you do want to get an encounter. For example, I used it in this challenge mission to (partially) plan a ballistic trajectory that encounters all of Jool's moons.
answered 11 mins ago
Ilmari KaronenIlmari Karonen
3,1161525
3,1161525
add a comment |
add a comment |
Thanks for contributing an answer to Arqade!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fgaming.stackexchange.com%2fquestions%2f346882%2fin-parking-orbit-how-to-stay-out-of-nearby-moons-soi%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown