Ask Your Question
0

Xsens error comunicating with Ubuntu 12.04

asked 2013-02-28 06:20:42 -0500

this post is marked as community wiki

This post is a wiki. Anyone with karma >75 is welcome to improve it.

When I try to run:

$ rosrun xsens_driver mtnode.py

it shows this message:

[WARN] [WallTime: 1362075228.016104] Cannot find value for parameter: ~device, assigning default: auto

[WARN] [WallTime: 1362075228.017062] Cannot find value for parameter: ~baudrate, assigning default: 0

[ERROR] [WallTime: 1362075228.018932] Fatal: could not find proper MT device.

I don't know what is the cause of this error, the only thing I know is that when I plug sensor in the computer it doesn't create the virtual port ttyUSB0, what probably cause the node to doesn't find the sensor and send this error message. Someone know how can I fix this, what is causing this error, something is missing?

I'm using Ubuntu 12.04, Kernel 3.2.0-38-generic-pae, ros fuerte.

Before plug in the device:

dmesg|grep -i tty

[ 0.000000] console [tty0] enabled

[ 1.268379] serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A

[ 1.648533] 00:07: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A

[ 16.461250] Bluetooth: RFCOMM TTY layer initialized

After plug in

[ 0.000000] console [tty0] enabled

[ 1.268379] serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A

[ 1.648533] 00:07: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A

[ 16.461250] Bluetooth: RFCOMM TTY layer initialized

(It's the same answer)


lsusb

Before plug in

Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

Bus 002 Device 002: ID 413c:2106 Dell Computer Corp. Dell QuietKey Keyboard

Bus 002 Device 003: ID 413c:3012 Dell Computer Corp. Optical Wheel Mouse

After plug in

Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

Bus 002 Device 002: ID 413c:2106 Dell Computer Corp. Dell QuietKey Keyboard

Bus 002 Device 003: ID 413c:3012 Dell Computer Corp. Optical Wheel Mouse

Bus 005 Device 005: ID 2639:0013


And

udevadm monitor

When I plug in the device:

KERNEL[7687.265214] add /devices/pci0000:00/0000:00:1d.3/usb5/5-2 (usb)

UDEV [7687.266865] add /devices/pci0000:00/0000:00:1d.3/usb5/5-2 (usb)

KERNEL[7687.268106] add /devices/pci0000:00/0000:00:1d.3/usb5/5-2/5-2:1.0 (usb)

KERNEL[7687.268202] add /devices/pci0000:00/0000:00:1d.3/usb5/5-2/5-2:1.1 (usb)

UDEV [7687.269808] add /devices/pci0000:00/0000:00:1d.3/usb5 ...

(more)
edit retag flag offensive close merge delete

Comments

Please add dmesg output when you plug in the device.

dornhege gravatar image dornhege  ( 2013-02-28 06:41:33 -0500 )edit

4 Answers

Sort by ยป oldest newest most voted
3

answered 2013-03-04 00:21:47 -0500

this post is marked as community wiki

This post is a wiki. Anyone with karma >75 is welcome to improve it.

We are aware of this issue when using 4th generation MTi's (orange-coloured PCB/aluminum casing).

Currently, we are working on a new release of the Software Suite that solves these kind of connectivity issues when using the Xsens USB driver in Linux. Serial (RS232) interfaces don't experience this issue.

Marcel, Xsens

edit flag offensive delete link more

Comments

Do the new ones have a custom USB interface (i.e no more FTDI) or is the problem just a custom vendor/product id for the FTDI?

dornhege gravatar image dornhege  ( 2013-03-04 01:01:04 -0500 )edit

It is indeed a new USB interface, that comes directly from the PCB. It uses WinUSB. There is a driver for Linux in Gihub, but it may not work directly out of the box: https://github.com/xsens/xsens_mt

marcel_xsens gravatar image marcel_xsens  ( 2013-03-04 02:26:57 -0500 )edit

There is a prevision for when this new Software Suite will come out? Where can I obtain a cable with serial interface RS232 for this MTi generation?

Gabrielcarioca gravatar image Gabrielcarioca  ( 2013-03-05 01:04:47 -0500 )edit

Hi, Marcel. I have the the same problem. When the MTi-700 is inserted into the USB cable, no /dev/ttyUSB0 is created. However, when I inserted another USB-RS232 device, the /dev/ttyUSB0 file was successfully created. Do you have any idea about this?

Mark Chen gravatar image Mark Chen  ( 2013-12-28 17:24:43 -0500 )edit

I have solved this problem. The ttyUSB0 is concerned about the Linux version. My previous version is Ubuntu 12.04 3.2.0, and was then updated to 3.8.0. Now it works. It seems that the problem is due to the lack of the module ehci-pci. After updating the kernel, the following two steps should be run: 1. sudo modprobe usbserial 2. sudo insmod /home/abhishek/xsens_driver/xsens_mt/xsens_mt.ko (the xsens_mt.ko can be obtained by make the drive on http://github.com/xsens/xsens_mt).

Mark Chen gravatar image Mark Chen  ( 2013-12-29 01:47:42 -0500 )edit

Hi, I also use an xsens MTI-G 700 on ubuntu 12.04. I use the xsens_driver from the hydro debs and have the problem, that the configuration call "rosrun xsens_driver mtdevice.py --configure --output-mode=coapvs --output-settings=tqMAG" causes both the mtdevice.py as well as the node to fail have parsing problems: "MT error: could not parse MTData message" does anybody have an idea? both work fine when I use: rosrun xsens_driver "mtdevice.py -c -s 0x1 -m 0x4"

Georg gravatar image Georg  ( 2014-04-30 04:29:40 -0500 )edit
2

answered 2013-12-03 23:21:27 -0500

same error was coming in my system and it was solved by following procedure.

Install linux driver if your kernel version is less than 3.9

The hardware driver of the USB interface for Linux can be found on http://github.com/xsens/xsens_mt.

make the driver, and install it using the following commands

  1. make
  2. sudo modprobe usbserial
  3. sudo insmod /home/abhishek/xsens_driver/xsens_mt/xsens_mt.ko
edit flag offensive delete link more

Comments

Thanks, AbhishekMehta. However, this solution doesn't work for me. The Ubuntu 12.04 still can't find the IMU (Xsens MTI-G 700). Do you have any idea about this error? (The system can identify the USB insertion, but can't find the /dev/ttyUSB0)

Mark Chen gravatar image Mark Chen  ( 2013-12-25 18:17:44 -0500 )edit

after connecting Xsens via USB, run 2nd and 3rd command. I have to do that every time the system boots.

AbhishekMehta gravatar image AbhishekMehta  ( 2013-12-26 06:09:03 -0500 )edit

Thank you, AbhishekMehta. I have solved this problem.

Mark Chen gravatar image Mark Chen  ( 2013-12-28 17:19:22 -0500 )edit

Is there a similar solution for 3.10.96 kernel? I get error when executing make command. I am trying to interface xsens MTi-300 IMU with Nvidia TX1 (has the above kernel version). lsusb identifies the xsens sensor but /dev/ttyUSB0 is not created.

vinmean gravatar image vinmean  ( 2016-12-11 23:43:18 -0500 )edit

@vinmean The steps in this post fixed the make error for me:

https://base.xsens.com/hc/en-us/commu...

I also needed to run sudo depmod after the other steps for the module to be loaded at boot.

dpkoch gravatar image dpkoch  ( 2017-02-27 19:08:00 -0500 )edit
1

answered 2013-10-01 21:29:28 -0500

miguel_sgp gravatar image

updated 2013-10-01 21:30:46 -0500

I was having same error. Writting the following command (before executing the node): sudo chmod a+rw /dev/ttyUSB0 to give permission for the port worked for me. Good luck.

edit flag offensive delete link more
0

answered 2014-03-28 20:29:14 -0500

sai gravatar image

Configuring xsens_driver for XSENS IMU in ROS Here I employ xsens MTI-G IMU which is orange in colour.

I am working in ROS FUERTE on ubuntu 12.04 using the xsens_driver package that ships in ethzasl_xsens_driver.

I tried to get all the relevant data from IMU namely orientation orientation covariance angular velocity angular velocity covariance linear acceleration linear acceleration covariance

Configuration steps

  1. Attach IMU via USB
  2. sudo chmod 777 /dev/ttyUSB0
  3. rosrun xsens_driver mtdevice.py --configure --output-mode=coapvs --output-settings=tqMAG

The above command should result in something like this Configuring mode and settings Ok

Running the driver

  1. roslaunch xsens_driver xsens_driver.launch

  2. rostopic echo /imu/data

Then it should display all the data from IMU.

Good day!

edit flag offensive delete link more

Comments

Hi, I also use an xsens MTI-G 700 on ubuntu 12.04. I use the xsens_driver from the hydro debs and have the problem, that the configuration call "rosrun xsens_driver mtdevice.py --configure --output-mode=coapvs --output-settings=tqMAG" causes both the mtdevice.py as well as the node to fail have parsing problems: "MT error: could not parse MTData message" does anybody have an idea? both work fine when I use: rosrun xsens_driver "mtdevice.py -c -s 0x1 -m 0x4"

Georg gravatar image Georg  ( 2014-04-30 04:10:27 -0500 )edit

hi,after Configuration steps 1. Attach IMU via USB 2. sudo chmod 777 /dev/ttyUSB0 3. rosrun xsens_driver mtdevice.py --configure --output-mode=coapvs --output-settings=tqMAG after this step in the terminal, [rospack] Error: stack/package xsens_driver not found i receive this error and i cannot continue Please help ... i m using xsens MTI-G700 on ubuntu 12.04 hydro. Thanks.

Rizwan gravatar image Rizwan  ( 2014-05-01 17:53:14 -0500 )edit

@Rizwan Are you sure that you installed the correct version of the package and it lies in the ROS_PACKAGE_PATH ? Make sure that 'roscd xsens_driver' takes you to the corresponding directory

sai gravatar image sai  ( 2014-05-04 00:45:32 -0500 )edit

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Question Tools

3 followers

Stats

Asked: 2013-02-28 06:20:42 -0500

Seen: 6,345 times

Last updated: Mar 28 '14