Back to news

November 21, 2018 | International, Aerospace, C4ISR

DARPA: CODE Demonstrates Autonomy and Collaboration with Minimal Human Commands

Ground and flight tests highlight CODE-equipped UASs' ability to collaboratively sense and adapt to locate and respond to unexpected threats and new targets

In a recent test series at Yuma Proving Ground in Arizona, DARPA's Collaborative Operations in Denied Environment (CODE) program demonstrated the ability of CODE-equipped Unmanned Aerial Systems (UASs) to adapt and respond to unexpected threats in an anti-access area denial (A2AD) environment. The UASs efficiently shared information, cooperatively planned and allocated mission objectives, made coordinated tactical decisions, and collaboratively reacted to a dynamic, high-threat environment with minimal communication.

The air vehicles initially operated with supervisory mission commander interaction. When communications were degraded or denied, CODE vehicles retained mission plan intent to accomplish mission objectives without live human direction. The ability for CODE-enabled vehicles to interact when communications are degraded is an important step toward the program goal to conduct dynamic, long-distance engagements of highly mobile ground and maritime targets in contested or denied battlespace.

“The test series expanded on previously demonstrated approaches to low bandwidth collaborative sensing and on-board planning. It demonstrated the ability to operate in more challenging scenarios, where both communications and GPS navigation were denied for extended periods,” said Scott Wierzbanowski, DARPA program manager for CODE.

During the three-week ground and flight test series in a live/virtual/constructive (LVC) environment, up to six live and 24 virtual UASs served as surrogate strike assets, receiving mission objectives from a human mission commander. The systems then autonomously collaborated to navigate, search, localize, and engage both pre-planned and pop-up targets protected by a simulated Integrated Air Defense System (IADS) in communications- and GPS-denied scenarios.

“The demonstrated behaviors are the building blocks for an autonomous team that can collaborate and adjust to mission requirements and a changing environment,” said Wierzbanowski.

The DARPA team also has advanced the infrastructure necessary to support further development, integration, and testing of CODE as it transitions to future autonomous systems.

Achievements include incorporation of third-party autonomy algorithms into the current software build, the creation of a government repository and lab test environment for the CODE algorithms, and the successful demonstration of the Johns Hopkins University Applied Physics Laboratory White Force Network capability to provide constructive threats and effects in an LVC test environment.

CODE's scalable capabilities could greatly enhance the survivability, flexibility, and effectiveness of existing air platforms, as well as reduce the development times and costs of future systems.

Further development of CODE and associated infrastructure will continue under DARPA until the conclusion of the program in spring 2019, followed by full transition of the CODE software repository to Naval Air Systems Command.

https://www.darpa.mil/news-events/2018-11-19

On the same subject

  • Boeing preps for next test of US Navy’s future aerial tanker drone

    August 6, 2020 | International, Aerospace, Naval

    Boeing preps for next test of US Navy’s future aerial tanker drone

    By: David B. Larter WASHINGTON — The U.S. Navy's aircraft carrier-borne tanker drone, the MQ-25 Stingray, is preparing to head into the fall resuming test flights, this time with the crucial fuel store pod attached. The store pod — the same one integrated into the Navy's stalwart F/A-18 Super Hornet for aerial refueling — was recently integrated into the MQ-25 test article under the wing. “When we resume flight testing later this year, we'll have the opportunity to gather test points about the aerodynamics of that pod and the software commands that control it — all happening well before we deliver the Navy's first MQ-25 jet with the same pod,” MQ-25 program director Dave Bujold said in a statement from the aircraft's manufacturer, Boeing. “That early testing and early software development is a big part of supporting the Navy's goal to get MQ-25 to the fleet as quickly as possible,” he added. The engineers will primarily observe the aerodynamics of the pod mounted on the Stingray test article, then seeing how the hose and drogue behave while being dragged behind the airframe. Possible delays In June, Defense News reported that the MQ-25 could face a three-year testing delay if it doesn't get its designated test ships through the required modernizations on time, a possibility the Navy said was remote. Two carriers — Carl Vinson and George H.W. Bush — have limited windows to complete the installation of unmanned aircraft control stations, and if operational commitments intervene, the program could experience significant problems, according to Navy officials and a government watchdog report. “Program officials stated that, among other things, the Navy's potential inability to maintain its schedule commitments could require modifications to the contract that would impact the fixed-price terms,” the Government Accountability Office reported. “Specifically, the Navy faces limited flexibility to install MQ-25 control centers on aircraft carriers. “If the Navy misses any of its planned installation windows, the program would have to extend MQ-25 development testing by up to 3 years. According to officials, such a delay could necessitate a delay to initial capability and result in a cost increase.” The Navy's MQ-25 Stingray aerial refueling drone took its first flight Sept. 19, a historic step toward integrating an unmanned aircraft into the service's powerful strike arm. Navy officials say a three-year delay is “extremely unlikely”; however, the Navy has struggled in recent years to balance its modernization schedules with operational commitments, a problem that its “Optimized Fleet Response Plan” deployment rotation scheme was supposed to address. Ultimately, a delay would further push back the Navy's ability to extend its carrier air wing's range through unmanned tanking, critical to keeping the service's powerful strike arm relevant against long-range guided munitions. https://www.defensenews.com/naval/2020/07/24/boeing-preparing-for-the-next-big-step-testing-the-us-navys-new-aerial-tanker-drone

  • France orders 3,000 camouflage nets for cloaking foxhole radio signals

    February 28, 2024 | International, Land

    France orders 3,000 camouflage nets for cloaking foxhole radio signals

    Detection by way of electromagnetic emissions is a constant danger faced by Ukrainian forces in their defense against Russian invaders, analysts have said.

  • EXCLUSIVE DoD Seeks $2.9B For Hypersonics In 2021

    April 16, 2020 | International, Aerospace, Naval

    EXCLUSIVE DoD Seeks $2.9B For Hypersonics In 2021

    While Army and Navy spending nearly double, Air Force and independent agency spending drops almost 40 percent. By THERESA HITCHENS and SYDNEY J. FREEDBERG JR.on April 14, 2020 at 4:07 PM Breaking Defense graphic from DoD data WASHINGTON: The Pentagon is asking Congress for $2.865 billion for hypersonic weapons in 2021, up not quite 14 percent from a 2020 total of $2.508 billion, according to DoD budget documents obtained by Breaking Defense. Army and Navy hypersonics spending would nearly double in 2021. Each increases by 95 percent. But that's offset by a 40 percent reduction in spending by independent defense agencies like DARPA, which are handing off much of the work to the services as programs move from basic research to prototyping, and a 35 percent cut in the Air Force, which cancelled one of its two major hypersonics programs. Hypersonic weapons fall into two main categories. The more conservative approach — relatively speaking, since these are all bleeding-edge weapons — is known as boost-glide, because it uses a conventional rocket booster to accelerate the weapon to hypersonic speed, after which the glide body containing the warhead detaches from the booster and coasts, skipping along the upper limits of the atmosphere like a stone across a pond. The Navy and Army programs are both boost-glide weapons, and the two services are using a common booster rocket, built by the Navy, and a Common Glide Body, built by the Army and lead contractor Dynetics. The Navy also plans to customize the weapon to launch from submarines, while the Army version will fire from trucks, a much simpler engineering challenge. Notional flight paths of hypersonic boost-glide missiles, ballistic missiles, and cruise missiles. (CSBA graphic) The Air Force had two boost-glide programs. HCSW (pronounced hacksaw), the Hypersonic Conventional Strike Weapon, which would have used a modified version of Army-built Common Glide Body. But the Air Force decided to cancel HCSW and focus its efforts on the more compact ARRW (arrow), the Air-launched Rapid Response Weapon. (Both HCSW and ARRW are Lockheed Martin programs). Finally, DARPA is working on an alternative to boost-glide: air-breathing hypersonic cruise missiles that spend their entire flight in the atmosphere, with their engines providing continuous thrust. That allows the engine to take in oxygen from the air as it flies, rather carrying bulky oxygen tanks — as a boost-glide weapon's rocket boosters do. But flying through the atmosphere also creates friction, heating up an air-breathing hypersonic weapon in ways a boost-glide design, which spends most of its time in a near-vacuum, doesn't have to worry about. Since the air-breathing technology is more ambitious, it remains a DARPA effort for now, with two contracts: Northrup Grumman and Raytheon are working on the Hypersonic Air-Breathing Weapons Concept (HAWC) and Lockheed Martin on the Hypersonic Strike Weapon air-breathing (HSW-ab). While these programs will probably transition to the Air Force in the near future, they don't yet have their own budget lines in the documents we obtained; they're almost certainly folded into the figure for independent defense agencies. Breaking Defense graphic from DoD data The documents summed up a portfolio of programs the Pentagon now refers to as “missile defense and defeat,” a euphemism which combines offensive and defensive programs. As Breaking D readers know, DoD has taken to lumping long-range strike efforts known as left-of-launch into its budget reporting on missile defense, with a total of $3.26 billion included for such activities in the 2021 request. Spending on hypersonic weapons is listed as a subcategory of “nontraditional” missile defense funding, defined as: funding for missile defeat efforts outside of the above missile defense efforts. This captures ‘left-of launch' efforts that defeat missiles before they take flight via high-speed strike (e.g. Conventional Prompt Strike) or cyber-attack operations. We combed through the document to extract the offensive hypersonics programs from traditional missile defense, directed energy (lasers), cyber warfare, and other means of neutralizing enemy missile salvos. The document broke down 2020 funding and 2021 requests for Army, Navy, Air Force and defense-wide, both for foundational science, technology, test and evaluation (STTE) as well as for each individual service's programs to develop hypersonic missiles. Meanwhile, the Missile Defense Agency and the Space Development Agency are working on a space-based sensor to detect adversary hypersonic and cruise missiles, under the Hypersonic & Ballistic Tracking Space Sensor (HBTSS) Prototyping program. The Navy is the big spender in 2021, with the bulk of the funds slated for the Conventional Prompt Strike (CPS), a submarine-launched boost-glide weapon set to enter service in 2025. Its total hypersonic budget in 2020 is set at $526 million, but jumping to just over $1 billion in the 2021 request. (DoD agencies spent $31 million in 2020 wrapping up their portion of CPS, but the whole program will be in the Navy budget as of 2021). The Air Force's 2020 budget includes $848 million, the budget documents show, but that drops in the 2021 request to $554 million due to the cancellation of HCSW. The Air-launched Rapid Response Weapon (ARRW) is funded at $286 million in 2020 and the service is asking for $382 million in 2021. As for the Army, the documents put 2020 spending at $441 million, and the 2021 request is for $859 million. That increase is driven by a big jump in the budget for the land-based version of the common Army-Navy boost-glide weapon, the Long Range Hypersonic Weapon (LRHW), from $409 million in 2020 to $801 million in 2021. (This LRHW line item also includes some work on the cancelled Mobile Intermediate Range Missile. DoD never said publicly what MIRM would be, or even whether it would be a hypersonic missile or a conventional ballistic missile, and it appears to have been stillborn). The documents also show the Army spending $19 million on the Operational Fires ground-launched hypersonic missile program in 2020, and asking for another $28 million in 2021. OpFires is a joint program with DARPA. Lockheed Martin scored a $31.9 million contract from DARPA in January to begin Phase 3 Weapon System Integration under the program. https://breakingdefense.com/2020/04/exclusive-dod-asks-2-9b-for-hypersonics-in-2021

All news