August 01, 2014
ROSCon Sponsors Announced
We'd like to thank the many companies who have supported ROSCon this year through sponsorship. The support of our sponsors helps us provide the highest quality meeting possible while keeping the registration fees down. Below are our sponsors for this year. If you're not familiar with what they are doing in the ROS community come by and talk with them at ROSCon.  

As a quick reminder if you have not already registered. Early registration closes on August 15th. You can register here.













It's still possible to become a sponsor. If you'd like to lend your support to ROSCon, please contact us at roscon-2014-oc@osrfoundation.org.

by Tully Foote on August 01, 2014 10:05 PM

Turtlebot Navi - What You Should Be Getting Out Of It
When you start with the navistack it's not exactly clear what performance you can and should expect from it. Expectations are that it is good (hey, pr2 used this 24/7!), but you also hear that it isn't a solution that works for all use cases and might especially struggle with non PR2 style use cases (e.g. non-holonomic configurations) very well.

The following videos demonstrate what you can and should expect from a turtlebot in indigo as it moves, at speed, through a changing world. Start them together and you should be able to see them in stereo (err sync)!



These changes were mostly a result of tuning the velocity and acceleration parameters to match your robot as well as the local planning parameters to fit your use case (reactive distances, planning bias etc).

See dwa_local_planner_params.yaml for the reference parameter configuration.

by Daniel Stonier (noreply@blogger.com) on August 01, 2014 02:00 AM

July 30, 2014
ROSCon 2014 Program Posted and Registration Open!
We're happy to announce the program for ROSCon 2014 has been posted and that registration is now open.

The early registration deadline is August 15, 2014.

ROSConChicago_Layered-200x300.png

The program fills two days with talks on applications of ROS from outer space to inside mines as well as overviews of useful tools for both research and product development. There will also be presentations on upcoming development and ongoing efforts to make ROS available on more platforms. 

In addition to the talks ROSCon will feature two lightning talk sessions and two birds of a feather sessions, all organized on-site. The lightning talks are an opportunity for you to have 3 minutes to present a topic of your choice: introduce a new project, recruit collaborators or users to an existing project, announce a product, whatever you like.

Immediately follow the lightning talks are birds of a feather sessions, which are an opportunity to propose and find people to talk about topics of interest to subgroups at the conference. This will be a mostly unstructured time with topics proposed on site and groups forming organically. 

Before you come to ROSCon, think ahead about any topic you'd like to propose for the BoF sessions and have some slides ready to present a lightning talk (3 slides or fewer).

We look forward to seeing you in Chicago in September!

by Tully Foote on July 30, 2014 02:04 AM

July 29, 2014
New Package: MAVLink to ROS generator
From Pedro Marques da Silva via ros-users@

Hi all :)


I am pleased to announce that I created a kind of Mavlink generator for ROS.

You can see the pre-release here: https://github.com/posilva/mav2rosgenerator and download from here:https://pypi.python.org/pypi/mav2rosgenerator/0.1.2

I hope this could be helpful to the ROS guys to start using mavlink to control robots.

Best 

by Tully Foote on July 29, 2014 07:10 PM

July 28, 2014
New 1D ToF Range sensor looking for testing
From Luis Rodrigues via ros-users@

I'm one of the developers of a new ToF baser 1D ranging sensor, 
that was created in one of our research projects with CERN.

We've just finished the ROS module and would like to find people in the ROS 
community that would be willing to test it/use for their projects. 

The sensor is 20g, small and the refresh rate is up to 1kHz.

We have it on sale here: www.teraranger.com/product/teraranger-one  
but for people which can provide feedback we can offer a substantial discount.

If anyone here is interested in testing it/knowing more, please contact me at: luis.rodrigues@terabee.com 

by Tully Foote on July 28, 2014 08:33 PM

July 24, 2014
Ologic Announces integration between ROS and Project Tango
From Ted Larson

OLogic has been involved with Project Tango since the very beginning of the project, however we have always had our eyes on the goal of utilizing it for robotics applications.  The solution to the problem of indoor localization and mapping is one of several areas Project Tango is focused on, and when you overlap this with robotics, it is a perfect fit.    Google has provided several SDK's for working with project Tango in either Java, C, or Unity, and has shown some impressive demos using sparse mapping under Unity, to navigate around 3D virtual worlds, or games on the device.  The phone has the ability to perform Visual Inertial Odometery (VIO), and we wanted to extend this to use within the context of ROS.  We wrote some ROSJava Nodes that use the SDK to access the VIO to publish pose, transform frames (tf), and odometry messages.  This allowed us display a URDF of a floating phone on a map, in RViz and show the position information of where the phone is located in the office, in near-real-time.  We have several demo videos of our summer intern, roaming around the office with a Project Tango phone, while we visualize the phone's position and orientation in 3D space.  It is just a starting point for all the things we want to do with Project Tango and ROS, but we have a good framework in place to add other nodes into the puzzle, and get to the point soon where we will be able to navigate a robot around the office with only a Project Tango phone for the brains.  The project is available via a public project on Github https://github.com/ologic/Tango and all the build instructions for getting it running on a Tango device is there via the Wiki.  There are lots of helpful hints and tips on building 3D maps using the Tango Mapper application (the one that Google provides), and then taking those maps and bringing them into ROS to try to navigate a space using an existing ROS robot.   We will be adding to the project continually, as it is still definitely a work-in-progress.


by Tully Foote on July 24, 2014 09:27 PM

July 22, 2014
ROS Indigo Igloo Released!

indigoigloo_600.png

Hi Everyone,


We're pleased to announce the official release of ROS Indigo Igloo! This is the first LTS release of ROS; it will be supported until April 2019 in parallel with Ubuntu Trusty Tahr. It will also be available for Saucy Salamander during its duration of support from Canonical as outlined in the ROS Distributions page.


Thanks to our many active maintainers it can be seen on the Indigo Igloo build status page that 643 packages have already been released for Indigo Igloo. And we expect this number to continuously grow over the lifetime of the distribution.


The main focus of Indigo development has been to clean up the core packages in preparation for the LTS support cycle. Efforts have included integrating the ROS packages with packages officially taken up into the upstream Debian and Ubuntu repositories such as console_bridge, urdfdom, and OpenCV.


With the release of Indigo, development will be transitioned forward to the next ROS release, Jade Turtle.  ROS Jade Turtle will be targeted for release in May 2015, following the new 12 month release cycle. Also with the beginning of development for Jade Turtle, Groovy Galapagos will reach its end-of-life. Releases into Groovy have been winding down and in the near future the build infrastructure for Groovy will be taken offline.


To get started with Indigo see the installation page. A summary of updates for packages can be found in the migration guide.


Although Indigo is now officially available, ROS distributions are living entities built on the contributions of the community.  Hydro Medusa has almost doubled the number of packages available since it was initially released 9 months ago, and Indigo is tracking a similar trajectory through it's development phases.


We'd also like to take a moment to thank the many contributors to the community who improve documentation on the wiki as well as answering questions and moderating on answers.ros.org. One of the things that distinguishes ROS is the large helpful community. We now have dozens of moderators and thousands of contributors, thank you all for your contributions!


Details of the latest updated packages in Indigo are listed below as well as updated packages for Hydro.


Your ROS Indigo Igloo Release Team


Updates to indigo


Added Packages [43]:

 * ros-indigo-ax2550: 0.1.1-0

 * ros-indigo-gazebo-ros-control: 2.4.4-0

 * ros-indigo-image-exposure-msgs: 0.9.2-0

 * ros-indigo-nav2d: 0.1.3-0

 * ros-indigo-nav2d-exploration: 0.1.3-0

 * ros-indigo-nav2d-karto: 0.1.3-0

 * ros-indigo-nav2d-localizer: 0.1.3-0

 * ros-indigo-nav2d-msgs: 0.1.3-0

 * ros-indigo-nav2d-navigator: 0.1.3-0

 * ros-indigo-nav2d-operator: 0.1.3-0

 * ros-indigo-nav2d-remote: 0.1.3-0

 * ros-indigo-nav2d-tutorials: 0.1.3-0

 * ros-indigo-ntpd-driver: 1.0.1-0

 * ros-indigo-orocos-kinematics-dynamics: 1.3.0-0

 * ros-indigo-pointgrey-camera-driver: 0.9.2-0

 * ros-indigo-rosh: 1.0.5-0

 * ros-indigo-rosh-common: 1.0.1-0

 * ros-indigo-rosh-core: 1.0.5-0

 * ros-indigo-rosh-desktop: 1.0.2-0

 * ros-indigo-rosh-desktop-plugins: 1.0.2-0

 * ros-indigo-rosh-geometry: 1.0.1-0

 * ros-indigo-rosh-robot: 1.0.1-0

 * ros-indigo-rosh-robot-plugins: 1.0.1-0

 * ros-indigo-rosh-visualization: 1.0.2-0

 * ros-indigo-roshlaunch: 1.0.5-0

 * ros-indigo-serial-utils: 0.1.0-0

 * ros-indigo-shadow-robot: 1.3.2-0

 * ros-indigo-sr-description: 1.3.2-0

 * ros-indigo-sr-example: 1.3.2-0

 * ros-indigo-sr-gazebo-plugins: 1.3.2-0

 * ros-indigo-sr-hand: 1.3.2-0

 * ros-indigo-sr-hardware-interface: 1.3.2-0

 * ros-indigo-sr-mechanism-controllers: 1.3.2-0

 * ros-indigo-sr-mechanism-model: 1.3.2-0

 * ros-indigo-sr-moveit-config: 1.3.2-0

 * ros-indigo-sr-movements: 1.3.2-0

 * ros-indigo-sr-robot-msgs: 1.3.2-0

 * ros-indigo-sr-self-test: 1.3.2-0

 * ros-indigo-sr-standalone: 1.3.2-0

 * ros-indigo-sr-tactile-sensors: 1.3.2-0

 * ros-indigo-sr-utilities: 1.3.2-0

 * ros-indigo-statistics-msgs: 0.9.2-0

 * ros-indigo-wfov-camera-msgs: 0.9.2-0



Updated Packages [94]:

 * ros-indigo-arbotix: 0.9.2-0 -> 0.10.0-0

 * ros-indigo-arbotix-controllers: 0.9.2-0 -> 0.10.0-0

 * ros-indigo-arbotix-firmware: 0.9.2-0 -> 0.10.0-0

 * ros-indigo-arbotix-msgs: 0.9.2-0 -> 0.10.0-0

 * ros-indigo-arbotix-python: 0.9.2-0 -> 0.10.0-0

 * ros-indigo-arbotix-sensors: 0.9.2-0 -> 0.10.0-0

 * ros-indigo-compressed-depth-image-transport: 1.9.0-0 -> 1.9.1-0

 * ros-indigo-compressed-image-transport: 1.9.0-0 -> 1.9.1-0

 * ros-indigo-flir-ptu-description: 0.1.3-0 -> 0.1.4-0

 * ros-indigo-flir-ptu-driver: 0.1.3-0 -> 0.1.4-0

 * ros-indigo-flir-ptu-viz: 0.1.3-0 -> 0.1.4-0

 * ros-indigo-gazebo-msgs: 2.4.3-1 -> 2.4.4-0

 * ros-indigo-gazebo-plugins: 2.4.3-1 -> 2.4.4-0

 * ros-indigo-gazebo-ros: 2.4.3-1 -> 2.4.4-0

 * ros-indigo-gazebo-ros-pkgs: 2.4.3-1 -> 2.4.4-0

 * ros-indigo-image-transport-plugins: 1.9.0-0 -> 1.9.1-0

 * ros-indigo-mavlink: 1.0.9-5 -> 1.0.9-7

 * ros-indigo-mavros: 0.5.0-0 -> 0.6.0-0

 * ros-indigo-message-filters: 1.11.6-0 -> 1.11.7-0

 * ros-indigo-mk: 1.11.2-0 -> 1.11.3-0

 * ros-indigo-opencv-candidate: 0.2.1-0 -> 0.2.3-0

 * ros-indigo-orocos-kdl: 1.2.2-2 -> 1.3.0-0

 * ros-indigo-python-orocos-kdl: 1.2.2-2 -> 1.3.0-0

 * ros-indigo-ros: 1.11.2-0 -> 1.11.3-0

 * ros-indigo-ros-comm: 1.11.6-0 -> 1.11.7-0

 * ros-indigo-ros-ethercat: 0.1.7-0 -> 0.1.8-0

 * ros-indigo-ros-ethercat-eml: 0.1.7-0 -> 0.1.8-0

 * ros-indigo-ros-ethercat-hardware: 0.1.7-0 -> 0.1.8-0

 * ros-indigo-ros-ethercat-loop: 0.1.7-0 -> 0.1.8-0

 * ros-indigo-ros-ethercat-model: 0.1.7-0 -> 0.1.8-0

 * ros-indigo-rosbag: 1.11.6-0 -> 1.11.7-0

 * ros-indigo-rosbag-storage: 1.11.6-0 -> 1.11.7-0

 * ros-indigo-rosbash: 1.11.2-0 -> 1.11.3-0

 * ros-indigo-rosboost-cfg: 1.11.2-0 -> 1.11.3-0

 * ros-indigo-rosbuild: 1.11.2-0 -> 1.11.3-0

 * ros-indigo-rosclean: 1.11.2-0 -> 1.11.3-0

 * ros-indigo-rosconsole: 1.11.6-0 -> 1.11.7-0

 * ros-indigo-rosconsole-bridge: 0.4.1-0 -> 0.4.2-0

 * ros-indigo-roscpp: 1.11.6-0 -> 1.11.7-0

 * ros-indigo-roscreate: 1.11.2-0 -> 1.11.3-0

 * ros-indigo-rosgraph: 1.11.6-0 -> 1.11.7-0

 * ros-indigo-roslang: 1.11.2-0 -> 1.11.3-0

 * ros-indigo-roslaunch: 1.11.6-0 -> 1.11.7-0

 * ros-indigo-roslib: 1.11.2-0 -> 1.11.3-0

 * ros-indigo-roslz4: 1.11.6-0 -> 1.11.7-0

 * ros-indigo-rosmake: 1.11.2-0 -> 1.11.3-0

 * ros-indigo-rosmaster: 1.11.6-0 -> 1.11.7-0

 * ros-indigo-rosmsg: 1.11.6-0 -> 1.11.7-0

 * ros-indigo-rosnode: 1.11.6-0 -> 1.11.7-0

 * ros-indigo-rosout: 1.11.6-0 -> 1.11.7-0

 * ros-indigo-rosparam: 1.11.6-0 -> 1.11.7-0

 * ros-indigo-rospy: 1.11.6-0 -> 1.11.7-0

 * ros-indigo-rosservice: 1.11.6-0 -> 1.11.7-0

 * ros-indigo-rostest: 1.11.6-0 -> 1.11.7-0

 * ros-indigo-rostopic: 1.11.6-0 -> 1.11.7-0

 * ros-indigo-rosunit: 1.11.2-0 -> 1.11.3-0

 * ros-indigo-roswtf: 1.11.6-0 -> 1.11.7-0

 * ros-indigo-rqt-action: 0.3.7-0 -> 0.3.8-0

 * ros-indigo-rqt-bag: 0.3.7-0 -> 0.3.8-0

 * ros-indigo-rqt-bag-plugins: 0.3.7-0 -> 0.3.8-0

 * ros-indigo-rqt-common-plugins: 0.3.7-0 -> 0.3.8-0

 * ros-indigo-rqt-console: 0.3.7-0 -> 0.3.8-0

 * ros-indigo-rqt-dep: 0.3.7-0 -> 0.3.8-0

 * ros-indigo-rqt-ez-publisher: 0.0.5-0 -> 0.2.0-0

 * ros-indigo-rqt-graph: 0.3.7-0 -> 0.3.8-0

 * ros-indigo-rqt-image-view: 0.3.7-0 -> 0.3.8-0

 * ros-indigo-rqt-launch: 0.3.7-0 -> 0.3.8-0

 * ros-indigo-rqt-logger-level: 0.3.7-0 -> 0.3.8-0

 * ros-indigo-rqt-msg: 0.3.7-0 -> 0.3.8-0

 * ros-indigo-rqt-plot: 0.3.7-0 -> 0.3.8-0

 * ros-indigo-rqt-publisher: 0.3.7-0 -> 0.3.8-0

 * ros-indigo-rqt-py-common: 0.3.7-0 -> 0.3.8-0

 * ros-indigo-rqt-py-console: 0.3.7-0 -> 0.3.8-0

 * ros-indigo-rqt-reconfigure: 0.3.7-0 -> 0.3.8-0

 * ros-indigo-rqt-service-caller: 0.3.7-0 -> 0.3.8-0

 * ros-indigo-rqt-shell: 0.3.7-0 -> 0.3.8-0

 * ros-indigo-rqt-srv: 0.3.7-0 -> 0.3.8-0

 * ros-indigo-rqt-top: 0.3.7-0 -> 0.3.8-0

 * ros-indigo-rqt-topic: 0.3.7-0 -> 0.3.8-0

 * ros-indigo-rqt-web: 0.3.7-0 -> 0.3.8-0

 * ros-indigo-sr-ronex: 0.9.14-0 -> 0.9.15-0

 * ros-indigo-sr-ronex-controllers: 0.9.14-0 -> 0.9.15-0

 * ros-indigo-sr-ronex-drivers: 0.9.14-0 -> 0.9.15-0

 * ros-indigo-sr-ronex-examples: 0.9.14-0 -> 0.9.15-0

 * ros-indigo-sr-ronex-external-protocol: 0.9.14-0 -> 0.9.15-0

 * ros-indigo-sr-ronex-hardware-interface: 0.9.14-0 -> 0.9.15-0

 * ros-indigo-sr-ronex-launch: 0.9.14-0 -> 0.9.15-0

 * ros-indigo-sr-ronex-msgs: 0.9.14-0 -> 0.9.15-0

 * ros-indigo-sr-ronex-test: 0.9.14-0 -> 0.9.15-0

 * ros-indigo-sr-ronex-transmissions: 0.9.14-0 -> 0.9.15-0

 * ros-indigo-sr-ronex-utilities: 0.9.14-0 -> 0.9.15-0

 * ros-indigo-theora-image-transport: 1.9.0-0 -> 1.9.1-0

 * ros-indigo-topic-tools: 1.11.6-0 -> 1.11.7-0

 * ros-indigo-xmlrpcpp: 1.11.6-0 -> 1.11.7-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:

 * Aaron Blasdel

 * Ben Charrow

 * Dan Lazewatsky

 * David Gossow

 * Dirk Thomas

 * Dorian Scholz

 * Isaac Isao Saito

 * Isaac Saito

 * John Hsu

 * Jonathan Bohren

 * Julius Kammerl

 * Maintained by Dan Lazewatsky

 * Manos Nikolaidis

 * Michael Ferguson

 * Mike Purvis

 * MoveIt Setup Assistant

 * Orocos Developers

 * Ruben Smits

 * Scott K Logan

 * Sebastian Kasperski

 * Shadow Robot's software team

 * Takashi Ogura

 * Vincent Rabaud

 * Vladimir Ermakov

 * William Woodall


Updates to hydro

Added Packages [24]:
 * ros-hydro-catkinize-this: 0.1.0-2
 * ros-hydro-easy-markers: 0.1.0-2
 * ros-hydro-laser-filtering: 0.0.1-0
 * ros-hydro-leg-detector: 1.0.4-0
 * ros-hydro-libpointmatcher: 1.2.0-0
 * ros-hydro-manifest-cleaner: 0.1.0-2
 * ros-hydro-map-laser: 0.0.1-0
 * ros-hydro-multisense-description: 1.0.0-1
 * ros-hydro-nlopt: 1.0.29-0
 * ros-hydro-object-recognition-clusters: 0.1.0-0
 * ros-hydro-orocos-kinematics-dynamics: 1.3.0-0
 * ros-hydro-people-tracking-filter: 1.0.4-0
 * ros-hydro-people-velocity-tracker: 1.0.4-0
 * ros-hydro-range-sensor-layer: 0.2.0-0
 * ros-hydro-rosbaglive: 0.1.0-2
 * ros-hydro-rosh-desktop: 1.0.2-0
 * ros-hydro-rosh-desktop-plugins: 1.0.2-0
 * ros-hydro-rosh-visualization: 1.0.2-0
 * ros-hydro-roswiki-node: 0.1.0-2
 * ros-hydro-rqt-ez-publisher: 0.2.0-0
 * ros-hydro-simple-robot-control: 0.0.2-0
 * ros-hydro-social-navigation-layers: 1.0.4-0
 * ros-hydro-speech-recognition-msgs: 1.0.29-0
 * ros-hydro-wu-ros-tools: 0.1.0-2


Updated Packages [159]:
 * ros-hydro-amcl: 1.11.9-0 -> 1.11.10-0
 * ros-hydro-assimp-devel: 1.0.27-0 -> 1.0.29-0
 * ros-hydro-base-local-planner: 1.11.9-0 -> 1.11.10-0
 * ros-hydro-bayesian-belief-networks: 1.0.27-0 -> 1.0.29-0
 * ros-hydro-bond: 1.7.13-0 -> 1.7.14-0
 * ros-hydro-bond-core: 1.7.13-0 -> 1.7.14-0
 * ros-hydro-bondcpp: 1.7.13-0 -> 1.7.14-0
 * ros-hydro-bondpy: 1.7.13-0 -> 1.7.14-0
 * ros-hydro-camera-umd: 0.2.1-0 -> 0.2.4-0
 * ros-hydro-capabilities: 0.1.1-0 -> 0.2.0-0
 * ros-hydro-carrot-planner: 1.11.9-0 -> 1.11.10-0
 * ros-hydro-checkerboard-detector: 0.1.7-0 -> 0.1.11-0
 * ros-hydro-clear-costmap-recovery: 1.11.9-0 -> 1.11.10-0
 * ros-hydro-collada-urdf-jsk-patch: 1.0.27-0 -> 1.0.29-0
 * ros-hydro-costmap-2d: 1.11.9-0 -> 1.11.10-0
 * ros-hydro-default-cfg-fkie: 0.3.11-0 -> 0.3.12-0
 * ros-hydro-depth-image-proc-jsk-patch: 1.0.27-0 -> 1.0.29-0
 * ros-hydro-downward: 1.0.27-0 -> 1.0.29-0
 * ros-hydro-dwa-local-planner: 1.11.9-0 -> 1.11.10-0
 * ros-hydro-dynamic-tf-publisher: 1.0.27-0 -> 1.0.29-0
 * ros-hydro-eus-assimp: 0.1.4-0 -> 0.1.6-0
 * ros-hydro-euscollada: 0.1.4-0 -> 0.1.6-0
 * ros-hydro-euslisp: 1.1.19-0 -> 1.1.21-0
 * ros-hydro-face-detector: 1.0.3-0 -> 1.0.4-0
 * ros-hydro-fake-localization: 1.11.9-0 -> 1.11.10-0
 * ros-hydro-ff: 1.0.27-0 -> 1.0.29-0
 * ros-hydro-ffha: 1.0.27-0 -> 1.0.29-0
 * ros-hydro-flir-ptu-description: 0.1.3-0 -> 0.1.4-0
 * ros-hydro-flir-ptu-driver: 0.1.3-0 -> 0.1.4-0
 * ros-hydro-flir-ptu-viz: 0.1.3-0 -> 0.1.4-0
 * ros-hydro-geneus: 1.1.19-0 -> 1.1.21-0
 * ros-hydro-global-planner: 1.11.9-0 -> 1.11.10-0
 * ros-hydro-gmapping: 1.3.2-1 -> 1.3.3-0
 * ros-hydro-hector-localization: 0.1.2-0 -> 0.1.3-0
 * ros-hydro-hector-pose-estimation: 0.1.2-0 -> 0.1.3-0
 * ros-hydro-hector-pose-estimation-core: 0.1.2-0 -> 0.1.3-0
 * ros-hydro-hironx-moveit-config: 1.0.14-0 -> 1.0.18-1
 * ros-hydro-hironx-ros-bridge: 1.0.14-0 -> 1.0.18-1
 * ros-hydro-image-exposure-msgs: 0.9.1-0 -> 0.9.2-0
 * ros-hydro-image-view-jsk-patch: 1.0.27-0 -> 1.0.29-0
 * ros-hydro-image-view2: 1.0.27-0 -> 1.0.29-0
 * ros-hydro-imagesift: 0.1.7-0 -> 0.1.11-0
 * ros-hydro-imu-compass: 0.0.3-0 -> 0.0.5-0
 * ros-hydro-jpeg-streamer: 0.2.1-0 -> 0.2.4-0
 * ros-hydro-jsk-common: 1.0.27-0 -> 1.0.29-0
 * ros-hydro-jsk-footstep-msgs: 1.0.27-0 -> 1.0.29-0
 * ros-hydro-jsk-gui-msgs: 1.0.27-0 -> 1.0.29-0
 * ros-hydro-jsk-hark-msgs: 1.0.27-0 -> 1.0.29-0
 * ros-hydro-jsk-interactive: 1.0.4-0 -> 1.0.5-0
 * ros-hydro-jsk-interactive-marker: 1.0.4-0 -> 1.0.5-0
 * ros-hydro-jsk-interactive-test: 1.0.4-0 -> 1.0.5-0
 * ros-hydro-jsk-model-tools: 0.1.4-0 -> 0.1.6-0
 * ros-hydro-jsk-pcl-ros: 0.1.7-0 -> 0.1.11-0
 * ros-hydro-jsk-perception: 0.1.7-0 -> 0.1.11-0
 * ros-hydro-jsk-recognition: 0.1.7-0 -> 0.1.11-0
 * ros-hydro-jsk-roseus: 1.1.19-0 -> 1.1.21-0
 * ros-hydro-jsk-rqt-plugins: 1.0.4-0 -> 1.0.5-0
 * ros-hydro-jsk-rviz-plugins: 1.0.4-0 -> 1.0.5-0
 * ros-hydro-jsk-tools: 1.0.27-0 -> 1.0.29-0
 * ros-hydro-jsk-topic-tools: 1.0.27-0 -> 1.0.29-0
 * ros-hydro-laser-filters-jsk-patch: 1.0.27-0 -> 1.0.29-0
 * ros-hydro-libsiftfast: 1.0.27-0 -> 1.0.29-0
 * ros-hydro-libuvc: 0.0.3-0 -> 0.0.5-0
 * ros-hydro-map-server: 1.11.9-0 -> 1.11.10-0
 * ros-hydro-master-discovery-fkie: 0.3.11-0 -> 0.3.12-0
 * ros-hydro-master-sync-fkie: 0.3.11-0 -> 0.3.12-0
 * ros-hydro-mavlink: 1.0.9-4 -> 1.0.9-5
 * ros-hydro-mavros: 0.5.0-0 -> 0.6.0-0
 * ros-hydro-message-to-tf: 0.1.2-0 -> 0.1.3-0
 * ros-hydro-move-base: 1.11.9-0 -> 1.11.10-0
 * ros-hydro-move-base-msgs: 1.11.9-0 -> 1.11.10-0
 * ros-hydro-move-slow-and-clear: 1.11.9-0 -> 1.11.10-0
 * ros-hydro-moveit-commander: 0.5.5-0 -> 0.5.7-0
 * ros-hydro-moveit-core: 0.5.8-0 -> 0.5.9-0
 * ros-hydro-moveit-planners: 0.5.4-0 -> 0.5.6-0
 * ros-hydro-moveit-planners-ompl: 0.5.4-0 -> 0.5.6-0
 * ros-hydro-moveit-python: 0.2.4-0 -> 0.2.5-0
 * ros-hydro-moveit-ros: 0.5.16-0 -> 0.5.19-0
 * ros-hydro-moveit-ros-benchmarks: 0.5.16-0 -> 0.5.19-0
 * ros-hydro-moveit-ros-benchmarks-gui: 0.5.16-0 -> 0.5.19-0
 * ros-hydro-moveit-ros-manipulation: 0.5.16-0 -> 0.5.19-0
 * ros-hydro-moveit-ros-move-group: 0.5.16-0 -> 0.5.19-0
 * ros-hydro-moveit-ros-perception: 0.5.16-0 -> 0.5.19-0
 * ros-hydro-moveit-ros-planning: 0.5.16-0 -> 0.5.19-0
 * ros-hydro-moveit-ros-planning-interface: 0.5.16-0 -> 0.5.19-0
 * ros-hydro-moveit-ros-robot-interaction: 0.5.16-0 -> 0.5.19-0
 * ros-hydro-moveit-ros-visualization: 0.5.16-0 -> 0.5.19-0
 * ros-hydro-moveit-ros-warehouse: 0.5.16-0 -> 0.5.19-0
 * ros-hydro-multi-map-server: 1.0.27-0 -> 1.0.29-0
 * ros-hydro-multimaster-fkie: 0.3.11-0 -> 0.3.12-0
 * ros-hydro-multimaster-msgs-fkie: 0.3.11-0 -> 0.3.12-0
 * ros-hydro-nav-core: 1.11.9-0 -> 1.11.10-0
 * ros-hydro-navfn: 1.11.9-0 -> 1.11.10-0
 * ros-hydro-navigation: 1.11.9-0 -> 1.11.10-0
 * ros-hydro-nextage-description: 0.2.14-0 -> 0.2.15-1
 * ros-hydro-nextage-moveit-config: 0.2.14-0 -> 0.2.15-1
 * ros-hydro-nextage-ros-bridge: 0.2.14-0 -> 0.2.15-1
 * ros-hydro-node-manager-fkie: 0.3.11-0 -> 0.3.12-0
 * ros-hydro-opencv-candidate: 0.2.1-0 -> 0.2.3-0
 * ros-hydro-openni-tracker-jsk-patch: 1.0.27-0 -> 1.0.29-0
 * ros-hydro-opt-camera: 1.0.27-0 -> 1.0.29-0
 * ros-hydro-orocos-kdl: 1.2.2-0 -> 1.3.0-0
 * ros-hydro-pal-vision-segmentation: 0.0.1-0 -> 1.0.0-0
 * ros-hydro-people: 1.0.3-0 -> 1.0.4-0
 * ros-hydro-people-msgs: 1.0.3-0 -> 1.0.4-0
 * ros-hydro-pointgrey-camera-driver: 0.9.1-0 -> 0.9.2-0
 * ros-hydro-posedetection-msgs: 1.0.27-0 -> 1.0.29-0
 * ros-hydro-pr2-groovy-patches: 1.0.27-0 -> 1.0.29-0
 * ros-hydro-python-orocos-kdl: 1.2.2-0 -> 1.3.0-0
 * ros-hydro-qt-build: 0.2.5-0 -> 0.2.6-0
 * ros-hydro-qt-create: 0.2.5-0 -> 0.2.6-0
 * ros-hydro-qt-ros: 0.2.5-0 -> 0.2.6-0
 * ros-hydro-qt-tutorials: 0.2.5-0 -> 0.2.6-0
 * ros-hydro-resized-image-transport: 0.1.7-0 -> 0.1.11-0
 * ros-hydro-robot-pose-ekf: 1.11.9-0 -> 1.11.10-0
 * ros-hydro-ros-ethercat: 0.1.7-0 -> 0.1.7-1
 * ros-hydro-ros-ethercat-eml: 0.1.7-0 -> 0.1.7-1
 * ros-hydro-ros-ethercat-hardware: 0.1.7-0 -> 0.1.7-1
 * ros-hydro-ros-ethercat-loop: 0.1.7-0 -> 0.1.7-1
 * ros-hydro-ros-ethercat-model: 0.1.7-0 -> 0.1.7-1
 * ros-hydro-roseus: 1.1.19-0 -> 1.1.21-0
 * ros-hydro-roseus-msgs: 1.1.19-0 -> 1.1.21-0
 * ros-hydro-roseus-smach: 1.1.19-0 -> 1.1.21-0
 * ros-hydro-rosh: 1.0.3-0 -> 1.0.5-0
 * ros-hydro-rosh-core: 1.0.3-0 -> 1.0.5-0
 * ros-hydro-roshlaunch: 1.0.3-0 -> 1.0.5-0
 * ros-hydro-rosjava-bootstrap: 0.1.21-0 -> 0.1.22-0
 * ros-hydro-rospatlite: 1.0.27-0 -> 1.0.29-0
 * ros-hydro-rosping: 1.0.27-0 -> 1.0.29-0
 * ros-hydro-rostwitter: 1.0.27-0 -> 1.0.29-0
 * ros-hydro-rotate-recovery: 1.11.9-0 -> 1.11.10-0
 * ros-hydro-rtmros-hironx: 1.0.14-0 -> 1.0.18-1
 * ros-hydro-rtmros-nextage: 0.2.14-0 -> 0.2.15-1
 * ros-hydro-sklearn: 1.0.27-0 -> 1.0.29-0
 * ros-hydro-slam-gmapping: 1.3.2-1 -> 1.3.3-0
 * ros-hydro-smclib: 1.7.13-0 -> 1.7.14-0
 * ros-hydro-sr-ronex: 0.9.14-0 -> 0.9.14-2
 * ros-hydro-sr-ronex-controllers: 0.9.14-0 -> 0.9.14-2
 * ros-hydro-sr-ronex-drivers: 0.9.14-0 -> 0.9.14-2
 * ros-hydro-sr-ronex-examples: 0.9.14-0 -> 0.9.14-2
 * ros-hydro-sr-ronex-external-protocol: 0.9.14-0 -> 0.9.14-2
 * ros-hydro-sr-ronex-hardware-interface: 0.9.14-0 -> 0.9.14-2
 * ros-hydro-sr-ronex-launch: 0.9.14-0 -> 0.9.14-2
 * ros-hydro-sr-ronex-msgs: 0.9.14-0 -> 0.9.14-2
 * ros-hydro-sr-ronex-test: 0.9.14-0 -> 0.9.14-2
 * ros-hydro-sr-ronex-transmissions: 0.9.14-0 -> 0.9.14-2
 * ros-hydro-sr-ronex-utilities: 0.9.14-0 -> 0.9.14-2
 * ros-hydro-statistics-msgs: 0.9.1-0 -> 0.9.2-0
 * ros-hydro-stereo-synchronizer: 1.0.27-0 -> 1.0.29-0
 * ros-hydro-uvc-camera: 0.2.1-0 -> 0.2.4-0
 * ros-hydro-vision-visp: 0.7.3-1 -> 0.7.4-0
 * ros-hydro-visp-auto-tracker: 0.7.3-1 -> 0.7.4-0
 * ros-hydro-visp-bridge: 0.7.3-1 -> 0.7.4-0
 * ros-hydro-visp-camera-calibration: 0.7.3-1 -> 0.7.4-0
 * ros-hydro-visp-hand2eye-calibration: 0.7.3-1 -> 0.7.4-0
 * ros-hydro-visp-tracker: 0.7.3-1 -> 0.7.4-0
 * ros-hydro-voxel-grid: 1.11.9-0 -> 1.11.10-0
 * ros-hydro-wfov-camera-msgs: 0.9.1-0 -> 0.9.2-0
 * ros-hydro-world-magnetic-model: 0.1.2-0 -> 0.1.3-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:
 * Alexander Tiderko
 * Bence Magyar
 * Carnegie Robotics
 * Dan Lazewatsky
 * Daniel Stonier
 * David Lu!!
 * David V. Lu!!
 * Esteve Fernandez
 * Fabien Spindler
 * Francois Pomerleau
 * Hiroyuki Mikita
 * Ioan Sucan
 * Isaac Isao Saito
 * Johannes Meyer
 * KazutoMurase
 * Kei Okada
 * Ken Tossell
 * Manos Nikolaidis
 * Michael Ferguson
 * Mike Purvis
 * Noda Shintaro
 * Orocos Developers
 * Prasenjit Mukherjee
 * Ruben Smits
 * Ryohei Ueda
 * Sachin Chitta
 * Shadow Robot's software team
 * Shohei Fujii
 * Takashi Ogura
 * Takuya Nakaoka
 * Vincent Rabaud
 * Vladimir Ermakov
 * William Woodall
 * Yohei Kakiuchi
 * Youhei Kakiuchi
 * Yuki Furuta
 * Yusuke Furuta
 * furuta
 * k-okada
 * lil1pal

by Tully Foote on July 22, 2014 08:38 PM

Robotnik AGVS: New ROS Open Platform for Logistics Transport

from Roberto Guzmán via ros-users@


Hi all :)

We are pleased to announce AGVS: the new Open ROS Platform for Logistics Transport. 

AGVS is an autonomous robot for indoor logistic intra-hospital transport. The robot has Ackermann kinematics and is provided with ROS architecture for simulation and control. 

This robot is currently serving in several European hospitals, and this is the first open version released. 

The provided software includes the packages for simulating the robot in several environments, generating maps, localize and define routes through a rviz interactive marker based interface.

It is an excellent starting point for anyone developing new generation logistics applications. 

You can find more info in:

Some additional information about the robot can be found in:

Enjoy it!,

  Roberto


by Ugo Cupcic on July 22, 2014 12:29 PM

July 21, 2014
Thanks for a great ROS Kong 2014!
IMG_20140606_175935760-SMILE.jpg
We want to express our thanks to everyone who made ROS Kong 2014 a great success. It was our first ROS event in Asia and it was great to see the enthusiasm from the nearby community as well as the community members who came from all around the globe. ROS Kong was designed as a complement to our annual conference ROSCon, which will happen in Chicago in September.

It took many people to make ROS Kong happen.  We'd like to give a special thanks to:

  • Our sponsors: Yujin Robot, ETRI, and GaiTech
  • Our host: The University of Hong Kong
  • Our organizers: Tully Foote, Brian Gerkey, Wyatt Newman, Daniel Stonier
  • Our volunteers: David Coleman, Annie Lam, Team HKU
  • Our speakers, who put together awesome talks.
  • Our attendees, without whom there would be no event!

The event included invited talks from ROS community members in the Australasia region. We started with a keynote from Kei Okada from the University of Tokyo. We also had talks from Paulo Borges, Chris Swetenham, Noriaki Ando, and Daniel Stonier. 

IMG_20140606_092859948.jpg
We have added links to video recordings of all the talks from the agenda and several of the presenters have provided their slides. 

We had two Lightning Talk sessions in which many attendees talked about their current work, put out calls for collaboration, or showed off new sensors or robots, such as Einstein from Hansen Robotics and the new RPLidar sensor from RoboPeak.  

IMG_20140606_152834850_HDR.jpg
In the afternoon we left a period open for Birds of a Feather sessions during which there were 16 different topics discussed. 

IMG_20140606_164334911.jpg

Over lunch, our host, The University of Hong Kong, provided us with live demos of ATLAS as well as a chance to check out the robot up close. 

IMG_20140606_125105864.jpg
We finished out the day with a reception overlooking Hong Kong in the HKU Faculty Club. 

IMG_20140606_175446460.jpg

If you'd like to see more pictures and videos of the event they are posted on the Google+ event page

 

by Tully Foote on July 21, 2014 05:44 PM

July 16, 2014
ROSCon 2014 submission deadline is Friday
If you want to achieve fame and fortune (well, maybe just fame) within the ROS community, get your proposal in today to present at ROSCon 2014!  Check the Call for Proposals for details on submitting.  The deadline is this Friday, July 18, 2014.

Thumbnail image for ROSConChicago_Layered.png

by Brian Gerkey on July 16, 2014 05:36 PM

July 12, 2014
ROS Indigo Igloo Beta 2
We are pleased to announce ROS Indigo Igloo Beta 2 today. We have resolved all the issues discovered during the first beta and plan this to be the release candidate for a final release. If everything goes well through the next ~10 days of testing we will make the final release. 

This release includes many updates as well a few new packages. The full list is below. Thank you to everyone who has worked hard to get this out. 

In the next week I encourage all maintainers and developers to review their packages as well as any Indigo relevant documentation to verify that it is up to date. Of particular note please make sure to review the migration guide [1].

[1] http://wiki.ros.org/indigo/Migration

Updates to indigo

Added Packages [3]:
 * ros-indigo-effort-controllers: 0.8.1-0
 * ros-indigo-ros-controllers: 0.8.1-0
 * ros-indigo-rqt-ez-publisher: 0.0.5-0


Updated Packages [73]:
 * ros-indigo-catkin: 0.6.7-0 -> 0.6.9-1
 * ros-indigo-diff-drive-controller: 0.8.0-1 -> 0.8.1-0
 * ros-indigo-force-torque-sensor-controller: 0.8.0-1 -> 0.8.1-0
 * ros-indigo-forward-command-controller: 0.8.0-1 -> 0.8.1-0
 * ros-indigo-genmsg: 0.5.2-0 -> 0.5.3-0
 * ros-indigo-gripper-action-controller: 0.8.0-1 -> 0.8.1-0
 * ros-indigo-imu-sensor-controller: 0.8.0-1 -> 0.8.1-0
 * ros-indigo-joint-state-controller: 0.8.0-1 -> 0.8.1-0
 * ros-indigo-joint-trajectory-controller: 0.8.0-1 -> 0.8.1-0
 * ros-indigo-message-filters: 1.11.5-0 -> 1.11.6-0
 * ros-indigo-position-controllers: 0.8.0-1 -> 0.8.1-0
 * ros-indigo-python-qt-binding: 0.2.13-0 -> 0.2.14-0
 * ros-indigo-qt-dotgraph: 0.2.24-0 -> 0.2.25-0
 * ros-indigo-qt-gui: 0.2.24-0 -> 0.2.25-0
 * ros-indigo-qt-gui-app: 0.2.24-0 -> 0.2.25-0
 * ros-indigo-qt-gui-core: 0.2.24-0 -> 0.2.25-0
 * ros-indigo-qt-gui-cpp: 0.2.24-0 -> 0.2.25-0
 * ros-indigo-qt-gui-py-common: 0.2.24-0 -> 0.2.25-0
 * ros-indigo-ros-comm: 1.11.5-0 -> 1.11.6-0
 * ros-indigo-rosbag: 1.11.5-0 -> 1.11.6-0
 * ros-indigo-rosbag-storage: 1.11.5-0 -> 1.11.6-0
 * ros-indigo-rosconsole: 1.11.5-0 -> 1.11.6-0
 * ros-indigo-roscpp: 1.11.5-0 -> 1.11.6-0
 * ros-indigo-rosgraph: 1.11.5-0 -> 1.11.6-0
 * ros-indigo-roslaunch: 1.11.5-0 -> 1.11.6-0
 * ros-indigo-roslz4: 1.11.5-0 -> 1.11.6-0
 * ros-indigo-rosmaster: 1.11.5-0 -> 1.11.6-0
 * ros-indigo-rosmsg: 1.11.5-0 -> 1.11.6-0
 * ros-indigo-rosnode: 1.11.5-0 -> 1.11.6-0
 * ros-indigo-rosout: 1.11.5-0 -> 1.11.6-0
 * ros-indigo-rospack: 2.2.3-1 -> 2.2.4-0
 * ros-indigo-rosparam: 1.11.5-0 -> 1.11.6-0
 * ros-indigo-rospy: 1.11.5-0 -> 1.11.6-0
 * ros-indigo-rosservice: 1.11.5-0 -> 1.11.6-0
 * ros-indigo-rostest: 1.11.5-0 -> 1.11.6-0
 * ros-indigo-rostopic: 1.11.5-0 -> 1.11.6-0
 * ros-indigo-roswtf: 1.11.5-0 -> 1.11.6-0
 * ros-indigo-rqt-action: 0.3.6-0 -> 0.3.7-0
 * ros-indigo-rqt-bag: 0.3.6-0 -> 0.3.7-0
 * ros-indigo-rqt-bag-plugins: 0.3.6-0 -> 0.3.7-0
 * ros-indigo-rqt-common-plugins: 0.3.6-0 -> 0.3.7-0
 * ros-indigo-rqt-console: 0.3.6-0 -> 0.3.7-0
 * ros-indigo-rqt-dep: 0.3.6-0 -> 0.3.7-0
 * ros-indigo-rqt-graph: 0.3.6-0 -> 0.3.7-0
 * ros-indigo-rqt-image-view: 0.3.6-0 -> 0.3.7-0
 * ros-indigo-rqt-launch: 0.3.6-0 -> 0.3.7-0
 * ros-indigo-rqt-logger-level: 0.3.6-0 -> 0.3.7-0
 * ros-indigo-rqt-moveit: 0.3.5-0 -> 0.3.6-0
 * ros-indigo-rqt-msg: 0.3.6-0 -> 0.3.7-0
 * ros-indigo-rqt-nav-view: 0.3.5-0 -> 0.3.6-0
 * ros-indigo-rqt-plot: 0.3.6-0 -> 0.3.7-0
 * ros-indigo-rqt-pose-view: 0.3.5-0 -> 0.3.6-0
 * ros-indigo-rqt-publisher: 0.3.6-0 -> 0.3.7-0
 * ros-indigo-rqt-py-common: 0.3.6-0 -> 0.3.7-0
 * ros-indigo-rqt-py-console: 0.3.6-0 -> 0.3.7-0
 * ros-indigo-rqt-reconfigure: 0.3.6-0 -> 0.3.7-0
 * ros-indigo-rqt-robot-dashboard: 0.3.5-0 -> 0.3.6-0
 * ros-indigo-rqt-robot-monitor: 0.3.5-0 -> 0.3.6-0
 * ros-indigo-rqt-robot-plugins: 0.3.5-0 -> 0.3.6-0
 * ros-indigo-rqt-robot-steering: 0.3.5-0 -> 0.3.6-0
 * ros-indigo-rqt-runtime-monitor: 0.3.5-0 -> 0.3.6-0
 * ros-indigo-rqt-rviz: 0.3.5-0 -> 0.3.6-0
 * ros-indigo-rqt-service-caller: 0.3.6-0 -> 0.3.7-0
 * ros-indigo-rqt-shell: 0.3.6-0 -> 0.3.7-0
 * ros-indigo-rqt-srv: 0.3.6-0 -> 0.3.7-0
 * ros-indigo-rqt-tf-tree: 0.3.5-0 -> 0.3.6-0
 * ros-indigo-rqt-top: 0.3.6-0 -> 0.3.7-0
 * ros-indigo-rqt-topic: 0.3.6-0 -> 0.3.7-0
 * ros-indigo-rqt-web: 0.3.6-0 -> 0.3.7-0
 * ros-indigo-topic-tools: 1.11.5-0 -> 1.11.6-0
 * ros-indigo-velocity-controllers: 0.8.0-1 -> 0.8.1-0
 * ros-indigo-xacro: 1.9.1-0 -> 1.9.2-0
 * ros-indigo-xmlrpcpp: 1.11.5-0 -> 1.11.6-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:
 * Aaron Blasdel
 * Adolfo Rodriguez Tsouroukdissian
 * Ben Charrow
 * Bence Magyar
 * Dan Lazewatsky
 * Dirk Thomas
 * Dorian Scholz
 * Isaac Isao Saito
 * Isaac Saito
 * Mirza A. Shah
 * Morgan Quigley
 * Sachin Chitta
 * Scott K Logan
 * Takashi Ogura
 * Vijay Pradeep
 * Wim Meeussen
 * Ze'ev Klapow

by Tully Foote on July 12, 2014 01:32 AM

July 11, 2014
ROSCon 2014 Update: Location and Logo announced, 1 week left for proposals
This is a quick update on ROSCon.

Location:
ROSCon 2014 will take place at the Palmer House, which is the same location at IROS. There is a discounted group rate available. Details are posted at http://roscon.ros.org/2014/location/

One week left for proposals:
Reminder there is just over one week left for submissions. The CFP is available at: http://roscon.ros.org/2014/call-for-proposals/

Logo:
We're pleased to reveal this years ROSCon Logo:

ROSConChicago_Layered.png

We're looking forward to seeing you there. 

by Tully Foote on July 11, 2014 08:51 AM

July 10, 2014
New Book: A Gentle Introduction to ROS
From Jason O'Kane of University of South Carolina
AGentileIntroductionToROS_cover-front.jpg
I am happy to announce a short book called A Gentle Introduction to

ROS, which is designed to ease the learning curve for new ROS users.
It aims to supplement the existing tutorials and documentation for
basic concepts like nodes, topics, messages, resource names, launch
files, parameters, services, and more.  There are example programs in
C++.  The book does not assume any previous experience with ROS, and
includes warnings about some pitfalls that, in the author's
experience, are often troublesome for beginners.  The goal is that,
after reading this book, beginners should have a strong foundation to
understand and explore the ROS ecosystem on their own.  The book is
based on the hydro distribution, with an update to indigo planned for
the near future.

To help ensure that the book is broadly useful to the community,
electronic copies are available for free from the author's website
(http://www.cse.sc.edu/~jokane/agitr).


by Tully Foote on July 10, 2014 10:49 PM

July 09, 2014
Fraunhofer IPA Press Release: Kick-off of European ROS-Industrial consortium at Fraunhofer IPA

Under the leadership of Fraunhofer IPA, the kick-off of the European ROS-Industrial consortium as well as the second international ROS-Industrial conference took place in Stuttgart, Germany, at the end of June 2014. Experts from industry and research presented ROS-Industrial key developments, applications, components and trends.

Continue reading the press release on the Fraunhofer IPA website.

ROS-Industrial Consortium-Europe Kickoff Meeting Attendees

ROS-Industrial Consortium-Europe Kickoff Meeting Attendees

More than 70 people attended the public ROS-I conference that preceded the Consortium members' meeting.

More than 70 people attended the public ROS-I conference that preceded the Consortium members' meeting.

by Paul Hvass on July 09, 2014 11:57 AM

July 03, 2014
Call for Proposals: ROSCon 2014
-------------------------------------------------
ROSCon 2014

September 12-13th, 2014  Chicago, IL, USA
Between ITMS and IROS
-------------------------------------------------

Important Dates
-------------------------------------------------

Call for Proposals -- June 23rd, 2014
Proposal submission deadline -- July 18th, 2014
Proposal acceptance notification -- July 22nd, 2014

ROSCon 
-------------------------------------------------

ROSCon 2014 is a chance for ROS developers of all levels, beginner to expert, to spend an extraordinary two days learning from and networking with the ROS community. Get tips and tricks from experts and meet and share ideas with fellow developers from around the globe.

ROSCon is a developers conference, in the model of PyCon and BoostCon. Following the success of the inaugural ROSCon in St. Paul, Minnesota (http://roscon.ros.org/2012) and last year's event in Stuttgart, Germany (http://roscon.ros.org/2013)  this year's ROSCon will be held in Chicago, Illinois. Similar to last year, the two-day program will comprise technical talks and tutorials that will introduce you to new tools and libraries, as well as teach you more about the ones you already know. The bulk of the program will be 30-40 minute presentations (some may be longer or shorter). To submit a proposal please visit the Call for Proposals page (http://roscon.ros.org/2014/call-for-proposals/)

If you don't want to make a formal presentation, you should still bring your new project or idea to ROSCon! There will be sessions of Lightning Talks, which are 5-minute mini-talks that are scheduled just-in-time at the conference. There will also be open space for Birds-of-a-Feather (BoF) meetings, impromptu hacking sessions, and informal presentations.

Submission Guidelines
------------------------------------------------

Presentations and tutorials on all topics related to ROS are invited.  Examples include introducing attendees to a ROS package or library, exploring how to use tools, manipulating sensor data, and applications for robots.

Proposals will be reviewed by an ad-hoc committee that will evaluate fit, impact, and balance.

We cannot offer sessions that are not proposed!  If there is a topic on which you would like to present, please propose it.  If you have an idea for an important topic that you do not want to present yourself, please post it to ros-users@lists.ros.org.

Topic areas
------------------------------------------------

All ROS-related work is invited. Topics of interest include:

Best practices
Useful packages and stacks
Robot-specific development
ROS Enhancement Proposals (REPs)
Safety and security
ROS in embedded systems
Product development & commercialization
Research and education
Enterprise deployment
Community organization and direction
Testing, quality, and documentation
Robotics competitions and collaborations

Proposal Submission 
------------------------------------------------

A session proposal should include:

Title
Recommended duration (Short or Long)
Summary, 100 word max (to be used in advertising the session)
Description (for review purposes): outline, goals (what will the audience learn?), pointers to packages to be discussed (500 Words Maximum)
To submit a proposal please visit: http://roscon.ros.org/review2014/

Further Info
------------------------------------------------

The event website is http://roscon.ros.org  You can contact the organizing committee at roscon-2014-oc@osrfoundation.org

by Tully Foote on July 03, 2014 05:25 PM

ROS-Industrial Update

The ROS-Industrial team has been very busy developing new functionality that I am very excited to share with you.

ROS-Industrial Hydro Release!

We officially released a few ROS-Industrial packages about six months back, and released the final package just a couple of months ago. A brief description of the new features/updates can be found here. It's now possible to install from debians: sudo apt-get install ros-hydro-industrial-desktop. More detailed instructions can be found here. We typically lag ROS releases to ensure stability, but the switch to catkin really delayed us. It feels like we transitioned to catkin twice, first to get source builds working and then a second time to get debian builds working. Having put the port to catkin behind us, I'm confident we will do better next release.

Robot Vendor Package Support

Early ROS-Industrial development was focused on developing robot specific drivers. Some of these packages were developed from scratch, such as the Fanuc package, developed by TUDelft and others were acquired as orphaned projects. In order to ensure the continued development and maintenance of these drivers, we are reaching out to the community for help. Recently, Fraunhofer IPA has taken ownership of the Universal Robot. We appreciate the help of both TUDelft and IPA. We are actively looking for developers/maintainers for our other driver packages (if you are interested send an email to this developers list).

Google Summer of Code

We are participating in the Google Summer of Code (GSoC) under the OSRF umbrella. GSoC pays students to perform open source development. ROS-Industrial has two projects: a cartesian planner GUI plugin for MoveIt (repo) and an intuitive 3D interface for industrial painting (repo). We are very excited to be part of this awesome program and are looking forward to what our students come up with. Stay tuned for posts from our students.

Special Thanks to the Community

It's no secret that ROS-Industrial is a community effort. I'm very proud to say that ROS-Industrial receives contributions from some of the best academic, research, and commercial organizations from around the world. Our current stats have us at 24 contributors in the last year and that's not even counting those who participate in code reviews and submit issues. I can honestly say I've worked with some of the greatest developers in my career through the ROS-Industrial program.

by Shaun Edwards on July 03, 2014 02:59 AM

July 02, 2014
Release of Java based ROS Client with UDPROS support
From Aaron Sims via ros-users@

Dear ROS News & ROS Users,

We recently released our Java based ROS Client in our RMDMIA Framework with the addition of functional UDPROS support. We currently are releasing our ROS Client under our Preview Evaluation License for free. We intend to use a much more open license on the ROS Client version of it after we deal with IP on our Autonomous framework. A list of tutorials is below. To enable UDP, specify UDPROS in the Preferred Protocol Column in the Configuration Manager, Save and Restart.

Thanks for any assistance you may be able to provide!

Sincerely,

Aaron Sims

Release Announcement - 6/24/2014
UDPROS protocol support added to RMDMIA slipstream 8 release. This release includes major bug fixes, new functionality, and feature enhancements.
We are building the most flexible, developer friendly, high performance ROS Client for Java. Its time to share our ROS Client with the Java Development Community. We need input on our new Robotic Controller platform, and we will be releasing incremental components to our autonomous robotic framework to Java developers. Developer registration will be required to download and use our new components. We will strongly encourage Java developers to make the RMDMIA Framework their Robotics platform for Java (Registration required).
Features:
  • Java based ROS Client integrated with TCPROS & UDPROS protocol implementations. (UDPROS is broken until the next slipstream).
  • Automated performance tuning for autonomous robotic systems (will be included in next slipstream).
  • Automated Topic/Service Discovery
  • Graphical Configuration Tool (Java only)
  • Low level datastream reader
  • A single consistent API for ROS that does not require compilation or complicated configurations to run.
  • RCSM ROS Provider API Documentation
Here is a screenshot of the ROS Configuration Manager.
ROS_Configuration_Manager.png

The Java based Robotic Software Controller Framework for the RMDMIA for Android/Java(Robotic Mission Decision Manager Intelligent Agent). API Documentation, and framework included. The RMDMIA Framework is a plugin/provider framework that is flexible enough that a developer can write a User Interface plugin that works across multiple Robotic Hardware Control Systems. This Technology Preview Release includes a configurable Timer Service, RCSM (Robot Control System Messenger) API, and ROCI (Robot Operator Control Interface) API. Implementers of ROCI, & RCSM interfaces will be able to post there plugins/providers/RMDMIA components to the Happy Artist Marketplace in the near future. 
Happy_Artist_Visio_1a.jpg

New Tutorial Announcement - 5/27/2014
  1. Tutorial: RMDMIA Client Configuration for ROS Turtlesim
  2. Tutorial: Howto build a teleoperation controller for  ROS Turtlesim with a PS/3 Joystick using the RMDMIA ROCI Provider
  3. Tutorial: Howto implement a ROS Topic Subscriber Message Handler
  4. Tutorial: Howto Publish to a ROS Topic
  5. Tutorial: Howto to call a ROS Service
  6. Tutorial: Howto to call a persistent ROS Service
  7. Tutorial: Howto implement a ROCI (Robot Operater Control Interface) Provider 

by Tully Foote on July 02, 2014 09:11 PM

July 01, 2014
ROS Japan Users Group + Kawada host a successful ROS Meetup
From Daiki Maekawa via ros-users@

by Tully Foote on July 01, 2014 11:38 PM

June 26, 2014
Robopeak announces ROS Drivers for the RPLIDAR
From ShiKai Chen

Descriptions & Images:
=====================
RPLIDAR is a low cost LIDAR sensor suitable for indoor robotic SLAM application. It provides 360 degree scan field, 5.5hz rotating frequency with guaranteed 6 meter ranger distance.  By means of the high speed image processing engine designed by RoboPeak, the whole cost are reduced greatly, RPLIDAR is the ideal sensor in cost sensitive areas like robots consumer and hardware hobbyist.

The RPLIDAR core engine performs high speed distance measurement with more than 2000 samples per second. For a scan requires 360 samples per rotation, the 5.5hz scanning frequency can be achieved. Users can customized the scanning frequency from 2hz to 10hz freely by control the speed of the scanning motor. RPLIDAR will self-adapt the current scanning speed.

ROS Node:
=====================

Videos:
====================
Odometer Free Hector map building using RPLIDAR

Scan Record:

About RoboPeak
~~~~~~~~~~~~~~~
RoboPeak is a research & development team in robotics platforms and applications, founded in 2009. Our team members are Software Engineers, Electronics Engineers and New Media Artists that all come from China.

RoboPeak develops both software and hardware, which include personal robotic platforms, Robot Operating System and related devices.

Our vision is to enrich people's daily-life with the ever-changing development and innovation in robotic technologies.

by Tully Foote on June 26, 2014 12:23 AM

June 20, 2014
Call for attendance ROS-RM. Workshop on "ROS and its applications for Robotic Manipulation"
From Pablo Gil via ros-news@

Call for Participation (apologies for multiple copies)

 

______________________________________________________

ROS-RM. Workshop on "ROS and its applications for Robotic Manipulation"

Alicante, Spain, 23 July 2014

 

Web: www.aurova.ua.es/rosrm2014

Email: rosrm@dfists.ua.es

 

REGISTRATION

 

The fee for the ROS-RM 2014 Workshop is 100 Euros.

Registration covers attendance to all lectures, handling material, two coffee breaks and one lunch from the University to Alicante city. Payment should be done by bank transfer (more information at the web site).

 

APPLICATION DEADLINE: 20 June 2014

http://www.aurova.ua.es/index.php/es/rosrmapp

 

 

VENUE

 

ROS-RM Workshop 2014 will be held at the Polytechnic College of the University of Alicante, in San Vicente del Raspeig (Alicante), Spain. Alicante is located on south east at the Mediterranean coast. The University is 15 minutes from the city center of Alicante by tram, while the Alicante airport is 20 minutes by car.

______________________________________________________

 

SPEAKERS AND PROGRAMME

 

-Juan Antonio Corrales, Marie Curie University, Paris-France

-Sachin Chitta, SRI, USA.

-Guillaume Walck, University of Bielefeld, Germany

-Federico Tombari, University of Bologna, Italy

-Toni Oliver, Shadow Robot Company, UK

 

-Session 1: ROS Architecture. Introduction and basic concepts

-Session 2: MoveIt! A Tool for Manipulation

-Session 3: Manipulation with a Dexterous Hand

-Session 4: 3D Object recognition with the PCL

-Session 5: Shadow-hand with ROS

 

___________________________________________________

 

MOTIVATION AND DESCRIPTION

 

The hands-on will be delivered by world renowned experts in the field, from both academia and industry, and will cover both theoretical and practical aspects of different tools integrated in ROS.

 

The workshop aims to provide a stimulating opportunity for young researchers and Ph.D. students. The participants will benefit from direct interaction and discussions with world leaders in ROS framework.

 

____________________________________________________

 

ORGANIZERS

- Group of Automation, Robotics and Computer Vision(http://www.aurova.ua.es)

- University of Alicante (http://www.ua.es/)

 

ROS-RM SPONSORS

- Valencia Regional Government (PROMETEO 2013/085).

 

ENDORSED BY:

- Group of Automation, Robotic and Artificial Vision (http://www.aurova.ua.es)

- University of Alicante (http://www.ua.es/)

- University Institute for Computing Research (http://www.iuii.ua.es)

____________________________________________________

 

MORE INFORMATION

 

www.aurova.ua.es/rosrm2014

rosrm@dfists.ua.es

 


Call for Participation (apologies for multiple copies)

 

______________________________________________________

ROS-RM. Workshop on "ROS and its applications for Robotic Manipulation"

Alicante, Spain, 23 July 2014

 

Web: www.aurova.ua.es/rosrm2014

Email: rosrm@dfists.ua.es

 

REGISTRATION

 

The fee for the ROS-RM 2014 Workshop is 100 Euros.

Registration covers attendance to all lectures, handling material, two coffee breaks and one lunch from the University to Alicante city. Payment should be done by bank transfer (more information at the web site).

 

APPLICATION DEADLINE: 20 June 2014

http://www.aurova.ua.es/index.php/es/rosrmapp

 

 

VENUE

 

ROS-RM Workshop 2014 will be held at the Polytechnic College of the University of Alicante, in San Vicente del Raspeig (Alicante), Spain. Alicante is located on south east at the Mediterranean coast. The University is 15 minutes from the city center of Alicante by tram, while the Alicante airport is 20 minutes by car.

______________________________________________________

 

SPEAKERS AND PROGRAMME

 

-Juan Antonio Corrales, Marie Curie University, Paris-France

-Sachin Chitta, SRI, USA.

-Guillaume Walck, University of Bielefeld, Germany

-Federico Tombari, University of Bologna, Italy

-Toni Oliver, Shadow Robot Company, UK

 

-Session 1: ROS Architecture. Introduction and basic concepts

-Session 2: MoveIt! A Tool for Manipulation

-Session 3: Manipulation with a Dexterous Hand

-Session 4: 3D Object recognition with the PCL

-Session 5: Shadow-hand with ROS

 

___________________________________________________

 

MOTIVATION AND DESCRIPTION

 

The hands-on will be delivered by world renowned experts in the field, from both academia and industry, and will cover both theoretical and practical aspects of different tools integrated in ROS.

 

The workshop aims to provide a stimulating opportunity for young researchers and Ph.D. students. The participants will benefit from direct interaction and discussions with world leaders in ROS framework.

 

____________________________________________________

 

ORGANIZERS

- Group of Automation, Robotics and Computer Vision(http://www.aurova.ua.es)

- University of Alicante (http://www.ua.es/)

 

ROS-RM SPONSORS

- Valencia Regional Government (PROMETEO 2013/085).

 

ENDORSED BY:

- Group of Automation, Robotic and Artificial Vision (http://www.aurova.ua.es)

- University of Alicante (http://www.ua.es/)

- University Institute for Computing Research (http://www.iuii.ua.es)

____________________________________________________

 

MORE INFORMATION

 

www.aurova.ua.es/rosrm2014

rosrm@dfists.ua.es

 

by Tully Foote on June 20, 2014 12:13 AM

June 18, 2014
New package: (SVO) Semi-direct Monocular Visual Odometry
From Christian Forster via ros-users@

Dear Colleagues,

We would like to draw your attention to a new open-source monocular
visual odometry algorithm called SVO (``Semi-direct Visual Odometry'').
The semi-direct approach eliminates the need of costly feature
extraction and robust matching techniques for motion estimation. Our
algorithm operates directly on pixel intensities, which results in
subpixel precision at high frame-rates (up to 70 fps on latest
smartphone processors, up to 400 fps on laptops). A probabilistic
mapping method that explicitly models outlier measurements is used to
estimate 3D points, which results in fewer outliers and more reliable
points. Precise and high frame-rate motion estimation brings increased
robustness in scenes of repetitive, and high-frequency texture.

In our group, we use SVO for vision-based, on-board ego-motion
estimation of micro aerial vehicles, which also allows them to navigate
fully autonomously.

Please check the video with a demonstration of the system capabilities:
http://youtu.be/2YnIMfw6bJY

The code is hosted on GitHub:
https://github.com/uzh-rpg/rpg_svo
A closed-source professional edition is available for commercial
purposes. Please contact us for further info.

The algorithm is described in our the paper (please cite it if you use
it for your publications):
C. Forster, M. Pizzoli, D. Scaramuzza, "SVO: Fast Semi-Direct Monocular
Visual Odometry," IEEE International Conference on Robotics and
Automation (ICRA), 2014.
PDF: http://rpg.ifi.uzh.ch/docs/ICRA14_Forster.pdf

Best regards,

Christian Forster, Matia Pizzoli, Davide Scaramuzza

Robotics and Perception Group, http://rpg.ifi.uzh.ch
University of Zurich,
Switzerland

by Tully Foote on June 18, 2014 12:19 AM

June 17, 2014
ROS-Industrial Conference and Consortium Europe kick-off

From Ulrich Reiser and Florian Weisshardt


Dear ROS-I community,

 

We cordially invite you to the following events:

 

=============================================================

ROS-Industrial Conference and Consortium Europe kick-off

=============================================================

at Fraunhofer IPA, Stuttgart, Germany

 

June 26: ROS-Industrial conference (public)

June 27: ROS-Industrial Consortium Europe Kick-Off (restricted to RIC-members)

 

Conference Objectives

---------------------------

The objective of the ROS-Industrial conference is to bring together representatives from academia and industry to exchange experiences on application development with ROS and clarify the needs of industry with respect to ROS-Industrial. The participants have the opportunity to obtain most recent information on current activities, already achieved results and future goals of the ROS-Industrial community.

 

Conference Topics:

------------------------

- Developments, Trends, Technologies in the ROS-Industrial community

- Examples of successful transfer of ROS components established in research into industrial applications

- Current ROS-Industrial Projects (hosted by the ROS-Industrial Consortium so far)

 

Target Audience

--------------------

The conference addresses in particular system integrators that aim at providing flexible, economic and manufacturer independent automation solutions, ROS-Industrial developers in research and industry, executive personal of small and medium enterprises as well as R&D divisions of larger companies in the field of automation, logistics and production.

 

Speakers

------------

-          Urko Esnaola, Tecnalia

-          Andrija Feher, Synapticon GmbH

-          Clay Flannigan, Southwest Research Institute

-          Joshua Hampp, Fraunhofer IPA

-          Gijs van der Hoorn, TU Delft Robotics Institute

-          Berend Küpers, ALTEN Nederland

-          Fabrizio Romanelli, Comau S.p.A. Robotics

-          Dirk Thomas, Open Source Robotics Foundation

-          Elisa Tosello, University of Padova

-          Florian Weißhardt, Fraunhofer IPA

 

 

General Chair

-----------------

Martin Hägele, Fraunhofer IPA

 

Session Chair

-----------------

Ulrich Reiser, Fraunhofer IPA

 

Registration

-----------------

Register for ROS-Industrial conference until June 18, 2014:

http://ric-eu.rosindustrial.org/2nd-ros-industrial-conference/

 

Link to Consortium:

http://ric-eu.rosindustrial.org/consortium/

 

 

Looking forward to meeting you at both events!



by Tully Foote on June 17, 2014 05:39 PM

MORSE CODE - PART 3
Since there are a good lot of robot simulators, Gazebo and Stage for the ROS enthusiast, V-REP and webots in the more commercial domain, OpenRave and Microsoft Robotics Developer's Studio are other options one can explore into, therefore when one comes across a new robot simulator, the obvious question is - so what is special about it ? I have been asked this question a few times about MORSE, and is usually accompanied with a comparison with Gazebo. 

My answer is, 
  • MORSE is not limited to few robots (10 for Gazebo), I have used Morse for (i) 176 small robots (ATRV) and (ii) 9 PR2 robots, in 2 separate simulations. The limit to the number of robots is not a limitation of the simulator, but rather the limitation of the CPU and graphics card.
Pic.1. Multiple PR2 simulations
  • MORSE has bindings with various middlewares ROS, YARP and MOOS, which enables it more versatility [1]. 
Pic.2. ROS binding, rviz visualisation and mapping of MORSE simulation
  • There is facility for human robot interaction. Like in motion gaming, direct input from the motion sensor (Microsoft Kinect, ASUS Xtion or Nintendo Wiimote) enables human avatar in the simulator [2]. 
Pic.3. Human avatar
  • Since everything happens through Python scripts,one need not care about compilation and executable files. MORSE is 'pythonic' [3] and can be arguably said to be an extension of Blender.
  • It is based on Blender and not Ogre, so it doesn't take up a hell lot of resources. Also, the texture and the graphics are more sleeker than Gazebo.
  • New robot models can be developed through Blender, and the developmental process is simple [4]. 
Pic.4. Blender model of the robots
  • Blender has a huge online community. Hence help and support is easy to find.
I would not be giving a very honest opinion if I do not talk about the shortcomings of MORSE,
  • Binding with ROS is a laborious process and often discourages the novice ROS user, particularly due to Python 3 and also because only certain versions of Blender works well with the MORSE + ROS + Python 3 set-up.
  • Physics simulation in Blender/MORSE is inferior to Gazebo. Getting force, torque values etc is not yet possible.
The latest release is MORSE 1.2 and more details can be found at http://www.openrobots.org/wiki/morse. A good part of this post came out of discussions at the MORSE mailing list, morse-users at laas dot fr .

REFERENCES

by Arkapravo Bhaumik (noreply@blogger.com) on June 17, 2014 08:06 AM

June 15, 2014
ROS-I Training Class Curriculum Free for Public Use

The ROS-Industrial Basic Developers' Training Class curriculum was developed under funding from the ROS-Industrial Consortium to streamline the introduction of Ubuntu Linux, ROS, ROS-I, PCL, and MoveIt! to industrial automation C++ code developers who are new to ROS. The curriculum culminates with a vision-enabled pick-and-place project. The class was first developed for the ROS-Groovy version and held in June 2013. In May 2014, we updated and extended the course for ROS-Hydro.

With the approval of the ROS-I Consortium Advisory Committee, the curriculum has been made public (Creative Commons license) and linked to the ROS-I wiki. The class materials consist of presentation slides, step-by-step instructions, and source code for exercises. Each of the exercises is intended to take approximately 30 minutes to complete. The source code is now available on the ROS-I GitHub site. Links:

by Paul Hvass on June 15, 2014 09:38 PM

June 13, 2014
ROS Spotlight: Shadow Robot's RoNeX

This ROS Spotlight introduces Shadow Robot's new platform for
connecting ROS to robot hardware.

A spin-off from he Stiff-Flop Project, RoNeX is designed specially for cutting edge robotics prototyping and development. RoNeX provides a high speed, modular I/O network that fully integrates with ROS straight out of the box, accessible directly on ROS topics or within standard ROS controllers.

Utilising the industrial strenght real-time EtherCAT field-bus, RoNeX has 100Mbps of bandwidth available, and maintains a 1 kHz update rate on all channels allowing for real time joint control from a ROS Host.

To show just how easy it is to build a robot with RoNeX, Shadow has done just that in this video:

Using standard ROS packages for joint control, kinematics, path planning and visualisation, Shadow needed only ten new lines of code plus a URDF file automatically generated from Solidworks to drive the robot!

The Shadow team is releasing RoNeX with three Modules available now and are putting the final touches to a roadmap that includes motor drivers, ability to daisy chain RoNeX stacks and Dev Kits for advanced users and OEMs.

To find out more about RoNeX visit the Shadow Website.

RoNeX drivers are open source on Github and the user manual is here.

by Tully Foote on June 13, 2014 05:09 PM


Powered by the awesome: Planet