Stories
Slash Boxes
Comments

SoylentNews is people

posted by janrinok on Tuesday July 07 2015, @11:45AM   Printer-friendly
from the software-doing-what-it-should dept.

Days before NASA's New Horizons probe to Pluto experienced a technical issue, the Dawn spacecraft orbiting Ceres "experienced an anomaly":

NASA's Dawn spacecraft is healthy and stable, after experiencing an anomaly in the system that controls its orientation. It is still in its second mapping orbit 2,700 miles (4,400 kilometers) above dwarf planet Ceres.

On June 30, shortly after turning on its ion engine to begin the gradual spiral down to the next mapping orbit, its protective software detected the anomaly. Dawn responded as designed by stopping all activities (including thrusting), reconfiguring its systems to safe mode and transmitting a radio signal to request further instructions. On July 1 and 2, engineers made configuration changes needed to return the spacecraft to its normal operating mode. The spacecraft is out of safe mode, using the main antenna to communicate with Earth.

The Dawn issue is less serious than problems with New Horizons since the third and fourth mapping orbits can be executed whenever NASA is ready, and the final orbit around Ceres will last indefinitely. By contrast, New Horizons will speed past Pluto and reach its closest approach on July 14th at 11:49:57 UTC at a relative velocity of 13.78 km/s. After collecting data from Pluto, NASA will try to steer New Horizons towards one or two Kuiper belt objects within a narrow cone extending from Pluto.

NASA engineers have released an explanation for the July 4th glitch:

To prepare for these final days of its mission, the probe was doing two things at once. First, it was taking the scientific data it has already harvested, compressing it, and writing it to a portion of its 128 Gbit storage (two 8GB solid-state recorders). At the same time the instrument command sequence for the flyby was being uploaded. The combined workload slightly exceeded the processor's capabilities, and triggered a watchdog-like feature. This switched the main computer system over to the backup computer, while putting the main system into sleep mode as a safety measure. The processor is a Mongoose-V: a 12MHz MIPS R3000 CPU hardened against radiation. The R3000 is a 32-bit chip that's pretty similar to the one used in the original 1994-era Sony PlayStation among many other devices.


Original Submission

 
This discussion has been archived. No new comments can be posted.
Display Options Threshold/Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
  • (Score: 3, Informative) by VLM on Tuesday July 07 2015, @02:30PM

    by VLM (445) on Tuesday July 07 2015, @02:30PM (#206122)

    137 GB addressing space space barrier

    IDE protocol limitation. Never existed for SCSI drives. Can't remember off the top of my head if any R3000 CPU based workstations ever used IDE drives although PATA IDE is/was so crude at a hardware level that it would be trivially technically possible to make a R3000 based machine that used IDE drives.

    I'm not sure if anyone ever made large aerospace grade IDE drives. I have a laptop size industrial / automotive grade PATA drive laying around somewhere so "sorta hardened" IDE drives once existed.

    I wonder if the playstation cdrom-ish drive was IDE or SCSI or some whacked out proprietary thing (like mitsumi which was kinda PATA but not PATA)

    Could not find anything online about the new horizons computer system beyond the usual "Its a R3000 CPU just like a playstation".

    Starting Score:    1  point
    Moderation   +1  
       Informative=1, Total=1
    Extra 'Informative' Modifier   0  
    Karma-Bonus Modifier   +1  

    Total Score:   3  
  • (Score: 2) by quacking duck on Tuesday July 07 2015, @03:38PM

    by quacking duck (1395) on Tuesday July 07 2015, @03:38PM (#206145)

    Thanks; the wiki article [wikipedia.org] I got that from unfortunately didn't specify this was an IDE limitation.