How an ecto ros node looks like? [closed]

asked 2013-06-10 01:25:11 -0500

jorge gravatar image

Sorry for the absolute beginner on ecto questions (I have just read the doc and run the hello world):

ecto_ros claims to provide seamlessly integration between ros and ecto: you must create a cell to wrap any publisher/subscriber. But you can only do for common ROS message types. Am I right?

If so, how hard is to create bindings for custom messages?

The idea I have in mind is to replace a bunch of nodelets by ecto nodes, but I want to keep all topics that now glue the nodelets between them and with the outside (ros) world. So it would imply to have a couple tendril-topic for any topic I have now.

All use cases I have seen of ecto are complex processing pipelines more or less self-contained, with limited pub/sub interface, so... I wonder if my idea is just completely stupid.


edit retag flag offensive reopen merge delete

Closed for the following reason question is not relevant or outdated by tfoote
close date 2015-05-29 12:59:30.595627


It would be nice if you could answer your own question if you understood how it looks like.

Mehdi. gravatar image Mehdi.  ( 2014-10-21 03:35:30 -0500 )edit

Unfortunately no. We had a plan for replacing notelets for ecto modules, but never tried. Do you have any particular application in mind?

jorge gravatar image jorge  ( 2014-10-21 06:27:32 -0500 )edit