How to assemble & configure a complete SDHI CSM stack
The following guide demonstrates how to assemble and configure a complete Command-Service Module (CSM) stack using the parts included in the SDHI Service Module Systems pack.
Ensure that you have installed the latest version(s) of all the required dependencies.
1) Place a Mk 1-2 Command Pod (from the Pods tab) into the assembly area
2) Right-click on the Mk 1-2 Command Pod and click Install Umbilical Port
The umbilical port is a static model with no actual functionality, but provide a visually-plausible justification for the flow of resources between the pod and the Service Module. This port can be toggled off if you are building a vessel that does not use the Service Module system.
3) Add the SDHI 2.5m Heat Shield (from the Structural tab) to the bottom of the pod
You may also wish to make sure that the auto-triggering inflation collar is enabled, by right-clicking on the heat shield and checking to see if the Auto Deploy option is Enabled.
4) Add either the Clamp-O-Tron Docking Port - Parachute version or the IACBM 1.25m - Parachute version (from the Utility tab) to the bottom of the pod
Your choice of docking port depends on what sort of vessels you plan to dock with - the Clamp-O-Tron version is compatible with the classic Clamp-O-Tron docking port from the stock KSP game, while the IACBM used for FusTek Station Parts.
For the purposes of this guide, we're using the Clamp-O-Tron version. Make sure its staging icon (the parachute symbol) is in Stage 0.
5) Add the SDHI 2.5m Service Module (from the Propulsion tab) to the bottom of the stack
Make sure that its staging icon (the horizontal decoupler symbol) is in Stage 1. This is mainly for visual clarity during assembly, as we will see shortly.
6) Add the LV-909 Liquid Fuel Engine (Fairingless) (from the Propulsion tab) to the bottom of the stack
This is a special version of the stock LV-909 engine that does not come with automatic fairings, since we will be encapsulating the Service Module within its own fairing system.
Make sure that its staging icon (the liquid rocket engine symbol) is in Stage 2.
7) Add the SDHI 2.5m Service Module Adapter (from the Aerodynamic tab) to the bottom of the stack
Make sure that its staging icon (the horizontal decoupler symbol) is in Stage 2, along with the LV-909 engine. You don't want to confuse it with the Service Module's built-in decoupler.
8) Add solar panels, RCS thrusters, antennae etc. to the recessed ribbed surface of the Service Module
The fairing panels we will add in later steps will protect these from aerodynamic stresses during launch.
Here we're using a mix of stock and third-party add-on parts; feel free to choose accessories that best fit your specific mission requirements.
9) In Action Group editing mode, assign all your solar panels, antennae and any other items you want to deploy in orbit to Custom02
When the Alpha2 key (2 in Windows) is pressed in-flight, this will automatically deploy all of your accessories simultaneously, instead of having to extend/retract them one-by-one.
10) In Action Group editing mode, assign the Service Module's Decouple action to Custom03
When the Alpha3 key (3 in Windows) is pressed in-flight, this will decouple the command pod from the Service Module. This should be reserved for normal / end-of-mission decoupling, as we will be handling abort scenarios separately.
This decoupler was deliberately designed not to be staged, to prevent accidentally leaving a command pod in orbit without a means to retro-burn.
11) In Action Group editing mode, assign the parachute-equipped docking port's Deploy chute action to Custom04
When the Alpha4 key (4 in Windows) is pressed in-flight, this will initiate the drogue-mains parachute deployment sequence.
12) Add the SDHI 2.5m Service Module Fairings (from the Aerodynamic tab) to the floating "helper" attach nodes on the adapter
Make sure that their staging icons (the vertical decoupler symbols) are in Stage 3, as the fairings need to be jettisoned before the CSM stack separates from the rest of your lifter rocket.
TIP: To place the fairings on both sides simultaneously, set your Symmetry Mode to 2x and enable Angle Snap.
13) Add the SDHI Mk1-2 Pod Boost Protective Cover (from the Aerodynamic tab) to the stack node on top of the docking port
The slot cutout in the BPC should be aligned with the umbilical on the Service Module.
Make sure that its staging icon (the horizontal decoupler symbol) is in Stage 4, as during normal flight, the BPC needs to be jettisoned before the side fairings.
14) Add your choice of Launch Escape System (LES) or Escape Tower
Here we're using the KSPX Escape Tower, but you may use any other similar abort systems from third-party add-ons (or even build your own from stock parts).
In all cases, make sure that their associated staging icons (such as the solid booster rocket symbols) are in Stage 4, as during normal flight, the abort system will be jettisoned along with the BPC.
15) In Action Group editing mode, assign the side fairings' Decouple action to Custom02
When the Alpha2 key (2 in Windows) is pressed in-flight, because the fairings are bound to the same action group as all the orbital accessories described in steps 8) and 9), they will automatically jettison just before the accessories are deployed.
16) In Action Group editing mode, assign the Boost Protective Cover's Decouple and Active Engine actions to Custom10
When the Alpha0 key (0 in Windows) is pressed in-flight, the BPC will be jettisoned from the CSM stack.
A couple of things to note:
- It may seem redundant to manually assign an action to jettison the BPC, when it is already going to be staged during normal flight. However, after triggering an emergency abort sequence, it is preferable to be able to discard the BPC with one keypress rather than spamming the spacebar to trigger it via staging.
- By itself, the decoupler on the BPC does not provide sufficient force to push itself away from the Command Pod (stronger decouplers would have destroyed the parachute-equipped docking ports). Hence, a number of miniature solid rocket boosters have been added to the BPC to gently push the cover away from the pod.
17) In Action Group editing mode, assign the Service Module's Decouple and the Escape Tower's Activate Engine actions to Abort
When the Abort key (Backspace in Windows) is pressed in-flight, the Command Pod will be severed from the Service Module and be pulled away by the Escape Tower.
18) Build the rest of your lifter rocket
TIP: Have your second stage main engine in the same stage as the Boost Protective Cover and the Escape Tower, so that during normal flight the latter items will be discarded when the second stage engines are first fired.
- Custom02: Side fairing jettison, deploy solar panels / antennae
- Custom03: Command Pod / Service Module decoupling (normal, end-of-mission)
- Custom04: Deploy / arm drogue-mains parachutes
- Custom10: Boost Protective Cover jettison (post-abort)
- Abort: Activate Escape Tower, Command Pod / Service Module decoupling (emergency)
- If you have access to the Info Popup feature from the Firespitter plugin (e.g. Firespitter's FS3I Info popup, B9 Aerospace's Info Drive), you can add such a part to your vessel and use it to document the aforementioned Action Group settings, as an in-flight manual of sorts.
- If you wish to use the SDHI Heat Shield but do not need a fully-fledged Service Module, or are building your own propulsion trunk out of stock parts, you can use the SDHI 2.5m Avionics Ring (from the Structural tab) instead.
- If you are using a launch clamp as a crew access walkway (e.g. FASA Launch Tower) connected to the Boost Protective Cover on the Command Pod, assign the clamp to the Abort action group, so that in case of an pad abort, the pod can fly clear of the launch pad.
- The flag icon on the Boost Protective Cover can be toggled on or off via the ToggleFlag option in the right-click context menu.
