Attention: Answers.ros.org is deprecated as of August the 11th, 2023. Please visit robotics.stackexchange.com to ask a new question. This site will remain online in read-only mode during the transition and into the foreseeable future. Selected questions and answers have been migrated, and redirects have been put in place to direct users to the corresponding questions on Robotics Stack Exchange. Additional details are available here.

Asctec_Proc - Timeout: 0 bytes available 3 bytes requested

asked 2013-07-12 02:40:19 -0600

pkohout

336 ●35 ●42 ●49

updated 2013-07-12 02:47:04 -0600

Hi, i try to run ros on the Asctec Pelican, but when i run

roslaunch asctec_proc asctec_driver_nodelets.launch

i get the following error:

[ERROR] [1230811515.060357725]: Read (-1): [ERROR] [1230811515.061434957]: Read failed[ERROR] [1230811515.122562563]: Timeout: 0 bytes available 3 bytes requested[ERROR] [1230811515.123636163]:Error Reading Packet Header: Resource temporarily unavailable

On the Atomboard i have installed Ubuntu 11.10 and ROS-Fuerte.

The ros-node also sais it connects succsesfully to /dev/ttyUSB0, Baudrate 57600.

I have tried it with extern current and with the battery.

Does anyone know how to fix this problem ?

Please tell me if further information is needed

edit retag flag offensive close merge delete

add a comment

1 Answer

Sort by » oldest newest most voted

answered 2013-07-14 23:04:19 -0600

Markus Achtelik
390 ●8 ●11 ●19

is the Atomboard connected properly to the low level processor of the pelican? This might help: http://asctec-users.986163.n3.nabble....

edit flag offensive delete link

Comments

thanks...we was using a different cable, which of course do not work. now all starts without any erros :)

pkohout ( 2013-07-15 04:49:33 -0600 )edit

add a comment

Question Tools

Stats

Asked: 2013-07-12 02:40:19 -0600

Seen: 283 times

Last updated: Jul 12 '13

Asctec_Proc - Timeout: 0 bytes available 3 bytes requested edit

1 Answer

Comments

Question Tools

Stats

Related questions

Asctec_Proc - Timeout: 0 bytes available 3 bytes requested