this post was submitted on 21 Aug 2023
36 points (95.0% liked)

Programming

17351 readers
310 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev

founded 1 year ago
MODERATORS
snowe@programming.dev
Ategon@programming.dev
MaungaHikoi@lemmy.nz
36
Rumbles of a programing error causing the Russian Lunar mission failure. (twitter.com)
submitted 1 year ago by intelati@programming.dev to c/programming@programming.dev
27 comments fedilink hide all child comments
 

Perhaps the 84 second burn overflowed the integer (2^6) and was caught by a 2^7s check (127s)

you are viewing a single comment's thread
view the rest of the comments
[–] ImpossibleRubiksCube@programming.dev 1 points 1 year ago

You know what this reminds me of? The processing failure that killed Phobos 2 right before it reached Mars.

As I recall, the craft lost attitude control and didn't have a safe mood to orient it toward the sun; so it burned through its batteries making adjustments in a few hours. It had two landing probes on board that never got to be used. So, no emergency backup systems. Never heard from it again.

Of course this was 1989, and most people only had a vague idea what programmers did; but it still feels like a serious and kind of nebulous oversight.