ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange
Ask Your Question
0

sicktoolbox baud rate

asked 2014-09-06 13:26:33 -0500

asusrog gravatar image

Hello,

I am using UDOO board and a sick lms 200. I get an error when i run the sicktoolbox_wrapper which says "failed to detect baud rate". If not that the program waits indefintely at startup.

* Attempting to initialize the Sick LMS... Attempting to open device @ /dev/ttyUSB0

the program waits here forever or it says "failed to detect the baud rate". I've tried the same serial to usb converter cable on my x86 machine and it works perfectly. I sometimes get the following error

" * Attempting to initialize the Sick LMS... Attempting to open device @ /dev/ttyUSB0 Device opened! Attempting to start buffer monitor... Buffer monitor started! Attempting to set requested baud rate... A Timeout Occurred! 2 tries remaining A Timeout Occurred! 1 tries remaining A Timeout Occurred - SickLIDAR::_sendMessageAndGetReply: Attempted max number of tries w/o success! Failed to set requested baud rate... Attempting to detect LMS baud rate... Checking 19200bps... ERROR: I/O exception - SickLMS2xx::_setTerminalBaud: Unable to set device attributes! ERROR: I/O exception - SickLMS2xx::_setTerminalBaud: Unable to set device attributes! ERROR: I/O exception - SickLMS2xx::_setTerminalBaud: Unable to set device attributes! /opt/ros/hydro/lib/sicktoolbox_wrapper/sicklms: symbol lookup error: /opt/ros/hydro/lib/sicktoolbox_wrapper/sicklms: undefined symbol: _ZN3ros7console5printEPNS0_10FilterBaseEPvNS0_6levels5LevelEPKciS7_S7_z

edit retag flag offensive close merge delete

Comments

You have two open questions and an open bug about your problems already. Please update those before asking a new question.

ahendrix gravatar image ahendrix  ( 2014-09-06 15:05:38 -0500 )edit

sorryy.. forgot to update them.

asusrog gravatar image asusrog  ( 2014-09-06 15:26:52 -0500 )edit

2 Answers

Sort by ยป oldest newest most voted
1

answered 2014-09-07 11:07:55 -0500

asusrog gravatar image

yup got it working. I ripped open the usb-serial converter that i had been using and turns out the chip inside was of some chinese make and wasnt compatible with the ftdi_sio module. After a while i remembered that i had an old serial to ttl logic converter which also happens to be a serial-usb converter. It uses a silabs chip compatible with cp210x. Although i was quite skeptical since it uses a max232 IC to convert the serial signal to ttl levels. But anyhow i connected it and it worked right away.

On a side note though, will the max 232 IC cause me to miss some scans??

edit flag offensive delete link more

Comments

Requesting partial scan data stream..

Why does it say partial scan?..

asusrog gravatar image asusrog  ( 2014-09-07 11:35:56 -0500 )edit

Most of the max232 series of ICs have a rated baud rate. As long as you stay below that, you shouldn't lose any data.

ahendrix gravatar image ahendrix  ( 2014-09-07 12:30:54 -0500 )edit
Requesting partial scan data stream.. why am i getting this??..
asusrog gravatar image asusrog  ( 2014-09-07 13:39:09 -0500 )edit

I'm not sure what that message means. It may be normal. Do you think it's causing problems?

ahendrix gravatar image ahendrix  ( 2014-09-07 13:52:17 -0500 )edit

No not really.. hopefully wont be a problem. Just wanted your say on this.

asusrog gravatar image asusrog  ( 2014-09-07 14:26:26 -0500 )edit
1

answered 2014-09-06 16:37:22 -0500

ahendrix gravatar image

I'm not too sure about the baud rate detection, but it looks like the driver is crashing due to an ABI mismatch:

/opt/ros/hydro/lib/sicktoolbox_wrapper/sicklms: symbol lookup error: /opt/ros/hydro/lib/sicktoolbox_wrapper/sicklms: undefined symbol: _ZN3ros7console5printEPNS0_10FilterBaseEPvNS0_6levels5LevelEPKciS7_S7_z

I would start with an apt-get update and apt-get upgrade to install the latest version of the driver, and see if it still has this problem.

edit flag offensive delete link more

Comments

i did the upgrade.. the ABI mismatch doesnt occur now but the baudrate issue is still present. I have checked the cable manually (using multimeter) as well it seems to be receiving the signals properly.Let me show you the output of dmesg | grep tty it might give u a better overview of the situation.

asusrog gravatar image asusrog  ( 2014-09-07 03:19:54 -0500 )edit

[ 421.762333] ftdi_sio ttyUSB0: error from flowcontrol urb [ 2290.997438] ftdi_sio ttyUSB0: ftdi_set_termios FAILED to set databits/stopbits/parity [ 2291.005463] ftdi_sio ttyUSB0: ftdi_set_termios urb failed to set baudrate [ 2291.012692] ftdi_sio ttyUSB0: urb failed to clear flow control

asusrog gravatar image asusrog  ( 2014-09-07 03:20:54 -0500 )edit

This still looks like a driver/hardware problem. The only relevant post I've been able to find suggests using a powered USB hub: http://gumstix.8.x6.nabble.com/FTDI-U...

ahendrix gravatar image ahendrix  ( 2014-09-07 03:50:51 -0500 )edit

okay. I'll try doing that. Thanks alot for your help ahendrix. :) .

asusrog gravatar image asusrog  ( 2014-09-07 04:20:44 -0500 )edit

Question Tools

1 follower

Stats

Asked: 2014-09-06 13:26:33 -0500

Seen: 703 times

Last updated: Sep 07 '14