Content deleted Content added
m Updated Space ROS paragraph |
Frankg0n1627 (talk | contribs) m →ROS 2 |
||
| (15 intermediate revisions by 10 users not shown) | |||
Line 8:
| author = [[Willow Garage]]<br/>[[Stanford Artificial Intelligence Laboratory]]<br/>[[Open Robotics]]
| released = {{Start date and age|2007}}
| latest release version =
| latest release date = {{Start date and age|df=yes|
| latest preview version =
| operating system = [[Linux]], [[macOS]] (experimental), [[Windows 10]] (experimental)
| genre = [[Robotics suite]], [[operating system|OS]], [[Library (computing)|library]]
| license = [[Apache License 2.0|Apache 2.0]]
| website = {{URL|www.ros.org}}
| AsOf =
| repo = {{URL|https://github.com/ros2/ros2}}
| programming language = [[C++]], [[Python (programming language)|Python]], and [[Lisp (programming language)|Lisp]]
Line 24:
* language- and platform-independent tools used for building and distributing ROS-based software;
* ROS client library implementations such as {{Not a typo|roscpp}},<ref>{{cite web|title=Package Summary|url=http://wiki.ros.org/roscpp|website=ROS.org|publisher=Open Robotics|access-date=21 February 2016}}</ref> {{Not a typo|rospy}},<ref>{{cite web|title=Package SUmmary|url=http://wiki.ros.org/rospy|website=ROS.org|publisher=Open Robotics|access-date=21 February 2016}}</ref> and {{Not a typo|roslisp}};<ref>{{cite web|title=Package Summary|url=http://wiki.ros.org/roslisp|website=ROS.org|publisher=Open Robotics|access-date=21 February 2016}}</ref>
* packages containing application-related code
Both the language-independent tools and the main client libraries ([[C++]], [[Python (programming language)|Python]], and [[Lisp (programming language)|Lisp]]) are released under the terms of the [[BSD license]], and as such are [[open-source software]] and free for both commercial and research use. The majority of other packages are licensed under a variety of [[Open-source license|open-source licenses]]. These other packages implement commonly used functionality and applications such as hardware drivers, robot models, datatypes, planning, [[Robotic sensing|perception]], [[simultaneous localization and mapping]] (SLAM), [[Robotics simulator|simulation tools]], and other [[algorithm]]s.
Line 32:
=== Early days at Stanford (2007 and earlier) ===
Sometime before 2007, the first pieces of what eventually would become ROS began coalescing at [[Stanford University]].<ref name=":0">{{Cite web|url=https://spectrum.ieee.org/wizards-of-ros-willow-garage-and-the-making-of-the-robot-operating-system|title=Wizards of ROS: Willow Garage and the Making of the Robot Operating System|last=Guizzo|first=Evan Ackerman and Erico|date=2017-11-07|website=IEEE Spectrum: Technology, Engineering, and Science News|language=en|access-date=2019-04-29}}</ref><ref>{{Cite web|url=https://spectrum.ieee.org/the-origin-story-of-ros-the-linux-of-robotics|title=The Origin Story of ROS, the Linux of Robotics|last=Wyrobek|first=Keenan|date=2017-10-31|website=IEEE Spectrum: Technology, Engineering, and Science News|language=en|access-date=2019-04-29}}</ref> Eric Berger and Keenan Wyrobek, PhD students working in Kenneth Salisbury's<ref>{{Cite web|url=https://www.stanford.edu/group/sailsbury_robotx/cgi-bin/salisbury_lab/?page_id=1217|title=J. Kenneth Salisbury, Ph.D. {{!}} Salisbury Robotics Lab|language=en-US|access-date=2019-04-29}}</ref>
In their first steps towards this unifying system, the two built the [[PR1 (robot)|PR1]] as a hardware prototype and began to work on software from it, borrowing the best practices from other early open-source robotic software frameworks, particularly switchyard, a system that Morgan Quigley, another Stanford PhD student, had been working on in support of the STanford Artificial Intelligence Robot (STAIR)<ref>{{cite web|url=https://news.stanford.edu/2019/01/16/stanfords-robot-makers-andrew-ng/ |title=Stanford's Robot Makers |date=16 January 2019}}</ref><ref>{{cite web|url=http://stair.stanford.edu/papers.php |title=STAIR: The STanford Artificial Intelligence Robot project |year=2008 |publisher=Snowbird Workshop|last1=Ng|first1=Andrew|first2=Stephen|last2=Gould|first3=Morgan|last3=Quigley|first4=Ashutosh|last4=Saxena|first5=Eric|last5=Berger}}</ref><ref>{{cite web|url=http://stair.stanford.edu/|title=STAIR|website=stair.Stanford.edu|access-date=12 December 2017}}</ref><ref>{{citation|last1=Quigley|first1=Morgan|title=STAIR: Hardware and Software Architecture|url=http://www.aaai.org/Papers/Workshops/2007/WS-07-15/WS07-15-008.pdf|year=2007|publisher=AAAI 2007 Robotics Workshop|last2=Berger|first2=Eric|last3=Ng|first3=Andrew Y.|author3-link=Andrew Ng}}</ref> by the [[Stanford Artificial Intelligence Laboratory]]. Early funding of US$50,000 was provided by [[Joanna Hoffman]] and [[Alain Rossmann]], which supported the development of the PR1. While seeking funding for further development,<ref>{{Cite web|last=Keenan Wyrobek|date=2017-07-03|title=Personal Robotics Program Fund Fundraising Deck from 2006|url=https://www.slideshare.net/KeenanWyrobek/personal-robotics-program-fund-fundraising-deck-from-2006}}</ref> Eric Berger and Keenan Wyrobek met Scott Hassan, the founder of [[Willow Garage]], a [[technology incubator]] which was working on an autonomous SUV and a solar autonomous boat. Hassan shared Berger and Wyrobek's vision of a "Linux for robotics", and invited them to come and work at Willow Garage. Willow Garage was started in January 2007, and the first commit of ROS code was made to SourceForge on 7 November 2007.<ref>{{cite web|url=https://sourceforge.net/p/ros/code/10/log/?path=|title=Repository: code|website=Sourceforge.net|access-date=12 December 2017}}</ref>
=== Willow Garage (2007–2013) ===
[[Willow Garage]] began developing the PR2 robot as a follow-up to the PR1, and ROS as the software to run it. Groups from more than twenty institutions made contributions to ROS, both the core software and the growing number of packages
In December 2008, Willow Garage met the first of
Following this, Willow Garage achieved one of its longest
[[File:ROS Antarctica sunset.jpg|thumb|An image of Robot Operating System (ROS) running in Antarctica]]
Line 47:
2011 was a banner year for ROS with the launch of ROS Answers, a Q/A forum for ROS users, on 15 February;<ref>{{cite web|url=http://www.ros.org/news/2011/02/announcing-ros-answers.html|title=Announcing ROS Answers – ROS robotics news|website=ROS.org|publisher=Open Robotics|access-date=12 December 2017}}</ref> the introduction of the highly successful [[TurtleBot]] robot kit on 18 April;<ref>{{cite web|url=http://www.willowgarage.com/blog/2011/04/18/turtlebots-available-preorder|title=ROS on the Move: TurtleBots available for preorder |website=Willow Garage|access-date=12 December 2017}}</ref> and the total number of ROS repositories passing 100 on 5 May.<ref>{{cite web|url=http://www.ros.org/news/2011/05/100-repositories.html|title=100 Repositories – ROS robotics news|website=ROS.org|publisher=Open Robotics|access-date=12 December 2017}}</ref> Willow Garage began 2012 by creating the [[Open Robotics |Open Source Robotics Foundation]] (OSRF)<ref>{{Cite web|url=http://www.willowgarage.com/blog/2012/04/16/open-source-robotics-foundation|title=Willow Garage Spins Out OSRF|access-date=13 October 2017|archive-date=6 November 2017|archive-url=https://web.archive.org/web/20171106081726/http://www.willowgarage.com/blog/2012/04/16/open-source-robotics-foundation|url-status=dead}}</ref> in April. The OSRF was immediately awarded a software contract by the [[DARPA|Defense Advanced Research Projects Agency]] (DARPA).<ref>{{Cite news|url=https://spectrum.ieee.org/darpa-robotics-challenge-simulation-software-open-source-robotics-foundation|title=DARPA Awards Simulation Software Contract to Open Source Robotics Foundation}}</ref> Later that year, the first ROSCon was held in St. Paul, Minnesota,<ref>{{Cite web|url=http://www.ros.org/news/2012/05/thanks-for-a-great-roscon-2012.html|title=Thanks for a great ROSCon 2012! – ROS robotics news|website=ROS.org|publisher=Open Robotics|access-date=2018-11-24}}</ref> the first book on ROS, ''ROS By Example'',<ref>{{Cite web|url=http://www.ros.org/news/2012/09/new-book-ros-by-example.html|title=New Book: ROS by Example – ROS robotics news|website=ROS.org|publisher=Open Robotics|access-date=2018-11-24}}</ref> was published, and [[Baxter (robot)|Baxter]], the first commercial robot to run ROS, was announced by [[Rethink Robotics]].<ref>{{Cite web|url=http://www.ros.org/news/2012/09/rethink-ros.html|title=Rethink ROS – ROS robotics news|website=ROS.org|publisher=Open Robotics|access-date=2018-11-24}}</ref> Soon after passing its fifth anniversary in November, ROS began running on every continent on 3 December 2012.<ref>{{Cite web|url=http://www.ros.org/news/2012/12/ros-five-years.html|title=ROS: Five Years – ROS robotics news|website=ROS.org|publisher=Open Robotics|access-date=2018-11-24}}</ref>
In February 2013, the OSRF became the primary software maintainers for ROS,<ref>{{cite web|url=http://osrfoundation.org/blog/ros-at-osrf.html|title=Osrf – Ros @ Osrf|date=2013-02-11|publisher=Osrfoundation.org|access-date=2014-07-12}}</ref> foreshadowing the announcement in August that Willow Garage would be absorbed by its founders, [[Suitable Technologies]].<ref>{{cite web|url=http://www.willowgarage.com/blog/2013/08/21/willow-garage-employees-join-suitable-technologies|title=employees join Suitable Technologies|publisher=Willow Garage|access-date=2014-07-12|archive-date=8 October 2017|archive-url=https://web.archive.org/web/20171008140941/http://www.willowgarage.com/blog/2013/08/21/willow-garage-employees-join-suitable-technologies|url-status=dead}}</ref> At this point, ROS had released seven major versions (up to ROS Groovy),<ref name=":1">{{Cite web|url=http://wiki.ros.org/Distributions|title=Distributions – ROS Wiki|website=ROS.org|publisher=Open Robotics|access-date=2019-04-29}}</ref> and had users all over the globe. This chapter of ROS development would be finalized when [[Clearpath Robotics]] took over support responsibilities for
=== OSRF and Open Robotics (2013–present) ===
In the years since OSRF took over the primary development of ROS, a new version has been released every year,<ref name=":1"/> while interest in ROS continues to grow. ROSCons have occurred every year since 2012, co-located with either [[International Conference on Robotics and Automation|ICRA]] or [[International Conference On Intelligent Robots and Systems|IROS]], two flagship robotics conferences. Meetups of ROS developers have been organized in a variety of countries,<ref>{{Cite web|title=Notes from the first Korean ROS Users Meetup – ROS robotics news|url=https://www.ros.org/news/2015/01/notes-from-the-first-korean-ros-users-meetup.html|access-date=2021-07-30|website=ROS.org|publisher=Open Robotics}}</ref><ref>{{Cite web|url=http://www.ros.org/news/2016/01/invitation-to-the-first-danish-ros-meetup.html|title=First Danish ROS Meetup}}</ref><ref>{{Cite web|url=http://www.ros.org/news/2017/03/invitation-to-the-first-ukrainian-ros-meetup.html|title=First Ukrainian ROS Meetup}}</ref> a number of ROS books have been published,<ref>{{cite web|url=http://shop.oreilly.com/product/0636920024736.do|title=Programming Robots with ROS: A Practical Introduction to the Robot Operating System|website=OReilly.com|access-date=12 December 2017}}</ref> and many educational programs initiated.<ref>{{Cite web|url=http://www.ros.org/news/2015/08/report-from-first-ros-summer-school-in-china.html|title=Report from first ROS Summer School in China – ROS robotics news|website=ROS.org|publisher=Open Robotics|access-date=2018-11-24}}</ref><ref>{{Cite web|url=http://www.theconstructsim.com/construct-learn-develop-robots-using-ros/robotigniteacademy_learnros/|title=ROS Robot Ignite Academy}}</ref> On 1 September 2014, [[NASA]] announced the first robot to run ROS in space: [[Robonaut|Robotnaut 2]], on the [[International Space Station]].<ref>{{cite web|url=http://www.ros.org/news/2014/09/ros-running-on-iss.html|title=ROS running on ISS – ROS robotics news|website=ROS.org|publisher=Open Robotics|access-date=12 December 2017}}</ref> In 2017, the OSRF changed its name to [[Open Robotics]]. Tech giants [[Amazon (company)|Amazon]] and [[Microsoft]] began to take an interest in ROS during this time, with Microsoft porting core ROS to Windows in September 2018,<ref>{{Cite web|url=https://ros-win.visualstudio.com/ros-win|title=Summary|website=ros-win.visualstudio.com|access-date=2019-04-29}}</ref> followed by Amazon Web Services releasing RoboMaker in November 2018.<ref>{{Cite web|url=https://aws.amazon.com/about-aws/whats-new/2018/11/announcing-aws-robomaker-a-new-cloud-robotics-service/|title=Announcing AWS RoboMaker|website=Amazon Web Services, Inc.|language=en-US|access-date=2019-04-29}}</ref>
Perhaps the most important development of the OSRF/Open Robotics years thus far (not to discount the explosion of robot platforms
In November 2020, NASA announced Blue Origin had been selected through the Space Technology Mission Directorate’s Announcement of Collaboration Opportunity (ACO) to co-develop [[Space Robot Operating System]] (Space ROS) together with three NASA centers<ref>{{Cite web |date=2020-11-09 |title=2020 NASA Announcement of Collaboration Opportunity (ACO) Selections - NASA |url=https://www.nasa.gov/missions/station/2020-nasa-announcement-of-collaboration-opportunity-aco-selections/ |access-date=2024-10-31 |language=en-US}}</ref>. The purpose of Space ROS is to provide a reusable and modular software framework predicated on ROS 2 that is compliant to aerospace mission and safety assurance requirements (such as NPR 7150.2 and DO-178C). The project was formulated and led by [[S. Will Chambers|Will Chambers]]<ref>{{Cite AV media |url=https://www.youtube.com/watch?v=HtjYBQ8gZkc |title=RDP120: Space ROS |date=2023-03-13 |last=The Construct |access-date=2024-10-31 |via=YouTube}}</ref>, Blue Origin's principal technologist of robotics at the time. In 2021, Blue Origin subcontracted software development workload to Open Robotics who remained on the team until the program ended in 2022. Space ROS is currently an open community project.<ref>{{Cite web |title=Home |url=https://space.ros.org |access-date=2024-10-31 |website=space.ros.org}}</ref> <ref>{{Cite web |title=Space ROS |url=https://github.com/space-ros |access-date=2024-10-31 |website=GitHub |language=en}}</ref> ▼
▲Perhaps the most important development of the OSRF/Open Robotics years thus far (not to discount the explosion of robot platforms which began to support ROS or the enormous improvements in each ROS version) was the proposal of ROS 2, a significant API change to ROS which is intended to support [[Real-time computing|real-time programming]], a wider variety of computing environments, and more modern technology.<ref>{{Cite web|url=http://design.ros2.org/articles/why_ros2.html|title=Why ROS 2?|website=ROS.org|publisher=Open Robotics|access-date=2019-04-29}}</ref> ROS 2 was announced at ROSCon 2014,<ref>{{Cite web|url=https://docs.ros.org/en/rolling/|title=ROS 2 Overview|website=ROS.org|publisher=Open Robotics|access-date=2021-09-21}}</ref> the first commits to the {{Not a typo|ros2}} repository were made in February 2015, followed by alpha releases in August 2015.<ref name=":2">{{Cite web|url=https://docs.ros.org/en/rolling/Releases.html|title=ROS 2 Distributions|website=ROS.org|publisher=Open Robotics|access-date=2021-09-21}}</ref> The first distribution release of ROS 2, Ardent Apalone, was released on 8 December 2017,<ref name=":2" /> ushering in a new era of next-generation ROS development.
==Design==
Line 60 ⟶ 58:
=== Philosophy ===
[[File:Ros Equation.png|thumb|An image depicting the ROS equation: Plumbing + Tools + Capabilities + Ecosystem = ROS!|alt=An image depicting the ROS equation: Plumbing + Tools + Capabilities + Ecosystem = ROS!|500x500px]]
ROS was designed to be open source, intending that users would be able to choose the configuration of tools and libraries
=== Computation graph model ===
ROS processes are represented as nodes in a graph structure, connected by edges called topics.<ref name=":3">{{Cite web|url=http://wiki.ros.org/ROS/Tutorials/UnderstandingNodes|title=ROS/Tutorials/UnderstandingNodes – ROS Wiki|website=ROS.org|publisher=Open Robotics|access-date=2019-04-29}}</ref> ROS nodes can pass messages to one another through topics, make service calls to other nodes, provide a service for other nodes, or set or retrieve shared data from a communal database called the parameter server. A process called the
==== Nodes ====
A node represents one process running the ROS graph. Every node has a name, which
==== Topics ====
Line 72 ⟶ 70:
==== Services ====
A node may also advertise services.<ref name=":4">{{Cite web|url=http://wiki.ros.org/ROS/Tutorials/UnderstandingServicesParams|title=ROS/Tutorials/UnderstandingServicesParams – ROS Wiki|website=ROS.org|publisher=Open Robotics|access-date=2019-04-29}}</ref> A service represents an action that a node can take which will have a single result. As such, services are often used for actions
==== Parameter server ====
The parameter server<ref name=":4"/> is a database shared between nodes which allows for communal access to static or semi-static information. Data
==Tools==
ROS's core functionality is augmented by a variety of tools
=== {{Not a typo|rviz}} ===
Line 84 ⟶ 82:
==={{Not a typo|rosbag}}===
{{Not a typo|rosbag}}<ref>{{Cite web|url=http://wiki.ros.org/rosbag|title=rosbag – ROS Wiki|website=ROS.org|publisher=Open Robotics|access-date=2019-04-23}}</ref> is a command line tool used to record and playback ROS message data. {{Not a typo|rosbag}} uses a file format called bags,<ref>{{Cite web|url=http://wiki.ros.org/Bags|title=Bags – ROS Wiki|website=ROS.org|publisher=Open Robotics|access-date=2019-04-23}}</ref> which log ROS messages by listening to topics and recording messages as they come in. Playing messages back from a bag is largely the same as having the original nodes
=== catkin ===
catkin<ref>{{Cite web|url=http://wiki.ros.org/catkin|title=catkin – ROS Wiki|website=ROS.org|publisher=Open Robotics|access-date=2019-04-29}}</ref> is the ROS build system, having replaced {{Not a typo|rosbuild}}<ref>{{Cite web|url=http://wiki.ros.org/rosbuild|title=rosbuild – ROS Wiki|website=ROS.org|publisher=Open Robotics|access-date=2019-04-29}}</ref> as of ROS Groovy. catkin is based on [[CMake]]
==={{Not a typo|rosbash}}===
The {{Not a typo|rosbash}}<ref>{{Cite web|url=http://wiki.ros.org/rosbash|title=rosbash – ROS Wiki|website=ROS.org|publisher=Open Robotics|access-date=2019-04-23}}</ref> package provides a suite of tools which augment the functionality of the [[Bash (Unix shell)|bash shell]]. These tools include {{Not a typo|rosls}}, {{Not a typo|roscd}}, and {{Not a typo|roscp}}, which replicate the functionalities of [[ls]], [[Cd (command)|cd]], and [[Cp (Unix)|cp]] respectively. The ROS versions of these tools allow users to use {{Not a typo|ros}} package names in place of the file path where the package is located. The package also adds tab-completion to most ROS utilities
==={{Not a typo|roslaunch}}===
{{Not a typo|roslaunch}}<ref>{{Cite web|url=http://wiki.ros.org/roslaunch|title=roslaunch – ROS Wiki|website=ROS.org|publisher=Open Robotics|access-date=2019-04-23}}</ref> is a tool used to launch multiple ROS nodes both locally and remotely, as well as setting parameters on the ROS parameter server. {{Not a typo|roslaunch}} configuration files, which are written using [[XML]] can easily automate a complex startup and configuration process into a single command. {{Not a typo|roslaunch}} scripts can include other {{Not a typo|roslaunch}} scripts, launch nodes on specific machines, and even restart processes
== Packages of note ==
ROS contains many open-source implementations of common robotics functionality and algorithms. These open-source implementations are organized into packages. Many packages are included as part of ROS distributions, while others may be developed by individuals and distributed through code
=== Systems and tools ===
Line 134 ⟶ 132:
==Versions and releases==
ROS releases may be incompatible with other releases and are often referred to by code name rather than version number. ROS 2 currently releases a version every year in May, following the release of Ubuntu LTS versions.<ref>{{Cite web|url=https://discourse.ros.org/t/proposed-changes-to-the-ros-releases/4736|title=ROS Release Schedule Changes|date=9 May 2018}}</ref><ref>{{Cite
===ROS 1===
Line 154 ⟶ 152:
|Melodic Morenia
|23 May 2018
|
|{{Version|o|2023-05-30}}
|5 years
Line 249 ⟶ 247:
|N/A
|-
|Kilted Kaiju
|23 May 2025
|[[File:Kilted-kaiju.png|75px|Kilted Kaiju Logo]]
|{{Version|p|November 2026}}
|1.5 years
Line 264 ⟶ 262:
|23 May 2023<ref>{{cite web | url=https://discourse.ros.org/t/ros-2-iron-irwini-released/31553 | title=ROS 2 Iron Irwini Released! | date=23 May 2023 }}</ref>
|[[File:ROS2 Iron Irwini poster.png|75px|The release poster for ROS 2 Iron Irwini.]]
|{{Version|
|1.5 years
|-
Line 352 ⟶ 350:
|-
|(batch CI jobs for ROS 2<br/>and http://design.ros2.org)
|referenced in Q&A<br/>6 May 2015<ref>{{Cite web|url=https://answers.ros.org/question/208560/is-there-a-release-date-of-ros-2-or-more-informations-about-it/|title=Is there a release date of ros 2 or more
|N/A
|N/A
Line 373 ⟶ 371:
=== ROS-Industrial ===
ROS-Industrial<ref>{{cite web|url=https://rosindustrial.org/about/description/|title=ROS-Industrial About|website=rosindustrial.org|access-date=12 December 2017}}</ref> is an open-source project (BSD (legacy)/Apache 2.0 (preferred) license) that extends the advanced abilities of ROS to manufacturing automation and robotics. In the industrial environment, there are two different approaches to programming a robot: either through an external proprietary controller, typically implemented using ROS, or via the respective native programming language of the robot. ROS can therefore be seen as the software-based approach to
The ROS-Industrial repository includes interfaces for common industrial manipulators, grippers, sensors, and device networks. It also provides software libraries for automatic 2D/3D sensor calibration, process path/motion planning, applications like Scan-N-Plan, developer tools like the Qt Creator ROS Plugin, and training
The Consortia supports the global ROS-Industrial community by conducting ROS-I training, providing technical support and setting the future roadmap for ROS-I, as well as conducting
▲The ROS-Industrial repository includes interfaces for common industrial manipulators, grippers, sensors, and device networks. It also provides software libraries for automatic 2D/3D sensor calibration, process path/motion planning, applications like Scan-N-Plan, developer tools like the Qt Creator ROS Plugin, and training curriculum that is specific to the needs of manufacturers. ROS-I is supported by an international Consortium of industry and research members. The project began as a collaborative endeavor between Yaskawa Motoman Robotics, Southwest Research Institute, and Willow Garage to support the use of ROS for manufacturing automation, with the GitHub repository being founded in January 2012 by Shaun Edwards (SwRI). Currently, the Consortium is divided into three groups; the ROS-Industrial Consortium Americas (led by SwRI and located in San Antonio, Texas), the ROS-Industrial Consortium Europe (led by Fraunhofer IPA and located in Stuttgart, Germany) and the ROS-Industrial Consortium Asia Pacific (led by Advanced Remanufacturing and Technology Centre (ARTC) and Nanyang Technological University (NTU) and located in Singapore).
=== Space ROS ===
▲The Consortia supports the global ROS-Industrial community by conducting ROS-I training, providing technical support and setting the future roadmap for ROS-I, as well as conducting precompetitive joint industry projects to develop new ROS-I abilities.<ref>{{Cite web|url=https://rosindustrial.org/briefhistory/|title=Brief History|website=ROS-Industrial|language=en-US|access-date=2018-07-11}}</ref>
▲In November 2020, NASA announced Blue Origin had been selected through the Space Technology Mission Directorate’s Announcement of Collaboration Opportunity (ACO) to co-develop [[Space Robot Operating System]] (Space ROS) together with three NASA centers.<ref>{{Cite web |date=2020-11-09 |title=2020 NASA Announcement of Collaboration Opportunity (ACO) Selections - NASA |url=https://www.nasa.gov/missions/station/2020-nasa-announcement-of-collaboration-opportunity-aco-selections/ |access-date=2024-10-31 |language=en-US}}</ref>
==ROS-compatible robots and hardware ==
Line 404 ⟶ 405:
* BeagleBoard: the robotics lab of the [[Katholieke Universiteit Leuven]], [[Belgium]]<ref>{{Cite web|date=2013-10-29|title=Koen Buys|url=http://people.mech.kuleuven.be/~u0062536/embsensor.html|access-date=2021-07-30|archive-url=https://web.archive.org/web/20131029192925/http://people.mech.kuleuven.be/~u0062536/embsensor.html|archive-date=29 October 2013}}</ref> has ported ROS to the [[Beagleboard]].
* Raspberry Pi: image of Ubuntu Mate with ROS<ref>{{cite web|url=https://downloads.ubiquityrobotics.com/ |title=Ubiquity Robotics Downloads |access-date=29 January 2018}}</ref> by Ubiquity Robotics; installation guide for Raspbian
*[[Sitara ARM Processor|Sitara ARM Processors]] have support for the ROS package as part of the official Linux SDK.<ref>{{Cite web|title=5.3.6. ROS and Radar – Processor SDK Linux Documentation|url=http://software-dl.ti.com/processor-sdk-linux/esd/docs/latest/linux/Examples_and_Demos/Application_Demos/ROS_Radar.html|website=software-dl.ti.com|access-date=2020-05-01}}</ref>
| |||