Twu, Philip | Search NASA

NASA NTRS2022

Planning for a Martian Road Trip – The Mars2020 Mobility Systems Design

The Perseverance rover landed in Jezero Crateron Mars on February 18, 2021, marking the beginning of anepic road trip across Mars. The guiding principle of thePerseverance rover design was to replicate Curiosity, exceptfor when the new mission objectives mandated a change.The scientific objectives require that Perseverance drivemore quickly and more efficiently through more complexterrain than its predecessors. The mobility system forPerseverance exemplifies this, in that key portions areidentical, yet others have had major upgrades. Key upgradesinclude more tractive and more robust tires, newengineering cameras, a new computer dedicated for imageprocessing, and a more efficient AutoNav software suite.This paper will follow how the scientific objectives led tothe key and driving mobility requirements and how theserequirements were decomposed at the different subsystems.

Stragier, Michael M.↗

NASA NTRS2022

Testing Mars 2020 Flight Software and Hardware in the Surface System Development Environment

The Mars 2020 (M2020) Perseverance Rover is NASA's most advanced planetary rover mission to date. It includes a novel Sample Caching Subsystem (SCS) which will collect rock cores for possible future return to Earth, as well as an improved mobility system with enhanced autonomous navigation which will enable it to traverse faster and farther than prior rovers. The development of both systems required extensive flight software and flight hardware testing. To support this testing, we developed the Surface System Development Environment (SSDEV) and used it for a wide variety of testing. SSDEV is a bundled subset of M2020 Flight Software which runs on commercially available Linux computers and can be combined with multiple backend options for simulation and hardware control. The SSDEV architecture enabled our teams to perform much more testing of flight software and flight hardware than would have otherwise been possible. As a secondary benefit, the SSDEV-based test campaigns also helped our teams enter the operations phase of the mission with greater readiness of operations products and tools. In this paper, we summarize the motivation for SSDEV, provide an overview of the SSDEV architecture, list several examples of how SSDEV was used, and summarize lessons learned. SSDEV is not a substitute for integrated testing with flight-like avionics, but it enabled substantially more testing than would have otherwise been possible and also provided some unique benefits. We recommend architectures like SSDEV to future projects that need to perform extensive hardware and software testing using a limited set of flight-like avionics.

Wai, Dennis↗