/moon-dog-technologies

Library for High-level scripting of missions in Kerbal Space Program using KOS

Primary LanguageKerboScriptMIT LicenseMIT

Moon Dog Technologies Software Repository

The Moon Dog Technologies Consortium was the dream of one man, and now that of several dozen citizens of Kerbin.

Herein you will find a full featured suite of navigational software built in the kOS framework, and features and utilities to accompany the instructional videos on YouTube.

Major Features

  • Interactive Shell
  • Highly flexible, and extensible launch system.
  • High-level Mission Scripting
    • Allows for adding prebuilt programs to custom sequences.
    • Rapid mission automation
  • Assignable firmware

Quickstart

Set your kOS core boot file to ish.ks to start in interactive mode. Once at the prompt, type help.

Non-interactive mode has multiple entry points. If you know your way around kOS, start in the boot folder.

  • lv.ks
  • payload.ks

You can ignore the others, for now. Basically...lv.ks checks the core:tag for parameters. Either, give it: [LAUNCH VEHICLE NAME], [INCLINATION], [LAN], [ORBIT ALTITUDE], or specify a .launch file.

Other Resources

Satellite Constellation Designer

Most Recent Changes

22SEP2023

  • Is there anyone out there? If you have been using any enjoying this system, it would be great to hear some feed back. Just email the captian via gmail.
  • On the off-chance that there are any of you out there, I'm trying to be more polite, by respecting your expectations, but I may still break things.
  • I this release, I've tried to make things easier by changing the "add-program" ISH command with "Q", as in Queue this program. It is by far, the most common command I use, so this should make life easier.
  • Added a "countdown" program so you can add a simple countdown in the MISSION_PLAN.
  • Also tuned the docking program.

06JUL2023

  • Streamlined circularize program and added more helps.

05JUL2023

  • Empty core:tag now fails as is intuitive.
  • Specifying a ".launch" is required to source launch parameters from the launch.conf directory.

21JUN2023

  • Added online help to th interactive shell
  • Uploaded a video of it to YouTube
  • Fixed a bug in setup-launch

08JUN2023

  • Fixed a bunch of bugs and made some quality of life improvements in the Interactive SHell system.
  • Changed some of the commands to be more Spacey.
  • Status and Countdown lines should be displaying properly now.

Automated missions are increasingly easy to setup. The initial launch system is stable, and understands how to hand-off control to payload and mission firmware. payload.ks boot file now can load mission firmware and transition to it. lv.ks can transition to payload.ks on the same core, when using the launch.conf/current.launch parameters file.

Automated constellation deployments tested with the lv/Chihuahua.ks launch vehicle and the craft file you can find here: Model craft To try it yourself, use the lv.ks bootfile on the upperstage, and ensure that the core:tag is empty. Add your parameters for the LV and payload to launch.conf/current.launch, make sure that all the satellites have payload.ks as boot file, and `[Sat Name]:[Mission], [param1], ..., [param n] in the core:tag. (It should be ready out of the box. Just click launch, and it should automatically deploy a constellation of 4 satellites.).

Libraries

The libraries are Scope-Lexicon-Delegate libraries inspired by gisikw's KNU system.

Disclaimer

While these routines have been used successfully on occasion, they come with ABSOLUTELY NO WARRANTEE. Use at your own risk.