[ros-users] tcpros on ethernet-enabled embedded devices

Medi-Care Robotics itsmyrobot at gmail.com
Thu Sep 22 22:00:18 UTC 2011


I think you need to expand it's possibilities yourself. I havent worked with it yet because i'm still waiting for my ethernet module...

Did you get it to work at all and if you did; How?

Verstuurd vanaf mijn iPhone

Op 22 sep. 2011 om 22:52 heeft Mike Purvis <mpurvis at clearpathrobotics.com> het volgende geschreven:

> Hi,
> 
> The closest thing I was able to find is rosduino, which does bring itself up as a node and publish a topic, but it looks pretty hacky and single-purpose: https://code.ros.org/svn/wg-ros-pkg/branches/trunk_cturtle/sandbox/arduino/sketch/rosduino.pde
> 
> Is there something else that I'm missing?
> 
> M.
> 
> 
> 
> On 21 September 2011 17:23, Medi-Care Robotics <itsmyrobot at gmail.com> wrote:
> There seems to be a arduino tcp stack.  It is on the roswiki when you search for arduino. Allthough i also could not yet figure out how to use it...
> 
> Verstuurd vanaf mijn iPhone
> 
> Op 21 sep. 2011 om 23:19 heeft Mike Purvis <mpurvis at clearpathrobotics.com> het volgende geschreven:
> 
> > Hey all,
> >
> > Has anyone had any luck deploying TCPROS on microcontrollers which have ethernet interfaces?
> >
> > I'm using a Cortex M3, and I'd like to be able to do realtime stuff, so I would prefer to stay close to the metal, rather than running on top of a linux kernel. What I'm envisioning is this device participating on a wired network with a PC which provides roscore. The M3 would come up and have an IP configured where it looks for core (or it could just arp on its subnet and try them all).
> >
> > On a high level, what's the feasibility of this? How possible will it be to run the comms portion of roscpp without depending on OS-provided process management, signalling, sockets, etc?
> >
> > I've been having trouble using eros with the vendor-provided toolchain, so I've also been experimenting with just manually compiling portions of libros--- how realistic is that as an alternative approach?
> >
> > As a third possibility, would it make sense to try to build this up from rosserial, rather than by peeling away layers of roscpp?
> >
> > Thanks for any feedback or suggestions,
> >
> > Mike
> > _______________________________________________
> > ros-users mailing list
> > ros-users at code.ros.org
> > https://code.ros.org/mailman/listinfo/ros-users
> _______________________________________________
> ros-users mailing list
> ros-users at code.ros.org
> https://code.ros.org/mailman/listinfo/ros-users
> 
> _______________________________________________
> ros-users mailing list
> ros-users at code.ros.org
> https://code.ros.org/mailman/listinfo/ros-users
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ros.org/pipermail/ros-users/attachments/20110923/3129bc25/attachment-0004.html>


More information about the ros-users mailing list