Difference between revisions of "Tutorial:RemoteTech"

From Kerbal Space Program Wiki
Jump to: navigation, search
m (Fixed categories)
 
(6 intermediate revisions by 3 users not shown)
Line 1: Line 1:
 +
{{Move|Tutorial:RemoteTech Old|Make room for RemoteTech2 tutorial to move here}}
 +
 
This tutorial describes how to set up a basic relay network with the mod "RemoteTech".
 
This tutorial describes how to set up a basic relay network with the mod "RemoteTech".
 +
 +
:''For a tutorial on Remote Tech 2 or Remote Tech 1.5 and later, see [[Tutorial:RemoteTech2]]''
  
 
==Specifications==
 
==Specifications==
 
*'''Length:''' 30 minutes
 
*'''Length:''' 30 minutes
 
*'''Difficulty:''' Advanced - Be firm with [[Tutorial:Basic Rocket Design|basic rocketry]] and how to [[Tutorial:Basic Orbiting|establish and alter orbits]]
 
*'''Difficulty:''' Advanced - Be firm with [[Tutorial:Basic Rocket Design|basic rocketry]] and how to [[Tutorial:Basic Orbiting|establish and alter orbits]]
*'''For version:''' 0.18.2 and RemoteTech 0.4.0.3
+
*'''For version:''' 0.18.2 and higher and RemoteTech 0.4.0.3 to 1.3.3
  
  
Line 10: Line 14:
  
 
If things are too complicated or confusing, the fault lies with the tutorial for not being elaborate and/or clear enough, so complain!
 
If things are too complicated or confusing, the fault lies with the tutorial for not being elaborate and/or clear enough, so complain!
 
  
 
==Basic Relay Sat config==
 
==Basic Relay Sat config==
  
[[File:RT_Satellite_Example.png|thumb|right|A lightweight basic relay satellite]]
+
[[File:RT Satellite Example.png|thumb|right|A lightweight basic relay satellite]]
 
A mere relay satellite does not need much, but there are some absolute essentials:
 
A mere relay satellite does not need much, but there are some absolute essentials:
  
 
*RemoteControl element - Any "Pod" element that has "RemoteTech" in its description. These are the new RT pods/disks or - if you use the RT compatibility mod - all stock probes as well. This is required to process remote commands as well as relay them to other satellites
 
*RemoteControl element - Any "Pod" element that has "RemoteTech" in its description. These are the new RT pods/disks or - if you use the RT compatibility mod - all stock probes as well. This is required to process remote commands as well as relay them to other satellites
  
*[[Parts#Electricity|Solar Panel/Power Generator]] - The RT processor draws power continously. If energy supply is zero, you can no longer control the vessel.
+
*[[Parts#Electricity|Solar Panel/Power Generator]] - The RT processor draws power continuously. If energy supply is zero, you can no longer control the vessel.
  
*[[Parts#Electricity|Battery Packs]] - As the RT processor draws continous power and you want to keep control on Kerbin nights, do this. Not necessary for power generators, obviously.
+
*[[Parts#Electricity|Battery Packs]] - As the RT processor draws continuous power and you want to keep control on Kerbin nights, do this. Not necessary for power generators, obviously.
  
 
*Antenna - You always need this on unmanned probes.
 
*Antenna - You always need this on unmanned probes.
Line 33: Line 36:
 
''Remark on interplanetary probes:'' Interplanetary probes will require a satellite link for most of their travel time. As SatDishes are disabled by default, you'll immediately lose contact to the vessel right on the launchpad if no antenna is mounted. Tip: Attach the antenna to your first launcher stage. Before launch, enable your satdishes and link them up properly, then you can safely discard the antenna during ascent and don't have useless weight to carry around.
 
''Remark on interplanetary probes:'' Interplanetary probes will require a satellite link for most of their travel time. As SatDishes are disabled by default, you'll immediately lose contact to the vessel right on the launchpad if no antenna is mounted. Tip: Attach the antenna to your first launcher stage. Before launch, enable your satdishes and link them up properly, then you can safely discard the antenna during ascent and don't have useless weight to carry around.
  
The example satellite on the right shows that a relay satellite can be super small and doesn't require much at all. In fact, this satellite was used for the Mun Relay positions, as the available thrust is more than sufficient to complete the entire injection from LKO (75km orbit) to the Mun tandem position. The probe still has enough fuel left to do be deorbited back to Kerbin.
+
The example satellite on the right shows that a relay satellite can be super small and doesn't require much at all. In fact, this satellite was used for the Mun Relay positions, as the available thrust is more than sufficient to complete the entire injection from LKO (75 km orbit) to the Mun tandem position. The probe still has enough fuel left to do be deorbited back to Kerbin.
  
  
 
== Covering Kerbin ==
 
== Covering Kerbin ==
  
[[File:RemoteTech_Example.svg|thumb|right|A diagram of a RemoteTech satellite network]]
+
[[File:RemoteTech Example.svg|thumb|right|A diagram of a RemoteTech satellite network]]
  
 
The KSC (Kerbal Space Center), depicted on the left of [[Kerbin]] has an invisible 5Mm omni-antenna that always is powered. The range of the antenna is depicted in green. The planet Kerbin blocks the signal, so the effective range looks like a half-sphere.
 
The KSC (Kerbal Space Center), depicted on the left of [[Kerbin]] has an invisible 5Mm omni-antenna that always is powered. The range of the antenna is depicted in green. The planet Kerbin blocks the signal, so the effective range looks like a half-sphere.
  
This network approach relies on the usage of [[w:Geosynchronous_orbit|geosynchronous]] satellites as relays. The first satellite should be placed directly atop KSC. If it's your first launch, I suggest to make this a manned mission so you have full control of your vessel while trying to establish an orbit. If you want to go unmanned, you have to make sure that you circularize a first low orbit while still in direct range of KSC. When conducting the transfer to the geosynch orbit, also remember that you have to be in contact with KSC to start the transfer.
+
This network approach relies on the usage of [[w:Geosynchronous orbit|geosynchronous]] satellites as relays. The first satellite should be placed directly atop KSC. If it's your first launch, I suggest to make this a manned mission so you have full control of your vessel while trying to establish an orbit. If you want to go unmanned, you have to make sure that you circularize a first low orbit while still in direct range of KSC. When conducting the transfer to the geosynch orbit, also remember that you have to be in contact with KSC to start the transfer.
  
 
Then complete the network by placing at least two more satellites at a 90° angle from the first. If you do this perfectly and your satellites have a perfect stable orbit, this is sufficient. Due to lack of fine-control in speed and altitude (even with Mechjeb), satellites often tend to drift very slightly over time. It is safer to place a fourth satellite to complete coverage and serve as backup.
 
Then complete the network by placing at least two more satellites at a 90° angle from the first. If you do this perfectly and your satellites have a perfect stable orbit, this is sufficient. Due to lack of fine-control in speed and altitude (even with Mechjeb), satellites often tend to drift very slightly over time. It is safer to place a fourth satellite to complete coverage and serve as backup.
Line 63: Line 66:
 
The target orbit for the Mun relay satellites is a Kerbin orbit at the same altitude as the Mun, with the very same speed. This means you'll fly just behind/ahead of the Mun, retaining the same distance to it. We cannot use a geosynchronous orbit on Mun, as the Mun's sphere of influence is smaller than the necessary orbit. However, when looking from Kerbin, flying in "tandem" with the Mun is a pseudo-synchronous position, so it's a good trick for stable full-time Mun coverage.
 
The target orbit for the Mun relay satellites is a Kerbin orbit at the same altitude as the Mun, with the very same speed. This means you'll fly just behind/ahead of the Mun, retaining the same distance to it. We cannot use a geosynchronous orbit on Mun, as the Mun's sphere of influence is smaller than the necessary orbit. However, when looking from Kerbin, flying in "tandem" with the Mun is a pseudo-synchronous position, so it's a good trick for stable full-time Mun coverage.
  
Put one Mun relay ahead, one behind the Mun, both at a good distance (I suggest 3000-3500km distance from the Mun, this will give a nice overlap and cover the entire sphere of influence of the Mun).
+
Put one Mun relay ahead, one behind the Mun, both at a good distance (I suggest 3000–3500 km distance from the Mun, this will give a nice overlap and cover the entire sphere of influence of the Mun).
  
 
== Covering any celestial body ==
 
== Covering any celestial body ==
Line 69: Line 72:
  
 
== Related Links ==
 
== Related Links ==
* [[Tutorial:_Basic_Probe_And_Satellite_Building|Tutorial: Basic Probe And Satellite Building]]
+
* [[Tutorial: Basic Probe And Satellite Building]]
  
[[Category:Tutorials]]
+
[[Category:Tutorials|RemoteTech]]

Latest revision as of 20:21, 2 May 2019

This page has been requested to be moved to Tutorial:RemoteTech Old.

The given reason is: Make room for RemoteTech2 tutorial to move here

This tutorial describes how to set up a basic relay network with the mod "RemoteTech".

For a tutorial on Remote Tech 2 or Remote Tech 1.5 and later, see Tutorial:RemoteTech2

Specifications


Feedback is much appreciated on the Discussion page!

If things are too complicated or confusing, the fault lies with the tutorial for not being elaborate and/or clear enough, so complain!

Basic Relay Sat config

A lightweight basic relay satellite

A mere relay satellite does not need much, but there are some absolute essentials:

  • RemoteControl element - Any "Pod" element that has "RemoteTech" in its description. These are the new RT pods/disks or - if you use the RT compatibility mod - all stock probes as well. This is required to process remote commands as well as relay them to other satellites
  • Solar Panel/Power Generator - The RT processor draws power continuously. If energy supply is zero, you can no longer control the vessel.
  • Battery Packs - As the RT processor draws continuous power and you want to keep control on Kerbin nights, do this. Not necessary for power generators, obviously.
  • Antenna - You always need this on unmanned probes.
  • SatDish - Only if the relay satellite is to be used to control far away probes. Makes sense to place 2-4 on your Keo-Relay network satellites, as these are the base for any endeavour, really.


It also might be a good idea to include a docking port somewhere, should it become necessary to expand the array of dishes on your relay sat later on.


Remark on interplanetary probes: Interplanetary probes will require a satellite link for most of their travel time. As SatDishes are disabled by default, you'll immediately lose contact to the vessel right on the launchpad if no antenna is mounted. Tip: Attach the antenna to your first launcher stage. Before launch, enable your satdishes and link them up properly, then you can safely discard the antenna during ascent and don't have useless weight to carry around.

The example satellite on the right shows that a relay satellite can be super small and doesn't require much at all. In fact, this satellite was used for the Mun Relay positions, as the available thrust is more than sufficient to complete the entire injection from LKO (75 km orbit) to the Mun tandem position. The probe still has enough fuel left to do be deorbited back to Kerbin.


Covering Kerbin

A diagram of a RemoteTech satellite network

The KSC (Kerbal Space Center), depicted on the left of Kerbin has an invisible 5Mm omni-antenna that always is powered. The range of the antenna is depicted in green. The planet Kerbin blocks the signal, so the effective range looks like a half-sphere.

This network approach relies on the usage of geosynchronous satellites as relays. The first satellite should be placed directly atop KSC. If it's your first launch, I suggest to make this a manned mission so you have full control of your vessel while trying to establish an orbit. If you want to go unmanned, you have to make sure that you circularize a first low orbit while still in direct range of KSC. When conducting the transfer to the geosynch orbit, also remember that you have to be in contact with KSC to start the transfer.

Then complete the network by placing at least two more satellites at a 90° angle from the first. If you do this perfectly and your satellites have a perfect stable orbit, this is sufficient. Due to lack of fine-control in speed and altitude (even with Mechjeb), satellites often tend to drift very slightly over time. It is safer to place a fourth satellite to complete coverage and serve as backup.

If you use better antennae on your Kerbin relay satellites, all these problems will be reduced as well and you can make a safe and sound 3-satellite network, placing them 120° apart. I suggest using the big 8 or 9Mm antennae that have to be extended. These are retracted by default, so use the 5Mm antenna for launch.

If you intend to do unmanned missions on the Kerbin polar regions (in-atmosphere), you'll need at least two more satellites to orbit at 90° inclination. Place them on the same orbit, 180° apart and you'll have (almost) 100% coverage of these areas. For regular low polar orbits the basic relay network suffices.

Covering the Mun

If you want to expand your network to the Mun, your Mun relay satellites have to be mounted with satellite dishes so you can control them once you leave the coverage of your Kerbin relay satellites. It is a good idea to always use 2 satellite dishes per vessel. In our example we will link our fist satellite up to Relay 1 and Relay 2. The upside of two dishes is that Kerbin will ever only be able to block out one of two relay satellites, so you will have continuous control of your vessel during all stages of flight.

Pre-Launch preparation: While you are still on the launchpad, do the following steps to set up RemoteTech properly:

  • Activate the dishes (Right-click on them->Activate), something that is VERY easily forgotten later on
  • Set Dish 1 to link with "Relay 1" and Dish 2 to link with "Relay 2"
  • Using the RemoteTech window tab "List comsats", select "Relay 1" and "Relay 2" and set them to target your ship


The target orbit for the Mun relay satellites is a Kerbin orbit at the same altitude as the Mun, with the very same speed. This means you'll fly just behind/ahead of the Mun, retaining the same distance to it. We cannot use a geosynchronous orbit on Mun, as the Mun's sphere of influence is smaller than the necessary orbit. However, when looking from Kerbin, flying in "tandem" with the Mun is a pseudo-synchronous position, so it's a good trick for stable full-time Mun coverage.

Put one Mun relay ahead, one behind the Mun, both at a good distance (I suggest 3000–3500 km distance from the Mun, this will give a nice overlap and cover the entire sphere of influence of the Mun).

Covering any celestial body

To cover any celestial body, the Tutorial:Satellite Coverage can what altitude is needed for an amount of given satellites. The formula to calculate the distance between two satellites is important to select the correct antenna.

Related Links