Stories
Slash Boxes
Comments

SoylentNews is people

SoylentNews is powered by your submissions, so send in your scoop. Only 15 submissions in the queue.
posted by cmn32480 on Thursday March 24 2016, @08:57AM   Printer-friendly
from the flushing-your-tax-dollars dept.

The Lockheed Martin F-35 Lightning II multirole fighter plane has numerous software and hardware flaws. So many, in fact, that it won't be ready to deploy before 2019:

The F-35 multirole fighter won't be close to ready before 2019, the US House Armed Services Committee was told on Wednesday. The aircraft, which is supposed to reinvigorate the American military's air power, is suffering numerous problems, largely down to flaws in the F-35's operating system. These include straightforward code crashes, having to reboot the radar every four hours, and serious security holes in the code.

Michael Gilmore, the Pentagon's director of operational test and evaluation, reported that the latest F-35 operating system has 931 open, documented deficiencies, 158 of which are Category 1 – classified as those that could cause death, severe injury, or severe illness. "The limited and incomplete F-35 cybersecurity testing accomplished to date has nonetheless revealed deficiencies that cannot be ignored," Gilmore said in his testimony [PDF]. "Cybersecurity testing on the next increment of ALIS [Autonomic Logistics Information System] – version 2.0.2 – is planned for this fall, but may need to be delayed because the program may not be able to resolve some key deficiencies and complete content development and fielding as scheduled."

He reported that around 60 per cent of aircraft used for testing were grounded due to software problems. He cited one four-aircraft exercise that had to be cancelled after two of the four aircraft aborted "due to avionics stability problems during startup."


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: 1) by anubi on Saturday March 26 2016, @04:54AM

    by anubi (2828) on Saturday March 26 2016, @04:54AM (#323170) Journal

    Its got too much like out tax codes... by now they are so complex even the IRS can't seem to understand it either.

    I am having the same conniptions trying to figure out an HMI. Many years ago, I was involved in a MODBUS PLD implementation in an oil refinery. I am revisiting that now as I am attempting to use a modern Human-Machine-Interface panel as a "pushbutton replacer" for Arduino. I want all the functions of a traditional switchboard panel - knobs, meters, buttons, indicator lights, switches, graphs, and the like, but I don't want to do all the metalwork or mess with all those mechanical parts... I wanna use a touch panel and simply draw the graphics and functionality I want.

    I really do not need a real mechanical d'arsonval meter to display fuel level, but I would love to have the number presented to me graphically.
    My old Modbus was so simple. I would have simply instantiated meters, switches, whatever, given them an address, then written or read data to/from that address. BOOL's and INT16's. The HMI would have either returned the state of switches, or displayed the data given as numerical text, meter, bar, graph, whatever. The new ones are so damned complicated I am just about ready to abandon the whole shebang. Why does everybody have to use a different protocol? By God, Modbus was open source! ( Don't answer that... I already know... copyright workarounds and attempts to lock in customers by keeping them ignorant - deliberately - by confuscated codes ).

    --
    "Prove all things; hold fast that which is good." [KJV: I Thessalonians 5:21]