Skip to content
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

Closed
NoraCodes opened this issue Jul 7, 2016 · 220 comments
Closed

Check continuity on O2 cryogenic tanks before allowing stir #3

NoraCodes opened this issue Jul 7, 2016 · 220 comments

Comments

@NoraCodes
Copy link

@NoraCodes NoraCodes commented Jul 7, 2016

A customer has had a fairly serious problem with stirring the cryogenic tanks with a circuit fault present. To reproduce:

  1. Build CSM
  2. Perform mission up to translunar coast
  3. During translunar coast, attempt to stir cryo tanks

If a wiring fault exists, the issue may be replicated. Be aware that this may be hazardous to the tester attempting it.

@electron0zero
Copy link

@electron0zero electron0zero commented Jul 7, 2016

i think this issue should be closed because we can't reproduce it

@lbotinelly
Copy link

@lbotinelly lbotinelly commented Jul 7, 2016

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.

@pjanaya
Copy link

@pjanaya pjanaya commented Jul 7, 2016

Have you tried turning it off and on again?

@atpage
Copy link

@atpage atpage commented Jul 7, 2016

This is fixed in Apollo 14.

@adampats
Copy link

@adampats adampats commented Jul 7, 2016

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?"

@NoraCodes
Copy link
Author

@NoraCodes NoraCodes commented Jul 7, 2016

@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!

@leommoore
Copy link

@leommoore leommoore commented Jul 7, 2016

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.

@chrislgarry
Copy link
Owner

@chrislgarry chrislgarry commented Jul 7, 2016

@SilverWingedSeraph could you provide a screen shot of the error I should expect to see during repro?

@AdamFreemer
Copy link

@AdamFreemer AdamFreemer commented Jul 7, 2016

Let's work the problem people.

@NoraCodes
Copy link
Author

@NoraCodes NoraCodes commented Jul 7, 2016

@chrislgarry It looks a little something like this:

screenshot_20160707_104443

screenshot_20160707_104357

@khash
Copy link

@khash khash commented Jul 7, 2016

Which version of Apollo are you running? I suggest upgrading to Apollo 12

@lbotinelly
Copy link

@lbotinelly lbotinelly commented Jul 7, 2016

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.

@Wazzaps
Copy link

@Wazzaps Wazzaps commented Jul 7, 2016

Have you tried migrating your project to jQuery?

@AdamFreemer
Copy link

@AdamFreemer AdamFreemer commented Jul 7, 2016

Many bug fixes were addressed in Apollo 18 mission software, until the bugs infected the astronauts.

@predicat
Copy link

@predicat predicat commented Jul 7, 2016

It works for me

@lparkermg
Copy link

@lparkermg lparkermg commented Jul 7, 2016

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.

@g0ddish
Copy link

@g0ddish g0ddish commented Jul 7, 2016

@atpage Savage

@stkrzysiak
Copy link

@stkrzysiak stkrzysiak commented Jul 7, 2016

We're going to need a label for good first bug, agreed?

@lparkermg
Copy link

@lparkermg lparkermg commented Jul 7, 2016

@stkrzysiak It's got to be a hardware tag if what @atpage said is true.

@autoferrit
Copy link

@autoferrit autoferrit commented Jul 7, 2016

@Wazzaps
Have you tried migrating your project to jQuery?

we have tried converting to node. heres a mockup.

http://svtsim.com/moonjs/agc.html

@AstraSerg
Copy link

@AstraSerg AstraSerg commented Jul 7, 2016

Which exactly Universe do you use when face this bug?

@jerry-bachmann
Copy link

@jerry-bachmann jerry-bachmann commented Jul 7, 2016

Just had this issue happen to me, I took a screenshot.

apollo-13

@JohnTendik
Copy link

@JohnTendik JohnTendik commented Jul 7, 2016

Did you try uninstalling the drivers then reinstalling them?

@bstiller1
Copy link

@bstiller1 bstiller1 commented Jul 7, 2016

Looks like there could be an ID10T error, along with some memory leaks.

@ireun
Copy link

@ireun ireun commented Jul 7, 2016

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!

@AndrewFeeney
Copy link

@AndrewFeeney AndrewFeeney commented Jul 7, 2016

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.

@jerry-bachmann
Copy link

@jerry-bachmann jerry-bachmann commented Jul 7, 2016

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.

@kiweb
Copy link

@kiweb kiweb commented Jul 7, 2016

It's not a bug, it's a feature.

@luislobo
Copy link

@luislobo luislobo commented Jul 7, 2016

Well, I run the unit tests and it says 0 errors...

@AnthonyRinaldi
Copy link

@AnthonyRinaldi AnthonyRinaldi commented Jul 7, 2016

Did you try SCE to AUX?

@vickz84259
Copy link

@vickz84259 vickz84259 commented Jul 18, 2016

You forgot to import apollo_11.cms...

@Domminique
Copy link

@Domminique Domminique commented Jul 18, 2016

let me check it out

Regards,

Dominic A. Imbuga *
Blogs: http://imbuga.blogspot.co.ke || imbugad.wordpress.com
*Fullstack Developer | Blogger

Github:Domminique
Twitter:@dominicimbuga

Skype:Dominic-imbuga_+254 715 180 530 | +254 734 983 442_

_" _Science and technology revolutionize our lives, but memory, tradition
and myth frame our response"

On Mon, Jul 18, 2016 at 9:48 PM, Victor Otieno notifications@github.com
wrote:

You forgot to import apollo_11.cms...


You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#3 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AGX1iZKhwYKY2mTiS8n9ezBpcATSgQ_4ks5qW8prgaJpZM4JHJnx
.

@dreamyguy
Copy link

@dreamyguy dreamyguy commented Jul 20, 2016

🚫 USER ERROR 🚫

@ahmadawais
Copy link

@ahmadawais ahmadawais commented Jul 20, 2016

I just solved the issue. Here's how, have a listen!

🔘──────── 00:21

@Pablo-Ivan
Copy link

@Pablo-Ivan Pablo-Ivan commented Jul 26, 2016

I suggest assigning Stanley Kubrick to fix this issue.

@chrislgarry chrislgarry added the humor label Aug 6, 2016
@pantaluna
Copy link

@pantaluna pantaluna commented Aug 17, 2016

Which version of Apollo are you running? I suggest upgrading from Apollo 11 to Apollo 12

@khash We cannot upgrade simply because by our 60's semver rules the V12 contains "breaking" changes.

@humantorch
Copy link

@humantorch humantorch commented Sep 15, 2016

This never would have happened when Steve Jobs was alive.

@sdhar86
Copy link

@sdhar86 sdhar86 commented Sep 15, 2016

And that's why we should use docker, could have reproduced the issue easily.

@cristianmedeiros
Copy link

@cristianmedeiros cristianmedeiros commented Sep 16, 2016

works on my machine

@aniruddhas
Copy link

@aniruddhas aniruddhas commented Sep 17, 2016

You guys are trying to solve an issue which doesn't exist in future.
The Doctor has already solved it in past future.
In his words:
"People assume that time is a strict progression of cause to effect, but actually from a non-linear, non-subjective viewpoint - it's more like a big ball of wibbly wobbly... time-y wimey... stuff."

So, let's stop being geeky and go back to humour, ehh?

@brossow
Copy link

@brossow brossow commented Jan 24, 2017

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.

@timlindsay
Copy link

@timlindsay timlindsay commented Feb 5, 2017

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.

@Silmar
Copy link

@Silmar Silmar commented Apr 3, 2017

There is a plugin for jQuery that fixes it. Google4it.

@1337ninja
Copy link

@1337ninja 1337ninja commented Apr 5, 2017

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())

@orcaman
Copy link

@orcaman orcaman commented Apr 5, 2017

I think it's time we re-write this node.js code in golang.

@brianmay
Copy link

@brianmay brianmay commented Dec 2, 2018

Why hasn't anybody submitted a PR to fix this issue yet?

@j-degreef
Copy link

@j-degreef j-degreef commented Mar 26, 2019

This never would have happened when Steve Jobs was alive.

Who ?

@Stevie-C
Copy link

@Stevie-C Stevie-C commented Sep 3, 2019

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!

@brianmay
Copy link

@brianmay brianmay commented Sep 3, 2019

Don't understand why this was tagged "Won't fix" and "Humour". Seems to me you don't appreciate the seriousness of this report.

@theodesp
Copy link

@theodesp theodesp commented Sep 3, 2019

@brianmay what do you expect? They are the same people that worked on the Apollo13 and we all know what happened...

@soft9000
Copy link

@soft9000 soft9000 commented Jun 17, 2020

... it worked on my moon ...

@s3ver1na
Copy link

@s3ver1na s3ver1na commented Jun 18, 2020

... it worked on my moon ...

that's no moon.....

@lbotinelly
Copy link

@lbotinelly lbotinelly commented Jun 18, 2020

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.

@gamecoder-nz
Copy link

@gamecoder-nz gamecoder-nz commented Jul 17, 2020

It works on my machine

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
You can’t perform that action at this time.