Originally Posted by agamemnon
Fair enough, I was just trying to think of how you could run ROS without having to cross-compile an entire ROS install for the RIO. But then again, maybe I'm underestimating how many dependencies you'd have to cross compile to get roscpp working anyway, and I've never used ros_control so it wouldn't have occurred to me to want that on the RIO as well.
Great work again, can't wait to try it out.
Not trying to drive any particular approach, but the pain in a ROS for RIO cross compile is mainly in getting the first few packages going. Adding more after that is mostly painless - a few packages act up but the majority just work once you have things set up correctly to get any built.
And ros_control is a bit of a mind-bender until you try it, and then it makes a lot of sense. Most RIO-based HW interfaces map pretty cleanly. The talons are an exception, but that mostly depends on how many of the features you expose to users.