-
Notifications
You must be signed in to change notification settings - Fork 52
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
add /imu and /odom topic to HrpsysSeqROSBridge #409
Comments
|
@eisoku9618 @snozawa |
https://github.com/garaemon/rtmros_common/tree/support-odom-imu-topic |
I'd like to connect the data from imu sensor to HrpsysSeqStateBridge and publish the data to |
hrpsys.py # connection for kf
if self.kf:
# currently use first acc and rate sensors for kf
s_acc=filter(lambda s : s.type == 'Acceleration', self.sensors)
if (len(s_acc)>0) and self.rh.port(s_acc[0].name) != None: # check existence of sensor ;; currently original HRP4C.xml has different naming rule of gsensor and gyrometer
connectPorts(self.rh.port(s_acc[0].name), self.kf.port('acc'))
s_rate=filter(lambda s : s.type == 'RateGyro', self.sensors)
if (len(s_rate)>0) and self.rh.port(s_rate[0].name) != None: # check existence of sensor ;; currently original HRP4C.xml has different namin g rule of gsensor and gyrometer
connectPorts(self.rh.port(s_rate[0].name), self.kf.port("rate"))
connectPorts(self.seq.port("accRef"), self.kf.port("accRef")) according the code above, connection is like this:
|
Exactly. |
If possible, I'd like to read rate and accRef. And I'm wondering whether we should use |
Yes. |
You just need to add sensor connection like this to hrpsys_ros_bridge/scripts/sensor_ros_bridge_connect.py:
Please write these connection in hrpsys_ros_bridge/scripts/sensor_ros_bridge_connect.py instead of these connection in hrpsys_ros_bridge.launch |
gotcha, I will 2014年4月16日水曜日、snozawanotifications@github.comさんは書きました:
from iPhone |
|
which are the imu data ports? |
new PR #430 supports imu |
forked from start-jsk/rtmros_gazebo#24
The text was updated successfully, but these errors were encountered: