F-22 Raptor: Schermata Blu..riavviare il sistema..

[dantes76]

Six Lockheed F-22 Raptors have Y2K-esque glitch of their own over the Pacific

Lockheed’s F-22 Raptor is the most advanced fighter in the world with its stealth capabilities, advanced radar, state of the art weapons systems and ultra-efficient turbofans which allow the F-22 to "supercruise" at supersonic speeds without an afterburner. The Raptor has gone up against the best that the US Air Force and Navy has to offer taking out F-15s, F-16s and F/A-18 Super Hornets during simulated war games in Alaska. The Raptor-led "Blue Air" team was able to rack up an impressive 241-to-2 kill ratio during the exercise against the "Red Air" threat -- the two kills on the blue team were from the 30-year old F-15 teammates and not the new Raptors.

But while the simulated war games were a somewhat easy feat for the Raptor, something more mundane was able to cripple six aircraft on a 12 to 15 hours flight from Hawaii to Kadena Air Base in Okinawa, Japan. The U.S. Air Force's mighty Raptor was felled by the International Date Line (IDL).

When the group of Raptors crossed over the IDL, multiple computer systems crashed on the planes. Everything from fuel subsystems, to navigation and partial communications were completely taken offline. Numerous attempts were made to "reboot" the systems to no avail.

Luckily for the Raptors, there were no weather issues that day so visibility was not a problem. Also, the Raptors had their refueling tankers as guide dogs to "carry" them back to safety. "They needed help. Had they gotten separated from their tankers or had the weather been bad, they had no attitude reference. They had no communications or navigation," said Retired Air Force Major General Don Shepperd. "They would have turned around and probably could have found the Hawaiian Islands. But if the weather had been bad on approach, there could have been real trouble.”

"The tankers brought them back to Hawaii. This could have been real serious. It certainly could have been real serious if the weather had been bad," Shepperd continued. "It turned out OK. It was fixed in 48 hours. It was a computer glitch in the millions of lines of code, somebody made an error in a couple lines of the code and everything goes."

Luckily for the pilots behind the controls of the Raptors, they were not involved in a combat situation. Had they been, it could have been a disastrous folly by the U.S. Air Force to have to admit that their aircraft which cost $125+ million USD apiece were knocked out of the sky due to a few lines of computer code. "And luckily this time we found out about it before combat. We got it fixed with tiger teams in about 48 hours and the airplanes were flying again, completed their deployment. But this could have been real serious in combat," said Shepperd.

http://www.dailytech.com/article.aspx?newsid=6225

Traduzione
http://64.233.179.104/translate_c?u=...&hl=it&ie=UTF8

Altri articoli:
Software Bug Halts F-22 Flight
http://it.slashdot.org/article.pl?si...38217&from=rss

[fastezzZ]

forse gli hanno installato vista da poco

[Solertes]

ma premere CTRL+ALT+CANC no eh?

Meno male che questo, perchè ritenuto troppo avanzato, non viene venduto a nessuno.....speriamo che il JSF sia più affidabile

[maxsona]

Lockheed fixing computer glitches in 87 F-22s

By DONNA BORAK
The Associated Press
Published on: 02/27/07

Washington — The Air Force on Tuesday said it is fixing technological glitches in roughly 87 Marietta-built F-22 fighters after several aircraft computer systems were disabled earlier this month during a test flight.

The six stealth fighter jets — built by prime contractor Lockheed Martin Corp. and partner Boeing Co. — were participating in an inaugural 12-hour test flight from Hawaii to Kadena Air Base in Okinawa, Japan on Feb. 10 when a "navigation anomaly" maimed several computer systems on the aircraft, an Air Force colonel said.

The computer glitch, which occurred as aircraft crossed the International Date Line, crippled navigation systems and hindered communications.

The incident was first reported by CNN on Feb. 17. On Tuesday, the Air Force provided more details about the incident.

One pilot was able to contact contractor Lockheed Martin to troubleshoot the error during the flight, the Air Force said. Several pilots attempted to reboot the system with no success and returned to Hawaii with the help of aerial refueling tankers as a safety precaution.

Engineers were able to locate the problem within hours and fixed the glitch in a matter of days on the aircraft, according to the Air Force.

Lockheed Martin, which assembles the jets at its Marietta plant, declined to provide further comment on additional costs of the upgrades.

It is common for pilots to experience operational problems during initial deployments, said Loren Thompson, a defense analyst at the Virginia-based Lexington Institute.

A senior Air Force officer told reporters on Tuesday there are no plans to conduct further testing on the F-22 Raptor.

"Until you really fly the airplane and do something that's when the rubber hits the road. Industry are developing any kind of computer or airplane system, and you will see there is no substitute for flying something," Col. Tom Bergeson, Operations Group Commander at the First Fighter Wing, told reporters on a conference call from Langley Air Force Base, Va.

The Raptor, built to fight the now defunct Soviet Union and worth roughly $70 billion including development costs, has endured periodic delays and political attacks. Initial plans called for 750, but only 183 are now slated to be built under the proposed 2007 fiscal defense budget.

The Defense Department is requesting $2.78 billion in the 2007 budget under review by Congress.

Bethesda, Md.-based Lockheed is responsible for the majority of the airframe, weapons systems and final assembly, while partner Chicago-based Boeing is tasked with providing the aircraft with wings, fuselage, avionics integration and training for pilots and maintenance.

[Athlon]

Pessima scelta software quella di basarsi sulla data convenzionale (infatti appena si oltrepassa il confine di data il software andava in crisi)


nei computer affidabili si usa la datazione assoluta

[Paganetor]

ricordo il casino successo con non so quale sonda/satellite... quando il controllo missione è passato da un paese con unità anglosassoni a uno con unità metriche hanno semplicemente cambiato inch con cm senza convertire i numeri...

KABUM!

[jumpjack]

Originariamente inviato da Paganetor

ricordo il casino successo con non so quale sonda/satellite... quando il controllo missione è passato da un paese con unità anglosassoni a uno con unità metriche hanno semplicemente cambiato inch con cm senza convertire i numeri...

KABUM!

vogliamo parlare dell'Ariane 5, che si è autodistrutto in volo (costo: 1 miliardo di dollari) perche' un errore del SW effettuava una conversione sbagliata tra numeri ("overflow at data conversion from 64-bit floating point to 16-bit integer")?
http://www.sat-index.com/launchfailures/1996-06-04.html

A proposito di bachi software.... tempo fa ho letto in un romanzo (mi pare di Stephen King) di un tizio che si lamentava perche' il suo nuovo Maggiolino Volkswagen aveva un baco tale per cui, se restava spento per troppo tempo, il computer di bordo pensava che la macchina fosse abbandonata e "staccava tutto", o roba del genere....
Qualcuno ne ha mai sentito parlare?

[dsx2586]

Originariamente inviato da Paganetor

ricordo il casino successo con non so quale sonda/satellite... quando il controllo missione è passato da un paese con unità anglosassoni a uno con unità metriche hanno semplicemente cambiato inch con cm senza convertire i numeri...

KABUM!

Il Mars Climate Orbiter

[Paganetor]

Originariamente inviato da dsx2586

Il Mars Climate Orbiter

ecco, quello...