[13:11:19] NASSP Logging has been started by n7275 [13:11:21] hey Thymo [13:25:23] Hey [13:33:09] http://mwhume.space/Files/NASSP_Stuff/2022-04-05.log [13:33:52] http://mwhume.space/Files/NASSP_Stuff/2022-04-06.log [13:46:59] here's somd logs for you. the times are all UTC-4 [13:55:34] Thanks! [13:58:17] Panels are all installed and got some modifications done to the electrical panel. On the 20th a lineman will swing by to switch us over to three phase power and then a day or two later the PV guy will finalize the connection to the panel. [13:59:03] nice [13:59:55] Got a bunch of CT clamps on the wires to do some nice data plotting. Can't wait. [14:02:41] oooo cool. how much power are your panels rated for? [14:12:29] 13 panels doing 400W so 5200W maximum [14:21:19] wow, that's pretty good [14:44:12] as soon as I live in a building that I own, I want to hook up a bunch of data acquisition and loging functionality [14:54:11] hey [15:50:10] hey Nik [16:28:34] morning! [16:45:05] hey Mike [16:45:27] what's up? [16:46:48] got something working with the 2D panel I think. But now I have to add panel areas for each switch where previously it only had areas for each switch row. So that is going to take a while [16:47:29] ooo [16:49:01] and each type of switch needs a change applied to it [16:49:20] oh boy [16:49:24] I've kept it the old structure intact for now, so everything is still working [16:49:56] I would say just with toggle switches and three position switches there is already a lot of the CSM main panel covered [16:50:58] hopefully it has a good performance impact [16:56:15] yeah I would really hope so after how much work it's going to be haha [16:57:36] if I compare the main panel to all the other panels then I would say yes, it's going to be much better [16:57:46] but, I can't apply to type of improvement to e.g. the FDAI [16:58:21] if it's the FDAI that is causing most of the problems and all the other redraws are not so significant that would be annoying [16:59:45] apply this* [17:11:02] so I did some literal smoke testing on my test rope reader last night [17:11:17] intentional? [17:11:22] indeed! [17:11:45] so far it's held up completely fine to probably tens of thousands of read cycles (based on how many times I clicked the button) [17:12:14] but to test out the fuses last night I wired it up such that the reset driver would get stuck on, driving a constant 450mA into the rope [17:12:53] and it let out a tiny puff of smoke and made an open circuit what felt like immediately when I pushed turn on the reset driver -- probably in the 10s of milliseconds order of magnitude :D [17:13:46] according to our thermal engineers at work it would take probably 10+ seconds for a stuck driver to heat up the wiring inside the rope enough to damage it, so this is very definitely a fast enough response to protect the hardware [17:14:28] so if you get to the point of reading an actual rope, you have about 10 seconds to stop the process if you see something going wrong [17:16:23] or is that what you meant with 10s of milliseconds, that it open circuited on its own? [17:16:39] the fuse blew within 10s of milliseconds, so no human intervention required [17:16:45] I see [17:17:04] I'm sure all museums who won't give you ropes anyway will find that reassuring :D [17:17:56] n7275: This is about the earliest in the simulation that I can trigger a save. There are some differences. https://pastebin.com/3x30UWzq [17:21:33] I figure everything I can do to maybe convince a tiny bit more helps :) [17:22:28] and also helps me with the private collectors who have tentatively agreed to let me read their ropes but want me to demonstrate safety first [17:22:29] yeah definitely, I was thinking about it yesterday what one could do [17:23:08] "is the software not worth preserving as much as the hardware?" is what always goes through my mind [17:24:12] I would argue it's even more -- but obviously I am biased :D [17:24:44] and it only takes getting the rope for a few minutes and one upload to the Internet to have it preserved [17:24:49] quite cost effective [17:26:01] But that was already the case with the real AGC. Of course the logistics are going to be much nicer with the rope reader. [17:26:06] I'm probably going to end up putting together a slideshow about why it's safe (overvoltage/undervoltage protection, overcurrent protection, a dozen+ fuses spread throughout the design, mechanical dimensions taken directly from AGC engineering drawings, replica pins made by Samtec exactly to the NASA spec, etc...) [17:26:25] I can confidently say that the fuses and things in the rope reader make it even safer than using the real AGC :P [17:26:33] but yeah logistics are the real winner here [17:29:57] Which museums do we know have ropes? [17:30:10] Does the Smithsonian have any Skylab ropes for sure? [17:30:22] I actually don't know what they have [17:30:42] I'm not sure if there are any 100% known confirmed ropes in museums that we still need [17:30:53] Block II ropes at least [17:32:41] yeah there is really 3 steps to it [17:32:55] Where are the CMs, do they still have the AGCs, do the AGCs still have the ropes [17:33:25] and having somebody get inside one, remove the panel covering the AGC, and then remove the ropes is a very big ask [17:33:56] if the AGCs and their ropes are still inside the CMs, which is very much up for debate [17:35:11] in some cases the museums don't "own" the CMs [17:35:23] just lent on a temporary or permanent basis [17:35:25] yeah mostly they are on loan from the smithsonian [17:35:37] so they won't necessarily have people themselves who would go inside [17:36:04] Ideal time would be CM back at the Smithsonian for restoring it in some way [17:36:15] yeah [17:36:26] If there is any good time for removing something temporarily, that would be it [17:38:12] But yeah, once the rope reader is operational we will have to make a big push on this topic, lots of emails to be written :D [17:38:28] If there is any hope of finding Skylark, that will be it [17:38:31] for sure [17:38:58] and if my current plans pan out, we'll be able to say that it has already read 10 modules from private collectors [17:39:20] or 11 or 12 actually [17:39:36] yeah at least 12 [17:39:39] that's more than I thought [17:39:47] and not one Skylark? :( [17:40:22] or were there some where it wasn't known [17:40:50] Sundance (from Don, for testing), Aurora 88 (three modules), Comanche 67 (six modules), LM131 rev 1 (one module), Comanche 72 (just rev 0 of one module, the one that was taken up to rev 3 for flight) [17:41:50] one giant leap for Comanche [17:42:27] that will be very nice [17:42:29] yeah, still have never found one skylark module. there aren't any unknowns at this point -- we know pretty much all of the part numbers except for a couple of murky ones in the weird middle 2003960 configuration [17:42:31] yeah for sure [17:42:52] if we get Comanche 67 and a Comanche 72 module, I'd say Comanche 72 reconstruction is extremely likely to be possible [17:43:40] yeah [17:43:48] we have done more difficult things [17:44:09] ... I say that now before all the hacky weird stuff in 72 becomes known [17:44:14] hehehehe yeah [17:50:51] lots of work still to be done though! [17:51:00] it's probably still at least a few months out [17:54:36] Thymo, does that load correctly (with the right temperatures) when the updater runs? [17:57:19] This is no updater yet. This is just me calling SaveScenario at the start of the first timestep and seeing what the differences are. As I said the scenario needs to be written back so that it doens't need to be upgraded each time you load it [17:57:44] I was hoping they'd be pretty much identical. [17:58:14] But the spacecraft will get moved slightly and you can't really preserve the description easily [18:00:45] hmm [18:05:54] Perhaps we should just take a completely different approach and only do the check in the scenario as I already do and let the PA Configurator scan the Scenarios dir for outdated scenarios and ask the user if he wants to update [18:39:46] Oh sweet [18:40:01] "Apollo Guidance Computer" is now a recognised syntax in Github search [18:40:16] Including syntax highlighting :D [19:03:03] oh wow [19:03:12] who did that? [19:04:32] I like the approch of doing it through PA configurator [19:41:48] roughly halfway done with the switches on panel 1-3 [19:42:06] I can't really tell if performance has improved because it has been quite random for me [19:42:20] or rather, roughly stable framerate at two different levels [19:42:41] 45 and 75 fps maybe. And now it's more like 50 and 80. But very difficult to tell [19:44:30] I hope I can see a noticable difference once all the switches are done. Meter would also help of course but some of them are a bit more complicated. [19:44:39] Meters* [19:51:33] Hmm is there even a way to run something when the launchpad starts? [19:51:57] There's launcpad item, but that only gets called when you open the menu in the extra tab [19:54:03] Unless everything gets done in a DLL init callback I don't really see a way yet [20:06:33] its been a long time since I read that part of the API reference [20:13:16] I'm reading WIN32API stuff now. Need to create a dialog. [20:13:20] I hate this. [20:13:29] Complicated 80s crap [20:14:03] Only thing I've managed so far is to freeze the launchpad [20:15:25] ugh that's no fun [20:16:29] There are things that make it a lot easier. MFC would be good. [20:16:36] Of course Orbiter doesn't use it [20:52:00] night! [21:23:06] Orbiter is going to need a major launchpad UI overhaul if it ever goes cross-platform [14:13:49] Just tested positive for COVID :/ [16:28:05] hey [16:28:28] Thymo, oh no, I hope you are feeling good [16:30:25] Just coughing a lot. Too be honest I'm probably over the worst of it already. I've been like this all week, except for being a bit tired on tuesday. Kept testing negative until today though. [16:31:06] Or at least I hope this is the worst it gets. [16:32:04] I'm just glad I'm getting it now and not last week while finishing my thesis. [16:35:18] yeah could have come at a worse time [16:35:29] the coughing is still the problem for my grandma [16:36:15] a few weeks after Covid that is [16:36:27] otherwise she went through it fairly well [16:37:04] should be easier for you hopefully, she is 91 [16:46:28] Glad to hear she got through it without too much trouble. I'm sure I'll be fine with 70 laps less around the sun. :) [16:55:35] ok I have converted basically all switches on CSM panels 1-3 so that they aren't redrawn every timestep. I find it hard to judge what the performance gain is, that main panel has always been quite random for me. [16:55:42] Maybe like 10 fps better which is already nice [16:56:23] none of the meters or so changed yet [16:57:29] the DSKY seems to be bad for performance, as are the FDAIs, but I guess that was expected [17:09:21] I know someone with the perfect machine to test performance improvements on [17:18:01] one problem with this system is our special J-type mission panels [17:18:13] the bitmaps for the panel backgrounds are right now drawn onto the panel [17:18:17] followed by the switches [17:23:01] a very old Delta Glider version seems to have solved that by loading the panel background bitmap and then if it was the scramjet version of the DG, manipulate the bitmap to show the scramjet instruments, before it gets given to Orbiter as panel background [17:42:42] morning! [17:42:50] Hey Mike [19:17:27] n7275: I've adjusted the times to UTC and added your logs to the webserver. The log for the sixth doesn't get recognised as ASCII though. Could you check what is up with that? [19:17:50] File tells me it's data. xxd doesn't make me much wiser either. [19:23:44] Looks like this was the issue: https://dpaste.com/FSY7PNP6W [21:01:31] well that's odd [21:02:43] Yeah it was quite a challenge to fix, tried all kinds of commands I never heard of. [21:03:17] In the end it was a copy and then use echo to overwrite it. [21:03:38] I did the timezone fix using awk. That was a nice exercise. [21:06:43] I need to learn awk at some point [21:07:08] so it was those 0x15 characters? [21:08:00] I'm logging using znc I bet there's some options to make the log character set more friendly [21:19:55] not 0x15 haha. 0x2 and 0xF [21:25:51] so weird. I just copied them all over using cp [21:43:56] Yeah dunno. The one from the fifth was fine.