-
Notifications
You must be signed in to change notification settings - Fork 7.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Check continuity on O2 cryogenic tanks before allowing stir #3
Comments
i think this issue should be closed because we can't reproduce it |
Does it happens only with translunar coast (sol-3-a), or any moon coasting? It may be a problem with the moon. Just trying to narrow down the issue. |
Have you tried turning it off and on again? |
This is fixed in Apollo 14. |
This is a hardware problem. I suggest a wontfix and close. http://history.nasa.gov/SP-4029/Apollo_13a_Summary.htm In other words: "What was that gauge reading before you hit the switch?" |
@adampats Hey, don't tell me how to fly the CM, all right? They brought me in here to do a job, they asked me to stir the tanks, and I stirred the tanks! |
As a temporary solution, you could try gently rolling the CM/LAM to agitate the O2. You may need to do it on the X and Y axis to get optimal agitation. |
@SilverWingedSeraph could you provide a screen shot of the error I should expect to see during repro? |
Let's work the problem people. |
@chrislgarry It looks a little something like this: |
Which version of Apollo are you running? I suggest upgrading to Apollo 12 |
Not specifically for this issue, but maybe we should consider trimming down. I'm pretty sure we can automate this, eliminating both meatbags and O2 tanks from the final implementation. |
Have you tried migrating your project to jQuery? |
Many bug fixes were addressed in Apollo 18 mission software, until the bugs infected the astronauts. |
It works for me |
So, I think it might be a hardware issue. Have you tried taking the tanks out and putting them back in again? Maybe that will fix it. |
@atpage Savage |
We're going to need a label for good first bug, agreed? |
@stkrzysiak It's got to be a hardware tag if what @atpage said is true. |
we have tried converting to node. heres a mockup. |
Which exactly Universe do you use when face this bug? |
Did you try uninstalling the drivers then reinstalling them? |
Looks like there could be an ID10T error, along with some memory leaks. |
Well, can I just update the firmware to fix this issue? Or do I have to take my Apollo to local NASA-spacecraft dealer? Really frustrating! |
This software has reached end of life and is no longer receiving security updates. NASA strongly recommends that you migrate to a supported version. Unfortunately no such version exists at this time. |
Ok I'm in a real pickle here, after you experience this issue apparently you can't simply reboot to fix it. Does anyone have a good workaround? Also my CO2 is getting pretty high, please answer quickly this is a production issue for me. |
It's not a bug, it's a feature. |
Well, I run the unit tests and it says 0 errors... |
Did you try SCE to AUX? |
You forgot to import apollo_11.cms... |
let me check it out Regards, Dominic A. Imbuga * Skype:Dominic-imbuga_+254 715 180 530 | +254 734 983 442_ _" _Science and technology revolutionize our lives, but memory, tradition On Mon, Jul 18, 2016 at 9:48 PM, Victor Otieno [email protected]
|
🚫 USER ERROR 🚫 |
I just solved the issue. Here's how, have a listen! ▶ 🔘──────── 00:21 |
I suggest assigning Stanley Kubrick to fix this issue. |
@khash We cannot upgrade simply because by our 60's semver rules the V12 contains "breaking" changes. |
This never would have happened when Steve Jobs was alive. |
And that's why we should use docker, could have reproduced the issue easily. |
works on my machine |
You guys are trying to solve an issue which doesn't exist in future. So, let's stop being geeky and go back to humour, ehh? |
Unless someone can point to the specific user story in the functional design document that proves this is not working as intended, this should be considered a billable change request. Please submit this to the internal review board for discussion at next month's meeting. |
if we split the tank and stirrer into separate micro-services and implement some sort of ESB, then at least we can deal with faults in isolation. I highly recommend [flavour of the day] hosting service, in my experience they have been A1 and their 24hr support is awesome. |
There is a plugin for jQuery that fixes it. Google4it. |
And that's why we have not sent anyone to the moon for 47 years! Please use upcoming Android O which comes with blazing vibration support for stirring (android.os.Vibrator.vibrate()) |
I think it's time we re-write this node.js code in golang. |
Why hasn't anybody submitted a PR to fix this issue yet? |
Who ? |
This is just like that time you complained that the autopilot's "hold altitude" function caused a 200 foot per minute descent. No matter how hard I try, I have yet to successfully reproduce this problem on the ground! |
Don't understand why this was tagged "Won't fix" and "Humour". Seems to me you don't appreciate the seriousness of this report. |
... it worked on my moon ... |
that's no moon..... |
Client decided to upgrade from legacy 60s tech stack alternatives like Soyuz and is now implementing https://github.com/r-spacex/SpaceX-API with at least one success case in production. Gotta say - it's about time. |
It works on my machine |
A customer has had a fairly serious problem with stirring the cryogenic tanks with a circuit fault present. To reproduce:
If a wiring fault exists, the issue may be replicated. Be aware that this may be hazardous to the tester attempting it.
The text was updated successfully, but these errors were encountered: