[18:10:51] NASSP Logging has been started by thewonderidiot [18:10:53] morning! [18:10:58] Guenter! [19:26:15] hey Mike [19:26:27] busy debugging things, so I hadn't looked here yet :D [19:31:30] hahaha [20:55:52] What up [20:58:27] hey [20:58:34] coming out of standby mode is still broken [20:58:53] despite your fix for it in November. It's not a pending interrupt, there are none [20:59:03] so it must be some other issue [21:00:49] Hmm [21:01:27] .at 13-08 Look at standby bug. Improper resume behavior. [21:01:35] .on 13-08 Look at standby bug. Improper resume behavior. [21:02:18] .on 12-07 test [21:02:23] Guenter! [21:02:31] .help [21:03:07] .in 5 weeks investigate standby resume bug [21:03:11] There we go [21:03:33] I leave for the US this satuday so I don't expect to be able to look into it for a while. [21:04:04] But maybe Mike and I can discuss it when we meet up this sunday :P [21:06:27] lol we certainly could, although I think it might be a silly thing to travel all the way to the US to do :P [21:08:48] I might be able to look into it sooner....... but also I don't want to commit to anything until I get this rope reader board sent out for fab [21:09:06] I want to get this thing done ASAP [21:10:29] Well it's a bit further obviously but flying down to the Cape from MIT for meetings or issues was not uncommon during the program. [21:10:46] But in todays context it would be silly indeed [21:19:56] we went on holiday just to meet a family of friends of ours there [21:20:01] three times [21:20:04] but actually, it was by chance [21:20:18] and 3 different places many hours from home [21:20:32] could have met them at home :D [21:20:39] but what are the chances of that happening haha [21:23:00] night! [22:27:52] Damn. Someone just opened an issue on AndroidAGC. I'm honestly a bit surprised someone managed to build it and is actually using it. [22:28:16] I don't even have it set up to the point where I can built it right now lol [22:28:41] Heh. And his issue is not even a bug. [22:28:56] "I get OPR ERR when I press 8 or 9 what gives" :P [23:29:56] lol 8 and 9 aren't real numbers [16:24:13] hello [16:28:24] quite the bug we have on the forum [16:57:39] yeah it's very strange [17:13:59] morning! [17:24:27] hey [18:03:51] I am very anxiously awaiting this AMS manual haha [18:11:05] I am cautiously optimistic awaiting the AMS manual [18:15:19] hahahaha [20:42:00] Evening [20:42:31] yo [20:43:23] What's up? [20:44:01] 63 more nets to route out of ~1300 on the rope reader board [20:44:04] getting very close [20:45:37] I've been starting to think about disassemblers again [20:45:52] if I want to write a custom one for the AGC, or try to add it as a target for Ghidra or something [20:46:54] ....and also I need to clean my apartment so it's not a disaster when you visit :P [20:49:00] Hehehe my stuff is also more often than not in a state of "organised chaos". Don't worry about it too much. [15:54:55] hey Nik [15:56:13] hey hey [16:03:11] morning! [16:03:36] AMS manual is allegedly supposed to be delivered in the next 2-3 hours [16:13:28] hey, sounds great [16:14:05] what sounds not so great is, I have somehow deleted my file of notes of listening to the Apollo 11 FIDO [16:14:28] lots of good stuff in there. Buuuut, I should have a backup on my laptop. [16:14:40] oh noooo [16:14:49] hopefully your backup is good [16:16:14] I took the file with me on the road together with 10s of hours of more MOCR audio, in case I had too much time [16:16:34] so might be slightly outdated, but I haven't added many notes in the last year [16:17:07] I should maybe enable the Windows Explorer to ask me for confirmation when I delete a file :D [16:19:54] uh oh [16:19:58] only Apollo 13 FIDO on there [16:21:41] eeeeeee [16:21:55] you might be able to recover most of it. there's some good "undelete" tools out there [16:37:59] it's probably been deleted for too long [16:39:50] oh no [17:05:02] time to re-listen to the whole thing? [17:07:58] well good thing that I had never listened to the whole thing yet in the first place :D [18:54:58] facepalms [18:55:04] So the car rental company has confused dutch with deutsch... Doing the online check-in in German wasn't a big deal but understanding the German legalese in their booking conditions is another level. [19:04:12] if it said Waschmaschine anywhere in the conditions then you now own a new device [19:04:35] lol [19:04:40] also oh man oh man the AMS manual is here [19:05:01] and holy crap this thing is extremely technically dense [19:05:16] no table of contents, no exposition, zero paragraphs [19:05:22] every single page is just a schematic [19:05:45] I see, same author as the IBM RTCC documents [19:05:57] and very interestingly, it appears to reproduce spacecraft schematics where actual spacecraft hardware was used [19:06:08] case in point, there are DSKY schematics copied straight from MIT in here [19:06:13] yeah, that is what I imagined [19:06:20] so zero things about the RCS :D [19:06:27] unfortunately yes [19:06:30] in this one [19:06:39] but I now have this guy's contact info so I'm going to see if I can get the rest of them [19:07:08] are they more AMS technical manuals or any chance of software of program flows of the software [19:07:17] or program* [19:07:35] I was hoping this one would have a table of contents that would have an answer to that [19:07:52] the table of contents is its own volume :D [19:07:57] all I know is that this is part of section 8, and I don't know what the other sections are haha [19:08:18] I do have a whole bunch of ECS pages [19:08:27] that might be helpful for CM ECS simulation, maybe [19:08:33] yeah probably [19:09:06] could be quite good if it has schematics that go beyond the ones we have [19:09:15] for some subsytems [19:16:48] hopefully! [19:17:13] well I have my work cut out for me. this thing probably has a couple hundred foldouts [19:17:21] the new scanner is going to pay for itself multiple times over on this one [19:18:33] does it come with a minimum wage worker doing it for you [19:18:55] no unfortunately not [19:19:17] although I would be thrilled to be said worker if any of y'all wanted to pay me minimum wage for buying and scanning this stuff :P [19:19:29] (kidding) [19:20:42] only half kidding, I appreciate it a lot when I mention a document is interesting and suddenly you own it. I haven't given back enough when you have done that. [19:21:43] somehow all this stuff is owned by people in the US instead of Germany :D [19:22:10] :D [19:23:10] remember when you wanted to buy East German core memory, that's where I could have been useful lol [19:23:27] happy to do my part, and the combo of getting to keep a document and have it be actually useful is good enough :D [19:23:41] oh I do have a bunch of East German cores haha [19:23:59] but yes I will definitely keep that in mind if I ever make it back to the AGC replica project [19:24:12] might even be able to resell some of those documents [19:24:20] ....although to be completely honest that has sort of fallen off my project roadmap at this point [19:24:23] oh yeah for sure [19:24:29] I'm always happy with a PDF. just have not press delete it seems. [19:24:38] have to* [19:24:54] lol [19:25:05] you have reminded me that I really really really need to back up stuff on my laptop [19:25:20] there's a bunch of stuff from the restoration that only exists there, still, years later [19:25:37] 9 out of 10 times I check the trash bin before I permanently delete the stuff in there [19:25:59] really got unlucky with the FIDO audio notes [19:26:58] yeah do a backup. For that process I have already taken up all the bad luck on this planet for a few decades. [19:27:08] lol [19:27:13] A few years ago my laptop hard drive was dying [19:27:19] oh yeah that is the ultimate danger [19:27:25] so I used an external hard drive to move stuff over [19:27:30] and somehow in that process, both of them died [19:27:47] I lost some stuff, luckily not everything [19:28:01] ooooof [19:28:47] I unplugged the external drive from the laptop [19:28:53] and that was the last time it ever worked :D [19:29:03] wow that super sucks [19:29:07] made a strange noise once afterwards [19:29:33] I should maybe also back up all my PDFs somewhere. [19:29:52] But nothing super unique is in there. At worst UHCL needs to scan something again [19:30:16] everything from NARA is twice backed up on the Internet [19:30:27] ibiblio and archiv.org [19:30:30] archive* [19:31:15] I also need to make contingency backups of ibiblio and archive.org [19:31:24] too many things to do [19:31:51] also hah -- pages 8-606 and 8-607, "Smoke Generator" [19:32:02] gotta have those realistic effects :D [19:32:08] ah yeah, I read about that in the instructor handbook I think [19:32:42] Turry needs that for Apollo 9, controlled by the livestream chat [19:37:53] hehehe [19:45:07] there is also launch and thruster noises [20:45:53] night! [13:02:43] hallo [13:06:26] hey [13:08:15] I finally started on Apollo 12 last night [13:08:51] nice! [15:24:31] as a result of my new job, I'm now becoming a bit of an expert at removing potting material from electronics [15:42:34] that might get you hired for the next AGC restoration, if there should be one :D [15:55:54] morning! [15:56:01] yes that sounds very interesting :D [16:21:07] I think I'd still be very nervous to touch an AGC [16:22:00] have you had to deal with the rigid polyurethane foam that MIT liked to use? [16:24:34] this stuff is about Shore D40 [16:26:32] and it's solid, not foam [16:27:40] it's like digging through a tire [17:07:36] indy91, is there a list of characters/symbols used by the D/TV displays in any document that you know of? [17:13:41] ahh PHO-TR515 has it [17:18:27] I know it can show greek letters [17:18:53] one of the differences to the RTACF [17:20:16] hmm [17:20:22] now that I think about it [17:20:36] most of these letters would be part of the background slide [17:20:58] maybe the RTACF displays don't use background slides at all and what's why it can't show them? [17:21:15] in some cases that's the only difference between a RTCC and a RTACF display [17:21:19] greek letters [17:21:39] but in any case the RTCC could dynamically display greek letters, too [17:23:47] so I talked to the guy who sold me the AMS manual last night -- it's not a done deal yet but it sounds like I will be able to get the other four volumes of it from him [17:24:19] he says the first volume has a lot of details on the mechanical instruction, the second volume has pictures of all of the circuit boards and talks about those, and then the other two are more schematic-filled ones [17:24:41] and they are all maintenance manuals? [17:24:52] as far as I know this is all the same manual [17:24:57] right [17:24:58] he's sending me pictures sometime today [17:26:55] well it's great manuals if someone wants to rebuild the AMS :D [17:27:30] for me, I can't say I can use anything from it much. The software part would be a lot more helpful with certain things. [17:28:11] Struggling with some of the same issues as NASSP, how they could simulate some systems at 25 frames per second if the timing really needed to be much smaller to simulate it "properly" [17:33:47] analogue "computers"? [17:35:01] that's the thing [17:35:03] not analog [17:35:44] they often used hybrid computers at the time to be able to simulate things with fine timing like RCS [17:36:07] I'm not sure about the MIT digital simulator, that couldn't be run in real-time I think? [17:36:31] but I am pretty sure the AMS is all digital if you don't count the AGC emulator [17:36:44] I found one memo online with the struggles that are caused by that [17:38:07] http://www.ctandi.org/empty-blog/2017/10/14/effect-of-lms-fifty-millisecond-integration-steps-on-simulated-response-of-abort-attitude-control-system-lem-engineering-memorandum [17:40:33] ok even further disclaimer. The AMS uses a lot of actual hardware where possible, hence the large volumes of maintenance manuals :D [17:40:44] but no analog computers I believe [17:44:27] gotcha gotcha [17:44:42] well the actual hardware information is quite useful still haha [17:44:59] indeed [17:45:48] we could use some drawings of what I would call "sub-subcontractor black boxes" [17:46:15] where the Systems Handbook etc. just have a empty box because they didn't get detailed drawings?! [17:46:18] like HGA electronics [17:48:42] yeah for sure [17:49:54] I kind of doubt the AMS had a real HGA electronics box though [17:49:59] wouldn't be much use [17:50:24] without also having a real HGA :D [18:15:00] hehehe [18:15:14] yeah, and despite all of the comms stuff in our lab we don't have a real HGA/electronics box either [21:44:56] night! [12:20:43] good morning [14:16:26] hey Matt [17:11:58] morning! [18:12:42] hey Mike [18:13:09] remind me, what did you want the AMS manuals for mainly? CDU schematics? [18:16:53] general knowledge haha [18:17:53] it's the smoke generator, admit it [18:18:10] alright you got me [18:22:05] it is hard to top restoring an AGC, but restoring a smoke generator might just do it [18:26:47] luckily the AGC was never a smoke generator [18:30:55] this LM PSA we have sure was though [21:12:05] night! [12:05:52] hey Niklas [12:21:07] was looking through HSI-209462 a bit this morning, specifically at all the JCL code. there are a bunch of clues to filenames (DSNAME= ...), and the delog program looks very sophisticated. [12:21:12] cool stuff [12:33:59] yeah definitely. I also really like the list of programs and tables, helps when I want to name stuff in our RTCC [12:44:35] I've been thinking about the best way to store things like telemetry and plotboard data. might be something we need to wait for 64 bit Orbiter. I think some compact binary file to which the scenerio has a path [12:52:20] what does 64bit Orbiter have that 32bit doesn't? [12:52:54] the ability to address more than 4GB of memory [12:53:14] would we really generate that much data? [12:58:11] hmm, my LM telemetry client does something strange [12:58:26] it only processes LGC data when I open it with the VS debugger [12:58:37] opening the debug or release exe files directly doesn't work [12:58:42] the other telemetry data are fine [12:58:52] does that sound like something uninitialized? [13:00:01] oh haha. I thought LGC telemetry wasn't implemented yet [13:00:42] not sure I pushed my latest version from a few months ago [13:00:49] could be uninitialized. and debug mode somehow initializes something to 0 [13:00:50] actually, it could be a really dumb bug [13:01:06] I have files with the LGC downlink format [13:01:13] it could be a path problem [13:01:18] that it doesn't find those [13:01:31] probably looking in the same folder as the exe normally [13:01:37] but not with the debugger maybe [13:02:40] lol, yeah that is it [13:08:07] re: your question about memory. I think at most (physical limitations of the 2314 DASF, 2x DSEs, plus plotboards, would be around 400MB. but Orbiter already uses 2.9GB and if we do any report/stripchart/tape generation that could eat up the rest fairly quick [13:08:50] hmm right [13:09:02] we need to write data to tape :D [13:10:30] so how do I solve the folder path problem... [13:12:37] is it an issue of the working directory changing between debug/release [13:13:33] i had that issue when I was testing my console-based Pines Gravity tester program [13:14:23] the VS debugger would make the CWD the directory of the debugger rather than the directory of the exe [13:14:42] you could print the directory to a text box [13:15:17] yeah it's VS debugger where it worked, debug/release not [13:16:13] but I have an idea what could work [13:23:10] hmm, now it's causing CTDs [13:27:09] and now not :D [13:27:14] didn't really change anything [13:27:21] the exe file is in a Release folder [13:27:38] next to the Release folder is a LMTelemetryClient2 folder with the downlink formats [13:27:39] sprintf_s(listname, "../LMTelemetryClient2/LGCDownlinkFormat%d.txt", list + 1); [13:27:39] myfile.open(listname); [13:27:41] this works [13:27:54] I think I'll push a version of it for testing [13:30:22] https://github.com/indy91/LMTelemetryClient2/tree/main/Release [13:30:40] test with Apollo 11 [13:30:58] coast/align and maneuver downlink formats are implemented [13:31:01] so P00, P40 etc. [13:32:19] LGC and uplink pages are working [13:32:26] and you can already uplink DSKY inputs [13:44:12] are CMC downlink/uplink formats the same for all software versions or do they change too? [13:46:15] they change [13:46:25] not a lot, but enough haha [02:08:10] .tell indy91 I tested out your updated telemetry client and it works. [15:56:06] hey [15:58:24] hey Matt [15:58:53] great. It's a bit buggy still, occasionally the LGC telemetry somehow causes a CTD [15:59:10] at least in Sundance [15:59:18] could depend on the active downlink list [16:21:00] morning! [16:21:24] that doesn't surprise me too much, sundance's lists are a bit weird [16:22:36] the CTD would probably come from some wrong formatting [16:23:01] the telemetry client does scaling and such, maybe it overflows the text box or so :D [16:25:22] now I remember why I didn't continue with the other downlink formats. It's a lot of new erasables that aren't in the other lists. I kind of ran out of space to display them all on one page. [16:50:21] I need about 5 more screens so I can have all the telemetry client windows open at once [20:57:49] night! [15:15:30] hey [16:31:40] morning! [16:32:44] what's up? [16:33:34] not a whole lot [16:33:55] still have 57 traces to route on the rope reader board, but I made some progress (I think?) on sorting those out last night [16:34:06] started routing both ends and just need to figure out how they all meet in the middle lol [16:35:06] sounds like some work that you can divide in many pieces and do whenever [16:35:54] which can be good for motivation to even start working on it in the evening :D [16:36:56] hahaha [16:37:09] well the tough thing is, I'm getting very constrained in where I can place my vias [16:37:31] so I think these 57 traces are either all going to come together at once, or won't and I have to start over with them [16:37:37] so it's been a bit of a tough problem to start cracking [16:38:00] not like I can open it up and route 10 and commit the work, because they might have to be ripped up if they end up blocking the others :) [16:38:30] ah so, nearly the opposite of what I concluded from your earlier words haha [16:38:36] lol pretty much [16:39:12] I'm looking at Sundance compatible RTCC calculations. [16:39:24] stupid outdated rendezvous programs [16:39:45] it's a bit of a new problem caused by something entirely unrelated, the CSM having a shifting center of gravity [16:40:11] the SPS-5 maneuver, happening the day before rendezvous, was supposed to circularize the orbit [16:40:15] oh that's a weird cause [16:40:27] but there were large residuals due a slow reacting DAP [16:40:48] happened on the actual mission and now also in NASSP. [16:41:06] So Turry has a not super circular orbit for rendezvous, like the actual mission [16:41:41] And that's where Sundance and the RTCC now diverge a bit, more than before [16:42:15] To the point that the ground calculated CDH maneuver would be quite bad to use, because its time of ignition is quite off [16:43:09] it seems like they actually had a AGC compatible mode in the RTCC for this [16:43:30] when it comes to calculating the CDH TIG from the post CSI orbit [16:43:57] one option to place CDH at the next apsis, but basically using an integrated trajectory [16:44:17] but then this: "Number of apsis since CSI (Keplerian)" [16:45:16] I guess what you could do with that mode is: use AGC state vectors for RTCC rendezvous calculations. Use same inputs as the AGC. And as a result you can replicate the same CDH time that the AGC would calculate. [16:45:41] might be something they had added specifically for Apollo 9 [16:49:30] hmmmmm weird [16:49:33] the AGC is not iterating on integrated trajectories for rendezvous [16:49:51] it does do that in P37 for the onboard return to Earth [16:50:04] but the result is that calculation can take foreeeever [16:57:41] need Block 3 AGC with hardware interpreter acceleration :D [16:59:17] oh was that a proposed feature or did you just make that up? :D [16:59:47] it sounds useful in any case haha [17:06:29] that's what Hugh Blair-Smith wanted to do with Block 3 [17:06:50] so it wasn't ever official, but it's as close to official as you can get while being unofficial lol [17:10:58] Mike, sounds like you and James need to write a block 3 emulator :) [17:11:15] can you emulate something that never existed? :D [17:11:43] Hugh was actually working with somebody to implement a Block 3 emulator a few years back [17:11:45] I don't know how far they got [17:11:55] but no, that is not a project for me lol [15:42:17] hey [15:56:56] hey Matt [16:12:29] you might not recognize me from my username, but it's me, indy91 [17:05:54] haha [17:06:09] connection issues today? [17:12:55] seems like it, not sure why [17:25:49] that one was actually a short power outage. Maybe the heat, something must be struggling. We are nearly setting temperature records yesterday and today. [17:49:55] that's never good [16:37:03] hey [16:39:04] do we have any good scans of telemetry strip-charts? [16:41:37] hey Matt [16:41:38] uhhh [16:47:21] https://honeysucklecreek.net/msfn_missions/Apollo_10_mission/a10_biomed.html [16:47:25] like this? [16:50:04] yes! [17:28:36] I know I've seen similar charts for Apollo 13 fuel cell voltages and tank pressures during the incident [17:33:05] yeah the mission operations report has something like that [17:33:24] But that looks more hand drawn, with telemetry data [17:33:38] Apollo in Real Time also uses the tank pressure chart there [17:57:56] I want to make something in python/matplotlib to do strip charts [18:02:09] and using actual telemetry, that would be nice [20:29:13] I just pinged UHCL again about that parameter printout document [20:37:13] the system parameters? [20:38:00] ha yeah, that would still be good to have, if it exists :D [20:45:28] I guess the person that was looking for it left, so hopefully there are still places left the search [20:53:28] surely it has to hit a nerve of a librarian [20:53:32] if you point to them out that they have a document listed, but somehow it can't be found [20:56:47] night! [04:07:00] Good evening! [06:30:42] hey Thymo [19:48:05] hey Nik [19:50:45] hey [20:45:59] @Thymo, is there no way on Github to add the person who opened an issue as a reviewer for the pull request with the fix for it? [20:56:14] don't they need to be a member of orbiternassp? [20:57:40] I guess so [20:57:56] which limits the number of readily available reviewers [21:16:22] I need to jump on reviews a bit more quickly [21:39:12] we just need to hire some more people :D [21:43:10] we should try to recruit some more regulars [21:50:16] I would be glad to wear fewer hats [21:50:20] good night! [14:27:39] good morning [14:33:54] doing some reading on telemetry processing today [14:37:00] an alternate universe where DEC computers and TCP were used by NASCOM would make this much easier to understand [14:38:03] also, apparently RS-232 is way older than I thought it was [14:41:26] according to my research, the CCATS 494s do the final PCM decomunication on the data they receieve from the GSFC data lines [14:42:57] then they send a buffer into the RTCC, consisting of 8 bit words, once per second. [14:43:56] RTCC does all the scaling and limit sensing, but doesn't do anything with frame sync, etc. [15:08:28] yeah, we have the scaling and limit sensing functions documented in the IBM RTCC documents [15:21:09] so those would sit between the CCATS buffer and the Intermediate Data Array [15:23:34] so the intermediate data array is where e.g. MOCR displays would get their data or is there more processing? [15:24:20] it would have double precision floating point data then I guess [15:24:26] or single? [15:24:34] I guess it depends... [15:28:36] morning! [15:40:39] single [15:40:46] I think [15:41:23] hey Mike [15:42:38] I think each value in the array uses a single 32 bit word [15:43:57] trying to find my bookmark... [15:50:35] and yes. the Intermediate Data Array is where the plot boards, MOCR displays, and telemetry logger read data from [17:10:35] I'm not sure I ever want to have full telemetry processing in the RTCC MFD [17:11:00] maybe there could be some standalone RTCC application, with integrated telemetry client [17:11:15] kind of starting our RTCC from scratch haha [17:11:28] just would need some system to talk to Orbiter [17:15:53] starting over has the advantage that I can use the right scaling and coordinate systems from the beginning :D [17:24:46] it would be nice to have the option of running either the RTCC in Orbiter, or as a separate application [17:24:58] options add complexity though [17:26:45] iirc Thymo was working on some ideas for a networking API [14:51:36] hey Nik [14:56:18] good afternoon [15:02:15] got a very simple PR up. Just a slight change in how a LM telemetry signal is generated. [15:02:42] so that the APS also shows up as armed if it got armed from the ground, with the telemetry client [15:03:46] relay K206 isn't directly what was used to generate telemetry, the relay contacts get used otherwise, but the telemetry signal basically uses the same spot in the wiring to get its data [15:07:59] code looks good. approved [15:08:55] and merged, thanks. Now it shows up properly in the telemetry client [15:09:10] or on telemetry in general [15:09:46] good to have the LM-3 Systems Handbook :D [15:13:59] morning! [15:15:19] hey Mike [15:15:29] are the new documents on the Virtual AGC website all from you? [15:16:01] those ASTP EMPs look fun :D [15:16:25] yep, those are all from me :) [15:17:10] hmm I didn't look at them too closely when scanning [15:18:02] a routine like the one that calculates the HGA angles to point it at the Earth, but instead pointing it at the "LM" state vector position [15:18:27] oh and this "raster scan" one is very cute haha [15:18:38] yeah [15:19:37] very creative [15:19:49] how did they find the erasable memory space for that... [15:20:18] maybe Skylark is not so limited there [15:20:36] yeah they must have saved a lot deleting all the lunar stuff [15:21:13] there's also this from yesterday's scanning: https://archive.org/details/ams_manual_book1/ [15:22:45] I see a table of contents :D [15:23:17] haha yup [15:24:04] and nice, a description of each subsystem with interfaces to others [15:24:40] even when it's software [15:29:38] ah, it's still for a Block I CM [15:30:31] yeah, this is all the SC-012 configuration [15:37:54] pretty nice stuff. So is this the second book you got? Because you had mentioned a lack of a table of contents before. [15:38:55] I have four of these volumes now [15:39:09] the first one I scanned was Book 3 of the same manual [15:39:22] Book 2 is a lot like Book 3 -- mostly schematics [15:39:46] and then the fourth is like this one, but entirely dedicated to the visual subsystem [15:47:07] you really could construct a lot of the AMS with these books [15:48:47] do we know that the software was written by Link? [15:50:21] hmmmm, good question [15:50:29] I'm not sure [16:01:48] finding out more about the software would be great. Just like finding out more about the AGC emulator :D [16:05:43] oh man I would love to know more about the AGC emulator [16:13:24] I noticed how old our CSM telemetry client really is today. There was a typo in the keycode for uplinking the DSKY plus key. [16:13:33] and I had copied over that code to the LM one. [16:14:04] Of course in the in-sim uplink programs (in PAMFD and RTCC MFD) that had long been fixed [16:15:18] I bet in 2006 or 2007, when the Virtual AGC got first implemented in NASSP, they first started experimenting with uplinks. And later the PAMFD also got that uplink code, where the typo was eventually corrected. [16:16:39] so the CSM telemetry client came first, when it comes to any Virtual AGC uplink feature [16:17:05] oh wow haha [16:18:02] I have some very foggy memories of reading about telemetry implientation back in 200? on the Meadville forums [16:18:58] ...and probably thinking something like "wow this will probably be done soon" [16:19:12] but I don't know if having the Virtual AGC also inspired the very detailed PCM and telemetry generation [16:19:27] or if that came first and generating "more stuff" with the Virtual AGC followed [16:22:11] some of the development is hard to follow from back in the SVN days [16:25:29] I think an Orbiter plugin might be the best way to manage telemetry and external connections [16:29:52] btw, did you see the Buzz Aldrin Sotheby's auction tomorrow? https://www.sothebys.com/en/buy/auction/2022/buzz-aldrin-american-icon [16:32:21] we should save some images of those data cards [17:11:27] yeah, I have a jugsaw puzzle of activation checklist pages, maybe I can add to it [17:11:55] and seeing more cue cards like that really makes me want to finally have them in NASSP [17:31:09] yeah. they have really useful information, right where you need it [17:33:59] I'm just hopeless with meshes and textures, otherwise I would have tried it myself already [19:11:14] Jordan seems to be around, at least on the forums. could he help? [19:14:42] yeah, I think I'll just do a post on the forum, I'm sure someone will jump on it [15:13:44] hey Niklas [15:14:19] hey [15:50:22] was trying to find info on PCM telemetry decommunicators last night [15:50:28] didn't have much luck [16:04:50] morning! [16:05:33] hey Mike [16:05:41] n7275, where are the decommunicators located? [16:06:22] One fun random fact I know about LM telemetry is that RCS thruster activity produces telemetry at such a rate that it can't even be sent to Houston [16:06:38] I think any evaluation of them would be done in the tracking stations even, but not quite sure there [16:09:47] between the reciever and the computer at the remote station [16:10:38] they do frame sync, and have a bunch of parallel outputs to the remote site UNIVAC 642b computers [16:11:02] they were made by Dynatronics in Longwood Florida [16:12:14] https://honeysucklecreek.net/images/other_stations/madrid/more/MAD-MSFTP-2-Decom.jpg [16:14:56] they also have 127 analog outputs, and a 4096x36 bit program memory, as I understand it they do their own scaling for output to analog chart recorders etc. [16:19:04] sounds like a pretty capable I/O machine [16:38:14] I don't think anything faster than 1 s/s made it back through the telemetry network [16:42:28] yeah would make sense [16:43:46] that excludes quite a bit of telemetry data though [16:45:25] I would presume that the digital words weren't sent, and the analog signals were subsampled [16:47:38] by digital [16:48:09] I mean the bi level words [16:48:34] not the CMC/LGC/LVDC words [17:08:46] right [17:09:19] yeah they definitely still need the data that gets sent with a higher sample rate [17:09:31] but subsample will be usually enough [15:56:01] hey [15:59:41] hey Matt [16:24:44] morning! [14:36:53] hey [14:57:33] hey Nik [16:00:29] morning! [16:09:11] while I'm thinking about telemetry stuff, it would be nice to switch away from winsock [16:13:44] I think I want to try to make a plugin that connects to the LM and CSM, and then allows multiple connections to connect to it [16:15:15] hey Mike [16:15:22] winsock is bad because Windows exclusive? [16:19:17] yes [16:22:17] the plugin could also have 2 legacy ports (14242 and 14243), so that we can still use the telemetry clients, but it would also have an additional port for whatever network API we end up making [16:24:40] do you also want to move away from TCP/IP then? [16:31:12] not sure. need to do some research. my knowledge is a little lacking in this area [16:37:16] maybe something like MQTT. [16:40:32] I quite like it being TCP/IP, very universal system that could easily be set up to e.g. send uplink to CSM or LM over the Internet. Using some system that doesn't depend on Windows makes sense, but TCP/IP still seems like a good choice. [16:45:56] but my knowledge there is also lacking :D [16:49:03] I doubt we need an overly complex protocol [16:53:51] in fact we probably just need to send some time and state vector information along with the telemetry [16:54:57] ooh you were thinking in terms of an API for Orbiter to send data to an external application [16:57:22] yes [17:01:55] if we do it right we could have external applications and internal tools connected and our LM and CSM wouldn't even know the difference [17:26:33] thewonderidiot, this scenario from Zuppermati on the forum has some really strange behavior [17:26:43] V11 N10E 5E [17:26:54] monitoring an input channel, seems pretty straight forward [17:26:57] but R1 stays blank [17:27:17] if I do V37E 00E and try again then it works as it should. R1 shows the channel data, R3 the channel number (00005) [17:28:05] the LGC also seems... laggy [17:28:47] like it doesn't clear the DSKY registers as quickly as usual [17:29:03] not sure if that means anything. Also seems to be better if I do a V37E 00E [17:32:40] but how could V11 N10E 5E ever not work correctly... [17:38:32] the same happens with any display really [17:38:40] like, V01 N01 isn't even showing anything :D [17:55:43] output channel of course, channel 5 is send to the RCS [18:07:04] well that's rather odd [18:26:34] uhhhh [18:26:36] that is weird [18:39:46] V35 also fixes it [18:43:21] so some pinball erasable(s) must be messed up somehow [18:43:47] yeah, it's like there is a V11 N10 active in the background somewhere, messing things up [18:57:11] does V34 fix it? [18:58:14] ah, that would kill some routine, extended verb or so [18:58:49] it does not [18:59:25] hmm [18:59:39] now it randomly started working [18:59:47] need to do the same sequence of inputs again [19:01:24] haha [19:01:37] if I do V11 N10E 30E it does show channel 30 [19:01:51] and then if I do the same with channel 5 again then it also works [19:01:57] no V34 or V37E 00E or so [19:03:12] almost seems like it is thinking when I want it to look at channel 30 [19:03:28] some process stopping or starting [19:03:39] and then it shows channel 30 and from then on everything is fine [19:03:47] maybe I'm imagining the thinking part :D [19:04:54] so what process would be kickstarted when looking at an input channel [19:05:55] something that doesn't happen when looking at an output channel [19:07:34] uhhh [19:07:37] there should be no difference [19:07:59] actually there is no difference, for sure [19:08:39] so pinball only refreshes digits on the DSKY if it thinks they have changed [19:09:01] could it be that it thinks it already has 00000 (or whatever) displayed? [19:09:32] possible [19:09:44] would it be 0000 in the DSPTAB? [19:09:47] 00000* [19:10:20] yeah [19:10:30] or no [19:10:38] sorry, that would be a blank register [19:10:54] the DSPTAB corresponding to that would be... a lot of random bits [19:11:13] five sets of 10101 spread across three different relay words [19:11:27] ooooh [19:11:33] that is it though [19:11:39] LM telemetry client be praised :D [19:11:46] R1 has 00000, R3 has 00005 [19:11:46] hahahaha [19:29:55] sorry, was away for a moment. But the theory is correct that pinball thinks the data is already on the DSKY, but it's actually blank [20:54:52] night! [14:03:37] hey Nik [14:03:51] hey hey [14:04:21] I'm also bothering UHCL again. Request the Apollo 7 and 9 flight control division postmission reports. [14:04:34] Requested* [14:05:04] hopefully includes the FIDO reports. I'm looking for stuff like details on maneuver planning or K-factor determination. [14:15:21] they didn't reply to my last email. I hope I'm not blacklisted. [14:16:40] ah, maybe Ryan is, too :D [14:17:08] and somehow I haven't been. Well, we will see... [14:25:48] I added a new project for my network multiplexer/thing last night [14:26:21] took me a good 2 hours to remember how to do [14:28:44] I have a small RTCC side project from a few weeks ago that will be rather fun to test [14:29:06] it requires you to do some Mode IV aborts [14:30:26] there are different techniques that can be used. One of them would be burning until 200 NM apogee, with a priority of having a positive altitude rate [14:30:48] it can then happen that you are in a e.g. 0 x 200 orbit or so [14:31:04] in this case you would perform a maneuver called apogee kick [14:31:18] oh fun [14:31:34] and for that they had a display that is well documented in the IBM RTCC documents [14:31:49] 31.7° line on the horizon and the displays shows the DV to get to some input perigee altitude [14:32:01] display* [14:32:34] I've had trouble replicating this actually. I never got the altitude rate high enough, so I usually ended up with a safe orbit already after the Mode IV burn [14:32:45] successfull failure... [14:35:04] a separate calculation is done on a display updated in real time [14:35:24] you know how you put 6999.9 on the DSKY for launch [14:35:46] the display would calculate a DV for the Mode IV burn [14:35:59] burn until EMS shows that amount of DV given by MCC [14:36:16] but that display shows a lot of telemetry, so I never implemented it yet [14:54:28] ahh [14:54:43] okay [14:55:02] oh sorry [14:55:12] " you know how you put 6999.9 on the DSKY for launch" [14:55:30] I meant the EMS of course [15:01:00] hmm, but I can already get AGC and LVDC state vectors with the logic on the vector panel summary [15:07:16] it's kind of too fun to not try to implement that display [15:08:40] yeah. would be very cool [15:09:01] I have the rare problem of having two versions of it [15:09:16] late 1968 and early 1970 [15:09:36] main difference is the 1970 version directly includes an apogee kick calculation [15:14:38] have you ever done a launch looking at the launch analog displays? [15:21:28] I have :) [16:07:57] well I am not on a blacklist, so that is good news :D [16:29:09] morning! [16:33:23] hey Mike [17:09:24] hey [17:29:02] starts dreaming about V79 [17:29:04] I'm going to try to polish off the BOM for the rope reader this weekend [17:29:17] and probably get the final backplane board ordered [17:29:18] haha [17:29:23] yeah me too :P [17:30:24] maybe I'll hold off on Apollo 12 for now... [17:30:46] to be clear, we're still talking on the order of a couple of months at least [17:30:53] it's not like a next week thing :P [17:31:16] it's a matter of hours from getting the binary to having an NASSP update though [17:31:52] lots of experience by now doing that sort of update [17:31:56] :D [17:33:17] ah, and we have Luminary 116 and 131, so the bad Apollo 11 ephemerides in Comanche 55 will only need a tiny change in the padload calculation [17:33:54] just a case of using the right numbers for the right mission, but we already have the numbers [17:35:29] we have the flight padload for Comanche 67 don't we? or is that some math that NASSP needs to do differently? [17:36:08] yeah, different math because our Earth doesn't do nutation and our Moon doesn't do the same libration movement as in reality [17:36:16] gotcha gotcha [17:37:32] the calculation for Earth was done with a wrong sign in the past :D [17:37:41] but it's a tiny error [17:37:52] hahaha [17:37:54] only noticed it when I build the Skylab 2 scenario with Artemis [17:38:07] Earth precession period is 26,000 years [17:38:14] so that is equivalent to 360° [17:38:48] and due to the yearly changing coordinate system the precession to be taken into account is half a year at most (except Apollo 17) [17:39:06] so you can calculate that angle there and it's not very large, even if the sign is wrong [17:39:50] but I'll go through it mission by mission very soon and fix it all [18:23:36] right that makes sense [12:49:29] good morning [14:20:27] hey [15:31:53] RTCC question: how are MEDs processed in the real RTCC? is there single routine that waits for MED input and directs other tasks when it sees specific MEDs? [15:36:38] yeah pretty much [15:36:44] the main function ins GMGMED [15:37:02] NTRS ID 19730062603 [15:37:07] PDF page 352 [15:37:27] and that decodes the MED input and then calls the various subroutines for more decoding [15:37:36] there is a subroutine for each letter [15:37:53] like, MED M50, there is one subroutine decoding M code MEDs specifically [15:38:10] CENTER-RTCC-14-001-001.pdf [15:38:17] that file has a lot of the MED decoding functions [15:39:29] in some cases it's actually two functions doing the decoding for one type of input [15:39:39] GMGPMED and GMSMED for P-type MEDs [15:40:00] but I've only done it in one function [15:40:12] so I have the GMGMED function which has the full string as an input [15:40:52] and that decodes the MED and calls the right subroutine, giving to it a vector with the individual items [15:41:18] there was also an option to prepare punch cards [15:41:28] and read that in, and that then gets decoded [15:41:54] GMGCARD [15:42:13] can also be found in CENTER-RTCC-14-001-001 [16:57:41] okay, cool [17:34:38] what is this RTATTACH macro that GMGMED references? [17:41:46] I wished I knew how these macros worked [17:42:21] "Creation of and [17:42:22] communication with dependent and independent tasks is via the ATTACH and [17:42:23] RTATTACH system macro. " [17:47:09] ooooooo [17:47:13] hmmmmm [17:49:29] so maybe a case where it's not a function call, but creating a "thread"? [17:49:34] or talking to one [17:50:23] "After phase checking, error [17:50:24] checking, and converting all items on the input MED, GMGMED RTATTACHes [17:50:26] the specified subsystem load module and passes the converted and for-matted data to it." [17:51:06] so however RTATTACH works, it's done with the e.g. M-type MED module [17:51:23] in my case just a simple function call [17:53:40] if you search for "ATTACH MACRO" in mwhume.space/Files/OS360TAPES/AAPVTF1.TXT there are some references to it [17:57:17] this has some references to both: https://files.eric.ed.gov/fulltext/ED082488.pdf [18:06:40] Aparently the JPLOS had this macro as well https://ipnpr.jpl.nasa.gov/progress_report/XV/XVT.PDF [19:05:30] Whatever this "Master Control and User Interface Software System Description" document is, looks interesting. no luck finding it unfortunately [19:17:21] where is that being referenced? [19:25:29] ah, in the JPL document [21:08:17] night! [11:45:46] hey [12:36:01] hello hello [12:46:31] there really isn't that much out there for cross-platform TCP libraries [12:48:23] I don't like the idea of including Boost... [13:53:59] maybe I just throw some #ifdef WIN32 blocks at it eventually and don't worry about it for now. writing simple code twice sounds wey better than writing complicated code once [15:52:29] "writing simple code twice is better than writing complicated code once" I need to put that in a frame [16:23:21] haha [17:08:31] for some reason this does not want to build... [16:20:09] morning! [16:49:20] hey Mike! [16:50:31] what's up? [16:51:40] work mostly, but there's a few post-it note sketches of what a NASSP networking API might look like [16:55:59] I probably need to stop thinking about how the bytestream should like like, and start thinking about how (and what) external applications should connect and communicate [16:57:16] oooooh nice [17:11:47] good evening [17:12:56] hey Nik [17:14:24] yo [17:15:16] what's up? [17:15:56] I'm making good progress on a real, proper AGC disassembler [17:16:03] which would have saved my fingers a lot of pain with Sundance :D [17:17:17] that sounds useful for reconstructing Comanche 72, provided we get 67 [17:17:35] indeed! [17:35:20] so yeah, I ordered what should be the final version of the backplane board on Friday, and it shipped today [17:35:42] that'll let us build up the connector plate on the rope reader, with the Samtec-Malco pins [17:36:01] and over the next couple of days I'm going to work on finishing off the BOM for the driver board [17:37:56] very nice [17:38:17] other topic, do we have a good system for distinguishing GSOP only PCRs? [17:40:30] I'm looking at PCR 772.1 and 772.2 [17:40:38] "Libration vector at landing time" [17:40:54] if this is GSOP only then I think it's a very ignored PCR [17:41:21] hmmmmm [17:41:38] we have two printouts of the TRW onboard data load program, in the Apollo 11 and 12 padload documents [17:42:01] I wanted to make our inputs for the same calculation the same, or at least a lot closer [17:42:04] I don't think we do? although I vaguely remember seeing something that might be useful, if my brain isn't making it up [17:46:51] well anyway, before the PCR the GSOP said [17:47:00] libration vector should be for mid mission [17:47:09] after the PCR the Luminary GSOP said [17:47:19] at landing time, uplink a new one for lunar liftoff [17:47:38] and Colossus just says, very unspecific, "at the time it will be used" [17:48:07] but the vectors in CM and LM padload are identical for all missions :D [17:48:21] I have no evidence for any uplinks, but I need to search for that a bit more [17:48:46] and with Apollo 11 and 12 at least (the GSOP change was for 12) it uses the same, very very rough landing time to calculate the vector [17:48:55] hahaha [17:49:00] hmmm [17:49:04] so yeah, I think this is rather ignored PCR, at least operationally [17:51:34] so this PCR went in between 11 and 12? [17:51:47] I wonder if the FSRR material for 12 has anything [17:52:11] yeah, was added for 12 in both GSOPs [17:52:19] https://www.ibiblio.org/apollo/Documents/apollo_12_fsrr_slides.pdf [17:52:58] no mention [17:53:10] so yeah, very likely GSOP-only [17:55:48] makes sense [17:56:30] would be nice if he had more examples of that onboard data load program printout, we have only 11 and 12 and they are identical for CM and LM [17:56:48] and as the libration vector time they both use 4.5 days after noon GMT of liftoff [17:56:55] which is very roughly landing time I guess :D [20:56:23] night! [14:09:11] hey [14:11:52] good morning [14:31:59] ok, created my share of PRs for the day :D [15:08:29] morning! [15:08:42] indy91, I did a bunch of research and you were right [15:09:03] I hear that all the time [15:09:06] just kidding :D [15:09:09] :P [15:09:18] MANCHE72 Rev 3 is going to be a puzzle almost identical to the Comanche 45 puzzle [15:09:28] fun... I hope [15:09:53] it's in a place where we can compare Comanche and Artemis which is slightly helpful [15:10:04] what did they break this time [15:10:44] https://www.ibiblio.org/apollo/listings/Comanche055/T4RUPT_PROGRAM.agc.html#474C4F434B43484B [15:10:52] there's the relevant part of Comanche 55 [15:11:05] ah gimbal lock stuff [15:11:21] and Artemis: https://www.ibiblio.org/apollo/listings/Artemis072/T4RUPT_PROGRAM.agc.html#474C4F434B43484B [15:12:02] the addition is essentially that if you are in Saturn mode, don't run a coarse align if you get into gimbal lock [15:12:16] that sounds very familiar [15:12:36] Artemis's implementation has been further modified by PCN 1041, which makes it so that average G also must be running [15:12:42] Manche72 R3 doesn't have that restriction [15:13:15] but, this happens in bank 6 which is completely full in Comanche 55, and presumably will also be in 67 and 72 [15:13:27] between 72 and 72R3, both the bank 6 and 11 checksums changed [15:13:37] so I think they may have stuck the additional logic at the end of bank 11, possibly [15:14:19] which is interesting because this is all in basic, and it's much more annoying to do inter-bank stuff like that in basic than it is with interpretive [15:16:51] ok, so the initial change from Comanche 55 there is PCR 984 [15:17:04] Avoid Coarse Align during Saturn [15:18:07] did they add this for 72 or 72 rev 3? [15:18:35] and then what is the puzzle going to be. some fix to it? [15:54:20] or is PCR 984 the change from 72 and 72 rev 3, and the puzzle is how to squeeze that into banks 6 and 11 [15:54:28] 72 to 72 rev 3* [16:32:50] indy91, sorry am back now [16:33:03] PCR 984 was the change between 72 and 72r3 [16:33:19] so the puzzle is (a) what it looks like without the PCN 1041 changes, and (b) how they fit it into those banks [16:33:42] was it A change or THE change [16:33:50] the timeline is slightly confusing [16:34:14] SCB meeting #34 approved four Colossus 2D changes after 72r3 had already been released for manufacturing?! [16:34:31] and why rev 3 and not rev 1 if it was only one change [16:34:46] they held off on including PCR 984 in Comanche 73+ and Artemis for a very long time because they thought they might to PCR 954 instead [16:34:52] *do [16:35:01] https://www.ibiblio.org/apollo/Documents/apollo_13_fsrr_minutes.pdf [16:35:19] pdf pages 15-17 [16:35:48] I think the r3 vs. r1 thing might be similar to e.g. Luminary 69 rev 2 [16:35:53] they screwed up the first tries [16:35:55] maybe? [16:36:21] that "T6JOB OPCODE Correction" PCR was also added to the same revision of the GSOP as PCR 984 [16:36:32] but this FSRR material seems to indicate that's GSOP-only [16:37:21] oh the other changes are GSOP only [16:37:27] even if they sound like not GSOP only [16:38:21] possibly yeah [16:41:00] the FSSR specifically says (GSOP) for them [16:41:14] only for PCR 984 does it say 72r3 [16:42:09] yeah, that's what's making me think it is the only change [16:42:55] we don't have PCR 984 but we do have PCR 1041 https://www.ibiblio.org/apollo/Documents/PCN-1041.pdf [16:44:52] PCR 984 sounded so familiar, I need to think where I had all heard and read about it [16:45:14] maybe just GSOP and the usual memos, but maybe not... [16:45:26] https://www.ibiblio.org/apollo/Documents/COL-258.pdf [16:45:30] there's a brief mention at the bottom here [16:47:05] it finally went in between revs 102 and 104: https://www.ibiblio.org/apollo/Documents/COL-unnumbered-042770.pdf [16:51:32] of course we have Comanche 72 flowcharts but not 72R3 [16:51:34] hmmm [16:52:08] well, this being in basic might be both a blessing and a curse [16:52:42] because unlike interpretive, we can place some meaning in the bits of the difference between expected and actual checksums [16:53:06] i.e. we can probably work out what set of addresses the instructions in each bank reference to solve the lower bits, and then work on the opcodes to solve the upper bits [16:53:26] with some small lower-bit error coming in through e.g. EXTEND [17:07:20] it wasn't so immediately clear to me that PCR 984 was the 72r3 fix because there wasn't an obvious new feature in 72 that needed to be fixed [17:08:03] in fact it seems more likely that this issue was already there ever since they could manually steer the Saturn during powered flight, starting on Apollo 10 or 11 [17:08:55] but when they finally found this problem they might have thought it serious enough to manufacture a new version [17:09:10] yeah [17:09:16] similar to LNY-77 in a way [17:09:22] that was there in 9 and 10 [17:09:31] trust in all subsystems increased with every mission, just in the CDU it increased all the time :D [17:09:37] decreased* [17:09:40] hehehehe [17:09:55] poor CDU [17:10:23] it's also kind of interesting that it's just a PCR and not a COM [17:11:21] ....I was about to say that every other module remake was an anomaly fix of some kind [17:11:27] but that's not true at all [17:11:45] even on the same mission LM131r1 was all about adding P66 auto, and not fixing some anomaly [17:12:02] yeah [17:12:29] have the CDR of the upcoming mission lobby for something, and things start to happen [17:12:55] although strictly speaking LUM131r9 was the P66 auto, and LM131r1 was the anomaly fix release for that :P [17:13:50] you say that like we already have done a successful reconstruction of that :D [17:14:17] I've researched the everliving hell out of that one already [17:14:39] that one is also backwards in that we're going to get a LM131r1 dump and then have to reintroduce the bugs to make LUM131r9 [17:15:11] ah yes, reintroducing bugs, our specialty [17:15:38] I'm sure I have done that with the RTCC once or twice [17:16:32] hehehe [20:50:24] from all the reasearch I've done on the question of "what logic decides which station is transmitting a carrier, at any given time?" I think it was just manually switched [20:52:51] which would be pretty easy to implement. [20:52:54] at least that wasn't a lot of work at lunar distance [20:55:40] would also be pretty easy to automate in the MCC class [20:56:29] yeah, it already does all that AOS/LOS logic anyway [20:57:13] I'll just make the new signal source the most recent AOS [20:59:25] yeah that makes a lot of sense [21:06:22] oh, one other benefit of this network plugin, is that we could very easily remotely cause system failures [21:11:35] ah yes, one of us streaming a mission and everyone else thinking of ways to screw it up and send failures [21:12:07] good night! [14:28:06] hey [14:44:12] hey Nik [14:49:45] how far did you test the PR for the LM master alarm buttons? [14:49:56] did you also check if the Checklist MFD can use it now? [15:14:31] oh. whoops. I just tested pressing them. [15:14:43] did I miss the whole point of that? [15:17:06] well there was a point to only asking Ryan for a review in this rare case :D [15:17:45] I'll wait with merging for when he has given his ok that the buttons can now be used with the Checklist MFD [15:17:56] I've tested that a little bit, but he is the expert [15:18:42] and yeah, that is the point of the PR. Previously the buttons didn't exist as an object, they just had some mouse click processing [15:18:49] and redraw, both in CWEA code [15:18:54] now they are actual Panel SDK buttons [15:20:12] the equivalent buttons in the CM are actually a sort of hybrid [15:20:22] ahh okay. [15:20:40] was that discussed on Discord? [15:20:45] there is one fake button that the Checklist MFD can use in the CM, which simulates clicking any of the buttons [15:21:31] well, I just said to Ryan that he has the exclusive job of approving that PR. But we didn't talk much about it, you might have missed it. [15:21:55] yeah. I probably just missed it [15:22:43] no problem [15:26:23] I think when I do this AOS/ground station project, I will implement it with clbkGeneric rather than a connector, but using the same "message" format that our connectors use. can you think of any features we should add? [15:30:11] hmm, I'll try think of some [15:33:55] definitely needs to be able to get state vectors for vessels [15:44:36] there's a vector3 message value in the ConnectorMessage type [15:44:52] might need to add a few more [16:12:11] morning! [16:24:23] hey Mike [16:29:22] what's up? [16:37:41] hey [16:37:59] time for padload work [16:43:30] finally fixing my embarassing wrong sign on AXO and -AYO [16:48:00] hehehe [16:53:33] to be fair, it doesn't help when the variable itself is already called "-AYO" :D [16:53:54] hahaha [16:54:00] is -AYO supposed to be positive or negative? [16:55:04] it moves from negative to positive with precession [16:55:59] yearly coordinate system defined at January 1st and being used from July 1st to July 1st next year. So a launch in early July has a larger negative value, Late June larger positive value [16:56:40] near January 1st it is close to zero [16:57:02] and Apollo 17 is still using the 1972 coordinate system, so that has to take one year of precession into account [16:57:47] which made me discover that I got the sign wrong in the first place [16:58:12] because it has the larget -AYO value of all missions, and it's positive [16:58:14] I had it negative [16:58:18] largest* [16:59:24] it's negative in the padload document. The real padloads also have to take nutation into account, but the trend is quite obvious [16:59:45] ahhhhh [16:59:51] yeah that is very tricky [17:00:11] well when I created the Skylab 2 scenario I discovered that P21 gives a wrong longitude by 0.01-0.02° [17:00:27] but the Apollo 17 padload gave it away that I always had calculated it wrong [20:53:06] night! [14:50:54] hey [15:17:51] hey Nik [15:49:25] trying to do the best possible test for the updated AGC correction vectors [15:49:53] I'm uplinking a state vector at a specific time and then call P31 with that time, so that it doesn't do any coasting integration [15:49:58] P21* [15:50:18] and with Apollo 17, worst case [15:50:39] and then use the RTCC MFD Nav Check PAD to compare [15:50:44] so for longitude I get [15:50:48] actual: -115.03903° [15:51:06] old padload: -115.04245° [15:51:19] new padload: -115.03934° [15:52:46] I thought the new padload should even be closer to the actual, but it's definitely better haha [15:53:44] an order of magnitude decrease in error is never bad [15:55:00] on the surface that previously was an error 380 meters [15:55:33] now 35 meters [15:58:17] any idea what the remaining 35m is from? [15:58:57] earth shape? [16:01:28] for longitude that shouldn't be relevant [16:01:48] maybe I still used a wrong number in generating the correction vector [16:02:04] some CMC constant I converted wrong [16:02:46] oh, yeah for longitude that shouldn't matter. unless the moon hits the earth or something like that. [16:03:14] I was thinking latitude for some reason. I can read. [16:05:12] I feel like I am not taking the hardcoded AZO into account correctly... [16:09:33] but maybe they didn't in reality either [16:10:03] if you don't care about that then UNITW, the correct vector, is essentially the polar unit vector in reference coordinates [16:10:52] correction* [16:53:51] thewonderidiot, the pressure is on: https://github.com/orbiternassp/NASSP/pull/814/files#diff-2473019f94f65ede2f1084b526351b7e7cc281bef1e804d38f8191a5f6e6e0deR5286 [16:54:06] hahahaha [16:54:08] I'm working on it! [16:54:48] until then we still need to use Comanche 55 with its broken fixed constants. Actually about that. [16:55:01] https://www.ibiblio.org/apollo/Documents/COM-11.pdf [16:55:12] https://www.ibiblio.org/apollo/Documents/LNY-55.pdf [16:56:07] only COM-11 mentions an "octal conversion error" in addition to the constants having been calculated wrong [16:56:22] but on Apollo 11 in both Luminary and Comanche the constant is identical [16:56:47] oh interesting [16:57:51] or was that the revision of the anomaly report [16:58:04] I feel like it could affect both [16:58:33] hmmm [16:58:34] but "octal conversion error" is weird when you don't any octalsf for this into the code [16:58:51] WEARTH 2DEC .973561595 [16:58:53] oh you don't? [16:58:57] ohhhh that's super weird then [16:59:16] maybe they mean the conversion from rad/sec to revs/centiseconds? [16:59:49] or, the CMC is not as consistent with these things, there is another variable which does nearly the same, just maybe with different scaling [16:59:56] constant* [17:00:17] Luminary has its controlled constants section and you can rely that everything important is in there [17:03:02] ah but you know what, I think they mean WEARTH in general [17:03:33] if I compare that bad Comanche 55 value with anything they used before or after then I get almost exactly the 3760 meters error they mention [17:07:49] nice :) [17:07:59] reproducability is good haha [17:14:17] and ggalfi's PR is very good. Usually it's a headache when there are PRs that can break a lot of things (ALL of our accelerometers in this case), but this one is ready already. [17:14:35] what's the motivator for these changes? [17:15:20] lots of duplicate code [17:15:38] and ggalifi came up with the system for shaking and viewpoint moving under acceleration [17:15:43] his code had a bug [17:16:02] and it would have meant that he had to do a calculation as complicated as our accelerometers [17:16:25] so instead he implemented one class that calculates the proper acceleration for the vessel [17:16:30] and accelerometers can access [17:16:38] so it only gets calculated once per vessel [17:25:57] oh awesome :D [17:37:55] we should give him a raise [17:41:32] we don't have that budget. But I can give an approving PR review. [17:41:43] although... there is a build conflict [17:41:50] uh oh [17:42:04] indy91 what do you mean? I'm positive that we have the budget to at least double his salary [17:42:24] yeah, in percent we have a lot of wiggle room for that [17:42:39] oh is it just git thinking an addition is a rename or something. I think I saw that. [17:43:41] a merge conflict I meant. And it seems to be real [17:43:50] Orbitersdk/samples/ProjectApollo/Build/VC2017/Saturn1b.vcxproj.filters [17:44:25] and Saturn5 [17:44:43] I guess fairly typical when you add a new file when in the main branch there was another file added [17:47:46] can I somehow solve it for him... [17:50:20] I remember Thymo changing a PR of mine before merging it [17:51:46] was your MR off of orbiter-nassp/NASSP? he probably had write access to it then and could just check out your branch [17:51:56] if ggalfi is MRing from a fork, you probably can't fix it for him [17:54:46] I'm not sure [17:56:08] I'll just ask him to fix it, it's a bit of annoying text editing but I am sure he knows how to do it. Otherwise I would make a PR for his branch with his PR :D [18:00:48] if your a reviewer you can commit directly to someone else's branch [18:03:41] how do I even do that though [18:03:55] would I push directly to it? [18:04:14] create local branch of it, make the changes, push it to ggalf/accel? [18:04:17] ggalfi* [18:08:50] yeah, just checkout ggalfi/branchname and then commit and push to it [18:11:02] s/branchname/accel [18:11:07] only checkout? That's what I have done to review the branch, it says I am in a detached head. Can I commit there? [18:11:40] ah, well it says I can make experimental changes and commits etc. [18:11:45] I guess it wouldn't hurt to try [18:17:29] hmm [18:17:32] there are typos :D [18:17:35] intertial [18:24:15] if I ever need a term for internal+inertial I will use that one [18:27:14] I hope this works [18:27:44] nope [18:28:03] it warned me not to commit on a detached head and it's not letting me push [18:28:10] probably a bad idea [18:29:16] ah [18:29:18] now maybe [18:29:22] I hope I didn't ruin it [18:30:17] just had to do "git checkout -b accel" before pushing. Should have done that before committing really. [18:31:46] ahh, because it was just the commit that was checked out, not the branch [18:34:43] I did "git checkout ggalfi/accel" [18:34:49] is that not checking out the branch? [18:36:31] and lol, "if I ever need a term for internal+inertial I will use that one" When the PAO says during the Apollo 11 launch that "guidance is internal" I think he means inertial :D [18:36:50] power is switched to internal at T-50 seconds [18:37:09] but guidance is internal wouldn't make much sense. There is no external guidance [19:15:40] they never got around the making the wire guided Saturn V? [19:20:10] that would be one mighty wire, reaching 3 times around the Earth so that it still works for TLI [19:22:50] https://imgs.xkcd.com/comics/voyager_wires_2x.png [19:35:40] haha [19:35:57] and eventually the wire falls on some distant planet and starts a bronze age [03:29:58] oh god why https://github.com/orbiternassp/NASSP/blob/41f2a6c784d73b15454e45ffecf95903db7dfcd6/Orbitersdk/samples/ProjectApollo/src_launch/mcc.cpp#L584 [13:15:53] hey guys [13:22:26] hey Niklas [13:22:40] I believe I still owe you a cue card mesh [13:26:10] hey Alex. I wouldn't call it owe, but I still would quite like one, yes haha. I planned to make an open request on the forum about it, but hadn't come around to it yet :D [13:27:33] really, at first I just need something I can use for testing, the logic to switch it on or off etc. [13:27:58] yeah, I apologize for it taking so long... I thought I would have more time then I did [13:28:17] I will start by getting my blender working environment back up to speed [13:33:09] I'm implementing a long desired features, doing an EVA with two astronauts instead of one [13:33:13] feature* [13:33:50] ah nice [13:38:16] btw is it me does this commit hint to a Comanche67 in the near future? :D [13:38:20] https://github.com/orbiternassp/NASSP/commit/0438753b3508b99dbafd6b6a98547cc19bd04583 [13:38:56] not quite near, but, probably :D [13:39:56] it would be nice to get the Apollo 14 CM software too [13:40:21] maybe it can be reconstructed [13:40:25] that way the checklists would work [13:40:46] from 67 to 72 and 72 rev 3 should be quite achievable to reconstruct [13:40:55] right [13:41:14] to 108... who knows [13:46:29] https://i.imgur.com/qyoFIqT.png [13:50:57] Neil's happy to finally have company [13:53:44] and his company is... Neil [13:53:53] we only have one texture, both say N. Armstrong :D [13:54:00] haha [14:34:00] brb [14:45:13] hmm [14:45:32] CSM LV sep has the long pause once again [14:45:47] I thought that was mostly fixed [14:47:08] by pre-loading the LM mesh beforehand [14:47:22] yeah, that is still done I think [14:47:36] for the LM VC as well? [14:47:55] hmm [14:48:46] I only get a very short pause [14:48:59] noticable, but I am pretty sure a lot shorter than we used to get [14:50:59] need to even find in the code where the LM meshes would be loaded [14:51:47] https://github.com/orbiternassp/NASSP/pull/588 [14:51:51] ah, its in LoadSat5Meshes() [14:52:00] the VC mesh is preloaded [14:52:42] which makes sense since its almost 40 MB [14:53:18] but the other LM meshes aren't? [14:53:57] I remember that commit [14:54:17] I had tried it with the Ascent+Descent stage as well but I think it didnt make much difference [14:54:34] I think combined they are only like 5 MB [15:14:02] morning! [15:15:21] yeah 108 would be hard. and we don't even have the bank checksums for it like we do for most of the other ropes... NARA was missing that one :( [15:15:35] but we do have good Comanche memos, so we might be able to get close-ish [15:16:31] hey Mike [15:16:54] sounds exciting [15:18:32] ah damn, I didn't know that we don't have those banksums :( [15:19:00] after Frankendance follows... Frankenmanche? [15:19:33] hehehe [15:19:46] Manchenstein [15:21:32] indy91, the long pause only happened on my initial session earlier [15:21:42] now every subsequent load is much better [15:28:36] ah ok [16:19:11] but yes, AlexB_88, nothing is ever guaranteed until it's already happened.... but I think a Comanche 67 dump is very nearly as close to guaranteed as it gets. I'll be ordering the boards for the rope reader in the next week or two, and then it's just a matter of getting it built up and tested [16:19:25] and then scheduling :) [16:20:01] I think this year is somewhat likely, if not then early next [16:22:29] sounds great...Ill have to brush off those Apollo 12 procedures ;) [16:22:52] though I think my next run will be 16 [16:26:40] so if/when 67 is released (Apollo 12), the Apollo 13 CM software (72?) can be easily constructed as well? [16:27:55] oh no, you said the E word [16:28:32] ah forgot thats a bad word here :D [16:31:30] if we have the banksums for both 72 and 72 rev 3 then getting to 72 could be quite managable [16:31:39] and not only 72 rev 3* [16:32:36] right [16:32:44] we already know that 72 to 72 rev 3 is going to be a bit of a puzzle [16:33:24] hey guys [16:33:58] hey [16:34:02] hey Matt [16:34:32] now that I think about it, revision 3 could have been caused by the tumbling IMU on Apollo 12. Does the timing of that change work out? [16:34:38] thewonderidiot [16:35:14] they made this somewhat last minute change which prevents an IMU coarse align while you are controlling the Saturn manually with the RHC [16:36:12] you don't really need a good IMU for Saturn takeover, but the CDUs are used during coarse align, so if the IMU goes into coarse align the CMC/IU interface becomes unusable [16:42:55] hmmmm [16:43:32] could be [16:43:59] 12 launched on November 14, then Manche72 rev 3 went out for manufacturing on December 12 [16:44:04] so about a month after [16:44:35] that sounds right [16:44:54] https://www.ibiblio.org/apollo/Documents/edg_memo_216.pdf [16:45:01] if something was wrong with the LVDC on Apollo 12 they couldn't have taken over if the IMU went into gimbal lock [16:45:04] this memo was published on November 21 [16:45:18] yeah [16:46:30] they were definitely worried about these type of issue at the time [16:46:41] yup [16:48:35] 67 -> 72 is still a bit of an unknown for me. it's a small set of changes, and there isn't anything major like a whole new PTC verb missing [16:49:01] but it will get progressively harder to compare Comanche with Artemis since they diverged at 67 [16:52:30] we will get a dump module 2 (so banks 6-13)... so the more changes that were in those banks, the better [16:52:58] Comanche 72 module? [16:54:03] yeah [16:54:36] PCR 936.1 will be here: https://www.ibiblio.org/apollo/listings/Comanche055/P34-P35,_P74-P75.agc.html#52333641 [16:54:50] at the start of R36A [16:54:56] loads TIG instead of zero [16:55:06] that sounds easy enough :) [16:55:09] if that is still in the same place [16:55:13] yeah that is the easy one [16:55:29] oh, cool, looking at banksums [16:55:32] nice user friendliness update, too [16:55:42] 55->67, almost all of the banks are quite different [16:56:09] 67->72, a decent number of banksums are identical (including both fixed-fixed banks), and a lot of others are only different by small amounts [16:56:31] a much easier starting point :) [17:00:41] https://github.com/virtualagc/virtualagc/issues/1140#issuecomment-761917970 [17:01:02] Ron did a bunch of research on PCR 960, which likely only went in on 72 and not already in 67 [17:05:02] ah but I think we already know what that is [17:05:12] we have the Colossus 2D GSOP section 5, I totally forgot [17:06:12] https://www.ibiblio.org/apollo/listings/Comanche055/P51-P53.agc.html#312E335345434450 [17:06:28] PCR 960 is changing this constant to 2.4 seconds I think [17:16:57] enough comparisons of two AGC versions which we BOTH don't have :D [17:30:02] hahahahaha [17:30:04] soon! [17:33:03] especially since my weekend is totally free [17:33:31] I'm going to hold myself to finishing the BOM this weekend and ordering the boards next week [17:42:58] although you know what's very weird? [17:43:12] the PCR 984 stuff in module 2 is entirely self-contained [17:43:29] it's very possible that we figure out how to make 72R3 from 72 before we figure out how to make 72 from 67 [17:43:43] ....kind of like how we knew exactly how to make 45R2 but were struggling with 45 :D [17:44:34] self contained, didn't you say there was a full bank and they would have to do some non-Interpreter bank switching? [17:44:48] yes, but in the same module [17:44:52] ah right [17:44:53] we have all the addresses and things we need [17:44:58] probably 2 banks involved, but one module [17:45:02] yep [17:45:13] also I'm like 80% sure I know how they did the bank switch [17:46:17] https://www.ibiblio.org/apollo/listings/Comanche055/T4RUPT_PROGRAM.agc.html#534554474C4F434B [17:46:45] whoops, clicked the wrong thing [17:46:46] https://www.ibiblio.org/apollo/listings/Comanche055/T4RUPT_PROGRAM.agc.html#474C4F434B43484B [17:46:49] in here [17:47:04] TC IBNKCALL [17:47:05] CADR SETCOARS [17:47:16] they're already doing a bank switch to call for coarse align [17:47:30] so to add a new check, all they would have to do is change that CADR to point to the code at the end of the other bank [17:50:06] hmm, so this is basically some example how they would have probably done it and we can copy it? [17:50:33] ah no, this is the code they modified [17:50:42] and not call it from elsewhere [17:51:06] the gimbal lock check code itself was changed to include the checks [17:51:19] on the flags for Saturn mode [17:53:24] right, yeah [17:53:33] https://www.ibiblio.org/apollo/listings/Artemis072/T4RUPT_PROGRAM.agc.html#474C4F434B43484B [17:54:13] PCR 984 adds the [17:54:14] CAF EBANK6 [17:54:15] TS EBANK [17:54:16] CS DAPDATR1 [17:54:17] MASK PRIO30 [17:54:18] ..... [17:54:23] the AVEGBIT stuff is PCN 1041 [17:54:32] and yeah, seems quite likely we could more easily get a Comanche 67 with this fix in than Comanche 72 rev 0 [17:54:54] so I think they most likely changed that IBNKCALL to [17:54:55] TC IBNKCALL [17:54:56] CADR PCR984 [17:55:04] and then put the above code at the end of bank 11, with some other bank jumping code to go back [17:55:15] right [17:55:42] hopefully this is something that doesn't take 100 variations until the correct one is found [17:55:54] seems straight forward but there are still more than 1 way to do it [17:56:23] oh yes, I'm almost positive we will at least have to try dozens of variations lol [18:00:56] I said I was done, but do we know of any more changes from 67 to 72? I only got two actual changes from the GSOP section 5. And one additional GSOP only change. [18:01:25] none in section 3 at all [18:02:18] https://www.ibiblio.org/apollo/Documents/apollo_13_fsrr_minutes.pdf [18:02:27] FSRR slides are our friend :) [18:03:08] right, I always forget them [18:05:03] sounds challening. But at least I can probably be useful. [18:08:14] :D [19:44:06] indy91, in the RTCC MFD PAD section, the P37 PAD button is not clickable, is that normal? [19:46:02] ah, I forgot to remove that still being shown [19:46:10] there is no P37 PAD anymore [19:46:18] the Abort Scan Table has the same information [19:48:46] ah ok [19:50:44] also [19:51:02] in a recent commit: "TLI PAD calculation in RTCC MFD uses new functions" [19:51:08] is it more accurate now? [19:51:48] like the EMS counter being closer to zero at SIVB cutoff [19:53:59] I think I remember getting an accurate DVC for the EMS, but only when using the manual method for TLI PAD (MPT+DMT+Checkout monitor etc) [19:58:22] yep, the TLI PAD calculation now uses the accurate TLI simulation that previously was only available with the MPT [19:59:06] ok [19:59:13] and no need to have TLI on the MPT? [19:59:37] correct [19:59:47] cool [19:59:52] that was not easy to get working haha [20:00:10] those TLI functions the MPT can use are quite integrated with the MPT [20:00:32] I also saw some updates to the entry PADs [20:00:56] I while back I added the RTCC entry simulation [20:01:02] was mostly used in the deorbit targeting [20:01:13] but now also for some new parameters on the Entry PADs [20:02:21] I think the only parameters missing are the numbers for P65, a skip reentry [20:02:30] those are usually N/A [20:02:36] Apollo 11 got them [20:02:43] DL and VL numbers? [20:03:00] yep [20:03:07] right I see [20:03:12] different missions have different criteria for that I think [20:03:28] min/max [20:11:52] and I see the DKI got a revamp [20:12:51] definitely will be used for my upcoming Apollo 16 [20:14:44] I gave the DKI a bunch of new capabilities, but in a way I also took some away [20:15:17] like for the No PDI + 12 burns that have a constant radial DV [20:15:46] I could not find any reference to that actually having been a capability in the RTCC [20:15:55] so to properly target those you will now need the MPT [20:16:15] add the No PDI+12 and boost burn on the MPT [20:16:21] and then a DKI targeted burn [20:16:28] which would normally be zero [20:16:56] and then you would adjust the DV of the No PDI+12 based on that. We can work out a procedure for the input guide when you get there. [20:17:10] sure [20:17:22] sounds straight forward, just a bit more labor [20:17:37] but if it how they did it in reality then im for it [20:17:39] yeah and it's not too bad with the MPT maneuver replace feature [20:17:53] just have to have a few RTCC MFDs open :D [20:18:03] but then it's really only changing one number at a time [20:18:26] I think this is how they did it. Eventually we will get the Apollo 16 MOCR audio... [20:18:49] that mission is next, but Covid delayed things a lot. I think it's not going to be this year for that to become available. [20:19:09] ah right [20:19:18] they skipped 14 & 15? [20:19:46] well they also skipped 12 :D [20:19:55] but I guess 11 and 13 were the really interesting ones [20:20:04] true [20:20:06] they probably started the process on 16 before Covid even [20:20:17] maybe they had the 50th anniversary in mind or so, not sure [20:35:24] the launch targeting thing, that uplinks directly to the LVDC? [20:36:22] ah and theres a skylab mission ow [20:36:30] now* [20:39:39] yes, launch targeting to an object in Earth orbit [20:39:50] very preliminary testing scenario for this launch targeting [20:40:03] requires a Skylab addon [20:40:15] and the DKI can be used for targeting the rendezvous maneuvers [20:40:47] the Skylab rendezvous targeting we had in the past was based on the AGC calculations [20:40:59] but in reality they expanded the DKI to support it [20:41:56] we still don't support countdown holds [20:42:05] so an IU uplink is made sometime before launch I guess? [20:42:10] yeah [20:42:16] for the latest targeting [20:42:25] right [20:42:33] preliminary launch time was decided earlier of course [20:42:52] within a reasonable launch window the targeting can get you into the right orbit [20:43:11] including an updated launch azimuth [20:56:37] Ill have to fly it one of these days [21:05:07] good night, it's good to have you back! [10:50:12] good morning [11:28:18] hey Matt [11:28:20] nice video [11:38:42] clbkGeneric is supprisingly easy to implement. [11:43:29] how does it track the ground station? [11:47:16] the csm calls the MCC's clbkGeneric (API function, so no need to include mcc. or mccvessel.h) and passed a pointer to the vector that I used to use as the global position for earth [11:48:31] mccvessel then writes the global position vector of the "transmitting" ground station to it [11:50:51] interesting, we already used clbkGeneric for lua stuff [11:51:08] does it have to be a global message ID? [11:51:41] ah you have the update on Github [11:52:19] I don't think it has to be global, just both vessels' need to know what it is [11:52:36] s/vessels'/vessels [11:53:07] I have 0s as placeholders there right now [11:53:31] right [11:53:47] the HGA doesn't need its own MCC pointer I think [11:53:51] the Saturn class already has pMCC [11:54:01] ahh okay [11:54:13] one less function call [11:54:55] I can probably take the get earth and moon pointers out of that loop too [11:57:15] the other thing I can do now is ask MCC for the power output and gain of the station (and whether or not it's an sband station) [12:00:46] right [12:01:02] seems like a good function for this kind of communication [12:02:14] once upon a time I wanted to test clkbGeneric for communication between Saturn stages [12:02:49] needs a test if the stages are still docked, but can probably be used for that, too [12:05:06] but it seems simpler than the connector classes [12:06:36] I think we might be able to migrate away from the connector class [12:09:27] when I did vhf ranging and the rendezvous radar transponder I had to make functionality for sending and receiving data on both ends, plus you have to register the connector and then connect during initalization [12:16:11] yeah I think for simulating any kind of radio communication this is ideal [12:21:40] I think even the electrical and fluid connectors between the CSM and LM would benefit from this. it's probably way less overhead to call [12:34:56] well then, electrical connectors is exactly what Saturn stages consists of mostly [12:42:00] a docked stage Saturn 5, à la our Apollo 5 scenerio would be fun. [13:46:47] hey [13:49:40] hey Alex [13:55:14] just realised all of us are on discord as well lol [13:57:51] ever since I also joined the Discord Ryan has never shown up here again haha [13:58:19] But I quite like having this as the main developer talk chat. It's a bit more private, even if the chat logs are public [14:16:07] I feel like libera/IRC is a bit more FOSS-appropriate. discord is great for support [14:21:22] ooooo new eva feature :) [14:23:06] yeah, two astronauts with the name N. Armstrong on it instead of one [14:23:47] with some acceptable limitations I feel. CDR always exists first [14:23:53] only CDR can spawn the flag and the LVR [14:23:57] LRV* [14:24:04] exits* [14:25:55] that makes sense [14:25:56] .ask Thymo Have you automated your PR approvals because I complained too much about nobody looking at submitted PRs? :D [14:26:33] lol [14:29:17] indy91, im building your eva branch right now [14:29:36] anything to test in particular? [14:29:49] saving/loading, try to break it with exiting/entering the LM [14:29:58] ok [14:30:04] maybe there is a bug where suddenly you can't exit or enter [14:30:16] or end up spawning a few too many LEVA vessels [14:31:08] this is the kind of update that does need testing [14:34:31] hmm [14:34:48] I haven't implemented any code for backwards compatibility [14:35:15] I thought it was just a small scenario edit for old LEVAs being able to enter the LM again, but I think it's slightly more complex [14:35:36] I will definitely make a post on the forum about it [14:36:11] you have to edit two lines, add "-CDR" to the name of the astronaut [14:36:50] and also, which I didn't think about at first, change the STATE variable [14:37:20] right [14:37:31] is that just for scenarios where the EVA is already started? [14:37:42] yep, old scenarios with the "CDR" outside of the LM [14:38:01] so no mission scenarios are affected, we have an Apollo 11 before and an after EVA scenario [14:38:37] so far so good for me [14:41:34] hmm [14:42:46] ok so I had the CDR come back in the LM and then saved/reloaded [14:42:56] the LMP is still outside [14:43:14] so after reloading I cant get the CDR to go back outside [14:43:32] ah nice. Let me try that [14:43:40] and CDR status is stuck in "EVA" [14:46:38] yeah, when you exit the scenario it is CDR in PLSS and LMP in EVA [14:46:43] but when you reload it is the other way around [14:46:54] so something doesn't get saved/loaded correctly [14:51:23] right [14:59:17] ah, stupid code [14:59:27] if the CDR is outside the LM it saves in the scenario [14:59:31] EVA 1 [14:59:33] for the LMP it is [14:59:35] EVA2 1 [14:59:49] but when loading it doesn't care for the one [14:59:57] and it sees EVA in "EVA2 1" [15:00:11] so that's why it thought the CDR was outside, not the LMP [15:02:58] indy91, when you have a chance I have a question about https://github.com/orbiternassp/NASSP/issues/737 [15:03:28] sure [15:03:36] I'll quickly do the fix [15:04:01] ok [15:04:18] and I think the way I will do it is, the LM thinks there is nobody outside in old scenarios [15:05:18] you can't enter with the old CDR either, but you can then just delete the CDR [15:05:35] ah makes sense [15:09:09] seems like a clean way to do it. [15:09:37] morning! [15:09:43] hey Mike [15:12:14] n7275, btw loving the new CSM lights! [15:20:28] thanks! [15:21:55] oh. you're good with meshes. do you think you could help me with the csm running lights? [15:23:56] I want to make them not look like giant glowing cubes [15:24:24] is that the red/green/yellow ones? [15:24:30] yes [15:25:59] right they should be defined as actual lights like the LM docking lights? [15:26:14] if we just the light enclosures as a small cylinderical mesh, I can add beacons to them like the lm [15:26:47] I would love to add actual lights, but dx9 has a hardware limitation of 8 maximum lights [15:26:58] tight budget to work with [15:28:32] right. I can definitely come up with a light mesh [15:28:50] ok, pushed the fix [15:30:25] ok I will try it [15:31:53] there wasn't really a good solution for old scenarios, they will require scenario editing in any case now [15:40:59] all is good [15:44:11] no other issues found on my end, PR approved [15:49:25] yeah, should be good now [15:49:51] merged and update in the forum posted [15:51:24] ok, to issue #737 [15:53:20] AlexB_88, the VC uses some bitmaps that only get loaded if you have looked at the 2D panel once [15:53:25] like the DV light on the EMS [15:53:29] SRF_EMS_LIGHTS [15:53:38] that gets used in the VC [15:53:53] but is loaded in InitPanel, which does not get called from the VC loading function [15:54:36] ah damn [15:54:44] ooh [15:54:47] you made dds files [15:54:58] I made a VC version of that, but I dont think I referenced the right one for the EMS [15:54:59] there is a [15:55:00] ems_lights.dds [15:55:01] files [15:55:03] yeah [15:55:05] ah then it's easy [15:55:19] just needs to load SRF_VC_EMS_LIGHTS [15:55:24] yeah [15:55:25] which already exists [15:55:31] is that the only one? [15:56:22] I feel like there were more [15:56:59] wasn't there on in the LM I saw... [15:57:38] maybe not, all the srf in there have VC in the name [15:58:04] its the SPS and 0.05 G light that are affected [15:58:35] I accidently referenced SRF_EMS_LIGHTS for those in clbkVCRedrawEvent [15:58:56] easy fix as you said [15:59:13] yeah [15:59:17] maybe it was just those [16:00:03] as long as everything in there uses the SRF_VC then I think there shouldn't be more issues [16:01:31] maybe it was just that I noticed the missing 0.05g light and SPS Thrust light on separate instances [16:20:03] made a PR with the fix [16:25:43] merged and one less issue on Github [16:26:44] 2 less :D [16:26:54] 693 was also the same thing [16:28:30] right, and I fixed the Apollo 7 issue a while ago, so, lots of issues fixed [16:28:49] oh about the Apollo 7 thing. That was caused by a thing I changed regarding the first timestep when you load a scenario. [16:29:07] Would you believe it, our AGCs lost 0.01 seconds every time you loaded a scenario [16:29:32] that's why the AGC clocks were off by a random amount, up to 0.5 seconds for me, after 100 hours [16:30:19] ah really [16:30:23] There is one notorious NASSP user in Discord who reloads the scenario every time he does a small mistake. So his AGC clock was off by up to 1.5 seconds at PDI [16:30:52] and that's when I thought, no, this isn't a random frame rate related issue that is tricky to fix, this was something else. [16:30:54] I definetly dont remember having that issue before, so it was caused by the running systems on 1st timestep thing? [16:31:00] yeah [16:31:14] If you fly a whole mission without saving/loading you would have no clock error [16:31:19] right [16:31:27] I do save/reload quite a bit [16:31:38] and it isn't actually noticable until it gets up to 0.5-1 seconds [16:31:41] that would be bad if you want a pinpoint landing I think [16:31:47] indeed [16:32:02] 1 second, state vector in lunar orbit would be 1650 meters off [16:32:08] all downrange [16:32:27] we also started noticing it more when I implemented a better method for uplinking clock time increments [16:32:34] that being said I think we have new tools in the RTCC MFD to update the clock? [16:32:36] and I added a button to compare the AGC with RTCC time [16:32:40] yeah [16:33:46] bunch of new things in the RTCC I have to get up to speed on [16:33:51] I think my new feature is going to need some further considerations for non-ground tracking mode [16:35:16] I feel like sending full Site Configuration Messages might be a bit out of scope [16:38:43] full site configuration? What all had you in mind to send? Right now it's just the CSM HGA getting a vector from the MCC [16:40:03] indy91, what exact cue card did you want to use for testing again? [16:40:11] DAP Config Card [16:40:16] ah right [16:40:50] DAP Monitor Card is the correct name I think [16:41:50] we have a few versions of it [16:44:14] indy91, the network controller sends each station a SCM which contains a table of times, at which the station should be: acquiring the spacecraft, tx or rx, lbr/hbr, etc [16:44:16] not sure if there is a complete, clean version, so maybe the texture will eventually need refinement. I just need something with the right size [16:45:24] ah, that's a manual message. There were also automated AOS messages to the ground stations [16:45:29] based on the ephemeris [16:49:16] ok ill see what I can do, just firing up Blender now [16:49:25] trying to find the best way to allow this "active station" feature to work when flying in "RTCC mode" [16:51:59] what is "RTCC mode"? [16:53:01] do you mean if the MCC vessel even exists in the simulation? [16:53:07] Apollo 12+ or with ground tracking disabled [16:53:08] yes [16:53:16] I think the current philosophy is that it should always exist, we can add the MCC to those scenarios [16:53:42] ahh. okay. that would do it [16:53:58] when you open the RTCC MFD the MCC vessel also gets created [16:54:08] because the RTCC stores its data there [16:54:54] okay. I should probably have known that by now... [16:55:50] it just doesn't exist right now on Apollo 12+ before you open the MFD for the first time [16:57:10] but an additional problem is, you can disable ground tracking in the CAPCOM menu [16:57:22] and then the calculations for the active station are not done, I think [16:57:29] correct [17:01:40] maybe calculate the local position of the active ground station where it is done right now, with ground tracking active [17:02:01] and then in any case, even with that disabled, that (sometimes null) vector gets converted to global and return to the HGA? [17:02:16] Then it would point at the center of the Earth with ground tracking disabled [17:03:09] so some function called from clbkGeneric [17:04:25] so deactivating ground tracking would actually disable MSFN entirely :D [17:15:06] the other option would be manually choosing ground stations [17:17:38] or maybe we just hide the messages when ground tracking is disabled [17:19:58] yeah, it would make sense to have a MSFN that always operates [17:20:23] indy91, https://www.dropbox.com/s/i0lhrhiac9wwpcf/Screenshot%202022-08-06%2013.12.35.png?dl=0 [17:20:44] thats from the Apollo 14 CSM cue cards [17:20:50] we do have better looking ones I believe [17:23:39] https://readux.io/volume/sc97f/page/sc97f_015a.tif [17:25:40] ah yeah thats better [18:07:57] oh those are going to be nice to have [18:33:15] my plan is to have clickspots on the velcro patches [18:33:32] and when there are multiple cue cards in one place you cycle through them by clicking [18:35:13] and I want to do it not by hiding the mesh normally but by dynamically loading it in when it's needed [18:35:20] I like it [18:37:23] I think the solution with making it part of the VC mesh, but hiding it, would only have worked when it's one cue card in one spot always [18:37:37] or maybe even if there are different texture, but the same cue card shape (mesh) [18:37:43] but I don't think that's always the case [18:38:45] so it has to be a completely separate mesh [18:44:30] should have something ready shortly [18:47:06] any pictures of the CSM panel with the DAP monitor card showing? [18:47:47] for now I am using the diagram in the Apollo 14 cue cards document [18:48:01] so just under and to the right of FDAI 2 [18:50:14] we have video of a MCC-2 with it in place, need to search for photos [18:51:06] do I understand correct that you make it a separate mesh, but the coordinates match up with the VC? [18:51:21] that way I don't need to use any offset in AddMesh? [18:51:26] yes [18:51:42] you can use the same offset as the VC itself [18:51:50] right [18:52:09] ok during MCC-2 Apollo 12 had other cue cards in place, but not that one [18:52:30] I think its just above the DSKY digits [18:53:04] yeah, where we have the velcro already [18:55:48] https://youtu.be/ezckueX38u8?t=2350 [18:55:57] but you can't really see much, bad quality [18:56:02] but it's there, above the DSKY [19:01:56] https://www.flickr.com/photos/projectapolloarchive/21672887342/in/album-72157659052908231/ [19:02:06] there it is to the right of the DSKY, slightly different version [19:02:12] we have that one, too, can't find it right now... [19:09:08] https://www.dropbox.com/s/mjehoet87xsap20/Screenshot%202022-08-06%2015.07.48.png?dl=0 [19:09:12] hows that? [19:09:44] thats the view in blender [19:10:07] I just made a flat simple mesh and added a texture to it [19:10:38] that's where I already failed :D [19:11:11] maybe a bit to the left? So that it's centered on the velcro? [19:11:32] and in the long term we might want to get rid of the date on it, our CSM doesn't have a favourite mission ;) [19:12:15] ok [19:12:36] oh lol [19:12:47] how about I give you a photo from our own wiki [19:12:49] https://nassp.space/images/8/89/FDAI.gif [19:13:05] not necessarily representative though [19:13:38] I think centered on the velcro is good enough [19:14:25] that one almost looks like a sticker [19:14:34] yeah [19:23:20] and I would like to make it a oapiVCSetAreaClickmode_Quadrilateral [19:23:34] is generating the coordinates for that simple? [19:31:57] yeah I can figure them out in blender [19:32:12] I guess it would be the 4 corners of the velcro? [19:39:20] indy91, https://www.dropbox.com/s/rntbd4jg3ln69im/CueCardDAP.zip?dl=0 [19:39:51] just unzip into the main orbiter directoy [19:40:20] ou just need to add the code to load the mesh [19:40:23] you* [19:40:38] Im sure you'll figure out the system for that [19:41:08] yeah, the corners of the velcro [19:41:12] thanks so much! [19:41:29] let me know if it needs adjustments, I can make it bigger smaller or move it if needed [19:42:26] anytime [19:56:31] indy91, https://www.dropbox.com/s/n2gfrwulgibbxhw/CCquadclick.txt?dl=0 [19:56:57] thats the coordinates for the DAP monitor card velcro [19:57:00] got them, great [19:57:46] do I have to switch y and z coordinates on those? [19:57:53] already done [19:57:56] ah thanks [19:58:16] we both know the fun of the left handed coordinate systems... [19:58:41] yep haha [20:05:33] oh and im sure you know but you have to add the view offset to each of those 4 vectors [20:08:34] I know that but I managed to forget doing that :D [20:13:49] hehe [20:15:28] back in a few [20:40:25] how does the card it look for you? [20:40:54] card look* [20:41:10] haven't managed to see it in the sim yet :D [20:46:36] it looked pretty good on mine, but then again I have a UHD monitor [20:46:50] hopefully it comes out well on lower resolutions too [20:47:28] just have to zoom in enough [20:47:41] yeah true [20:52:26] the simulator version of squinting your eyes to try to read something small :D [20:53:22] that's when I abandoned trying to put the cue cards on the 2D panel [20:53:28] no zooming there [20:55:38] squinting the eyes to a level not possible :D [20:59:26] AlexB_88, mesh offset gets a bit complicated with a dynamically loaded and not hidden mesh [21:01:55] hmm [21:02:07] what about load them all and use visibility flags? [21:02:32] tempting [21:03:49] or maybe it works if I do GetMeshOffset on the VC mesh [21:05:00] oh hello [21:05:57] https://i.imgur.com/prDIs2l.png [21:06:14] and I can cycle it on and off [21:11:04] nice [21:11:13] and the clickspot works good? [21:12:23] yes [21:13:10] great [21:13:38] so shifting CG during burns or so should be fine, that happens automatically [21:13:48] not sure if this mesh survives staging though [21:14:31] but that is all detail work, lots of work needed before this becomes a mature feature [21:16:43] I can keep adding the rest of the cards to that same zip file [21:17:16] and the click coordinates to that same file as well which ill move into the zip [21:17:26] sounds good [21:17:42] there are cue cards they would put above the DSKY lights [21:17:53] I wonder if you would have been able to see them through the card... [21:17:56] yeah [21:20:54] Ryan complains about the date on the cue card [21:29:06] with that initial success, thanks for the help and good night! [22:12:29] o9%41.3.95.}:‑)3.%^_^^_(◍•ᴗ•◍)❤^(^(づ。◕‿‿◕。)づ^⊂(・▽・⊂)ï¼¼(^o^)/⊂(•‿•⊂ )*.✧⊂(◉‿◉)つ༼ つ ◕‿◕ ༽つლ(◕ω◕ლ)⊂(•‿•⊂ )*.✧\(^o^)/\(^o^)ಡ ͜ ʖ ಡ◉‿◉<( ̄︶ ̄)>ᕦ( ⊡ 益 ⊡ )ᕤ୧(ï¼¾ 〰 ï¼¾)୨୧( ಠ Д ಠ )୨ᕦ༼✩ل͜✩༽ᕤ(=^・ェ・^=)(´(ェ)`/ᐠ。ꞈ。ᐟ\U ´꓃ ` U(◠ᴥ◕(づ ̄ ³ ̄)づʋ(◠ᴥ◕ʋ)(・(ェ)・)…ᘠ[00:11:42] wtf did I do [11:22:43] n7275, do I need to ban you as a spam bot :D [11:34:58] haha [11:36:33] my phone has one of those fancy fingerprint unlock buttons, which means if I pick it up wrong, sometimes I unlock it and apparently mash my hand all over the keyboard. [11:36:47] I hope I haven't sent any work emails like that... [11:57:09] do you think nasspdefs.h is a good spot to define message IDs? [12:13:48] A separate header file would be good I think [12:14:05] and that is the central place where all definitions like that go [12:27:34] I like that idea better [12:48:14] good morning [12:51:53] hey Alex [13:43:27] hello Alex [14:36:16] AlexB_88, to the surprise of noone, ClearMeshes is getting in the way [14:36:49] was that something we could only get rid of with docked stages or were we in the process of solving it just with the ShiftCG, I forgot... [14:56:27] ah [14:58:25] yeah I had made a custom ClearMeshes I think [14:59:11] that only deletes Meshes from index 1 onward [14:59:24] since 0 is used by the VC [14:59:40] and we lose animations if the VC mesh is deleted [15:00:14] but yeah we switched to using ShiftCG at staging [15:00:43] so I wonder if all those ClearMeshes are still needed [15:01:41] well I think it would still be a hell of a job to remove them [15:02:30] yeah, would be great to be rid of them [15:02:46] right now, because the cue card meshes are optional, I need to add some logic to keep track of them [15:02:58] they are getting deleted by ClearMeshes at e.g. staging, but then re-added [15:03:48] I'll attempt a bit of a meshes cleanup with this, too [15:04:04] not starting a whole project, but a slight reduction of duplicate code [15:04:29] right [15:18:04] morning! [15:27:38] hey Mike [15:29:03] https://i.imgur.com/KtSzaOx.png [15:29:15] making some progres on fleshing out the GUI for the rope reader :) [15:29:42] very nice! [15:30:29] is that a real-time deassembly in the center? [15:31:15] or disassembly [15:32:16] and the stuff like "Sundance 292" is user input so the data gets saved with the correct name or so? [15:32:40] or does that also get automatically detected, which is possible I guess :D [15:33:02] it's real-time very rough disassembly. no interpretive or anything like that, only smart enough to track EXTEND [15:33:14] and the stuff at the top is all automatically detected based off of the banksums [15:33:29] ah very nice, with the database of banksums we have [15:33:38] https://github.com/thewonderidiot/lachesis/blob/main/gui/ropes.json [15:33:46] that also means you instantly know that the rope reading worked [15:33:48] I filled in every module I knew banksums for there [15:33:49] yup! [15:33:58] at least for the ones with banksums we have [15:35:38] that's going to be spectacularly unspectacular. "Wait, that was it?" [15:35:53] hahahaha [15:35:59] yeah like Aurora 88 [15:36:05] which ironically might be the first rope I read [15:36:32] the other thing the middle panel is smart about is identifying potential problems [15:36:34] https://i.imgur.com/9VjGff8.png [15:36:42] like here, it's highlighting pariy errors in red [15:37:15] that's not actually a problem because those are after the banksum... but I don't have it processing the banksums quite yet so it's expected for now [15:40:36] what even happens on a TC 0 [15:41:02] it's valid sometimes [15:41:06] but that's a TC A [15:41:14] which more often than not leads to a TC trap [15:42:10] yeah, I can imagine that with A [16:11:25] indy91, I see a new REFSMMAT code for Apollo 12+ TEI [16:11:35] in RTE digitals [16:11:42] haha yeah, finally that type of REFSMMAT can be calculated [16:11:49] ah [16:11:58] so its a perfect 0,0,0 now? [16:12:03] or 180,0,0 [16:12:11] 180,0,0 [16:12:16] nice [16:21:53] is it possible to figure out RTGO using the MCC displays for a lunar entry that is dependent on one or more prior maneuvers on the MPT? [16:22:26] for example the RTGO written on the TEI pad [16:23:55] not in the correct way with the correct displays [16:24:07] you should be able to calculate an Entry PAD if the splashdown coordinates have been saved [16:26:07] hmm, I tried that from TLC but it gives 0 for RTGO [16:26:31] then again I do have 2 maneuvers on the MPT, maybe a bit optimistic :D [16:26:45] Ill try TEI [16:26:45] and you calculated the RTED solution and saved the coordinates with the SPL button or whatever it is? [16:26:56] yes [16:27:10] in MPT mode the state vector given to the Entry PAD calculation should be the cutoff vector of the last maneuver on the MPT [16:27:57] potentially there is a SOI issue [16:28:02] otherwise it should work [16:52:59] but then you are the one who is finding these bugs usually... [17:03:12] AlexB_88, you said you had two maneuvers on the MPT, was that TEI and an MCC? And does the Entry PAD work with just the TEI on the MPT as you wanted to test? [17:06:40] ah I see it not working [17:06:43] I'll try to debug [17:27:58] ah just a stupid little bug [17:28:13] one [17:28:14] ! [17:28:16] too much [17:34:10] yeah I tried it with just TEI and same issue [17:37:00] btw do the other PADs have MPT compatibility now? Like the maneuver PAD for example...does it use the last maneuver on the MPT? [17:37:53] Lunar Entry PAD is MPT compatible, it just has this little bug of using a current SV anyway despite it having gotten the burnout SV from the last MPT maneuver :D [17:38:05] Maneuver PAD, no, not compatible [17:38:10] right [17:38:33] ah well, partially [17:38:56] Maneuver PAD calculation gets a SV at TIG [17:39:34] so if you have a maneuver on the MPT and then you got the TIG and DV on the Maneuver PAD as usual then it will take the trajectory with maneuvers at TIG into account [17:39:47] but it won't get the maneuver from the MPT itself [17:39:53] ah [17:40:33] so you can just enter the TIG and DV of the desired burn? [17:40:41] yeah, you could do it that way [17:41:13] would it be feasible to put a button to "pull" a desired burn from the MPT? [17:41:28] maybe with a box where you just enter the number? [17:42:03] I guess that makes me look a bit lazy :D [17:43:16] definitely possible [17:43:32] not all maneuver on the MPT are External DV maneuvers though [17:43:36] but there could be a check on that [17:43:46] like, you wouldn't pull the TLI maneuver onto the Maneuver :D [17:43:49] Maneuver PAD* [17:44:28] right [17:45:44] oh and maybe this is asking much but an option to use another REFSMMAT then CUR if desired [17:49:05] that way building multiple abort PADs in the future referencing different maneuvers/REFSMMATs would be easier I think [17:49:25] but of course I guess the most realistic way is to look at the different MCC displays [17:51:06] that's definitely possible [17:51:44] the whole REFSMMAT table is separate from the MPT, so no need to have that enabled to use different REFSMMATs [17:53:09] right [17:53:41] you did mean different REFSMMATs for the Maneuver PAD, right? [17:53:56] I guess also Entry PAD would be useful [17:54:06] yeah [17:54:12] maneuver PAD [17:54:18] any PAD with an attitude on it really [17:56:42] I had opened a PR for an Apollo 9 SPS-7 fix, just pushed the fix for the Entry PAD, too [17:56:43] https://github.com/orbiternassp/NASSP/pull/817 [17:58:12] the two updates are put together there [18:04:55] thanks, ill give it a test [18:06:04] more things working :D https://i.imgur.com/dak1WHz.png [18:07:10] Bugger [18:07:29] as the Brits would say [18:07:33] hehehe [18:26:38] indy91, works beautifully [18:27:46] to be sure I placed to maneuvers on the MPT, and during TLC still in earth SOI [18:27:52] two* [18:28:46] great [18:34:30] so the PR gets a positive review? :D [18:36:31] done! [18:39:02] I imagine you were waiting all day to get that other thing merged weren't you? :P [18:42:30] like a 0 subscriber Youtuber waiting for their first like on a video [18:42:49] well it was mostly TurryBoeing waiting for this update to continue his Apollo 9 training :D [18:42:58] haha [18:44:05] at this rate Apollo 9 SPS-7 calculation has been failing about every other mission... [18:58:38] I think I will make a few updates to the input guide [19:01:03] hmm, the one on my PC is dated July 2nd 2021, while the one on github is October 2020...looks like I had a newer version I forgot to commit [19:04:48] ah that's why it's so outdated [19:05:40] yeah the one on my PC references the newer RTE stuff, like the abort scan table [19:06:10] I will have to do the DKI next' [19:35:17] do we have the TeX code on GitHub for that? [19:54:14] you mean for the RTCC input guide? [21:35:24] night! [16:19:35] morning! [16:24:57] hey guys [16:26:15] hey [16:29:20] I'm almost done with the BOM for the rope reader board... just need to figure out what I want to specify as the defaults for the tuning resistors [16:29:36] but then it's just re-re-re-re-checking everything and then ordering the board [16:33:56] don't forget to recheck everything [16:42:07] indy91, I need your opinion. I'm making a list of message IDs and parameter IDs. would you prefer a tree-like structure where ever messageID has sub-list of parameters, or more grid-like where some (messageID, parameter) exists for all possible combinations, but wont all necessarily have any meaning [16:47:40] do you mean something like, the message ID is only addressing a specific subsystem or so and then the parameters contain the more detailed type of message? [16:48:53] as opposed to, the message ID already being the fully detailed type of message [16:52:23] i think that's what I mean [16:52:57] messageID is going to be very similar to connector type [16:53:37] but maybe a bit more generalized [16:54:30] I think a good advantage of having it more like the connectors is that clbkGeneric is really generic [16:54:40] so it's something that would affect all vessels etc [16:54:53] so it's probably better to not have too many of those [16:56:13] I will build some notion of get vs send into these as well, since the actual data is passed by pointer [19:14:13] indy91, do we have anything by way of Network-related MOCR displays? [19:31:35] not directly. There are e.g. displays with station AOS/LOS times [20:23:18] those are very helpful [20:28:34] requires initialized MPT and trajectory. There were basically two displays. Next Station Contacts to show the current and next 5 stations that will acquire [20:28:53] that's a real-time updated display [20:29:19] and then Predicted Site Acquition where you can input a timespan and it gives AOS/LOS times, no dynamic update [21:15:53] night!