[Ros-kinect] OpenNI driver launch: recursive print statement - process has died

classic Classic list List threaded Threaded
6 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[Ros-kinect] OpenNI driver launch: recursive print statement - process has died

mvoge3
Hi,

I try to get data from kinect using OpenNI. I use Ubuntu 10.10 and ROS Diamondback and I'm a beginner in both.

I have followed the instructions from :
ros.org/wiki/kinect, /ni and /openni_camera.

When I try "
roslaunch openni_camera openni_node.launch" this is returned: (attached is the entire text)

[text which looks ok...]

auto-starting new master
process[master]: started with pid [28167]
ROS_MASTER_URI=http://localhost:11311

setting /run_id to 8a06c75a-4c2e-11e0-bf32-000cf1a6fb2e
process[rosout-1]: started with pid [28180]
started core service [/rosout]
process[openni_node1-2]: started with pid [28192]
process[kinect_base_link-3]: started with pid [28193]
process[kinect_base_link1-4]: started with pid [28194]
process[kinect_base_link2-5]: started with pid [28195]
process[kinect_base_link3-6]: started with pid [28196]
[/openni_node1] Number devices connected: 1
Warning: recursive print statement has occurred.  Throwing out recursive print.
Warning: recursive print statement has occurred.  Throwing out recursive print.
[openni_node1-2] process has died [pid 28192, exit code -4].
log files: /home/mvoge3/.ros/log/8a06c75a-4c2e-11e0-bf32-000cf1a6fb2e/openni_node1-2*.log

For reference, lsusb returns this for the USB port where kinect is plugged :
Bus 001 Device 075: ID 045e:02ae Microsoft Corp.
Bus 001 Device 074: ID 045e:02ad Microsoft Corp.
Bus 001 Device 073: ID 045e:02b0 Microsoft Corp.
Bus 001 Device 072: ID 0409:005a NEC Corp. HighSpeed Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

and roscd openni_camera works.

Matthieu


_______________________________________________
Ros-kinect mailing list
[hidden email]
https://code.ros.org/mailman/listinfo/ros-kinect

ERRORSroslaunch openni_camera openni_node.launch (3K) Download Attachment
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: [Ros-kinect] OpenNI driver launch: recursive print statement - process has died

futureignobel
Hi Matthieu,

if you're on an Pentium IV machine without SSE[3-4] support, this is your answer: http://answers.ros.org/question/341/how-to-compile-openni_ros-with-sse2-only-support . I'm about to open a ticket.

Regards, Tom

W dniu 12.03.2011 00:35, Matthieu Voge pisze:
Hi,

I try to get data from kinect using OpenNI. I use Ubuntu 10.10 and ROS Diamondback and I'm a beginner in both.

I have followed the instructions from :
ros.org/wiki/kinect, /ni and /openni_camera.

When I try "
roslaunch openni_camera openni_node.launch" this is returned: (attached is the entire text)

[text which looks ok...]

auto-starting new master
process[master]: started with pid [28167]
ROS_MASTER_URI=http://localhost:11311

setting /run_id to 8a06c75a-4c2e-11e0-bf32-000cf1a6fb2e
process[rosout-1]: started with pid [28180]
started core service [/rosout]
process[openni_node1-2]: started with pid [28192]
process[kinect_base_link-3]: started with pid [28193]
process[kinect_base_link1-4]: started with pid [28194]
process[kinect_base_link2-5]: started with pid [28195]
process[kinect_base_link3-6]: started with pid [28196]
[/openni_node1] Number devices connected: 1
Warning: recursive print statement has occurred.  Throwing out recursive print.
Warning: recursive print statement has occurred.  Throwing out recursive print.
[openni_node1-2] process has died [pid 28192, exit code -4].
log files: /home/mvoge3/.ros/log/8a06c75a-4c2e-11e0-bf32-000cf1a6fb2e/openni_node1-2*.log

For reference, lsusb returns this for the USB port where kinect is plugged :
Bus 001 Device 075: ID 045e:02ae Microsoft Corp.
Bus 001 Device 074: ID 045e:02ad Microsoft Corp.
Bus 001 Device 073: ID 045e:02b0 Microsoft Corp.
Bus 001 Device 072: ID 0409:005a NEC Corp. HighSpeed Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

and roscd openni_camera works.

Matthieu

_______________________________________________ Ros-kinect mailing list [hidden email] https://code.ros.org/mailman/listinfo/ros-kinect

_______________________________________________
Ros-kinect mailing list
[hidden email]
https://code.ros.org/mailman/listinfo/ros-kinect
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: [Ros-kinect] OpenNI driver launch: recursive print statement - process has died

mvoge3
I'm on a Pentium 4. I replaced "-msse4" with "-msse2" and "-O4" with "-O3" in the ni/openni_camera/CMakeLists.txt as suggested in your link. I also recompiled openni_camera and openni_kinect (which I use now) with "rosmake". The recompiling doesn't return any failures.
I still have the error quoted below when I run "roslaunch openni_camera openni_node.launch", whether or not the CMakeLists file is changed. So did I miss something?

Thanks, Matthieu

"
[...]

auto-starting new master
process[master]: started with pid [4448]
ROS_MASTER_URI=http://localhost:11311

setting /run_id to 613bb15c-509b-11e0-a295-000cf1a6fb2e
process[rosout-1]: started with pid [4461]
started core service [/rosout]
process[openni_node1-2]: started with pid [4473]
process[kinect_base_link-3]: started with pid [4474]
process[kinect_base_link1-4]: started with pid [4475]
process[kinect_base_link2-5]: started with pid [4476]
process[kinect_base_link3-6]: started with pid [4478]
[ INFO] [1300368911.610212676]: [/openni_node1] Number devices connected: 1
[ INFO] [1300368911.610688132]: [/openni_node1] 1. device on bus 001:06 is a Xbox NUI Camera (2ae) from Microsoft (45e) with serial id 'B00364204248046B'
[ INFO] [1300368911.615817067]: [/openni_node1] searching for device with index = 1
[openni_node1-2] process has died [pid 4473, exit code -4].
log files: /home/mvoge3/.ros/log/613bb15c-509b-11e0-a295-000cf1a6fb2e/openni_node1-2*.log"

Here is the log file : logopenninode1-2 .
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: [Ros-kinect] OpenNI driver launch: recursive print statement - process has died

futureignobel
Matthieu, from what you're saying I don't see you missing something. Try
executing make clean in openni_camera before calling rosmake in case you
didn't do it (you can then only call make in the openni_camera directory
instead of calling rosmake on the package). Secondly, if the latter
doesn't work, try using openni_kinect instead of ni, as ni is deprecated.

Let know if any of those worked.

Regards,
Tom

W dniu 17.03.2011 14:52, mvoge3 pisze:

> I'm on a Pentium 4. I replaced "-msse4" with "-msse2" and "-O4" with "-O3" in
> the ni/openni_camera/CMakeLists.txt as suggested in your link. I also
> recompiled openni_camera and openni_kinect (which I use now) with "rosmake".
> The recompiling doesn't return any failures.
> I still have the error quoted below when I run "roslaunch openni_camera
> openni_node.launch", whether or not the CMakeLists file is changed. So did I
> miss something?
>
> Thanks, Matthieu
>
> "
> [...]
>
> auto-starting new master
> process[master]: started with pid [4448]
> ROS_MASTER_URI=http://localhost:11311
>
> setting /run_id to 613bb15c-509b-11e0-a295-000cf1a6fb2e
> process[rosout-1]: started with pid [4461]
> started core service [/rosout]
> process[openni_node1-2]: started with pid [4473]
> process[kinect_base_link-3]: started with pid [4474]
> process[kinect_base_link1-4]: started with pid [4475]
> process[kinect_base_link2-5]: started with pid [4476]
> process[kinect_base_link3-6]: started with pid [4478]
> [ INFO] [1300368911.610212676]: [/openni_node1] Number devices connected: 1
> [ INFO] [1300368911.610688132]: [/openni_node1] 1. device on bus 001:06 is a
> Xbox NUI Camera (2ae) from Microsoft (45e) with serial id 'B00364204248046B'
> [ INFO] [1300368911.615817067]: [/openni_node1] searching for device with
> index = 1
> [openni_node1-2] process has died [pid 4473, exit code -4].
> log files:
> /home/mvoge3/.ros/log/613bb15c-509b-11e0-a295-000cf1a6fb2e/openni_node1-2*.log"
>
> Here is the log file :
> http://kinect-with-ros.976505.n3.nabble.com/file/n2693518/logopenninode1-2
> logopenninode1-2  .
>
> --
> View this message in context: http://kinect-with-ros.976505.n3.nabble.com/Ros-kinect-OpenNI-driver-launch-recursive-print-statement-process-has-died-tp2667354p2693518.html
> Sent from the Kinect with ROS mailing list archive at Nabble.com.
> _______________________________________________
> Ros-kinect mailing list
> [hidden email]
> https://code.ros.org/mailman/listinfo/ros-kinect
_______________________________________________
Ros-kinect mailing list
[hidden email]
https://code.ros.org/mailman/listinfo/ros-kinect
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[Ros-kinect] Save skeleton calibration data

Thorsten Engelhardt

Hello,

i use the openNi skeleton tracking. I achieved good results by saving the calibration data of the first Person, and the loading the data for all other Persons. Is it possible to save/load the data to/from a file or something like that? I found nothing like that in the API...

cheers,
Thorsten

___________________________________________________________
WEB.DE DSL Doppel-Flat ab 19,99 €/mtl.! Jetzt mit
gratis Handy-Flat! http://produkte.web.de/go/DSL_Doppel_Flatrate/2
_______________________________________________
Ros-kinect mailing list
[hidden email]
https://code.ros.org/mailman/listinfo/ros-kinect
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: [Ros-kinect] OpenNI driver launch: recursive print statement - process has died

mvoge3
In reply to this post by futureignobel
I still have this error. I didn't know "make clean" so I have first used "rosmake openni_camera --pre-clean", which returned 88 compiler warnings (rosmakeprecleanreturn , logbuildoutput) but no failures. Then I used "make clean" and "rosmake openni_camera" which didn't returned failures or warnings. Also I'm already using openni_kinect since yesterday. I have begun working on a more recent PC where I get another kind of issues, maybe I should pursue on that one.

Regards, Matthieu
Loading...