Recommended Posts

Curiosity is attempting one of the most complex and dangerous maneuvers possible: Switching out its primary on-board computer for the identical, redundant fail-safe computer. It is hoped that the swap will restore Curiosity to full operational capability. The failure is due to some corrupted flash memory.

Curiosity?s RCEs is a single-board RAD750 computer ? a radiation-hardened computer made by BAE that has a PowerPC 750 (G3) CPU clocked at around 200MHz, 256MB of RAM, 2GB of flash, and 256KB of EEPROM. It runs VXworks as its OS and managed with a Linux workstation.

http://www.extremete...l-functionality

I believe they did something similar on the earlier rovers, I always love seeing these suckers pull through! (wasn't it opportunity that had bad flash and couldn't upload pictures at first?)

If I remember right, yes. I think it's so interesting that such a complex advanced piece of machinery has about the same specs as a G3 iBook.

If I remember right, yes. I think it's so interesting that such a complex advanced piece of machinery has about the same specs as a G3 iBook.

Seriously. We have smartphones with higher specs than Curiosity. It's actually a little sad.

Seriously. We have smartphones with higher specs than Curiosity. It's actually a little sad.

Radiation is difficult to deal with since you have so many different types (Total Ionizing Dose, Single Event Upset, Proton, Neutron, etc...) that can kill electronics.

Seriously. We have smartphones with higher specs than Curiosity. It's actually a little sad.

It isn't sad when you consider the importance of such a computer. The rover doesn't need anything high-end. It needs something that's radiation-hardened (e.g. resistant to ionizing radiation) and something that is reliable. You wouldn't put a Ferrari engine in a car you use to drive to work everyday right?

Radiation is difficult to deal with since you have so many different types (Total Ionizing Dose, Single Event Upset, Proton, Neutron, etc...) that can kill electronics.

Oh I know. Doesn't make it any less sad. We're making water resistant dual-core phones (Xperia Z) and the Curiosity is floating up there with nearly decade old hardware, is the point. I'm sure there are things that can be done to improve the hardware we're sending up in space. Why wouldn't a dual or quad-core processor not be able to make it through space, but a processor essentially from 5 or more years ago? It's a bit ridiculous when you think about it!

It isn't sad when you consider the importance of such a computer. The rover doesn't need anything high-end. It needs something that's radiation-hardened (e.g. resistant to ionizing radiation) and something that is reliable. You wouldn't put a Ferrari engine in a car you use to drive to work everyday right?

No, of course you wouldn't. However, I'd argue this is hardly even remotely close to the same thing. We're talking about exploring space. You don't believe that hardware capable of doing 10-20 times more would be infinitely more efficient? Using your analogy if we were to go into space today, you would rather have an engine built many years ago, or something built by today's standards and technology?

You wouldn't put a Ferrari engine in a car you use to drive to work everyday right?

...I would.

(sorry, somebody had to say it)

Oh I know. Doesn't make it any less sad. We're making water resistant dual-core phones (Xperia Z) and the Curiosity is floating up there with nearly decade old hardware, is the point. I'm sure there are things that can be done to improve the hardware we're sending up in space. Why wouldn't a dual or quad-core processor not be able to make it through space, but a processor essentially from 5 or more years ago? It's a bit ridiculous when you think about it!

No, of course you wouldn't. However, I'd argue this is hardly even remotely close to the same thing. We're talking about exploring space. You don't believe that hardware capable of doing 10-20 times more would be infinitely more efficient? Using your analogy if we were to go into space today, you would rather have an engine built many years ago, or something built by today's standards and technology?

I think the Curiosity team explained why such a slow processor on their AMA. In short, the specs get finalized years before the actual mission and when Curiosity's planning started, that's what they had available.

Oh I know. Doesn't make it any less sad. We're making water resistant dual-core phones (Xperia Z) and the Curiosity is floating up there with nearly decade old hardware, is the point. I'm sure there are things that can be done to improve the hardware we're sending up in space. Why wouldn't a dual or quad-core processor not be able to make it through space, but a processor essentially from 5 or more years ago? It's a bit ridiculous when you think about it!

No, of course you wouldn't. However, I'd argue this is hardly even remotely close to the same thing. We're talking about exploring space. You don't believe that hardware capable of doing 10-20 times more would be infinitely more efficient? Using your analogy if we were to go into space today, you would rather have an engine built many years ago, or something built by today's standards and technology?

I think there must be a technical reason to choose that old system instead of our 8 cores.

Oh I know. Doesn't make it any less sad. We're making water resistant dual-core phones (Xperia Z) and the Curiosity is floating up there with nearly decade old hardware, is the point. I'm sure there are things that can be done to improve the hardware we're sending up in space. Why wouldn't a dual or quad-core processor not be able to make it through space, but a processor essentially from 5 or more years ago? It's a bit ridiculous when you think about it!

Power consumption, for one. Plus, as was already said, things like this are designed for a specific processing requirement and anything more than that is wasted resources. Your phone has million more functions than Curiosity, so of course it's going to have a million times more processing power. In the electronics world, a few MHz and a few KB, goes a long long way.

No, of course you wouldn't. However, I'd argue this is hardly even remotely close to the same thing. We're talking about exploring space. You don't believe that hardware capable of doing 10-20 times more would be infinitely more efficient? Using your analogy if we were to go into space today, you would rather have an engine built many years ago, or something built by today's standards and technology?

I understand what you're saying and I agree, it makes sense to use powerful hardware to aid in the exploration of space and planets. However, it makes even more sense to use something that's reliable and stable. A computer hardware failure would kill a mission. Also, I'm sure they'd use something more powerful if they needed it. Anything beyond that would be a waste of power.

In response to all of the above responses directed towards me:

Don't get me wrong, I don't think an octo-core is necessary. I also understand the issues with power consumption and wasted resources. I don't expect them to use brand-spanking new, top of the line hardware. I just find it odd that it'sas behind as it is. Personally, I think they could have done better. Maybe next time? ;)

The RAD computers are designed from go to be radiation resistant, largely by using larger circuit elements on the die at lower clock speeds. This allows it to continue even if one of the CPU circuit elements takes a direct hot by a cosmic ray (usually energetic protons) because the ions that event creates are few in a much larger current flow. Higher clock speeds and smaller elements would make these radiation induced ions statistically more significant. They also use error correction to a much greater degree than other computers.

SpaceX uses newer computer bits, but compensates for each board having a bit more radiation sensitivity by using them in polled arrays; if a board takes a hit and sends a result differing from the others it gets voted off the island and the others continue. Later they can reset it to see if it's let back in the game.

Tidbit: a couple of says ago a UK micro-satellite was orbited by an Indian launcher that is to test using a Nexus One smartphone as its main computer. Should get results soon.

  • Like 2

Also see They Write The Right Stuff. Consider how obnoxiously buggy and indigested nearly every piece of today's code is. Can't do any updates over 14 minute latency, ~2 (!) kbit/s channel for something that had to be got there in 8 months and cost several billion. There's zero room for error and zero minus one room for any field testing - it has to work and it's accepted that even then it will fail for unknown reasons (and it does). Solution - to slow the development down to such a mindboggling degree to iron out every possible bug, optimize it thoroughly and check it for what otherwise would be considered absolute impossibilities. And that's why "we haven't got anywhere". It's for this reason I'd argue that we haven't got anywhere near better with our earthly, ridiculously fast hardware and big blobs of software and useless data, either - it's many orders of magnitude more inefficient, buggy and insecure, being crapped out like shyte.

The middle road is to throw hardware at the problem - multiple arrays of lower cost. I think it's the wrong way - expecting and allowing for known problems.

How long does it take for commands sent to reach curiosity ?

The one-way communication delay with Earth varies from 4 to 22 minutes, depending on the planets' relative positions, with 12.5 minutes being the average. Took 13:46 minutes at the time of landing.

Oh I know. Doesn't make it any less sad. We're making water resistant dual-core phones (Xperia Z) and the Curiosity is floating up there with nearly decade old hardware, is the point. I'm sure there are things that can be done to improve the hardware we're sending up in space. Why wouldn't a dual or quad-core processor not be able to make it through space, but a processor essentially from 5 or more years ago? It's a bit ridiculous when you think about it!

No, of course you wouldn't. However, I'd argue this is hardly even remotely close to the same thing. We're talking about exploring space. You don't believe that hardware capable of doing 10-20 times more would be infinitely more efficient? Using your analogy if we were to go into space today, you would rather have an engine built many years ago, or something built by today's standards and technology?

Your's is a perfect example of consumer mentality. Hardware is not really obsolete until it stops working yet the vendors have make us believe we always need the latests and greatest (and more expensive). With the right software and optimizations apparent low hardware can be enough for any task. I mean, I'm sure Nasa techs know a little more about this that us, right? And I'm willing to bet that Curiosity is a little bit more mission critical than our facebook-checking pocket devices. Just a little.

Why do people think old hardware is bad? Old hardware is much more known about than new hardware, it's characteristics are known, as are rare bugs and other problems, how long they last etc. plus you can optimise them to use much less power by shrinking the dye.

The reason ABSOLUTELY NO single-device (this excludes clusters) mission critical system uses a brand new CPU or type of RAM, it hasn't been tested and for all you know after spending ?500m on getting a spacecraft built and launched into space could fail right away.

I wish people would stop moaning that things don't have the latest and greatest hardware in them - they don't need the latest and greatest hardware, what they need is reliability.

This topic is now closed to further replies.
  • Posts

    • Zed 1.7.2 has landed with updated OpenCode models, bug fixes and other improvements by David Uzondu Zed 1.7.2 recently landed on the stable release channel, bringing a host of AI-related features including automatic context compaction and settings-based skill management, along with other things like better Markdown preview rendering and custom git commands in the graph view. Starting with the AI stuff, the developers introduced "/compact", a command that basically summarizes your conversation history on demand. This tool prevents your active chat window from hitting token limits by compressing older parts of the dialogue into a brief overview. In addition to that, the team relocated skill management to the settings UI, improving how the application communicates errors regarding those skills, and updated the OpenCode model roster to support DeepSeek V4 Flash, MiniMax M3, Qwen 3.7 Plus, and Nemotron 3 Ultra Free. External agent users can also monitor context window cost metrics and delete individual sessions directly from their history. Right-clicking ref labels in the git graph now opens a context menu that runs different actions against selected targets, kind of how VS Code does it. Here are some of the bug fixes this new release brings: The active agent fails to auto-select when creating a new git worktree. A scrollbar unexpectedly appears on wrapped code blocks in the agent chat. Collapse indicators for project headers appear when performing sidebar searches. Bracketed ellipsis title prefixes fail to show the ellipsis icon properly. Project icons render incorrectly in the recent projects picker. Diff hunk controls appear inside non-editable commit view multibuffers. The software update button hangs indefinitely on the downloading stage. Restoring an agent terminal in a remote project triggers a sudden crash. Splitting a pane that contains an active commit view causes a crash. Linux Wayland freezes when trying to read the clipboard from laggy external apps. Zed is a "newish" code editor trying to break the massive stronghold VS Code has on the developer community. Funny enough, the editor was created by former GitHub employees who worked on the Atom text editor (which Microsoft killed in 2022, several years after it bought GitHub). The project officially hit version 1.0 back in April, introducing platform parity for Windows and Linux alongside deep support for DeepSeek-V4-Pro.
    • 26H2 absolutely will support ARM Windows just not on devices that came with 26H1. This is evident by the fact I am running 26H2, which on my MacBook Neo and Surface Pro 12 (inch), within a VM.
    • Mp3tag 3.35 by Razvan Serea Mp3tag is a powerful and yet easy-to-use tool to edit metadata (ID3, Vorbis Comments and APE) of common audio formats. It can rename files based on the tag information, replace characters or words from tags and filenames, import/export tag information, create playlists and more. The program supports online freedb database lookups for selected files, allowing you to automatically gather proper tag information for select files or CDs. Mp3tag supports the following audio formats: Advanced Audio Coding (aac) Free Lossless Audio Codec (flac) Monkeys Audio (ape) Mpeg Layer 3 (mp3) MPEG-4 (mp4 / m4a / m4b / iTunes compatible) Musepack (mpc) Ogg Vorbis (ogg) OptimFROG (ofr) OptimFROG DualStream (ofs) Speex (spx) Toms Audio Kompressor (tak) True Audio (tta) Windows Media Audio (wma) WavPack (wv) Mp3tag 3.35 changelog: This version introduces a new Files options page, enhanced toolbar customization, support for RF64 WAV files, improved Discogs and MusicBrainz tag sources, and many other improvements and fixes. See the Release Notes for more details. Download: Mp3tag 64-bit | 5.7 MB (Freeware) Download: Mp3tag 32-bit | 5.2 MB Link: Mp3tag Homepage | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • The FIFA World Cup is not US centric.
    • It’s amusing how Microsoft is pushing IT admins as if this was a major, game-changing update. In reality, it’s just an enablement package that bumps the build number, which is disappointing compared to the more substantial 22H2 and 24H2 releases. Technically, 25H2, 26H1, and the upcoming 26H2 are essentially the same, differing only in support schedules. They could have included the Windows K2 improvements here, but chose not to. The era of Windows being in the backburner continues, and this 26H2 release feels like an afterthought. Shame, Nadella, shame.
  • Recent Achievements

    • Week One Done
      AMV earned a badge
      Week One Done
    • One Month Later
      AMV earned a badge
      One Month Later
    • Collaborator
      ryansurfer98 went up a rank
      Collaborator
    • One Month Later
      Eurosoft10 earned a badge
      One Month Later
    • Week One Done
      Eurosoft10 earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      523
    2. 2
      +Edouard
      172
    3. 3
      PsYcHoKiLLa
      78
    4. 4
      Steven P.
      72
    5. 5
      Michael Scrip
      71
  • Tell a friend

    Love Neowin? Tell a friend!