September 2015 Archives

From Bert Willaert via ros-users@

Since its inception, Intermodalics' journey has been an amazing trip in a varied landscape. We're solving problems for high-end industries worldwide and for small businesses in our vicinity. Yet both are depending on extremely reliable robotic solutions. Numerous technologies are part of these solutions: 3D vision and reconstruction, 3D robot simulation and collision checking, real-time robot control, man-safe robotics, fieldbus deployment or large scale communication networks. Solving today's robotic challenges requires a creative and multi-disciplinary approach. This is exactly what we love in a project.

See our jobs page for more information: http://www.intermodalics.eu/jobs

Also, the entire Intermodalics team will be present at ROSCON in Hamburg. We are looking forward to meeting interested candidates there! 

ROSCon 2015: sold out, and live streaming

| No Comments | No TrackBacks
For the first time, this year we have sold out registration for ROSCon!

Due to the capacity limit on the venue at University of Hamburg, we
can't accommodate any more registrations.  We will *not* have on-site
registration this year.  If you haven't received an email confirmation
of your registration, then we won't be able to admit you to the event.

If you're interested in ROSCon but weren't able to register, you still
have options for enjoying the event:

* Thanks to generous sponsorship from Qualcomm, we're live-streaming
all the ROSCon talks, free of charge.  Closer to the event, a link to
the streaming site will be posted here:
  http://roscon.ros.org/2015/#live-streaming

* As in previous years, we will post videos of the ROSCon talks after
the event, free of charge.

* We are maintaining a waiting list, which is being processed as slots
open up; if you'd like to be added to that list, send email to
roscon-2015-oc@osrfoundation.org.

Thanks for all your support, and we're looking forward to a great ROSCon 2015!

- your ROSCon 2015 Organizing Committee

~~~
Thanks again to our Platinum Sponsors: Canonical / Ubuntu and Fetch Robotics!
And our Gold Sponsors: 3D Robotics, Bosch, Clearpath Robotics,
GaiTech, Magazino, NVIDIA, Qualcomm, Rethink Robotics, ROBOTIS,
Robotnik, ROS-Industrial, Shadow Robot, SICK, and Synapticon!
~~~
From Clearpath Robotics:

Modern factories and warehouses need to be reconfigurable, responsive, and efficient to survive. Designed to address these conditions, OTTO uses the same underlying self-driving technology popularized by the Google self-driving car.  The system delivers dynamic and efficient transport in increasingly congested industrial operations.  Traditional material handling systems require costly and rigid changes to infrastructure, cannot adapt to a changing environment, and are not safe for collaboration with warehouse personnel.  OTTO does not rely on external infrastructure for navigation, making implementation hassle-free and highly scalable.  It can transport 3300 lb loads at speeds up to 4.5 mph, while tracking along optimal paths and safely avoiding collisions.


 
"North American manufacturers are constantly under pressure to find new ways to gain an edge against low-cost offshore competition. Traditional automation is saturating.  But what about the more complex tasks too difficult or expensive to automate?" said Matt Rendall, CEO and Co-Founder of Clearpath Robotics.  "We created OTTO to reinvent material transport and give North American manufacturers a new edge."
 
Applications for OTTO include moving pallets in a warehouse or cross-dock, and for kitting or assembly line delivery.  OTTO units are currently deployed in five test facilities, the first of which belonging to GE.

ROS Gentoo Status

| No Comments | No TrackBacks
From Allen Hunter via ros-users@

thought I would take a moment to update you all on the current status
of ROS Gentoo (Woot).

Namely, the location of the overly has moved! It is now located at
ros/ros-overlay as opposed to allenh1/ros-overlay. The wiki has been
changed to reflect this move.

Also, as a neat side-note, Gazebo is working!

Finally, an ebuild was created for the most recent release of wstool.
From Paul Bovbel via ros-users@

As part of a summer hack project at Clearpath Robotics, I've released a ROS package [http://wiki.ros.org/vrpn_client_ros] wrapping the VRPN client library. This package provides support for exposing information on VRPN Tracker devices (pose, velocity, acceleration data) into ROS. 

We've tested it in house with VICON and OptiTrack mocap systems - please keep in mind that neither system exposes velocity or acceleration data over VRPN. Any feedback, bug reports, or validation is greatly appreciated!

A list of VRPN supported devices can be found here [https://github.com/vrpn/vrpn/wiki/Supported-hardware-devices]

ROS at Robot Launch 2015

| No Comments | No TrackBacks

It was great to see all the different pitches at Robot Launch 2015 Finals

You can see the results announced on twitter here

We're proud to say that 1/3rd of the Robot Launch startups used ROS.

The Construct won the "Industrial Robotics Award" sponsored by Siemens as well as the "Readers Pick"


And Luvozo won the "Robot Launch ROS Award" sponsored by Clearpath Robotics.


Another ROS company,Erle Robotics, also earned an honorable mention.

MoveIt! website changes

| No Comments | No TrackBacks
From Sachin Chitta via ros-users@

The MoveIt! webpage has been moved to use github-pages, thanks to help from MoveIt! user Praveen Singh. This makes it easier to maintain (the old webpage setup based on Wordpress was outdated and broken). 

As a result of this move, the old MoveIt! wiki no longer exists. We do have a backup of it and can move information over if needed. The documentation in the Wiki was outdated, so please let me know if there's particular parts of the Wiki that should be ported over. A redirect has been added for moveit.ros.org/wiki

If you are willing to contribute tutorials and documentation (or anything else), PRs are welcome against the relevant github repo: https://github.com/julienking/julienking.github.io

wstool/rosws updates

| No Comments | No TrackBacks
From Thibault Kruse via ros-users@

the latest release of wstool (1.6 -> 1.9.1) provides some minor improvements I'd like to advertise.

Highlights:
- 'wstool info' provides more information about (git) branches and remote state
- There is a new 'wstool foreach' sub-command that allows to execute shell scripts inside all or selected repositories (similar to vcstool's 'custom' command)
- manpages and bash/zsh completion scripts are also packaged
- 'wstool set ... --update' updates new / changed repositories

Thanks to Kentaro Wada for the initiative and coding effort.

The complete changelog is available at
https://raw.githubusercontent.com/vcstools/wstool/master/doc/changelog.rst

Report any issues to https://github.com/vcstools/wstool/issues

ROS package for Basler cameras

| No Comments | No TrackBacks
From Beatriz Leon Pinzon via ros-users@

We have created a ROS package to be able to publish images using a Basler camera. We have a Basler Dart camera but the package should work with any of their cameras as all use the same API.

Here is the github address:
https://github.com/shadow-robot/basler_camera

Their cameras are not yet uvc compatible so this package would be helpful in the meantime.

ROS Hydromedusa Final Release

| No Comments | No TrackBacks
Hi Everyone, 

We again have reached another milestone which is the End of Life ROS Hydromedusa. We have reached the final release with 223 updated packages and 15 new packages. Full details are below. 

Hydro has had a long history over 877 days with commits on 743 of those days. We had 241 individual contributors submitting 4879 commits which is an average of 5.4 commits per day. There were 1690 packages released and built into debian packages in the hydro rosdistro as well as uncounted packages maintained outside the public release pipeline.

Here's a visualization of the public rosdistro releases for Hydro over the course of it's development cycle:

As we've reached EOL we will begin the process of tearing down the Hydro buildfarm. 

Please take a moment and thank anyone you know who has released packages into Hydro. The thousands of releases into the rosdistro are what drives our community and helps create value for everyone.

You ROS Release Team


Updates to hydro

Added Packages [15]:
 * ros-hydro-cob-scan-unifier: 0.5.3-0
 * ros-hydro-eusurdf: 0.1.13-0
 * ros-hydro-ir-trans-drivers: 0.0.4-0
 * ros-hydro-jsk-201504-miraikan: 0.0.11-0
 * ros-hydro-jsk-3rdparty: 2.0.8-0
 * ros-hydro-jsk-common-msgs: 2.0.0-1
 * ros-hydro-jsk-recognition-utils: 0.3.6-0
 * ros-hydro-jsk-robot-utils: 0.0.11-0
 * ros-hydro-libcmt: 2.0.8-0
 * ros-hydro-roseus-mongo: 1.3.9-0
 * ros-hydro-roseus-remote: 0.0.11-0
 * ros-hydro-rosjava: 0.1.1-0
 * ros-hydro-rosjava-core: 0.1.6-0
 * ros-hydro-rosjava-extras: 0.1.5-0
 * ros-hydro-rosjava-messages: 0.1.345-0


Updated Packages [223]:
 * ros-hydro-ackermann-msgs: 0.9.1-0 -> 1.0.0-0
 * ros-hydro-app-manager: 1.0.2-0 -> 1.0.3-0
 * ros-hydro-assimp-devel: 1.0.71-0 -> 2.0.8-0
 * ros-hydro-baxtereus: 0.0.6-0 -> 0.0.11-0
 * ros-hydro-bayesian-belief-networks: 1.0.71-0 -> 2.0.8-0
 * ros-hydro-catkinize-this: 0.2.3-0 -> 0.2.4-0
 * ros-hydro-checkerboard-detector: 0.2.12-0 -> 0.3.6-0
 * ros-hydro-cob-linear-nav: 0.5.1-2 -> 0.5.3-0
 * ros-hydro-cob-mapping-slam: 0.5.1-2 -> 0.5.3-0
 * ros-hydro-cob-navigation: 0.5.1-2 -> 0.5.3-0
 * ros-hydro-cob-navigation-config: 0.5.1-2 -> 0.5.3-0
 * ros-hydro-cob-navigation-global: 0.5.1-2 -> 0.5.3-0
 * ros-hydro-cob-navigation-local: 0.5.1-2 -> 0.5.3-0
 * ros-hydro-cob-navigation-slam: 0.5.1-2 -> 0.5.3-0
 * ros-hydro-collada-urdf-jsk-patch: 1.0.71-0 -> 2.0.8-0
 * ros-hydro-depthcloud-encoder: 0.0.4-0 -> 0.0.5-0
 * ros-hydro-diagnostic-aggregator: 1.8.7-0 -> 1.8.8-0
 * ros-hydro-diagnostic-analysis: 1.8.7-0 -> 1.8.8-0
 * ros-hydro-diagnostic-common-diagnostics: 1.8.7-0 -> 1.8.8-0
 * ros-hydro-diagnostic-updater: 1.8.7-0 -> 1.8.8-0
 * ros-hydro-diagnostics: 1.8.7-0 -> 1.8.8-0
 * ros-hydro-downward: 1.0.71-0 -> 2.0.8-0
 * ros-hydro-dynamic-tf-publisher: 1.0.71-0 -> 2.0.3-0
 * ros-hydro-easy-markers: 0.2.3-0 -> 0.2.4-0
 * ros-hydro-ethercat-hardware: 1.8.11-0 -> 1.8.15-0
 * ros-hydro-eus-assimp: 0.1.12-0 -> 0.1.13-0
 * ros-hydro-eus-nlopt: 0.1.5-0 -> 0.1.6-1
 * ros-hydro-eus-qp: 0.1.5-0 -> 0.1.6-1
 * ros-hydro-eus-qpoases: 0.1.5-0 -> 0.1.6-1
 * ros-hydro-euscollada: 0.1.12-0 -> 0.1.13-0
 * ros-hydro-eusgazebo: 0.1.8-0 -> 0.1.9-0
 * ros-hydro-euslisp: 9.12.2-0 -> 9.15.1-0
 * ros-hydro-ff: 1.0.71-0 -> 2.0.8-0
 * ros-hydro-ffha: 1.0.71-0 -> 2.0.8-0
 * ros-hydro-fingertip-pressure: 1.8.11-0 -> 1.8.15-0
 * ros-hydro-geneus: 2.2.2-0 -> 2.2.4-0
 * ros-hydro-hironx-calibration: 1.0.31-0 -> 1.0.37-0
 * ros-hydro-hironx-moveit-config: 1.0.31-0 -> 1.0.37-0
 * ros-hydro-hironx-ros-bridge: 1.0.31-0 -> 1.0.37-0
 * ros-hydro-hrpsys: 315.4.0-0 -> 315.7.0-2
 * ros-hydro-hrpsys-gazebo-general: 0.1.8-0 -> 0.1.9-0
 * ros-hydro-hrpsys-gazebo-msgs: 0.1.8-0 -> 0.1.9-0
 * ros-hydro-hrpsys-ros-bridge: 1.2.12-0 -> 1.2.14-0
 * ros-hydro-hrpsys-tools: 1.2.12-0 -> 1.2.14-0
 * ros-hydro-image-view2: 1.0.71-0 -> 2.0.3-0
 * ros-hydro-imagesift: 0.2.12-0 -> 0.3.6-0
 * ros-hydro-imu-filter-madgwick: 1.0.4-0 -> 1.0.5-0
 * ros-hydro-imu-tools: 1.0.4-0 -> 1.0.5-0
 * ros-hydro-joy-listener: 0.2.3-0 -> 0.2.4-0
 * ros-hydro-joy-mouse: 0.1.5-0 -> 0.1.6-1
 * ros-hydro-jsk-baxter-desktop: 0.0.6-0 -> 0.0.11-0
 * ros-hydro-jsk-baxter-startup: 0.0.6-0 -> 0.0.11-0
 * ros-hydro-jsk-baxter-web: 0.0.6-0 -> 0.0.11-0
 * ros-hydro-jsk-calibration: 0.1.5-0 -> 0.1.6-1
 * ros-hydro-jsk-common: 1.0.71-0 -> 2.0.3-0
 * ros-hydro-jsk-data: 1.0.71-0 -> 2.0.3-0
 * ros-hydro-jsk-footstep-controller: 0.1.5-0 -> 0.1.6-1
 * ros-hydro-jsk-footstep-msgs: 1.0.71-0 -> 2.0.0-1
 * ros-hydro-jsk-footstep-planner: 0.1.5-0 -> 0.1.6-1
 * ros-hydro-jsk-gui-msgs: 1.0.71-0 -> 2.0.0-1
 * ros-hydro-jsk-hark-msgs: 1.0.71-0 -> 2.0.0-1
 * ros-hydro-jsk-ik-server: 0.1.5-0 -> 0.1.6-1
 * ros-hydro-jsk-interactive: 1.0.20-0 -> 1.0.24-0
 * ros-hydro-jsk-interactive-marker: 1.0.20-0 -> 1.0.24-0
 * ros-hydro-jsk-interactive-test: 1.0.20-0 -> 1.0.24-0
 * ros-hydro-jsk-model-tools: 0.1.12-0 -> 0.1.13-0
 * ros-hydro-jsk-nao-startup: 0.0.6-0 -> 0.0.11-0
 * ros-hydro-jsk-network-tools: 1.0.71-0 -> 2.0.3-0
 * ros-hydro-jsk-pcl-ros: 0.2.12-0 -> 0.3.6-0
 * ros-hydro-jsk-pepper-startup: 0.0.6-0 -> 0.0.11-0
 * ros-hydro-jsk-perception: 0.2.12-0 -> 0.3.6-0
 * ros-hydro-jsk-planning: 0.1.3-0 -> 0.1.4-1
 * ros-hydro-jsk-pr2-calibration: 0.0.6-0 -> 0.0.11-0
 * ros-hydro-jsk-pr2-startup: 0.0.6-0 -> 0.0.11-0
 * ros-hydro-jsk-pr2eus: 0.1.10-0 -> 0.1.11-0
 * ros-hydro-jsk-recognition: 0.2.12-0 -> 0.3.6-0
 * ros-hydro-jsk-recognition-msgs: 0.2.12-0 -> 0.3.6-0
 * ros-hydro-jsk-robot-startup: 0.0.6-0 -> 0.0.11-0
 * ros-hydro-jsk-roseus: 1.3.5-0 -> 1.3.9-0
 * ros-hydro-jsk-rqt-plugins: 1.0.20-0 -> 1.0.24-0
 * ros-hydro-jsk-rviz-plugins: 1.0.20-0 -> 1.0.24-0
 * ros-hydro-jsk-teleop-joy: 0.1.5-0 -> 0.1.6-1
 * ros-hydro-jsk-tilt-laser: 1.0.71-0 -> 2.0.3-0
 * ros-hydro-jsk-tools: 1.0.71-0 -> 2.0.3-0
 * ros-hydro-jsk-topic-tools: 1.0.71-0 -> 2.0.3-0
 * ros-hydro-jsk-visualization: 1.0.20-0 -> 1.0.24-0
 * ros-hydro-jskeus: 1.0.6-0 -> 1.0.10-0
 * ros-hydro-julius: 1.0.71-0 -> 2.0.8-0
 * ros-hydro-kalman-filter: 0.2.3-0 -> 0.2.4-0
 * ros-hydro-katana: 1.0.2-0 -> 1.0.3-0
 * ros-hydro-katana-arm-gazebo: 1.0.2-0 -> 1.0.3-0
 * ros-hydro-katana-description: 1.0.2-0 -> 1.0.3-0
 * ros-hydro-katana-driver: 1.0.2-0 -> 1.0.3-0
 * ros-hydro-katana-gazebo-plugins: 1.0.2-0 -> 1.0.3-0
 * ros-hydro-katana-moveit-ikfast-plugin: 1.0.2-0 -> 1.0.3-0
 * ros-hydro-katana-msgs: 1.0.2-0 -> 1.0.3-0
 * ros-hydro-katana-teleop: 1.0.2-0 -> 1.0.3-0
 * ros-hydro-katana-tutorials: 1.0.2-0 -> 1.0.3-0
 * ros-hydro-kni: 1.0.2-0 -> 1.0.3-0
 * ros-hydro-laser-filters-jsk-patch: 1.0.71-0 -> 2.0.8-0
 * ros-hydro-laser-tilt-controller-filter: 0.1.23-0 -> 0.1.26-0
 * ros-hydro-librms: 0.0.2-0 -> 0.0.3-0
 * ros-hydro-libsiftfast: 1.0.71-0 -> 2.0.8-0
 * ros-hydro-maggie-serial-comm-drivers: 0.0.1-0 -> 0.0.4-0
 * ros-hydro-manifest-cleaner: 0.2.3-0 -> 0.2.4-0
 * ros-hydro-mavlink: 2015.6.12-0 -> 2015.9.9-0
 * ros-hydro-mini-maxwell: 1.0.71-0 -> 2.0.8-0
 * ros-hydro-multi-map-server: 1.0.71-0 -> 2.0.3-0
 * ros-hydro-multisense: 3.4.3-0 -> 3.4.4-0
 * ros-hydro-multisense-bringup: 3.4.3-0 -> 3.4.4-0
 * ros-hydro-multisense-cal-check: 3.4.3-0 -> 3.4.4-0
 * ros-hydro-multisense-description: 3.4.3-0 -> 3.4.4-0
 * ros-hydro-multisense-lib: 3.4.3-0 -> 3.4.4-0
 * ros-hydro-multisense-ros: 3.4.3-0 -> 3.4.4-0
 * ros-hydro-nextage-description: 0.6.2-0 -> 0.6.3-0
 * ros-hydro-nextage-moveit-config: 0.6.2-0 -> 0.6.3-0
 * ros-hydro-nextage-ros-bridge: 0.6.2-0 -> 0.6.3-0
 * ros-hydro-nlopt: 1.0.71-0 -> 2.0.8-0
 * ros-hydro-object-recognition-ros-visualization: 0.3.6-1 -> 0.3.7-0
 * ros-hydro-openrtm-ros-bridge: 1.2.12-0 -> 1.2.14-0
 * ros-hydro-openrtm-tools: 1.2.12-0 -> 1.2.14-0
 * ros-hydro-opt-camera: 1.0.71-0 -> 2.0.8-0
 * ros-hydro-pddl-msgs: 0.1.3-0 -> 0.1.4-1
 * ros-hydro-pddl-planner: 0.1.3-0 -> 0.1.4-1
 * ros-hydro-pddl-planner-viewer: 0.1.3-0 -> 0.1.4-1
 * ros-hydro-peppereus: 0.0.6-0 -> 0.0.11-0
 * ros-hydro-posedetection-msgs: 1.0.71-0 -> 2.0.0-1
 * ros-hydro-pr2-base-trajectory-action: 0.0.6-0 -> 0.0.11-0
 * ros-hydro-pr2-ethercat-drivers: 1.8.11-0 -> 1.8.15-0
 * ros-hydro-pr2-move-base: 0.1.23-0 -> 0.1.26-0
 * ros-hydro-pr2-navigation: 0.1.23-0 -> 0.1.26-0
 * ros-hydro-pr2-navigation-config: 0.1.23-0 -> 0.1.26-0
 * ros-hydro-pr2-navigation-global: 0.1.23-0 -> 0.1.26-0
 * ros-hydro-pr2-navigation-local: 0.1.23-0 -> 0.1.26-0
 * ros-hydro-pr2-navigation-perception: 0.1.23-0 -> 0.1.26-0
 * ros-hydro-pr2-navigation-self-filter: 0.1.23-0 -> 0.1.26-0
 * ros-hydro-pr2-navigation-slam: 0.1.23-0 -> 0.1.26-0
 * ros-hydro-pr2-navigation-teleop: 0.1.23-0 -> 0.1.26-0
 * ros-hydro-pr2eus: 0.1.10-0 -> 0.1.11-0
 * ros-hydro-pr2eus-moveit: 0.1.10-0 -> 0.1.11-0
 * ros-hydro-resized-image-transport: 0.2.12-0 -> 0.3.6-0
 * ros-hydro-rosapi: 0.7.8-0 -> 0.7.13-0
 * ros-hydro-rosauth: 0.1.6-0 -> 0.1.7-0
 * ros-hydro-rosbaglive: 0.2.3-0 -> 0.2.4-0
 * ros-hydro-rosbridge-library: 0.7.8-0 -> 0.7.13-0
 * ros-hydro-rosbridge-server: 0.7.8-0 -> 0.7.13-0
 * ros-hydro-rosbridge-suite: 0.7.8-0 -> 0.7.13-0
 * ros-hydro-roseus: 1.3.5-0 -> 1.3.9-0
 * ros-hydro-roseus-smach: 1.3.5-0 -> 1.3.9-0
 * ros-hydro-roseus-tutorials: 1.3.5-0 -> 1.3.9-0
 * ros-hydro-rosjava-bootstrap: 0.1.23-0 -> 0.1.24-0
 * ros-hydro-rosnode-rtc: 1.2.12-0 -> 1.2.14-0
 * ros-hydro-rospatlite: 1.0.71-0 -> 2.0.8-0
 * ros-hydro-rosping: 1.0.71-0 -> 2.0.8-0
 * ros-hydro-rostwitter: 1.0.71-0 -> 2.0.8-0
 * ros-hydro-roswiki-node: 0.2.3-0 -> 0.2.4-0
 * ros-hydro-rqt-action: 0.3.11-0 -> 0.3.12-0
 * ros-hydro-rqt-bag: 0.3.11-0 -> 0.3.12-0
 * ros-hydro-rqt-bag-plugins: 0.3.11-0 -> 0.3.12-0
 * ros-hydro-rqt-common-plugins: 0.3.11-0 -> 0.3.12-0
 * ros-hydro-rqt-console: 0.3.11-0 -> 0.3.12-0
 * ros-hydro-rqt-dep: 0.3.11-0 -> 0.3.12-0
 * ros-hydro-rqt-graph: 0.3.11-0 -> 0.3.12-0
 * ros-hydro-rqt-image-view: 0.3.11-0 -> 0.3.12-0
 * ros-hydro-rqt-launch: 0.3.11-0 -> 0.3.12-0
 * ros-hydro-rqt-logger-level: 0.3.11-0 -> 0.3.12-0
 * ros-hydro-rqt-msg: 0.3.11-0 -> 0.3.12-0
 * ros-hydro-rqt-plot: 0.3.11-0 -> 0.3.12-0
 * ros-hydro-rqt-publisher: 0.3.11-0 -> 0.3.12-0
 * ros-hydro-rqt-py-common: 0.3.11-0 -> 0.3.12-0
 * ros-hydro-rqt-py-console: 0.3.11-0 -> 0.3.12-0
 * ros-hydro-rqt-reconfigure: 0.3.11-0 -> 0.3.12-0
 * ros-hydro-rqt-service-caller: 0.3.11-0 -> 0.3.12-0
 * ros-hydro-rqt-shell: 0.3.11-0 -> 0.3.12-0
 * ros-hydro-rqt-srv: 0.3.11-0 -> 0.3.12-0
 * ros-hydro-rqt-top: 0.3.11-0 -> 0.3.12-0
 * ros-hydro-rqt-topic: 0.3.11-0 -> 0.3.12-0
 * ros-hydro-rqt-web: 0.3.11-0 -> 0.3.12-0
 * ros-hydro-rtmbuild: 1.2.12-0 -> 1.2.14-0
 * ros-hydro-rtmros-common: 1.2.12-0 -> 1.2.14-0
 * ros-hydro-rtmros-hironx: 1.0.31-0 -> 1.0.37-0
 * ros-hydro-rtmros-nextage: 0.6.2-0 -> 0.6.3-0
 * ros-hydro-rtt-actionlib: 2.7.0-3 -> 2.7.2-0
 * ros-hydro-rtt-actionlib-msgs: 2.7.0-3 -> 2.7.2-0
 * ros-hydro-rtt-common-msgs: 2.7.0-3 -> 2.7.2-0
 * ros-hydro-rtt-diagnostic-msgs: 2.7.0-3 -> 2.7.2-0
 * ros-hydro-rtt-dynamic-reconfigure: 2.7.0-3 -> 2.7.2-0
 * ros-hydro-rtt-geometry-msgs: 2.7.0-3 -> 2.7.2-0
 * ros-hydro-rtt-kdl-conversions: 2.7.0-3 -> 2.7.2-0
 * ros-hydro-rtt-nav-msgs: 2.7.0-3 -> 2.7.2-0
 * ros-hydro-rtt-ros: 2.7.0-3 -> 2.7.2-0
 * ros-hydro-rtt-ros-comm: 2.7.0-3 -> 2.7.2-0
 * ros-hydro-rtt-ros-integration: 2.7.0-3 -> 2.7.2-0
 * ros-hydro-rtt-ros-msgs: 2.7.0-3 -> 2.7.2-0
 * ros-hydro-rtt-rosclock: 2.7.0-3 -> 2.7.2-0
 * ros-hydro-rtt-roscomm: 2.7.0-3 -> 2.7.2-0
 * ros-hydro-rtt-rosdeployment: 2.7.0-3 -> 2.7.2-0
 * ros-hydro-rtt-rosgraph-msgs: 2.7.0-3 -> 2.7.2-0
 * ros-hydro-rtt-rosnode: 2.7.0-3 -> 2.7.2-0
 * ros-hydro-rtt-rospack: 2.7.0-3 -> 2.7.2-0
 * ros-hydro-rtt-rosparam: 2.7.0-3 -> 2.7.2-0
 * ros-hydro-rtt-sensor-msgs: 2.7.0-3 -> 2.7.2-0
 * ros-hydro-rtt-shape-msgs: 2.7.0-3 -> 2.7.2-0
 * ros-hydro-rtt-std-msgs: 2.7.0-3 -> 2.7.2-0
 * ros-hydro-rtt-std-srvs: 2.7.0-3 -> 2.7.2-0
 * ros-hydro-rtt-stereo-msgs: 2.7.0-3 -> 2.7.2-0
 * ros-hydro-rtt-tf: 2.7.0-3 -> 2.7.2-0
 * ros-hydro-rtt-trajectory-msgs: 2.7.0-3 -> 2.7.2-0
 * ros-hydro-rtt-visualization-msgs: 2.7.0-3 -> 2.7.2-0
 * ros-hydro-rviz: 1.10.19-0 -> 1.10.20-0
 * ros-hydro-rviz-imu-plugin: 1.0.4-0 -> 1.0.5-0
 * ros-hydro-self-test: 1.8.7-0 -> 1.8.8-0
 * ros-hydro-semantic-point-annotator: 0.1.23-0 -> 0.1.26-0
 * ros-hydro-sklearn: 1.0.71-0 -> 2.0.8-0
 * ros-hydro-speech-recognition-msgs: 1.0.71-0 -> 2.0.0-1
 * ros-hydro-staro-moveit-config: 0.1.8-0 -> 0.1.9-0
 * ros-hydro-task-compiler: 0.1.3-0 -> 0.1.4-1
 * ros-hydro-test-diagnostic-aggregator: 1.8.7-0 -> 1.8.8-0
 * ros-hydro-ueye-cam: 1.0.9-0 -> 1.0.11-0
 * ros-hydro-usb-cam: 0.3.3-0 -> 0.3.4-0
 * ros-hydro-virtual-force-publisher: 1.0.71-0 -> 2.0.3-0
 * ros-hydro-voice-text: 1.0.71-0 -> 2.0.8-0
 * ros-hydro-wu-ros-tools: 0.2.3-0 -> 0.2.4-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
 * Anqi Xu
 * Austin Hendrix
 * Brice Rebsamen
 * Carnegie Robotics
 * Damon Kohler
 * Dan Lazewatsky
 * Daniel Stonier
 * Dash
 * David Gossow
 * David V. Lu!!
 * Devon Ash
 * Dorian Scholz
 * Florian Mirus
 * Henning Deeken
 * Isaac Isao Saito
 * Isaac Saito
 * Jim Rothrock
 * KazutoMurase
 * Kei Okada
 * Maintained by Carnegie Robotics LLC
 * Martin G√ľnther
 * Matthias Gruhler
 * MoveIt Setup Assistant
 * Noda Shintaro
 * Orocos Developers
 * Raul Perula-Martinez
 * Russell Toris
 * Ryohei Ueda
 * Scott K Logan
 * Shohei Fujii
 * Shunichi Nozawa
 * Social Robots
 * TORK
 * Takuya Nakaoka
 * Vincent Rabaud
 * Vladimir Ermakov
 * Yohei Kakiuchi
 * YoheiKakiuchi
 * Youhei Kakiuchi
 * Yuki Furuta
 * Yusuke Furuta
 * Yuto Inagaki
 * furuta
 * inagaki
 * k-okada
 * saito

From Mani Monajjemi via ros-users@

I would like to announce the release of "bebop_autonomy" package: ROS driver for Parrot Bebop Drone [1].


This driver is based on Parrot's official ARDroneSDK3 [2]. As of this release, it provides interfaces for piloting the drone, subscribing to its camera and on-board sensory data as well as tweaking its configuration.

Happy flying!

Mani Monajjemi
AutonomyLab, Simon Fraser University

PS. Feel free to join the discussion on feature development of this driver (and ardrone_autonomy) here: https://trello.com/b/C6rNl8Ux 

Erle-Spider, the Ubuntu drone with legs

| No Comments | No TrackBacks
From Victor MV via ros-users@

I'm delighted to introduce Erle-Spider as the first legged drone powered by ROS and running Snappy Ubuntu Core. This smart robot with a 900 MHz quad-core ARM Cortex-A7 processor runs Linux natively and embeds several sensors onboard.

erle-spider.jpg

The hexapod has been designed to meet the increasing demand of robot kits to learn, research and develop while being subject to low levels of regulation. The drone is also capable of accessing hard-to-reach places such as pipes and disaster areas, bringing cameras on board and supporting Wi-Fi, Bluetooth, as well as 3G and 4G networks to provide connectivity where needed.

Besides support for ROS, our team has been working with Canonical over last months to provide access to a cloud-based app store that would allow anyone to enhance the intelligence of this robot directly by installing new apps.

Erle-Spider has been launched together with Indiegogo at https://www.indiegogo.com/projects/erle-spider-the-ubuntu-drone-with-legs/and will be delivered this Christmas for only 399 $.

First MoveIt! Community Meeting Slides and Recording

| No Comments | No TrackBacks
From Sachin Chitta via ros-users@

Thank you again for coming to the meeting and thanks to the presenters for making this a fantastic meeting. There were more than 240 people registered and more than 150 who attended from all over the world. I apologize to those running Ubuntu who had issues joining us (using Chrome was the suggested solution for the future).

The recording of the meeting is available online: https://youtu.be/D5rs9uLrveg


The slides from the meeting are posted here: http://www.sachinchitta.org/blog/report-on-the-first-moveit-community-meeting

MoveIt! now has a twitter account for updates: @moveitrobot

Feel free to let us know (on the moveit-users mailing list) if you have any feedback. 
From Sachin Chitta via ros-users@

We are a well-funded stealth robotics startup in Silicon Valley developing advanced robotic applications. The members of our team have been creators/prime architects/developers of some of the most popular open-source software for manipulation and robotics including MoveIt!, Rviz, Arm Navigation and ROS-Control, used by hundreds of researchers, universities and companies around the world.

We are looking for full-time and intern positions in motion planning, perception and manipulation starting immediately. 


** Motion Planning and Manipulation Engineer (Full-time or Intern) **
Experience: Bachelors, Masters or PhD in Robotics, Computer Science or Equivalent Degree
Must haves:
- Experience writing motion planners/controllers and applying them to real world manipulation problems
- Experience with MoveIt!/OMPL/SBPL/ROS-Control or any other motion planning/manipulation software
- Strong C++ skills with 3 or more years of experience
- Strong system integration skills
Nice to have:
- ROS experience
- Python experience
- Experience working with industrial robots


** Perception Engineer (Full-time or Intern) **
Experience: Bachelors, Masters or PhD in Robotics, Computer Science or Equivalent Degree
Must haves:
- Experience writing fast, advanced 2D/3D computer vision software
- Experience developing state of the art algorithms with PCL and/or OpenCV
- Strong C++ skills with 3 or more years of experience
Nice to have:
- Experience integrating motion planning, perception and control for manipulation
- ROS experience
- Python experience
- GPU based development


** Robotics Software Engineer/Architect(Full-time or Intern) **
We are looking for people who have been key developers/architects of a robotics or other software package.
Experience: Bachelors, Masters or PhD in Robotics, Computer Science or Equivalent Degree
Must haves:
- Experience architecting complex robotics or other software infrastructure (3+ years)
- Extremely strong C++ skills
- Extremely strong Linux skills
- Experience with build and distribution systems
Nice to have:
- ROS Experience
- MoveIt! Experience


You will get to work with one of the best teams in manipulation in the world developing revolutionary robotic applications. All candidates must be willing to move to the SF Bay Area.

If you are interested in any of these positions, please email a resume including a link to robotics or other projects you have worked on and a link to publicly available code that you have written to robot.moveit@gmail.com. We do not work with recruiters. 

TurtleBot updates for Indigo

| No Comments | No TrackBacks

Greetings!


We would like to announce that TurtleBot got major(and minor) updates in both software and hardware. These updates are final (apart from bugfixes) and won't change api for indigo.


  • Turtlebot2 has equipped with better navigation skills, so it can now navigates a lot better with tuned parameters and by Asus Xtion Pro as default sensor.

  • It supports integrated interaction tools, Remocon & Interactions as new ways to interact with robots.

  • Turtlebot2 now can be easily installed and repaired by Turtlebot2 ISO to create Turtlebot2 netbook easily. Check Turtlebot Installation Tutorial.

  • In addition, there are miscellaneous updates in configuration, simulation, and multi robot implementation. Please see Migration Guide for the details.



Cheers,

TurtleBot Team

From Rachel Pelayo via ros-users@

My name is Rachel Pelayo, and I am a Recruiter at Southwest Research Institute. I would like to inform the Ros Subscribers of an amazing opportunity at Southwest Research Institute! Here is a link to learn more about the Division this opportunity is in: http://www.swri.org/4org/d10/d10home.htm

Our Careers webpage is at this link: http://www.swri.org/hr/

 

If anyone has any questions regarding the job application process, please reach out to me, and I would be happy to help!

 

You can find the position at our careers webpage, but please see below for information on the position!

 

Job Summary: Develop hardware/software solutions (including sensor fusion and control systems) for autonomous/automated vehicle, mobile robotic, and intelligent vehicle systems; perform in all phases of the development lifecycle, including requirements definition, hardware/software/systems design, implementation, testing, and integration; initiate advanced research and development programs, interact with clients, and make technical presentations

 

Education/Experience: Requires a BS degree in Electrical, Mechanical, Computer Engineering or Computer Science with at least a 3.5 GPA. MS or PHD is preferred. MS and PhD candidates must have done their thesis/dissertation in a research area pertinent to autonomous/automated vehicles or robotics. Must have a minimum of one year of related education project work or internship/co-op experience in autonomous vehicle and/or mobile robotic systems including, but not limited to, image/sensor processing for those applications. Must have experience with Linux and various PC operating systems. Must have excellent interpersonal skills and the ability to work well individually or as a member of a project team. Must have excellent written and verbal communication skills. Must have C++ development experience. ROS experience is preferred. Must be a US citizen and be able to obtain a DoD Security Clearance. Occasional travel is required. A valid/clear driver's license is required

Special Considerations: Applicant selected will be subject to a government security investigation and must meet eligibility requirements for access to classified information. Applicant must be a U.S. citizen

An Equal Employment Opportunity/Affirmative Action Employer
Race/Color/Religion/Sex/Sexual Orientation
Gender Identity/National Origin/Disabled/Veteran
Committed to Diversity in the Workplace

 

Location: San Antonio, Texas

Southwest Research Institute (SwRI) offers great opportunities for those who are seeking exciting, fulfilling careers. Be part of SwRI's more than 60 year tradition of solving challenging science and technology problems.
Benefits to Working at SwRI
Competitive salaries
Medical, dental, and vision care plans
Ten paid holidays
Retirement plan and benefits
Fitness facilities and trainers
Aerobics classes
Credit union
Dining services
Discount tickets and merchandise
Travel agency
Family picnics and other social activities 

New sig for Shadow Robot

| No Comments | No TrackBacks
From Ugo Cupcic via ros-users@

I just created a SIG to synchronize discussions around our robots and software: http://wiki.ros.org/sig/shadow_robot

The global aim is to facilitate discussion with our user base. For example, we're in the process of refactoring our repositories right now to make for an easier release process and more modular approach. During that process we'd love to have more feedback from our end users but it is quite hard for us to reach them. We also think that it'd be a good place to discuss different uses of our hardware / software, sharing exciting demos or tutorials, discussing new features, etc.

If you are using our software (the Shadow hand simulation or real Hardware, the Cyberglove package, etc...), I hope you'll be joining that list!

Real-time stereo vision integration into ROS

| No Comments | No TrackBacks
From Konstantin Schauwecker via ros-users@

I'm glad to announce the ROS integration of the SP1 stereo vision system by Nerian Vision Technologies. The SP1 provides real-time 3D data through the use of a stereo camera and a powerful FPGA. In ROS, this data can be published as a point cloud or as a disparity map.

You can find the wiki page for the ROS node here:
http://wiki.ros.org/nerian_sp1

Further information about the SP1 system can be found on the product page:
http://nerian.com/products/sp1-stereo-vision/

The ROS node and the API code are published under the MIT license, and can thus be freely modified and redistributed.

Navigation engineer at Locus Robotics in Boston, MA

| No Comments | No TrackBacks

From Brad Powers

Locus Robotics (locusrobotics.com) is looking for a talented software engineer/roboticist to help bring the next generation of warehousing robots to market. Locus is a Boston area stealth-mode startup working with partners in the warehousing market to build a product that is performant and flexible to meet the dynamic needs of our customers.

Our ideal candidate has significant experience with navigation and planning in a multi-robot context, and is familiar with ROS and the ROS navigation stack. Additionally, strong candidates will be comfortable with significant autonomy and self-organized. We're looking for candidates interested in full time employment or consulting work, local or remote. If interested, please send a resume (and if applicable, Github link, portfolio, etc.) to careers@locusrobotics.com. We look forward to hearing from you.

ROS 2 alpha1 release: Anchor

| No Comments | No TrackBacks
We're happy to announce the release of ROS 2 alpha1, code-named Anchor!

Installation instructions and tutorials designed to exercise new
features in ROS 2 are in the wiki:
  https://github.com/ros2/ros2/wiki

To get an idea of what's in (and what's not in) this release, be sure
to read the overview page:
  https://github.com/ros2/ros2/wiki/Alpha1-Overview

From that page, an important caveat:
~~~
As the "alpha" qualifier suggests, this release of ROS 2 is far from
complete. You should not expect to switch from ROS 1 to ROS 2, nor
should you expect to build a new robot control system with ROS 2.
Rather, you should expect to try out some demos, explore the code, and
perhaps write your own demos.
~~~

We invite you to try out the new software, give feedback, report bugs,
and suggest features:
  https://github.com/ros2/ros2/wiki/Contact

- your ROS 2 team

Find this blog and more at planet.ros.org.


Please submit content to be reviewed by emailing ros-news@googlegroups.com.

Monthly Archives

About this Archive

This page is an archive of entries from September 2015 listed from newest to oldest.

August 2015 is the previous archive.

October 2015 is the next archive.

Find recent content on the main index or look in the archives to find all content.