No version for distro crystal. Known supported distros are highlighted in the buttons above.
No version for distro bouncy. Known supported distros are highlighted in the buttons above.
No version for distro melodic. Known supported distros are highlighted in the buttons above.

Package Summary

Tags No category tags.
Version 2.9.1
License BSD
Build type CATKIN
Use RECOMMENDED

Repository Summary

Checkout URI https://github.com/orocos/rtt_ros_integration.git
VCS Type git
VCS Version toolchain-2.9
Last Updated 2018-08-30
Dev Status MAINTAINED
Released RELEASED

Package Description

This package provides an RTT plugin to add a ROS node to the RTT process, as well as several wrapper scripts to enable roslaunching of orocos programs.

Additional Links

Maintainers

  • Orocos Developers

Authors

  • Ruben Smits

RTT ROS

This package contains tools for building and running Orocos components integrated into a ROS architecture.

RTT Services

ROS Package Import Chaining Service

The "ros" RTT service can be used to import all of the RTT plugins built in a given ROS package along with plugins on which they depend. These dependencies are specified in package.xml files in the <export> section.

For example, all RTT plugins in the ROS package "my_package_name" along with its dependencies can be imported by running the following Orocos .ops script (or calling the appropriate operation on the "ros" global service):

import("rtt_ros")
ros.import("my_pkg_name")

When doing the above, first the rtt_ros package is imported using the normal mechanism. This then loads the ros service, which provides a ROS import function, ros.import(), which will parse ROS package metadata and import the Orocos plugins from the named package and all packages listed in <rtt_ros><plugin_depend>PKG_NAME</plugin_depend></rtt_ros> tags in the <export> section of the package.xml files.

Catkin introduces several new dependency types for buildtime, development, and other purposes. In order to keep the RTT plugin depdencencies clear, and avoid trying to load orocos components from every package dependency, we use the extensible ROS metadata <export> tag.

For example, if loading the plugins from package pkg_one should necessitate first loading plugins from packages rtt_roscomm and pkg_two, then pkg_one/package.xml should have the following:

<package>
  <name>pkg_one</name>
  <!-- ... -->
  <export>
    <rtt_ros>
      <plugin_depend>rtt_roscomm</plugin_depend>
      <plugin_depend>pkg_two</plugin_depend>
    </rtt_ros>
  </export>
</package>

Launch Files

  • deployer.launch Launch the orocos deployer
    • LOG_LEVEL (default "info") The Orocos log level
    • DEPLOYER_ARGS (default "") Additional arguments passed to the deployer
    • OROCOS_TARGET (default $OROCOS_TARGET)
    • RTT_COMPONENT_PATH (default $LD_LIBRARY_PATH)
    • DEBUG (default false) Launch the deployer in GDB.

Launchfile Examples

For example, the deployer can be launched by including the launchfile in another launchfile like the following:

<launch>
  <include file="$(find rtt_ros)/launch/deployer.launch">
    <arg name="DEPLOYER_ARGS" value="-s $(find rtt_ros_integration_example)/example.ops"/>
    <arg name="LOG_LEVEL" value="debug"/>
    <arg name="DEBUG" value="false"/>
  </include>
</launch>

Wrapper Scripts

  • deployer
  • orocreate-pkg
  • orogen
  • orogen-unregister
  • rttlua
  • rttlua-tlsf
  • rttscript
  • typegen
CHANGELOG

Changelog for package rtt_ros

2.9.1 (2017-11-16)

2.9.0 (2017-05-02)

  • rtt_std_msgs: added a transport plugin for ROS primitive types
  • Contributors: Johannes Meyer

2.8.6 (2017-11-15)

2.8.5 (2017-03-28)

  • Merge pull request #85 from meyerj/ros-primitives-transport-indigo-devel Added a ROS transport plugin for primitive types (indigo-devel)
  • Contributors: Johannes Meyer

2.8.4 (2016-11-26)

  • rtt_ros: fixed comment in rtt_ros/scripts/deployer-corba
  • Merge pull request #40 from ahoarau/corba-deployer add Corba deployer scripts
  • rtt_ros: fixed rttlua.launch for the SCREEN:=false case (fix #72)
  • Contributors: Johannes Meyer, Antoine Hoarau

2.8.3 (2016-07-20)

2.8.2 (2015-06-12)

2.8.1 (2015-03-16)

2.7.2 (2015-07-21)

Wiki Tutorials

See ROS Wiki Tutorials for more details.

Source Tutorials

Not currently indexed.

Launch files

  • launch/rttlua.launch
      • NAME [default: $(anon rttlua)]
      • RTTLUA_ARGS [default: ]
      • OROCOS_TARGET [default: $(optenv OROCOS_TARGET)]
      • RTT_COMPONENT_PATH [default: $(env RTT_COMPONENT_PATH)]
      • DEBUG [default: false]
      • SCREEN [default: false]
      • INTERACTIVE [default: true]
  • launch/deployer.launch
      • NAME [default: $(anon deployer)]
      • LOG_LEVEL [default: info]
      • DEPLOYER_ARGS [default: ]
      • OROCOS_TARGET [default: $(optenv OROCOS_TARGET)]
      • RTT_COMPONENT_PATH [default: $(env RTT_COMPONENT_PATH)]
      • CORBA [default: false]
      • DEBUG [default: false]

Messages

No message files found.

Services

No service files found

Plugins

No plugins found.

Recent questions tagged rtt_ros at answers.ros.org

Package Summary

Tags No category tags.
Version 2.9.1
License BSD
Build type CATKIN
Use RECOMMENDED

Repository Summary

Checkout URI https://github.com/orocos/rtt_ros_integration.git
VCS Type git
VCS Version toolchain-2.9
Last Updated 2018-08-30
Dev Status MAINTAINED
Released RELEASED

Package Description

This package provides an RTT plugin to add a ROS node to the RTT process, as well as several wrapper scripts to enable roslaunching of orocos programs.

Additional Links

Maintainers

  • Orocos Developers

Authors

  • Ruben Smits

RTT ROS

This package contains tools for building and running Orocos components integrated into a ROS architecture.

RTT Services

ROS Package Import Chaining Service

The "ros" RTT service can be used to import all of the RTT plugins built in a given ROS package along with plugins on which they depend. These dependencies are specified in package.xml files in the <export> section.

For example, all RTT plugins in the ROS package "my_package_name" along with its dependencies can be imported by running the following Orocos .ops script (or calling the appropriate operation on the "ros" global service):

import("rtt_ros")
ros.import("my_pkg_name")

When doing the above, first the rtt_ros package is imported using the normal mechanism. This then loads the ros service, which provides a ROS import function, ros.import(), which will parse ROS package metadata and import the Orocos plugins from the named package and all packages listed in <rtt_ros><plugin_depend>PKG_NAME</plugin_depend></rtt_ros> tags in the <export> section of the package.xml files.

Catkin introduces several new dependency types for buildtime, development, and other purposes. In order to keep the RTT plugin depdencencies clear, and avoid trying to load orocos components from every package dependency, we use the extensible ROS metadata <export> tag.

For example, if loading the plugins from package pkg_one should necessitate first loading plugins from packages rtt_roscomm and pkg_two, then pkg_one/package.xml should have the following:

<package>
  <name>pkg_one</name>
  <!-- ... -->
  <export>
    <rtt_ros>
      <plugin_depend>rtt_roscomm</plugin_depend>
      <plugin_depend>pkg_two</plugin_depend>
    </rtt_ros>
  </export>
</package>

Launch Files

  • deployer.launch Launch the orocos deployer
    • LOG_LEVEL (default "info") The Orocos log level
    • DEPLOYER_ARGS (default "") Additional arguments passed to the deployer
    • OROCOS_TARGET (default $OROCOS_TARGET)
    • RTT_COMPONENT_PATH (default $LD_LIBRARY_PATH)
    • DEBUG (default false) Launch the deployer in GDB.

Launchfile Examples

For example, the deployer can be launched by including the launchfile in another launchfile like the following:

<launch>
  <include file="$(find rtt_ros)/launch/deployer.launch">
    <arg name="DEPLOYER_ARGS" value="-s $(find rtt_ros_integration_example)/example.ops"/>
    <arg name="LOG_LEVEL" value="debug"/>
    <arg name="DEBUG" value="false"/>
  </include>
</launch>

Wrapper Scripts

  • deployer
  • orocreate-pkg
  • orogen
  • orogen-unregister
  • rttlua
  • rttlua-tlsf
  • rttscript
  • typegen
CHANGELOG

Changelog for package rtt_ros

2.9.1 (2017-11-16)

2.9.0 (2017-05-02)

  • rtt_std_msgs: added a transport plugin for ROS primitive types
  • Contributors: Johannes Meyer

2.8.6 (2017-11-15)

2.8.5 (2017-03-28)

  • Merge pull request #85 from meyerj/ros-primitives-transport-indigo-devel Added a ROS transport plugin for primitive types (indigo-devel)
  • Contributors: Johannes Meyer

2.8.4 (2016-11-26)

  • rtt_ros: fixed comment in rtt_ros/scripts/deployer-corba
  • Merge pull request #40 from ahoarau/corba-deployer add Corba deployer scripts
  • rtt_ros: fixed rttlua.launch for the SCREEN:=false case (fix #72)
  • Contributors: Johannes Meyer, Antoine Hoarau

2.8.3 (2016-07-20)

2.8.2 (2015-06-12)

2.8.1 (2015-03-16)

2.7.2 (2015-07-21)

Wiki Tutorials

See ROS Wiki Tutorials for more details.

Source Tutorials

Not currently indexed.

Launch files

  • launch/rttlua.launch
      • NAME [default: $(anon rttlua)]
      • RTTLUA_ARGS [default: ]
      • OROCOS_TARGET [default: $(optenv OROCOS_TARGET)]
      • RTT_COMPONENT_PATH [default: $(env RTT_COMPONENT_PATH)]
      • DEBUG [default: false]
      • SCREEN [default: false]
      • INTERACTIVE [default: true]
  • launch/deployer.launch
      • NAME [default: $(anon deployer)]
      • LOG_LEVEL [default: info]
      • DEPLOYER_ARGS [default: ]
      • OROCOS_TARGET [default: $(optenv OROCOS_TARGET)]
      • RTT_COMPONENT_PATH [default: $(env RTT_COMPONENT_PATH)]
      • CORBA [default: false]
      • DEBUG [default: false]

Messages

No message files found.

Services

No service files found

Plugins

No plugins found.

Recent questions tagged rtt_ros at answers.ros.org

Package Summary

Tags No category tags.
Version 2.8.6
License BSD
Build type CATKIN
Use RECOMMENDED

Repository Summary

Checkout URI https://github.com/orocos/rtt_ros_integration.git
VCS Type git
VCS Version indigo-devel
Last Updated 2018-07-23
Dev Status MAINTAINED
Released RELEASED

Package Description

This package provides an RTT plugin to add a ROS node to the RTT process, as well as several wrapper scripts to enable roslaunching of orocos programs.

Additional Links

Maintainers

  • Orocos Developers

Authors

  • Ruben Smits

RTT ROS

This package contains tools for building and running Orocos components integrated into a ROS architecture.

RTT Services

ROS Package Import Chaining Service

The "ros" RTT service can be used to import all of the RTT plugins built in a given ROS package along with plugins on which they depend. These dependencies are specified in package.xml files in the <export> section.

For example, all RTT plugins in the ROS package "my_package_name" along with its dependencies can be imported by running the following Orocos .ops script (or calling the appropriate operation on the "ros" global service):

import("rtt_ros")
ros.import("my_pkg_name")

When doing the above, first the rtt_ros package is imported using the normal mechanism. This then loads the ros service, which provides a ROS import function, ros.import(), which will parse ROS package metadata and import the Orocos plugins from the named package and all packages listed in <rtt_ros><plugin_depend>PKG_NAME</plugin_depend></rtt_ros> tags in the <export> section of the package.xml files.

Catkin introduces several new dependency types for buildtime, development, and other purposes. In order to keep the RTT plugin depdencencies clear, and avoid trying to load orocos components from every package dependency, we use the extensible ROS metadata <export> tag.

For example, if loading the plugins from package pkg_one should necessitate first loading plugins from packages rtt_roscomm and pkg_two, then pkg_one/package.xml should have the following:

<package>
  <name>pkg_one</name>
  <!-- ... -->
  <export>
    <rtt_ros>
      <plugin_depend>rtt_roscomm</plugin_depend>
      <plugin_depend>pkg_two</plugin_depend>
    </rtt_ros>
  </export>
</package>

Launch Files

  • deployer.launch Launch the orocos deployer
    • LOG_LEVEL (default "info") The Orocos log level
    • DEPLOYER_ARGS (default "") Additional arguments passed to the deployer
    • OROCOS_TARGET (default $OROCOS_TARGET)
    • RTT_COMPONENT_PATH (default $LD_LIBRARY_PATH)
    • DEBUG (default false) Launch the deployer in GDB.

Launchfile Examples

For example, the deployer can be launched by including the launchfile in another launchfile like the following:

<launch>
  <include file="$(find rtt_ros)/launch/deployer.launch">
    <arg name="DEPLOYER_ARGS" value="-s $(find rtt_ros_integration_example)/example.ops"/>
    <arg name="LOG_LEVEL" value="debug"/>
    <arg name="DEBUG" value="false"/>
  </include>
</launch>

Wrapper Scripts

  • deployer
  • orocreate-pkg
  • orogen
  • orogen-unregister
  • rttlua
  • rttlua-tlsf
  • rttscript
  • typegen
CHANGELOG

Changelog for package rtt_ros

2.8.6 (2017-11-15)

2.8.5 (2017-03-28)

  • Merge pull request #85 from meyerj/ros-primitives-transport-indigo-devel Added a ROS transport plugin for primitive types (indigo-devel)
  • Contributors: Johannes Meyer

2.8.4 (2016-11-26)

  • rtt_ros: fixed comment in rtt_ros/scripts/deployer-corba
  • Merge pull request #40 from ahoarau/corba-deployer add Corba deployer scripts
  • rtt_ros: fixed rttlua.launch for the SCREEN:=false case (fix #72)
  • Contributors: Johannes Meyer, Antoine Hoarau

2.8.3 (2016-07-20)

2.8.2 (2015-06-12)

2.8.1 (2015-03-16)

2.7.2 (2015-07-21)

Wiki Tutorials

See ROS Wiki Tutorials for more details.

Source Tutorials

Not currently indexed.

Launch files

  • launch/rttlua.launch
      • NAME [default: $(anon rttlua)]
      • RTTLUA_ARGS [default: ]
      • OROCOS_TARGET [default: $(optenv OROCOS_TARGET)]
      • RTT_COMPONENT_PATH [default: $(env RTT_COMPONENT_PATH)]
      • DEBUG [default: false]
      • SCREEN [default: false]
      • INTERACTIVE [default: true]
  • launch/deployer.launch
      • NAME [default: $(anon deployer)]
      • LOG_LEVEL [default: info]
      • DEPLOYER_ARGS [default: ]
      • OROCOS_TARGET [default: $(optenv OROCOS_TARGET)]
      • RTT_COMPONENT_PATH [default: $(env RTT_COMPONENT_PATH)]
      • CORBA [default: false]
      • DEBUG [default: false]

Messages

No message files found.

Services

No service files found

Plugins

No plugins found.

Recent questions tagged rtt_ros at answers.ros.org

No version for distro ardent. Known supported distros are highlighted in the buttons above.

Package Summary

Tags No category tags.
Version 2.8.6
License BSD
Build type CATKIN
Use RECOMMENDED

Repository Summary

Checkout URI https://github.com/orocos/rtt_ros_integration.git
VCS Type git
VCS Version jade-devel
Last Updated 2018-07-23
Dev Status MAINTAINED
Released RELEASED

Package Description

This package provides an RTT plugin to add a ROS node to the RTT process, as well as several wrapper scripts to enable roslaunching of orocos programs.

Additional Links

Maintainers

  • Orocos Developers

Authors

  • Ruben Smits

RTT ROS

This package contains tools for building and running Orocos components integrated into a ROS architecture.

RTT Services

ROS Package Import Chaining Service

The "ros" RTT service can be used to import all of the RTT plugins built in a given ROS package along with plugins on which they depend. These dependencies are specified in package.xml files in the <export> section.

For example, all RTT plugins in the ROS package "my_package_name" along with its dependencies can be imported by running the following Orocos .ops script (or calling the appropriate operation on the "ros" global service):

import("rtt_ros")
ros.import("my_pkg_name")

When doing the above, first the rtt_ros package is imported using the normal mechanism. This then loads the ros service, which provides a ROS import function, ros.import(), which will parse ROS package metadata and import the Orocos plugins from the named package and all packages listed in <rtt_ros><plugin_depend>PKG_NAME</plugin_depend></rtt_ros> tags in the <export> section of the package.xml files.

Catkin introduces several new dependency types for buildtime, development, and other purposes. In order to keep the RTT plugin depdencencies clear, and avoid trying to load orocos components from every package dependency, we use the extensible ROS metadata <export> tag.

For example, if loading the plugins from package pkg_one should necessitate first loading plugins from packages rtt_roscomm and pkg_two, then pkg_one/package.xml should have the following:

<package>
  <name>pkg_one</name>
  <!-- ... -->
  <export>
    <rtt_ros>
      <plugin_depend>rtt_roscomm</plugin_depend>
      <plugin_depend>pkg_two</plugin_depend>
    </rtt_ros>
  </export>
</package>

Launch Files

  • deployer.launch Launch the orocos deployer
    • LOG_LEVEL (default "info") The Orocos log level
    • DEPLOYER_ARGS (default "") Additional arguments passed to the deployer
    • OROCOS_TARGET (default $OROCOS_TARGET)
    • RTT_COMPONENT_PATH (default $LD_LIBRARY_PATH)
    • DEBUG (default false) Launch the deployer in GDB.

Launchfile Examples

For example, the deployer can be launched by including the launchfile in another launchfile like the following:

<launch>
  <include file="$(find rtt_ros)/launch/deployer.launch">
    <arg name="DEPLOYER_ARGS" value="-s $(find rtt_ros_integration_example)/example.ops"/>
    <arg name="LOG_LEVEL" value="debug"/>
    <arg name="DEBUG" value="false"/>
  </include>
</launch>

Wrapper Scripts

  • deployer
  • orocreate-pkg
  • orogen
  • orogen-unregister
  • rttlua
  • rttlua-tlsf
  • rttscript
  • typegen
CHANGELOG

Changelog for package rtt_ros

2.8.6 (2017-11-15)

2.8.5 (2017-03-28)

  • Merge pull request #85 from meyerj/ros-primitives-transport-indigo-devel Added a ROS transport plugin for primitive types (indigo-devel)
  • Contributors: Johannes Meyer

2.8.4 (2016-11-26)

  • rtt_ros: fixed comment in rtt_ros/scripts/deployer-corba
  • Merge pull request #40 from ahoarau/corba-deployer add Corba deployer scripts
  • rtt_ros: fixed rttlua.launch for the SCREEN:=false case (fix #72)
  • Contributors: Johannes Meyer, Antoine Hoarau

2.8.3 (2016-07-20)

2.8.2 (2015-06-12)

2.8.1 (2015-03-16)

2.7.2 (2015-07-21)

Wiki Tutorials

See ROS Wiki Tutorials for more details.

Source Tutorials

Not currently indexed.

Launch files

  • launch/rttlua.launch
      • NAME [default: $(anon rttlua)]
      • RTTLUA_ARGS [default: ]
      • OROCOS_TARGET [default: $(optenv OROCOS_TARGET)]
      • RTT_COMPONENT_PATH [default: $(env RTT_COMPONENT_PATH)]
      • DEBUG [default: false]
      • SCREEN [default: false]
      • INTERACTIVE [default: true]
  • launch/deployer.launch
      • NAME [default: $(anon deployer)]
      • LOG_LEVEL [default: info]
      • DEPLOYER_ARGS [default: ]
      • OROCOS_TARGET [default: $(optenv OROCOS_TARGET)]
      • RTT_COMPONENT_PATH [default: $(env RTT_COMPONENT_PATH)]
      • CORBA [default: false]
      • DEBUG [default: false]

Messages

No message files found.

Services

No service files found

Plugins

No plugins found.

Recent questions tagged rtt_ros at answers.ros.org

Package Summary

Tags No category tags.
Version 2.7.2
License BSD
Build type CATKIN
Use RECOMMENDED

Repository Summary

Checkout URI https://github.com/orocos/rtt_ros_integration.git
VCS Type git
VCS Version hydro-devel
Last Updated 2015-07-21
Dev Status MAINTAINED
Released RELEASED

Package Description

This package provides an RTT plugin to add a ROS node to the RTT process, as well as several wrapper scripts to enable roslaunching of orocos programs.

Additional Links

Maintainers

  • Orocos Developers

Authors

  • Ruben Smits

RTT ROS

This package contains tools for building and running Orocos components integrated into a ROS architecture.

RTT Services

ROS Package Import Chaining Service

The "ros" RTT service can be used to import all of the RTT plugins built in a given ROS package along with plugins on which they depend. These dependencies are specified in package.xml files in the <export> section.

For example, all RTT plugins in the ROS package "my_package_name" along with its dependencies can be imported by running the following Orocos .ops script (or calling the appropriate operation on the "ros" global service):

import("rtt_ros")
ros.import("my_pkg_name")

When doing the above, first the rtt_ros package is imported using the normal mechanism. This then loads the ros service, which provides a ROS import function, ros.import(), which will parse ROS package metadata and import the Orocos plugins from the named package and all packages listed in <rtt_ros><plugin_depend>PKG_NAME</plugin_depend></rtt_ros> tags in the <export> section of the package.xml files.

Catkin introduces several new dependency types for buildtime, development, and other purposes. In order to keep the RTT plugin depdencencies clear, and avoid trying to load orocos components from every package dependency, we use the extensible ROS metadata <export> tag.

For example, if loading the plugins from package pkg_one should necessitate first loading plugins from packages rtt_roscomm and pkg_two, then pkg_one/package.xml should have the following:

<package>
  <name>pkg_one</name>
  <!-- ... -->
  <export>
    <rtt_ros>
      <plugin_depend>rtt_roscomm</plugin_depend>
      <plugin_depend>pkg_two</plugin_depend>
    </rtt_ros>
  </export>
</package>

Launch Files

  • deployer.launch Launch the orocos deployer
    • LOG_LEVEL (default "info") The Orocos log level
    • DEPLOYER_ARGS (default "") Additional arguments passed to the deployer
    • OROCOS_TARGET (default $OROCOS_TARGET)
    • RTT_COMPONENT_PATH (default $LD_LIBRARY_PATH)
    • DEBUG (default false) Launch the deployer in GDB.

Launchfile Examples

For example, the deployer can be launched by including the launchfile in another launchfile like the following:

<launch>
  <include file="$(find rtt_ros)/launch/deployer.launch">
    <arg name="DEPLOYER_ARGS" value="-s $(find rtt_ros_integration_example)/example.ops"/>
    <arg name="LOG_LEVEL" value="debug"/>
    <arg name="DEBUG" value="false"/>
  </include>
</launch>

Wrapper Scripts

  • deployer
  • orocreate-pkg
  • orogen
  • orogen-unregister
  • rttlua
  • rttlua-tlsf
  • rttscript
  • typegen
CHANGELOG
No CHANGELOG found.

Wiki Tutorials

See ROS Wiki Tutorials for more details.

Source Tutorials

Not currently indexed.

Launch files

  • launch/rttlua.launch
      • NAME [default: $(anon rttlua)]
      • RTTLUA_ARGS [default: ]
      • OROCOS_TARGET [default: $(optenv OROCOS_TARGET)]
      • RTT_COMPONENT_PATH [default: $(env RTT_COMPONENT_PATH)]
      • DEBUG [default: false]
      • SCREEN [default: false]
      • INTERACTIVE [default: true]
  • launch/deployer.launch
      • NAME [default: $(anon deployer)]
      • LOG_LEVEL [default: info]
      • DEPLOYER_ARGS [default: ]
      • OROCOS_TARGET [default: $(optenv OROCOS_TARGET)]
      • RTT_COMPONENT_PATH [default: $(env RTT_COMPONENT_PATH)]
      • DEBUG [default: false]

Messages

No message files found.

Services

No service files found

Plugins

No plugins found.

Recent questions tagged rtt_ros at answers.ros.org