Block E for Vostok rocket (Lunar version)

Version 1.0

Build: 24.01.2009

Orbiter addon by Andrew Thielmann (igel)

atil@pin-plus.ca

Block E is a third stage of the Russian Vostok rocket, from the famous family of the R-7 -derived rockets.

Vostok rocket is most known for its orbital missions, especially the first-ever human space flight of Yuri Gagarin on 12 April, 1961. However, by the time of this most famous flight, it had already carried a number of the unique lunar "firsts". This addon is specifically concentrated on these early lunar shots.

Block E flown on the lunar missions was very different from its orbital cousin. Other than a shorter body (housing an understandably smaller payload), it carried a reasonable set of scientific instruments and additional antennas, making it the space probe of its own. Two first flights also had a most unique piece of hardware on board: an artificial comet generator. On the way to the Moon, this instrument created a huge cloud of sodium vapours, visible from the Earth even to the naked eye! The goal of this experiment was to calibrate the still-unreliable radio navigation with the ever-robust astronomical means.

Credits

Thorton (Nikita Vtyurin) - meshes and textures

astronavt (Dmitry Pritykin) - base R-7 addon

Big thanks to all beta testes for tons of valuable feedback!

Requirements and Compatibility

This addon is designed for Orbiter 2006 P1.

This addon requires R-7 project by astronavt. In other words, it is specifically designed for and tested with this addon. Many of its "out of the box" scenarios reference this addon and will crash without it, unless modified.

However, addon may [happen to be] compatible with other R-7 addons (and maybe even with other rockets!)

Payloads

Here is the list of three famous payloads launched by Vostok rocket using block E in the direction of the Moon:

You can substitute historical payloads with your custom payloads. Block E addon supports fully automated launch into the direct non-ecliptic translunar trajectory.

Autopilot and Trajectory

Historical block E autopilot was strictly pre-programmed on the ground. In this addon, the autopilot is more "smart". It activates during separation from the 2-nd stage. At this moment it "locks" on its target (the Moon!) and tries its best to calculate the achievable interception trajectory. Its success hugely depends on the proper launch time of the primary rocket. Block E can provide some compensation to the launch time errors- but very little! For best results, stick historical mission times. Otherwise, some trial and error may be required to find a reasonable launch window.

Vostok rocket with the block E was using Direct Accent Trajectory to fly to the Moon. No interim orbits, no timed burns, no midcourse corrections. The fastest way to get to the Moon, but unfortunately the least accurate. Luna-1 can tell the story...

Because of the high latitude of the Baikonur space port, all lunar trajectories flown by Vostok rocket were highly inclined, almost perpendicular to the ecliptic plane.

At the end of the block E burn, you'll almost certainly will see some pitch occilations. This is normal. Historical block E did not have them - but it did not have to fly the flexible trajectory that requires constant adjustments. And lacking the movable steering thrusters or gimballed engine, the only way to steer for block E is to turn the whole thing into the proper attitude.

By default, block E will try to hit the Moon square on! If you are launching Luna-3, or trying to recreate a flight of Luna-1, this might not be what you want. In this case, switch trajectory over to the FLYBY mode by overriding the corresponding scenario variable.

If you take block E off autopilot, be aware that, like with any realistic addon, its fuels supply is very limited and tightly set to make it "just right". If you deviate too far away from the optimum flight path, and then return back to autopilot, it may be too late to fix the trajectory...

Block E does not have normal jet attitude control thrusters, only those that are part of the main propulsion system. So, manual attitude control is unavailable when the main engine is not running. And when it is running, the only preprogrammed navigation mode available is KILLROT.

"Artificial Comet"

This addon implements the unique "artificial comet" feature that became a hallmark of the lunar version of block E. The "comet" has to be explicitly set in the scenario file. It fires automatically at a distance of 130 Mm from Earth. The firing length is one minute, during which the time acceleration is disabled. The comet provides a very rewarding view both from the block E point of view and from the payload that it had been carrying.

Rocketcams

The historical block E did not carry any rocketcams. We, however, have no reason to miss the opportunity for good views. Block E has no "cockpit" - but carries three rocketcams. All three rocketcams are mounted on the side, off the rocket axis, for more interesting views. The first, default rocketcam, looks down. It is best used during ascent phase. Second rocketcam looks at the payload from aside. It also provides nice views - as long as the payload shroud is separated. The best show, however, happens during payload separation: the camera tries to follow the separating payload. But you may have to do a little trick to see this. By default, immediately following payload separation, Orbiter's focus will be switched to the separating payload. In most cases, this is exactly what you want - but not if you want to enjoy the view of the space probe slowly drifting away. In this case, press Ctrl+J key combination prior to payload separation - this will suppress automatic focus switching. Third rocketcam looks straight forward. It can also be used during payload separation, and may provide some good views during the run of the "artificial comet". But the main reason to have this camera was to provide a generic "forward" view for those brave enough for the manual control mode. The cameras are rotated by "C" control key.

Crashes and Burns

Block E is fragile! It won't survive many events that are considered normal in the ultra-forgiving Orbiter universe. If you - accidentally or intentionally - drop it on the ground, or crash it into the Moon, or send it on a fiery atmospheric reentry course - prepare for harsh consequences!

Scenario configuration

Payload. To specify and attach payload, substitute the payload name and adjust attachment parameters: 
  PAYLOAD xxx
  APOINT 0 0 -Z
  PDIR 0 0 -1
  PROT 1 0 0

Trajectory type. Skip this parameter for the default direct impact trajectory. To intentionally miss the Moon by a narrow margin, set the following scenario variable: 

  FLYBY 1

Artificial comet. To set the comet to be automatically activated en route to the Moon, set the following scenario variable: 

  COMET 1

Control keys

C cycle through rocketcams in the cockpit view;
M toggle between manual and autopilot mode;
J separate payload;
Ctrl+J     toggle focus switching for the oncoming payload separation;
+ start main engine;
- stop main engine.

* * *