December 13, 2017
ROS 2 Ardent Apalone released

We're happy to announce the ROS 2 release Ardent Apalone!

Installation instructions and tutorials can be found on the ROS 2 wiki.

To get an idea of what's in this release, be sure to read the Ardent page.

A few features and improvements we would like to highlight in this release:

  • The first non-beta release.
  • rviz including a few plugins (the Windows version will follow in a few weeks)
  • Different initialization options for message data structures in C++
  • Logging API improvements, now also used in the demos
  • Time support in C++ with different clocks
  • wait-for-service support in the Python client library
  • Draft implementation of REP 149 specifying format 3 of the package manifest files

While there is always more work to be done we consider several of the core components to be ready to be used by a broader audience. Therefore we have dropped the "beta" label and will support Ardent for one year, fixing bugs and keeping the release working, especially on platforms with rolling dependency releases (OS X / Windows). We'll start a regular six month release cycle for newer versions of ROS 2. While we do aim to keep the API as stable as possible, we can't guarantee 100% API compatibility between releases. That being said, whether or not ROS 2 is ready to be used for your application or if you can switch from ROS 1 to ROS 2 right now depends on the exact feature set and requirements of your use case. Please check the features page as well as the roadmap for more information.

As always, we invite you to try out the new software, give feedback, report bugs, and suggest features (and contribute code!): https://github.com/ros2/ros2/wiki/Contact

Your friendly neighborhood ROS 2 Team

by Tully Foote on December 13, 2017 07:13 PM

Beta of official ROS driver for Ensenso stereo cameras (ROSIN)

@gavanderhoorn wrote:

A quick update on an early result of the ROSIN project: Ensenso GmbH has made the first beta available of the driver for their stereo cameras.

ROS wiki page: wiki/ensenso_driver
Github repository: ensenso/ros_driver

This is a beta, so try it out and please use the issue tracker to report any problems.

Posts: 1

Participants: 1

Read full topic

by @gavanderhoorn gavanderhoorn on December 13, 2017 08:06 AM

December 12, 2017
Hector_mapping results in tf transformation error

@senoa95 wrote:

The hector mapping package is not finding the TF even though I have created a static reference TF. I keep getting the following error when I try to launch the training.launch file located in ~/hector_slam/launch. I modified the training.launch file in order to create my TF. The hector_slam package partially works but it does not publish the map_odom transformation so I have no way of knowing the relative location of my rover from the initial location. Can you please help?

The error is:

[ERROR] [1513111318.589547578, 1512355461.660118665]: Transform failed during publishing of map_odom transform: Lookup would require extrapolation into the future. Requested time 1512355460.650420421 but the latest data is at time 1512355460.113152033, when looking up transform from frame [base_link] to frame [nav]

Posts: 1

Participants: 1

Read full topic

by @senoa95 Senoa95 on December 12, 2017 09:07 PM

December 11, 2017
OpenCV 3.3.1 is breaking builds in Kinetic

@preed wrote:

Apologies in advance for not asking this on ROS Answers, but it’s been unusable all day and this is a somewhat pressing question.

After upgrading my Ubuntu Xenial / ROS Kinetic over the weekend, I noticed that the latest release included OpenCV 3.3.1, and now none of my packages that use OpenCV will build. I’m having this issue on my workstation, but I’ve also reproduced the exact issue in a Docker container based on ros:kinetic.

Whenever I build a component that adds ${OpenCV_LIBRARIES} to its target_link_libraries macro, the build fails saying there is “no rule to make target ‘opencv_core-NOTFOUND’”. For example, if I clone and build swri_geometry_util, also modifying it to print out the contents of catkin_LIBRARIES and OpenCV_LIBRARIES just before the error happens, I get this:

Starting  >>> swri_geometry_util                                                                                                                                                                                                            
____________________________________________________________________________________________________________________________________________________________________________________________________________________________________________
Warnings   << swri_geometry_util:cmake /workspace/logs/swri_geometry_util/build.cmake.000.log                                                                                                                                               
catkin_LIBRARIES: /opt/ros/kinetic/lib/libcv_bridge.so;/opt/ros/kinetic/lib/libopencv_core3.so.3.3.1;/opt/ros/kinetic/lib/libopencv_imgproc3.so.3.3.1;/opt/ros/kinetic/lib/libopencv_imgcodecs3.so.3.3.1;/opt/ros/kinetic/lib/libtf.so;/opt/ros/kinetic/lib/libtf2_ros.so;/opt/ros/kinetic/lib/libactionlib.so;/opt/ros/kinetic/lib/libmessage_filters.so;/opt/ros/kinetic/lib/libroscpp.so;/usr/lib/x86_64-linux-gnu/libboost_signals.so;/usr/lib/x86_64-linux-gnu/libboost_filesystem.so;/opt/ros/kinetic/lib/libxmlrpcpp.so;/opt/ros/kinetic/lib/libtf2.so;/opt/ros/kinetic/lib/libroscpp_serialization.so;/opt/ros/kinetic/lib/librosconsole.so;/opt/ros/kinetic/lib/librosconsole_log4cxx.so;/opt/ros/kinetic/lib/librosconsole_backend_interface.so;/usr/lib/x86_64-linux-gnu/liblog4cxx.so;/usr/lib/x86_64-linux-gnu/libboost_regex.so;/opt/ros/kinetic/lib/librostime.so;/opt/ros/kinetic/lib/libcpp_common.so;/usr/lib/x86_64-linux-gnu/libboost_system.so;/usr/lib/x86_64-linux-gnu/libboost_thread.so;/usr/lib/x86_64-linux-gnu/libboost_chrono.so;/usr/lib/x86_64-linux-gnu/libboost_date_time.so;/usr/lib/x86_64-linux-gnu/libboost_atomic.so;/usr/lib/x86_64-linux-gnu/libpthread.so;/usr/lib/x86_64-linux-gnu/libconsole_bridge.so
OpenCV_LIBRARIRES: opencv_core
cd /workspace/build/swri_geometry_util; catkin build --get-env swri_geometry_util | catkin env -si  /usr/bin/cmake /workspace/src/marti_common/swri_geometry_util --no-warn-unused-cli -DCATKIN_DEVEL_PREFIX=/workspace/devel/.private/swri_geometry_util -DCMAKE_INSTALL_PREFIX=/opt/rtk/kinetic -DCMAKE_BUILD_TYPE=RelWithDebInfo; cd -
............................................................................................................................................................................................................................................
____________________________________________________________________________________________________________________________________________________________________________________________________________________________________________
Errors     << swri_geometry_util:make /workspace/logs/swri_geometry_util/build.make.000.log                                                                                                                                                 
make[2]: *** No rule to make target 'opencv_core-NOTFOUND', needed by '/workspace/devel/.private/swri_geometry_util/lib/libswri_geometry_util.so'.  Stop.
make[2]: *** Waiting for unfinished jobs....
make[1]: *** [CMakeFiles/swri_geometry_util.dir/all] Error 2
make: *** [all] Error 2
cd /workspace/build/swri_geometry_util; catkin build --get-env swri_geometry_util | catkin env -si  /usr/bin/make --jobserver-fds=6,7 -j; cd -
............................................................................................................................................................................................................................................
Failed     << swri_geometry_util:make              [ Exited with code 2 ]                                                                                                                                                                   
Failed    <<< swri_geometry_util                   [ 9.4 seconds ]

My CMAKE_PREFIX_PATH and LD_LIBRARY_PATH are set appropriately, and the opencv libs exist in /opt/ros/kinetic/lib/ . If I manually downgrade to the 3.2.0 version of OpenCV, it works fine without any other changes. I’ve tested this with a handful of different packages on both my workstation and in a Docker container, and it’s the same behavior everywhere.

If I hand-edit /opt/ros/kinetic/share/OpenCV-3.3.1/OpenCVConfig.cmake to make it return absolute paths to libraries instead of just library names, it works fine. I wouldn’t think I should need to do that, and it worked fine with 3.2.0.

Am I missing something? Did the way OpenCV should be included change in 3.3.1?

On a related note, OpenCV 3.3 seems to have broken some other things, too. See https://github.com/opencv/opencv_contrib/issues/1376 for an example. I’m surprised that a major package that breaks backward compatibility was allowed to be released into Kinetic at this point.

Posts: 5

Participants: 4

Read full topic

by @preed P. J. Reed on December 11, 2017 08:30 PM

PlotJuggler 1.5 released

@facontidavide wrote:

I am happy to announce the release of PlotJuggler 1.5.0

For those of you which are not familiar with it, PlotJuggler is a time series visualization that allows the user to load rosbags or visualize ros topics, similarly to rqt_plot.

This new release includes:

  • faster load or rosbags,
  • More parsing options to deal with large arrays.
  • many bug fixes. In particular, the live visualization of ROS topics (streaming) won’t use anymore 100% of the CPU.

Don’t hesitate to share suggestions for improvements, bug reports and any feedback.

Cheers

Davide

Posts: 1

Participants: 1

Read full topic

by @facontidavide Davide Faconti on December 11, 2017 07:19 PM

A rewarding European Robotics League tournament, at PAL Robotics

Five teams from different European universities competed in Barcelona in a thrilling European Robotics League Tournament hosted by PAL Robotics! In this Service Robots’ category contest, robots had to prove themselves useful helping an old woman at home autonomously. This is why PAL Robotics’ offices got quite transformed, adapting the space to recreate an apartment. Tests involved domestic tasks like following a person, understanding and obeying voice commands, accomplishing with specific orders or receiving guests at the house.

Using TIAGo for Service tasks

Four teams used TIAGo to compete at ERL! They got creative on integrating their favourite devices to the robot to expand its capabilities, easily plugging gadgets such as an Amazon Echo Dot or an Intel NUC. Participants could also use an independent operating system on a laptop to command TIAGo thanks to the ROS open source framework it uses.

European-Robotics-League-Barcelona-PAL-testThe RGB-D camera that comes inside TIAGo helped a lot in the object recognition tasks and in supporting the autonomous navigation. Thanks to the camera, TIAGo can detect obstacles like tables, which are trickier if only detected by the lasers. All of this, in addition to the comfort of programming the robot from the TIAGo’s convenient laptop tray!

Raphael Memmesheimer, from the HOMER@UniKoblenz Team, pointed out: “I’m impressed by the progress we’ve made in just one month with TIAGo. We received it one month ago and we are already able to grasp objects, to navigate properly, and I think that we can achieve much more in the future.”

ERL: An enriching experience that boosts research

“At Bristol Robotics Lab in the UK, it’s quite a sterile environment, quite clinical, things are organized. But when you come to an environment like this that represents a real home, there is a lot to learn about uncertainty, things not being quite what you expect them to be. That’s what has been so valuable about the competition, that we can test it in a realistic environment”, expressed the HEARTS team member Zale Steer.

European-Robotics-League-Barcelona-testMany hopes are put into the role of robots in the future, as the SocRob@HOME Team Member Luis Luz said: “I think that they will help in a good way and not as we sometimes see in movies”. In fact, ERL stands as a unique framework to boost such robotics field. The IRI@ERL Team member Ferran Martinez stated that ERL “is a good opportunity to improve your code skills, to learn new things that you don’t learn in your studies. And it is a chance to learn how different people approach to the same kind of problem”.

This practical side of the competition is also appreciated by Juan Victores, member of the Robotics Lab UC3M Team, who said that “the problem with robotics up to now is that all the fields have been studied separately. Challenges like ERL force us to focus our developments on integration. So you are bridging all the gaps that are classically missing in robotics”.

ALL-TEAMS-PAL-ROBOTICS-European-Robotics-League

A way of celebrating the European Robotics Week

The European Robotics League was one exciting way to celebrate the European Robotics Week. The participants could be part of the one-of-a-kind working environment that is felt at PAL Robotics, while being also surrounded by many robots from the company during the contest. Organizing and hosting the Tournament was a pleasure for PAL Robotics!

Now we’ll have to wait until the European Robotics Forum, in Tampere (Finland), to see the final classification. Best of luck to all teams!

The post A rewarding European Robotics League tournament, at PAL Robotics appeared first on PAL Robotics Blog.

by Judith Viladomat on December 11, 2017 03:44 PM

ROS webinar | How to train your technical team on ROS skills?

@YUHONG_LIN wrote:


ROS Webinar | How to train your technical team on ROS skills?
December 13th, 2017


Dear Roboticists,

The webinar of How to train your technical team on ROS skills will be held on December 13, 2017 from 18:00 pm - 19:00 pm CET.

Attendance is free.
All the attendants will receive a document explaining in detail all the techniques for fast ROS training (only for attendants).

= Description =
ROS is becoming the essential skills for robotics engineers. Apart from labs, there are an increasing number of commercial sector, industrial and services robots using ROS. Gradually, it has became a widely-used platform in the robotics research community.

Is a “good solution” for companies who are seeking a quick development. In recent year there are a high demand in the self-driving car industry and due to it’s low level of functionality benefits, it attracts a larger number start-up companies using it from warehousing to agriculture, which are growing at an exponential pace. It supports the robot development and industry growth without specifically costs for building software and hardware.

But as you may understand, robotics engineers spend a lot of time developing ROS based software. Sometimes, they need to gather more knowledge about a specific ROS subject. Sometimes the team needs to incorporate more engineers with ROS knowledge.

In order to speed things up, in this one-hour webinar we will show how to smooth ROS learning path for technical staff or interns in order to maximize their learning speed and apply to related robotics development.

= Who Should Attend =
Technical teams, robotics start-ups and companies who need to equip their team or their interns on ROS in an effective way, and apply ROS into robotics development quickly and effectively.

= Instructor =
RICARDO TÉLLEZ, Ph.D. (https://www.linkedin.com/in/ricardotellez/4)

= Pre-registration =
To assist us in planning, pre-registration is required.
Pre-registration website: http://www.theconstructsim.com/ros-webinars-train-team-ros/

= More Information =
You can contact us with questions and doubts here: info@theconstructsim.com

Posts: 1

Participants: 1

Read full topic

by @YUHONG_LIN on December 11, 2017 02:33 PM

New Packages for Kinetic 2017-12-11

@tfoote wrote:

We’re happy to announce a large update for Kinetic. There are 47 new packages and over 300 packages updated. In this sync there are 13 packages that regressed. We’ve been tracking them and there are issues tracking resolving them. You can find more info in the release preparation thread.

Thank you to everyone who contributed to this sync! This one took a little extra effort. A special thanks to the testers and maintainers to worked through the issues during this cycle.

Full details are below.

Package Updates for kinetic

Added Packages [47]:

  • ros-kinetic-axis-camera: 0.2.1-0
  • ros-kinetic-bcap-core: 3.0.1-0
  • ros-kinetic-bcap-service: 3.0.1-0
  • ros-kinetic-bcap-service-test: 3.0.1-0
  • ros-kinetic-catkin-virtualenv: 0.1.4-1
  • ros-kinetic-denso-robot-bringup: 3.0.1-0
  • ros-kinetic-denso-robot-control: 3.0.1-0
  • ros-kinetic-denso-robot-core: 3.0.1-0
  • ros-kinetic-denso-robot-core-test: 3.0.1-0
  • ros-kinetic-denso-robot-descriptions: 3.0.1-0
  • ros-kinetic-denso-robot-gazebo: 3.0.1-0
  • ros-kinetic-denso-robot-moveit-config: 3.0.1-0
  • ros-kinetic-denso-robot-ros: 3.0.1-0
  • ros-kinetic-dnn-detect: 0.0.2-0
  • ros-kinetic-dynamixel-workbench: 0.1.9-0
  • ros-kinetic-dynamixel-workbench-controllers: 0.1.9-0
  • ros-kinetic-dynamixel-workbench-operators: 0.1.9-0
  • ros-kinetic-dynamixel-workbench-single-manager: 0.1.9-0
  • ros-kinetic-dynamixel-workbench-single-manager-gui: 0.1.9-0
  • ros-kinetic-frame-editor: 1.0.2-0
  • ros-kinetic-grid-map-sdf: 1.6.0-0
  • ros-kinetic-gx-sound: 0.2.2-0
  • ros-kinetic-gx-sound-msgs: 0.2.2-0
  • ros-kinetic-gx-sound-player: 0.2.2-0
  • ros-kinetic-hebiros-description: 0.0.4-1
  • ros-kinetic-jog-arm: 0.0.3-2
  • ros-kinetic-nao-audio: 0.1.5-0
  • ros-kinetic-nao-interaction: 0.1.5-0
  • ros-kinetic-nao-interaction-launchers: 0.1.5-0
  • ros-kinetic-nao-interaction-msgs: 0.1.5-0
  • ros-kinetic-nao-vision: 0.1.5-0
  • ros-kinetic-osm-cartography: 0.2.4-0
  • ros-kinetic-romeo-moveit-config: 0.2.8-0
  • ros-kinetic-ros-speech-recognition: 2.1.6-0
  • ros-kinetic-route-network: 0.2.4-0
  • ros-kinetic-sainsmart-relay-usb: 0.0.2-0
  • ros-kinetic-tango-ros-messages: 2.0.0-0
  • ros-kinetic-test-catkin-virtualenv: 0.1.3-0
  • ros-kinetic-test-catkin-virtualenv-py3: 0.1.3-0
  • ros-kinetic-test-osm: 0.2.4-0
  • ros-kinetic-tracetools: 0.1.0-1
  • ros-kinetic-velodyne: 1.3.0-0
  • ros-kinetic-velodyne-driver: 1.3.0-0
  • ros-kinetic-velodyne-laserscan: 1.3.0-0
  • ros-kinetic-velodyne-msgs: 1.3.0-0
  • ros-kinetic-velodyne-pointcloud: 1.3.0-0
  • ros-kinetic-vision-msgs: 0.0.1-0

Updated Packages [311]:

  • ros-kinetic-abseil-cpp: 0.2.0-0 -> 0.2.3-0
  • ros-kinetic-actionlib: 1.11.9-0 -> 1.11.11-0
  • ros-kinetic-aruco-detect: 0.7.3-0 -> 0.7.5-0
  • ros-kinetic-assimp-devel: 2.1.4-0 -> 2.1.6-0
  • ros-kinetic-auv-msgs: 0.0.1-1 -> 0.1.0-0
  • ros-kinetic-baldor: 0.1.0-0 -> 0.1.1-0
  • ros-kinetic-bayesian-belief-networks: 2.1.4-0 -> 2.1.6-0
  • ros-kinetic-bond: 1.7.19-0 -> 1.8.1-0
  • ros-kinetic-bond-core: 1.7.19-0 -> 1.8.1-0
  • ros-kinetic-bondcpp: 1.7.19-0 -> 1.8.1-0
  • ros-kinetic-bondpy: 1.7.19-0 -> 1.8.1-0
  • ros-kinetic-camera-calibration: 1.12.20-0 -> 1.12.22-0
  • ros-kinetic-camera-calibration-parsers: 1.11.12-0 -> 1.11.13-0
  • ros-kinetic-camera-info-manager: 1.11.12-0 -> 1.11.13-0
  • ros-kinetic-catch-ros: 0.1.1-0 -> 0.1.2-0
  • ros-kinetic-catkin: 0.7.6-0 -> 0.7.8-0
  • ros-kinetic-checkerboard-detector: 1.1.3-0 -> 1.2.3-0
  • ros-kinetic-class-loader: 0.3.6-0 -> 0.3.8-0
  • ros-kinetic-control-toolbox: 1.15.0-0 -> 1.16.0-0
  • ros-kinetic-cpp-common: 0.6.2-0 -> 0.6.7-0
  • ros-kinetic-cv-bridge: 1.12.4-0 -> 1.12.7-0
  • ros-kinetic-denso: 2.0.1-0 -> 2.0.2-0
  • ros-kinetic-denso-launch: 2.0.1-0 -> 2.0.2-0
  • ros-kinetic-denso-ros-control: 2.0.1-0 -> 2.0.2-0
  • ros-kinetic-depth-image-proc: 1.12.20-0 -> 1.12.22-0
  • ros-kinetic-diff-drive-controller: 0.13.0-0 -> 0.13.1-0
  • ros-kinetic-downward: 2.1.4-0 -> 2.1.6-0
  • ros-kinetic-dynamixel-workbench-toolbox: 0.1.5-2 -> 0.1.9-0
  • ros-kinetic-ecto-opencv: 0.7.0-0 -> 0.7.2-0
  • ros-kinetic-effort-controllers: 0.13.0-0 -> 0.13.1-0
  • ros-kinetic-ethercat-manager: 1.0.6-0 -> 1.0.7-1
  • ros-kinetic-ff: 2.1.4-0 -> 2.1.6-0
  • ros-kinetic-ffha: 2.1.4-0 -> 2.1.6-0
  • ros-kinetic-fiducial-detect: 0.7.3-0 -> 0.7.5-0
  • ros-kinetic-fiducial-lib: 0.7.3-0 -> 0.7.5-0
  • ros-kinetic-fiducial-msgs: 0.7.3-0 -> 0.7.5-0
  • ros-kinetic-fiducial-pose: 0.7.3-0 -> 0.7.5-0
  • ros-kinetic-fiducial-slam: 0.7.3-0 -> 0.7.5-0
  • ros-kinetic-fiducials: 0.7.3-0 -> 0.7.5-0
  • ros-kinetic-find-object-2d: 0.6.1-5 -> 0.6.2-0
  • ros-kinetic-force-torque-sensor-controller: 0.13.0-0 -> 0.13.1-0
  • ros-kinetic-forward-command-controller: 0.13.0-0 -> 0.13.1-0
  • ros-kinetic-genmsg: 0.5.8-0 -> 0.5.9-0
  • ros-kinetic-genpy: 0.6.5-0 -> 0.6.7-0
  • ros-kinetic-geometric-shapes: 0.5.2-0 -> 0.5.3-1
  • ros-kinetic-gps-common: 0.1.9-0 -> 0.2.0-0
  • ros-kinetic-gps-umd: 0.1.9-0 -> 0.2.0-0
  • ros-kinetic-gpsd-client: 0.1.9-0 -> 0.2.0-0
  • ros-kinetic-grid-map: 1.5.2-0 -> 1.6.0-0
  • ros-kinetic-grid-map-core: 1.5.2-0 -> 1.6.0-0
  • ros-kinetic-grid-map-costmap-2d: 1.5.2-0 -> 1.6.0-0
  • ros-kinetic-grid-map-cv: 1.5.2-0 -> 1.6.0-0
  • ros-kinetic-grid-map-demos: 1.5.2-0 -> 1.6.0-0
  • ros-kinetic-grid-map-filters: 1.5.2-0 -> 1.6.0-0
  • ros-kinetic-grid-map-loader: 1.5.2-0 -> 1.6.0-0
  • ros-kinetic-grid-map-msgs: 1.5.2-0 -> 1.6.0-0
  • ros-kinetic-grid-map-octomap: 1.5.2-0 -> 1.6.0-0
  • ros-kinetic-grid-map-pcl: 1.5.2-0 -> 1.6.0-0
  • ros-kinetic-grid-map-ros: 1.5.2-0 -> 1.6.0-0
  • ros-kinetic-grid-map-rviz-plugin: 1.5.2-0 -> 1.6.0-0
  • ros-kinetic-grid-map-visualization: 1.5.2-0 -> 1.6.0-0
  • ros-kinetic-gripper-action-controller: 0.13.0-0 -> 0.13.1-0
  • ros-kinetic-grpc: 0.0.5-0 -> 0.0.6-0
  • ros-kinetic-image-common: 1.11.12-0 -> 1.11.13-0
  • ros-kinetic-image-geometry: 1.12.4-0 -> 1.12.7-0
  • ros-kinetic-image-pipeline: 1.12.20-0 -> 1.12.22-0
  • ros-kinetic-image-proc: 1.12.20-0 -> 1.12.22-0
  • ros-kinetic-image-publisher: 1.12.20-0 -> 1.12.22-0
  • ros-kinetic-image-rotate: 1.12.20-0 -> 1.12.22-0
  • ros-kinetic-image-transport: 1.11.12-0 -> 1.11.13-0
  • ros-kinetic-image-view: 1.12.20-0 -> 1.12.22-0
  • ros-kinetic-imagesift: 1.1.3-0 -> 1.2.3-0
  • ros-kinetic-imu-sensor-controller: 0.13.0-0 -> 0.13.1-0
  • ros-kinetic-joint-state-controller: 0.13.0-0 -> 0.13.1-0
  • ros-kinetic-joint-trajectory-controller: 0.13.0-0 -> 0.13.1-0
  • ros-kinetic-jsk-3rdparty: 2.1.4-0 -> 2.1.6-0
  • ros-kinetic-jsk-common-msgs: 4.2.0-0 -> 4.3.1-0
  • ros-kinetic-jsk-footstep-msgs: 4.2.0-0 -> 4.3.1-0
  • ros-kinetic-jsk-gui-msgs: 4.2.0-0 -> 4.3.1-0
  • ros-kinetic-jsk-hark-msgs: 4.2.0-0 -> 4.3.1-0
  • ros-kinetic-jsk-pcl-ros: 1.1.3-0 -> 1.2.3-0
  • ros-kinetic-jsk-pcl-ros-utils: 1.1.3-0 -> 1.2.3-0
  • ros-kinetic-jsk-perception: 1.1.3-0 -> 1.2.3-0
  • ros-kinetic-jsk-recognition: 1.1.3-0 -> 1.2.3-0
  • ros-kinetic-jsk-recognition-msgs: 1.1.3-0 -> 1.2.3-0
  • ros-kinetic-jsk-recognition-utils: 1.1.3-0 -> 1.2.3-0
  • ros-kinetic-julius: 2.1.4-0 -> 2.1.6-0
  • ros-kinetic-julius-ros: 2.1.4-0 -> 2.1.6-0
  • ros-kinetic-libcmt: 2.1.4-0 -> 2.1.6-0
  • ros-kinetic-libfranka: 0.1.0-2 -> 0.1.0-3
  • ros-kinetic-libmavconn: 0.21.3-0 -> 0.21.5-0
  • ros-kinetic-libsiftfast: 2.1.4-0 -> 2.1.6-0
  • ros-kinetic-lpg-planner: 2.1.4-0 -> 2.1.6-0
  • ros-kinetic-marti-can-msgs: 0.3.0-0 -> 0.4.0-0
  • ros-kinetic-marti-common-msgs: 0.3.0-0 -> 0.4.0-0
  • ros-kinetic-marti-nav-msgs: 0.3.0-0 -> 0.4.0-0
  • ros-kinetic-marti-perception-msgs: 0.3.0-0 -> 0.4.0-0
  • ros-kinetic-marti-sensor-msgs: 0.3.0-0 -> 0.4.0-0
  • ros-kinetic-marti-status-msgs: 0.3.0-0 -> 0.4.0-0
  • ros-kinetic-marti-visualization-msgs: 0.3.0-0 -> 0.4.0-0
  • ros-kinetic-mavlink: 2017.10.10-0 -> 2017.12.1-0
  • ros-kinetic-mavros: 0.21.3-0 -> 0.21.5-0
  • ros-kinetic-mavros-extras: 0.21.3-0 -> 0.21.5-0
  • ros-kinetic-mavros-msgs: 0.21.3-0 -> 0.21.5-0
  • ros-kinetic-message-filters: 1.12.7-0 -> 1.12.12-0
  • ros-kinetic-minas: 1.0.6-0 -> 1.0.7-1
  • ros-kinetic-minas-control: 1.0.6-0 -> 1.0.7-1
  • ros-kinetic-mini-maxwell: 2.1.4-0 -> 2.1.6-0
  • ros-kinetic-mk: 1.13.5-0 -> 1.13.6-0
  • ros-kinetic-moveit: 0.9.9-0 -> 0.9.10-0
  • ros-kinetic-moveit-commander: 0.9.9-0 -> 0.9.10-0
  • ros-kinetic-moveit-controller-manager-example: 0.9.9-0 -> 0.9.10-0
  • ros-kinetic-moveit-core: 0.9.9-0 -> 0.9.10-0
  • ros-kinetic-moveit-fake-controller-manager: 0.9.9-0 -> 0.9.10-0
  • ros-kinetic-moveit-kinematics: 0.9.9-0 -> 0.9.10-0
  • ros-kinetic-moveit-planners: 0.9.9-0 -> 0.9.10-0
  • ros-kinetic-moveit-planners-ompl: 0.9.9-0 -> 0.9.10-0
  • ros-kinetic-moveit-plugins: 0.9.9-0 -> 0.9.10-0
  • ros-kinetic-moveit-ros: 0.9.9-0 -> 0.9.10-0
  • ros-kinetic-moveit-ros-benchmarks: 0.9.9-0 -> 0.9.10-0
  • ros-kinetic-moveit-ros-control-interface: 0.9.9-0 -> 0.9.10-0
  • ros-kinetic-moveit-ros-manipulation: 0.9.9-0 -> 0.9.10-0
  • ros-kinetic-moveit-ros-move-group: 0.9.9-0 -> 0.9.10-0
  • ros-kinetic-moveit-ros-perception: 0.9.9-0 -> 0.9.10-0
  • ros-kinetic-moveit-ros-planning: 0.9.9-0 -> 0.9.10-0
  • ros-kinetic-moveit-ros-planning-interface: 0.9.9-0 -> 0.9.10-0
  • ros-kinetic-moveit-ros-robot-interaction: 0.9.9-0 -> 0.9.10-0
  • ros-kinetic-moveit-ros-visualization: 0.9.9-0 -> 0.9.10-0
  • ros-kinetic-moveit-ros-warehouse: 0.9.9-0 -> 0.9.10-0
  • ros-kinetic-moveit-runtime: 0.9.9-0 -> 0.9.10-0
  • ros-kinetic-moveit-setup-assistant: 0.9.9-0 -> 0.9.10-0
  • ros-kinetic-moveit-simple-controller-manager: 0.9.9-0 -> 0.9.10-0
  • ros-kinetic-mqtt-bridge: 0.1.5-0 -> 0.1.6-0
  • ros-kinetic-nao-dcm-bringup: 0.0.4-0 -> 0.0.5-0
  • ros-kinetic-naoqi-dcm-driver: 0.0.2-0 -> 0.0.3-0
  • ros-kinetic-nerian-stereo: 2.0.3-0 -> 2.1.0-0
  • ros-kinetic-nlopt: 2.1.4-0 -> 2.1.6-0
  • ros-kinetic-nmea-msgs: 1.0.0-0 -> 1.1.0-0
  • ros-kinetic-nodelet: 1.9.10-0 -> 1.9.14-0
  • ros-kinetic-nodelet-core: 1.9.10-0 -> 1.9.14-0
  • ros-kinetic-nodelet-topic-tools: 1.9.10-0 -> 1.9.14-0
  • ros-kinetic-object-recognition-transparent-objects: 0.4.2-0 -> 0.4.3-0
  • ros-kinetic-opencv-apps: 1.12.0-0 -> 2.0.0-0
  • ros-kinetic-opencv3: 3.2.0-4 -> 3.3.1-0
  • ros-kinetic-openni2-camera: 0.2.9-0 -> 0.3.0-0
  • ros-kinetic-openni2-launch: 0.2.2-0 -> 0.3.0-0
  • ros-kinetic-opt-camera: 2.1.4-0 -> 2.1.6-0
  • ros-kinetic-pepper-control: 0.0.3-0 -> 0.0.4-0
  • ros-kinetic-pepper-dcm-bringup: 0.0.3-0 -> 0.0.5-0
  • ros-kinetic-pepper-gazebo-plugin: 0.0.3-0 -> 0.0.4-0
  • ros-kinetic-pgm-learner: 2.1.4-0 -> 2.1.6-0
  • ros-kinetic-pid: 0.0.20-0 -> 0.0.23-0
  • ros-kinetic-plotjuggler: 1.3.0-0 -> 1.5.0-0
  • ros-kinetic-pluginlib: 1.10.5-0 -> 1.11.2-0
  • ros-kinetic-polled-camera: 1.11.12-0 -> 1.11.13-0
  • ros-kinetic-pose-cov-ops: 0.1.5-0 -> 0.1.7-0
  • ros-kinetic-posedetection-msgs: 4.2.0-0 -> 4.3.1-0
  • ros-kinetic-position-controllers: 0.13.0-0 -> 0.13.1-0
  • ros-kinetic-qb-chain: 1.0.3-0 -> 1.0.4-0
  • ros-kinetic-qb-chain-control: 1.0.3-0 -> 1.0.4-0
  • ros-kinetic-qb-chain-description: 1.0.3-0 -> 1.0.4-0
  • ros-kinetic-qb-device: 1.0.8-0 -> 1.2.2-0
  • ros-kinetic-qb-device-bringup: 1.0.8-0 -> 1.2.2-0
  • ros-kinetic-qb-device-control: 1.0.8-0 -> 1.2.2-0
  • ros-kinetic-qb-device-description: 1.0.8-0 -> 1.2.2-0
  • ros-kinetic-qb-device-driver: 1.0.8-0 -> 1.2.2-0
  • ros-kinetic-qb-device-hardware-interface: 1.0.8-0 -> 1.2.2-0
  • ros-kinetic-qb-device-msgs: 1.0.8-0 -> 1.2.2-0
  • ros-kinetic-qb-device-srvs: 1.0.8-0 -> 1.2.2-0
  • ros-kinetic-qb-hand: 1.0.5-0 -> 1.0.6-0
  • ros-kinetic-qb-hand-control: 1.0.5-0 -> 1.0.6-0
  • ros-kinetic-qb-hand-description: 1.0.5-0 -> 1.0.6-0
  • ros-kinetic-qb-hand-hardware-interface: 1.0.5-0 -> 1.0.6-0
  • ros-kinetic-qb-move: 1.0.5-0 -> 1.0.6-0
  • ros-kinetic-qb-move-control: 1.0.5-0 -> 1.0.6-0
  • ros-kinetic-qb-move-description: 1.0.5-0 -> 1.0.6-0
  • ros-kinetic-qb-move-hardware-interface: 1.0.5-0 -> 1.0.6-0
  • ros-kinetic-qt-dotgraph: 0.3.7-0 -> 0.3.8-0
  • ros-kinetic-qt-gui: 0.3.7-0 -> 0.3.8-0
  • ros-kinetic-qt-gui-app: 0.3.7-0 -> 0.3.8-0
  • ros-kinetic-qt-gui-core: 0.3.7-0 -> 0.3.8-0
  • ros-kinetic-qt-gui-cpp: 0.3.7-0 -> 0.3.8-0
  • ros-kinetic-qt-gui-py-common: 0.3.7-0 -> 0.3.8-0
  • ros-kinetic-realtime-tools: 1.10.0-0 -> 1.11.0-0
  • ros-kinetic-resized-image-transport: 1.1.3-0 -> 1.2.3-0
  • ros-kinetic-romeo-control: 0.2.2-0 -> 0.2.3-0
  • ros-kinetic-romeo-gazebo-plugin: 0.2.2-0 -> 0.2.3-0
  • ros-kinetic-ros: 1.13.5-0 -> 1.13.6-0
  • ros-kinetic-ros-comm: 1.12.7-0 -> 1.12.12-0
  • ros-kinetic-ros-controllers: 0.13.0-0 -> 0.13.1-0
  • ros-kinetic-ros-type-introspection: 1.0.0-0 -> 1.0.1-0
  • ros-kinetic-rosapi: 0.8.4-0 -> 0.8.6-0
  • ros-kinetic-rosbag: 1.12.7-0 -> 1.12.12-0
  • ros-kinetic-rosbag-storage: 1.12.7-0 -> 1.12.12-0
  • ros-kinetic-rosbash: 1.13.5-0 -> 1.13.6-0
  • ros-kinetic-rosboost-cfg: 1.13.5-0 -> 1.13.6-0
  • ros-kinetic-rosbridge-library: 0.8.4-0 -> 0.8.6-0
  • ros-kinetic-rosbridge-server: 0.8.4-0 -> 0.8.6-0
  • ros-kinetic-rosbridge-suite: 0.8.4-0 -> 0.8.6-0
  • ros-kinetic-rosbuild: 1.13.5-0 -> 1.13.6-0
  • ros-kinetic-rosclean: 1.13.5-0 -> 1.13.6-0
  • ros-kinetic-rosconsole: 1.12.7-0 -> 1.12.12-0
  • ros-kinetic-rosconsole-bridge: 0.4.4-0 -> 0.5.1-0
  • ros-kinetic-roscpp: 1.12.7-0 -> 1.12.12-0
  • ros-kinetic-roscpp-core: 0.6.2-0 -> 0.6.7-0
  • ros-kinetic-roscpp-serialization: 0.6.2-0 -> 0.6.7-0
  • ros-kinetic-roscpp-traits: 0.6.2-0 -> 0.6.7-0
  • ros-kinetic-roscreate: 1.13.5-0 -> 1.13.6-0
  • ros-kinetic-rosgraph: 1.12.7-0 -> 1.12.12-0
  • ros-kinetic-roslang: 1.13.5-0 -> 1.13.6-0
  • ros-kinetic-roslaunch: 1.12.7-0 -> 1.12.12-0
  • ros-kinetic-roslib: 1.13.5-0 -> 1.13.6-0
  • ros-kinetic-roslz4: 1.12.7-0 -> 1.12.12-0
  • ros-kinetic-rosmake: 1.13.5-0 -> 1.13.6-0
  • ros-kinetic-rosmaster: 1.12.7-0 -> 1.12.12-0
  • ros-kinetic-rosmsg: 1.12.7-0 -> 1.12.12-0
  • ros-kinetic-rosnode: 1.12.7-0 -> 1.12.12-0
  • ros-kinetic-rosout: 1.12.7-0 -> 1.12.12-0
  • ros-kinetic-rospack: 2.3.3-0 -> 2.4.4-0
  • ros-kinetic-rosparam: 1.12.7-0 -> 1.12.12-0
  • ros-kinetic-rospatlite: 2.1.4-0 -> 2.1.6-0
  • ros-kinetic-rospilot: 1.3.8-0 -> 1.4.0-0
  • ros-kinetic-rosping: 2.1.4-0 -> 2.1.6-0
  • ros-kinetic-rospy: 1.12.7-0 -> 1.12.12-0
  • ros-kinetic-rosserial: 0.7.6-0 -> 0.7.7-0
  • ros-kinetic-rosserial-arduino: 0.7.6-0 -> 0.7.7-0
  • ros-kinetic-rosserial-client: 0.7.6-0 -> 0.7.7-0
  • ros-kinetic-rosserial-embeddedlinux: 0.7.6-0 -> 0.7.7-0
  • ros-kinetic-rosserial-mbed: 0.7.6-0 -> 0.7.7-0
  • ros-kinetic-rosserial-msgs: 0.7.6-0 -> 0.7.7-0
  • ros-kinetic-rosserial-python: 0.7.6-0 -> 0.7.7-0
  • ros-kinetic-rosserial-server: 0.7.6-0 -> 0.7.7-0
  • ros-kinetic-rosserial-tivac: 0.7.6-0 -> 0.7.7-0
  • ros-kinetic-rosserial-windows: 0.7.6-0 -> 0.7.7-0
  • ros-kinetic-rosserial-xbee: 0.7.6-0 -> 0.7.7-0
  • ros-kinetic-rosservice: 1.12.7-0 -> 1.12.12-0
  • ros-kinetic-rostest: 1.12.7-0 -> 1.12.12-0
  • ros-kinetic-rostime: 0.6.2-0 -> 0.6.7-0
  • ros-kinetic-rostopic: 1.12.7-0 -> 1.12.12-0
  • ros-kinetic-rostune: 1.0.5-1 -> 1.0.7-0
  • ros-kinetic-rosunit: 1.13.5-0 -> 1.13.6-0
  • ros-kinetic-roswtf: 1.12.7-0 -> 1.12.12-0
  • ros-kinetic-rqt-bag: 0.4.10-0 -> 0.4.11-0
  • ros-kinetic-rqt-bag-plugins: 0.4.10-0 -> 0.4.11-0
  • ros-kinetic-rqt-joint-trajectory-controller: 0.13.0-0 -> 0.13.1-0
  • ros-kinetic-rqt-topic: 0.4.8-0 -> 0.4.10-0
  • ros-kinetic-rtt-actionlib: 2.9.0-0 -> 2.9.1-0
  • ros-kinetic-rtt-actionlib-msgs: 2.9.0-0 -> 2.9.1-0
  • ros-kinetic-rtt-common-msgs: 2.9.0-0 -> 2.9.1-0
  • ros-kinetic-rtt-diagnostic-msgs: 2.9.0-0 -> 2.9.1-0
  • ros-kinetic-rtt-dynamic-reconfigure: 2.9.0-0 -> 2.9.1-0
  • ros-kinetic-rtt-geometry-msgs: 2.9.0-0 -> 2.9.1-0
  • ros-kinetic-rtt-kdl-conversions: 2.9.0-0 -> 2.9.1-0
  • ros-kinetic-rtt-nav-msgs: 2.9.0-0 -> 2.9.1-0
  • ros-kinetic-rtt-ros: 2.9.0-0 -> 2.9.1-0
  • ros-kinetic-rtt-ros-comm: 2.9.0-0 -> 2.9.1-0
  • ros-kinetic-rtt-ros-integration: 2.9.0-0 -> 2.9.1-0
  • ros-kinetic-rtt-ros-msgs: 2.9.0-0 -> 2.9.1-0
  • ros-kinetic-rtt-rosclock: 2.9.0-0 -> 2.9.1-0
  • ros-kinetic-rtt-roscomm: 2.9.0-0 -> 2.9.1-0
  • ros-kinetic-rtt-rosdeployment: 2.9.0-0 -> 2.9.1-0
  • ros-kinetic-rtt-rosgraph-msgs: 2.9.0-0 -> 2.9.1-0
  • ros-kinetic-rtt-rosnode: 2.9.0-0 -> 2.9.1-0
  • ros-kinetic-rtt-rospack: 2.9.0-0 -> 2.9.1-0
  • ros-kinetic-rtt-rosparam: 2.9.0-0 -> 2.9.1-0
  • ros-kinetic-rtt-sensor-msgs: 2.9.0-0 -> 2.9.1-0
  • ros-kinetic-rtt-shape-msgs: 2.9.0-0 -> 2.9.1-0
  • ros-kinetic-rtt-std-msgs: 2.9.0-0 -> 2.9.1-0
  • ros-kinetic-rtt-std-srvs: 2.9.0-0 -> 2.9.1-0
  • ros-kinetic-rtt-stereo-msgs: 2.9.0-0 -> 2.9.1-0
  • ros-kinetic-rtt-tf: 2.9.0-0 -> 2.9.1-0
  • ros-kinetic-rtt-trajectory-msgs: 2.9.0-0 -> 2.9.1-0
  • ros-kinetic-rtt-visualization-msgs: 2.9.0-0 -> 2.9.1-0
  • ros-kinetic-slic: 2.1.4-0 -> 2.1.6-0
  • ros-kinetic-smclib: 1.7.19-0 -> 1.8.1-0
  • ros-kinetic-speech-recognition-msgs: 4.2.0-0 -> 4.3.1-0
  • ros-kinetic-stereo-image-proc: 1.12.20-0 -> 1.12.22-0
  • ros-kinetic-teraranger: 1.0.1-0 -> 1.1.0-0
  • ros-kinetic-teraranger-array: 1.0.1-0 -> 1.2.1-0
  • ros-kinetic-teraranger-array-converter: 1.0.0-0 -> 1.1.0-0
  • ros-kinetic-test-mavros: 0.21.3-0 -> 0.21.5-0
  • ros-kinetic-tf2-web-republisher: 0.3.1-0 -> 0.3.2-0
  • ros-kinetic-topic-tools: 1.12.7-0 -> 1.12.12-0
  • ros-kinetic-tra1-bringup: 1.0.6-0 -> 1.0.7-1
  • ros-kinetic-tra1-description: 1.0.6-0 -> 1.0.7-1
  • ros-kinetic-tra1-moveit-config: 1.0.6-0 -> 1.0.7-1
  • ros-kinetic-trac-ik: 1.4.5-1 -> 1.4.6-0
  • ros-kinetic-trac-ik-examples: 1.4.5-1 -> 1.4.6-0
  • ros-kinetic-trac-ik-kinematics-plugin: 1.4.5-1 -> 1.4.6-0
  • ros-kinetic-trac-ik-lib: 1.4.5-1 -> 1.4.6-0
  • ros-kinetic-ubiquity-motor: 0.6.0-0 -> 0.6.1-0
  • ros-kinetic-urdf: 1.12.11-0 -> 1.12.12-0
  • ros-kinetic-urdf-parser-plugin: 1.12.11-0 -> 1.12.12-0
  • ros-kinetic-velocity-controllers: 0.13.0-0 -> 0.13.1-0
  • ros-kinetic-vision-opencv: 1.12.4-0 -> 1.12.7-0
  • ros-kinetic-visp: 3.0.1-3 -> 3.0.1-6
  • ros-kinetic-voice-text: 2.1.4-0 -> 2.1.6-0
  • ros-kinetic-vrpn: 0.7.33-9 -> 7.33.1-1
  • ros-kinetic-vrpn-client-ros: 0.1.1-0 -> 0.2.2-0
  • ros-kinetic-vs060: 2.0.1-0 -> 2.0.2-0
  • ros-kinetic-vs060-gazebo: 2.0.1-0 -> 2.0.2-0
  • ros-kinetic-vs060-moveit-config: 2.0.1-0 -> 2.0.2-0
  • ros-kinetic-web-video-server: 0.0.6-0 -> 0.0.7-0
  • ros-kinetic-xmlrpcpp: 1.12.7-0 -> 1.12.12-0
  • ros-kinetic-xpp: 1.0.1-0 -> 1.0.3-0
  • ros-kinetic-xpp-examples: 1.0.1-0 -> 1.0.3-0
  • ros-kinetic-xpp-hyq: 1.0.1-0 -> 1.0.3-0
  • ros-kinetic-xpp-msgs: 1.0.1-0 -> 1.0.3-0
  • ros-kinetic-xpp-quadrotor: 1.0.1-0 -> 1.0.3-0
  • ros-kinetic-xpp-states: 1.0.1-0 -> 1.0.3-0
  • ros-kinetic-xpp-vis: 1.0.1-0 -> 1.0.3-0

Removed Packages [13]:

  • ros-kinetic-bag-tools
  • ros-kinetic-cob-manipulation
  • ros-kinetic-cob-pick-place-action
  • ros-kinetic-cost-map
  • ros-kinetic-cost-map-core
  • ros-kinetic-cost-map-cv
  • ros-kinetic-cost-map-demos
  • ros-kinetic-cost-map-ros
  • ros-kinetic-cost-map-visualisations
  • ros-kinetic-rosserial-test
  • ros-kinetic-srv-tools
  • ros-kinetic-thormang3-gripper-module-msgs
  • ros-kinetic-xpp-ros-conversions

Thanks to all ROS maintainers who make packages available to the ROS community. The above list of packages was made possible by the work of the following maintainers:

  • Adam Allevato
  • Adolfo Rodriguez Tsouroukdissian
  • Alessandro Tondo
  • Alexander W. Winkler
  • Andy Zelenak
  • Ben Charrow
  • Bence Magyar
  • Blake Anderson
  • Chris Lalancette
  • Christopher Berner
  • D. Hood
  • DENSO WAVE INCORPORATED
  • Dave Coleman
  • Davide Faconti
  • Dirk Thomas
  • Ed Venator
  • Edmond DuPont
  • Elliot Johnson
  • Fabien Spindler
  • Francisco Suarez-Ruiz
  • Franka Emika GmbH
  • GROOVE X Development Team
  • Gary Servin
  • George Stavrinos
  • Ha Dang
  • Hitoshi Kamada
  • Ilya Lysenkov
  • Ingo Luetkebohle
  • Isaac I. Y. Saito
  • Jack O’Quin
  • Jim Vaughan
  • Jon Binney
  • Jose-Luis Blanco-Claraco
  • Josh Whitley
  • Junya Hayashi
  • Kareem Shehata
  • KazutoMurase
  • Kei Okada
  • Ken Tossell
  • Kevin Hallenbeck
  • Konstantin Schauwecker
  • Mahsa Parsapour
  • Manos Tsardoulias
  • Marc Alban
  • Mateusz Sadowski
  • Mathias Lüdtke
  • Mathieu Labbe
  • Max Schwarz
  • Michael Ferguson
  • Michael Görner
  • Mikael Arguedas
  • Mike Purvis
  • MoveIt Setup Assistant
  • Natalia Lyubova
  • Noda Shintaro
  • Orocos Developers
  • Patrick Beeson
  • Paul Bouchier
  • Paul Bovbel
  • Pierre-Louis Kabaradjian
  • Pyo
  • Péter Fankhauser
  • Rohan Agrawal
  • Ruben Smits
  • Russell Toris
  • Ryohei Ueda
  • Ryosuke Tajima
  • Sachin Chitta
  • Sammy Pfeiffer
  • Shengye Wang
  • Shohei Fujii
  • Stuart Glaser
  • Takuya Nakaoka
  • Timo Roehling
  • Tokyo Opensource Robotics Kyokai (TORK) Developer Team
  • Vincent Rabaud
  • Vitor Matos
  • Vladimir Ermakov
  • Xavier Artache
  • Yohei Kakiuchi
  • Youhei Kakiuchi
  • Yuki Furuta
  • Yuto Inagaki
  • dfaconti
  • ipa-frn

Posts: 1

Participants: 1

Read full topic

by @tfoote Tully Foote on December 11, 2017 08:39 AM

December 09, 2017
ROS 2 Ardent Apalone released

@dirk-thomas wrote:

We’re happy to announce the ROS 2 release Ardent Apalone!

Installation instructions and tutorials can be found on the ROS 2 wiki.

To get an idea of what’s in this release, be sure to read the Ardent page.

A few features and improvements we would like to highlight in this release:

  • The first non-beta release.
  • rviz including a few plugins (the Windows version will follow in a few weeks)
  • Different initialization options for message data structures in C++
  • Logging API improvements, now also used in the demos
  • Time support in C++ with different clocks
  • wait-for-service support in the Python client library
  • Draft implementation of REP 149 specifying format 3 of the package manifest files

While there is always more work to be done we consider several of the core components to be ready to be used by a broader audience. Therefore we have dropped the “beta” label and will support Ardent for one year, fixing bugs and keeping the release working, especially on platforms with rolling dependency releases (OS X / Windows). We’ll start a regular six month release cycle for newer versions of ROS 2. While we do aim to keep the API as stable as possible, we can’t guarantee 100% API compatibility between releases. That being said, whether or not ROS 2 is ready to be used for your application or if you can switch from ROS 1 to ROS 2 right now depends on the exact feature set and requirements of your use case. Please check the features page as well as the roadmap for more information.

As always, we invite you to try out the new software, give feedback, report bugs, and suggest features (and contribute code!): https://github.com/ros2/ros2/wiki/Contact

Your friendly neighborhood ROS 2 Team

Posts: 3

Participants: 2

Read full topic

by @dirk-thomas Dirk Thomas on December 09, 2017 10:37 PM

Super newbie asking mechanism question

@leiw wrote:

Hello,

If the ROS software successfully configuration, How to connect mechanism of legging, arm, body etc ? can someone give me example ?

Thanks

Posts: 3

Participants: 2

Read full topic

by @leiw Wilson on December 09, 2017 12:56 AM

December 06, 2017
ROS with Arduino

@Lagan_Kapoor wrote:

Hi everyone I am new in ROS . I like to make my own robot so that I can practice ROS with that robots .my first robot is robotic arm . I make one with 3. D.O.F arm and try to build 7 D.O.F of arm . how I can interface my Arduino based arm with ROS and moveIt .if anyone before work on that so help me or if any one have any resources please provide me . Guys eagerly waiting your reply

Posts: 3

Participants: 2

Read full topic

by @Lagan_Kapoor Lagan Kapoor on December 06, 2017 03:59 PM

HRI Sound Library

@DLu wrote:

There was a ton of great work that happened at Willow Garage and some of it doesn’t get the attention it deserves. This post serves to promote not my work, but the work done by Leila Takayama and the HRI team at Willow Garage.

Willow Garage HRI Sound Library

Willow Garage commissioned Skywalker Sound/Pixar sound designer EJ Holowicki (who developed sounds for BB-8 and Wall-E) to make a Creative Commons licensed library of sounds for the ROS HRI community to use.

I’ve re-hosted the files on my website above to make them easier to browse (and since the original link on the Willow Garage blog is broken).

Posts: 2

Participants: 2

Read full topic

by @DLu David!! on December 06, 2017 03:16 AM

December 05, 2017
ROS 10 Year Montage! It's Exciting

@lentinjoseph wrote:

Here is the ROS 10 Year Montage from OSRF!

Posts: 2

Participants: 2

Read full topic

by @lentinjoseph Lentin Joseph on December 05, 2017 05:28 PM

ROS Turns 10!

We're happy to be celebrating the 10th anniversary of ROS today!

On this date in 2007 the first commit was made to the ROS project on SourceForge.

Since then, ROS has grown from that first public commit to over 200000 commits made by more than 2800 individuals from around the world. These contributions have built up to over 4.5 million significant lines of code which - following standard development effort estimators - would take 169 full time developers 8.5 years.



As an open source community it's sometimes very hard to quantify the involvement in the project. To help measure what we can, we started putting together an annual Metrics report. Using these snapshots the progress of ROS is quite striking.

Charting the information over time can be seen in this post. Showing things like Monthly Unique IPs or Total Downloads year over year.

unique_ips.png

total_downloads.png

This year being a large anniversary we're happy to see that there are many others who are recognizing this historic milestone. There is already coverage in Science Robotics, , ZDNet and IEEE Spectrum

To help highlight the greater ROS community we've running a series of blog posts about some of the ROS Contributors who have helped grow the community.

Another way that we're celebrating is by making anniversary edition t-shirts available for CTurtle, Indigo, and Kinetic. You can order from the:

CTurtle was our first release with a full logo. And Indigo and Kinetic are our new current Long Term Support Releases. Get your anniversary shirt to support the ROS community by showing how many of us there are. This is a limited campaign and will end on November 21.

Of course if you'd rather have stickers, they are available from Sticker Mule.

For those of us involved in ROS since its inception, these last 10 years have gone by in the blink of an eye. We've gone from a first commit to an industry standard. The enthusiasm of this community, the creativity of the work already accomplished, and the plans to come all combine to paint a very bright picture of the future of ROS. All of us at Open Robotics and very much looking forward to the next 10 years, and beyond.

by Tully Foote on December 05, 2017 06:04 AM

December 04, 2017
Celebrating a remarkable European Robotics Week!

The European robotics community celebrated its Robotics Week (ERW) from 17th to 26th of November with more than 950 events all around the territory. This year, the house of all the regions, the European Committee of the Regions, hosted the ERW Central Event in Brussels, an event sponsored by PAL Robotics.

European-Robotics-Week-Brussels-Education-PAL

The European Robotics Week Central Event at the CoR. Picture credits: euRobotics

The diverse EU projects in which we participate stand as an example of the direction in which we want to push robotics: to make robots serve people and improve the quality of life. The ERW Central Event was a useful chance to share this vision with the European institutions and related stakeholders, who were also very enthusiastic to meet REEM-C and two TIAGos – for some, it was their very first time shaking hands with a robot!

The Co4Robots project had a special relevance at the ERW Central Event. The project aims to develop a decentralized system to control and coordinate heterogeneous robots in collaborative complex tasks. This is a key step to ensure an efficient future for robotics.

There was time for fun too! REEM-C played a bit of piano to celebrate the #DayOfMusic and could meet the youngest participants of the event, who showed us their robotic creations! Meanwhile, we couldn’t take the eyes off of the ERL with the Facebook Live streaming that we broadcasted through our screens there.

piano-kid-robots-ERW-Brussels-Committee-Regions-PAL-humanoid

The European Robotics League, at PAL Robotics!

This year PAL Robotics changed the traditional Open Day to host an European Robotics League Tournament in Barcelona! PAL Robotics’ offices were transformed to recreate a house for this Service Robotics Local Tournament. The five teams made an outstanding performance, you can check the final scores hereWe will reveal more insights on the European Robotics League outcome very soon, so stay tuned!

III Iberian Robotics Conference in Sevilla

The robotic developments of the Iberian Peninsula were also gathered together at ROBOT 2017, the III Iberian Robotics Conference hosted by Universidad de Sevilla. TIAGo also traveled to this conference and was especially attentive to the industrial applications and collaborative robotics’ debates and talks.

We enjoyed so much this European Robotics Week all over Europe, can’t wait for next year’s!

The post Celebrating a remarkable European Robotics Week! appeared first on PAL Robotics Blog.

by Judith Viladomat on December 04, 2017 12:03 PM

December 03, 2017
What do people think of the RoboWare IDE?

@Yossarian wrote:

Hello, this is my first time post on this forum so apologies if I don’t adhere to the community guidelines. Although I’m aware the Q&A website is for asking questions I thought this topic is farther reaching and more appropriate for a forum discussion.

I’m a university student who is just picking up ROS (linux and C++ as well) for a university robotics project. Reading the tutorials for ROS I have found the learning curve rather steep, and this is why I started to look for an IDE that can help me with getting started quickly. My search has lead me to the RoboWare package which is an IDE that helps users setup, manage and build ROS code (links lower down). It also features a graphical development tool that looks quite handy for a beginner.

I was really excited to find this, however I realized that not many people have used it before, and therefore I’m concerned whether it is safe or not (i.e. I’m uneasy with downloading and running random software from the internet)? The code is also not opensource, which might be a red flag. I also figured that it might be error prone and therefore might be more effort than what its worth.

So my question is this:
Is it safe to download and use Roboware?
If someone has used it before what is your experience with it?

Links:
Website: http://www.roboware.me/#/Home
Github: https://github.com/tonyrobotics/RoboWare
Only video I could find about it: https://www.youtube.com/watch?v=_NW-VFB0uMw
It is also briefly mentioned on the bottom of the ROS wiki IDE page: http://wiki.ros.org/IDEs

Posts: 6

Participants: 3

Read full topic

by @Yossarian on December 03, 2017 10:03 PM

December 01, 2017
Python API for OpenSplice

@kydos wrote:

Hello Everyone,

Do you guys know that that we’ve have had an Open Source Python API for OpenSplice for a few months now? Check it out at https://github.com/atolab/dds-python

These API allow to use topics generated from IDL or Python Classes. The examples should illustrate how they work, but don’t hesitate to post questions on GitHub.

The API is not 100% complete but provides most of the useful features and some additions – such as synchronous read and take.

Happy Hacking!

@kydos

Posts: 1

Participants: 1

Read full topic

by @kydos Angelo Corsaro on December 01, 2017 11:50 PM

November 30, 2017
New Packages for Lunar 2017-11-30

@marguedas wrote:

We’re happy to announce the availability of 40 new packages and 127 updated packages for ROS Lunar.
As always thank you to all the maintainers who are making these releases as well as all the contributors who have helped contribute to these releases. Full details are below.

Package Updates for lunar

Added Packages [40]:

  • ros-lunar-axis-camera: 0.2.1-0
  • ros-lunar-explore-lite: 2.1.0-0
  • ros-lunar-find-object-2d: 0.6.2-0
  • ros-lunar-four-wheel-steering-msgs: 1.0.0-1
  • ros-lunar-grid-map: 1.6.0-1
  • ros-lunar-grid-map-core: 1.6.0-1
  • ros-lunar-grid-map-costmap-2d: 1.6.0-1
  • ros-lunar-grid-map-cv: 1.6.0-1
  • ros-lunar-grid-map-demos: 1.6.0-1
  • ros-lunar-grid-map-filters: 1.6.0-1
  • ros-lunar-grid-map-loader: 1.6.0-1
  • ros-lunar-grid-map-msgs: 1.6.0-1
  • ros-lunar-grid-map-octomap: 1.6.0-1
  • ros-lunar-grid-map-pcl: 1.6.0-1
  • ros-lunar-grid-map-ros: 1.6.0-1
  • ros-lunar-grid-map-rviz-plugin: 1.6.0-1
  • ros-lunar-grid-map-sdf: 1.6.0-1
  • ros-lunar-grid-map-visualization: 1.6.0-1
  • ros-lunar-mqtt-bridge: 0.1.6-0
  • ros-lunar-multirobot-map-merge: 2.1.0-0
  • ros-lunar-rosserial: 0.7.7-0
  • ros-lunar-rosserial-arduino: 0.7.7-0
  • ros-lunar-rosserial-client: 0.7.7-0
  • ros-lunar-rosserial-embeddedlinux: 0.7.7-0
  • ros-lunar-rosserial-mbed: 0.7.7-0
  • ros-lunar-rosserial-msgs: 0.7.7-0
  • ros-lunar-rosserial-python: 0.7.7-0
  • ros-lunar-rosserial-server: 0.7.7-0
  • ros-lunar-rosserial-tivac: 0.7.7-0
  • ros-lunar-rosserial-windows: 0.7.7-0
  • ros-lunar-rosserial-xbee: 0.7.7-0
  • ros-lunar-vrpn: 7.33.1-5
  • ros-lunar-vrpn-client-ros: 0.2.2-0
  • ros-lunar-xpp: 1.0.3-0
  • ros-lunar-xpp-examples: 1.0.3-0
  • ros-lunar-xpp-hyq: 1.0.3-0
  • ros-lunar-xpp-msgs: 1.0.3-0
  • ros-lunar-xpp-quadrotor: 1.0.3-0
  • ros-lunar-xpp-states: 1.0.3-0
  • ros-lunar-xpp-vis: 1.0.3-0

Updated Packages [127]:

  • ros-lunar-abseil-cpp: 0.1.4-0 -> 0.2.3-0
  • ros-lunar-actionlib: 1.11.10-0 -> 1.11.11-0
  • ros-lunar-bond: 1.8.0-0 -> 1.8.1-0
  • ros-lunar-bond-core: 1.8.0-0 -> 1.8.1-0
  • ros-lunar-bondcpp: 1.8.0-0 -> 1.8.1-0
  • ros-lunar-bondpy: 1.8.0-0 -> 1.8.1-0
  • ros-lunar-camera-calibration: 1.12.20-0 -> 1.12.21-0
  • ros-lunar-camera-calibration-parsers: 1.11.12-0 -> 1.11.13-0
  • ros-lunar-camera-info-manager: 1.11.12-0 -> 1.11.13-0
  • ros-lunar-catkin: 0.7.7-2 -> 0.7.8-0
  • ros-lunar-class-loader: 0.3.7-0 -> 0.3.8-0
  • ros-lunar-cpp-common: 0.6.5-0 -> 0.6.7-0
  • ros-lunar-cv-bridge: 1.12.4-0 -> 1.12.7-0
  • ros-lunar-depth-image-proc: 1.12.20-0 -> 1.12.21-0
  • ros-lunar-diff-drive-controller: 0.13.0-0 -> 0.13.1-0
  • ros-lunar-effort-controllers: 0.13.0-0 -> 0.13.1-0
  • ros-lunar-executive-smach-visualization: 2.0.1-0 -> 2.0.2-0
  • ros-lunar-force-torque-sensor-controller: 0.13.0-0 -> 0.13.1-0
  • ros-lunar-forward-command-controller: 0.13.0-0 -> 0.13.1-0
  • ros-lunar-genpy: 0.6.6-0 -> 0.6.7-0
  • ros-lunar-gps-common: 0.1.9-0 -> 0.2.0-0
  • ros-lunar-gps-umd: 0.1.9-0 -> 0.2.0-0
  • ros-lunar-gpsd-client: 0.1.9-0 -> 0.2.0-0
  • ros-lunar-gripper-action-controller: 0.13.0-0 -> 0.13.1-0
  • ros-lunar-grpc: 0.0.5-0 -> 0.0.6-0
  • ros-lunar-image-common: 1.11.12-0 -> 1.11.13-0
  • ros-lunar-image-geometry: 1.12.4-0 -> 1.12.7-0
  • ros-lunar-image-pipeline: 1.12.20-0 -> 1.12.21-0
  • ros-lunar-image-proc: 1.12.20-0 -> 1.12.21-0
  • ros-lunar-image-publisher: 1.12.20-0 -> 1.12.21-0
  • ros-lunar-image-rotate: 1.12.20-0 -> 1.12.21-0
  • ros-lunar-image-transport: 1.11.12-0 -> 1.11.13-0
  • ros-lunar-image-view: 1.12.20-0 -> 1.12.21-0
  • ros-lunar-imu-sensor-controller: 0.13.0-0 -> 0.13.1-0
  • ros-lunar-joint-state-controller: 0.13.0-0 -> 0.13.1-0
  • ros-lunar-joint-trajectory-controller: 0.13.0-0 -> 0.13.1-0
  • ros-lunar-jsk-common-msgs: 4.2.0-0 -> 4.3.1-0
  • ros-lunar-jsk-footstep-msgs: 4.2.0-0 -> 4.3.1-0
  • ros-lunar-jsk-gui-msgs: 4.2.0-0 -> 4.3.1-0
  • ros-lunar-jsk-hark-msgs: 4.2.0-0 -> 4.3.1-0
  • ros-lunar-libmavconn: 0.21.2-0 -> 0.21.5-0
  • ros-lunar-marti-can-msgs: 0.3.0-0 -> 0.4.0-0
  • ros-lunar-marti-common-msgs: 0.3.0-0 -> 0.4.0-0
  • ros-lunar-marti-nav-msgs: 0.3.0-0 -> 0.4.0-0
  • ros-lunar-marti-perception-msgs: 0.3.0-0 -> 0.4.0-0
  • ros-lunar-marti-sensor-msgs: 0.3.0-0 -> 0.4.0-0
  • ros-lunar-marti-status-msgs: 0.3.0-0 -> 0.4.0-0
  • ros-lunar-marti-visualization-msgs: 0.3.0-0 -> 0.4.0-0
  • ros-lunar-mavlink: 2017.10.10-0 -> 2017.11.11-0
  • ros-lunar-mavros: 0.21.2-0 -> 0.21.5-0
  • ros-lunar-mavros-extras: 0.21.2-0 -> 0.21.5-0
  • ros-lunar-mavros-msgs: 0.21.2-0 -> 0.21.5-0
  • ros-lunar-message-filters: 1.13.2-0 -> 1.13.5-0
  • ros-lunar-mk: 1.14.1-0 -> 1.14.2-0
  • ros-lunar-nodelet: 1.9.12-0 -> 1.9.14-0
  • ros-lunar-nodelet-core: 1.9.12-0 -> 1.9.14-0
  • ros-lunar-nodelet-topic-tools: 1.9.12-0 -> 1.9.14-0
  • ros-lunar-opencv3: 3.2.0-6 -> 3.3.1-0
  • ros-lunar-openni2-camera: 0.2.8-0 -> 0.3.0-0
  • ros-lunar-openni2-launch: 0.2.3-0 -> 0.3.0-0
  • ros-lunar-pid: 0.0.22-0 -> 0.0.23-0
  • ros-lunar-plotjuggler: 1.3.0-0 -> 1.5.0-0
  • ros-lunar-pluginlib: 1.11.0-0 -> 1.11.2-0
  • ros-lunar-pointcloud-to-laserscan: 1.3.1-0 -> 1.4.0-0
  • ros-lunar-polled-camera: 1.11.12-0 -> 1.11.13-0
  • ros-lunar-posedetection-msgs: 4.2.0-0 -> 4.3.1-0
  • ros-lunar-position-controllers: 0.13.0-0 -> 0.13.1-0
  • ros-lunar-python-qt-binding: 0.3.2-2 -> 0.3.3-2
  • ros-lunar-qt-dotgraph: 0.3.6-0 -> 0.3.8-0
  • ros-lunar-qt-gui: 0.3.6-0 -> 0.3.8-0
  • ros-lunar-qt-gui-app: 0.3.6-0 -> 0.3.8-0
  • ros-lunar-qt-gui-core: 0.3.6-0 -> 0.3.8-0
  • ros-lunar-qt-gui-cpp: 0.3.6-0 -> 0.3.8-0
  • ros-lunar-qt-gui-py-common: 0.3.6-0 -> 0.3.8-0
  • ros-lunar-realtime-tools: 1.10.0-0 -> 1.11.0-0
  • ros-lunar-ros: 1.14.1-0 -> 1.14.2-0
  • ros-lunar-ros-comm: 1.13.2-0 -> 1.13.5-0
  • ros-lunar-ros-controllers: 0.13.0-0 -> 0.13.1-0
  • ros-lunar-ros-type-introspection: 1.0.0-0 -> 1.0.1-0
  • ros-lunar-rosbag: 1.13.2-0 -> 1.13.5-0
  • ros-lunar-rosbag-storage: 1.13.2-0 -> 1.13.5-0
  • ros-lunar-rosbash: 1.14.1-0 -> 1.14.2-0
  • ros-lunar-rosboost-cfg: 1.14.1-0 -> 1.14.2-0
  • ros-lunar-rosbuild: 1.14.1-0 -> 1.14.2-0
  • ros-lunar-rosclean: 1.14.1-0 -> 1.14.2-0
  • ros-lunar-rosconsole: 1.13.2-0 -> 1.13.5-0
  • ros-lunar-rosconsole-bridge: 0.4.4-0 -> 0.5.0-0
  • ros-lunar-roscpp: 1.13.2-0 -> 1.13.5-0
  • ros-lunar-roscpp-core: 0.6.5-0 -> 0.6.7-0
  • ros-lunar-roscpp-serialization: 0.6.5-0 -> 0.6.7-0
  • ros-lunar-roscpp-traits: 0.6.5-0 -> 0.6.7-0
  • ros-lunar-roscreate: 1.14.1-0 -> 1.14.2-0
  • ros-lunar-rosgraph: 1.13.2-0 -> 1.13.5-0
  • ros-lunar-roslang: 1.14.1-0 -> 1.14.2-0
  • ros-lunar-roslaunch: 1.13.2-0 -> 1.13.5-0
  • ros-lunar-roslib: 1.14.1-0 -> 1.14.2-0
  • ros-lunar-roslz4: 1.13.2-0 -> 1.13.5-0
  • ros-lunar-rosmake: 1.14.1-0 -> 1.14.2-0
  • ros-lunar-rosmaster: 1.13.2-0 -> 1.13.5-0
  • ros-lunar-rosmsg: 1.13.2-0 -> 1.13.5-0
  • ros-lunar-rosnode: 1.13.2-0 -> 1.13.5-0
  • ros-lunar-rosout: 1.13.2-0 -> 1.13.5-0
  • ros-lunar-rosparam: 1.13.2-0 -> 1.13.5-0
  • ros-lunar-rospy: 1.13.2-0 -> 1.13.5-0
  • ros-lunar-rosservice: 1.13.2-0 -> 1.13.5-0
  • ros-lunar-rostest: 1.13.2-0 -> 1.13.5-0
  • ros-lunar-rostime: 0.6.5-0 -> 0.6.7-0
  • ros-lunar-rostopic: 1.13.2-0 -> 1.13.5-0
  • ros-lunar-rosunit: 1.14.1-0 -> 1.14.2-0
  • ros-lunar-roswtf: 1.13.2-0 -> 1.13.5-0
  • ros-lunar-rqt-bag: 0.4.9-0 -> 0.4.11-0
  • ros-lunar-rqt-bag-plugins: 0.4.9-0 -> 0.4.11-0
  • ros-lunar-rqt-image-view: 0.4.10-0 -> 0.4.11-0
  • ros-lunar-rqt-joint-trajectory-controller: 0.13.0-0 -> 0.13.1-0
  • ros-lunar-rqt-topic: 0.4.8-0 -> 0.4.10-0
  • ros-lunar-smach-viewer: 2.0.1-0 -> 2.0.2-0
  • ros-lunar-smclib: 1.8.0-0 -> 1.8.1-0
  • ros-lunar-speech-recognition-msgs: 4.2.0-0 -> 4.3.1-0
  • ros-lunar-stereo-image-proc: 1.12.20-0 -> 1.12.21-0
  • ros-lunar-test-mavros: 0.21.2-0 -> 0.21.5-0
  • ros-lunar-topic-tools: 1.13.2-0 -> 1.13.5-0
  • ros-lunar-urdf: 1.12.11-0 -> 1.12.12-0
  • ros-lunar-urdf-parser-plugin: 1.12.11-0 -> 1.12.12-0
  • ros-lunar-velocity-controllers: 0.13.0-0 -> 0.13.1-0
  • ros-lunar-vision-opencv: 1.12.4-0 -> 1.12.7-0
  • ros-lunar-visp: 3.0.1-2 -> 3.0.1-4
  • ros-lunar-xmlrpcpp: 1.13.2-0 -> 1.13.5-0

Removed Packages [0]:

Thanks to all ROS maintainers who make packages available to the ROS community. The above list of packages was made possible by the work of the following maintainers:

  • Adolfo Rodriguez Tsouroukdissian
  • Alexander W. Winkler
  • Andy Zelenak
  • Ben Charrow
  • Bence Magyar
  • Chris Lalancette
  • D. Hood
  • Davide Faconti
  • Dirk Thomas
  • Edmond DuPont
  • Elliot Johnson
  • Fabien Spindler
  • Gary Servin
  • Isaac I. Y. Saito
  • Jack O’Quin
  • Jiri Horner
  • Jonathan Bohren
  • Junya Hayashi
  • Kareem Shehata
  • KazutoMurase
  • Kei Okada
  • Ken Tossell
  • Marc Alban
  • Mathieu Labbe
  • Michael Ferguson
  • Mikael Arguedas
  • Mike Purvis
  • Paul Bouchier
  • Paul Bovbel
  • Péter Fankhauser
  • Ryohei Ueda
  • Sachin Chitta
  • Sammy Pfeiffer
  • Shengye Wang
  • Shohei Fujii
  • Stuart Glaser
  • Timo Roehling
  • Vincent Rabaud
  • Vincent Rousseau
  • Vitor Matos
  • Vladimir Ermakov
  • Yuki Furuta
  • dfaconti

Posts: 1

Participants: 1

Read full topic

by @marguedas Mikael Arguedas on November 30, 2017 10:32 PM

The jog_arm package

@AndyZe wrote:

Just wanted to announce a new package for Cartesian jogging of robot arms. It arose from the annoyances of URscript – namely, no collision checking, no singularity handling, and no coordinate frame integration.

The package has been tested on a UR5 but it should work for any robot driver that subscribes to trajectory_msgs::JointTrajectory data. Some features:

  • The robot slows as a singularity is approached. It is possible to reverse out of singularities.

  • Most parameters are configurable via a YAML document.

  • Being multi-threaded, the node sustains a constant joint publish rate, despite incoming data rates that may vary.

  • Joint velocities are filtered to prevent abrupt jerks.

  • TODO soon: add MoveIt! collision detection.

Posts: 1

Participants: 1

Read full topic

by @AndyZe Andy on November 30, 2017 08:46 PM

November 28, 2017
3rd Robotics Craftsmanship International Academy (RobotCraft 2018)

@Micael wrote:

The call for applications for the 3rd Robotics Craftsmanship International Academy (RobotCraft 2018) is now officially open!

background3

RobotCraft is something in-between a summer camp and a collective internship promoted by Ingeniarius, a company devoted to the development of robotic solutions and other hi-tech devices, and University of Coimbra, through their Robotics Club and the Institute of Systems and Robotics. Back in 2016, RobotCraft received 65 students coming from 18 different countries. These numbers were only beaten by the second edition of the programme, RobotCraft 2017, which exceeded all expectations with 84 promising future roboticists coming from 21 different countries. RobotCraft has received students from all over the world and fields, coming from Electrical Engineering, Mechanical Engineering, Computer Sciences, Physics, Business, and others, with the common objective of developing mobile robots from scratch.

RobotCraft is way more than the typical classroom learning or even laboratory work - it is a way of living for 2 months, bounded by the common interest of learning robotics. Students will not only explore the multiple crafts around robotics, such as CAD, mechatronics, Arduino programming, ROS and AI, but also balance these technical skills promoted by mentors with keynote presentations from invited speakers.

If you have any doubt about the programme, contact us or your own national contact point (NCP):
http://robotcraft.ingeniarius.pt/hub

See you next summer in Portugal!

Posts: 1

Participants: 1

Read full topic

by @Micael Micael Couceiro on November 28, 2017 09:08 AM

November 27, 2017
Rosservice_echo.py a wannabe tool to imitate rostopic echo with services

@awesomebytes wrote:

Hey everyone,

Trying to make the best use of my jetlag I was playing around and made:

rosservice_echo

As the README says:

Just like rostopic echo /your_topic but with services.

Well, similarly.

You need to run it as root from a machine that is either doing the service calls or exposing the server. That’s because it internally uses scapy to sniff network packets.

It looks something like:

rosrun rosservice_echo rosservice_echo.py /rosout/get_loggers
[roscpp/GetLoggersRequest]:

[roscpp/GetLoggersResponse]:
loggers: 
  - 
    name: ros
    level: info
  - 
    name: ros.roscpp
    level: info
  - 
    name: ros.roscpp.roscpp_internal
    level: info
  - 
    name: ros.roscpp.superdebug
    level: warn
---

Maybe someone else is interested. It may be a baby step in order to have rosservice bag tool someday. Or just a fun toy project to discover scapy.

Posts: 1

Participants: 1

Read full topic

by @awesomebytes Sam Pfeiffer on November 27, 2017 09:10 PM

November 24, 2017
Timestamps and rosbags: discussing an alternative to clock and use_sim_time

@facontidavide wrote:

Hi,

when I play rosbags, sometimes I feel that the whole timestamp / clock /use_sim_time is hard to grasp and has many pitfalls and corner cases where it doesn’t work.

When I use rosbag play --clock and set the rosparam use_sim_time=true things work 90% of the time, but occasionally, especially with TF, this approach seems to be unreliable.

Am I the only one that had this kind of problems? Am I missing something?

I would like to implement an additional option for rosbag play to change the Header/stamp field of each message to avoid the simulated clock.

I am not asking if this is technically feasible (because I know how to implement it), I wonder if this is even desirable and if the community would find it useful; as I said, maybe the rest of the community is just happy with the default approach.

Cheers

Davide

Posts: 8

Participants: 6

Read full topic

by @facontidavide Davide Faconti on November 24, 2017 08:29 AM

November 23, 2017
[webinars] How to train new lab's new members with ROS

@YUHONG_LIN wrote:


ROS Webinar | How to train new lab’s new members with Robot Operating System (ROS)
November 30th, 2017


Dear Roboticists,

The webinar of How to train new lab’s new members with Robot Operating System (ROS) will be held on November 30, 2017 from 18:00 pm - 19:00 pm CET.

Attendance is free.
All the attendants will receive a document explaining in detail all the techniques for ROS training (only for attendants).

= Description =
Even if we would like to, engineering students do not receive proper ROS training during their undergraduate period.

This is a problem when students get engaged in the development of the Msc Thesis inside one of the labs of the University, or want to start their PhD. The students must dedicate a long time to get up to speed in ROS, before they can really use the code that is there already.

Typical option for the lab is to provide to the student with a computer, and a link to the ROS Wiki tutorials. Hence the student will pass the days and weeks trying to get the most of it.

In this one-hour webinar we will show how to smooth learning path for your interns in order to maximize their learning speed.

= Instructor =
RICARDO TÉLLEZ, Ph.D. (https://www.linkedin.com/in/ricardotellez/4)

= Pre-registration =
To assist us in planning, pre-registration is required.
Pre-registration website: http://www.theconstructsim.com/ros-webinars-train-team-ros/

= More Information =
You can contact us with questions and doubts here: info@theconstructsim.com

Posts: 1

Participants: 1

Read full topic

by @YUHONG_LIN on November 23, 2017 10:00 AM

November 21, 2017
New Packages for Indigo 2017-11-21

@tfoote wrote:

We’ve completed another sync for Indigo. This sync includes 7 new packages and 127 updates as well as one removed package.

Thank you to all the maintainers and contributors who have made this possible. Full details are listed below.

Package Updates for indigo

Added Packages [7]:

  • ros-indigo-alliance-msgs: 1.0.5-0
  • ros-indigo-baldor: 0.1.1-0
  • ros-indigo-frame-editor: 1.0.1-0
  • ros-indigo-jsk-apc: 4.2.0-0
  • ros-indigo-jsk-arc2017-baxter: 4.2.0-0
  • ros-indigo-tracetools: 0.1.0-1
  • ros-indigo-velodyne-laserscan: 1.3.0-0

Updated Packages [127]:

  • ros-indigo-abseil-cpp: 0.2.0-0 -> 0.2.3-0
  • ros-indigo-camera-calibration: 1.12.20-0 -> 1.12.21-0
  • ros-indigo-camera-calibration-parsers: 1.11.12-0 -> 1.11.13-0
  • ros-indigo-camera-info-manager: 1.11.12-0 -> 1.11.13-0
  • ros-indigo-cv-bridge: 1.11.15-0 -> 1.11.16-0
  • ros-indigo-depth-image-proc: 1.12.20-0 -> 1.12.21-0
  • ros-indigo-ethercat-manager: 1.0.6-0 -> 1.0.7-1
  • ros-indigo-fetch-calibration: 0.7.12-0 -> 0.7.13-0
  • ros-indigo-fetch-depth-layer: 0.7.12-0 -> 0.7.13-0
  • ros-indigo-fetch-description: 0.7.12-0 -> 0.7.13-0
  • ros-indigo-fetch-ikfast-plugin: 0.7.12-0 -> 0.7.13-0
  • ros-indigo-fetch-maps: 0.7.12-0 -> 0.7.13-0
  • ros-indigo-fetch-moveit-config: 0.7.12-0 -> 0.7.13-0
  • ros-indigo-fetch-navigation: 0.7.12-0 -> 0.7.13-0
  • ros-indigo-fetch-teleop: 0.7.12-0 -> 0.7.13-0
  • ros-indigo-freight-calibration: 0.7.12-0 -> 0.7.13-0
  • ros-indigo-gps-common: 0.1.9-0 -> 0.2.0-1
  • ros-indigo-gps-umd: 0.1.9-0 -> 0.2.0-1
  • ros-indigo-gpsd-client: 0.1.9-0 -> 0.2.0-1
  • ros-indigo-hrpsys-ros-bridge: 1.3.2-0 -> 1.4.1-0
  • ros-indigo-hrpsys-tools: 1.3.2-0 -> 1.4.1-0
  • ros-indigo-image-common: 1.11.12-0 -> 1.11.13-0
  • ros-indigo-image-geometry: 1.11.15-0 -> 1.11.16-0
  • ros-indigo-image-pipeline: 1.12.20-0 -> 1.12.21-0
  • ros-indigo-image-proc: 1.12.20-0 -> 1.12.21-0
  • ros-indigo-image-publisher: 1.12.20-0 -> 1.12.21-0
  • ros-indigo-image-rotate: 1.12.20-0 -> 1.12.21-0
  • ros-indigo-image-transport: 1.11.12-0 -> 1.11.13-0
  • ros-indigo-image-view: 1.12.20-0 -> 1.12.21-0
  • ros-indigo-jsk-2015-05-baxter-apc: 4.1.8-0 -> 4.2.0-0
  • ros-indigo-jsk-2016-01-baxter-apc: 4.1.8-0 -> 4.2.0-0
  • ros-indigo-jsk-apc2015-common: 4.1.8-0 -> 4.2.0-0
  • ros-indigo-jsk-apc2016-common: 4.1.8-0 -> 4.2.0-0
  • ros-indigo-jsk-arc2017-common: 4.1.8-0 -> 4.2.0-0
  • ros-indigo-marti-can-msgs: 0.3.0-0 -> 0.4.0-0
  • ros-indigo-marti-common-msgs: 0.3.0-0 -> 0.4.0-0
  • ros-indigo-marti-nav-msgs: 0.3.0-0 -> 0.4.0-0
  • ros-indigo-marti-perception-msgs: 0.3.0-0 -> 0.4.0-0
  • ros-indigo-marti-sensor-msgs: 0.3.0-0 -> 0.4.0-0
  • ros-indigo-marti-status-msgs: 0.3.0-0 -> 0.4.0-0
  • ros-indigo-marti-visualization-msgs: 0.3.0-0 -> 0.4.0-0
  • ros-indigo-minas: 1.0.6-0 -> 1.0.7-1
  • ros-indigo-minas-control: 1.0.6-0 -> 1.0.7-1
  • ros-indigo-nao-dcm-bringup: 0.0.4-0 -> 0.0.5-0
  • ros-indigo-naoqi-dcm-driver: 0.0.2-0 -> 0.0.3-0
  • ros-indigo-openni2-camera: 0.2.9-0 -> 0.3.0-0
  • ros-indigo-openni2-launch: 0.2.2-0 -> 0.3.0-0
  • ros-indigo-openrtm-ros-bridge: 1.3.2-0 -> 1.4.1-0
  • ros-indigo-openrtm-tools: 1.3.2-0 -> 1.4.1-0
  • ros-indigo-pepper-control: 0.0.3-0 -> 0.0.4-1
  • ros-indigo-pepper-dcm-bringup: 0.0.3-0 -> 0.0.5-0
  • ros-indigo-pepper-gazebo-plugin: 0.0.3-0 -> 0.0.4-1
  • ros-indigo-plotjuggler: 1.3.0-0 -> 1.4.2-0
  • ros-indigo-polled-camera: 1.11.12-0 -> 1.11.13-0
  • ros-indigo-rapid-pbd: 0.1.4-0 -> 0.2.0-0
  • ros-indigo-rapid-pbd-msgs: 0.1.1-1 -> 0.1.3-0
  • ros-indigo-roch: 1.0.14-0 -> 1.0.15-0
  • ros-indigo-roch-base: 1.0.15-0 -> 1.0.16-0
  • ros-indigo-roch-bringup: 1.0.14-0 -> 1.0.15-0
  • ros-indigo-roch-capabilities: 1.0.15-0 -> 1.0.16-0
  • ros-indigo-roch-control: 1.0.15-0 -> 1.0.16-0
  • ros-indigo-roch-description: 1.0.15-0 -> 1.0.16-0
  • ros-indigo-roch-follower: 1.0.14-0 -> 1.0.15-0
  • ros-indigo-roch-ftdi: 1.0.15-0 -> 1.0.16-0
  • ros-indigo-roch-msgs: 1.0.15-0 -> 1.0.16-0
  • ros-indigo-roch-navigation: 1.0.14-0 -> 1.0.15-0
  • ros-indigo-roch-rapps: 1.0.14-0 -> 1.0.15-0
  • ros-indigo-roch-robot: 1.0.15-0 -> 1.0.16-0
  • ros-indigo-roch-safety-controller: 1.0.15-0 -> 1.0.16-0
  • ros-indigo-roch-sensorpc: 1.0.15-0 -> 1.0.16-0
  • ros-indigo-roch-teleop: 1.0.14-0 -> 1.0.15-0
  • ros-indigo-romeo-control: 0.2.2-0 -> 0.2.3-0
  • ros-indigo-romeo-gazebo-plugin: 0.2.2-0 -> 0.2.3-0
  • ros-indigo-romeo-moveit-config: 0.2.7-0 -> 0.2.8-0
  • ros-indigo-ros-type-introspection: 1.0.0-0 -> 1.0.1-0
  • ros-indigo-rosnode-rtc: 1.3.2-0 -> 1.4.1-0
  • ros-indigo-rqt-topic: 0.4.8-0 -> 0.4.10-0
  • ros-indigo-rtmbuild: 1.3.2-0 -> 1.4.1-0
  • ros-indigo-rtmros-common: 1.3.2-0 -> 1.4.1-0
  • ros-indigo-rtt-actionlib: 2.8.5-0 -> 2.8.6-0
  • ros-indigo-rtt-actionlib-msgs: 2.8.5-0 -> 2.8.6-0
  • ros-indigo-rtt-common-msgs: 2.8.5-0 -> 2.8.6-0
  • ros-indigo-rtt-diagnostic-msgs: 2.8.5-0 -> 2.8.6-0
  • ros-indigo-rtt-dynamic-reconfigure: 2.8.5-0 -> 2.8.6-0
  • ros-indigo-rtt-geometry-msgs: 2.8.5-0 -> 2.8.6-0
  • ros-indigo-rtt-kdl-conversions: 2.8.5-0 -> 2.8.6-0
  • ros-indigo-rtt-nav-msgs: 2.8.5-0 -> 2.8.6-0
  • ros-indigo-rtt-ros: 2.8.5-0 -> 2.8.6-0
  • ros-indigo-rtt-ros-comm: 2.8.5-0 -> 2.8.6-0
  • ros-indigo-rtt-ros-integration: 2.8.5-0 -> 2.8.6-0
  • ros-indigo-rtt-ros-msgs: 2.8.5-0 -> 2.8.6-0
  • ros-indigo-rtt-rosclock: 2.8.5-0 -> 2.8.6-0
  • ros-indigo-rtt-roscomm: 2.8.5-0 -> 2.8.6-0
  • ros-indigo-rtt-rosdeployment: 2.8.5-0 -> 2.8.6-0
  • ros-indigo-rtt-rosgraph-msgs: 2.8.5-0 -> 2.8.6-0
  • ros-indigo-rtt-rosnode: 2.8.5-0 -> 2.8.6-0
  • ros-indigo-rtt-rospack: 2.8.5-0 -> 2.8.6-0
  • ros-indigo-rtt-rosparam: 2.8.5-0 -> 2.8.6-0
  • ros-indigo-rtt-sensor-msgs: 2.8.5-0 -> 2.8.6-0
  • ros-indigo-rtt-shape-msgs: 2.8.5-0 -> 2.8.6-0
  • ros-indigo-rtt-std-msgs: 2.8.5-0 -> 2.8.6-0
  • ros-indigo-rtt-std-srvs: 2.8.5-0 -> 2.8.6-0
  • ros-indigo-rtt-stereo-msgs: 2.8.5-0 -> 2.8.6-0
  • ros-indigo-rtt-tf: 2.8.5-0 -> 2.8.6-0
  • ros-indigo-rtt-trajectory-msgs: 2.8.5-0 -> 2.8.6-0
  • ros-indigo-rtt-visualization-msgs: 2.8.5-0 -> 2.8.6-0
  • ros-indigo-stereo-image-proc: 1.12.20-0 -> 1.12.21-0
  • ros-indigo-tra1-bringup: 1.0.6-0 -> 1.0.7-1
  • ros-indigo-tra1-description: 1.0.6-0 -> 1.0.7-1
  • ros-indigo-tra1-moveit-config: 1.0.6-0 -> 1.0.7-1
  • ros-indigo-urdf: 1.11.14-0 -> 1.11.15-1
  • ros-indigo-urdf-parser-plugin: 1.11.14-0 -> 1.11.15-1
  • ros-indigo-velodyne: 1.2.0-0 -> 1.3.0-0
  • ros-indigo-velodyne-driver: 1.2.0-0 -> 1.3.0-0
  • ros-indigo-velodyne-msgs: 1.2.0-0 -> 1.3.0-0
  • ros-indigo-velodyne-pointcloud: 1.2.0-0 -> 1.3.0-0
  • ros-indigo-vision-opencv: 1.11.15-0 -> 1.11.16-0
  • ros-indigo-warthog-control: 0.0.1-0 -> 0.0.2-0
  • ros-indigo-warthog-description: 0.0.1-0 -> 0.0.2-0
  • ros-indigo-warthog-msgs: 0.0.1-0 -> 0.0.2-0
  • ros-indigo-xpp: 1.0.1-1 -> 1.0.3-0
  • ros-indigo-xpp-examples: 1.0.1-1 -> 1.0.3-0
  • ros-indigo-xpp-hyq: 1.0.1-1 -> 1.0.3-0
  • ros-indigo-xpp-msgs: 1.0.1-1 -> 1.0.3-0
  • ros-indigo-xpp-quadrotor: 1.0.1-1 -> 1.0.3-0
  • ros-indigo-xpp-states: 1.0.1-1 -> 1.0.3-0
  • ros-indigo-xpp-vis: 1.0.1-1 -> 1.0.3-0

Removed Packages [1]:

  • ros-indigo-xpp-ros-conversions

Thanks to all ROS maintainers who make packages available to the ROS community. The above list of packages was made possible by the work of the following maintainers:

  • Adriano Henrique Rossette Leite
  • Alexander W. Winkler
  • Carl
  • Chris Lalancette
  • Davide Faconti
  • Dirk Thomas
  • Edmond DuPont
  • Elliot Johnson
  • Francisco Suarez-Ruiz
  • Ha Dang
  • Hasegawa Shun
  • Ingo Luetkebohle
  • Isaac I. Y. Saito
  • Jack O’Quin
  • Josh Whitley
  • Justin Huang
  • Kei Okada
  • Ken Tossell
  • Kentaro Wada
  • Marc Alban
  • Michael Ferguson
  • Natalia Lyubova
  • Orocos Developers
  • Ryosuke Tajima
  • Timo Roehling
  • Tokyo Opensource Robotics Kyokai (TORK) Developer Team
  • Tony Baltovski
  • Vincent Rabaud
  • dfaconti
  • ipa-frn

Posts: 1

Participants: 1

Read full topic

by @tfoote Tully Foote on November 21, 2017 10:24 PM

November 16, 2017
ROSCon 2018

@BrettHemes wrote:

Is it too early to know approximately when/where ROSCon will be held in 2018? I would like to attend and need to get some basic info entered to start our corporate approval process…

Posts: 4

Participants: 3

Read full topic

by @BrettHemes Brett Hemes on November 16, 2017 09:02 PM


Powered by the awesome: Planet