Slashdot Mirror


Lockheed Martin Selects Linux for Missile Defense

m3lt writes "Business Wire is reporting that Concurrent announced today that Lockheed Martin Space Systems has selected RedHawk(TM) Linux as the operating system for their United States Army Theater High Altitude Area Defense (THAAD) program." From the article: "Lockheed Martin selected RedHawk for the THAAD program due to the precision and guaranteed response time of Concurrent's RedHawk Linux real-time operating system. Only RedHawk Linux was able to ensure the high frame rates required in their HIL simulation without frame overruns, thereby ensuring the highest quality of system test."

5 of 532 comments (clear)

  1. THAAD by Karrde712 · · Score: 5, Interesting

    First point. THAAD is actually "Terminal High Altitude Area Defense" and is being developed concurrently between Lockheed Martin and Raytheon.

    I worked on the THAAD project for Raytheon from 1999-2000. Here is the unclassified description of how it functions:

    Upon radar detection of an incoming missile (such as a SCUD) the THAAD missile is launched against it. Unlike earlier technologies for missile defense (such as the PATRIOT*), the THAAD missile does not contain any explosive warhead, instead using the available space and weight for a more sophisticated guidance system. The THAAD warhead contains an active guidance system that will seek the incoming missile and collide with it, destroying the incoming missile with its own warhead.

    Earlier technologies relied on a wide-area warhead that would be detonated once the missile was within a certain diameter about the target, relying on the concussion wave and shrapnel to destroy the missile. This was unsatisfactory as in some circumstances the missile would destroy only the target's propulsion system and allow the undamaged warhead to fall to the ground, resulting in collateral damage.

    *The PATRIOT missile was not designed as an anti-missile weapon, it was in fact designed as an anti-aircraft weapon, but was retasked during Operation: Desert Storm to shoot down SCUD missiles. It was considered very impressive that it worked at all, considering it was designed for use against much slower-moving targets.

    --
    You may treat all information submitted above as wild speculation.
  2. Re:HWIL = Hardware In the Loop by florescent_beige · · Score: 4, Interesting
    Gosh.

    ...a missile is put basically in a 3 axis gyroscope mount...
    The THAAD missile it 20 ft long and weights a ton, putting it in a gymbal would be expensive and pointless because...

    ...projection screen where RADAR images are being projected...
    This is wrong on so many levels. First of all, how does one "project" a radar "image"? Second of all, the THAAD radar is ground-based, not part of the missile. The vehicle is steered to the projected intercept point by commands from the ground. The kill vehicle steers itself to the intercept with an IR seeker.

    Maybe the KV hardware test article is gymbal mounted but again, how does one "project" an IR "image" on a "screen"?

    ...sends a signal to the fins...

    THAAD is exoatmospheric. Fins would be useless. It uses vectored thrust.

    ...A computer program tracks how the missile would have really moved in space...
    See now, if you are modeling the dynamics of the vehicle, why bother actually physically moving it? In this case, you aren't testing the vehicle dymanics, you are imposing them, the only purpose of which would be to exersize the seeker mechanisms (of which the missile has none.) Why not simply vary the seeker's simulated target signal (what you call an "image" projected on a "screen" but which is probaby purely electronic)?

    Modded +5. Lordy.

    --
    Equine Mammals Are Considerably Smaller
  3. Way Back When by jmichaelg · · Score: 5, Interesting
    I worked on an air defense system back in the 70's. It was built for the King of Morroco so he could show off to the other despots in North Africa. It wasn't as if Morocco was seriously threatened by anyone but I guess that having been overrun by the Germans, French and the occasional American task force rescuing a Greek who claimed to be an American, the king was a little concerned. The system consisted of two radars parked on a couple of mountaintops talking to a single cpu which updated a couple of consoles and huge wall screen. Whereas the consoles got the standard cryptic designators for each plane, the wall screen got elaborate detailed descriptions since they were for the king to read. The cpu was the fastest cpu of the time, a 16 mhz behemoth that filled a room.

    The guy I reported to was one of the smartest people I've ever met and fortunately for the project, he was responsible for the software. He'd come into our offices (the only people that worked in cubicles back then were HP employees) and see how we were doing. He'd frequently find us waiting on a compile as the machine was hard pressed to have 30 or so developers using a single computer to compile with. It began to bother him quite a bit because he'd read the design spec which called for the system to handle a couple of 1000 radar returns each minute. As he was technically capable, he sat down one day and wrote a radar simulator that fed radar packets to a "processor." All the processor did was count the number of packets it received and all the radar simulator did was send empty packets. Not a very complicated piece of software but it was enough to show the hardware wasn't going to meet the spec. It couldn't do that simple task, let alone process the packets, draw positions on the controller screens etc.

    He wrote a memo and sent it up the chain. A week passed and no response so he wrote another memo saying the same thing but he changed the memo title. The new title was "I know you're out there - I can hear you breathing." That got his bosses moving and the problem was addressed.

  4. Re:The alternative: Mutual assured destruction by s20451 · · Score: 4, Interesting

    I agree that point (3) is a problem. Points (1) and (2) are technological issues that can be solved with time.

    I think the "cruise missiles and container bombs" argument makes no sense, because these two delivery systems do not have the same potential as ICBMs. A cruise missile is basically a jet aircraft, and we already know how to shoot those down. They also take a relatively long time (i.e., hours) to arrive at their target, giving plenty of warning. As for container bombs, you could use them to attack a city, but you could never get one close enough to a hardened military installation to do significant damage. It would be an effective tool for terrorists, but totally worthless as a military strike. And it would be almost impossible to co-ordinate more than a few simultaneous container-bomb attacks.

    By contrast, ICBMs can be used to attack any target in the world, take around 45 minutes from launch to impact, can be used in co-ordinated attacks of unlimited size, and cannot be stopped with existing technology.

    The promise of missile defence is to make massive nuclear attack obsolete as a weapon of war. I think that is a worthwhile goal.

    --
    Toronto-area transit rider? Rate your ride.
  5. Hardware In the Loop: Been There by cmholm · · Score: 4, Interesting
    The parent for this thread probably doesn't have any first hand experience with HWIL, but s/he has the basic ideas down. Lemme hit the previous bullets:

    Gyroscopic mount: typically, the seeker for the missile (radar, ir, video, whatever) in question is mounted on the gimbals. The rest of the guidance section is in a nearby rack. The reactions of the rest of the missile (fins, motor, body) is simulated in the kinematic codes running on the HWIL simulation computer(s).

    Projection screen: a jargon problem. For Radar: an array of radio frequency feed horns are mounted on a wide hemispheric frame about 50 to 100 feet in front of the seeker, which is at the focal point of their output. By varying the frequency, power, and polarity of the energy from each feed horn, one or more targets can be represented. The simulation computer usually takes care of the radar pulse delay to represent range. Simulated changes in target angle are handled by moving the seeker on it's gimbals.

    IR projection: a "hot" video display, to my experience using an led array no bigger than a laptop display a few feet in front of the seeker. Video: to my experience, either a large front or rear video projection system, or a tv display a few feet in front of the seeker.

    Fins/vectored thrust: in a HWIL system, the aerodynamic controls are usually simulated. The control computer intercepts the commands from the guidance section, and feeds them into the kinematic software for use in the virtual environment.

    Movement in 3D space: Why move the seeker at all? Because it's cheaper than moving the display mechanism (whether radar, ir, or video). The seeker is built to withstand intense shock and vibration, small, and usually weighs anywhere from a few tens to hundreds of pounds. The display system is usually custom built, touchy, and too unwieldy to move in angle or rate in degrees per second needed to represent how a target might present itself. Depending on the scenario, the simulated target may well start 'waaaaaaay off to the side of the seeker's POV. So, throw the seeker on gimbals and move it.

    Before moving into an expensive HWIL lab, the guidance software, or guidance computer and s/w, will have been put thru it's paces on a computer-in-the-loop simulation, where nothing moves except logic states. HWIL is the final stage of integration testing before trying the whole missile out on a test range.

    Just between you, me, and the lamp post, I believe Lockeed won the THAAD contract on price, and the Army has been paying the price for what, twelve years? If (my previous employer) had won this, I assert we'd have a deployable system by now.

    --
    Luke, help me take this mask off ... Just for once, let me butterfly kiss you with my own eyes.