Hello,

Is there any progress on this topic?

It's really a hassle to pass lots of parameters to the components.

Thanks,

Tim

Hello,

Is there any progress on this topic?

It's really a hassle to pass lots of parameters to the components.

Thanks,

Tim

On Thursday 28 October 2010 14:54:03 t [dot] t [dot] g [dot] clephas [..] ... wrote:
> Hello all,
>
> Using the rtt-ros-integration package I was able to 'convert' topics to
> ports.
>
> In the presentation from KU Leuven
> (http://www.ros.org/presentations/pr2betaprogram/Team-KUL.pdf) it states
> that rtt and ros have similar semantics.
>
> I was wondering if I could use the parameters from the ros server in the
> rtt environment. I am not sure if I'm just missing documentation and an
> example, or if it isn't implemented (yet) at all.

It is the first thing on my todo list for the rtt-ros integration.

It will be available as a plugin service.

Ruben

> Thanks,
>
> Tim

Hey Tim,

> Using the rtt-ros-integration package I was able to 'convert' topics to ports.
>
> In the presentation from KU Leuven (http://www.ros.org/presentations/pr2betaprogram/Team-KUL.pdf) it states that rtt and ros have similar semantics.
>
> I was wondering if I could use the parameters from the ros server in the rtt environment. I am not sure if I'm just missing documentation and an example, or if it isn't implemented (yet) at all.

I think this is still on our TODO list.
There will be exchange between the ros parameter server and the RTT properties.

Tinne