ROS-OpenRTM interfacing package for the opensource version of Kawada's Hiro/NEXTAGE dual-arm robot.
NOTE: This package is multi-license -- pay attention to file header in each file where license is declared. For Creative Commons nc 4.0 applied, see here.
Maintainer status: developed
Maintainer: Kei Okada <k-okada AT jsk.t.u-tokyo.ac DOT jp>, Isaac Isao Saito <iisaito AT kinugarage DOT com>
Author: Kei Okada <k-okada AT jsk.t.u-tokyo.ac DOT jp>
ROS-OpenRTM interfacing package for the opensource version of Kawada's Hiro/NEXTAGE dual-arm robot.
NOTE: This package is multi-license -- pay attention to file header in each file where license is declared. For Creative Commons nc 4.0 applied, see here.
This package also contains some sensor driver software (as of April 2016 they are the following force sensors such as Dynpick and JR3) for QNX. These drivers are stored in this robot-specific package for not many reasons than they are slightly customized for the robot. So if you can separate those as a standalone, generic package that'll be appreciated (please just let us know if you will).
Maintainer status: developed
Maintainer: Kei Okada <k-okada AT jsk.t.u-tokyo.ac DOT jp>, TORK <dev AT opensource-robotics.tokyo DOT jp>
Author: Kei Okada <k-okada AT jsk.t.u-tokyo.ac DOT jp>, Isaac I.Y. Saito <iiysaito AT opensource-robotics.tokyo DOT jp>
ROS-OpenRTM interfacing package for the opensource version of Kawada's Hiro/NEXTAGE dual-arm robot.
NOTE: This package is multi-license -- pay attention to file header in each file where license is declared. For Creative Commons nc 4.0 applied, see here.
This package also contains some sensor driver software (as of April 2016 they are the following force sensors such as Dynpick and JR3) for QNX. These drivers are stored in this robot-specific package for not many reasons than they are slightly customized for the robot. So if you can separate those as a standalone, generic package that'll be appreciated (please just let us know if you will).
Maintainer status: developed
Maintainer: Kei Okada <k-okada AT jsk.t.u-tokyo.ac DOT jp>, TORK <dev AT opensource-robotics.tokyo DOT jp>
Author: Kei Okada <k-okada AT jsk.t.u-tokyo.ac DOT jp>, Isaac I.Y. Saito <iiysaito AT opensource-robotics.tokyo DOT jp>
ROS-OpenRTM interfacing package for the opensource version of Kawada's Hiro/NEXTAGE dual-arm robot.
NOTE: This package is multi-license -- pay attention to file header in each file where license is declared. For Creative Commons nc 4.0 applied, see here.
This package also contains some sensor driver software (as of April 2016 they are the following force sensors such as Dynpick and JR3) for QNX. These drivers are stored in this robot-specific package for not many reasons than they are slightly customized for the robot. So if you can separate those as a standalone, generic package that'll be appreciated (please just let us know if you will).
Maintainer status: developed
Maintainer: Kei Okada <k-okada AT jsk.t.u-tokyo.ac DOT jp>, TORK <dev AT opensource-robotics.tokyo DOT jp>
Author: Kei Okada <k-okada AT jsk.t.u-tokyo.ac DOT jp>, Isaac I.Y. Saito <iiysaito AT opensource-robotics.tokyo DOT jp>
DEVELOPMENTAL: This status indicates that this software is not yet production ready code. The software has some level of unit-testing. There are known issues and missing functionality. The APIs are unstable but unlikely to change drastically. Use in production systems will likely require modifications including improvements and/or bug fixes. For more information see the ROS-Industrial software status page.
Dependency graph (that's yielded by rqt_dep) of hironx_ros_bridge.
Tutorials
Tutorial for Hironx is integrated into NEXTAGE OPEN's page.
Available Robot Client Methods
hironx_ros_bridge is supported by the opensource community per best-effort basis. If you find anything wrong, or would like to add more documentation, please consider opening a ticket and providing patches at the issue tracker.
Methods' API Doc
User can get a the most control of the Hironx robot through the Python class hironx_ros_bridge.hironx_client.HIRONX, where the large part of methods are derived from hrpsys.HrpsysConfigurator. Some of their methods are overridden specifically for Hironx at the Python class `HIRONX` (that is a derived class of hrpsys.HrpsysConfigurator).
As of today (Jan 31, 2014), you might want to modify the file to adjust to your environment. Open the file with the editor, replace rtm.nshost with the QNX hostname of your robot.
This will be improved so that you can specify the hostname in easier way.
Software_Status(2f)Developmental/2Column.png "Developmental")
