Skip to content
Snippets Groups Projects
  1. Jul 08, 2013
  2. May 22, 2013
  3. Apr 25, 2013
    • olivier stasse's avatar
      Fix a pb for inclusion of ROS & python interpreter in ART OpenRTM. · 06cf4fe8
      olivier stasse authored
      Pb: The openrtm architecture loads a shared library to implement the services of
      an OpenRTM node. The scheduling properties are ensured by the operating system
      running openrtm. Then on the robot, when the shared library is loaded it is
      run inside the real-time loop. As sot-hrp-2 was creating the interpreter and
      the ros-node in the constructor this used to break HRP-2 real-time OS.
      
      This commit change the initialization of the ros-node to use a multi-threaded
      spinner. Then ros calls are handled in a seperate non-realtime thread.
      06cf4fe8
  4. Feb 21, 2013
  5. Feb 08, 2013
  6. Sep 07, 2012
  7. May 21, 2012
  8. May 17, 2012
  9. May 15, 2012
  10. May 11, 2012
  11. May 09, 2012
  12. May 07, 2012
  13. Apr 28, 2012
  14. Mar 21, 2012
  15. Mar 20, 2012
  16. Mar 14, 2012
    • Thomas Moulard's avatar
      Add RosRobotModel entity. · d1cc7ad3
      Thomas Moulard authored
      d1cc7ad3
    • Thomas Moulard's avatar
      Add missing dependency. · 93d88047
      Thomas Moulard authored
      93d88047
    • Thomas Moulard's avatar
      Read the joint names in the robot model to fill the joint_states message. · 876acbcc
      Thomas Moulard authored
      Previous version of abstract-robot-dynamics did not contain the joint
      name. Therefore, we had no way to forward the joint names to ROS.
      
      This patch changes the ros_joint_state entity to add a
      retrieveJointNames command. This command uses the pool to retrieve an
      instance of the Dynamic entity (i.e. robot.dynamic) by using the
      entity name. It then iterates on the robot structure to fill the joint
      names in the message.
      
      This command is automatically called in the Ros class so this change
      is transparent for the end-user.
      
      However, no more assumptions are made on the robot structure so the
      sent message is exactly matching the robot structure loaded in the
      dynamic entity. In particular, the free floating DOFs are sent and the
      hard coded hand values have been removed.
      
      ROS, in fact, requires DOF names and not joint names. Therefore, the
      names are computed as follow:
      - 0 dof: ignored,
      - 1 dof: dof name is the joint name,
      - >1 dof: <joint name>_<dof id>
      876acbcc
    • Florent Lamiraux's avatar
    • Florent Lamiraux's avatar
      Fix RosImport entity documentation. · 66440792
      Florent Lamiraux authored
          RosImport entity writes data from a signal to a ROS topic.
      66440792
  17. Mar 13, 2012
  18. Mar 12, 2012
  19. Mar 08, 2012
  20. Feb 28, 2012
  21. Feb 27, 2012
  22. Feb 11, 2012
Loading