Meadville Space Center
Welcome, Guest. Please login or register.
January 25, 2021, 02:47:10 PM

Login with username, password and session length
Search:     Advanced search
Project Apollo Beta 7.0 released!
25068 Posts in 2094 Topics by 2266 Members
Latest Member: Apollo Next
* Home Help Search Login Register
  Show Posts
Pages: [1] 2 3 ... 88
1  Project Apollo - NASSP / Project Apollo - NASSP Development / Re: TLI PAD on: June 16, 2018, 11:56:47 AM
Wait, when did you try to calculate the TLI PAD? Before or after TLI? The calculation doesn't work after TLI.
2  Project Apollo - NASSP / Project Apollo - NASSP Development / Re: TLI PAD on: June 16, 2018, 07:28:05 AM
I am using Orbiter 2016 and NASSP Alpha Orbiter 2016 1192. When I try to calculate the TLI Pad to get the Sep Angles in ApolloMCC MFD the program freezes any idea why?

Does the RTCC MFD freeze or Orbiter? There are some bugs currently, causing CTDs when using the MCC scenarios. I haven't been able to find the cause yet.
3  Project Apollo - NASSP / Project Apollo - NASSP News & Discussion / Re: NASSP moving to Orbiter Forum? on: May 23, 2018, 03:43:54 AM
Seems like the vote was won 10:1 for moving to the Orbiter Forum. Obviously our current forum is trolling us right now, because I have experienced no issues at all in the last 4 weeks. But I am sure the issues will come back eventually. I'll talk to the Orbiter Forum admins to start the process of giving us a developer section!
4  Project Apollo - NASSP / Project Apollo - NASSP Development / Re: V8 Release Work Thread on: May 23, 2018, 03:41:33 AM
Yeah, because P52 still has to complete the fine alignment, even with an uplinked REFSMMAT. And I don't recall V42 being done via ground uplink for any reason...

Yeah, the IMU wouldn't be adjusted through a mission with a V42, but by updating the IMU and PIPA biases. That's the reason for the crew reporting the gyro torquing angles of their P52s to Houston. They calculated new biases from those numbers and if they were very different from what is currently in the AGC, then they would uplink updated values.
5  Project Apollo - NASSP / Project Apollo - NASSP Development / Re: V8 Release Work Thread on: May 13, 2018, 06:09:01 AM
It would also be fairly pointless to implement, because once our IMU can drift we would simply compensate that drift with the AGC padload, which would send torquing pulses back to the IMU to adjust the attitude every so often for the drift compensation. Same for the PIPAs. This part of the padload is of course all set to 0 right now. So it just seems like an unnecessary complication and potential source of issues. It doesn't add realism because in the end, with the compensation in the AGC, everything would be just like before.
6  Project Apollo - NASSP / Project Apollo - NASSP Development / Re: V8 Release Work Thread on: April 29, 2018, 07:22:52 AM
I have some basic questions about DAP. When I'm prompted to enable DAP V48E (according to checklist), the total weight will be specified. My question is, should I use the weight specified in the Orbiter info tab (kg) or should the weight given in 06 47 (LBS) DSKY be used? Despite conversion to LBS, it is not the same weight. The weight specified in the Orbiter info tab does not correspond to the weight in DSKY.

The weight in Noun 47 changes automatically during a SPS burn, but it doesn't take any other weight loss into account, like RCS firing. So occasionally you will need to update it. Maneuver PADs usually have an updated weight and the RTCC MFD also has a "DAP PAD" page, that you can use to get an updated number for the weight. And it's always going to be in pounds of course.

My second question is, how do I disable DAP? I understand that DAP is enabled with V46E but how do I disable DAP without using FREE (CMC MODE)? Hope the question is understandable.  Happy

The first digit in register 1 of Noun 46 (so just when you did the V48E) is the basic DAP configuration:

0 = DAP disabled
1 = CSM alone
2 = CSM/LM docked
3 = CSM attached to S-IVB
7  Project Apollo - NASSP / Project Apollo - NASSP Development / Re: V8 Release Work Thread on: April 26, 2018, 05:46:45 AM
Thank you for a very interesting and fun simulator! The simulator is a really difficult challenge, at least for me. I'm in Apollo 7-04 Before Phasing Maneuvering and wondering if something is wrong with the translation feature. Whatever I do, I do not get the translation to work. Are simulation scenarios of Apollo 7 broken in v 8? I also wonder if I'm expected to change my attitude in that scenarie? I need more careful instructions to understand what I am doing.  Happy


Those are the scenarios that came with NASSP 7.0 and they haven't been updated since. So they are a little bit outdated in some ways. Your specific problem was caused by two simulated relays being moved from one CSM subsystem to another. All you have to do is enable the RCS again. On panel 8 make sure the two SEQ EVENTS CONT SYS - ARM circuit breakers are closed. Then on panel 2 switch RCS CMD to On. That should do the trick and enable the normal rotation and translation modes again. And this probably will be the case in all those Apollo 7 and 8 mission scenarios. Once we get closer to the NASSP 8 release the scenarios will be replaced by new and updated ones.

For the attitude, the astronauts got a Maneuver PAD for the phasing maneuver. You access it by opening the CAPCOM Menu (press TAB) and then "Hide/Show PAD" (press 5). At the bottom of the PAD the desired attitude for the burn is shown:

183 R
297 P
002 Y

Just follow the Checklist MFD instructions to maneuver to that attitude with V49. Also note that the -X thrusters are used for the phasing burn, so you basically have to thrust backwards.
8  Project Apollo - NASSP / Project Apollo - NASSP News & Discussion / NASSP moving to Orbiter Forum? on: April 24, 2018, 12:50:58 PM
Because of continuing issues with access to this forum, I have sent an initial request to the admins of the Orbiter Forum, if NASSP could get its own subsection of the forum there. The reply was that we would be very welcome, if we decided to move the NASSP development forums there. So I created this thread to discuss that topic.

I believe it would be our best option to move into a subforum of the Orbiter Forum. This forum only works sporadically right now (for me at least), new user registration is annoying because of the manual process required for it and because there rarely is any admin active here anyway. And I believe moving to the main english speaking forum about Orbiter would also be good to show that NASSP and Orbiter have active development on-going. This forum is a great resource of old posts that always help with development, so I am very much in favour of keeping this forum alive, at least as a archive of old NASSP development threads. But a forum with active admins and an active community is the better solution for NASSP in the future, in my opinion.
9  Project Apollo - NASSP / Project Apollo - NASSP Development / Re: V8 Release Work Thread on: April 14, 2018, 11:56:07 AM
I hope we soon are able to solve the problem with the oxygen flow in v8. I think it's important that we soon can get Apollo 7 and 8 functional in Orbiter 2016 so we can leave Orbiter 2010. Most user using NASSP v8 I think. Is it possible to prioritize Apollo 7 and 8 before 9-11?

Thanks  Happy

There isn't a real problem with the oxygen flow. The oxygen flow caused by the Direct O2 switch was actually previously wrong and is now correct. There only is a problem with the logic for the O2 FLOW light on the caution and warning system. The ECS plumbing in NASSP is not completely realistic and the CWS is basically taking its O2 flow measurement at the wrong spot. That together with the Direct O2 flow rate change is what is currently causing the O2 FLOW light when it shouldn't actually be on.

What about Apollo 7 and 8 isn't working? To be fair, I haven't flown these missions in a while, but nothing specifically should be broken about those missions in Orbiter 2016. Not that I know of.
10  Project Apollo - NASSP / Project Apollo - NASSP Development / Re: Virtual AGS Development on: April 14, 2018, 11:35:58 AM
The last remaining big feature of the AGS has now been implemented, PGNS to AGS downlink. Previously AGS state vector updates had to be done all manually, typing the data into the DEDA. Now Verb 47 of the LGC can be used to send the LGC state vectors of CSM and LM to the AEA. Should be much more convenient.
11  Project Apollo - NASSP / Project Apollo - NASSP Development / Re: V8 Release Work Thread on: March 28, 2018, 04:46:04 AM
heres the scn., about 1 min before lgc activation uplink

Turns out that having a combined clock update, CSM state vector, LM state vector and REFSMMAT uplink string was a bit too much and exceeded the 1024 character limit of the uplink_data variable.  ROTFL And that overflowing caused access violations. Should be fairly straight forward to fix. Thanks for finding this!

EDIT: Should hopefully be fixed now.
12  Project Apollo - NASSP / Project Apollo - NASSP Development / Re: V8 Release Work Thread on: March 27, 2018, 03:47:18 PM
I cannot figure out logging into the irc channel, maybe someone can hold my hand and walk me thru it.

There are several different ways of doing this, but the easiest way is to go to then click Chat there, choose a username and the channel #nassp and join. That should be a fairly reliable way of joining. I personally use an IRC Client called Hexchat, but that is one of the more advanced option of joining the channel.

Anyways just wanted to report Iím getting a CTD every time the MCC thread starts for LGC activation on Apollo 10. Can post a scn tomorrow if needed

Yeah, a scenario would be good. I just did some changes to the MCC that I was sure would cause new bugs, so it's quite likely that you found one.
13  Project Apollo - NASSP / Project Apollo - NASSP Development / Re: V8 Release Work Thread on: March 27, 2018, 01:33:04 PM
Very nice to follow the development of version 8 of NASSP! I'm still using Version 7, which is a great simulator with so many opportunities to learn all the features of Apollo Spacecraft. The question is if you ever get ready with this simulator. Thank you once again for a great simulator and space experience!  Happy


Haha, NASSP will never be truly finished. NASSP 8.0 is progressing quite well and we might enter the Beta stage in the next few months. Just not much activity here on the forum, it's mostly the IRC channel these days. But even after the Lunar Module is mostly done there is still a lot of work to do to support all Apollo mission properly.
14  Project Apollo - NASSP / Support & Bugs / Re: LVDC++ switch event list? on: February 23, 2018, 05:24:11 AM
On PA MFD now i see option to change switch events or how is this called for the stages.
Is there any list of all those switch events with their effect? Is there any documentation for new IU related PA MFD functions?

Yeah, I've added a bunch of uplink options for the IU to the PAMFD. It's not all properly documented yet, but it will be.

Each Saturn stage (S-I, S-II, S-IVB, IU) has a switch selector, that the LVDC can use to send commands to each stage, by selecting switches in a switch box (the switch selector). All the LVDC has to sent to the stage is an ID number of the desired event. What each code means is documented in code at least right now:

IU (Saturn IB):
IU (Saturn V):

Uplinking a switch selector command through the LVDC would be rarely done, the other uplinks will be used more frequently. As an example, on Apollo 9 a lot of switch selector commands were uplinked to the S-IVB and IU for the 2nd restart of the S-IVB. It's quite a powerful tool, you can command every step for S-IVB reingnition through the IU uplink.
15  Project Apollo - NASSP / Programming / Re: Telemetry client, documentation on up/down link socket interface on: February 21, 2018, 02:15:30 PM

Also i'd like to ask if there are any sockets for LM and LVDC already, or is it just for CM?
And also what are the ports for sending and receiving?

I don't know much about the telemetry client, but this might be the relevant line in CSM and LM telemetry code for the ports:

service.sin_port = htons( 14243 ); // CM on 14242, LM on 14243

And there is no LVDC telemetry yet.

A new telemetry client would be great to have, the old one is difficult to work with, because it was created in now outdated Visual Studio versions.
Pages: [1] 2 3 ... 88
Powered by MySQL Powered by PHP Powered by SMF 1.1.10 | SMF © 2006-2009, Simple Machines LLC Valid XHTML 1.0! Valid CSS!