Stories
Slash Boxes
Comments

SoylentNews is people

SoylentNews is powered by your submissions, so send in your scoop. Only 18 submissions in the queue.
posted by CoolHand on Friday May 29 2015, @08:42AM   Printer-friendly
from the sailing-away dept.

Covered at Sen is the news that a software glitch is causing problems for the Light Sail project launched by the Planetary Society

The privately funded Planetary Society, a California-based space exploration advocacy group, has not been in communication with its LightSail since Friday, two days after it hitched a ride to orbit aboard an Atlas 5 rocket carrying the U.S. Air Force’s X-37B robotic mini shuttle.

This is also covered at the Planetary Society blog:

It is now believed that a vulnerability in the software controlling the main avionics board halted spacecraft operations, leaving a reboot as the only remedy to continue the mission. When that occurs, the team will likely initiate a manual sail deployment as soon as possible.
...
The manufacturer of the avionics board corrected this glitch in later software revisions. But alas, LightSail’s software version doesn’t include the update.

The team are hoping for a reboot to bring the device back to life, either from a ground transmission or charged particle glitch, although attempts to reboot from the ground look to have failed to date.

Cal Poly is automating the reboot command transmission to be sent every few ground station passes, on the hope that one command sneaks through (we don't send the command on every pass because a successful reboot triggers a waiting period before beacon transmissions begin). But as of right now, we can’t do much except wait, hoping a charged particle smacks the spacecraft in just the right way to cause a reboot. LightSail is capable of remaining in orbit about six months in its CubeSat form.

Additional background on the project is available in a previous SN article, and ongoing updates at the mission control page for the LightSail project.


[Editor's Comment: 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: 2) by ticho on Friday May 29 2015, @01:48PM

    by ticho (89) on Friday May 29 2015, @01:48PM (#189655) Homepage Journal

    But it _is_ a vulnerability, just not a security vulnerability.

    Starting Score:    1  point
    Karma-Bonus Modifier   +1  

    Total Score:   2  
  • (Score: 0) by Anonymous Coward on Friday May 29 2015, @01:58PM

    by Anonymous Coward on Friday May 29 2015, @01:58PM (#189658)

    Actually it could be a security vulnerability, depending on the exact path leading to the crash. Often things that can lead to crashes for arbitrary data can also lead to security breaches with specially crafted data.

  • (Score: 2) by sudo rm -rf on Friday May 29 2015, @02:19PM

    by sudo rm -rf (2357) on Friday May 29 2015, @02:19PM (#189668) Journal

    Then I completely misunderstood the meaning of vulnerability (quite possible). Care to elaborate?
    To me a vulnerability means there has to be an attacker, or as this random military page [dod.mil] defines it:
    System vulnerability is defined to be the intersection of a system susceptibility or flaw, access to the flaw, and the capability to exploit the flaw.

    • (Score: 2) by ticho on Friday May 29 2015, @06:19PM

      by ticho (89) on Friday May 29 2015, @06:19PM (#189766) Homepage Journal

      The system is simply vulnerable to having too many records in the CSV file, just like, I don't know, a human body is vulnerable to open fire.

      The definition you linked to is still talking about a _security_ vulnerability.