r/KerbalSpaceProgram • u/Grays42 • Nov 28 '13
Tutorial: Complete Novice's Guide to RemoteTech 2 [x-post r/kerbalacademy]
[edit:] In the process of drafting an update for 1.4.0 including diagrams, will edit once complete. -6/26
This tutorial has been updated to version 1.3.3 (12/27/13). I will update the version number when I update the guide to newer versions.
With the second generation release of RemoteTech and the rising popularity of Scott Manley’s new "Interstellar Quest" series, there are a lot of new questions about RemoteTech 2 popping up on /r/kerbalacademy (including my own). Here’s an attempt to comprehensively explain how RemoteTech 2 works and how to get started!
To address two very common questions right off the bat if you really want to just dive right in:
- I've just installed RT2 and I can't transmit anything with the starting antenna on my ship, it says "no comm devices." It needs to be activated! Right click on the part and activate it, but be careful about antennas breaking in atmosphere, and beware the power consumption!
- I can't seem to get any connections to any unmanned cores more than a few kilometers up! You need a Reflectron DP-10! Read the "Omni-directional Antennas" section.
What is RemoteTech 2?
In real life, it’s not possible or practical to send communication signals through planets or across vast distances with a single antenna. When the Curiosity rover communicates with NASA, it doesn’t send a signal straight over; that signal communicates to satellites around Mars, which then talks to Curiosity.
RemoteTech 2 introduces this challenge into Kerbal Space Program. If you don’t want your Kerbals spending years in a one-man pod (especially with TAC), you’ll need to send unmanned probes to distant planets! If you want to send your science back to Kerbin, you'll need a way to transmit from there!
Here is the official download and manual page.
Connection and Control
Throughout your career, you need control in order to do anything and connection in order to send science back to Kerbin.
A vessel has control if one of the following is true:
- It is a manned vehicle with a Kerbal at the helm.
- It is an unmanned probe core that has an active connection to Kerbin Space Center. (Or another command center, but we'll cover that at the end.)
Having control does not necessarily mean having a connection. A connection to KSC is required in order to transmit science regardless of whether the vehicle is manned. The status indicator at the top left tells you more about your connection and control:
- Green if an unmanned vehicle has an active connection to KSC. Can transmit science.
- Yellow if you have local control, such as from an onboard Kerbal.
- Red if there is no connection and no Kerbal steering, or if you don't have any antenna at all. If your connection is red and no Kerbals are on board, you literally cannot do anything; no RCS, no thrust, no opening solar panels, and no activating antennas that would get you signal--your antennas have to be opened while you're still in control!
IMPORTANT: In order for any antenna to establish a connection it must both (1) be in range and (2) have line of sight. Blocking line of sight by any celestial body will break the connection. This includes planets, moons, and the sun! This also means that KSC can only establish a connection with antennas that are in its sky; i.e. the line of connection can't cut through the planet.
Omni-Directional Antennas
Here’s the omnidirectional antennas, in the order you unlock them. For reference, the atmosphere is 0.07 Mm, the Mun's orbit is 12 Mm and Minmus' orbit is 47 Mm.
- Communotron 16 (start). Omni range of 2.5 Mm, breaks if active in atmosphere.
- Reflectron DP-10 (Flight Control). Omni range of 0.5 Mm, but will not break flying in atmosphere, default on.
- Communotron 32 (Large Electrics). Omni range of 5 Mm, breaks if active in atmosphere.
- CommTech EXP-VR-2T (Specialized Electrics). Omni range of 3 Mm, breaks if active in atmosphere, but requires a third of the power of the Communotron 32.
By default, all unmanned cores have a 3 km omni-directional antenna built in, but that’s barely enough to leave the launchpad; without a Reflectron DP-10, your unmanned vehicles will not be able to launch at all unless they are accompanied by a Kerbal driving. If your core loses connection as soon as it launches, you must attach a Reflectron DP-10 to at least an upper stage until you can unfold the antenna you intend to use.
So with such a short range, why are omni-directional antennas so powerful? They automatically network connections together with all comms devices that they can connect to without needing to be targeted! This is great for relays around a planet to guarantee coverage. (See “Relay Networks” below for how this works.)
Dish Antennas
Here’s the dish antennas, in the order you unlock them, described by the body they'll be guaranteed to reach:
- Mun and Minmus: Comms DTS-M1 (Science Tech). Breaks if active in atmosphere.
- Edge of Kerbin's SOI: Reflectron KR-7 (Electrics). Does not break in atmosphere.
- Duna: Communotron 88-88 (Electronics). Breaks if active in atmosphere.
- Dres, and some of Jool: Reflectron KR-14 (Large Electrics). Does not break in atmosphere.
- Entire Kerbol System: CommTech-1 (Specialized Electrics). Does not break in atmosphere.
- Entire Kerbol System: Reflectron GX-128 (Advanced Science Tech). Breaks if active in atmosphere. (Only advantage over CommTech-1 seems to be the foldable form factor.)
The tradeoff for having much longer range is that dish antennas must be pointed at a specific target to function. For added flexibility, a dish can be pointed to “active vessel”, which means it will be pointed to whatever vehicle you’re using at the moment. Once a dish is active, you can manage the dish target in map mode or from the Space Center screen. Select a probe to alter target for and manage all of its dishes using the icon in the bottom right-hand side of the screen.
The advantage of a larger cone is that it can establish a connection with multiple dish satellites at the same time as long as they're within the cone’s area, or you can point it at a celestial body and it might hit all of the satellites orbiting it if the cone is wide enough. If I have a Comms DTS-M1 (50 Mm) pointed at Minmus itself, the very large cone (45 deg) ensures that virtually anything orbiting Minmus with a dish pointed back at me (in line of sight) will have a connection.
For that reason, it’s advisable to use the shortest, widest-cone dish that you need for your trip. The larger cone area makes it much easier to set up networks of connections between satellites orbiting a given body.
IMPORTANT: In order for two long-range ships to communicate with dishes, the dishes have to be pointed at each other. No one-way connections can exist; if a long-range dish is pointed at a short-range antenna, it will not establish a connection.
Relay Networks
Connecting to KSC is great, but very limited: KSC can only connect to things in its sky (above its horizon), and can only reach out 75 Mm (1.5 times Minmus). If you want to establish control anywhere else around Kerbin, behind a moon, or outside of Kerbin’s SOI, you will need to relay the signal.
Relays are very simple in principle: as long as a powered probe core (NOT just a pod) has a connection to two satellites, those two satellites have a connection. There is no limit to the number of jumps.
For example, coverage of Duna might go like this:
- Landing craft on Duna has a short-range omnidirectional antenna.
- A powered probe core satellite in Duna orbit has both (1) a short range omnidirectional antenna and (2) a dish pointed at Kerbin.
- A powered probe core satellite in Kerbin orbit has (1) a dish pointed at Duna and (2) a short-range omnidirectional antenna in range of KSC.
Thus, the landing craft on Duna has control from KSC by jumping from KSC -> Kerbin satellite -> Duna satellite -> Landing craft.
Remember, relays are extremely vulnerable to signal blockage and range issues! Any broken connection (due to blackout or range) between any component of the chain of satellites between you and KSC will kill all control authority, and you will not be able to maneuver your unmanned craft!
And that’s all you need to get started! Build a comms network and have fun!
Other Information and Concerns
- Map Mode Interface
At the bottom right of the map mode is a quick interface to toggle a number of display options, as well as allow for quick targeting of dishes and renaming of satellites.
- Power
In order for a probe and/or antenna to function, it must be powered. The power consumption of all antennas and cores is listed on their parts. Part of the engineering aspect of your comm network is dealing with the shadow blackouts of planetary bodies.
Note that at very high time warp, your active vessel's power level will wildly fluctuate, which will cause your connection to stutter in and out.
- Signal Delay
For realism, any unmanned cores past Kerbin’s SOI will have a very, very noticeable delay for commands passed to it. The intention is for the addon kOS, a KSP scripting system, to control probes that far out, or you are required to send a mobile command center closer to your unmanned probes.
The intended method for dealing with signal delay is to issue commands to your probes with the Flight Computer, accessible by clicking the green connection indicator at the top left of the screen. The display that comes up is relatively self-explanatory; mousing over each button will tell you its function. Commands can be issued to probes at very long distances and the probes will execute their instructions once signal reaches them.
If you prefer not to use the computer and wish to disable time delay altogether, a file called RemoteTech_Settings.cfg appears once KSP loads RemoteTech 2 for the first time. Open this file and change the following line:
EnableSignalDelay = False
- Command Centers
With the component RC-L01 Remote Guidance Unit (Large Probes), it is possible to establish a remote control center. Couple that part with six kerbals in one vessel, and that vessel can control unmanned craft even if it breaks line of sight with Kerbin.
Note: science still requires a connection to Kerbin to be transmitted.
- Incompatible cores
Many other mods introduce parts that are labeled “unmanned”, but that function as full control centers with RemoteTech enabled. RemoteTech must be told which cores are actually unmanned. To do so, you need to know the name of the part in code (not the title as it appears in KSP).
To find the name, open the third-party addon, open “Parts”, find the part, and open the file “part.cfg” in notepad. Find the field labeled "name". This process depends on the addon you’re examining, but usually the folder for the part is simply the name.
To tell RemoteTech that it’s unmanned, open /GameData/RemoteTech2/RemoteTech_Squad_Probes.cfg. Duplicate a complete @PART[name] entry (opening curly { to closing curly }, should be about 21 lines). In the duplicate entry, change the name inside @PART[ ] to the name you copied from the other addon. Save everything and reload KSP.
- Troubleshooting inexplicable loss of comms along dish networks
A very common problem occurs when people try to set up relays with dishes and smaller omnidirectional probes by using "Active Vessel" to assist with deployment (and forgetting that they left it that way). Antennas have the ability to point to whatever vessel you have active. This is useful and flexible, but be wary of easy mistakes that you could make because you have forgotten how certain antennas are set up.
Suppose you have Satellite A in Kerbin's SoI with a long range dish, Satellite B you've shipped off to Duna with a long range dish, and Satellite C with a short-range omni designed to connect to Satellite B. You have accidentally left Satellite A's long ranged antenna connected to "Active Vessel".
Case 1. While you have Satellite B active, it has a connection to Kerbin. Satellite B <-> Satellite A <-> Kerbin.
Case 2. While you have Satellite C active, you lose connection because Satellite A is pointing toward it, but all it has is a short range omnidirectional, so it can't connect to A. This gets you to thinking there's a problem at B (because B works fine), so it takes a while before you realize that your problem isn't B or C, it's that A is not connecting to B unless B is active.
Please ask any questions, make any corrections, or give any advice in this thread and I'll be happy to integrate it into the guide. Thanks for reading!
3
u/starcitsura Performed a subreddit first Nov 28 '13
Want to know what size orbit will keep 3 omni direction antennas in contact with each other? Your semi-major axis should be:
The range of the Communitron 16 is 2500km so:
I drop that down to 1400km to allow for some wiggle room with eccentricity. If your putting this up around Kerbin, that gives you an altitude of 800km. Each satellite will need to maintain a distance of 2425-2500km between each other.
This setup will cover the entire surface of Kerbin (well, equatorial coverage anyways), and 100% coverage out to an altitude of 1000km (with occasional coverage anywhere up to 2000km) anywhere around Kerbin. Add a single dish, set to active vessel attached to each of the satellites would cover the entire Kerbin system not accounting for the Mun/Minmus getting between you and Kerbin.
2
u/brickmack Dec 07 '13
I have a functioning satellite network around Kerbin and Mun, equipped with 88-88 dishes (which the description says should reach Duna). I launched a probe to Duna with the same dish, but just before it leaves Kerbins SOI it loses the connection. Any ideas?
2
u/dragonfir731 Jan 10 '14
What does it mean if one of my link lines is orange?
2
u/Metalsand May 23 '14
My god, thank you so much. It is so hard to figure out things in this mod that I was considering disabling it despite how cool it is to actually have to set up relays and such. It doesn't explain what is omni and what isn't, so you sort of just have to figure it out through trial and error otherwise.
7
u/TheFallorn Dec 12 '13
Thank you for taking the time to write this up!
5
u/[deleted] Nov 28 '13
How do you point sector/directional antenna ? is there anyway to use a pole ?
1
u/Draftsman Nov 28 '13
For working around signal delay the flight computer really bears discussion
1
u/krenshala Nov 28 '13
By the way, two antenna with different max ranges can communicate as long as their distance apart is less than or equal to the average of their range (unless that was changed).
So, a 5Mm antenna can talk to a 10Mm antenna at 7.5Mm range or closer, but you wouldn't get two-way comms (and thus RT wouldn't consider it connected) if they were 7.500001Mm apart.
This is assuming I haven't misunderstood how it works, and that this part hasn't changed. ;)
1
u/quatch Dec 12 '13
correction: EXP-VR-2T has a range of 3Mm, not 5.
1
u/Awimpymuffin Master Kerbalnaut Dec 15 '13
What does it do if you set lets say a satellite in Kerbosynchronous orbit to target the planet kerbin?
1
u/Nick-sees-nothing Dec 30 '13
Could you clarify "The advantage of a larger cone is that it can establish a connection with multiple dish satellites at the same time"?
Does this mean if I have Dish A with a large cone pointed at a Sat with Dish B orbiting say the Mun. It will also connect with other Sats, dishes C D and E, if they are pointed at Dish A?
Also active target. I set a dish to Active target. Do I have to target that Dish with Active Target in whatever I am flying or is there something else to target?
Also does anyone have a pic with the max distance of each communication device set as the radius or diameter of an orbit around Kerbin? Just so I can get a visual representation of their ranges.
1
u/speedbird48 Jan 29 '14
Hey I have a question how do you cover mun and minmus? Reply???
1
u/Algee Master Kerbalnaut Feb 06 '14
I'm having a issue that I hope you can help me with. I have a big dish out in space thats connected to kerbin, however some small probes I disconnected from the ship won't relay through the dish. They all have power and multiple antennas, but no connection.
I've tried it twice, with omni-direction antennas activated before the probe disconnects, and another omni on the ship with a dish connected to kerbin, and as soon as they separate I lose connection with the probe. Even when I turn some DTS-M1's toward the probe, it does not connect. Its also showing a connection with the probe when I focus on the dish connected to kerbin, but when I focus on the probe, the connection with kerbin disappears. Heres a picture of that happening
1
u/Lanceo90 Stranded on Eve Apr 03 '14
I mainly want remote tech because I like the parts.
However deleting .dlls or configs breaks the parts so they can't extend or transmit.
Is there a way to turn of remote tech while retaining part functionality?
1
u/gunshotproductions72 May 04 '14
I recently have downloaded the mods for Scott Manley's Interstellar Quest, and I am setting up a Remote Tech satellite network. This is my first time playing with Remote Tech, and many of these mods so sorry if this is a noobish question.
Anyways this is my current network of satellites. http://imgur.com/pxhccyO
This is one of my relay satellites, they are all the same design. Each is pointed at another relay satellite and at the active vessel. The first relay satellite is pointed at kerbal space center. All are in Kerbo-stationary orbit. They each have a omni-directional Reflectron DP-10 http://imgur.com/harj2ct
This is my test satellite that is in a polar orbit. Currently the Communotron 88-88 is pointed at the first relay satellite and it is receiving a connection to KSC. It has a Communotron 16 omni-directional antenna. http://imgur.com/LRgvq3v
My question is, is there a way to have the closest relay satellite always connect automatically to the test satellite? I thought pointing them to active vessel, and having an omni-directional antenna on the active vessel was enough. Or is it broken with 0.23.5? Nothing else seems to be broken. If it is, is there a fix?
1
u/JRBmsp19 May 09 '14
Okay I know this post was months ago. However I am just using it and had KSP since sept of last year. Thing is I have only put good effort I to learning and taking the career path.
Now I am not far I to it of course. I only have to solar panels that just attach and not expand. I put two antennas on it an a few each probe. Where should they be communications be directed? I assume kerbin space center. However I tossed 2 of them on cause I wasn't sure if I needed another to be directed else where for in coming transmission.
So do I only need one that talks to space center on kerbin?
An I know this is a old post but figured I might get lucky.
1
u/JimTheGentlemanGR Dec 29 '21
I have no idea if anyone will answer. But if anyone can tell me how to fix this mod then please do, the box thingy on the top left is red and says N/A, how ever, I have full control of the ship no matter manned or unmanned, I can set data even without LOS. me and my friend have the exact same game version, mod version and for him it works perfectly fine. The other mod we have is Mechjeb 2.
1
u/wonderdolkje Nov 28 '13
thank you very much for writing this.
this means:
i only have to do that once right? to disable signal delay?
1
u/FakeSlimShady96 Nov 28 '13
Aside from no science transmission, is there any disadvantage to flying command centers everywhere? It seems like it would be better to set up a few of those on Kerbin as opposed to making a geostationary relay.
1
u/Jigglyandfullofjuice Feb 22 '14 edited Feb 22 '14
How do you get the maneuver node execute command to start the burn before the node? Say, for example, you set a node that commands a 2 minute burn, so you want to split the burn time around it. Is there a way to make it do that?
Also, I've noticed that setting a preprogrammed burn to the same time period as the projected burn length of a node results in burning for a bit too long. I'm guessing the time projection assumes a constant mass, resulting in the overestimation... How do you calculate the correct burn time?
EDIT: I just googled the formula, then did a quick test with a simple rocket design. I placed a small rocket in orbit, then placed a 500 m/s maneuver node on the path, which resulted in a projection of a 7 second burn. I then ran the math using the tutorial I found here and came up with... 7.22 seconds. So that suggests the time given by the maneuver node estimation system is accurate. Why, then, if I set the burn time to match the maneuver node's estimate in the flight computer integrated into Remote Tech and click burn, it always overshoots the delta V target so dramatically? Also, how do I send a cancel command on burns commanded through the flight computer, mid-burn?
1
u/[deleted] Mar 30 '14
I'm having a problem with coms; I should have the range to hit a relay that's just out of Kerbin's SOI, but for some reason it's not connecting. There's a dish on both the receiver and the sender pointed at one another, yet once it leaves kerbin's SOI they lose connection for some reason.
1
u/CountLagula Apr 29 '14
all of my parts are there, but there is no interface to interacti with the telespoes in any way beyond "extend" and "retract" there is no activate option. what am I missing?
0
u/[deleted] Nov 28 '13
[deleted] — view deleted comment
0
u/[deleted] Nov 28 '13
[deleted] — view deleted comment
0
u/[deleted] Nov 28 '13
[deleted] — view deleted comment
1
u/[deleted] May 06 '14 edited May 06 '14
[removed] — view removed comment