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

Error with openni_launch, arm, ubuntu 12.04

asked 2013-04-05 04:18:46 -0600

obsti gravatar image

updated 2013-04-05 21:42:08 -0600

Hello, I am using ROS groozy on a Cubox (arm) with a ASUS Xtion. When I try to start openni_launch openni.launch I get the following error

process[camera/depth/metric_rect-8]: started with pid [7815]
[FATAL] [1365171117.658239431]: Service call failed!
[FATAL] [1365171117.661252715]: Service call failed!
[FATAL] [1365171117.663611321]: Service call failed!
[FATAL] [1365171117.665707073]: Service call failed!
[camera_nodelet_manager-1] process has died [pid 6771, exit code 1, cmd /opt/ros/groovy/lib/nodelet/nodelet manager __name:=camera_nodelet_manager __log:=/home/quadcopter/.ros/log/74c9f996-9dfa-11e2-b4d2-0050431e252a/camera_nodelet_manager-1.log].
log file: /home/quadcopter/.ros/log/74c9f996-9dfa-11e2-b4d2-0050431e252a/camera_nodelet_manager-1*.log
[camera/driver-2] process has died [pid 6772, exit code 255, cmd /opt/ros/groovy/lib/nodelet/nodelet load openni_camera/driver /camera_nodelet_manager --no-bond ir:=ir rgb:=rgb depth:=depth depth_registered:=depth_registered projector:=projector __name:=driver __log:=/home/quadcopter/.ros/log/74c9f996-9dfa-11e2-b4d2-0050431e252a/camera-driver-2.log].
log file: /home/quadcopter/.ros/log/74c9f996-9dfa-11e2-b4d2-0050431e252a/camera-driver-2*.log
[camera/ir/rectify_ir-6] process has died [pid 7761, exit code 255, cmd /opt/ros/groovy/lib/nodelet/nodelet load image_proc/rectify /camera_nodelet_manager --no-bond image_mono:=image_raw __name:=rectify_ir __log:=/home/quadcopter/.ros/log/74c9f996-9dfa-11e2-b4d2-0050431e252a/camera-ir-rectify_ir-6.log].
log file: /home/quadcopter/.ros/log/74c9f996-9dfa-11e2-b4d2-0050431e252a/camera-ir-rectify_ir-6*.log
[camera/depth/rectify_depth-7] process has died [pid 7785, exit code 255, cmd /opt/ros/groovy/lib/nodelet/nodelet load image_proc/rectify /camera_nodelet_manager --no-bond image_mono:=image_raw image_rect:=image_rect_raw __name:=rectify_depth __log:=/home/quadcopter/.ros/log/74c9f996-9dfa-11e2-b4d2-0050431e252a/camera-depth-rectify_depth-7.log].
log file: /home/quadcopter/.ros/log/74c9f996-9dfa-11e2-b4d2-0050431e252a/camera-depth-rectify_depth-7*.log
[camera/rgb/rectify_mono-4] process has died [pid 7010, exit code 255, cmd /opt/ros/groovy/lib/nodelet/nodelet load image_proc/rectify /camera_nodelet_manager --no-bond __name:=rectify_mono __log:=/home/quadcopter/.ros/log/74c9f996-9dfa-11e2-b4d2-0050431e252a/camera-rgb-rectify_mono-4.log].
log file: /home/quadcopter/.ros/log/74c9f996-9dfa-11e2-b4d2-0050431e252a/camera-rgb-rectify_mono-4*.log

EDIT 1:

Most of the log files don't exist or they are empty or without use.

Here are the (I think) most important log files:

master.log: http://pastebin.com/tgMEB33e

roslaunch-cubox-qc-8340.log: http://pastebin.com/3F4SLAJw

rosout.log: http://pastebin.com/GQAv2R79

If more is needed please let me know! Thanks!

edit retag flag offensive close merge delete

Comments

Take a look at and update this question with the log files in the message you posted - the actual errors will be there.

Dan Lazewatsky gravatar image Dan Lazewatsky  ( 2013-04-05 04:59:49 -0600 )edit

Any ideas? Thanks for any help!!

obsti gravatar image obsti  ( 2013-04-06 11:42:16 -0600 )edit

I have the same issue using an Asus XtionPro Live, Ubuntu 12.04 and ROS Fuerte. The service call failed! error appears after a few secodns and most of the log files are empty. Don't know if this is a launch or run time error.

Pino gravatar image Pino  ( 2013-06-10 09:52:58 -0600 )edit

2 Answers

Sort by ยป oldest newest most voted
1

answered 2013-06-10 10:31:36 -0600

Pino gravatar image

In my case this only ocurred when using a SS USB port (super-speed USB or USB 3.0). Try using a different USB port on your computer.

edit flag offensive delete link more
0

answered 2015-01-06 09:13:42 -0600

almy91 gravatar image

For future reference same problem installed with

sudo apt-get install ros-<rosdistro>-openni-launch

and this problem was fixed.

edit flag offensive delete link more

Question Tools

1 follower

Stats

Asked: 2013-04-05 04:18:46 -0600

Seen: 1,533 times

Last updated: Jun 10 '13