Using CH Robotics IMU UM7 with ROS

asked 2016-04-07 15:53:40 -0500

1464 ●96 ●119 ●139 http://www.namankmr.com/

Hi,

I am using the UM7 Orientation sensor with the USB Expansion board from Pololu. I am using um7_ros to use the IMU with ROS. It is getting detected and the port is /dev/ttyUSB0. But when I run rosrun um7 um7_driver, it gives the following :

[ INFO] [1460061766.522068698]: um7_driver ver 0.0.2 connected to serial port.
[ WARN] [1460061766.620629302]: Timed out waiting for packet from device.
[ WARN] [1460061766.719146180]: Timed out waiting for packet from device.
[ WARN] [1460061766.817532799]: Timed out waiting for packet from device.
[ WARN] [1460061766.915818153]: Timed out waiting for packet from device.
[ WARN] [1460061767.014103974]: Timed out waiting for packet from device.
[ERROR] [1460061767.112069178]: Unable to set CREG_COM_SETTINGS.
[ INFO] [1460061767.112128423]: Attempting reconnection after error.

Also, when I run it using CHR Serial Interface software in Windows, I get the following error:

Error: Timeout while communicating with sensor.

In both Ubuntu and Windows, it is getting detected but the Communication is not taking place.
I am not able to find why is this happening. Any help will be appreciated.

Thanks in advance.
Naman Kumar

edit retag flag offensive close merge delete

Comments

1

If the Windows tool also doesn't work, it could be that something is wrong with your hardware. Can you test a minimal scenario? Has it ever worked?

gvdhoorn ( 2016-04-08 02:35:25 -0500 )edit

1

I have the same problem while executing ros but when I tested the um7 with CH Robotics Serial Interface it works fine! However when try to read configuration by CH interfce it is blocked and only create graph works properly --> communication with um7 is damaged (UM7 is partially damaged I think)

rob_tun ( 2016-08-25 05:01:46 -0500 )edit

@Naman @rob_tun, Hi, Naman and rob_tun, now I have the same problem while executing ros node. And my hardware interface is Serial2USB.could you tell me what do you solved your problem?

zzzZuo ( 2017-03-30 04:08:47 -0500 )edit

add a comment

0

answered 2016-04-08 15:10:44 -0500

Icehawk101

955 ●27 ●35 ●55 http://ca.linkedin.com...

I ran into this problem last summer. The USB expansion board is crap. Try replacing it.

edit flag offensive delete link

add a comment

0

answered 2017-03-31 04:12:08 -0500

rob_tun
1

There is a communication problem that has no relation with ROS. The communication is not done properly. You can first check your hardware connection they try to check the communication mode and especially the baudrate since it could be changed after a reset.

edit flag offensive delete link

Comments

Also you should try to run rostopic list if you are able to see default ros nodes. 2nd problem should be if you are using ros on different IP addres. For example you can change your ROS_MASTER_URI to different IP. Try to check if your roscore running on correct IP and your port is not closed by ufw

Wiew ( 2017-03-31 06:33:37 -0500 )edit

add a comment

0

answered 2017-01-25 08:44:06 -0500

Wiew
53 ●5 ●7 ●9

What type of communication you are using? Do you have convertor RS232 to USB? i have UM7 sensor without USB (serial link directly connected to RPI pins and i must set rosrun um7 um7_driver _port:=/dev/ttyAMA0 and it runs without problem.