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

    • Same Internet Archive seemed to grab the new version https://web.archive.org/web/20...d/Setup_MakeMKV_v1.18.4.exe Here's the link to an additional file it periodically downloads https://web.archive.org/web/20260213092148/https://www.makemkv.com/sdf.bin I think update's keys, etc. To manually trigger this update, put the sdf.bin file in the root of where the program is installed. When you launch the program it will pick up the file and import it. Typically put it here: C:\Program Files (x86)\MakeMKV\sdf.bin
    • Windows 11 KB5094126, KB5093998 bugging out Office apps but it may not be Microsoft's fault by Sayan Sen Microsoft last week released Windows 11 KB5094126 and KB5093998 as the latest Patch Tuesday updates. Following that the company also published the accompanying dynamic updates under KB5094149, KB5095971, and KB5094156. Although the tech giant did not acknowledge any major problems, some users online reported various issues ranging from OneDrive and Dropbox access problems, BitLocker recovery lockouts, to blue screens and BSODs. You can read about them in this dedicated piece. While there is still no confirmation about those problems from Microsoft the company has admitted to another bug which we did not report on. The tech giant has confirmed it has received reports of an issue in which certain third-party applications may be unable to launch Microsoft Office apps or open Office documents after installing the Patch Tuesday. This affects both Windows 11 as well as Windows 10. The company says the problem impacts a subset of applications that rely on OLE (Object Linking and Embedding) automation to communicate with Microsoft Office programs. According to Microsoft, affected scenarios involve third-party software attempting to open Office applications or documents from within their own interface. In such cases, the Office program may fail to launch altogether, or the requested document may not open. Oddly there may not be any error message, which probably makes the issue difficult to diagnose. The bug affects several Office products, including Word, Excel, PowerPoint, Access, and other apps in the Microsoft Office suite when they are launched through the affected software. These include tax and accounting software such as CCH Engagement and Workpaper Manager, dental practice management solutions like Dentrix and Softdent, as well as the popular research and reference management tool Zotero. Microsoft adds that other applications using similar Office integration methods could also experience the same problematic behavior. To understand the issue it is important to look at OLE, the Microsoft technology involved. OLE allows different applications to work together and share data, while its Automation feature lets one program control another. Thus this enables third-party software to launch Microsoft Office apps, open documents, and perform tasks automatically without requiring users to switch between programs. Because many accounting, healthcare, research, and business applications rely on OLE automation to interact with Word, Excel, PowerPoint, and other Office apps, any disruption can break those workflows. As a result, affected software may be unable to open Office documents or launch Office applications even though the programs themselves continue to work normally. At the moment the company has not provided a permanent fix though it has confirmed that engineers are actively working on a resolution, which will be delivered through a future Windows update. As such additional details will be shared once more information becomes available. In the meantime, Microsoft recommends a simple workaround for affected users whic is to open the Office application or document directly rather than launching it through the third-party program. For enterprise customers and organizations managing larger deployments, Microsoft says an additional mitigation is available. Admins experiencing the problem on their managed devices are advised to contact Microsoft Support for business to obtain and apply the workaround.
    • It saddens me when cars are such dull colours now. Mine is bright metallic blue and I absolutely adore it for standing out in contrast to that depressing backdrop of traffic.
    • Sparkle 2.20.0 by Razvan Serea Sparkle is a free, open-source Windows optimization tool designed to make your PC faster, cleaner, and more private. With Sparkle, you can easily debloat Windows by removing unnecessary apps and services, disable Microsoft tracking to enhance privacy, and apply performance tweaks to boost speed. Its cleaner removes junk and temporary files, while every change is safe and fully reversible. Sparkle also features a modern, user-friendly interface with automatic updates, making system maintenance simple. Explore over 39 tweaks, from disabling telemetry and hibernation to optimizing network and game settings, all aimed at customizing and enhancing your Windows experience. Sparkle supports Windows 10 and 11. Sparkle 2.20.0 changelog: Debloat Tweak has animated border New homepage loading UI New Tweak Modal (Markdown Supported) Refactored GPU Detection Added Tests with vitest Added foobar2000 to apps Added Localsend to apps Updated Modal Styles Added styles for disabled inputs Added Animated Border to debloat-windows tweak Bumped dependencies Refactor System info logic for speed Tweak info modals now support Markdown Added Clear System info cache to settings Redesigned Home Page Loading UI Changed Some Icons around the app Download: Sparkle 2.20.0 | Portable | ~100.0 MB (Open Source) Links: Sparkle Website | Github | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • lol it was a typo, fixed! haha imagine an actual 4TB Gen4 NVMe for $40 in 2026
  • Recent Achievements

    • Reacting Well
      Dys Topia earned a badge
      Reacting Well
    • Conversation Starter
      NovaEdgeX earned a badge
      Conversation Starter
    • One Year In
      Console General earned a badge
      One Year In
    • Week One Done
      Twozo Technologies earned a badge
      Week One Done
    • One Month Later
      Twozo Technologies earned a badge
      One Month Later
  • Popular Contributors

    1. 1
      +primortal
      517
    2. 2
      +Edouard
      184
    3. 3
      PsYcHoKiLLa
      106
    4. 4
      Steven P.
      88
    5. 5
      ATLien_0
      68
  • Tell a friend

    Love Neowin? Tell a friend!