[23:34:06] NASSP Logging has been started by thewonderidiot [23:34:11] Guenter! [00:12:08] oh good, someone woke him up [13:06:10] Hey Nik [13:06:16] hey [13:17:13] the SCS update will be fun to review [13:17:20] it's exciting changes like [13:17:25] pitchrate = pitchBmag->GetRates().x*cos(Attitude.x) + yawBmag->GetRates().y*sin(Attitude.x); [13:17:26] to [13:17:30] pitchrate = pitchBmag->GetRates().y*cos(Attitude.x) - yawBmag->GetRates().z*sin(Attitude.x); [13:17:50] "Looks good to me" [13:24:23] still working on SCS Auto TVC though. Not 100% sure I got it right yet [13:26:26] it was all kicked off by Alex asking innocently if the DV CG switch is now doing something :D [13:36:16] on average I get about 10 ft/s error in the DVY and DVZ axes for both LOI-1 and TEI [13:36:30] I'm not really sure if that's good [13:37:03] I guess it isn't bad at least, it's like a 0.25° average pointing error of the thrust vector [13:57:29] I'm flying 10 right now. did my first TD&E last night with the new cg [14:00:31] ah fun [14:00:45] with the updated RCS directions it will feel slightly different, but not too much [14:01:13] I think in general the rotations caused by translations will be less [14:02:02] it wasn't as bad as I thought it would be. going slow is definitely the trick [14:03:13] yeah it's just the opposite effect of what we had before and a bit stronger because the moments of inertia are smaller [14:07:25] i wonder how bad a CSM-active rendezvous and docking in lunar orbit, with tank slosh modes would be. [14:17:20] GSOP section 6 has calculations for slosh [14:36:34] ooooo cool. I might throw this into a matlab simulation this weekend [14:36:49] I see there's bending mode dynamics too. [14:37:07] yep [14:41:47] I'm not sure that there is a Orbiter API function apply a custom moment [14:41:52] there is AddForce though [15:22:00] Good morning [15:23:48] hey Mike, Ryan. [15:28:15] morning! [15:30:31] indy91 any luck looking at that TLI? [15:30:54] hey [15:31:08] well all I saw was the normal small transient when it switches to terminal guidance [15:31:16] maybe slightly larger than usual [15:31:25] but nothing unusual [15:31:32] ok which is what I saw as well [15:31:49] and using the correct timing for it (30 seconds vs. 15 seconds) doesn't change much [15:32:05] trajectory differences negligible? [15:32:07] time from cutoff [15:32:13] hmm good question [15:32:24] if anything doing it earlier will be slightly less accurate [15:32:34] but it's what they used [15:33:03] terminal guidance at 30 seconds from cutoff, the 15 seconds came from the 1967 Boeing document [15:33:20] its interesting that the jump isnt on the TLI tables under the psi (which I assume is ordeal?) [15:33:40] it's visible in the graph in the launch checklist [15:34:42] very much so haha [15:35:11] interesting its not on the table as well [15:35:57] it's a 4 degree jump in the table [15:36:11] 260° at 5:00, 256° at 5:30 [15:36:26] hmm [15:36:47] the graph and table are 1° off from each other at 5:00 [15:37:11] but not on the psi [15:37:39] did you get a jump in yaw? [15:37:52] Apollo 17 yaw angle is basically 0° throughout the burn [15:37:53] oh psi is yaw [15:38:16] and you of course have to look at the nominal table [15:38:18] not manual [15:38:20] I dont know why I was thinking that was the ordeal pitch *facepalm* [15:38:29] manual is fixed yaw, and constant pitch profile [15:39:03] oh you thought ORDEAL pitch, I see [15:39:13] Apollo 17 is doing extremely little yaw haha [15:39:14] yes thats the root of my confusion [15:54:07] I have the draft PR of my RCS/SCS update up [15:54:32] not 100% convinced yet about the SCS Auto TVC, but I don't have a good reference for what is good [15:57:13] Manual TVC in Rate CMD works as well as before even with the shifting CG [16:05:20] being able to set the right trim angle before the burn is very important, so I don't think the "hidden" right click option to change the angle by 0.1° is good enough. That should be more obvious. [16:08:01] yeah probably true [16:08:09] also, did you look at the ASCP by chance? [16:08:27] it takes 11 right clicks to move 1 degree which seems wrong [16:09:00] I think that might just be a visual glitch [16:09:06] I can check [16:09:21] there is also this [16:09:22] https://github.com/orbiternassp/NASSP/issues/47 [16:10:56] I'm seeing 10 clicks for 1° [16:11:04] maybe it depends on the initial angle? [16:11:17] and where did you see it, roll, pitch, yaw? [16:16:08] let me test [16:16:36] just tested in yaw at 0deg [16:17:19] going up 0 to 1 takes 11 [16:17:24] going from 0 to 359 takes 9 [16:17:40] ah [16:17:53] so I think the actual 0° position is visually off [16:20:12] VC or 2D? [16:21:22] and I don't think its consistent haha [16:30:43] all 2d [16:30:47] havent tried vc with this [16:39:54] ASCP needs an overhaul anyway, the code for it is bad a complicated [16:39:58] and* [16:40:22] at least the code related to displaying and controlling it [16:59:52] I wrote a really incorrect BCD to hexadecimal converter in a PLC once. our ascp behavior reminds me of it. [17:09:18] haha [17:19:46] n7275 LM press went normally [17:19:56] No surprises or unusual readings [17:22:01] that was my experience with 10 as well. good to know. [17:37:37] insy91 just making sure I still remember, its the evasive maneuver enable that starts the sequence for the SIVB yaw maneuver etc correct? [17:37:41] indy91 [17:38:06] yeah [17:38:20] and then TB8 enable [17:38:49] evasive maneuver is the yaw maneuver and tb8 is the evasive burn? [17:39:35] TB8 starts the evasive burn [17:39:49] got it [17:39:58] and the yaw maneuver is basically the first step for in the evasive maneuver [17:40:06] but the naming can be confusing [17:40:15] right thats why I had to confirm [17:40:43] Apollo 17 flight evaluation report calls it "evasive yaw maneuver" and "TB8 Initiate" [17:40:53] maybe I'll add the yaw in the PAMFD description [17:41:25] makes it a bit more clear [17:42:32] gotcha [17:42:40] the flight plan has yaw maneuver and evasive burn [17:46:55] bye bye SIVB [17:51:31] do we have a complete pdf systems checklist for 17? I see the one on the AFJ but its individual pages [17:53:21] thewonderidiot scanned one [17:54:31] or was that Systems Data only... [17:55:20] I see systems data [17:55:32] right [17:55:37] I haven't made the Systems Checklist into a PDF yet [17:56:16] Are you just using these pages? [17:56:17] https://history.nasa.gov/afj/ap17fj/a17-csmscindex.html [17:56:51] that's what I have looked at in the past [17:57:03] we do have the very similar Apollo 15 one though [17:58:43] right I have that [18:00:00] you fly the mission with the CSM CG update, right? [18:02:36] Yes [18:04:16] let me know if you see anything unusualy. I hadn't tested SIM bay door jettison yet, but the change for it was exactly the same as for the optics cover. [18:04:28] and that I did test that it gets created in the right place [18:04:31] so should all be fine [18:04:40] TD&E actually felt good [18:04:51] it felt more "expected" if that makes sense [18:08:39] will still change a little bit with the update RCS thruster directions [18:09:33] it mainly makes the rotations causing by translations weaker [18:09:38] but they are still there [18:09:45] oh I saw them [18:10:16] but nothing out of the ordinary if anything it felt more stable [18:10:34] when I tested SCS Auto TVC with TEI and did the ullage burn the rotations were quite strong [18:10:42] that's why I checked and then changed the thruster directions [18:10:50] they are in the draft PR I have up [18:10:59] should get merged soon, a bit more testing [18:11:45] sounds good [18:17:02] https://www.dropbox.com/s/d7ycxt0x2o3gpiz/Apollo%2017%20CSM%20Systems%20Checklist.pdf?dl=0 [18:17:12] combined from the AFJ files if you want it [18:19:05] ah great, thanks! [18:20:27] Mike scanned the EXP/EVA Checklist [18:20:37] that used to be in the Systems Checklist [18:21:07] I saw that, I haven't opened it yet though but I am certainly looking forward to putting flight plan references to it and procedures into context this time [18:21:36] 16 already had that, right? [18:21:44] for 15 it was in the Systems Checklist, I think [18:22:43] 16 has it yeah [18:23:18] systems checklist we have for 15 had TBD on thoser sections [18:24:10] not the flown 15 one [18:24:34] https://readux.ecds.emory.edu/books/readux:vg61k/ [18:25:25] the copy on the AFJ has the TBD yeah, that's what was available first [18:28:05] I keep forgetting about that collection [18:29:22] oh can I see when my tb8 time is via the lvlog? [18:30:15] ah found it [19:27:32] So with this late launch do i need to do anything different when calculating MCC2 [19:28:52] looks like the actual MCC2 was burned on the FP time of 35h30m [19:29:41] just that you want the planned LOI GMT instead of GET [19:30:10] so basically a bias on the flight plan GET [19:30:13] with your launch delay [19:30:58] 2:40h earlier than the flight plan GET, or whatever the delay was [19:31:52] ah ok [19:32:09] I hope that works [19:32:20] well the initial guess is already close to that [19:32:26] maybe try an unconstrained LOI GET first [19:32:29] if it even works [19:32:43] yeah thats what I meant [19:32:46] oh [19:32:48] great [19:33:05] what's the DV like [19:33:08] 13 minutes different unconstrained (taking the 2h40m difference into account) [19:33:12] 8.1 [19:33:15] love it [19:33:24] going to constrain a bit and see what happens [19:35:11] I constrained to the FP LOI time and have a dv if 17.1 [19:35:29] I'm totally fine with that considering we don't have the full presettings for 17 [19:35:33] is there a proper way to run the constraints? I usually just tweak TLMAX [19:35:48] and leaver TLMIN the rounded hour before the burn or so [19:35:56] ah if that works, great [19:36:09] on Apollo 13 they kept it in a 10 minute window from TLMIN to TLMAX [19:36:17] oh ok cool [19:36:20] and then shift that window around until I get the desired result [19:36:41] how large the time window is does make a little bit of a difference in the generalized iterator [19:37:09] but in general it should work fine with any values [19:38:22] I usually keep it within about 30 minutes, I reduced to 10 in this case and now have it within 1 second of LOI planned time [19:38:29] 17.7 the final dv [19:39:02] https://www.dropbox.com/s/b6cwiwb4qjzvqiv/Screenshot%202021-09-24%20133850.jpg?dl=0 [19:39:33] I'll recompute after PTC but I am happy with that initial computation I think [19:39:34] I'd say that is the better IU navigation at work [19:39:49] Yeah it looks good [19:39:58] the display there estimates the LOI TIG in a fairly simple way [19:40:18] so that will already be a few seconds off from when you would calculate LOI for real [19:40:41] maybe some bored night shift FIDO tweaked the numbers even more to get the actual LOI TIG right on the second [19:41:20] that's my impression from listening to the FIDO audio :D [19:42:08] actual LOI ignition was about a minute earlier than flight plan [19:42:43] 88:54:21.74 versus FP 88:55:37.5 [19:56:25] yeah, I think the actual desired condition is rev 2 meridian crossing time or so [21:16:24] just for grins I am burning APS-1 and APS-2 [21:21:23] what are all the "minor loop" in the lvlog? [21:22:16] maybe ran out of propellant during time accel? [21:22:35] hmm yep [21:27:32] oh haha [21:27:48] I guess it displays a bunch of stuff that it normally doesn't [21:27:54] or logs I mean [21:29:06] the lvlog needs to write less stuff in general [21:39:13] night! [21:44:28] .tell indy91 forgot to ask before you left, can we uplink a SIVB PTC command yet? [22:03:16] hmm I think waste water dumps slower now (it was already slow before I believe) [22:04:41] 3 hours to dump 80% [22:04:47] that seems wrong [22:59:29] yeah, that doesn't seem right at all. [23:03:15] I question is: why. [23:04:10] I bet the pressure is lower. [23:32:10] I mean it dumped slow to begin with I think, but yeah [23:39:59] I will have to look up the spec'd flowrate but increasing the size of the valve should be a nice tidy solution to that. [23:45:36] yeah easy fix we just need to figure out how much [23:52:59] the units of "size" are alegedly in liters/(Pa*sec) [23:53:29] so hopefully not too much trial and error [14:54:44] good morning [14:56:18] morning [14:57:53] hey [15:12:39] hey [15:20:05] I dont think the water dump is entirely dependent on the valve size... [15:20:07] wasteWaterDumpLevel = 0.5 * (wasteWaterDumpLevel + (wasteInletVentPipe->flow / wasteInletVentPipe->flowMax)); [15:20:45] the code is a little confusing to me its not a simple open/close [15:20:53] ecs.cpp line 1115 [15:29:32] yeah, I don't like how that's written either [15:33:26] oh I see updates to your vap branch, anything I should be merging? [15:36:00] I just pulled the changes that Nik pushed yesterday [15:39:11] Are you sure that line controls the water dump rate? [15:39:21] ah ok [15:39:26] And no I am not [15:39:57] But I increased the valve to 0.01 from 0.001 and saw no noticeable change in dump rate [15:40:30] I'm 95% sure it is used to control the particlestream [15:40:53] increased from 0.01 to 0.001? [15:41:41] no increased from 0.001 to 0.01 [15:44:40] okay, I need more coffee [15:49:22] ditto [15:51:48] let's point some debug strings at it [16:45:57] I am out of the house for a few hours. I can poke at that when I get home later. [16:55:55] I will be as well most of the day [18:28:04] hey [18:28:12] not really [18:28:19] Afternoon :) [18:40:23] I've added a bunch of people to review my PR, haven't found any new issue with it [18:40:51] I still want to go through the SCS coordinate changes to make a final check on the code itself, but testing has been all good [18:41:55] so still a draft for 1-2 more days [18:43:01] the SCS Auto TVC does now work differently for CSM vs. CSM/LM with the DV CG switch. But what is still not implemented is the filters [18:43:19] not that we really need them, we don't have noisy signals or body bending [18:43:23] right [18:43:43] in the NAA simulator there are the transfer functions for the filters [18:43:45] Any particular situation you want tested with that? [18:43:52] hey Niklas [18:43:56] hey [18:44:10] any SCS operation you can think of [18:44:34] ok [18:46:02] there is a LM-on and a LM-off shaping filter for noise in the SCS Auto TVC. The transfer function is basically a damped harmonic oscillator, so that wouldn't be too difficult to implement [18:46:34] for the CSM/LM docked case there is an additional filter for body bending I think. That looks a bit more complex [18:47:41] but in any case, they won't be part of this PR [18:47:50] just a nice enhancement for the future [18:50:30] Indeed [18:50:43] I guess the SCS Auto TVC could use some specific testing [18:51:05] Some long and short burns under SCS? [18:51:08] sure [18:51:31] that's the enhancement part of this update. The other SCS changes are to make the code readable haha [18:52:06] was really confusing dealing with attitude rates in Orbiter coordinates while everything else is in the correct, CSM coordinates [18:52:38] the issue isn't even completely fixed. It goes as far as displaying the the attitude rate in the FDAI class [18:52:47] that is still not using the right signs and coordinate I think [18:53:05] but I didn't want to have to do changes in the LM when I wanted to fix stuff in the CSM SCS... [18:53:50] I dont blame you [18:54:08] MTVC with Rate Cmd hasn't really changed, just that the CG shifting means that you have to do more inputs [18:54:14] especially during TEI I guess [18:55:04] but I think that still works very well, you could easily fly a maneuver using CMC guidance, but SCS control looking at the error needles [18:55:17] like manually flying a reentry to the CMC guidance [18:59:01] I meant it's a bit like that. I was of course talking about SPS thrusting maneuvers with manual TVC. [18:59:27] although SCS entry is something I also haven't tested yet with the update [19:04:22] I wouldnt mind playing around with that [19:04:32] Though not using a joystick makes it challenging [19:07:41] it's not too bad actually, the MTVC integrator means it remembers the last input you did [19:08:12] so you don't really have to constantlly do a small input [19:08:29] so it works ok with keyboard [19:10:21] Accel Cmd however would be difficult without joystick [19:14:34] just tried a TEI, using the CMC error needles, but manual TVC in Rate Cmd. 2.0 ft/s residuals [19:14:49] with keyboard [19:14:55] it's definitely better with joystick [19:15:01] but it works fine without [19:23:28] Ok good to know [16:07:00] good morning [16:10:51] hey Matt [16:13:17] I feel a bit stupid asking, but what exactly is this ECS project you and Ryan are working on exactly changing. Just behavior of the substances? [16:21:58] hey, nothing wrong with asking. Yes, I am working on am inprovement to our substances. [16:22:29] right now I'm focusing on vapor pressure, and enthalpy of vaporization [16:22:55] so really just a physics change [16:23:01] trying to find my graphs to show you... [16:23:06] and not a format change to scenarios or so [16:23:35] or chemistry I should probably say [16:25:37] amazingly, no, I don't think we'll need to change anything. [16:25:40] https://i.imgur.com/IZXEZGU.png [16:26:35] that's good and we should keep it that way, I think changing how the substances behave is a big enough update [16:26:57] the red shows the the systems as they are now, and the blue shows the new version [16:27:05] definitely a difference [16:27:12] Ryan is flying 17, and I'm flying 10 with these changes [16:27:30] it's probably not even that bad for old scenarios I would imagine [16:27:54] and I used a scenario from Ryan in my branch without the update, got an O2 flow alarm but it settled down after a bit [16:28:09] I think the systems that are currently implimented, and the values that were chosen for the implimented systems work really well together [16:29:35] the heats of vaporization are constant, but they were chosen at temperatures that most of the implimented systems are at, [16:30:14] right [16:30:41] like the CG of the CSM was well optimized, but sadly just for Apollo 7 only haha [16:30:45] and the slopes and values of vapor pressure are close approximations of the new and improved versions at the temperature-pressure values that most things are at [16:30:55] haha, yeah. [16:31:20] are a lot of additional calculations required? [16:31:24] what this update should do, is allow us to impliment things that were previously impossible [16:31:37] not that I really think the systems simulation is really the CPU killer [16:31:45] it's the 2D panel and the emulators [16:33:16] very little extra overhead https://github.com/orbiternassp/NASSP/compare/Orbiter2016...n7275:VapPressAndHvap?expand=1 [16:33:57] yeah that's not much [16:34:31] calling exp() instead of simple arithmetic is probably the biggest, but CPUs are good at that [16:36:29] yeah [16:37:07] I was already thinking about the SCS Auto TVC filter and how I would implement that in the most optimized way [16:37:22] but it would also just be two exp() and a sine and a cosine or so [16:37:58] but I can make it so that the same calculation isn't done multiple times at least [16:41:52] direct solution of the transfer function which is a damped harmonic oscillator [16:42:01] can't have a numerical, timestep by timestep solution [16:42:15] that differential equation is extremely stiff [16:42:50] yeah, that wouldn't work [16:44:09] thankfully, damped harmonic oscilators have nice analytical solutions [16:44:21] yeah [16:44:52] even though I had trouble figuring out the right equation to use. Had a confusion about degrees and radians, rookie mistake [16:47:14] ouch, yeah. "why is this off by a factor of 57..." [16:49:34] I havn't made it very far on the tank-slosh project, didn't have the time yesterday. [16:49:43] https://i.imgur.com/beEdP1z.png [16:50:15] simple noise filter [16:51:31] what is your noise function? [16:52:50] x = 0.9 + 2*rand()/10.0; [16:53:02] random from 0.9 to 1.1 [16:53:07] on average 1 [16:54:07] that looks nice and easy to compute [16:55:04] yeah, easier than I initially thought [16:55:12] it's a forced damped harmonic oscillator [16:55:18] but the force function is the constant input [16:55:33] at least constant over one timestep [16:55:47] you still need to calculate and keep track of the initial conditions [16:57:37] I wonder if the magnitude of the noise should decrease with increasing timestep? [16:57:43] length [16:58:59] you mean remaining noise of the output? [17:00:22] yeah. unless I'm thinking about this wrong [17:00:29] you are thinking right [17:00:40] if I make it 10 fps then there is no difference to see between input and output at all [17:00:51] the graph was with 60 fps [17:01:20] for 600 fps the output looks basically the same as with 60 [17:01:32] but the noise graph is of course a lot more visible [17:01:39] as it's a random number on each step [17:10:15] this is for the CSM alone case [17:10:29] I think the CSM/LM docked version is a bit less stiff [17:11:38] CSM: damping ratio 0.805, angular frequency 40.7 rad/s [17:11:52] CSM/LM: 0.489, 29.0 rad/s [17:17:50] ok SCS works correctly during entry [18:05:45] nice [18:07:33] I still need to review/test your changes. [18:07:34] out of the house now, hopefully can do it tonight [18:08:16] sure, no rush [20:21:40] night! [05:14:49] .ask rcflyinghokie when you edited the waste water valve size did you do the one in the CFG file, or in the scenerio? [14:10:08] hey [14:11:33] morning [14:11:58] I did the config file [14:12:09] but then reverted when I found that code [14:17:40] I changed the valve size in the scenario, and was able to change the flowrate [14:18:18] I think the scenario overrides the cfg if the system exists already. [14:21:46] it does, yes [14:43:59] 0.05 was nice. no idea if it's right or not. [14:50:09] yeah I dont know where to find flow rates for the dump [14:50:35] maybe in some of the 16 and 17 experiment docs since they used urine and water dumps to test some of the equipment [14:54:51] hey [14:55:18] morning [14:55:45] what are you looking for? Waste water flow rates? [14:55:49] dump* [14:57:09] yeah [15:02:49] AOH had nothing [15:05:16] Is the dump valve the same as the pressure relief valve? [15:05:29] or are they different components [15:06:00] the water overboard dump nozzle is the one connected to the pressure relief valve [15:06:08] urine is separate [15:06:36] the waste water you manually dump is the pressure relief valve [15:09:13] 12 lbh at 70F and 6.5psi dP [15:10:28] and for the relief valve in all positions its a .3 gal/min minimum flow with 48psi dP [15:11:05] n7275 CSM data book pdf 307/308 [15:11:16] data book part 1 [15:15:19] thank you [15:22:06] Hmm I cannot seem to get this MCC4 on the MPT [15:22:20] I computed one and then deleted it and now am doing another and it wont go on the table [15:23:23] any error on the online monitor? [15:24:17] nope [15:24:56] are there old maneuvers on the MPT? [15:24:57] ephemris updates completed and rmmascnd convergence limit [15:25:04] MPT is blank [15:25:21] "rmmascnd convergence limit" is it trying to find the ascending node, which only works in low Earth or lunar orbit [15:25:34] so that error is always there in TLC or TEC [15:25:35] I did compute one, it appeared there, then I did a replace and it didnt replace [15:25:45] so I deleted it and tried again with no luck [15:25:47] oh replace hmm [15:26:07] another instance of an invisible maneuver? [15:26:19] possible, it would appear in the scenario [15:26:36] maybe the replace option doesn't work right in all cases [15:27:01] hmm both csm and lm have the maneuver 0 [15:27:35] did you still have the replace option set to something? [15:27:51] no it was on dont replace after I deleted [15:28:44] https://www.dropbox.com/s/21l1hiu1izn1juu/Apollo%2017%20-%20LM%20TM%200001.scn?dl=0 if you wish to peek [15:30:23] which engine did you choose? [15:32:56] I did a test in our Apollo 11 scenarios, the replace option for MCCs does at least work in general [15:33:02] SPS [15:33:19] hmm, maybe that's where the problem is [15:33:23] I should have used RCS when I recalculated though [15:33:25] burn too short for SPS [15:33:30] the previous dV was 5fps [15:33:36] ahh [15:33:46] surprised it didnt return an error [15:33:48] but that still doesn't really explain what happened [15:34:58] worked upon reload and choosing RCS [15:35:30] yeah no issue with the replace option [15:35:37] but it doesn't add the burn to the MPT with SPS [15:35:38] yeah its just not computing it for SPS [15:35:42] also the iterate option, right? [15:35:44] yes [15:35:54] it works without iterate [15:36:06] yeah that's still a problem, short burn logic and iterate [15:36:55] because right now it doesn't exactly achieve the desired DV [15:37:09] which is kind of realistic, but I think the maneuver sim might have to simulate residuals trimming or so [15:38:20] that's actually why I had requested the Apollo 7 RTCC system parameters document from UHCL [15:38:51] because it has the numbers for simulating the burn itself and also the short burn logic in the CMC [15:39:05] so I tried this yesterday as well, my DOI seems to have a very high dvz [15:40:00] oh, maybe because of the later launch you needed to adjust the REV numbers for MCC and LOI this time [15:40:25] Ohh [15:40:29] MCC2 I didnt [15:40:44] haha, you probably did it for all the other missions so far and didn't need to adjust [15:40:55] yep! [15:41:20] yeah I guess the trajectory is different [15:41:26] faster to the Moon [15:41:29] right [15:41:31] to arrive at the same GMT at the Moon [15:41:45] Maybe my MCC3 can correct it? [15:42:18] possible [15:42:24] Ah no MCC3 slot [15:42:43] I mean [15:42:48] I can make one, i know :P [15:42:50] Apollo 15 used their MCC-4 to adjust this [15:42:54] Oh [15:43:03] not really sure... how [15:43:21] Would be another option 4? [15:44:05] if that is able to calculate, maybe [15:44:13] it doesn't really like to work right close to the Moon [15:44:36] seems to work though [15:45:13] I really dont understand the Apollo 17 DOI-1 instructions in the RTCC manual [15:46:53] or this rev 2 dt [15:47:09] you mean the document that Alex made? [15:47:24] yeah [15:48:17] wait [15:48:21] when is the clock update [15:48:30] 65h [15:48:34] I am still before it [15:48:39] so adjusting everything [15:48:51] aaah [15:49:03] was wondering why the LOI time looked weird :D [15:50:46] yeah haha [15:52:56] hmm, is Alex not using the descent planning processor for DOI-1... [15:53:27] thats my confusion there [15:53:28] maybe it doesn't calculate it right [15:54:18] but I am stuck on this rev 2 dt thing [15:55:48] tries to find the rev2 crossing time with the checkout monitor [15:57:24] "MPT:MCC+LOI" does that mean I need to have an MCC and LOI on the MPT? [15:57:45] yeah [15:57:51] which MCC? which option? lol [15:57:57] doesn't matter [15:58:13] the ephemeris needs to reflect a post LOI trajectory [15:58:30] ah ok [15:58:31] so that the checkout monitor can look at the trajectory after LOI [15:59:49] ok there is a second solution for the DOI-1 point [15:59:56] the descent planning processor doesn't find it [16:00:17] but you can manually search for it with a general purpose maneuver [16:02:05] hmm [16:02:19] N = 0 on the descent planning [16:02:40] Currently working this REV 2 dT [16:02:56] because it's set up for DOI-2 [16:03:12] -1m54s is what I came up with [16:04:09] shouldn't that be close to 2h40m? [16:04:13] I am very confused because I dont know if this is taking into account the delay [16:04:25] No idea I just followed the instructions verbatum [16:04:37] I have my adjusted times on LOI [16:04:39] actually, this DT is what the clock update should be like [16:05:00] ok, but first with the DOI [16:05:07] ok [16:05:11] for 17 the descent planning page is set up for DOI-2 [16:05:26] so no way without changes to the init page can it calculate something good haha [16:05:40] I see [16:05:42] I gave myself a general purpose maneuver DOI-1 [16:05:50] but didn't adjust the longitude [16:05:56] but made it a DVX maneuver only [16:06:07] put that on the MPT and then calculated DOI-2 [16:06:18] gave me -9.5 0 -8.5 [16:06:27] so only 8.5 ft/s of orbit rotation needed [16:06:52] can maybe be done with adjusting DOI-1 a little bit more [16:07:10] I am trying to figure out my MCC/LOI at the moment [16:07:32] yeah, I think you don't need to change the REVS actually is what I wanted to say with that [16:07:44] So I can press with what I have? [16:07:49] I think so [16:08:04] let's calculate your clock update time with rev 2 [16:08:58] Before that, I have my MCC4 and LOI on my MPT [16:09:04] I think you didn't actually find rev 2 [16:09:08] but rev 3 [16:09:16] they are both 2h40minutes ahead of the fp times [16:09:22] *behind [16:09:24] right [16:09:57] the initial guess Alex uses doesn't work with a time delay that is more than 1 lunar orbit [16:10:39] Currently on MPT https://www.dropbox.com/s/um6mv7ituxsuw3v/Screenshot%202021-09-27%20101022.jpg?dl=0 [16:11:16] yeah that's fine [16:11:35] I would suggest using GET on the checkout monitor [16:11:41] rev 2 time in flight plan about 91h [16:11:50] so initial guess is 88:20h [16:12:00] got me 176° longitude or so [16:12:11] and Orbiter Sound crashed me [16:12:18] its been crashing me a lot [16:12:29] I have it deactivated a lot because of that [16:12:33] so try GET instead of GMT, initial guess 88:20h [16:12:38] on the checkout monitor [16:12:55] then use the procedure that Alex says to find exactly the time of 180° longitude [16:13:10] and then we can math the DT for the clock update [16:13:29] Hmm [16:13:42] Same results as before [16:13:54] U02,CSM,GET,88:20:0,,MCT; [16:13:58] yes [16:14:14] Last time I used GMT and it was 2h40 different [16:14:31] Which means GET and GMT didnt change using GET [16:14:34] not sure what you mean [16:15:02] I used the calculation in the manual to get rev 2 GMT and came up with 93:52:20 [16:15:24] REV 2 being about 90:59:20 [16:15:41] that can't be GMT [16:16:07] https://www.dropbox.com/s/v6rcgy4ish61s9n/Screenshot%202021-09-27%20101554.jpg?dl=0 [16:16:40] REV 2 time plus nominal lift off time gets me 93:52:20 [16:16:46] ah I see [16:16:59] so everything looks right [16:17:09] I see 88:19:20 GET [16:17:13] yes [16:17:20] LONC is -174° [16:17:33] thats where I got my dT of 1m54s [16:17:47] aaah, I thought you meant the DT for the clock update [16:17:48] -1m54s [16:17:51] oh no [16:18:07] yeah then increment the input time by that [16:18:10] to get close to 180° [16:18:17] ok so i did do this correctly haha [16:18:24] which input time [16:18:31] for the checkout monitor [16:18:53] oh ok [16:19:07] 1m54s earlier [16:20:08] And what am I looking for here now [16:20:17] rev crossing is 180° longitude [16:20:24] lonc? [16:20:26] yeah [16:20:31] 168.217 now [16:20:42] great, it was the other way then haha [16:20:53] so the signs are wrong in the manual? [16:21:06] hmm, seems unlikely [16:21:18] you sure you did the inputs all the same otherwise? [16:21:20] yes [16:21:21] GET/GMT and MCT? [16:21:49] https://www.dropbox.com/s/fhdrvn3sjx615vf/Screenshot%202021-09-27%20102138.jpg?dl=0 [16:23:12] hmm [16:23:19] around the Moon you travel west [16:23:30] so longitude always gets more negative in the direction of travel [16:23:40] so want 3° more negative [16:23:47] so DT has to be positive [16:24:17] input guide must be wrong then [16:24:35] 88:21:16 GET is probably a better guess [16:24:58] i think it contradicts itself [16:25:34] Says if LON is west (-) of 180, dt is negative, but then in the example has 177 as positive dt [16:26:08] oh its +177 hmm yeah thats not clear at all [16:26:30] I think the later versions of the checkout monitor had an automatic option to converge on longitude [16:26:36] I can implement that some time [16:26:59] 179.514 [16:27:29] one more iteration [16:27:56] I think it's 10 seconds? [16:28:16] 8.68 :P [16:28:38] ah I typed 15 this time, so 179.566 [16:28:51] so increase 8.68 seconds [16:29:35] hmm [16:29:40] no [16:29:41] subtract [16:29:43] yeah [16:29:51] we had minus before and had to add time [16:30:34] 179.957 with 88:21:06 [16:30:44] close enough [16:30:50] your liftoff time increment is then [16:30:56] 88:21:06 minus 90:59:22 [16:31:17] or [16:31:24] go back to the nominal liftoff time [16:31:29] if that is close enough [16:31:35] I am confused [16:31:47] this was to adjust LOI time not my clock update [16:32:13] oh [16:32:25] ok, if clock update is back to nominal time [16:32:36] Constant lunar arrival GMT (Apollo 14+): Find REV 2 Delta T (Common Functions), Note initial GET LOI (TAR, MCC, MID), then TAR, MCC, CON, F23: Adjust TLMIN/TLMAX (10-minute range) until new GET LOI = old GET LOI + REV 2 Delta T [16:32:39] thats what I am doing [16:33:00] but again I dont know if this is supposed to take into account the delay [16:33:18] what was the exact delay again? [16:33:24] 2:40h? [16:33:25] 2h40m exactly [16:34:24] ok, then your rev 2 crossing time, with everything as currently planned, is 91:01:06 [16:34:39] after a 2:40h clock update [16:34:54] desired time is 90:59:22 [16:35:10] so LOI needs to be about 2 minutes earlier [16:35:42] Apollo 14 FIDO mentioned they got very confused about this all [16:35:54] I bet by 17 they had better procedures, worksheets etc. [16:36:39] but I think the result of this is, make LOI 1m44s earlier [16:36:57] and then try this again to make sure it worked [16:38:06] and I guess you probably would have wanted to already do this for MCC-2 [16:38:17] 2 minutes change in LOI time is a bunch of DV for MCC-4 [16:38:19] yeah haha [16:38:47] I'll figure out why nothing happened with small burn, SPS, iterate [16:38:50] certainly a bug [16:41:17] option 4 with new LOI time of 86:14:41 is 5.8fps [16:41:38] thats adjusting for the 2h40m [16:41:54] and then subtracting the rev 2 difference [16:43:14] does that seem correct [16:52:06] using those values on the MPT, I get a DOI time of 90:33:25 with dvx of -191.8 and dvz of +87.4 [17:06:37] as I said, the DOI page is not set up for DOI-1 but for DOI-2 [17:06:56] at least the number of revs between DOI and PDI would need to be adjusted [17:07:31] and Alex seems to think the descent planning can't properly calculate the Apollo 17 DOI-1 anyway [17:13:07] that DOI was not using the DOI processor [17:13:13] But the alternate method [17:14:37] I see [17:14:46] I don't think that's a very good method though [17:15:03] that gives longitude on the same rev as DOI-1 and the Moon rotates [17:15:39] my method is work intensive [17:15:53] DVX only DOI-1 [17:15:57] put that on MPT [17:15:59] calculate DOI-2 [17:16:02] see it has a DVZ [17:16:06] adjust DOI-1 time [17:16:14] I am ok with that...stepping back though how does that MCC/LOI look [17:16:26] I will try your DOI method after [17:16:58] I can't tell how your MCC/LOI looks [17:17:19] relevant is the new rev 2 crossing time [17:18:19] DOI time tends to be off from the flight plan due to different gravity model [17:18:55] if LOI is now 1m44s earlier than before then it should be good [17:19:38] https://www.dropbox.com/s/fxfdnueslw3jez7/Screenshot%202021-09-27%20111718.jpg?dl=0 [17:19:45] https://www.dropbox.com/s/0ydjmsih4vztv3a/Screenshot%202021-09-27%20111930.jpg?dl=0 [17:20:10] https://www.dropbox.com/s/qlwcw5jlnshzh9b/Screenshot%202021-09-27%20112001.jpg?dl=0 [17:21:43] did you adjust HP after LOI? [17:22:52] your old LOI was 86:15:31 [17:23:01] now it is 86:14:41 [17:23:09] only 50 seconds [17:23:17] not 1m44s [17:23:39] was it a larger difference on the MCC display? [17:23:58] hmm no [17:24:58] Let me recompute that MCC [17:27:24] https://www.dropbox.com/s/ntithg8zr0pct1v/Screenshot%202021-09-27%20112702.jpg?dl=0 [17:27:29] https://www.dropbox.com/s/gy6sszvdvzwcx5f/Screenshot%202021-09-27%20112718.jpg?dl=0 [17:41:06] it's probably good? Only the rev 2 crossing time can really tell [17:43:52] so I just figure that out like before with this new LOI on the MPT? [17:44:08] yep [17:44:18] you can directly try the GET that you want it to be [17:44:28] should hopefully be very close to 180° [17:44:39] that's the 88:19:22 [17:45:33] hmm [17:45:36] nope [17:45:53] Oh hold on, wrong ref [17:46:21] hmm 177.285 [17:47:01] Wait I wanted 88:21:06 [17:47:09] no [17:47:24] wait haha [17:47:30] where is that number coming from now haha [17:47:31] thats the GET that got me closest to 180 [17:47:35] before [17:47:41] ok [17:47:56] so thats what i should be using? [17:48:01] no [17:48:07] I am so confused haha [17:48:21] flight plan has 90:59:22 GET for rev 2 crossing [17:48:29] so you want 2h40m less than that [17:48:51] so the 88:19:22 [17:48:54] yeah [17:49:05] and that now gives +177°? [17:49:11] gives me -177.285 [17:50:18] and you have a LOI on the MPT with 86:13 [17:50:23] yes [17:51:46] so I need to increment 43 seconds? [17:51:59] I find that extremely confusing [17:52:11] you changed the LOI TIG to 1m50s earlier than before [17:52:22] yes [17:52:23] how does that only make a 1° difference [17:52:26] 1° is 20 seconds [17:52:28] I dont know haha [17:52:41] can you show me the checkout monitor? [17:53:09] https://www.dropbox.com/s/23pzmiizqjkd2t4/Screenshot%202021-09-27%20115257.jpg?dl=0 [17:53:31] https://www.dropbox.com/s/8a1x9220kfp1k8h/Screenshot%202021-09-27%20115322.jpg?dl=0 [17:54:23] which LOI solution is that each time [17:54:25] 2? [17:54:43] I guess 1 and 2 are basically identical [17:55:19] although... [17:55:50] yeah [17:55:56] they are identical [17:56:26] I have no idea. You could try make LOI even earlier [17:56:53] but the earlier LOI time shouldn't be able to change the post LOI orbit so much that the rev 2 crossing time is now different [17:57:34] I mean that it should be different by the same amount that the LOI time is different [17:58:28] so any idea whats not working? [17:59:14] I can only imagine that the LOI maneuver is different than before [17:59:17] in its DV vector [18:00:15] uhh [18:00:21] MCC-4 has become 17 ft/s??? [18:00:27] that's too large [18:00:31] no way that's right [18:00:55] yes because of the increase of LOI time [18:01:00] this is an option 4 again [18:01:06] ah option 4 [18:01:27] I moved LOI time back a bit more its closer to 180 [18:02:08] and LOI increase by the same amount nearly [18:02:19] MCC-4 speeds up more, LOI slows down more [18:02:33] not sure all that is really worth the right rev 2 crossing time [18:03:28] Maybe if I did this for MCC2 [18:03:44] you could deviate from the actual mission. Which you basically already did by not doing this for MCC-2. You could do what I initially thought what you wanted to do, calculate a clock time increment that is not 2:40 [18:04:08] then you could do an unconstrained MCC-4 [18:04:20] and still get the right rev 2 crossing time [18:04:29] Sure, lets try it [18:04:44] I think we already did that [18:04:50] I didnt [18:04:56] 88:21:06 minus 90:59:22 [18:05:02] earlier [18:05:08] we did that earlier [18:05:16] I wasnt following at the time because we were talking 2 different things [18:05:18] when you initially tried to calculate an update LOI time [18:05:34] I came up with that "88:21:06 minus 90:59:22" [18:05:43] I think you can do a option 1 for MCC-4 [18:05:44] which I kind of ignored :( [18:05:56] no I was calculating the wrong thing for you at the time haha [18:06:04] but now it's maybe useful [18:06:15] lets try it, I am almost at clock update time anyways [18:07:00] so my calculation is, liftoff time update of minus 2:38:16 [18:07:05] instead of minus 2:40:00 [18:07:14] where did those GETs come from [18:07:32] 90:59:22 is rev 2 [18:07:41] yeah, in the flight plan at the clock update [18:07:47] page 3-62 [18:08:08] 88:21:06 is your actual rev 2 crossing time [18:08:17] with the LOI before you changed its TIG [18:08:25] I think that was with the 2 ft/s MCC-4 [18:08:30] ah ok [18:08:34] the option 1 [18:09:07] Ah oh no I updated the SFP [18:10:18] I will do it without a MCC4 [18:10:26] should be close enough [18:10:55] 20 seconds different [18:12:01] haha why did you update the SFP [18:12:17] did you try option 4 for MCC-3 and the option 1 for MCC-4? [18:12:23] then* [18:12:25] Honestly I have no idea why, I thought I was committing to it [18:12:42] is the SFP stored in the scn file? [18:12:45] yes [18:12:49] you could restore it [18:13:36] RTCC_SFP lines? [18:13:40] yeah [18:14:21] SFP only needs to be updated if there is a future option 1 maneuver that needs numbers from a past option 2-5 [18:14:43] ahh I thought it impacted LOI as well [18:14:53] not at all [18:14:58] good to know haha [18:15:07] in fact the REV numbers don't carry over to the LOI processor [18:15:12] ok those are replaced [18:15:44] if you change the rev stuff for MCCs then you also need to change them manually for LOI [18:16:27] MCC and LOI processors are quite independent [18:17:17] the Apollo 11 version of the actual LOI processor might have still used the SFP, but it was never implemented this way in our RTCC. [18:17:50] That older LOI version they had repeated some of the full mission optimization features from the MCC processor [18:18:02] so I think it calculated TEI like the MCC processor [18:18:23] Interesting [18:18:28] but for the Apollo 14 version of the LOI processor they had removed it [18:18:38] that's the version we have [18:18:46] very streamlined version [18:18:49] haha [18:18:55] removing a bunch of options they never used etc. [18:19:12] But that are useful for our older missions [18:19:24] Or useful in general [18:19:28] Well I have my MCC4 and LOI restored now [18:20:50] -179.960 using 88:21:06 [18:21:19] great [18:22:35] 2:38:16 [18:23:00] I agree [18:23:26] the old LOI processor had more options that varied the approach azimuth [18:23:44] the Apollo 14 version doesn't have extra options for that [18:24:18] but it does still calculate and show "AZMN FND" and "AZMX FND" [18:24:41] that's true anomaly at the node with the min and max azimuth specified on the input page [18:24:55] a smart FIDO can read things into those numbers [18:25:01] no idea what [18:25:32] maybe to find a node that is closer to pericynthion [18:25:49] YEAH THATS ABOVE MY PAYGRADE LOL [18:25:53] ah capslock [18:26:46] your MCCs would have to be quite off nominal for that to become relevant haha [18:30:09] ok walk me through the clock once more? [18:30:15] I am on the update page [18:33:36] left side of the page is not relevant again [18:33:56] just increment 2:38:16? [18:34:04] minus [18:34:17] to make the liftoff timer earlier [18:34:27] which makes the GET later [18:34:30] right [18:34:31] time* [18:34:47] basically moving the liftoff time back to nearly nominal [18:35:21] and after the uplink you need to sync the RTCC again [18:35:41] UPD button [18:35:43] on that page [18:35:59] exactly identical to the button on the config page [18:37:06] RTCC liftoff now 2:54:44 [18:38:04] planned liftoff time was 2:53:00 I think [18:38:08] so that seems right [18:38:24] TEPHEM is 00020 34670 56565 [18:38:33] all positive, nice [18:38:35] uhh [18:38:37] lol [18:38:39] not [18:38:49] not? [18:39:16] 56565 [18:39:19] negative [18:39:35] 0-37777 is positive, 40000 to 77777 is negative [18:40:10] still need to add something so that you can manually load the TEPHEM [18:40:56] but I can calculate a TEPHEM with the padload worksheet [18:41:37] 20, 34667, 16520 [18:42:01] load that on the DSKY and then sync the RTCC liftoff time again [18:42:03] hmm wait [18:42:16] has to be accurate to the centisecond [18:42:19] 2:54:44 isn't enough [18:42:22] where is the padload worksheet [18:42:28] we outsourced them [18:42:42] https://github.com/orbiternassp/padloads/tree/develop/Padload%20Worksheets [18:43:30] does it show the RTCC liftoff time in centiseconds? [18:43:41] yes 2:54:44.38 [18:45:45] 20, 34667, 16566 [18:46:04] How did you get those [18:46:23] padload worksheet wants a MJD for TEPHEM [18:46:29] calculate the MJD for that time [18:46:33] calculated* [18:46:45] Oh thats not just AGC Epoch from the RTCC config? [18:47:13] And I havent a clue how to convert to MJD lol [18:47:37] AGC epoch is for the yearly coordinate system [18:47:46] that's a time close to January 1st [18:48:51] MJD is in days [18:48:57] 41658.0 is midnight of launch day [18:49:13] so you would add 2/24 + 54/24/60 + 44.38/24/60/60 to that [18:49:58] I'll come up with a TEPHEM display on that uplink page [18:50:38] that would be handy haha [18:50:50] But I am seeing how thats added I think [18:51:13] if you press the UPD button after loading the TEPHEM it should not change at all [18:52:14] no change [18:52:50] to be sure also try the clock increment page [18:52:59] and calculate how off the clock time is [18:53:10] manually loading TEPHEM is a bit scary [18:53:14] can easily screw things up [18:53:18] UPD on the time update page? [18:53:23] I think so [18:53:29] nothing changed there [18:53:35] uhh [18:53:52] wrong button [18:54:00] that did the same thing on the other page haha [18:54:02] CLC button [18:54:16] as on* [18:54:20] https://www.dropbox.com/s/w68khm7edttht1l/Screenshot%202021-09-27%20125349.jpg?dl=0 [18:54:39] clock increment [18:54:59] other page [18:55:03] naming is a bit confusing [18:55:18] I am not following [18:55:20] "07: CMC Time Increment" [18:55:25] that is what I meant [18:55:26] oh [18:55:39] and there CLC [18:55:50] that's for only updating the clock [18:56:10] I bet it's around 0.15-0.2 [18:56:23] dT? [18:56:27] yeah [18:56:28] .15 [18:56:37] knew it, that seems very predicatable [18:56:41] https://www.dropbox.com/s/f1wcg6ol64ylov6/Screenshot%202021-09-27%20125610.jpg?dl=0 [18:56:42] our clock drift [18:57:10] so the CMC clock and the TEPHEM work together well [18:57:11] I didnt need to use this page to uplink at all did I [18:57:18] nah [18:57:21] ok cool [18:57:28] although you can if you are bothered by a 0.15 second clock drift [18:57:31] lol [18:57:35] Why not [18:57:50] mission rules need better than 0.5s for rendezvous [18:58:07] righty back to 0.15 [18:58:21] right [18:58:38] hmm? [18:58:53] it doesn't automatically carry over the time [18:58:55] I did an uplink and its still 0.15 [18:59:03] you need to manually put in 0.15 on the right side [18:59:06] Ohh [18:59:08] INP button [18:59:15] you uplinked a +0.00 increment [18:59:29] do I do the negative of the dT [18:59:32] I don't know why you would do that, but I wanted to allow the uplink of any input DT [18:59:38] gotcha [18:59:50] nah, same as on the left side [18:59:53] the DELTA T [19:00:09] and we are all balls haha [19:00:33] so now I need to recalculate my MCC and LOI [19:00:52] it should give the same DVs etc, but it's better yeah [19:01:03] also for a Maneuver PAD with a useful GET haha [19:01:19] Yeah also my LOI isnt going to be at 86 hours anymore [19:03:19] dVs didnt change [19:03:23] good sign [19:05:03] checkout monitor for 90:59:22 GET should do good things now [19:05:52] -179.961 [19:07:10] hopefully still is correct after LOI [19:07:29] after LOI you can use the FIDO Orbit Digitals, it has a longitude search option [19:41:10] MCC4 is next so I will let you know [19:41:22] Now what about this DOI computation [19:52:00] using Alex' procedure, I manually adjusted the TIG to get 0 DVZ for it. And I ignored the longituder of perilune. [19:52:03] longitude* [19:52:30] put that on the MPT and then calculated DOI-2 with the descent planning [19:55:54] but I mainly wanted to see what DOI-2 comes up with when DOI-1 has 0 DVZ [20:42:04] night! [20:57:44] .tell indy91 looks like the vent points for the urine and water are off now :P [20:58:04] .tell indy91 https://www.dropbox.com/s/bkrq40dwx9dq5b2/Screenshot%202021-09-27%20145703.jpg?dl=0 [20:58:13] .tell indy91 https://www.dropbox.com/s/v34pl8bpfdx1x2f/Screenshot%202021-09-27%20145739.jpg?dl=0 [13:20:12] good morning [13:23:57] morning [14:17:11] hey [14:17:31] yeah, seems like particle effects aren't shifted with ShiftCG [14:17:37] yeah haha [14:18:03] I'll just have to make a function and call it from our shifting code [14:18:46] Apollo 13 O2 vent is a implemented as a thruster and not a particle effect [14:19:03] thruster get shifted automatically [14:24:59] did you have a chance to test the SM RCS and SCS fixes? [14:25:20] But I guess Matt, Thymo and myself have already tested it enough, I think I'll just merge it [14:26:40] Haha yeah I am still on my J mission branch I have not yet [14:27:29] most noticable thing is the SM RCS thrusters pointing more outward [14:27:47] and SCS Auto TVC works a lot better with the shifting CG [14:28:00] merged [14:28:45] yay! [14:28:53] \o/ [14:32:09] now I can go back to scratching my head over things I don't understand about the RTCC [14:34:25] Thymo, did you ever make any progress on the telemetry stuff you were working on? [14:38:39] speaking of RTCC, my LOI seems to have a large dvz [14:38:43] compared to actual [14:40:49] You mean wiring up the PCM? I postponed it for a little bit as doing that would also mean overhauling all our socket stuff and I still haven't decided how that's gonna look exactly. Are you waiting on them? [14:41:39] rcflyinghokie, how large [14:42:25] -237 [14:42:33] compared to about -37 [14:42:48] DVZ and Y look about on point [14:42:53] *dvX [14:43:45] might or might not be different lunar gravity models [14:43:53] speaking of large DVZ [14:44:02] what is this TEI-4 that Apollo 17 got... [14:44:17] plus 2004.8, Minus 2951.1, Minus 1547.3 [14:44:24] ??? [14:44:43] good morning [14:45:03] hey Alex [14:45:18] Wow thats a big burn lol [14:45:48] huge Y and Z lol [14:46:58] the later PADs get better, but not much [14:47:08] TEI-5: plus 2329.8, minus 2403.1, minus 1152.8 [14:47:17] maybe that tries to get back to 40° return inclination or so [14:47:56] 17 had a larger one [14:48:19] RTCC doc has 66.5D [14:48:28] yeah [14:48:36] you would need a large DVY to get back to 40° [14:49:01] you could try to calculate those with the 40° constraint once you are in lunar orbit [14:53:05] so there are some updates to SCS TVC? [14:53:32] indy91 I also want to try that iteration technique for DOI [14:54:09] AlexB_88, yes, I noticed during TEI, which has the SPS yaw gimbal shift a lot during the burn that it wasn't working quite right, didn't keep the thrust vector inertial [14:54:35] and I also implemented the control gains for CSM alone vs. CSM/LM docked [14:54:40] so the CG DV switch now does something [14:54:52] and the SM RCS thrusters weren't pointing quite right [14:55:19] doing an ullage burn for TEI resulted in a lot of rotation [14:55:40] that's a little bit better now. The change is quite noticable if you look at the thruster effects [14:56:01] rcflyinghokie, AlexB_88 might even be more of a help with that, my method is really purely trial and error [14:56:52] haha sure [14:57:03] trying to figure out LOI REFSMMAT right now [14:57:12] the heads up/heads down debate [14:57:21] isn't it always heads down [14:58:06] I think so [14:59:02] and confirmed with the angles in this case [14:59:50] you could probably even confirm it with the REFSMMAT shown in the SCOT [15:00:07] if you compare those numbers to the uplink page [15:00:29] very true [15:00:36] I did that for 12 for some of them [15:01:34] REFSMMAT page shows a different REFSMMAT [15:01:40] because of coordinate system weirdness [15:01:48] that is in ecliptici coordinates [15:01:56] yeah i used the uplink page [15:01:58] while the uplink page has the correct coordinates [15:02:02] ecliptic* [15:04:01] AlexB_88 mind helping me compute DOI for Apollo 17? [15:04:16] I have LOI on the MPT [15:04:44] is it normal for the 4-jett ullage to rotate the CSM alone? [15:05:32] yes [15:05:40] the shifting CG made that stronger [15:05:48] because the CG is no longer on the centerline [15:05:53] rcflyinghokie, sure in a few mins I am just working am something [15:05:59] no worries [15:05:59] on* [15:06:00] the SM RCS direction fixes made it weaker again [15:06:55] I guess a 2 jett ullage would be better in this case [15:08:39] is this with a very light CSM? [15:09:09] the ullage is done in att hold anyway, so you won't actually change attitude [15:09:52] hmm I am in min deadband SCS [15:10:11] and Att 1/Rate 2? [15:10:15] yes [15:10:19] pre-PDI CSM [15:10:42] doesn't do att hold? [15:11:24] Manual Attitude in Rate Cmd? [15:12:35] ok so I was using the direct ullage button [15:12:43] that wasn't holding attitude no [15:12:50] ah right, I had noticed that [15:12:55] but doing it with the THC is fine [15:13:24] there is an inhibit logic in the SCS that prevents att hold when you press direct ullage [15:13:26] among other things [15:13:33] I found that weird [15:13:36] ah ok [15:13:42] have to look at it again [15:14:00] what helps is to interrupt the ullage for a second or so every few seconds [15:19:10] just did a 3000 ft/s burn in a prograde attitude to test [15:19:31] CSM alone AUTO SCS TVC [15:19:41] kept the attitude very well [15:20:03] indy91 when I replace the LOI burn on the MPT it displays an Ha of 216.7 and Hp of 23.9? [15:20:14] Did I miss something? [15:20:52] that HA and HP looks like the TIG isn't right [15:21:39] looks right to me [15:21:42] it didnt change [15:21:56] I had an LOI on the MPT and all I did was recalculate it and replace [15:22:11] LOIP table didnt change [15:22:34] I saw this before as well, only happens with LOI replacement that I have seen [15:22:44] interesting [15:23:10] yep, can replicate it [15:23:13] I'll take a look [15:23:37] great [15:23:39] rcflyinghokie, you can't use the normal DOI targeting for Apollo 17 DOI-1 [15:23:43] Right [15:23:49] Which is why I am asking :) [15:24:03] I see the snipped in the RTCC manual but it wasnt entirely clear to me [15:24:07] snippet* [15:24:11] I found that using the GPM processor is best [15:31:14] iterating I got 93:11:18 with dvx -192.8 dvz +65.2 [15:31:17] seems reasonable [15:32:48] Using the GPM with the MPT active will take into account maneuvers on it, correct? [15:32:50] https://www.dropbox.com/s/qgoxj56akidgqtg/Screenshot%202021-09-28%20093226.jpg?dl=0 [15:34:01] yes [15:34:21] when I tried this I made it a burn without DVZ [15:34:30] and only got 9.5 ft/s DVZ for DOI-2 [15:34:52] so I don't think this is the right procedure to use, because 65 ft/s is a lot [15:35:52] actual was 47.8 [15:36:01] oh, quite a lot [15:36:15] Noun 81s; minus 01916, all balls for Delta-VY, Delta-VZ is plus 0047.8; [15:36:30] AlexB_88, your procedure puts longitude of perilune at a specific spot [15:36:37] which is what I used [15:36:45] is that accounting for Moon rotating? [15:37:09] yeah [15:37:18] LONG P = 31.36 [15:38:00] I think I had used that value since it will rotate to the correct position for PDI [15:38:47] rcflyinghokie, your are following the procedure in my guide? [15:39:22] yes [15:39:36] there might be two TIGs where that LONG P is achieved [15:39:46] maybe the other one is better? [15:40:26] this TIG is awfully close to actual [15:40:43] 18 seconds difference [15:40:44] maybe this isn't so bad then [15:41:13] but I needed only 9.5 ft/s of DVZ in total for DOI-1 and 2 combined when I tried your scenario [15:41:30] not sure why [15:42:45] but making it so that DOI-2 has 0 DVZ and DOI-1 has a little bit only could be quite tricky [15:43:48] https://www.dropbox.com/s/kxhbju54c5shyr6/Apollo%2017%20-%20LOI%200005.scn?dl=0 [15:43:58] ah found the LOI replace bug [15:44:01] feel free to try again, about an hour from LOI [15:44:08] it used masses from after the last burn on the MPT [15:44:28] so post LOI masses for calculating the replacement LOI [15:44:40] ah [15:45:16] I would suggest putting that DOI-1 on the MPT and then calculate a DOI-2 [15:45:42] sure [15:45:51] DOI2 using the descent planning? [15:46:06] yep [15:46:24] like an Apollo 11 DOI [15:47:28] for one rev later? [15:49:48] and use 40000 feet for DOI-2 [15:50:28] yeah, I think it's all set up for DOI-2 by default [15:50:35] it is [15:50:40] just needs vector time and thresholds [15:50:59] 94:52:02 -9.8 0.0 -21.2 [15:52:03] hmm [15:52:07] that is worse than my solution [15:52:20] and next rev is 96:48:07 -9.8 0.0 -18.8 [15:52:39] uhh wait [15:53:12] nominal DOI-2 time is at 112:01h [15:53:46] "for one rev later", I thought you meant PDI one (half) rev after DOI-2 [15:54:08] it should be N = 0, and threshold time maybe 111:30 or so [15:54:17] Well I asked if I was using 1 rev after DOI 1 :P [15:54:33] yeah, I misunderstood, thought you were asking about the N [15:55:05] ahh [15:55:13] -9.4 0.0 0.5 [15:55:17] perfect [15:55:37] so that DOI-1 should be god [15:55:39] good [15:55:59] one purpose of the late DOI-2 is that they didn't feel safe having such a low perilune over the mountains for the hours between LOI and PDI [15:56:11] rcflyinghokie, just did the DOI-1 calc with your scenario [15:56:13] so DOI-2 has a nominal perilune lowering effect [15:56:37] DVX -192.8 and DVZ +65.2 [15:56:39] so doing DOI-2 just after DOI-1 would get you flying over the bad mountains for all those hours :D [15:56:40] makes sense good way to have a mascon pull you into a mountain :P [15:56:47] I think that is quite close to the flightplan [15:56:59] AlexB_88 its very close to the actual [15:57:16] I am happy with it [15:59:44] indy91 https://www.orbiter-forum.com/threads/nassp-8-apollo-7-realtime-simulation-attempt-preparation.40153/ [15:59:54] oh boy [16:00:06] yeah... [16:00:19] Have fun :) [16:05:26] I guess the GPM way of doing DOI-1 is a bit sketchy but at least it seems to work [16:05:50] indy91, maybe Apollo 17 had a more recent version of the LDP? [16:06:14] yeah, they already had an updated version for 13 [16:06:25] for the first CSM DOI [16:07:09] they changed something in the calculations, optionally, to use the coasting integrator instead of Kepler orbit or so [16:07:26] must have been a very inefficient implementation [16:07:47] FIDO was always joking about the person in the RTCC being able to get a coffee while it's running, because it takes so long [16:08:16] we have the RTCC requirements with a first update document [16:08:31] I think that takes it to the state that the LDP was in by Apollo 11 [16:14:34] we have scans of the first pages of (nearly) all MSC memos until early in 1971 or so [16:14:53] so there is probably missing a lot that we don't even know about yet [16:15:28] right [16:17:37] NARA still not open again... [16:20:06] that's really my next priority when NARA is open again. Not getting scans of specific documents, but finding out if they even have certain documents [16:34:23] was there any more progress with changing to ShiftCG function for the saturn staging? [16:40:41] yeah a little bit [16:41:00] loss of clickspots with apex cover jettison is fixed, I think [16:44:04] LOI in work with the new changes [16:44:55] that Y component is so evident looking at the ground track [16:45:24] hmmm [16:45:43] I am watching in 2d through the hatch and the LM is slowly moving up and down in the window [16:46:46] which panel? [16:47:01] hatch [16:47:32] side hatch view in 2D (the one that shares the hatch controls and panel 601 etc) [16:48:39] very fine LOI [16:49:13] maybe some views are still not right [16:49:21] I guess I had mainly focused on the VC... [16:50:13] no worries just passing the observation on [16:50:38] While I didnt SCS the LOI, the residuals were tiny [16:50:57] yeah, I think the CMC likes it, more than before the shifting CG update [16:51:34] N48 post burn showing +1.83 -.38 [16:51:44] +1.28/-0.04 prior [16:52:26] I think that agrees with the charts [16:52:50] https://history.nasa.gov/afj/ap14fj/csmgc/a14-csmgc-5-15.jpg [16:53:16] looks good! [16:53:19] the general trend at least [16:54:02] ShiftCG should shift the camera position [16:54:08] Thymo, not waiting per se, but I wanted to make sure we weren't going to have a massive merge conflict to resolve down the road. [17:03:26] rcflyinghokie, not really sure what's going on there, I see the camera position shifting by calling GetCameraOffset [17:03:35] but it should be shifting, ShiftCG does that [17:03:47] does it shift in the wrong way or something... [17:07:13] well the LM shouldnt move in the window [17:08:28] yeah [17:08:37] CG moves, camera moves relative to the CG [17:08:42] and the view should stay the same [17:11:51] rcflyinghokie, MaxQ isn't having RTCC issues, the orbit is bad [17:12:18] Yep I have the scn open [17:12:28] I was just about to edit my post haha [17:12:40] Wonder what happened [17:13:20] Bad TLI? [17:14:32] must be, if there was no maneuver after TLI [17:21:15] wonder how a bad TLI occured [17:28:29] yeah [17:29:47] maybe I can tell from the LVDC state in his scenario [17:31:08] looks good from what I can tell [17:31:21] it at least tried to target the right orbit, I think [17:31:49] scenario is at 7 hours, but LVDC already is shut off [17:32:32] ah no, that's fine [17:32:39] he never started TB8 [17:32:57] time when the LVDC shuts itself off is earlier when that happens in TB7 [17:33:57] TB6 time was good [17:37:32] if TLI did go well wouldnt it have taken SPS to change the orbit that much? [17:41:34] yeah [17:41:48] the separated S-IVB has J-2 fuel left [17:41:55] so didn't run out of fuel [17:42:13] Yeah i checked that as well that was my initial guess [18:38:42] well my optimal DOI-1 time has shifted post LOI [18:39:00] DVZ is a lot worse :( [18:39:28] +92.3 [18:47:23] did the TIG change, too? [18:47:33] or is it basically the same TIG as before [18:49:46] oh, you said haha [18:49:50] I was only focusing on the DVZ [18:50:13] I still feel that DVZ shouldn't really be necessary [18:52:12] the real PAD I think had a ~60 ft/s DVz for DOI-1 [19:01:36] 47.8 [19:02:26] and now I need to change the time again lol, hitting CLC again after 30 minutes of coasting the LONG P is different [19:08:19] but hey..... [19:09:10] https://www.dropbox.com/s/k2xntt984nxon44/Screenshot%202021-09-28%20130854.jpg?dl=0 [19:09:15] look at that dv [19:09:52] so whats changing here [19:10:09] I have just been in P20 this whole time post LOI [19:10:15] no translation [19:13:23] no idea [19:13:35] MPT is active? [19:14:20] yes [19:14:20] I can take a look at the scenario [19:15:14] Sure [19:15:15] https://www.dropbox.com/s/53rnx3skdl8myb6/Apollo%2017%20-%20DOI%20Computation.scn?dl=0 [19:15:35] No idea why the TIG changed as well as the DVs dropped [19:16:55] there is a DOI on the MPT [19:17:00] looks weird though [19:17:23] and there is no vector time input [19:17:40] so you probably had a vector randomly inside the DOI already on the MPT [19:17:46] That should be the one I just put on there [19:18:03] Oh I take that back [19:18:14] Thats the one from 30 minutes ago I forgot to remove [19:18:29] that maneuver in the picture has to be inside or after DOI [19:18:34] because the DVX makes no sense either [19:19:21] I thought I had removed it from the MPT [19:21:06] made the deletion failed somehow, because in the scenario the maneuver looked weird [19:21:07] so yeah the dvz has increased a lot after LOI [19:21:09] no maneuver code [19:21:31] I reloaded and it seemed to delete properly [19:23:07] yeah, I could delete it [19:23:09] just looked weird [19:23:26] but the DVZ has certainly increased [19:24:16] And when I do the DOI-2 its huge [19:25:02] something isnt right [19:26:02] maybe something was bad with the LOI solution [19:26:12] you said there was a weird DVZ [19:27:13] it was higher than the actual pad [19:27:53] pre LOI scenario? :D [19:27:58] just want to check [19:28:29] sure one sec [19:29:31] https://www.dropbox.com/s/kxhbju54c5shyr6/Apollo%2017%20-%20LOI%200005.scn?dl=0 [19:31:32] didn't you say someth with +400 DVZ? [19:31:37] something* [19:32:03] I get -237 [19:33:36] no, -237 [19:33:46] compared to -37 [19:34:02] ah ok [19:34:08] remembered that wrong then [19:34:36] I just dont really understand why the maneuver has change so much [19:35:01] unless there was something hung on the MPT earlier [19:35:07] in any case the dvz seems high [19:36:01] yeah LOI calculation seems fine [19:37:21] maybe it changes a lot because DOI is at perilune, but does a orbit rotation with HA and HP that are both different from before DOI [19:37:33] so a small difference in LOI already changes perilune altitude a bit [19:37:58] What about the DOI-2 with -125 dvz [19:38:51] thats what is concerning me here [19:39:21] is that with DOI-1 only having DVX? [19:39:31] or is that with DOI-1 having that DVZ of 90 or so [19:40:39] Thats with the DOI-1 I just computed [19:42:36] This is on the MPT https://www.dropbox.com/s/k2xntt984nxon44/Screenshot%202021-09-28%20130854.jpg?dl=0 [19:42:49] https://www.dropbox.com/s/rm03m2ium8i6s5f/Screenshot%202021-09-28%20134203.jpg?dl=0 [19:42:56] Am I missing something? [19:43:02] yes [19:43:16] that was calculated when you already had DOI on the MPT [19:43:34] no, I looked at the first picture [19:43:50] so the one with DVZ being 92 [19:43:52] hmm [19:43:54] yeah [19:44:06] that on the MPT gives me that huge DOI-2 DVZ [19:44:12] that does indeed not make sense how that would result in any DOI-2 DVZ [19:45:22] now I can't move the maneuver to the MPT... [19:47:47] now it worked, no idea what happened [19:48:38] are you able to replicate the results? [19:49:07] yeah [19:50:52] I'm seeing something very weird [19:51:54] landing site coordinates are screwed up [19:51:59] in the RTCC [19:52:10] 42°W 4°S [19:52:34] interesting I havent even been to the LS page [19:52:34] your pre LOI scenario still had it right [19:52:45] Did that DOI calculation change things? [19:52:58] hmm, it shouldn't [19:53:11] Or let me rephrase, other than updating in that page, is there any way the LS changes [19:53:11] what could have done it is a trajectory update [19:53:28] DC button with a spacecraft that is landed [19:53:40] is that maybe where the S-IVB landed... [19:54:00] Ohh [19:54:05] yep [19:54:06] I did an SIVB calculation [19:54:47] ah hah [19:54:59] the DOI-2 is back to a 0.5 dvz [19:55:02] hahah [19:55:24] ok that makes me feel better [19:55:25] ok, how did this happen and should something be changed [19:55:58] I wanted to see where the SIVB was going to impact, but I think it had already impacted when I checked (and put it on the VPS) [19:56:13] yeah, that automatically updates the LS vector [19:56:26] the coordinates [19:56:44] As far as what to change, thats a good question [19:56:59] it kind of has to be that way for the DC button to work for landed vessels [19:57:19] is there a check on if its landed or not? [19:57:26] yes [19:57:37] perhaps reverting that back to the landing target when putting a flying vessel back in there [19:57:56] It wouldnt help if I didnt add the LM back of course [19:59:32] hmm, I think for convenience I implemented this slightly wrong anyway [20:00:25] a vector that is stored as a ground tracking vector would just have the normal state vector format, plus landing site indicator [20:00:52] and if that is used for a TUP then that input vector would be used, and not the stored landing site lat, lng, rad [20:01:19] the stored landing site coordinates are always used as a target for PDI [20:01:35] and after PDI it uses that to generate the lunar surface ephemeris vectors [20:02:00] so maybe I should just make that work right and not update the LS coordinates there at all [20:04:09] all that means is that you need to update the LS coordinates manually after landing, but without the MPT you have to do that anyways [20:05:32] and by manually I mean "Landing Site Update" page [20:06:16] Yeah I am fine with that [20:06:55] so if you have to initialize the MPT with landed state vector then right now that really only sets the LS indicator and nothing else [20:06:57] Checking again now I need to change my TIG again for DOI-1 [20:07:06] the LONG P keeps changing lol [20:07:28] is that after reloading the scenario or also if you keep it running [20:07:48] keeping it running [20:08:00] have you merged the SM RCS update? [20:08:03] yes [20:08:15] I hope that isn't somehow causing uncoupled thrusting... [20:08:29] Hmm [20:08:33] Maybe not [20:08:38] I merged this morning [20:08:58] I think the change to the SM RCS directions is quite noticable haha [20:09:12] yeah it looks like I have it [20:09:27] got merged 6 hours ago [20:09:51] can't be uncoupled [20:10:00] has to be some iteration tolerance for the GPM or so [20:10:12] yeah its in [20:11:49] I guess because I am closer to my position, I am at my pre LOI solution pretty much [20:12:10] time is closer to actual and dvz is lower lol [20:12:51] that all sounds weird haha [20:13:14] yeah [20:13:20] the new thruster directions are so perfect that Orbiter doesn't even show a tiny force vector if I command a rotation in any direction [20:13:29] great! [20:13:55] they are cross checked against the AOH Data Book, would have been surprised if it was any different to the real thing [20:14:01] CSM Data Book* [20:15:14] does the solution jump around with MPT active and inactive? [20:15:17] or only one of them [20:16:56] or do you have the DOI on the MPT again [20:17:07] and the TIG is inside the maneuver again [20:17:12] making the DV random [20:17:41] GPM processor needs some more MPT compatibility [20:17:55] like a separate vector time [20:18:51] It hardly changes with it active or inactive [20:18:58] it was after elapsed time [20:19:19] LONG P changed maybe 0.1-0.2 between active and inactive [20:19:33] 0.01-0.02 [20:19:34] do you have a DOI on the MPT right now [20:19:36] no [20:19:39] ok [20:19:59] I've waited a bit and recalculated, but none of the numbers change [20:20:30] so larger change with MPT on and off here [20:20:40] My wait was about 30 minutes [20:20:49] let me update my DC vector [20:21:41] maybe you activated my lunar gravity model plugin that I never published :D [20:22:10] lol [20:22:37] LONG P 31.35 with and without MPT with an updated DC vector [20:22:52] but the tme changed another second to get the LONG P [20:22:56] time [20:23:20] how accurate are you trying to make it? [20:25:03] trying to get the LONG P 31.36 [20:25:58] oh, I think the LS coordinates fix is relevant [20:26:06] HA and HP are relative to the landing site radius [20:26:17] so changing that is what really changed the DVZ back from 90 to 65 [20:26:24] haha makes sense [20:26:30] my dv has not changed much since [20:26:39] only tig by a second or so [20:27:20] so that and the burn left on MPT were the primary issues [20:27:25] yeah, I think that is not so big of a change for this. It needs some orbital travel for the orbit rotation (DVZ) to be any different [20:27:39] I think so [20:27:56] although I still don't know how you had an empty maneuver code on the MPT haha [20:29:02] nor doI [20:30:46] ha, you said DOI [20:31:17] Ah! [20:31:23] No pun intended? [20:31:32] Speaking of, my final DOI PAD [20:31:33] https://www.dropbox.com/s/bac88bee9mffufz/Screenshot%202021-09-28%20143100.jpg?dl=0 [20:32:11] good enough [20:32:44] N42 shows an Hp of 13.2 [20:32:53] Hopefully I dont hit anything :P [20:36:33] nah, high enough [20:36:52] especially without the right gravity model [20:37:16] Well if the paint gets scraped I know who I am calling ;) [20:37:19] https://i.imgur.com/8rq3mUI.png [20:37:26] this is why you have to be afraid of mountains [20:37:41] oh yes [20:42:47] I can't wait for the day when we have proper lumpy moon gravity :) [20:52:37] oh no. my telemetry branch has a merge conflict...again. [20:53:26] :( [20:56:13] those are never fun [20:58:18] bank A DOI, residuals .1 0 .1 with -5.5 on the EMS [20:58:53] nice residuals [21:00:41] night! [21:01:21] see ya [21:16:29] Hmm not sure if the optics can see the LM like this :P https://www.dropbox.com/s/mjnwusw70x7wflj/Screenshot%202021-09-28%20151604.jpg?dl=0 [22:57:10] uhhhh... probably not lol [13:27:30] hey [13:29:16] morning [13:31:14] I completely forgot the orbiter commands work on the SIVB [13:33:11] we really need to disable that [13:37:28] yeah theres no reason to have them is there [13:37:59] well, we need custom engine sound code if we disable that [13:38:03] like we already have for the RCS [13:40:07] hey guys [13:42:00] hey [13:45:04] morning [14:32:23] someone want to help me with a RTCC problem? It's a conceptual issue more than anything [14:33:07] I can try [14:33:13] do you have NTRS ID 19730062603? [14:33:23] one of the IBM RTCC documents [14:33:51] I dont think so [14:34:57] please read all of page 79 [14:35:23] ok [14:37:42] I have an implementation of both functions that page talks about. But RMMEACC needs to change to work right with some more general changes I am doing in the RTCC. [14:38:14] we don't have the program flow for RMMEACC, but we have it for RLMTLC. So we know all its input/outputs [14:38:41] the ephemeris in Earth centered inertial coordinates. So a collection of state vectors, maybe 2-3 minutes apart. [14:38:58] in low earth orbit this is likely to be more than 1000 state vectors [14:39:29] RLMTLC takes an ephemeris in Earth centered true coordinates as input [14:39:43] so you can basically directly calculate longitude from that kind of state vector [14:40:22] my old implementation is: Give pointer to the entire ephemeris to RLMTLC, and convert to ECT and lat/long in RLMTLC [14:40:44] but I know that is wrong from the program flow of it [14:41:00] so basically RMMEACC needs to do a few things it currently does not. [14:41:15] convert ECI to ECT, decide which vectors to convert and detect groundtrack reversal [14:41:22] pretty sure RLMTLC can't do that [14:41:51] I have trouble figuring out how RMMEACC should do all that... [14:42:14] it could just convert the entire ephemeris to ECT, temporarily. That would be a lot of temporary memory being used haha [14:42:51] funny how many spelling errors are in here [14:42:55] yeah [14:43:20] even says RLMTCL once instead of RLMTLC [14:43:35] yeah that threw me off at first I was looking for another subroutine [14:45:45] but yeah it doesnt really explain the details of how RMMEACC puts everything together [14:46:14] either it converts the entire ephemeris to ECT and maybe stops doing that when it detects ground track reversal [14:46:29] or maybe it does it piece wise and gives that to RLMTLC [14:46:43] but then RMMEACC would need to know roughly how many state vectors are in one rev [14:46:56] and the ephemeris can have maneuvers like TLI in it [14:47:24] is it known how many state vectors are typically used in 1 rev? [14:47:32] or does it vary [14:48:23] well it's probably fairly constant [14:48:35] but only without maneuvers [14:48:49] you could e.g. calculate the orbital period with the first state vector [14:49:30] right [14:49:36] but your accuracy would be limited [14:50:05] yeah there might be a maneuver which throws it off and then it doesn't even have a cape crossing in that piece of the ephemeris [14:50:52] the documents keep insisting the ephemeris is only kept in ECI coordinates. If they would just store it in multiple coordinate systems you could cut down on a lot of converting of state vectors [14:51:11] and extremely large amounts of temporary storage space [14:51:33] RMMEACC is probably going to have to convert the entire ephemeris to ECT in some cases [14:51:52] but is there even enough temporary storage to do that in one bug chunk... [14:51:53] big* [14:52:20] in their system or in the emulation [14:53:03] in the real RTCC [14:53:22] I mean, I could do it in the most wasteful way possible in terms of memory [14:53:31] that would be simpler in some ways [14:54:23] I have the table format for the ephemeris for the very early versions of the RTCC only [14:54:45] it says one state vector needs 48 bytes [14:55:29] hmm, even if the ephemeris is 2000 SVs, that's less than 100 KB [14:55:35] yeah thats not bad [14:55:36] that shouldn't really be a problem [14:55:41] not even for the RTCC :D [14:55:54] its hard to think in terms of KB these days haha [14:55:56] and RMMEACC definitely does conversions [14:56:04] I have the list of errors from RMMEACC [14:56:28] "ELVCNV UNABLE TO ROTATE EPH. TO ECT." [14:56:34] ELVCNV is the vector conversion routine [14:57:28] yeah I think I'll go with the route of converting the entire ephemeris, but checking on ground track reversal [14:57:31] on each SV [14:57:50] so if you have an ephemeris with EPO and then TLI, shortly after TLI it will go backwards in terms of longitude [14:57:55] so ground track reversal [14:58:37] sometimes you just have to spell things out to come to a conclusion, so thanks :D [14:58:48] haha no problem that was all you :P [14:59:07] this routine is specifically for earth longitude crossing, correct? [15:00:29] it works for the Moon, too [15:00:44] RLMTLC takes either ECT or MCT as input [15:01:29] would this come into play for that DOI computation? [15:01:54] in what way? [15:02:50] this is mainly relevant for displays that can use the rev number as an input [15:02:54] for MPT mode only [15:03:35] I think you need to initialize the cape crossing table again when you enter lunar orbit [15:03:36] I was thinking for that longitude crossing iteration [15:03:52] right, so, RLMTLC is also used by the FIDO Orbit Digitals display [15:04:19] which can give you the time when you cross a longitude [15:05:02] but that's all it does, not place perilune at a longitude or so [15:05:18] the GPM page finds the actual apoapsis and periapsis positions [15:05:23] and then calculates lat/long from that [15:05:43] the GPM page also has the option to have the maneuver at a specific longitude [15:05:57] but that is a separate calculation, doesn't use the ephemeris, but a single input state vector [15:06:40] there is a lot of these "duplications" in the RTCC actually. Functions that nearly do the same thing, but one variant uses and interpolates the ephemeris and the other uses one input state vector [15:09:02] Ahh [15:09:25] the page I asked you to read is not even from the final version that was first used on Apollo 8, but wrong the simulation version that didn't even have proper lunar orbit support yet [15:09:33] from* [15:09:53] this whole document is split in 3 volumes [15:10:03] volume 2 was on the archived NTRS [15:10:09] volume 1 is at UHCL [15:10:13] volume 3 is ???? [15:10:22] finding that volume 3 would be nice haha [15:10:54] ah a missing piece yay [15:11:18] if I didn't even know exactly how RLMTLC works I could make something up [15:11:24] and would have an easier time [15:11:38] but when I do know something exactly I really try to not deviate from it [15:20:07] Yeah that makes perfect sense [15:44:21] 7 hour rest period then we shall see how well all these burns worked out with Challenger's powerup [16:01:57] oh any idea what this is? "UPLINK: JET - ON MONITOR LOADS" [16:02:13] Apollo 17 flight plan about 96:12 [16:03:40] could be an EMP [16:04:23] 523 maybe [16:04:32] Then at 106:45 ish, "TERMINATE JET - ON MONITOR" "P30" "P20" "V21N26 (00000)" [16:05:53] EMP 523 mentions P30 [16:06:01] where are those listed [16:06:27] https://www.ibiblio.org/apollo/Documents/HSI-208442.pdf [16:08:40] interesting program [16:08:55] why would you leave it on during a rest period lol [16:11:28] because they kept P20 running [16:11:45] I'd say a master alarm with a jet failed on is quite useful [16:12:11] so that they quickly wake up [16:12:44] ah I see [18:32:26] n7275 my first observation is my glycol pressure sits a bit lower now [18:32:33] in the LM [18:47:50] time to test the evaporator [19:46:27] .tell indy91 I will forget if I dont ask...why did we do this with the water separator RPM? Shouldnt it return the selected sep RPM and not the larger? if (*Water_Sep1_RPM > *Water_Sep2_RPM) [19:46:27] { [19:46:28] return (*Water_Sep1_RPM); [19:46:28] } [19:46:29] return (*Water_Sep2_RPM); [20:38:09] rcflyinghokie, that makes sense, less of it should be in the vapor phase to reach equilibrium now [20:51:34] Where in the codebase does that live? [20:53:19] hSystem.cpp iirc under /src_sys/PanelSDK/internals [21:12:46] I found it in lm_ecs.cpp [21:15:06] rcflyinghokie: I don't know exactly what the supposed behaviour is but isn't the separator with the highest RPM by definition the selected one? [21:15:16] If it's deselected, its off, so RPM is 0. [23:59:40] Thymo, I am pretty sure the SC reads the RPM of the selected water sep [00:00:20] Right now what happens when you do the suit/fan test, it reads the incorrect sep RPM when you switch [00:00:39] so you get a delayed h2o sep light which is not correct [00:01:00] I need to look into the circuitry [00:13:00] And to answer that question, no the definition of selected one is not highest RPM because they take time to spin up and down [14:27:02] hey [14:27:28] is Libera having some SSL issues? [14:36:54] Not that I know of [14:36:58] What makes you think it does? [14:37:32] I couldn't connect until I set it to accept invalid SSL certificate [14:37:42] it always said "certificate has expired" [14:38:11] is that something on my end? [14:39:11] Works fine on my end. Check the date and time of your computer. If not that it might be the certificate you set up to automatically sign in. [14:40:13] date and time are correct [14:41:26] I haven't set up anything for a certificate [14:41:29] I use HexChat [14:44:11] yeah only works if I use that "accept invalid SSL certificates" option [14:47:33] ok turns I was wrong about the engine sound not playing if the main thruster group isn't defined [14:47:41] but it does play a slightly different sound [14:47:59] I checked the server certificate and its valid till October 31st [14:48:31] I'll put together a PR and you can have a listen. It takes a moment to get used to the new sound, but I think it's acceptable. We could also customize it if we want. [14:48:53] not entire sure which sound Orbiter Sound normally uses for the main engines, there is 3 similarly named sound files [14:49:44] I'm sure the sounds will change anyway if/when we switch to XRSound [14:50:58] right [14:51:13] but if we keep that slightly different "new" sound it's an easy fix [14:51:31] no longer can you control the thrust level of SPS, DPS and Saturn engines [14:51:37] at least not manually [14:59:43] nice. [14:59:50] morning, btw [14:59:53] That's good [14:59:56] Hey Matt [15:01:11] hey [15:01:33] pretty sure a noisy joystick throttle lever caused an early TLI cutoff for Max-Q on the forum [15:02:16] the DPS throttle control and engine start/stop is already custom code, so nothing should really be broken by this [15:02:26] but it doesn't hurt to test stuff [15:02:45] and listen to the engine sounds if they work and the changed sound is acceptable [15:04:41] it now plays AuxThr.wav from /Sound/Vessel [15:04:55] instead of one of the three mainext files I think [15:13:43] oh I think I know why I thought it wouldn't play any sound if I change it to THGROUP_USER [15:13:56] when I previously tried it I just deleted the thruster group entirely [15:14:01] so only individual thrusters [15:14:13] for those Orbiter Sound doesn't play sounds [15:14:25] but it does for custom thruster groups [15:25:12] indy91: Ryan also cannot connect due to an expired cert. I guess you were right after all. :P [15:26:21] haha, I saw him in the forum but not here, so I kind of already suspected that was the case :D [15:30:25] strange, no issues for me [15:35:15] https://scotthelme.co.uk/lets-encrypt-old-root-expiration/ [15:35:43] Root certificate expired today. Normally they are updated in advance, apparantly not on your systems. Trying to figure out why. [15:37:22] does ZNC not care? [15:41:39] yeah, the certificate that page mentions is expiring today for me [15:43:00] It should have been replaced by a different certificate by ISRG signed in 2015. For some reason your windows machines don't have it [15:43:14] I'm on Linux right now and I have the cert [16:02:14] that explains it for me too. [16:02:59] android appears to be fine too [16:04:22] what do you even do to update that [16:27:52] Windows update usually [16:28:27] I need to step away for a couple hours, I'll ask staff again when I get back [16:28:46] Basically, update anything that has to do with the internet :p [16:29:35] haha ok [18:03:35] indy91, would they have had the MPT populated with the full mission in the real RTCC, or just with the next few maneuvers? [18:04:30] Looks like it worked [18:04:35] hey Ryan [18:05:00] afternoon [18:05:04] n7275, they sometimes cleaned out the MPT and got rid of old maneuvers that were already done [18:05:54] and for planning ahead, they had the next maneuver or two on the MPT usually [18:06:11] but they were very often deleting or replacing upcoming maneuvers [18:08:02] they couldn't look too far into the future, there is always going to be ground tracking in between which makes you recalculate maneuvers [18:17:19] ahh okay. [18:19:55] they launched with a blank MPT [18:20:09] and then quickly added TLI, sep and evasive maneuvers [18:20:30] at which point RETRO could calculate abort PADs [18:26:41] were the same rtcc systems/routines used for mission planning? [18:29:14] you mean preflight vs. during the mission? [18:30:11] yes [18:30:16] I think the RTCC was really mainly a real time program for the mission and the hours before it. [18:30:26] not for long term planning [18:30:54] there was sometimes the problem that the operational trajectory was generated with different maneuver calculations than were available in the RTCC [18:31:24] RTCC was started up a day before launch or so. They could already put maneuvers on the MPT in preflight etc. [18:32:43] but not for the long term planning I believe [19:03:26] rcflyinghokie, about my PR, one side effect of not using the main and hover thruster groups anymore is that Orbiter Sound is using a different sound file for the engines [19:04:00] so it sounds slightly different now. I could use some feedback if the new sound is good enough or if I should try and make it use the same sound file as before [19:04:34] I will give it a listen [19:05:00] I think the DPS had a different sound than the others before [19:05:05] because it's a hover engine [19:05:11] Yeah [19:05:14] but now it's all the same [19:06:32] customthrustergroups? [19:07:07] yeah, THGROUP_USER instead of THGROUP_MAIN or HOVER [19:07:16] I mean the branch to merge [19:07:33] oh [19:07:37] yes [19:07:49] haha ok building now I will give it a listen [19:08:53] also do you remember why we coded the water separator RPM the way we did? [19:09:15] Shouldnt it return RPM of the selected sep? [19:09:52] LEM_ECS::GetWaterSeparatorRPM ? [19:12:07] yeah [19:12:25] checking [19:12:47] right now it only returns the fastest one, but I think it should return the selected SEP RPM [19:13:24] for example, when I do a suit fan test, I switch separators, and about a minute after I get the caution light instead of when switching separators because of that code [19:17:21] I see a xducer on each separator, GF1112R/GF1111R [19:18:19] And an angular velocity sig conditioner, but I cannot see what determines which signal is routed [19:20:05] And in the systems handbook CW logic, it says the input is GF9999 H2O SEP NO 1 [19:20:16] Would that mean it only reads 1? [19:28:34] hmm, I can't tell for sure from the actual schematics haha [19:29:29] but I am fairly sure it's not directly switched when the valve is switched [19:29:35] there is no electrical signal from that or so [19:30:01] but of course when the flow is interrupted to one of the separators the RPM should start going down [19:35:04] which suit fan test procedure do you follow. Apollo 17 LM Activation Checklist? [19:40:55] most recently yes [19:41:34] But the procedures are the same [19:42:09] The difference is the mention of the h20 sep light [19:42:42] where in the procedure do you switch the separators and immediately get an alarm? [19:44:32] so that happens when you do the initial ecs activation [19:45:04] page? [19:45:12] I'm only seeing suit fan being switched off [19:45:40] and what happens there is explained in the AOH Volume 2 [19:46:03] I mean the behavior currently is you get an h20 sep well after the procedure [19:46:48] "When suit fans are deactivated, water separator will slow down, causing delayed activation of ECS caution light and H2O SEP component caution light. Time for water separator to slow down is approximately 15 seconds when wet; 2.5 to 3 minutes when dry" [19:47:20] yes [19:48:14] after for example doing the suit fan/h20 sep check, I get a h20 sep light for about a second about a minute after [19:49:19] in the more expanded AOH Volume II procedures the quote from above is just after pulling the suit fan 2 CB [19:50:22] so it might take up to 3 minutes for the H2O sep light to be on [19:50:51] after pulling the CB, so during the procedure [19:51:09] "...when selected water separator comes up to speed" [19:51:50] to me that tells me the caution logic is dependent on the selected separator [19:52:17] Again I am just trying to figure out if that if 1 is > the other logic is correct [19:52:59] it's annoying that not even in the detailed drawing it's clear what happens there [19:53:05] very much [19:53:18] but I think it's still the best guess for what happens [19:53:29] there is no electrical signal from the selector, I am pretty sure [19:54:49] you just shut off the pipe to the other separator [19:55:01] so it will go down in RPM over time as there is no flow [19:55:13] and you switch to the other one which will go up in RPM [19:55:27] so there might be a short period where the RPM in both is below the threshold [19:55:35] although getting that condition for 1 second seems weird [19:55:44] well I was watching the TM [19:56:09] Watched the one sep go below the threshold and just a few moments after it switched [19:56:53] watching the RPM on the TM basiclaly looked like it slowed down then sped up, but of course it was the switchover point from that code [19:57:15] I'll investigate further, of course [20:02:16] GF9999 is also called "water separator no. 1 and 2" [20:02:28] so pretty sure it's not just 1 getting measured [20:04:11] its funny in the LM8 Handbook Caution schematic it says "GF9999 H2O SEP NO 1 [20:09:29] thats what confused me [20:11:10] hmm right [20:11:19] well most documentation says "selected separator" [20:11:30] but that doesn't mean much [20:11:38] separator always slows down when it's not selected [20:11:42] right [20:12:28] It could also be the rpm times are different with Matt's substance changes so I am seeing that behavior [20:12:50] Might need to be adjusted if this goes into a PR [20:13:27] yeah sure [20:13:59] it has hardcoded values for speeding up and slowing down [20:14:19] it calculates a desired RPM number from the flow [20:14:28] and then accelerates or decelerates [20:14:30] yeah i remember I used guess and test to determine those lol [20:14:47] Based on a 2 minute spin up and 1 minute spin down [20:14:52] ah [20:15:00] and it's a big difference between wet and dry [20:15:04] which we don't simulate [20:15:08] which we don't take into account yeah [20:15:27] maybe with the partial pressure of water or so it could be taken into account [20:15:29] I mean its possible to come up with something based on H2O in the air of course [20:15:34] haha [20:15:56] I will add it to my to do list but for now nothing is broken it seems :P [20:16:29] engine sounds were fine for the LM [20:16:35] yeah. At most that RPM code for telemetry needs a comment that that is our best guess [20:16:38] for how it works [20:16:46] Agreed [20:16:59] yeah the sound is only slightly different to the main engine sound [20:17:06] SPS sounded fine, didnt try the saturn though [20:17:28] you can quickly try the Apollo 11 T-30s scenario [20:17:36] which is loading as we speak [20:17:38] there is a bunch more sounds going on there [20:17:45] so it might "feel" different haha [20:18:55] having downloaded the code of old NASSP versions already paid off [20:18:58] https://www.orbiter-forum.com/threads/nassp-7-crew-egress-on-splashdown.39787/ [20:19:13] the boat with the crew in it, I found how that used to be activated [20:19:15] button R [20:19:27] but that's used by Orbiter [20:19:32] maybe it didn't back then [20:19:41] so I think I'll use ALT + R [20:19:47] all that needs to be set is a bool [20:19:53] the code for this still works [20:20:23] and conditions, hatch open and the landed CM stage [20:21:53] Haha cool! [20:22:05] Launch sounds just fine, no concerns here [20:22:28] but you hear that it's different [20:22:35] I do [20:22:46] my old headphones broke, so I wasn't even 100% sure :D [20:22:48] I was testing keys and forgot the - = keys move the THC :P [20:23:11] ah good key [20:24:15] if you want abort hard mode use CM/SM sep switch [20:24:23] that also causes a Mode I abort [20:24:34] but non of the automatic events afterwards are working [20:24:40] so you have to do it all manually [20:24:53] tower jettison, apex cover etc. [20:25:09] at least that's what I remember haha [20:26:47] I dont know my abort modes well enough [20:26:58] I ended up popping the CSM off just after tower jettison [20:27:12] popped the SM off and started P61 lol [20:27:18] any CG shifting problems? [20:27:24] I didnt see anything in 2d [20:27:33] starting P61, that's ambitious [20:27:55] that's a lot of lift up, the target is at the eastern end of the Atlantic [20:28:20] haha hit 11.5 gs [20:28:52] yeah, the minutes after first staging have the steepest reentry and highest Gs [20:29:01] Apollo 7 has a higher insertion altitude [20:29:11] Mode II aborts can go up to 16 Gs [20:29:18] PAMFD showing me at 30.57 and -72.17 [20:30:26] target is at 17°W [20:31:12] missed it by that much :P [20:31:28] nah, you hit exactly the target for Mode II [20:31:30] which is water [20:31:38] Haha [20:31:49] But yeah sounds are fine to me [20:32:09] the east Atlantic splashdown zone is mainly padloaded in the CMC so that it can calculate miss distance for a Mode III abort [20:32:48] good to hear. I think the PR doesn't need anything else then. [20:33:03] I think I want to test a LM staging tomorrow just to be sure [20:33:14] Yeah thats what I did first [20:33:27] oh you did a LM staging [20:33:33] I'm back [20:33:34] Yeah PDI and an abort [20:33:36] then abort stage [20:33:37] there was some code I removed related to the engines that I am 99.9% sure doesn't break anything but seemed redundant [20:33:39] They fixed the problem: https://twitter.com/liberachat/status/1443620787408224267 [20:33:54] let's put that to a test [20:34:04] Well I think I already tested it :P [20:34:26] they fixed the problem [20:34:30] yes lol [20:34:46] For the LM staging was there anything particular you were concerned with? [20:35:01] the old code set the hover engine thrust to 0 [20:35:11] but I don't really think that did anything [20:35:21] the thrusters were just all deleted and created from scratch [20:35:24] Well I did a PDI, then a DPS abort [20:35:29] of course it has 0 thrust level [20:35:33] then used abort stage [20:35:43] got me into a safe orbit [20:36:08] maybe Orbiter 2002 didn't initialize the thruster levels to 0 when they were created [20:36:15] you never know, that code sticks around in NASSP [20:36:40] and in the Saturn class the main thruster group got directly deleted [20:36:45] I also removed that [20:37:08] because all our functions creating a stage do [20:37:09] ClearThrusterDefinitions [20:37:21] so that already deletes all thrusters and thruster groups [20:43:20] then I'll just go ahead and merge it, if it's all been tested. Unless you want to have a look (or rather listen), Thymo? [20:43:51] Yeah I saw no ill effects in DPS APS SPS or saturn [20:44:03] I sure want to listen to it but I don't think it will change my opinion of merging it. Go ahead. [20:44:48] ok [20:47:22] done [20:49:49] even the RTCC still wanted to access the main thruster groups in some very old code [20:50:54] but only in mostly obsolete code [20:58:08] Well I guess my orbit timing wise is on part with the mission [20:58:29] SS in the LM activation checklist on this rev is 109:13 [20:58:39] SS in RTCC Map Update is 109:06:!3 [20:58:40] 13 [20:58:49] *109:13:06 [20:59:15] yeah, the clock update did good things [20:59:32] and the wrong lunar gravity isn't a big difference in the downrange direction [20:59:57] doesn't really change your semi-major axis over time [21:02:51] night! [13:56:55] hey [13:59:57] morning [14:00:36] Oh another report on that orbit, flight plan sep time and attitude 100% matched the actual to the second [14:01:30] P30 using sep pad gave me the same angles, and hit 90 on the ORDEAL on the second [14:03:41] great [15:01:40] Hmm I know it's trivial, but was a DOI-2 target load uplinked for 17? Or did they enter the pad data? [15:02:01] I cannot seem to find a target load uplink [15:16:45] hey [15:22:15] morning [15:27:32] hey alex. [15:42:33] rcflyinghokie, there might not be an uplink [15:43:26] timeline book has "P30 Load PAD" [15:45:07] Yeah thats what I saw [15:45:13] Just a sanity check [15:52:51] indy91, no more accidental engine thrusting anymore I see :D [15:52:58] yep [16:20:23] okay, I've got a dumb question, which I really should know the answer to: why, before starting PTC, do I go to P,Y 090, 000 rather then 000,000? [16:22:24] yes [16:22:27] pitch 90 or 270 [16:22:43] if you have a PTC REFSMMAT [16:28:51] maybe I'll uplink it again and realign. the antenna reacq angles seem to work though [16:38:44] I think for Apollo 10 and 11 it's not exactly 90° from the sun at 90° pitch [16:39:00] different kind of PTC REFSMMAT [16:39:13] which we can't actually calculate with the RTCC MFD [16:39:25] the MFD has the method to calculate the Apollo 12-17 PTC REFSMMAT [17:00:57] looks like VC clickspots are working well through all the states of the CM to post-splashdown [17:06:06] yeah that was a simple fix [17:06:31] there was only one ShiftCenterOfMass, which is when the apex cover is jettisoned [17:06:34] that broke it [17:25:38] now just the Saturn staging left to do... is it just a question of changing the ShiftCentreOfMass to ShiftCG? [17:28:12] I guess right now we already redefine things like the thruster positions at staging [17:28:25] but with ShiftCG that takes care of it too [17:33:07] it could be easy, not sure yet [17:33:35] after that all works right we could even remove the deleting/creating from scratch of many things like thrusters [11:17:02] good morning [11:20:07] hey [11:30:30] I see we have our boat back :) [11:31:59] yep [11:32:11] we always had the boat, just no way to get to it [12:05:10] I think Ryan and I are both having good luck with my systems update so far, so that's good. [12:11:41] great [12:20:50] I have an annoying HGA bug to track down... [12:22:25] yeah I am transitioning the RTCC to a different ephemeris format, the update I pushed earlier has an MPT bug during TLC [12:22:59] luckily not relevant for the MCC or so [12:23:11] but need to push a fixed version later [13:05:38] for some reason reacq mode only works if you've hit the scan limit for the first time. this is one of those things that should be obvious from the code...but it isn't [13:14:55] hmm, weird [13:18:37] RcvBeamWidthSelect and XmtBeamWidthSelect are initialized as 0, which means "none" [13:19:49] could it be related to that? [13:27:51] oh, that could be. [13:51:31] this is probably a good opportunity to make the tracking controler less stiff, and convert the automatic gain control signal strength to volts. [14:48:38] hey [14:58:30] hey Alex [16:37:48] ah annoying work converting everything to a new ephemeris format in the RTCC. Little gain, lots of potential for bugs [16:38:29] but has to be done [16:39:30] and had to implement a bunch of intermediate code [16:39:46] but I think I am at the point where I can delete old stuff [18:41:17] I should probably just make myself an "oops I committed changes to Orbiter2016 rather than a new branch", script at some point. [19:04:41] I tend to not commit anything and then when I get to the point where I need to I am deciding if I switch to a branch or not [20:01:56] n7275: You can set up a branch protection rule on github if you want. [20:02:49] oh that sounds like the thing for me :) [20:02:50] I did that in the main repo but that made Nik unhappy :p [20:03:03] haha [20:09:57] :) [20:48:34] night!