17 ms·
Robot Operating System – A flexible framework for writing robot software
- dang 8y agoA small recent-ish discussion: https://news.ycombinator.com/item?id=15530813 https://news.ycombinator.com/item?id=15530813
- carlsborg 8y agoAnyone using this.. what have you built?
- bpg_92 8y agoThe whole ROS ecosystem is huge, most of research platform robots are ROS enabled. Check the PR2 (http://wiki.ros.org/Robots/PR2 http://wiki.ros.org/Robots/PR2), Turtlebot (https://www.turtlebot.com/ https://www.turtlebot.com/), the Nao series (http://wiki.ros.org/nao http://wiki.ros.org/nao), even Boston Dynamic's Atlas robot (http://gazebosim.org/tutorials?tut=drcsim_atlas_siminterface&cat= http://gazebosim.org/tutorials?tut=drcsim_atlas_siminterface...) or Nasa's Robonaut (http://wiki.ros.org/Robots/Robonaut2 http://wiki.ros.org/Robots/Robonaut2). It facilitates work by not having to rewrite a bunch of code every time. Also, most robotic related libraries like OMP, or TF are supported.
- matthewmacleod 8y agoIt's a huge ecosystem of components, but from what I understand it's pretty ubiquitous in the research robotics and commercial space. My startup is using it to power an autonomous customer service robot. ROS modules handle things like pose calculations, trajectory planning, collision avoidance, and basically all other interaction between software and hardware. From my perspective as a developer on the user-facing software, it's basically a simple event bus and RPC framework that has a load of prebuilt datatypes and modules for handling common robotics tasks. Caveats – a lot of modules seem to follow pretty sketchy coding practices compared to what I'm used to in other industries. It seems to be a bit of a paragon of bad design. There also seems to be a lot of version confusion – lots of packages seem to support different subsets of versions, with most of the community possibly on older releases. There's an ongoing ROS 2.0 effort that I think uses MQTT as the transport. But I'm not a ROS expert, so take the above with a grain of salt!
- rcxdude 8y agoYeah, ROS is a very good example of worse being the enemy of good (to mangle some sayings). It's a common framework which does basically everything you'd want to do in a robotic system, with a bunch of useful functionality on top of it, but basically every part of it is incomplete, poorly documented, awkwardly designed, and buggy. However, since there's basically nothing else which addresses the same space, people feel compelled to use it. I know of two robotics projects, one with a pretty substantial budget, which have been basically hamstrung by developing initially on ROS and running headlong into its limitations while being unable or unwilling to pay the cost of moving off of it.
- TeMPOraL 8y agoSo basically, ROS is the UNIX of robotics (i.e. "worse is better", + judging by how many serious projects using it are mentioned elsewhere in this comment thread)?
- rcxdude 8y agoKind of. Fundamentally, it has never had much competition due to the narrowness of the scope. It is ubiquitous in university robotics due to its accessibility, but in my experience most (successful) industrial robotics applications will simply provide an interface to ROS: internally they will not use it at all. One thing with ROS is that reimplementing it is not particularly difficult: I have, for various reasons and projects (in some cases before ROS was available) implemented basically all the core components of it (to similar levels of completeness and reliability). So the cost of doing it yourself is actually not all that high (and I think people overestimate it).
- Scea91 8y agoIve done my bachelor's thesis in 2013 on this. We were working on a robot built for exploration of disaster sites (earthquake, fire, ...). I built: 1) Virtual camera: The robot was equipped with 6 fixed cameras. You can position virtual camera anywhere in the coordinate space and it constructs it's image with the information from the real cameras. 2) System for semi-automatic external calibration of cameras from LIDAR sensor. External calibration is the process of estimating the position and orientation of the camera. This system was not as precise as calibration using calibration patterns in lab, but it was useful when the robot was in the wild and you wanted to adjust the camera or strap a new camera on it quickly. However, to be frank I am not sure ft the system was ever actually used that way. I left the lab after finishing my thesis. The ROS ecosystem is reasonably simple to understand and definitely makes things much easier. Apart from having some issues with compatibility between versions and incomplete functionality I remember it as quite a nice platform. On the other hand I have not tried any of it's competitors if there are any.
- amarant 8y agothat's pretty cool! I'm particularly interested in how you made the virtual camera work? can I read your thesis, or (dare i ask) source code?
- Scea91 8y agoThe virtual camera vas done during summer project but the idea IIRC is quite simple. I will try some hasty writeup ;) 1) Create a virtual image plane (or cylinder/sphere for panoramic camera) in the 3D space. For this you need to specify the virtual camera's position, orientation, focal length and FOV. 2) Define pixels on the image plane. You need to specify the image resolution and just create grid on the the image plane. Each pixel corresponds to a 3D point in the world coordinate system. 3) To get a color of each pixel you project it's corresponding 3D point to all real cameras. Usually only some of the cameras see the point. Each camera that sees the point gives you a color according to the color of the pixel in it's image. You have to perform blending of these colors. What worked well in our case was to give more weight to cameras where the point projected close to the center of their image. As you can see, there will definitely be some artifacts, usually more the farther away the virtual camera is from the real cameras. However, it worked to my surprise quite well. It was even possible to look at the robot from 3rd person even though all of the real cameras were on it. Also it is crucial to have well calibrated cameras. Apart from their projection matrices you also need to consider their radial and tangential distortion which was very significant with our camera models. https://www.wikiwand.com/en/Pinhole_camera_model https://www.wikiwand.com/en/Pinhole_camera_model https://www.wikiwand.com/en/Camera_matrix https://www.wikiwand.com/en/Camera_matrix https://www.wikiwand.com/en/Distortion_(optics) https://www.wikiwand.com/en/Distortion_(optics)
- ragebol 8y agoHome service robots, controlled via 'natural' language: https://www.youtube.com/watch?v=b0P2MqmQ-DI https://www.youtube.com/watch?v=b0P2MqmQ-DI Wall cleaning robot (still testing): https://www.youtube.com/watch?v=4dMjt_Pj4og https://www.youtube.com/watch?v=4dMjt_Pj4og There are some nice projects on https://discourse.ros.org/c/ros-projects https://discourse.ros.org/c/ros-projects, I really like Kyler Laird's Tractobots: https://www.youtube.com/watch?v=oPI7f5kQRKo https://www.youtube.com/watch?v=oPI7f5kQRKo
- gntoni 8y agohttps://www.youtube.com/watch?v=Z70_3wMFO24 https://www.youtube.com/watch?v=Z70_3wMFO24
- cbames89 8y agoNASA's Valkyrie, and Robonaut 2, in addition Fetch, and Baxter,a couple of industrial arms via ROS-i. I know that it's pretty horrid, but it's also the devil I know. This allows for rapid prototyping. In addition, the API hasn't changed much so I can walk away for months and come back and still use the robot. Several organizations support OSRF, but they're still just a couple of people. It's all open source so I've been able to document bugs and submit fixes. That being said, they're still robotics people doing a systems job, but I've failed so far in convincing systems people that robotics is the next mobile.
- robotresearcher 8y ago> but they're still just a couple of people. 27 people are listed on their staff page. https://www.openrobotics.org/team/ https://www.openrobotics.org/team/
- cbames89 8y agoWoah, guess I lost track..
- Symmetry 8y agoWell, apart from adding some fish[1] support to ROS core I worked on these guys[2] at Vecna and they mostly use ROS. A pretty common pattern in commercial use of ROS is to start out with a vanilla setup and replace important nodes with ones you've written to work the way you need them to. At my current job we don't use ROS but being able to look at the ROS drivers of commercial arms is a big help in making our own drivers. [1]https://fishshell.com/ https://fishshell.com/ [2]https://robotics.vecna.com/ https://robotics.vecna.com/
- 0wl3x 8y agoI published a research paper as an undergrad on improving an existing algorithm for a team of mobile robots to navigate space and create a map of their environment. I also used it as an intern at a robotics company to use a microsoft kinect as a depth sensor for helping the robot perceive space in three dimensions.
- robotresearcher 8y agoAcademics use ROS a lot. The canonical ROS paper has been cited 4,714 times. This is an extreme outlier. https://scholar.google.com/citations?user=fMDLYCUAAAAJ&hl=en&oi=sra https://scholar.google.com/citations?user=fMDLYCUAAAAJ&hl=en... Use the 'cited by' link to see thousands of robot projects that use ROS: https://scholar.google.com/scholar?oi=bibs&hl=en&cites=143767492575573826 https://scholar.google.com/scholar?oi=bibs&hl=en&cites=14376... (I'm not affiliated with Open Robotics)
- snw 8y agoTo get ROS and a few more robot related software tools and libraries as nice binary packages robotpkg might also be of interest: http://robotpkg.openrobots.org http://robotpkg.openrobots.org
- raleighm 8y agoHow does this relate to, or compare with, say, BrainOS? (Please forgive the newbie question. I’m totally completely ignorant about robotics operating systems but interested to learn.)
- seren 8y agoI don't know BrainOS, but the most obvious difference is that ROS is open source, so you can prototype or tinker with it easily. BrainOS seems to be a totally closed solution, and details are sparse on what it actually runs and does. ROS has a BSD license, so it is even possible that BrainOS is actually using some ROS package or resources. After a quick look, most SW positions at BrainOS mentions than having a prior experience with ROS is a plus.
- protomikron 8y agoMy experience with ROS has been suboptimal. It's a collection of incompatible, outdated and buggy tools that communicate with each other via a single-point of failure (roscore) using a pub/sub mechanism. Furthermore they use their own build system (catkin, WHY?), define their own IDL (WHY?), use their own dependency system (rosdep, WHY?) and even mess with your Bash environment. I appreciate their effort and it is really hard to make a system that interfaces with all kinds of different robots and hardware, but I don't understand why they don't exploit existing high-quality solutions for the "not-robot-related" parts of their system. At the moment I don't think I would like to have ROS run a potential self-driving car.
- ragebol 8y agoThe build system is mostly macros on top of cmake. But not ideal indeed. Same for the IDL. ROS 2.0 [0] should adress a lot of those issues, also stuff like real-time, improved security, no roscore needed. On the robots I worked with, I never missed any of those features, to be honest. Largest project of those is a research home service robot, quite different from a self-driving car in terms of reliability requirements. The real-time stuff for motor control there is handled by EtherCAT. [0] https://design.ros2.org/ https://design.ros2.org/
- protomikron 8y ago> The build system is mostly macros on top of cmake. That makes it even worse. So it's crap on top of crap. CMake is mostly used to build cross-platform software, but I don't think anybody uses ROS on a system other than Linux, so why not just use established tools like simple `make`?
- oarfish 8y agoIt's not even really supported outside specific Ubuntu releases I think, so for anything else you're on your own mostly.
- ragebol 8y agoI think CMake is quite established. I don't like these kind of holy wars (I like vim too :-)) but to get stuff done. ROS lets me do that. I've seen several times that companies write their message passing stuff on top of ZeroMQ, mttq and what-have-you, while they could have spent all that time doing something novel as well. At the cost of using less than perfect tools made by someone else that a lot of people are also using.
- lnsru 8y agoCould somebody, please, explain me what I need in addition to ROS for functional safety. Some certified laser scanner? Do I understand it right, that ROS completely ignores functional safety?
- TickleSteve 8y agoIf you're meaning trying to create a safety-related or safety-critical system then the particular set of libraries you use is one very small part of the problem. The system design itself is examined as well as how it is implemented. The examiners will want to see proof that your system fails in predictable and deterministic ways suitable for their usage. Also systems dealing with the motion-control typically require hard-real-time response so you would not be running this on your average Linux system either. You need to be prepared to have your code and system design examined in great depth, a very long and expensive process generally.
- lzr_io 8y agoNote concerning the system: you will most likely need dedicated, redundant and/or diversified HW all the way from sensing over computing down to the actuator system. At least for industrial robots and cobots, not sure about social robots and such.
- lzr_io 8y agoROS is not a suitable tool at all. Functional safety is a totally different beast and SW is only a small part of it. Don't even think about implementing functional safety on your own without a few years of practical safety experience. Even if you get your hands on all the required hardware parts, you will need to spend a lot of time on making sure you tick all the boxes in relevant standards and convincing notified bodies you did your homework. Don't try to do this on your own, hire an experienced professional right from the start of any project which might touch on functional safety.
- roland35 8y agoThe best thing to do, if you can, is to isolate all functional safety related hardware and software to a smaller and simpler subcomponent of your entire system. Then you can prove that no matter what ROS does, it cannot cause harm. This also makes it easier to be certify since your safety related functions are isolated and hopefully smaller and simpler!
- asd4 8y agoAlso see ROS Industrial [1] for extensions to the ecosystem to include common industrial robots. [1] https://rosindustrial.org/about/description/ https://rosindustrial.org/about/description/
- mrfusion 8y agoCould someone explain for a new bee. If I’m building a robot why would I use this and not just write a python script running on Linux?
- dimatura 8y agoYou can use ROS with Python and Linux. In fact, that's a big chunk of actual ROS-based systems out there, with most of the rest being C++ and Linux. For simple robots, you can get away with a simple script. But say, you want to attach more sensors, add some visualization, some logging, etc. Pretty soon you'll find yourself writing multithreaded (not great in Python) and/or multiprocess code, some kind of simple GUI to visualize data, some logging code, some way to manage parameters... and before you know it you'll find yourself writing your own little version of ROS (or more generally, robotic middleware). And without the huge ecosystem of ROS packages that might solve all sort of problems for you.
- sronors 8y agoGood points. You also may find yourself wanting to have more than one robot. And then you may want them to talk to each other.
- 0wl3x 8y agoRobots usually consist of many complicated components. ROS provides a unique and consistent method for those components to communicate with each other via an API and a pub/sub method. That way each one of your components can handle it's own logic via whatever software it likes, just so long as you can connect to the ROS api and let the OS handle orchestrating each component. A bit like a conductor in an orchestra.
- CryptoPotato 8y agojj
- ausjke 8y agoUsed ROS1 and worked DDS in the past, but never did anything with ROS2 yet, anyone uses ROS2 and has something to say about it?
- MisterTea 8y agoPlease stop using names for version releases. Is "awesome igloo" newer than "super turtle" or "raring rino"? Just stop. Use boring versioning numbers. Your developers and users will thank you.
- tfolbrecht 8y agoThe software is versioned with numbers,the codenames are for releases which could have version number ranges, or help differentiate stable from testing, etc. The developers and users can better make the distinctions with codenames.
- MisterTea 8y agoDecimals do that job with less characters.
- anonymousCar 8y agoTell that to Android
- wjwwood 8y agoThey're alphabetical, lol. Plus cool shirts.
- sirsebastian 8y agoROS can be an super enjoyable and productive environment to build software in. It gives you access to a set of common sensor and actuator drivers, motion planning, navigation, perception libraries, and implementations of the latest IROS papers. I’ve seen it used to prototype lots of non-robotics applications too; really any local distributed system integrating, calibrating, and coordinating sensors. Personally I think the standardized data types it provides for robotics and perception data is one of its greatest assets [1], and could be a standards effort in itself. And it’s home to a great community. But it definitely has its limits, especially as applications mature, and the ecosystem can feel siloed from the technology landscape evolving so quickly in, for example, backend distributed systems. Knowledge transfer between the robotics community and the software engineering happening in distributed systems, databases, gaming, web development, etc. is a huge untapped opportunity. Hit me up if you want to talk more about this! [1] e.g. http://wiki.ros.org/sensor_msgs http://wiki.ros.org/sensor_msgs
- osterwood 8y agoI wrote a blog article recently wherein I propose that cloud-native infrastructure can be a better foundation for robotic software stacks than ROS/ROS2. I've been involved in several ROS-based robot & robot-sensor efforts and (like many others here) have found it lacking in major ways. https://capablerobot.com/blog/2018/2018-05-09-wheel-reinvention/ https://capablerobot.com/blog/2018/2018-05-09-wheel-reinvent... There are a whole host of performant, lightweight, and open source tools for distributed-tracking, pub/sub, logging, serialization, service discovery, KV stores, visualization, etc. Right now it seems the robot world (including me) ignores this fact and continues to reinvent wheels (poorly). I'm curious for feedback on this idea and will be publishing updates as I experiment with this idea. I'll likely be starting with timing & latency experiments between ROS, ROS2, and other cloud-native pub/sub brokers.