RTT 2.x

searching for: rtt_ros_sensor_msgs_typekit

Hi all

I tried to rosmake the Lin's FindBall component from the OpenCV additions. A package called "rtt_ros_sensor_msgs_typekit" is needed. Does someone know where I can get this package?

Best Dani


This section covers all development related pages.

Place to share user examples??


I spend now two weeks of hard work to get a the toolchain and a small sample application up and running. This included having the toolchain compiled on Linux and Windows, both with corba (TAO/ACE) for debug and release. My sample application connects a TaskContext directly to QT to show how signal/slot connections could be done. The build gets done by using cmake for Linux and Windows and handles also the moc/uic from QT in one go. Click below to read the rest of this post.

Enabling corba via cmake ???


I tried to play around with corba, following the example from the Wiki, but failed at the very beginning !

Background: I have compiled and installed the toolchain 2.3.1 with corba(TAO/ACE) enabled on Kubuntu 10.10 32Bit. The Hello-World example from the RTT-Exercises are working. I got also a connection with QT running, where a interface class is derived from TaskContext / QWidget and calls Operations in a worker TaskContext. Click below to read the rest of this post.

How to debug rtt-exercises in Eclipse??


After a long time I try to get started again with Orocos and got the toolchain installed on Ubuntu 10.04. I try to run the rtt-exercises in Eclipse and get them compieled and running. However debugging does not work. When ever set a break point gdb tells me that me that it has a "Break point attribute problem" ???

Is there anything special I have to configure?? I'm trapped here!

Regards Joerg

vector of ports causes a segfault

I discovered that when using a vector of ports

std::vector<RTT::OutputPort<double> >
and add one of the ports in the vector to the component, I get segfaults in the TaskBrowser. The segfault appears when I enter the component and then leave it (cd component / cd ..)

Is this behaviour unavoidable? ie: am I allowed to use a vector of ports? Click below to read the rest of this post.

how to test if an InputPort with a Buffer policy is full?

See subject.


error in documentation about addEventPort?

The Component Builder's Manual has this text:

There are two ways to add a port to the TaskContext interface: using addPort() or addEventPort(). In the latter case, new data arriving on the port will wake up ('trigger') the activity of our TaskContext and updateHook() get's executed. If you want to know which port caused the wake-up, do not implement updateHook() (ie remove this function from your component) and use updateHook(const std::vector<PortInterface*>& updatedPorts) which provides you a list of all ports having received new data. Click below to read the rest of this post.


I am building an app where I want a TaskContext to take action when a buffer is full with data that comes in irregularly via a port. I now have an event port and an updateHook in which data is copied to the buffer, and once the buffer is full, further action is taken. A more elegant solution in my view would be to let a port with a buffer policy generate an event and wake up the TC as soon as it becomes full. Would this in your view be an interesting feature to have and hence should be added to the API?



In 2.3.1, I get this warning: Warning: xpath not found. Can't read dependencies in manifest.xml file.

It appears to look for an xpath executable. Can you point me to the (linux) app it is looking for?

Thanks in advance, Theo.