[18:19:49] NASSP Logging has been started by thewonderidiot [18:20:10] rpmcmd starts at zero in this so the first timestep would be a divide by zero [18:20:50] but rpmcmd is set to "rpmcmd = flow * 4235.29;" before being used [18:21:20] and flow is zero on the first timestep [18:21:40] hmm [18:21:52] why? [18:21:56] No idea [18:22:04] That was already there [18:22:05] must be fanned.GetMass() returning 0 [18:22:15] Oh yeah [18:22:22] why? [18:22:24] :D [18:22:28] Well the flow when i start up this LM is zero [18:22:46] At least I think it is [18:23:17] This is a scn with no LM ecs until the scn starts, my ecs testing scn [18:23:32] But I would think that nan at first could be dangerous [18:23:45] I'll be back in a few [18:27:13] yes, a check on 0 flow has to be done [18:27:50] ok, I think I finally have the HGA geometry with 3 axis down [18:28:45] the two remaining tricky things are resolving the manual inputs into the A and C axis and resolving the A/B/C axis into the two angle display on the panel [18:35:04] but these new documents should tell me everything I need for auto tracking [18:54:28] Excellent [18:54:44] Now we need to get a moving mesh :P [18:55:14] yeah, that would be great [18:55:21] at least I have the geometry figured out [18:55:28] would be the same for the antenna movement [18:55:59] there are simulations of the RMS in Orbiter, so this can't be any more difficult than that [18:56:53] or I should call it Canadarm, before Alex complains :D [18:57:43] Haha [18:58:06] Yeah I have to be careful about that being an American and all :P [18:58:49] I put a check on flow in the code lets see if this works [18:59:36] Hmm actually, that might be too hacky where it is, I dont want zero flow to automatically stop everything, I want the RPM to still spin down [19:00:47] set h2oremovalratio to 0 if rpmcmd is 0? [19:01:25] or better [19:01:39] just skip the whole section after RPM += drpm; [19:02:13] Ah yeah if theres no flow, no more water should be added to remove in the sep [19:03:54] Would this work [19:03:54] if ((h2oremovalratio) > 1) [19:03:55] h2oremovalratio = 1; [19:03:55] if (rpmcmd == 0) [19:03:56] h2oremovalratio = 0; [19:04:31] No [19:04:44] ah yes the canadarm. Part of the lunar module feet were built in Canada, too. [19:05:08] Actually yeah that can work [19:05:32] AlexB_89, oh, I didn't know that [19:05:37] Nor did I [19:05:54] http://www.cbc.ca/news/technology/canada-and-the-moon-past-and-future-missions-1.810344 [19:07:15] https://en.wikipedia.org/wiki/H%C3%A9roux-Devtek [19:12:36] I guess we can copy some of the RMS code for the animation of the HGA [19:14:07] basically, yeah [19:24:45] indy91, what do you think of this? [19:24:46] https://github.com/rcflyinghokie/NASSP/commit/91c6151db16caa63a09991457a3c46ce721f79d2 [19:25:54] I think I can remove the if flow !=0 [19:26:01] hmm [19:26:06] if ((h2oremovalratio) > 1 || rpmcmd == 0) [19:26:07] h2oremovalratio = 1; [19:26:17] wouldn't this remove all of the water at 0 flow? [19:26:23] not that there would be any water... [19:26:42] yes technically [19:27:10] maybe a condition if the RPM is 0, that can be made zero [19:27:23] I would just skip the water removal section [19:27:39] If RPM is zero you mean [19:27:42] yes [19:27:44] so from [19:27:44] Sure [19:27:45] "// separate water" [19:27:50] to [19:27:51] "H20waste->Flow(h2o_volume);" [19:29:06] hmm [19:29:36] like an if RPM>0 for that? [19:30:15] I think that would work, otherwise the water content is unchanged [19:30:15] if wouldn't do a check on rpmcmd [19:30:22] better a check on flow directly [19:30:43] rpmcmd is only 0 if flow is 0 [19:30:47] right [19:31:07] and if the flow is zero all that needs to be done is spin down the RPM [19:31:22] And still remove water until it is zero [19:31:34] there will be no water without flow [19:31:44] fanned will have 0 mass of anything [19:31:48] Thats right this is not a tank [19:32:17] rpmcmd = flow * 4235.29 should be safe for flow = 0 [19:32:23] right [19:32:27] just "h2oremovalratio = (RPM / rpmcmd);" not [19:32:58] do above that line [19:33:04] add if (flow != 0) [19:33:32] and the parentheses go down to below [19:33:33] "fanned.composition[SUBSTANCE_H2O].Q = 0;" [19:34:02] do i keep the check on rpmcmd? [19:34:23] or is it unnecessary now [19:35:45] better check on flow [19:36:13] but only in that one place [19:36:17] for the if [19:38:08] https://github.com/rcflyinghokie/NASSP/commit/9798df5abf2b82757cf76107ee2369c849354dd3 [19:42:27] if ((h2oremovalratio) > 1 || rpmcmd == 0) [19:42:33] doesn't need the check on rpmcmd [19:46:34] Thats why i asked :P [19:47:03] Guess I didn't see an affirmative or negative answer [19:47:27] Other than that anything unsafe? [19:52:19] "but only in that one place" [19:52:30] that's what I meant with it [19:53:00] just one check on flow or rpmcmd, and only for the big if parenthesis [19:53:18] looks ok otherwise [19:54:22] Ah I see [19:54:26] And it works properly [19:54:34] Sorry for the complexity! [19:56:11] this is certainly simpler than your first approach with a separate class for this [19:56:25] Haha doesn't feel like it [19:56:37] But it did give me more practice with classes [19:56:58] PR inbound [19:57:55] Back in a few [20:00:39] did you test this with an unpressurized LM? [20:03:11] seems like a great potential NaN cause [21:21:13] I guess we're quite experienced at squashing NaN's now [21:22:32] I found an ancient installation of NASSP on my hold external HD, dating back to 2009 and Orbiter 2006, haha [21:22:43] and it runs [21:25:47] awesome [21:27:50] ok, I can now convert the manual HGA pitch and yaw angles into the ABC axis coordinate system and back [21:29:37] that was the biggest issue with the HGA geometrical considerations [21:30:43] the middle axis, or B-axis, is only used by auto tracking [21:30:57] to avoid high angular rates for the HGA at zenit [22:08:16] Well that took way longer than I thought [22:09:04] And yes my test case was an unpressurized LM thats where I saw the nan to begin with and got worried [22:09:28] a few iterations back [22:09:43] the NaNs don't happen in your PR version anymore, right? [22:10:18] Nope [22:10:25] alright [22:10:32] I ran it a few times as well [22:10:34] merged [22:10:36] No nans [22:11:31] Starts at 1 or a decimal value [22:11:39] And fluctuates with little to no flow [22:11:55] But no nan [22:12:56] Just tried again to be sure [22:15:53] hmm the glycol and H2O SEP lights are on when entering a freshly initialized LM [22:16:07] without having touched any of the switches yet [22:16:48] Hmm [22:17:01] They get power through the comp lighting breaker on panel 11 [22:17:32] I need to see if that is just for the lamp test [22:19:35] the cb is already closed when the LM is initialized, were those lights supposed to be on during launch? [22:20:22] maybe an issue with the light logic [22:20:54] Well its working properly based on the logic, but now I dont know if that is correct haha [22:21:07] Power to the bulbs comes from that breaker [22:21:29] But I wonder if they only turn on if the signal conditioners are on [22:21:38] logic looks right [22:21:51] for the glycol it is certainly the pressure switch [22:21:56] not the SCERA reading [22:22:13] Yep I see that [22:22:24] and 2-5VDC lighting is what powers the bulb [22:22:30] Which comes from that breaker [22:22:54] ah [22:23:01] ANNUN/NUM knob [22:23:06] ANUN* [22:23:17] that is turned to dim certainly [22:23:30] Which would have those off [22:23:30] and all lights getting power from the component lights are turned off that way [22:23:44] More reason for a lighting control module :P [22:23:46] that's why we need the lighting control assembly, haha [22:24:21] haha [22:24:26] I could add temprary logic for them [22:24:38] Similar to the dsky dimming in the CSM [22:24:42] I don't like temporary [22:24:46] Nor do I [22:24:56] it's probably not so easy coding wise [22:24:58] If you guys are ok with dealing with this as is for now [22:25:08] We can wait to have a control [22:25:18] yeah, no hurry. The lights aren't drawing power yet, right? [22:25:21] Nope [22:25:26] Also waiting for the LCA [22:25:29] so having them on doesn't hurt [22:26:53] I'll probably set it up similar to a DC Bus [22:27:10] the lights register their power draw in the LCA [22:27:19] and based on the switch settings (dim bright it draws power) [22:27:30] Would be cool to have the EL displays work [22:27:33] for the often used type of light we can also use different lightin levels [22:27:45] just need bitmaps for it I guess [22:27:51] simple white or blue could work [22:28:11] But that is of course purely cosmetic [22:28:38] I'd rather have lit start stop buttons first anyways [22:28:46] They come on during lamp testing [22:29:34] pushed my latest MCC work and the addition of the frequency parameter for AC buses [22:30:14] am I reading correctly though that the op err on the DEDA gets power through the lamp tone test ground? [22:30:23] on the lighting schematic [22:30:30] handbook pdf 48 [22:31:29] seems like it [22:31:33] so it would be on during a test? [22:34:06] anyway, good night! [22:35:13] Yeah I need to read that further [22:35:27] But other than the dimming the lights should work [22:35:45] The bat/dc bus lights do not have any logic other than lamp test though [22:35:52] As we dont simulate those parameters yet [22:36:27] right [22:52:51] And now the water separators have RPM based on flow but take time to make the comp light turn on [22:54:46] nice [22:58:32] night! [23:22:04] heyo [23:33:09] I'm doing my IMU realign with REFSMMAT and on F50 25 my R1 is reading 00013 instead of 00015 like it's supposed to [23:33:38] and when I go through with the rest of the checklist it gives me a PGNS program alarm [23:38:16] hey Uncooked [23:38:32] you missed Alex and Ryan by like ten minutes :/ [23:43:43] rip [23:49:15] what's the program alarm? [23:50:55] I didn't write it down [23:51:08] I followed a procedure in the GNC checklist for 00013 [23:51:21] I'm now at 052 01 70 [23:51:24] *p52 [23:52:44] but hitting pro gets me to V06 88 [23:52:57] and not 06 92 [23:53:07] R1 was 00000 at 01 70 [23:53:13] which star code was I supposed to enter? [00:12:25] I'm not going to be helpful, sorry :( [00:12:30] Uncooked: ^ [00:13:28] oh I manage to duplicate the program alarm again though @thewonderidiot [00:13:35] 05 09 [00:13:38] 00405 [00:13:47] and this is on Comanche 055? [00:13:59] this is on a p52 realign of the IMU [00:14:05] it's giving me a PGNS light [00:14:42] two stars not available [00:14:47] well that's a pickle [00:14:50] haha [00:15:23] I'm surprised because the IRL apollo mission plan calls for exactly this procedure at exactly this time [00:15:28] I'm not sure why that would happen, but that's what 405 means [00:16:14] it's strange [00:16:21] I first got this alarm at 05:32:00 [00:16:31] and the flight plan calls for a realign at 05:30:00 [00:19:05] really needs to learn more about the mission software [00:19:10] lol [00:20:10] flightplan calls for this IMU realign, then cislunar navigation which I assume needs a flightplan, and then a 4 hour period of doing nothing [00:20:36] *IMU realign not flightplan for cislunar navigation [00:25:42] hmm I'll try rotating the spacecraft [00:25:50] I have no idea if the computer works that way [00:27:25] huh ok it does work that way [00:33:02] haha [00:36:10] well now that's done I'm gonna go do something and then I get to figure out "cislunar navigation"