"It's only software!!"
Seems like the report from the JPL Special Review Board on the Loss of the
Mars Polar Lander blames the software!
They clearly state (section 7.7.2 in pdf file #4) that "The touchdown
sensors characteristically generate a false momentary signal at leg
deployment. This behavior was understood and the flight software was
required to ignore these events, however, the requirement did not
specifically describe these events, and consequently, the software
designers did not properly account for them."
Thus it seems like a project communication problem. Not unusual in my past
experience! Although, like someone said, "that's a 'management' problem".
Someone, probably the Project leader/Engineer should have made sure that
there was appropriate hardware/software team communication.
Someone else said "Lack of testing" When I was responsible for product
design (quite a while ago!) that was my main emphases--"test, test & then
test again! Also, we tried to use independent test persons-not the
designers!
However, testing a small electronic remote control system is a lot easier
and far lest costly than testing a Mars Lander, although the lack of good
testing was also far less consequential! If I remember correctly, the
failure of the initial Hubble mirror could also have been "caught" if
expensive testing had been approved!
In summary, this Mars Lander experience just reinforces for me, that
although projects can and should be organized so that detailed reviews
amongst the designers are a regular occurrence, there really is no
substitute for thorough testing! But I guess, EMC engineers already know
that!
Tony
Colorado.
-------------------------------------------
This message is from the IEEE EMC Society Product Safety
Technical Committee emc-pstc discussion list.
To cancel your subscription, send mail to:
majord...@ieee.org
with the single line:
unsubscribe emc-pstc
For help, send mail to the list administrators:
Jim Bacher: jim_bac...@mail.monarch.com
Michael Garretson: pstc_ad...@garretson.org
For policy questions, send mail to:
Richard Nute: ri...@ieee.org
