Slashdot Mirror


NASA Making Renewed Efforts To Contact Mars Rover Opportunity (spacenews.com)

NASA is making a new, and perhaps final, attempt to restore contact with the Mars rover Opportunity, which has not communicated with the Earth for more than six months. From a report: The Jet Propulsion Laboratory announced Jan. 25 that it was transmitting a new set of commands to address what it acknowledged are "low-likelihood" events that could have kept the rover from contacting Earth. These new efforts are in addition to the months-long "sweep and beep" campaign of transmitting other commands and listening for a reply from the rover.

The new commands address scenarios where the rover's primary X-band radio has failed or both the primary and backup X-band radios have failed, as well as cases where Opportunity's internal clock has an offset affecting its timing. The commands direct the rover to switch to the backup X-band radio or use its UHF transmitter to contact Earth, as well as resetting its clock. Those scenarios could explain why the rover has failed to contact Earth, but project officials acknowledge that those scenarios are unlikely. "A series of unlikely events would need to have transpired for any one of these faults to occur," JPL noted in the statement about the new campaign.

31 of 70 comments (clear)

  1. It was martians by The+Grim+Reefer · · Score: 2

    I misaligned my satellite dish the other night. The first program I saw showed Opportunity and these little green guys were messing with it. At the end of the hour they had put new 22 inch rims with spinners and low profile tires, a crazy new stereo with a coupe big ass subwoofers, neon lights on the undercarriage, lambo doors and shag carpet inside. I think it must have been the martian version of pimp my ride.

  2. Silly NASA by 110010001000 · · Score: 1

    Silly NASA still messing around with obsolete rovers. Why aren't they building space factories and Mars colonies and mining asteroids? They obviously don't read Slashdot comments. If they did we would be living on Mars by now.

    1. Re:Silly NASA by jellomizer · · Score: 3, Funny

      The problem is NASA did read the Slashdot Comments, they are still trying to get Gentoo Linux to compile.

      --
      If something is so important that you feel the need to post it on the internet... It probably isn't that important.
    2. Re:Silly NASA by UnknowingFool · · Score: 1

      Perhaps you should write to your Congressman about funding NASA to fulfill your fantasies. Otherwise as a government agency, NASA is limited to what Congress will allow them to do mission wise and budget wise.

      --
      Well, there's spam egg sausage and spam, that's not got much spam in it.
    3. Re:Silly NASA by PolygamousRanchKid+ · · Score: 1

      Perhaps you should write to your Congressman about funding NASA to fulfill your fantasies.

      Congress Critters will happily support funding for fantasies . . . as long as it results in government spending in their state.

      Unfortunately, asteroids and Mars don't have any representatives in Congress. Thus, no NASA funding for mining asteroids or building Mars colonies.

      Back on topic, didn't Musk land a Tesla on Mars? Maybe he could program that to look for the Rover?

      --
      Schroedinger's Brexit: The UK is both in and out of the EU at the same time!
    4. Re:Silly NASA by Tablizer · · Score: 1

      Silly NASA still messing around with obsolete rovers. Why aren't they building space factories and Mars colonies and mining asteroids? They obviously don't read Slashdot comments. If they did we would be living on Mars by now.

      Sounds familiar:

      [The President] asked the then-acting administrator of NASA whether the space agency could send American astronauts to Mars by the end of his first term, and even offered him "all the money you could ever need" to make it happen. The NASA official politely turned him down, explaining that such a fast turnaround to a distant planet wasn't possible.

      https://www.theatlantic.com/sc...

      Just get the Martians to pay for it. If there are none, plant some.

  3. Even so....What an Achivement! by bobbied · · Score: 5, Insightful

    Given how long past it's warranty this little rover lasted, what an achievement for JPL.

    I hope they can get things working again, but even if the effort fails, this little rover has gone over and above. It's hard to say good bye and we are sad about it, but we all knew this day was coming. Remember what JPL accomplished with these two rovers and revel in that. This isn't a failure, it's but the end a huge success.

    Way to go JPL, you really out did all our expectations and have contributed to a volume of scientific observations that will provide invaluable science and research for decades to come, not to mention some really impressive pictures which are very interesting to just look at. Thank You! Job well done.

    --
    "File to fit, pound to insert, paint to match" - Aircraft Maintenance 101
    1. Re:Even so....What an Achivement! by Only+Time+Will+Tell · · Score: 2

      Agreed, the two rovers were well engineered and survived numerous "near misses" along their way that could have shut them down prematurely. The fact that they lasted so long is a credit to those who worked on it to build in robust systems and backups to handle whatever unpredictability the Martian surface could throw at them. I look forward to the next rover projects and what feats they'll accomplish.

    2. Re:Even so....What an Achivement! by Kjella · · Score: 1

      It's incredibly impressive, but it's sad that we don't get any closure on whether it was old age or the extremely strong dust storm that killed it. Like could this have happened the first year or was it just the straw that broke the camel's back. It would have been a lot easier to make multi-year plans for solar powered rovers with confidence, though I suppose with Curiosity and Mars 2020 both going for RTGs that might not be such a big deal. I would think solar is still the better choice for any permanent structure, but then we really need to know the worst case. Either that or we could have some hybrid power but I would imagine that the crew get plenty radioactivity without bringing their own source.

      --
      Live today, because you never know what tomorrow brings
    3. Re:Even so....What an Achivement! by The+Grim+Reefer · · Score: 3, Interesting

      Agreed, the two rovers were well engineered and survived numerous "near misses" along their way that could have shut them down prematurely

      I'm not disagreeing with the phenomenal engineering, but in hindsight there is no way that anyone would say were at risk of been shutdown prematurely.

      Both Spirit and Opportunity landed on Mars in January of 2004 and were each scheduled for 90 (martian) days (92.5 earth days) missions.

      Spirit got stuck on May 1, 2009 and remained so until NASA lost contact with it in May of 2011. That amount of time past it's planned mission would have been amazing if it wasn't for Opportunity making it another 7 years. I just checked the Wikipedia page for Opportunity. It went 14 years, 277 days past it's original planned mission.

      It's kind of a shame that the Soviet Lunkhod rovers don't get more recognition. Both were launched over thirty years prior to the MER program. One of those rovers remained functional for over 300 days with late 1960's technology.

      Still, the rovers didn't come close to the still functioning Voyager 1 and 2 probes in terms of time or distance. They've both been functioning to some degree for over 40 years now.

    4. Re:Even so....What an Achivement! by The+Grim+Reefer · · Score: 1

      I forgot about the Pioneer 10 and 11 probes. Pioneer 10 launched in 1972 and remained functional until 2003. Pioneer 11 was launched in 1973 and was functional until 1995.

      Hubble has been kicking since 1990, and Mars Odyssey since 2001, I wish NASA made consumer electronics and home appliances. ;-)

  4. Gluhwein by Impy+the+Impiuos+Imp · · Score: 1

    This is what you get for gluing in the battery.

    --
    (-1: Post disagrees with my already-settled worldview) is not a valid mod option.
    1. Re:Gluhwein by Locke2005 · · Score: 2

      I know, right? if it was a user-replacable battery we could have... oh, wait...

      --
      I've abandoned my search for truth; now I'm just looking for some useful delusions.
    2. Re:Gluhwein by Kjella · · Score: 1

      Hey if you can use Hubble to justify the Space Shuttle I'm sure we can use the SLS to go to Mars to replace a battery. If it's not swept under a big fucking rug in the meantime.

      --
      Live today, because you never know what tomorrow brings
    3. Re:Gluhwein by Tablizer · · Score: 1

      This is what you get for gluing in the battery.

      Is a "Gluein Award" like a Darwin Award for devices?

  5. Re:Opportunity transmitted wrong DNA code by Megol · · Score: 2

    A grue did it.

  6. Re:NASA is incompetant by UnknowingFool · · Score: 1

    Let me see if I understand your nonsensical rant. You want to defund NASA for trying to revive a rover that they have kept working for more than 15 years past the original mission parameters because they are "incompetent". I feel that feat alone destroys your point.

    --
    Well, there's spam egg sausage and spam, that's not got much spam in it.
  7. Just like me trying to get back with my ex... by Locke2005 · · Score: 1

    Trust me, NASA, it isn't going to happen!

    --
    I've abandoned my search for truth; now I'm just looking for some useful delusions.
  8. The Real Reason by contrains · · Score: 2

    They're probably just hesitant to reveal the real story, that Opportunity has simply chosen to stop responding to us. https://xkcd.com/1504/

  9. Re:NASA is incompetant by UnknowingFool · · Score: 1

    First, please list all the NASA bloat that you think has occurred. Second, why would you think that NASA doesn't know what happened. The batteries being drained in a dust storm is the exact scenario that NASA predicted more than 16 years ago in their planning. And third, why would the Chinese and Russians getting to Mars help out NASA in this way? Have those countries have designed and built repair bots that can troubleshoot an American rover? I would bet they Chinese and Russian rovers have their own missions and not one thought has been put into fixing another rover.

    --
    Well, there's spam egg sausage and spam, that's not got much spam in it.
  10. Re:NASA is incompetant by UnknowingFool · · Score: 1

    I understand that claiming that NASA is "incompetent" after keeping rover up for 15 years past mission parameters is delusional. Perhaps you need to clarify what incompetent means. Now let's go to your second rant: how much money does NASA get and for what? I'm pretty sure you have very little clue.

    --
    Well, there's spam egg sausage and spam, that's not got much spam in it.
  11. Re:Why the hell by Anonymous Coward · · Score: 1, Informative

    I mean, robot doesn't get any response from home for some time, switch transponder, do a hard reset, whatever.

    Well its pretty damn hard for a robot to phone home with no electricity.
    One of the possibilities is the rover's solar panels got covered in dust and isn't getting enough power to do anything. It's also possible during the Martian winter the batteries depleted so deeply that pretty much everything froze solid.

    Why would they have to instruct it to do something the robot should be able to figure out by itself?

    I see you've never had a complicated piece of hardware or software fail on you. Most missions like this will send the device into a safe mode if there is a major issue waiting for commands as for what to do. Sometimes the best option in those cases is to wait for more input instead of possibly damaging the equipment.

    That said, they've kept a rover functioning on Mars for a bit over 14 years...the planned mission duration was 3 months. I think they maybe did something correct here. Also they learned from the MER
    program for future missions: don't rely on solar power on Mars. That's why Curiosity is powered by RTGs.

  12. You have Too Limited A View by Crashmarik · · Score: 1

    Jobs in their state is good, jobs for their relatives is better, non profits they can be on the board of and get paid for doing nothing DOUBLE PLUS GOOD

  13. Question by Areyoukiddingme · · Score: 1

    I have a question for anyone who has read more about survivable systems than I have.

    Does it make sense to design a remotely operated system to attempt to reestablish communication on its own if its primary communication channel is disrupted? Specifically, to do things like what Opportunity is being commanded to do manually, such as trying to use a backup radio, switching to a different frequency radio, and resetting its clock. These seem like the sorts of things that should be automated. It should be rate limited, and aware of how much on board power it has, so it avoids going into an infinite battery draining loop trying desperately to phone home, but shouldn't it actively try to reestablish communication?

    1. Re:Question by Tablizer · · Score: 1

      How would it know its primary communication channel(s) is disrupted? You'd have to have a receiver active at the same time to verify, which could complicate the logic and drain power. You want the recovery system to have relatively simple logic so that bugs or broken sensors inside of itself don't become a problem.

      And if you depend on a timer to tell you it's been "too long" since you received communication, you have the similar problem of knowing if the clock is bad.

      The recovery system has to consider the possibility of a bad timer (clock), bad transmitter(s), bad receiver(s), bad battery-level sensor, etc., and perhaps combo's.

      Even redundancy has trickiness associated with it. For example, what if the second "spare" sensor gives conflicting readings from the first? How do you know which is right? You can fill it up with AI etc. to better guess, but that takes CPU power, which could drain the battery. And it could make re-creating the problem back on Earth difficult, because mirroring AI is trickier than mirroring traditional "flow chart" logic. Mirroring problems on Earth-based replica probes has proven useful in the past.

  14. Re:It was martians by Tablizer · · Score: 1

    Is there a decent online English-to/from-Jive translator? (They don't call it "jive" anymore, but the alternatives are arguably not PC.)

  15. Re:NASA is incompetant by UnknowingFool · · Score: 1

    So you admit you don't have any clue to how much NASA spends? That seems like the totality of your argument: you don't know but sure you are right.

    --
    Well, there's spam egg sausage and spam, that's not got much spam in it.
  16. Re:NASA is incompetant by UnknowingFool · · Score: 1

    You've posted no points with actual facts and keep asserting things without foundation.

    --
    Well, there's spam egg sausage and spam, that's not got much spam in it.
  17. Re:A series of unlikely events by Tablizer · · Score: 1

    Or an election.

  18. Redundant redundancy by Tablizer · · Score: 2

    I remember reading that there were known spots on the circuit boards such that if that spot cracked due to the cold, the entire rover would fail.

    They were known weak-points which lacked redundancy, but the cost of the avoiding them was considered too high. The rovers have roughly 90% redundancy, but approaching 100% apparently has a steep cost curve.

    For example, at some point the redundant systems have to coordinate with each other to make sure both are not trying to do something at the same time, which could waste power or put noise into instrument readings. These coordination points are not easy to also make redundant. You need redundancy handlers to manage the redundancy handlers in almost a fractal way, requiring redundant "turtles all the way down", filling the rover with bunches of circuits.

  19. ntpd sync time is glacial by bill_mcgonigle · · Score: 1

    They forgot to run ntpdate first on startup?

    --
    My God, it's Full of Source!
    OUTSIDE_IP=$(dig +short my.ip @outsideip.net)