streaming to ROS topic from port

Hi,

I'm upgrading existing code from Orocos 2.6 to 2.8 on Ubuntu 14.04 with
ROS Indigo.
I have a component with a port of type "string":
$events_in = rtt.InputPort("string")
$tc:addEventPort(events_in, "events", "rFSM event input port")
I would like to stream a topic to this port:
$depl:stream("Supervisor.events",ros:topic("/events_in"))
However, I get:
1.084 [ Warning][ScriptingService] The protocol with id 3 did not
register a fall-back handler for unknown types!
1.084 [ Warning][ScriptingService] triggered by: unknown_t which does
not have a transport.
1.084 [ ERROR ][ScriptingService] Could not create transport stream for
port events with transport id 3
1.084 [ ERROR ][ScriptingService] No such transport registered. Check
your w or add the transport for type string

I import the following packages in my deploy script:
depl:import("rtt_ros")
depl:import("rtt_rosnode")
gs=rtt.provides()
ros = gs:provides("ros")
ros:import("rtt_roscomm")

In the past, string was a default type(kit) and this was no problem.
Is there a typekit that I should include?

Nick

ps: is there a way to introspect the 'policy.transport settings' at runtime?

streaming to ROS topic from port

On 12/15/2015 07:07 PM, Dominick Vanthienen wrote:
> Hi,
>
> I'm upgrading existing code from Orocos 2.6 to 2.8 on Ubuntu 14.04 with
> ROS Indigo.
> I have a component with a port of type "string":
> $events_in = rtt.InputPort("string")
> $tc:addEventPort(events_in, "events", "rFSM event input port")
> I would like to stream a topic to this port:
> $depl:stream("Supervisor.events",ros:topic("/events_in"))
> However, I get:
> 1.084 [ Warning][ScriptingService] The protocol with id 3 did not
> register a fall-back handler for unknown types!
> 1.084 [ Warning][ScriptingService] triggered by: unknown_t which does
> not have a transport.
> 1.084 [ ERROR ][ScriptingService] Could not create transport stream for
> port events with transport id 3
> 1.084 [ ERROR ][ScriptingService] No such transport registered. Check
> your w or add the transport for type string
>
> I import the following packages in my deploy script:
> depl:import("rtt_ros")
> depl:import("rtt_rosnode")
> gs=rtt.provides()
> ros = gs:provides("ros")
> ros:import("rtt_roscomm")
>
> In the past, string was a default type(kit) and this was no problem.
> Is there a typekit that I should include?
My bad,
it should be a std_msgs.String of course...

>
> Nick
>
> ps: is there a way to introspect the 'policy.transport settings' at runtime?