Revision history [back]

ok, I think I have some elements for the answer.

Basically:

• Do not follow the steps given in the orocos doc, they are deprecated and should be updated (as for the integration into ROS - the other parts of the doc are still relevant)

  -> the last doc corresponds to version 2.6 of orocos and we are now at version 2.8

• Follow the steps given in the rtt_ros_integration doc

In addition to this:

• create a folder in your workspace (as if you were doing a normal ROS package) and put all your code in there (CMakeLists.txt, package.xml, HelloWorld.cpp, Helloworld.ops...)
• for the content of these files (CMakeLists.txt, package.xml, HelloWorld.cpp, Helloworld.ops...), you can get inspiration from the examples in rtt_ros_integration_examples

• no longer use OCL_CREATE_COMPONENT in your .cpp, but ORO_CREATE_COMPONENT

  -> this is the new way of doing things

Cheers,

Antoine.

ok, I think I have some elements for the answer.

Basically:

• Do not follow the steps given in the orocos doc, they are deprecated and should be updated (as for the integration into ROS - the other parts of the doc are still relevant)

  -> the last doc corresponds to version 2.6 of orocos and we are now at version 2.8

• Follow the steps given in the rtt_ros_integration doc

In addition to this:

• create a folder in your workspace (as if you were doing a normal ROS package) and put all your code in there (CMakeLists.txt, package.xml, HelloWorld.cpp, Helloworld.ops...)
• for the content of these files (CMakeLists.txt, package.xml, HelloWorld.cpp, Helloworld.ops...), you can get inspiration from the examples in rtt_ros_integration_examples.

• no longer use OCL_CREATE_COMPONENT OCL_CREATE_COMPONENT in your .cpp, but ORO_CREATE_COMPONENT

  -> this is the new way of doing things

• compile your component the normal ROS way (catkin_make in your workspace)
• dynamically load your component: rosrun rtt_ros deployer -s helloworld.ops -linfo

Cheers,

Antoine.

ok, I think I have some elements for the answer.

Basically:

• Do not follow the steps given in the orocos doc, they are deprecated and should be updated (as for the integration into ROS - the other parts of the doc are still relevant)

  -> the last doc corresponds to version 2.6 of orocos and we are now at version 2.8

• Follow the steps given in the rtt_ros_integration doc

In addition to this:

• create a folder in your workspace (as if you were doing a normal ROS package) and put all your code in there (CMakeLists.txt, package.xml, HelloWorld.cpp, Helloworld.ops...)
• for the content of these files (CMakeLists.txt, package.xml, HelloWorld.cpp, Helloworld.ops...), you can get inspiration from the examples in rtt_ros_integration_examples.
• all instructions in helloworld.ops should end with a ";", no idea why...

• no longer use OCL_CREATE_COMPONENT in your .cpp, but ORO_CREATE_COMPONENT

  -> this is the new way of doing things

• compile your component the normal ROS way (catkin_make in your workspace)
• dynamically load your component: rosrun rtt_ros deployer -s helloworld.ops -linfo

Cheers,

Antoine.

ok, I think I have some elements for the answer.

Basically:

• Do not follow the steps given in the orocos doc, they are deprecated and should be updated (as for the integration into ROS - the other parts of the doc are still relevant)

  -> the last doc corresponds to version 2.6 of orocos and we are now at version 2.8

• Follow the steps given in the rtt_ros_integration doc

In addition to this:

• create a folder in your workspace (as if you were doing a normal ROS package) and put all your code in there (CMakeLists.txt, package.xml, HelloWorld.cpp, Helloworld.ops...)helloworld.ops...)
• for the content of these files (CMakeLists.txt, package.xml, HelloWorld.cpp, Helloworld.ops...), helloworld.ops...), you can get inspiration from the examples in rtt_ros_integration_examples
• all instructions in helloworld.ops should end with a ";", no idea why...

• no longer use OCL_CREATE_COMPONENT in your .cpp, but ORO_CREATE_COMPONENT

  -> this is the new way of doing things

• compile your component the normal ROS way (catkin_make in your workspace)
• dynamically load your component: rosrun rtt_ros deployer -s helloworld.ops -linfo

Cheers,

Antoine.