Tag Archives: shows

#439612 Boston Dynamics’ latest video ...

Boston Dynamics, the company known for its robotic dogs, now has a humanoid robot capable of doing gymnastics. Continue reading

Posted in Human Robots

#439608 Atlas Shows Most Impressive Parkour ...

Boston Dynamics has just posted a couple of new videos showing their Atlas humanoid robot doing some of the most impressive parkour we've yet seen. Let's watch!

Parkour is the perfect sandbox for the Atlas team at Boston Dynamics to experiment with new behaviors. In this video our humanoid robots demonstrate their whole-body athletics, maintaining its balance through a variety of rapidly changing, high-energy activities. Through jumps, balance beams, and vaults, we demonstrate how we push Atlas to its limits to discover the next generation of mobility, perception, and athletic intelligence.There are a couple of new and exciting things in this video. First, Atlas is doing some serious work with its upper body by vaulting over that bar. It's not supporting its entire weight with one arm, since it's jumping, but it's doing what looks like some fairly complex balancing and weight management using all four of its limbs at once. Most of what we've seen from Atlas up to this point has been lower body focused, and while the robot has used its arms for forward rolls and stuff, those moves have been simpler than what we're seeing here. Aaron Saunders, Boston Dynamics' VP of Engineering, suggested to us earlier this year that the Atlas team would be working on more upper-body stuff, it looks like they're now delivering. We're expecting that Atlas will continue to improve in this direction, and that at some point it'll be able to do the equivalent of a pull-up, which will open up a much wider variety of behaviors.
The second big new thing is that Atlas is now leveraging perception much more heavily, according to Scott Kuindersma, the Atlas team lead at Boston Dynamics, who wrote about it in a blog post:
“Atlas's moves are driven by perception now, and they weren't back then,” Kuindersma explains. “For example, the previous floor routine and dance videos were about capturing our ability to create a variety of dynamic moves and chain them together into a routine that we could run over and over again. In that case, the robot's control system still has to make lots of critical adjustments on the fly to maintain balance and posture goals, but the robot was not sensing and reacting to its environment.”
In this iteration of parkour, the robot is adapting behaviors in its repertoire based on what it sees. This means the engineers don't need to pre-program jumping motions for all possible platforms and gaps the robot might encounter. Instead, the team creates a smaller number of template behaviors that can be matched to the environment and executed online.This is a pretty big deal. Without perception, Atlas was running its routines blind—as long as the environment was kept more or less completely static, the robot would do okay, but obviously that's a major limitation. What Atlas is doing in this new video is still somewhat limited, in the sense that it's still relying on template behaviors created by humans rather than doing true dynamic planning, but this represents a lot of progress.
One other thing that's worth paying attention to is how Boston Dynamics thinks of humanoid robots:
“Humanoids are interesting from a couple perspectives,” Kuindersma says. “First, they capture our vision of a go-anywhere, do-anything robot of the future. They may not be the best design for any particular task, but if you wanted to build one platform that could perform a wide variety of physical tasks, we already know that a human form factor is capable of doing that.”This tends to be the justification for humanoid robots, along with the idea that you need a humanoid form factor to operate in human environments. But Kuindersma is absolutely right when he says that humanoids may not be the best design for any particular task, and at least in the near term, practical commercial robots tend not to be generalists. Even Boston Dynamic's dog-like robot Spot, with its capable legged mobility, is suited primarily to a narrow range of specific tasks—it's great for situations where legs are necessary, but otherwise it's complex and expensive and wheels often do better. I think it's very important that Boston Dynamics is working towards a go-anywhere, do-anything robot, but it's also important to keep expectations in check, and remember that even robots like Atlas are (I would argue) a decade or more away from this generalist vision.
Meanwhile, Boston Dynamics seems, for better or worse, to be moving away from their habit of surprise posting crazy robot videos with zero explanation. Along with the new parkour video, Boston Dynamics has put together a second behind the scenes video:

Can I just say that I love how absolutely trashed the skins on these robots look? That's how you know good work is getting done.

There's a bunch more detail in this blog post, and we sent Boston Dynamics a couple of questions, too. We'll update this post when we hear back later today. Continue reading

Posted in Human Robots

#439592 Robot Shows How Simple Swimming Can Be

Lots of robots use bioinspiration in their design. Humanoids, quadrupeds, snake robots—if an animal has figured out a clever way of doing something, odds are there's a robot that's tried to duplicate it. But animals are often just a little too clever for the robots that we build that try to mimic them, which is why researchers at
Swiss Federal Institute of Technology Lausanne in Switzerland (EPFL) are using robots to learn about how animals themselves do what they do. In a paper published today in Science Robotics, roboticists from EPFL's Biorobotics Laboratory introduce a robotic eel that leverages sensory feedback from the water it swims through to coordinate its motion without the need for central control, suggesting a path towards simpler, more robust mobile robots.

The robotic eel—called AgnathaX—is a descendant of
AmphiBot, which has been swimming around at EPFL for something like two decades. AmphiBot's elegant motion in the water has come from the equivalent what are called central pattern generators (CPGs), which are sequences of neural circuits (the biological kind) that generate the sort of rhythms that you see in eel-like animals that rely on oscillations to move. It's possible to replicate these biological circuits using newfangled electronic circuits and software, leading to the same kind of smooth (albeit robotic) motion in AmphiBot.

Biological researchers had pretty much decided that CPGs explained the extent of wiggly animal motion, until it was discovered you can chop an eel's spinal cord in half, and it'll somehow maintain its coordinated undulatory swimming performance. Which is kinda nuts, right? Obviously, something else must be going on, but trying to futz with eels to figure out exactly what it was isn't, I would guess, pleasant for either researchers or their test subjects, which is where the robots come in. We can't make robotic eels that are exactly like the real thing, but we can duplicate some of their sensing and control systems well enough to understand how they do what they do.

AgnathaX exhibits the same smooth motions as the original version of AmphiBot, but it does so without having to rely on centralized programming that would be the equivalent of a biological CPG. Instead, it uses skin sensors that can detect pressure changes in the water around it, a feature also found on actual eels. By hooking these pressure sensors up to AgnathaX's motorized segments, the robot can generate swimming motions even if its segments aren't connected with each other—without a centralized nervous system, in other words. This spontaneous syncing up of disconnected moving elements is called entrainment, and the best demo of it that I've seen is this one, using metronomes:

UCLA Physics

The reason why this isn't just neat but also useful is that it provides a secondary method of control for robots. If the centralized control system of your swimming robot gets busted, you can rely on this water pressure-mediated local control to generate a swimming motion. And there are applications for modular robots as well, since you can potentially create a swimming robot out of a bunch of different physically connected modules that don't even have to talk to each other.

For more details, we spoke with
Robin Thandiackal and Kamilo Melo at EPFL, first authors on the Science Robotics paper.

IEEE Spectrum: Why do you need a robot to do this kind of research?

Thandiackal and Melo: From a more general perspective, with this kind of research we learn and understand how a system works by building it. This then allows us to modify and investigate the different components and understand their contribution to the system as a whole.

In a more specific context, it is difficult to separate the different components of the nervous system with respect to locomotion within a live animal. The central components are especially difficult to remove, and this is where a robot or also a simulated model becomes useful. We used both in our study. The robot has the unique advantage of using it within the real physics of the water, whereas these dynamics are approximated in simulation. However, we are confident in our simulations too because we validated them against the robot.

How is the robot model likely to be different from real animals? What can't you figure out using the robot, and how much could the robot be upgraded to fill that gap?

Thandiackal and Melo: The robot is by no means an exact copy of a real animal, only a first approximation. Instead, from observing and previous knowledge of real animals, we were able to create a mathematical representation of the neuromechanical control in real animals, and we implemented this mathematical representation of locomotion control on the robot to create a model. As the robot interacts with the real physics of undulatory swimming, we put a great effort in informing our design with the morphological and physiological characteristics of the real animal. This for example accounts for the scaling, the morphology and aspect ratio of the robot with respect to undulatory animals, and the muscle model that we used to approximately represent the viscoelastic characteristics of real muscles with a rotational joint.

Upgrading the robot is not going to be making it more “biological.” Again, the robot is part of the model, not a copy of the real biology. For the sake of this project, the robot was sufficient, and only a few things were missing in our design. You can even add other types of sensors and use the same robot base. However, if we would like to improve our robot for the future, it would be interesting to collect other fluid information like the surrounding fluid speed simultaneously with the force sensing, or to measure hydrodynamic pressure directly. Finally, we aim to test our model of undulatory swimming using a robot with three-dimensional capabilities, something which we are currently working on.

Upgrading the robot is not going to be making it more “biological.” The robot is part of the model, not a copy of the real biology.

What aspects of the function of a nervous system to generate undulatory motion in water aren't redundant with the force feedback from motion that you describe?

Thandiackal and Melo: Apart from the generation of oscillations and intersegmental coupling, which we found can be redundantly generated by the force feedback, the central nervous system still provides unique higher level commands like steering to regulate swimming direction. These commands typically originate in the brain (supraspinal) and are at the same time influenced by sensory signals. In many fish the lateral line organ, which directly connects to the brain, helps to inform the brain, e.g., to maintain position (rheotaxis) under variable flow conditions.

How can this work lead to robots that are more resilient?

Thandiackal and Melo: Robots that have our complete control architecture, with both peripheral and central components, are remarkably fault-tolerant and robust against damage in their sensors, communication buses, and control circuits. In principle, the robot should have the same fault-tolerance as demonstrated in simulation, with the ability to swim despite missing sensors, broken communication bus, or broken local microcontroller. Our control architecture offers very graceful degradation of swimming ability (as opposed to catastrophic failure).

Why is this discovery potentially important for modular robots?

Thandiackal and Melo: We showed that undulatory swimming can emerge in a self-organized manner by incorporating local force feedback without explicit communication between modules. In principle, we could create swimming robots of different sizes by simply attaching independent modules in a chain (e.g., without a communication bus between them). This can be useful for the design of modular swimming units with a high degree of reconfigurability and robustness, e.g. for search and rescue missions or environmental monitoring. Furthermore, the custom-designed sensing units provide a new way of accurate force sensing in water along the entirety of the body. We therefore hope that such units can help swimming robots to navigate through flow perturbations and enable advanced maneuvers in unsteady flows. Continue reading

Posted in Human Robots

#439100 Video Friday: Robotic Eyeball Camera

Video Friday is your weekly selection of awesome robotics videos, collected by your Automaton bloggers. We’ll also be posting a weekly calendar of upcoming robotics events for the next few months; here's what we have so far (send us your events!):

RoboSoft 2021 – April 12-16, 2021 – [Online Conference]
ICRA 2021 – May 30-5, 2021 – Xi'an, China
RoboCup 2021 – June 22-28, 2021 – [Online Event]
DARPA SubT Finals – September 21-23, 2021 – Louisville, KY, USA
WeRobot 2021 – September 23-25, 2021 – Coral Gables, FL, USA
Let us know if you have suggestions for next week, and enjoy today's videos.

What if seeing devices looked like us? Eyecam is a prototype exploring the potential future design of sensing devices. Eyecam is a webcam shaped like a human eye that can see, blink, look around and observe us.

And it's open source, so you can build your own!

[ Eyecam ]

Looks like Festo will be turning some of its bionic robots into educational kits, which is a pretty cool idea.

[ Bionics4Education ]

Underwater soft robots are challenging to model and control because of their high degrees of freedom and their intricate coupling with water. In this paper, we present a method that leverages the recent development in differentiable simulation coupled with a differentiable, analytical hydrodynamic model to assist with the modeling and control of an underwater soft robot. We apply this method to Starfish, a customized soft robot design that is easy to fabricate and intuitive to manipulate.

[ MIT CSAIL ]

Rainbow Robotics, the company who made HUBO, has a new collaborative robot arm.

[ Rainbow Robotics ]

Thanks Fan!

We develop an integrated robotic platform for advanced collaborative robots and demonstrates an application of multiple robots collaboratively transporting an object to different positions in a factory environment. The proposed platform integrates a drone, a mobile manipulator robot, and a dual-arm robot to work autonomously, while also collaborating with a human worker. The platform also demonstrates the potential of a novel manufacturing process, which incorporates adaptive and collaborative intelligence to improve the efficiency of mass customization for the factory of the future.

[ Paper ]

Thanks Poramate!

In Sevastopol State University the team of the Laboratory of Underwater Robotics and Control Systems and Research and Production Association “Android Technika” performed tests of an underwater anropomorphic manipulator robot.

[ Sevastopol State ]

Thanks Fan!

Taiwanese company TCI Gene created a COVID test system based on their fully automated and enclosed gene testing machine QVS-96S. The system includes two ABB robots and carries out 1800 tests per day, operating 24/7. Every hour 96 virus samples tests are made with an accuracy of 99.99%.

[ ABB ]

A short video showing how a Halodi Robotics can be used in a commercial guarding application.

[ Halodi ]

During the past five years, under the NASA Early Space Innovations program, we have been developing new design optimization methods for underactuated robot hands, aiming to achieve versatile manipulation in highly constrained environments. We have prototyped hands for NASA’s Astrobee robot, an in-orbit assistive free flyer for the International Space Station.

[ ROAM Lab ]

The new, improved OTTO 1500 is a workhorse AMR designed to move heavy payloads through demanding environments faster than any other AMR on the market, with zero compromise to safety.

[ ROAM Lab ]

Very, very high performance sensing and actuation to pull this off.

[ Ishikawa Group ]

We introduce a conversational social robot designed for long-term in-home use to help with loneliness. We present a novel robot behavior design to have simple self-reflection conversations with people to improve wellness, while still being feasible, deployable, and safe.

[ HCI Lab ]

We are one of the 5 winners of the Start-up Challenge. This video illustrates what we achieved during the Swisscom 5G exploration week. Our proof-of-concept tele-excavation system is composed of a Menzi Muck M545 walking excavator automated & customized by Robotic Systems Lab and IBEX motion platform as the operator station. The operator and remote machine are connected for the first time via a 5G network infrastructure which was brought to our test field by Swisscom.

[ RSL ]

This video shows LOLA balancing on different terrain when being pushed in different directions. The robot is technically blind, not using any camera-based or prior information on the terrain (hard ground is assumed).

[ TUM ]

Autonomous driving when you cannot see the road at all because it's buried in snow is some serious autonomous driving.

[ Norlab ]

A hierarchical and robust framework for learning bipedal locomotion is presented and successfully implemented on the 3D biped robot Digit. The feasibility of the method is demonstrated by successfully transferring the learned policy in simulation to the Digit robot hardware, realizing sustained walking gaits under external force disturbances and challenging terrains not included during the training process.

[ OSU ]

This is a video summary of the Center for Robot-Assisted Search and Rescue's deployments under the direction of emergency response agencies to more than 30 disasters in five countries from 2001 (9/11 World Trade Center) to 2018 (Hurricane Michael). It includes the first use of ground robots for a disaster (WTC, 2001), the first use of small unmanned aerial systems (Hurricane Katrina 2005), and the first use of water surface vehicles (Hurricane Wilma, 2005).

[ CRASAR ]

In March, a team from the Oxford Robotics Institute collected a week of epic off-road driving data, as part of the Sense-Assess-eXplain (SAX) project.

[ Oxford Robotics ]

As a part of the AAAI 2021 Spring Symposium Series, HEBI Robotics was invited to present an Industry Talk on the symposium's topic: Machine Learning for Mobile Robot Navigation in the Wild. Included in this presentation was a short case study on one of our upcoming mobile robots that is being designed to successfully navigate unstructured environments where today's robots struggle.

[ HEBI Robotics ]

Thanks Hardik!

This Lockheed Martin Robotics Seminar is from Chad Jenkins at the University of Michigan, on “Semantic Robot Programming… and Maybe Making the World a Better Place.”

I will present our efforts towards accessible and general methods of robot programming from the demonstrations of human users. Our recent work has focused on Semantic Robot Programming (SRP), a declarative paradigm for robot programming by demonstration that builds on semantic mapping. In contrast to procedural methods for motion imitation in configuration space, SRP is suited to generalize user demonstrations of goal scenes in workspace, such as for manipulation in cluttered environments. SRP extends our efforts to crowdsource robot learning from demonstration at scale through messaging protocols suited to web/cloud robotics. With such scaling of robotics in mind, prospects for cultivating both equal opportunity and technological excellence will be discussed in the context of broadening and strengthening Title IX and Title VI.

[ UMD ] Continue reading

Posted in Human Robots

#439089 Ingenuity’s Chief Pilot Explains How ...

On April 11, the Mars helicopter Ingenuity will take to the skies of Mars for the first time. It will do so fully autonomously, out of necessity—the time delay between Ingenuity’s pilots at the Jet Propulsion Laboratory and Jezero Crater on Mars makes manual or even supervisory control impossible. So the best that the folks at JPL can do is practice as much as they can in simulation, and then hope that the helicopter can handle everything on its own.

Here on Earth, simulation is a critical tool for many robotics applications, because it doesn’t rely on access to expensive hardware, is non-destructive, and can be run in parallel and at faster-than-real-time speeds to focus on solving specific problems. Once you think you’ve gotten everything figured out in simulation, you can always give it a try on the real robot and see how close you came. If it works in real life, great! And if not, well, you can tweak some stuff in the simulation and try again.

For the Mars helicopter, simulation is much more important, and much higher stakes. Testing the Mars helicopter under conditions matching what it’ll find on Mars is not physically possible on Earth. JPL has flown engineering models in Martian atmospheric conditions, and they’ve used an actuated tether to mimic Mars gravity, but there’s just no way to know what it’ll be like flying on Mars until they’ve actually flown on Mars. With that in mind, the Ingenuity team has been relying heavily on simulation, since that’s one of the best tools they have to prepare for their Martian flights. We talk with Ingenuity’s Chief Pilot, Håvard Grip, to learn how it all works.

Ingenuity Facts:
Body Size: a box of tissues

Brains: Qualcomm Snapdragon 801

Weight: 1.8 kilograms

Propulsion: Two 1.2m carbon fiber rotors

Navigation sensors: VGA camera, laser altimeter, inclinometer

Ingenuity is scheduled to make its first flight no earlier than April 11. Before liftoff, the Ingenuity team will conduct a variety of pre-flight checks, including verifying the responsiveness of the control system and spinning the blades up to full speed (2,537 rpm) without lifting off. If everything looks good, the first flight will consist of a 1 meter per second climb to 3 meters, 30 seconds of hover at 3 meters while rotating in place a bit, and then a descent to landing. If Ingenuity pulls this off, that will have made its entire mission a success. There will be more flights over the next few weeks, but all it takes is one to prove that autonomous helicopter flight on Mars is possible.

Last month, we spoke with Mars Helicopter Operations Lead Tim Canham about Ingenuity’s hardware, software, and autonomy, but we wanted to know more about how the Ingenuity team has been using simulation for everything from vehicle design to flight planning. To answer our questions, we talked with JPL’s Håvard Grip, who led the development of Ingenuity’s navigation and flight control systems. Grip also has the title of Ingenuity Chief Pilot, which is pretty awesome. He summarizes this role as “operating the flight control system to make the helicopter do what we want it to do.”

IEEE Spectrum: Can you tell me about the simulation environment that JPL uses for Ingenuity’s flight planning?

Håvard Grip: We developed a Mars helicopter simulation ourselves at JPL, based on a multi-body simulation framework that’s also developed at JPL, called DARTS/DSHELL. That's a system that has been in development at JPL for about 30 years now, and it's been used in a number of missions. And so we took that multibody simulation framework, and based on it we built our own Mars helicopter simulation, put together our own rotor model, our own aerodynamics models, and everything else that's needed in order to simulate a helicopter. We also had a lot of help from the rotorcraft experts at NASA Ames and NASA Langley.

Image: NASA/JPL

Ingenuity in JPL’s flight simulator.

Without being able to test on Mars, how much validation are you able to do of what you’re seeing in simulation?

We can do a fair amount, but it requires a lot of planning. When we made our first real prototype (with a full-size rotor that looked like what we were thinking of putting on Mars) we first spent a lot of time designing it and using simulation tools to guide that design, and when we were sufficiently confident that we were close enough, and that we understood enough about it, then we actually built the thing and designed a whole suite of tests in a vacuum chamber where where we could replicate Mars atmospheric conditions. And those tests were before we tried to fly the helicopter—they were specifically targeted at what we call system identification, which has to do with figuring out what the true properties, the true dynamics of a system are, compared to what we assumed in our models. So then we got to see how well our models did, and in the places where they needed adjustment, we could go back and do that.

The simulation work that we really started after that very first initial lift test, that’s what allowed us to unlock all of the secrets to building a helicopter that can fly on Mars.
—Håvard Grip, Ingenuity Chief Pilot

We did a lot of this kind of testing. It was a big campaign, in several stages. But there are of course things that you can't fully replicate, and you do depend on simulation to tie things together. For example, we can't truly replicate Martian gravity on Earth. We can replicate the atmosphere, but not the gravity, and so we have to do various things when we fly—either make the helicopter very light, or we have to help it a little bit by pulling up on it with a string to offload some of the weight. These things don't fully replicate what it will be like on Mars. We also can't simultaneously replicate the Mars aerodynamic environment and the physical and visual surroundings that the helicopter will be flying in. These are places where simulation tools definitely come in handy, with the ability to do full flight tests from A to B, with the helicopter taking off from the ground, running the flight software that it will be running on board, simulating the images that the navigation camera takes of the ground below as it flies, feeding that back into the flight software, and then controlling it.

To what extent can simulation really compensate for the kinds of physical testing that you can’t do on Earth?

It gives you a few different possibilities. We can take certain tests on Earth where we replicate key elements of the environment, like the atmosphere or the visual surroundings for example, and you can validate your simulation on those parameters that you can test on Earth. Then, you can combine those things in simulation, which gives you the ability to set up arbitrary scenarios and do lots and lots of tests. We can Monte Carlo things, we can do a flight a thousand times in a row, with small perturbations of various parameters and tease out what our sensitivities are to those things. And those are the kinds of things that you can't do with physical tests, both because you can't fully replicate the environment and also because of the resources that would be required to do the same thing a thousand times in a row.

Because there are limits to the physical testing we can do on Earth, there are elements where we know there's more uncertainty. On those aspects where the uncertainty is high, we tried to build in enough margin that we can handle a range of things. And simulation gives you the ability to then maybe play with those parameters, and put them at their outer limits, and test them beyond where the real parameters are going to be to make sure that you have robustness even in those extreme cases.

How do you make sure you’re not relying on simulation too much, especially since in some ways it’s your only option?

It’s about anchoring it in real data, and we’ve done a lot of that with our physical testing. I think what you’re referring to is making your simulation too perfect, and we’re careful to model the things that matter. For example, the simulated sensors that we use have realistic levels of simulated noise and bias in them, the navigation camera images have realistic levels of degradation, we have realistic disturbances from wind gusts. If you don’t properly account for those things, then you’re missing important details. So, we try to be as accurate as we can, and to capture that by overbounding in areas where we have a high degree of uncertainty.

What kinds of simulated challenges have you put the Mars helicopter through, and how do you decide how far to push those challenges?

One example is that we can simulate going over rougher terrain. We can push that, and see how far we can go and still have the helicopter behave the way that we want it to. Or we can inject levels of noise that maybe the real sensors don't see, but you want to just see how far you can push things and make sure that it's still robust.

Where we put the limits on this and what we consider to be realistic is often a challenge. We consider this on a case by case basis—if you have a sensor that you're dealing with, you try to do testing with it to characterize it and understand its performance as much as possible, and you build a level of confidence in it that allows you to find the proper balance.

When it comes to things like terrain roughness, it's a little bit of a different thing, because we're actually picking where we're flying the helicopter. We have made that choice, and we know what the terrain looks like around us, so we don’t have to wonder about that anymore.

Image: NASA/JPL-Caltech/University of Arizona

Satellite image of the Ingenuity flight area.

The way that we’re trying to approach this operationally is that we should be done with the engineering at this point. We’re not depending on going back and resimulating things, other than a few checks here and there.

Are there any examples of things you learned as part of the simulation process that resulted in changes to the hardware or mission?

You know, it’s been a journey. One of the early things that we discovered as part of modeling the helicopter was that the rotor dynamics were quite different for a helicopter on Mars, in particular with respect to how the rotor responds to the up and down bending of the blades because they’re not perfectly rigid. That motion is a very important influence on the overall flight dynamics of the helicopter, and what we discovered as we started modeling was that this motion is damped much less on Mars. Under-damped oscillatory things like that, you kind of figure might pose a control issue, and that is the case here: if you just naively design it as you might a helicopter on Earth, without taking this into account, you could have a system where the response to control inputs becomes very sluggish. So that required changes to the vehicle design from some of the very early concepts, and it led us to make a rotor that’s extremely light and rigid.

The design cycle for the Mars helicopter—it’s not like we could just build something and take it out to the back yard and try it and then come back and tweak it if it doesn’t work. It’s a much bigger effort to build something and develop a test program where you have to use a vacuum chamber to test it. So you really want to get as close as possible up front, on your first iteration, and not have to go back to the drawing board on the basic things.

So how close were you able to get on your first iteration of the helicopter design?

[This video shows] a very early demo which was done more or less just assuming that things were going to behave as they would on Earth, and that we’d be able to fly in a Martian atmosphere just spinning the rotor faster and having a very light helicopter. We were basically just trying to demonstrate that we could produce enough lift. You can see the helicopter hopping around, with someone trying to joystick it, but it turned out to be very hard to control. This was prior to doing any of the modeling that I talked about earlier. But once we started seriously focusing on the modeling and simulation, we then went on to build a prototype vehicle which had a full-size rotor that’s very close to the rotor that will be flying on Mars. One difference is that prototype had cyclic control only on the lower rotor, and later we added cyclic control on the upper rotor as well, and that decision was informed in large part by the work we did in simulation—we’d put in the kinds of disturbances that we thought we might see on Mars, and decided that we needed to have the extra control authority.

How much room do you think there is for improvement in simulation, and how could that help you in the future?

The tools that we have were definitely sufficient for doing the job that we needed to do in terms of building a helicopter that can fly on Mars. But simulation is a compute-intensive thing, and so I think there’s definitely room for higher fidelity simulation if you have the compute power to do so. For a future Mars helicopter, you could get some benefits by more closely coupling together high-fidelity aerodynamic models with larger multi-body models, and doing that in a fast way, where you can iterate quickly. There’s certainly more potential for optimizing things.

Photo: NASA/JPL-Caltech

Ingenuity preparing for flight.

Watching Ingenuity’s first flight take place will likely be much like watching the Perseverance landing—we’ll be able to follow along with the Ingenuity team while they send commands to the helicopter and receive data back, although the time delay will mean that any kind of direct control won’t be possible. If everything goes the way it’s supposed to, there will hopefully be some preliminary telemetry from Ingenuity saying so, but it sounds like we’ll likely have to wait until April 12 before we get pictures or video of the flight itself.

Because Mars doesn’t care what time it is on Earth, the flight will actually be taking place very early on April 12, with the JPL Mission Control livestream starting at 3:30 a.m. EDT (12:30 a.m. PDT). Details are here. Continue reading

Posted in Human Robots