Jellyfish-like robot, developed with Navy funds, refuels itself with hydrogen and oxygen extracted from the sea. The goal: Perpetual ocean surveillance.
NASA's Blue Marble: 50 Years Of Earth Imagery
(click image for larger view and for slideshow)
Scientists at the University of Texas at Dallas and Virginia Tech have built a jellyfish-inspired robot that can refuel itself, offering the possibility of perpetual ocean surveillance.
Like Slugbot, a robot designed to be able to hunt garden slugs and devour them for fuel, Robojelly, as the machine is called, is self-sustaining. It extracts hydrogen and oxygen gases from the sea to keep itself running.
"We've created an underwater robot that doesn't need batteries or electricity," Yonas Tadesse, assistant professor of mechanical engineering at UT Dallas, told the UT Dallas news service. "The only waste released as it travels is more water."
The robot offers one way around a problem that continues to vex researchers developing autonomous machines: operational limitations imposed by the need for frequent refueling. Scientists at Sandia National Laboratories and Northrop Grumman last year concluded that nuclear power would extend the capabilities of aerial drones but couldn't be implemented due to political considerations. The U.S. government presumably would rather avoid the political outrage that would follow from a downed nuclear drone.
A self-sustaining surveillance bot that doesn't involve hazardous materials and doesn't pollute would be much more politically palatable, not to mention operationally useful.
Robojelly looks as if it could be related to a novelty umbrella hat, except that it has two hemispherical canopies, stacked one on top of another (the video embedded below depicts an earlier single-canopy version). These bell-like structures are made of silicone and are connected to artificial muscles that contract when heated. The contractions, like those in a real jellyfish, propel the device.
The muscles are made of a nickel-titanium alloy encased in carbon nanotubes, coated in platinum, and housed in a casing. The chemical reaction arising from contact between the mixture of hydrogen and oxygen and the platinum generates heat, which causes the artificial muscles to contract and move the silicone canopies while expelling water.
Tadesse says the next step in the project is to revise the device's legs so it can move in different directions. Right now, Robojelly's fixed supports allow it to move in only one direction.
Robojelly was funded by the Office of Naval Research, which has an obvious interest in monitoring the seas. In addition to scanning the waves, Tadesse suggests the device could be used to check the water for pollutants.
Nominate your company for the 2012 InformationWeek 500--our 24th annual ranking of the nation's very best business technology innovators. Deadline is April 27. Organizations with $250 million or more in revenue may apply for the 2012 InformationWeek 500 now.
Published: 2014-11-27 The SSL VPN implementation in Cisco Adaptive Security Appliance (ASA) Software 9.3(.2) and earlier does not properly allocate memory blocks during HTTP packet handling, which allows remote attackers to cause a denial of service (memory consumption) via crafted packets, aka Bug ID CSCuq68888.
Published: 2014-11-27 Cross-site request forgery (CSRF) vulnerability in IBM Security QRadar SIEM and QRadar Risk Manager 7.1 before MR2 Patch 9 and 7.2 before 7.2.4 Patch 1, and QRadar Vulnerability Manager 7.2 before 7.2.4 Patch 1, allows remote attackers to hijack the authentication of arbitrary users for requests tha...
Published: 2014-11-27 IBM Security QRadar SIEM and QRadar Risk Manager 7.1 before MR2 Patch 9 and 7.2 before 7.2.4 Patch 1, and QRadar Vulnerability Manager 7.2 before 7.2.4 Patch 1, allow remote attackers to hijack sessions via unspecified vectors.
Published: 2014-11-27 IBM Security QRadar SIEM and QRadar Risk Manager 7.1 before MR2 Patch 9 and 7.2 before 7.2.4 Patch 1, and QRadar Vulnerability Manager 7.2 before 7.2.4 Patch 1, allow remote attackers to obtain sensitive cookie information by sniffing the network during an HTTP session.
Published: 2014-11-27 resolv.c in the DNS resolver in uIP, and dns.c in the DNS resolver in lwIP 1.4.1 and earlier, does not use random values for ID fields and source ports of DNS query packets, which makes it easier for man-in-the-middle attackers to conduct cache-poisoning attacks via spoofed reply packets.