| ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
Hi. I have Microstrain 3DM-GX3-45, and testing with imu_drivers stack. http://www.ros.org/wiki/microstrain_3dmgx2_imu
However, the error message below shown. Have anyone suffered similar problem?
Make sure the IMU sensor is connected to this computer. (in microstrain_3dmgx2_imu::IMU:receive) You may find further details at http://www.ros.org/wiki/microstrain_3dmgx2_imu/Troubleshooting
The data communications protocol for the various MicroStrain 3DM inertial sensors is different. The 3DM-GX2, 3DM-GX3-25 and 3DM-GX3-35/45 each have a separate data communications protocol. All of these can be found at: http://www.microstrain.com/inertial/sensors. The error certainly could mean that the communication cable and/or power is disconnected/broken/mis-wired/etc. A number of other reasons could also cause the error including 1) the command being sent is not the correct command for the particular inertial sensor, 2) the serial port is not set correctly, 3) the command being sent is not structured correctly, 4) the sensor is busy with a previously instructed command, 5) the sensor is damaged, and so forth. A terminal program is often useful to observe the actual TX and RX traffic and troubleshoot the problem.
I started coding a new driver based on boost asio for this sensor. Code can be found on github. It's not very capable yet - at the moment it can ping sensor and run self-test. Any cooperation will be highly appreciated!
Driver documentation: http://ros.org/wiki/microstrain_3dm_gx3_45.
I haven't tried it under Indigo yet. Our robots run on Hydro. Btw, there is some new API from Microstrain: http://lord-microstrain.github.io/MSCL/ -> it would be great to build ROS driver on top of this.
Asked: 2012-07-23 21:51:47 -0500
Seen: 1,782 times
Last updated: Jun 16 '13
ROS Answers is licensed under Creative Commons Attribution 3.0 Content on this site is licensed under a Creative Commons Attribution Share Alike 3.0 license.
I'm sure that there is no other process using ttyUSB1
Do you receive any errors in your /var/log/messages when plugging it in?