Yeah, I've read that. It addresses getting ROS running on windows,
which is not what I want to do. I don't need a complete ROS environment
on windows. All I need is to communicate with a ROS network.
My question is whether it will be fairly straight forward to emulate a a
very simple ROS node on windows (capable of sending joystick commands),
or if that will be complicated enough that I'm better off doing
something proprietary for the windows<->ROS communication link.
To be clear, I'm talking about trying to implement the bare minimum
required to appear as a ROS node to roscore (running on another machine)
from scratch in C#.
-Aaron
On 6/14/2010 5:18 PM, Ken Conley wrote:
> This wiki page has all the currently known ways of getting running on
> Windows:
>
> http://www.ros.org/wiki/Windows
>
> - Ken
>
> On Mon, Jun 14, 2010 at 11:18 AM, Aaron Solochek
> <aarons-ros@aberrant.org <mailto:aarons-ros@aberrant.org>> wrote:
>
> The system I'm working on uses ROS on the backend for a variety of
> control stuff, but has a user interface that is going to be written
> in C#.
>
> What is the recommended way to get some 2-way communication going
> between this windows program and ROS? Should I make a node on the linux
> box that speaks some proprietary thing with the windows program, or
> should I try to implement a ROS node in C#?
>
> Better yet, has anyone already done something I can use for this? :)
>
> Any advice would be appreciated, and please copy me on replies since I'm
> only getting the daily digest of this list.
>
> Thanks,
>
> -Aaron
> _______________________________________________
> ros-users mailing list
> ros-users@code.ros.org <mailto:ros-users@code.ros.org>
> https://code.ros.org/mailman/listinfo/ros-users
>
>
> !DSPAM:4c169cd0309315323969998!
(text/plain)