[ros-users] Core robot controller manager

Konrad Banachowicz konradb3 at gmail.com
Sun Nov 7 14:46:30 UTC 2010

Hi Daniel,

I recently created controllers for irp6 manipulators. It use software only
servo algorithm implemented as OROCOS component. It's run 1kHz servo loop
for 8dof on pentium3 600MHz so performance isn't an issue heare. I think
OROCOS is the optimal solution for integration low-level real-time control
with ROS. You can look at orocos_controllers and irp6_robot stacks at
http://github.com/RCPRG-ros-pkg . As far as i know servo loop must have
constant period so real-time is what you need. There is some problems with
ROS and multiple servo loops running at different periods (for example
robot_state_publisher ) .

Konrad Banachowicz

2010/11/7 Daniel Stonier <d.stonier at gmail.com>

> Hi all,
> I've been working over the last few weeks to put together a core robot
> subsystem for one of our robots - it's pr2 like with a mobile base, a
> manipulator and various other motor driven mounts (14 motors in all),
> but on an a real budget and I was wondering what experiences others
> have had doing something similar.
> The primary challenges with ours are two fold:
> 1) It isn't running an ethercat based system. i.e. it's non-real time,
> though thats something I would like to upgrade on this particular
> robot in the future, however its not something that all of our robots
> will have. This means the motors are often driven on multiple loops,
> some fast and some slow (so not to burden the low spec embedded
> board). Also, the controllers in ros are using a real time publisher -
> and I made the assumption that is not usable for non real time (please
> correct me if I'm wrong!), so rebuilt all the
> controllers/transmissions we had to use.
> 2) We're running on a low spec intel atom (the lowest), so topic
> communication and loop frequencies need to be kept down. Since its not
> centralised, it needed some care designing to ensure callback
> frequencies didn't escalate and control loop periods weren't consuming
> too much horsepower. Most of it is interrupt driven now too because
> different subsystems are cycling at different speeds.
> Finally, its roughly working, but its quite ad-hoc and took alot of
> building in the long run and am wondering if there's an easier way to
> do it, or a way to genericise components so that they can be recycled
> for both non-realtime and realtime systems.
> Regards,
> Daniel Stonier
> --
> Phone : +82-10-5400-3296 (010-5400-3296)
> Home: http://snorriheim.dnsdojo.com/
> Yujin Robot: http://www.yujinrobot.com/
> Embedded Ros : http://www.ros.org/wiki/eros
> Embedded Control Libraries: http://snorriheim.dnsdojo.com/redmine/wiki/ecl
> _______________________________________________
> 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/20101107/32db9b30/attachment-0003.html>

More information about the ros-users mailing list