-
Notifications
You must be signed in to change notification settings - Fork 60
movidius_ncs_stream nodelet can be run only once #106
Comments
@paLeziart |
@chaoli2
However the next times, when I relaunch the nodes and it doesn't work (output
I will try to unplug the stick (mine is this one https://up-shop.org/1071-large_default/up-ai-core-x.jpg), boot once, shutdown then re-plug the stick to see if it changes something. Best, |
Hello, I have some news. After some tests, it looks like the problem is not entirely linked to the movidius node.
So I was wondering if it was not some kind of communication issue with the realsense cameram especially since I did not have the "realsense" string that I was supposed to have by typing So I just tried to install everything again from scratch with the "classic" ubuntu kernel just in case it was the special ubuntu kernel for upboard which was messing up some packages. With the classic Ubuntu 16.04 kernel I have this "realsense" string after the
is displayed in the middle of the [INFO] outputs when I run the node and
when I Ctrl+C the node, thing that I did not have before. There are still crashes with the movidius nodes not properly being killed. I tried to find a solution by searching a bit everywhere online and I finally found a workaround:
So basically I am decoupling the movidius node from the realsense camera nodes and there is no issue, I can run everything as many time as I want. In conclusion, I think there is something wrong going on with the communication between the movidius node which is in charge of calling the realsense camera nodes with the standard command I don't know if I can close the issue, as you want. Best, |
@paLeziart For this issue, we have no concern to close it. Thanks. |
Greetings,
I am facing an issue working with the ncs detection nodes, basically it works only once. I cannot launch the network again if I stop the node. Rebooting my hardware allows me to launch the node again but it is not very convenient.
When I run
roslaunch movidius_ncs_launch ncs_camera.launch cnn_type:=mobilenetssd camera:=realsense
for the first time I get:And if I then run in another terminal
roslaunch movidius_ncs_launch ncs_stream_detection_example.launch camera_topic:="/camera/color/image_raw"
a window opens with the video stream and the bounding boxes of detected objects. So everything works and I am happy.If I shut down both terminal with CTRL+C then run again
roslaunch movidius_ncs_launch ncs_camera.launch cnn_type:=mobilenetssd camera:=realsense
I get:I tried to avoid this error with:
roslaunch realsense2_camera rs_camera.launch
thenroslaunch movidius_ncs_launch ncs_camera.launch cnn_type:=mobilenetssd camera:=others input_topic:=/camera/color/image_raw
. There is no red error message but it still does not work.Finally, I quickly looked into the ncs_nodelet.cpp in /movidius_ncs_stream/src. I just tried to change the subscribed topic "/camera/rgb/image_raw" into "/camera/color/image_raw". After running
catkin_make
to take into account that change, runningroslaunch movidius_ncs_launch ncs_camera.launch cnn_type:=mobilenetssd camera:=realsense
outputs[ INFO] [1554458577.420255220]: started 0 threads
instead of the group of error messages.For the hardware, I am using an upboard squared with a movidius myriad X and a Realsense D435 camera. OS is Ubuntu 16.04 with Ubuntu kernel 4.15.0 for UP (UP is for upboard).
Can provide more information if you need it, the error logs for instance.
Thank you for your help.
Best,
The text was updated successfully, but these errors were encountered: