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

    • Win11Debloat 2026.06.14 by Razvan Serea Win11Debloat is a lightweight, easy to use PowerShell script that allows you to quickly declutter and customize your Windows experience. It can remove pre-installed bloatware apps, disable telemetry, remove intrusive interface elements and much more. The script also includes many features that system administrators and power users will enjoy. Such as a powerful command-line interface, support for Windows Audit mode and the option to make changes to other Windows users. All changes made by Win11Debloat can be easily reversed, and most removed apps can be restored via the Microsoft Store. A full guide on how to undo the changes is available here. Win11Debloat features: Below is an overview of the key features and functionality offered by Win11Debloat. Please refer to the wiki for more information about the default settings preset. Remove a wide variety of preinstalled apps. Click here for more info. Disable telemetry, diagnostic data, activity history, app-launch tracking & targeted ads. Disable tips, tricks, suggestions & ads across Windows. Disable Windows location services & app location access. Disable Find My Device location tracking. Disable 'Windows Spotlight' and tips & tricks on the lock screen. Disable 'Windows Spotlight' desktop background option. Disable ads, suggestions and the MSN news feed in Microsoft Edge. Hide Microsoft 365 ads on the Settings 'Home' page, or hide the 'Home' page entirely. Disable & remove Microsoft Copilot. Disable Windows Recall. Disable Click to Do, AI text & image analysis tool. Prevent AI service (WSAIFabricSvc) from starting automatically. Disable AI Features in Edge. Disable AI Features in Paint. Disable AI Features in Notepad. Disable the Drag Tray for sharing & moving files. Restore the old Windows 10 style context menu. Turn off Enhance Pointer Precision, also known as mouse acceleration. Disable the Sticky Keys keyboard shortcut. Disable Storage Sense automatic disk cleanup. Disable fast start-up to ensure a full shutdown. ...and more. Once you’ve downloaded the Win11Debloat file (Get.ps1), just follow these quick steps: Locate the Get.ps1 script file. Right-click the file and select Run with PowerShell from the context menu. If prompted by User Account Control (UAC), select Yes to grant the script the necessary administrative permissions. Win11Debloat 2026.06.14 changes: This is a minor release that hopefully addresses the false positives in Windows Defender and Bitdefender that prevented users from downloading and/or running Win11Debloat. Refactor Get-RegFileOperations.ps1 to address false positives by @Raphire in #626 Add logging around WinGet app retrieval and increase timeout to 20s by @Raphire Download: Win11Debloat 2026.06.14 | Open Source View: Win11Debloat Home Page | Screenshots 1| 2 Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • Still using Microsoft Money 2005 in 2026 here!
    • I have a couple to mention, and they still run great on Windows 11 Adobe Lightroom Version 2 Alcohol 120% CLZ Book, Comic, Game, Movie, & Music Collector (PC - No longer sold / Grandfathered in - now mobile apps/online only) DVDDecrypter ISO Buster Pro version 1.9.1 (Still supports HD-DVD too) Nero Burning Rom 8 (Only the burning software, no backup, media converter, etc)   OpenAL (Runtime) - GuildWars 1 Reforged still uses it for 3d headphone audio PowerDVD 12 Ultra SPTD (SCSI Pass through Direct Driver) UltraISO Windows Media Encoder 9 WinImage You can tell I still sport an optical drive    
    • Linux 7.1 arrives with an NTFS overhaul and major hardware performance boosts by Paul Hill The founder of the Linux kernel has just announced the availability of Linux 7.1. This is a stable version of the kernel that will now be tested by various Linux distributions before it is shipped to users through update managers. Some users, like those on Debian, for example, might not get it for a long time, if at all, while Fedora users can expect it in the near future. With Linux 7.1 out on time, the merge window for Linux 7.2 is now open, giving contributors the opportunity to send in major new features that have been waiting for the last two months. Torvalds warned that he is currently travelling and will be in another timezone, so timing for the merge window may be irregular due to timezone differences and limited internet access. Torvalds said that he has already fetched early pull requests to allow him to do some offline work, but the travel could still cause disruption. Right now, he is not planning to extend the release, but did consider it. He said he might later regret not extending, though. In terms of this last week of development for Linux 7.1, Torvalds said there were no major or alarming changes. This week consisted mostly of smaller driver updates to GPU, networking, and sound, networking fixes, trace tooling fixes, and misc minor fixes. The shortlog this week lists fixes for driver bugs, memory leaks, I/O and USB fixes, networking and RDMA fixes, DRM/graphics fixes, and tooling and verification improvements. Specific fixes include USB series heap-overflow and buffer overflow fixes, and multiple use-after-free, memory-leak, and refcount corrections across subsystems such as i2c, zram, gpio, and net. There are fixes for graphics drivers, including amdgpu, i915, and virtio, as well as hypervisor and virtualization tweaks affecting mshv, vmbus, and hyperv. According to Phoronix, anyone running Linux 7.1 should look out for the new NTFS driver, Intel FRED for improved performance on Panther Lake and future CPUs, faster graphics with Intel Arc Battlemage, and improvements for older AMD Radeon GPUs. If you are running Linux on your computer and everything is fine, then you don’t need to worry about updating to Linux 7.1 as a priority; just wait for it to be pushed to you. If you have tried Linux on hardware but it didn’t work properly, trying again with a distro that uses Linux 7.1 could cause Linux to work on your machine, thanks to the new hardware support.
    • you can also do this with this tool: PowerSettingsExplorer made by mbk1969 at 3dguru forum.. I found it by accident researching on modern standby and annoying quirks of it in 2022
  • Recent Achievements

    • Week One Done
      Jeroen Wilms earned a badge
      Week One Done
    • Week One Done
      rolfus earned a badge
      Week One Done
    • One Month Later
      Leroy Jethro Gibbs earned a badge
      One Month Later
    • Conversation Starter
      flexorcist earned a badge
      Conversation Starter
    • One Month Later
      AndreaB earned a badge
      One Month Later
  • Popular Contributors

    1. 1
      +primortal
      507
    2. 2
      +Edouard
      197
    3. 3
      PsYcHoKiLLa
      139
    4. 4
      ATLien_0
      90
    5. 5
      Steven P.
      81
  • Tell a friend

    Love Neowin? Tell a friend!