Project Space Shuttle Vessel

[GLS]

Is there a good way to implement the payload IDs for the POS and ATT when using the RMS? And the auto modes?

Implement as in using that, or implement as in writing the code?
For the first one the answer is no, as that is not implemented. For the second one, yeah, you can write "REX - The RMS Executive" (sounds like a TV show title...) and the functions it calls, add the MCIU, and remove the exiting RMS code from the RMS system, which should only be doing the animation and attachment managment. The GPC side will need features that are coming for v2.0, so only after that could this be released.

 

[Tiny_Bob]

41C is going well so far

 

[GLS]

Release Tuesday!

SSV v1.16 is out! https://github.com/GLS-SSV/SSV/releases/tag/v1.16

Highlights of the changes for this version are an initial version of the CRT tone/mission/"whatever they were called" timers, which in conjunction with a new option to force x1.0 time acceleration when a C&W alarm is triggered, allows the user to set a MET and accelerate forward (don't go full bananas) until that MET, upon which the SM alarm will be triggered and bring time acceleration back to x1.0.
In addition, the Launch tab in Mission Editor has now been improved, allowing the OMS Assist parameters to be easily set in there. Plus, there are now parameters for the new IY vector targeting, which thanks to the ascent guidance improvements by @indy91, allows for precise orbital plane targeting. Please read the manual (section 7.2.4) for an overview of the options available.



For the future, work for v2.0 is still going on at full speed, the control segment architecture is mostly done, with only a few issues remaining, and much cleanup. Programs can now be scheduled and canceled in a more realistic way, which hopefully should result in less hacks in the future. E.g., the OMS engines were fired by scheduling the "OMS FIRE SEQUENCE" program, which would immediately issue the commands to open the required valves, and at the end of the burn it would close them, and cancel itself. Things like these are now "easy" to do.
Building on that, I've started with the SM OPS control segment, its executive and hybrid dispatcher, which is a mechanism to handle the call to functions in the correct order at the correct time. It will need some massaging to allow for the PAM function in the future, but so far the changes seem easy. The PLB software was already written +/- correctly, so I just have to call it in the new way. Also want to tweak the way bus I/O is commanded, integrating it more with whatever software is currently running. All this will break some ground for the GNC, which is still full of unknowns in the program and function orchestration side of things.
One big item up in the air is the BFS. Up until now there was a hack to show some BFS displays with limited data, but that is likely no longer possible. Given that during ascent and entry, the SM functions were effectively performed by the BFS (there was no memory or CPU for that in the PASS), and as data flow gets less and less "hacked", the lack of the BFS becomes more noticeable. I'm not sure how much effort it would take to add another GPC for the BFS, and have it just perform display functions: like in reality, it would need to spy on buses, but based on content and not timing, plus manage the CRTs with the other GPCs. I think I'll let this one sit for a while, think some more, and decide later on whether it should be done sooner or later.

 

[Tim13]

I've been playing around with the SSV mission editor today. Opened up the STS-101 mission that defaults, and walked through the SSV manual section by section. It all looks pretty straight forward, until you want payloads, but for me, payloads are a down the road thing. So I tested and saved the mission, and all was good. I then exported the scenario, and jumped into O24 to check out the launch to the ISS. After liftoff, I opened up a couple of the legacy MFD's just to see what was going on, and in the scenario, the ISS was going 'down hill' while I was headed 'up hill' with the rINC large and getting larger of course. Is there an easy way, with Better ISS, to set the RPOS/RVEL so the ISS is in a good position at launch date/time? I was looking at orbital elements for another mission, but don't know how to convert those to RPOS/RVEL format. I think, as long as I've used all the forms of Orbiter over the literal decades, I've struggled with this the most.

 

[GLS]

I've been playing around with the SSV mission editor today. Opened up the STS-101 mission that defaults, and walked through the SSV manual section by section. It all looks pretty straight forward, until you want payloads, but for me, payloads are a down the road thing. So I tested and saved the mission, and all was good. I then exported the scenario, and jumped into O24 to check out the launch to the ISS. After liftoff, I opened up a couple of the legacy MFD's just to see what was going on, and in the scenario, the ISS was going 'down hill' while I was headed 'up hill' with the rINC large and getting larger of course.

Wow, I never noticed that never used that mission for rendezvous, so...

Is there an easy way, with Better ISS, to set the RPOS/RVEL so the ISS is in a good position at launch date/time? I was looking at orbital elements for another mission, but don't know how to convert those to RPOS/RVEL format. I think, as long as I've used all the forms of Orbiter over the literal decades, I've struggled with this the most.

Stay tuned because eventually there will be a way to plan all this.
For now, to position a vessel using a TLE, you can use ScenarioEditorTLE, and then save the scenario at time which you want to start of the mission scenario (T-9m or 31s), and copy the state vector to the Mission Editor.
Beware that there are a few "collisions" between Orbiter and the real world, namely the time reference (TDB vs UTC), and the shape of the Earth in Orbiter which puts the launch pad in the wrong place, so don't expect to perfectly imitate the historical missions.

And now I better fix STS-101...

 

[Geoair2]

I can't figure out how to get the new targeting system to work for launch and what target to enter

 

[GLS]

I can't figure out how to get the new targeting system to work for launch and what target to enter

First:

Please read the manual (section 7.2.4) for an overview of the options available.

Second: getting the 3 parameters for the IY vector targeting is the tricky part... For the rendezvous missions, using an inertial IY vector, something needs to calculate it... which is still in work. For the "ground-track missions", the Mission Editor can calculate the Earth-fixed IY vector for an inclination, or an external value can be used.

 

[Geoair2]

For the moment there is no way to calculate the vector IY ?

 

[GLS]

For the moment there is no way to calculate the vector IY ?

Not officially... please wait, "good things come to those who wait".

 

[Tiny_Bob]

The Flight Design System that Indy made has that. It’ll be in my videos about SSV rendezvous most likely. I’m thinking of doing a video on planing a Rndz.

 

[Banshii59]

Doesn't DX9Client optionally level the terrain around bases?

Hey Dennis, I hope this isn't too far off the topic, but I am very new to SSV and I've overcome a lot of hurdles, but I have spent hours trying to figure out why I keep getting "illegal entry" after loading tgt data in OPS301. I tried several different FDO-MFD solutions but I'm at a loss. Do you have any ideas what I might be doing wrong? I have followed the checklist meticulously and I have watched other missions on YouTube to pattern after other Orbiteers. Has this ever happened to you and what did you do to solve it?

 

[dennis.krenz]

Hey Dennis, I hope this isn't too far off the topic, but I am very new to SSV and I've overcome a lot of hurdles, but I have spent hours trying to figure out why I keep getting "illegal entry" after loading tgt data in OPS301. I tried several different FDO-MFD solutions but I'm at a loss. Do you have any ideas what I might be doing wrong? I have followed the checklist meticulously and I have watched other missions on YouTube to pattern after other Orbiteers. Has this ever happened to you and what did you do to solve it?

First of all, what is your scenario? Second, which checklist do you follow? Third when do you get the illegal entry message exactly, at which time and after which command?

There are many not that many possibilities for an illegal entry in a maneuever program, but its its hard to tell with that little information, which case you triggered.

 

[Banshii59]

First of all, what is your scenario? Second, which checklist do you follow? Third when do you get the illegal entry message exactly, at which time and after which command?

There are many not that many possibilities for an illegal entry in a maneuever program, but its its hard to tell with that little information, which case you triggered.

Scenario: STS-107 Launch Checklist: SSV Checklist Addon. I get the illegal entry after loading PEG4 info. BTW, the items 16-18 don't seem to stay on the page. When I attempt to input the item 18, it "blanks out" as if the info won't all fit.. I've also tried the VX,VY,VZ data. After I managed to get the info on the OPS301 Pg, I enter item 22 that's when the illegal entry " is triggered

 

[indy91]

Scenario: STS-107 Launch Checklist: SSV Checklist Addon. I get the illegal entry after loading PEG4 info. BTW, the items 16-18 don't seem to stay on the page. When I attempt to input the item 18, it "blanks out" as if the info won't all fit.. I've also tried the VX,VY,VZ data. After I managed to get the info on the OPS301 Pg, I enter item 22 that's when the illegal entry " is triggered

Items 14-18 (PEG 4) and items 19-21 (PEG 7) are mutually exclusive as inputs. If you enter any item 19-21 then items 14-18 get blanked.

Illegal entry on item 22 can only really happen if you are in MM 303 or if the input TIG is illegal. That would be the case if the TIG is more than 5 minutes in the past or more than 12 hours in the future.

 

[Banshii59]

Items 14-18 (PEG 4) and items 19-21 (PEG 7) are mutually exclusive as inputs. If you enter any item 19-21 then items 14-18 get blanked.

Illegal entry on item 22 can only really happen if you are in MM 303 or if the input TIG is illegal. That would be the case if the TIG is more than 5 minutes in the past or more than 12 hours in the future.

I appreciate the input. It was some good information and I was able to get past that point and get item 22 to accept my input. Many thanks, Indy.

 

[Banshii59]

First of all, what is your scenario? Second, which checklist do you follow? Third when do you get the illegal entry message exactly, at which time and after which command?

There are many not that many possibilities for an illegal entry in a maneuever program, but its its hard to tell with that little information, which case you triggered.

I did get some good info on the matter, but thank you for your effort. Cheers

 

[Banshii59]

I have a question about the OPS202 (ORBIT MNVR EXEC) I am using this to load my tgt date from the FDO MFD calc. What I'm trying to do is change my alt on the next apogee/perogee point. I'm inputing PEG4 info that was calculated but then when I tried to input item 22/23/27, I get illegal entry. Am I missing a step? Anyone with expertise in this would be greatly appreciated. I have read the SSV manual provided on this topic on pg25 but it didn't give me much info.

 

[GLS]

when I tried to input item 22/23/27, I get illegal entry.

On which ITEM entry are you getting that?
Could the time be wrong, i.e., in the past?

 

[Banshii59]

On which ITEM entry are you getting that?
Could the time be wrong, i.e., in the past?

After loading TGT, Item 22 gives me the issue. My data is 45 min into the projected burn. My FDO info was a simple 30 min Threshold with a sec HD 150

 

[GLS]

After loading TGT, Item 22 gives me the issue. My data is 45 min into the projected burn. My FDO info was a simple 30 min Threshold with a sec HD 150

Can you post an image of the OMS MNVR display? (if you can't, then post exactly what is being entered into which item)