ROSIN Consortium results

Tools | More info about QA | Papers

Tools

  • Date
    March 3, 2019
    Website
    View website
    Brief Description abb_libegm is a C++ communication library for facilitating, and easing, the use of the Externally Guided Motion (EGM) interface of ABB robot controllers. In a nutshell, the library helps with setting up communication channels, parsing EGM messages, as well as providing user APIs. The library does not depend on ROS, and as such it can also be used on non-ROS systems. However, the library has been wrapped inside a ROS package for making distribution and sharing a breeze. Please visit the library’s GitHub repository for a more in-depth description of supported features, requirements and limitations. The core part of the library was developed throughout the European project SYMBIO-TIC, while the open-source process and creation of a ROS package has been performed during the ROSIN project.
  • Date
    March 3, 2019
    Website
    View website
    Brief Description abb_librws is a C++ communication library for facilitating, and easing, the use of the Robot Web Services (RWS) interface of ABB robot controllers. In a nutshell, the library helps with setting up communication channels, parsing RWS messages, as well as providing user APIs. The library does not depend on ROS, and as such it can also be used on non-ROS systems. However, the library has been wrapped inside a ROS package for making distribution and sharing a breeze. Please visit the library’s GitHub repository for a more in-depth description of supported features, requirements and limitations. The core part of the library was developed throughout the European project SYMBIO-TIC, while the open-source process and creation of a ROS package has been performed during the ROSIN project.
  • Date
    February 26, 2019
    Website
    View website
    A simple bash script to generate .rosinstall files ‘from the past’. Overview This bash script is a wrapper around rosinstall_generator that accepts one additional argument: a date in the past. Using this date in the past, the script will try to generate a .rosinstall file using rosinstall_generator and the state of ros/rosdistro at the date specified. The .rosinstall file can then be used to build a set of ROS packages that will approximate the “state of ROS” as it was at the date specified. This is of course only an approximation as other parts of the technology stack (such as the OS) are not reverted. Usage and more information See the github repository for more information and precise usage instructions: rosin-project/rosinstall_generator_time_machine
  • Date
    February 20, 2019
    Website
    View website
      >> 3D animation Application implements godel (Scan and Plan): https://github.com/ros-industrial-consortium/godel ensenso_driver: https://github.com/ensenso/ros_driver ( funded) pilz_robots: https://github.com/PilzDE/pilz_robots pilz_industrial_motion: https://github.com/PilzDE/pilz_industrial_motion ( funded)
  • Date
    September 6, 2018
    Summary What if you could avoid writing nodes from scratch every time you create a package? What if you could just create a new node by defining its interface and then have all the ROS communication primitives automatically created for you, so that you can focus on the core logic of your component? What if you could still update your interface once you have created your node? What if you could even create your own package and node template, so that you could create nodes that exactly fit your needs? Well that´s what the ROS package generator proposes! https://github.com/tecnalia-advancedmanufacturing-robotics/ros_pkg_gen   Extended description The objective of this package is double. On one side, it enables a ROS user, hereafter called Developer, to create a package and its nodes automatically from the definition of the nodes interfaces. On the other side, it enables advanced users or Designers to define package and node templates, based on their expertise, requirements and best practices, so that Developers can reuse these templates to generate new packages and nodes following that model automatically. The available templates are designed to make a clear separation in between (i) the node interface implementation and management (based on ROS communication primitives, […]