Comments (9)
It probably means you burned a very good TLI ;) I would not worry about it, you will most likely get a burn pad for MCC-3 or 4. When the mission tracking detects than an MCC will be below a certain delta V threshold, it will scrub the burn, so yes, your trajectory is very good.
from nassp.
Hello. Thank you very much, it was what I thought, it was just to confirm :).
Best Regards.
from nassp.
It is possible that both MCC-1 and 2 are getting scrubbed, but the threshold for this (5 ft/s burn or less) is fairly low. So if you are getting a very large MCC-3 or 4 solution later on, then there still might be something wrong. So let me know if that is the case. But it's quite possible that you just had a very good TLI.
from nassp.
Hello
Okay, if that happens I'll report thank you. Just one more question, since I did not have MCC1 and MCC2, I decided to update my state vector through ApolloRTCCMFD since I was not having values below 100 in CisLunar navigation. After that Cislunar navigation started to go well! There is no problem in doing this update in ApolloRTCCMFD on an MCC mission, right?
from nassp.
Yeah, no problem at all doing updates from the RTCC MFD as well. I noticed the issue you are having with a lack of state vector updates due to scrubbed burns when I implemented the MCC-H support for Apollo 10. And on the actual missions they did get state vector updates at those times, so for the Apollo 10 MCC support I already implemented those alternative updates. So if the burn gets scrubbed, then you are getting a SV update anyway. Just haven't gotten around to retroactively implement this for Apollo 8, but I certainly will at some point.
If you are playing around with the RTCC MFD anyway, then you might as well check the DV of the burns that were scrubbed for you. Here is the general procedure to calculate MCC-1 and MCC-2: Open RTCC MFD, click on Maneuver Targeting, then Translunar. Click once on MAN to get to the maneuver option number 2. Click on TIG and input the MCC-2 time of ignition. After a short iteration it should give you a maneuver solution. If the DV for that is below 5 ft/s then everything is good. If it is larger or it doesn't find a solution at all, then there is a problem. Burn getting scrubbed because something is going wrong, not because things are going great.
from nassp.
Hello
Thanks for the sugestion. I used the RTCC MFD in the translunar program at my current get (30h14) and got values below 5 ft / s (dVC- 3.8 ft / s) as shown below:
https://puu.sh/BabyL/61b61da752.png
After that in GET 45h16 i checked the RTCC MFD in the translunar program and already had a value of dVC 6.0 ft / s:
https://puu.sh/Baltg/fbc53939b5.png
With these values I figured that MCC3 had to appear if everything was correct and appeared :)!
https://puu.sh/BalPp/c14df760f0.png
The burning dVC (6.7) is concordant with the dVC obtained previously, so I think things are really going well! Tomorrow i hope to be in moon orbit!
I'll ask one more question, when I was at a GET of + - 44h I had to make Cislunar to four stars (33,37,45,42). I started to have problems when making the first star, the PGNS light started to light up and i tried several times and still the same.Then I noticed that all the stars were too far from the earth's horizon and consequently out of reach of the SXT field. So I decided to choose a group of 4 stars closer to the earth (23,20,24,22). I had to cislunar without problems and with good values under 50. Is there or can there be a problem for doing this?
thank you
from nassp.
Ok I now i now its for Moon Horizont...right?
from nassp.
The cislunar navigation starting at 45h GET is using the horizon of the Moon, yes. In the flight plan that is the codes LNH (Lunar Near Horizon) and LFH (Lunar Far Horizon). So no wonder the stars were too far away from the Earth horizon, haha. You have to use a different option code in P23 for that and of course the horizon of the Moon now.
You are on an impressive trajectory I have to say, haha. Smallest DVs for the translunar MCCs I have seen so far. All thanks to using the historical TLI targeting parameters for Apollo 8, which have been available to us for about a year. Only burning MCC-3 will show another small problem with the current MCC mission support logic, because MCC-4 is currently never scrubbed on Apollo 8. So you will likely get something like a 0.1 ft/s DV for MCC-4. On the real mission the only criterion for scrubbing MCC-4 was a DV below the uncertainty of the radar tracking of the spacecraft. About 0.5 ft/s. So if you get a MCC-4 solution below 0.5 ft/s, you can decide if you even want to burn it, your choice.
from nassp.
Hello
Just to say that the MCC4 occurred with a DVC of 0.7, but I did the maneuver anyway. I've already reached the orbit of the moon. Thank you for your support.
Best regards
from nassp.
Related Issues (20)
- LM landing gear deployment causes RCS plume to become displaced HOT 1
- Building fails on Archlinux with error HOT 3
- Apollo 12 MCC2 PAD Bug HOT 3
- Add handles/functionality for LM RR stow and VHF EVA antenna HOT 1
- ABORT light in CM should be red, not yellow HOT 1
- Hardcoded Values for Textures and Materials HOT 1
- AGS from OFF to STBY or STBY to ON does not signal AGS CW light
- Lat/Lon within Apollo Navigation Landmarks.mkr should be updated HOT 7
- CSM Running lights "always on" need to be switchable HOT 1
- Virtual Cockpit GPI trim wheels dont save position/round when scenario reloaded HOT 1
- Add Waste Dump dV and turn off particle effect when tank is empty
- Add O2 and H2 tank control modules HOT 1
- Add Compressabiity Lookup Tables from NIST Data for liquid phases HOT 1
- Rocket won't show up on OpenOrbiter HOT 6
- MED P13 and P14 not working
- PQGS Circuit Breaker Misspelled in LM (Panel 16) HOT 1
- LM Loses S-band signal when CSM enters LOS
- LM RCS issues with Vesim enabled
- Cue Card Disappearance HOT 2
- LM LCA Implementation
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from nassp.