KSP MOCR (Mission Operations Control Room)

[Tunefix]

 

A standalone program that connects to a kRPC-server, and displays spacecraft/flight/orbital data.
There are several screen with different types of information on them, i.e. Engine data or Resources data.
There are also several screens that displays graphs of data, i.e. Altitude vs. Inertial speed, G-force and Dynamic pressure, Roll-Pitch-Yaw graphs, and more.
A resize-able map view shows the current position of the spacecraft with ground-track history.

Releases:
https://github.com/Tunefix/KSP_MOCR/releases/

Documentation: (The little that exists)
https://github.com/Tunefix/KSP_MOCR/blob/master/README.md

All the best,
  Tunefix.

Spoiler

 

 

Edited March 24, 2018 by Tunefix
new version released

[tryinghard]

I like this, and would really like to see it released   

[Tunefix]

Cool,

Development have continued on gitHub.
No releases are made yet, but anyone can build it with VS2015 or newer. (.NET 4.6)

https://github.com/Tunefix/KSP_MOCR

[Tunefix]

Alpha 1, can be tested now:

https://github.com/Tunefix/KSP_MOCR/releases/tag/A1

It comes with a new and improved FDAI:

Edited April 25, 2017 by Tunefix

[tryinghard]

Amazing work

[santiagokof]

my my.... can u make your mod show map view? if u can, ill buy it!

[Tunefix]

Current screen for FIDO calculations:

This is not using the games maneuver node-system. Istead it calculates the orbit resultant from burn parameters. It can also iterate through an orbit in steps of either 5 seconds of 1 second.
First use the [Iterate 5] to get close, and then the [Iterate 1] (witch takes a looong time to run) to get closer.
The result can then be relayed to the pilot, who can then set up his FDAI to show the correct burn attitude.

Then after the burn, you can see the new orbit-data from the game in the left column. Then it's time to calculate a mid-course correction!

A bit old-school, but thats half the fun.

It uses point-burns, so the person manning the Booster-position will have to calculate how long the burn needs to be to achieve the total deltaV, and when to start the burn. (Nominally FIDO TIG - (burntime / 2))
And the burn-angles are in a inertial reference frame.

Edited May 2, 2017 by Tunefix

[Tunefix]

Map view with ground track history:

[Mecripp]

This looks alot like

and nice work

[Tunefix]

@MeCripp,
Yes it does look like Telemachus. That was how i started this project, me wanting something more 1960's Apollo-style stuff. And more numbers, in addition to the graphs.
And then I found that kRPC was better suited to my use. And I tought i could share it also!
:-)

 

Oh, and with our own PySSMQ-server for inter-ksp_mocr-clients-data-exchange, you can have this (For those GO/NO-GO rounds):

Edited May 10, 2017 by Tunefix

[Uace24]

Does this work with RSS/RO?

[TheRagingIrishman]

I just saw this and I gotta say @Tunefix this is really freaking cool. 

[Tunefix]

On 30.7.2017 at 3:14 AM, Uace24 said:

Does this work with RSS/RO?

Have not tried, just used it with vanilla so far.

Status Update:
Not much have happend in a long time, because, you know, life, summer, and everything.
When fall comes, and the nights again get dark, I should get more time to move this forwards.

[Tunefix]

Finally, things are moving again.

Alpha 2 is released!

Check original post for more info.

[Tunefix]

Alpha 3 is now out.

Changes:
* Partial rewrite of graph-system, to get more flexibile graphs.
* Added a few new graphs.
* Added very approximate guides to some graphs, for launch trajectory. (screens 51, 53, 54)

[drtedastro]

great work.

many thanks for updates and keeping this alive.

Cheers.

[Tunefix]

8 minutes ago, drtedastro said:

great work.

many thanks for updates and keeping this alive.

Cheers.

Yeah, I got stuck in a kind of rut. Turns out; Rocket Science is HARD. And orbital mechanics; EVEN HARDER!
Who would have thunk!

So I am now dealing with more low-level issues, like graphs.
Will brush up some of the map-stuff next, like a button to turn the "tail" on/off, turn fading of the tail on/off, and setting tail length.

Suggestions are also highly appreciated.

[Tunefix]

Alpha 4 now available.

Changes:
* Added H/Hdot-graph (screen 55)
* Added some controls to map-view (sceen 8), show/hide tail, set tail length, fade tail

A badly managed launch. (But orbit acheived 117km by 75km)
The red line is a rough ballpark guideline. The target apoapse can be set in screen 1 (Ascent), and the max HDOT then adjusted if necessary.

Edited March 2, 2018 by Tunefix
typo

[SupperRobin6394]

How does this send/receive data from/to KSP, can you enlighten me?

I loved Telemachus which was a bit alike this, but it had big time performance issues for me (mainly RAM) so I was sorta forced to remove it.

[Tunefix]

47 minutes ago, SupperRobin6394 said:

How does this send/receive data from/to KSP, can you enlighten me?

I loved Telemachus which was a bit alike this, but it had big time performance issues for me (mainly RAM) so I was sorta forced to remove it.

This sends/receives data from KSP via the kRPC-plugin.

[Tunefix]

Alpha 5 is out.

Biggest changes are new look of some panels/screens.
Also I have added an Event Indicator panel for FIDO, and one Event Indicator panel (out of 4) for EECOM.
The layout of these panels are as they were during Apollo 15. They have no functionality in KSP_MOCR,
but are  more a display of possibilities.
 

[Tunefix]

Alpha 6 is out!

The biggest change is the look of the telemetry-screens. They are now more in a CRT-style, and with a 4:3 aspect ratio. I also found while doing research a specification for the charactron that generated these screens during Apollo, so i have made font-sizes of the CRT-screens as close to this spec as possible, in terms of number of chars pr. line, and number of lines.

Changelist:
 * Pilot-screen (#100) diabled. (So many things were wrong there, and it did bad things)
 * New screen for FDAI (#101)
 * Added error needles and roll rates to the FDAI
 * New screen for DSKY (#102) (Not wery functional, but the look of it)
 * Started rewrite of AGC, and added button on main form for starting/stopping it. The AGC should only be running on one instance of KSP_MOCR, preferably the same that will use the DSKY. The state of the AGC is then transmitted to other instances via PySSSMQ.
 * New screen: Temperature (#7). Shows the hottest parts, parts with ablator resource, and radiators.
 * New screen: Consumables (#3). Show parts that contains either liquid fuel, oxydizer or monopropellant.
 * New screen: Electrical system (#6). Show parts that either uses, generates or stores electricity.
 * Redone screen: Booster (#2). The booster screen is completly redone.
 * Redone screen: Orbit View (#4). Removed the old FIDO-screen (whitch did'nt work), and replaced with simple orbit-view. (Inclination not included)

And now, many pictures to show off the new screens.

 

Edited March 24, 2018 by Tunefix
Imgur albums don't work...

[Stone Blue]

Sweet mod... Good job

I was just wondering, and I assume so, but we kno how assuming can end up.. but will this work alongside Telemachus?
I like the ability to use some of the touch control button screens of Telemachus...

[Ericwi]

10 hours ago, Stone Blue said:

Sweet mod... Good job

I was just wondering, and I assume so, but we kno how assuming can end up.. but will this work alongside Telemachus?
I like the ability to use some of the touch control button screens of Telemachus...

I can confirm with you in 1.4.1 Telemachus\Krpc and this seems to be working ok with each other.

[Tunefix]

If you have a suggestion for a CRT-screen, I have added my template sheets to the git.
They makes is easy(er) to layout text and values.

Font-size 3 is the middle-of-the-road choice, and I have used that for everything, except the conusables-list (screen 3)

https://github.com/Tunefix/KSP_MOCR/raw/master/CRT-template.pdf