2012/1/17 <selma [dot] kchir [..] ...>
>
> Thanks for your answer Willy but I need Ros messages to communicate with the
> actuator and I can't use simple types.
>
Anyway it is the same but you'll have to put the Ros type into braquets.
If you want a Bool ROS type, insert the right Bool.h ROS header in
your component source and then use "InputPort<Bool> port;" (you may
have namespace to add in front of Bool)
Then there is a special synthax to connect your port to ROS dataflows.
I used to add this kind of line to the deployer, but if you are using
Orocos 2.5 their migth be a better way to do it
var ConnPolicy drive_power;
drive_power.transport = 3; // ROS == 3
drive_power.name_id = "/Protokrot/drive_power"; // ros topic
stream("Protokrot.outDriveEnable", drive_power); //connexion
>
> Thanks again,
>
> Selma.
> --
> Orocos-Users mailing list
> Orocos-Users [..] ...
> http://lists.mech.kuleuven.be/mailman/listinfo/orocos-users
error deployment
On Wed, Jan 18, 2012 at 5:21 PM, <selma [dot] kchir [..] ...> wrote:
> Thanks Ruben but I still have the same errors, it seems like the output port
> is not recognized?
> I tried to add an input port connected to a Laser sensor in the same way (I
> added a connection in the xml file and the port type is
> sensor_msgs::LaserScan) and it worked.
> Maybe the problem is related to the use of output ports or geometry_msgs?
Did you import the ros transport typekit for the geometry_msgs
(rtt_geometry_msgs package) or added it as a dependency in the
manifest of your package?
Ruben
> Selma.
> --
> Orocos-Users mailing list
> Orocos-Users [..] ...
> http://lists.mech.kuleuven.be/mailman/listinfo/orocos-users
Re:
Did you import the ros transport typekit for the geometry_msgs (rtt_geometry_msgs package) or added it as a dependency in the manifest of your package?
rtt ocl rtt_ros_integration rtt_ros_integration_std_msgs rtt_ros_integration_geometry_msgs rtt_ros_integration_sensor_msgs rtt_ros_paramSelma.error deployment