SIGTERM is a signal sent by Ubuntu to shut down active processes. The circumstances of your error make me think that the camera may be 'going to sleep' after the first run and making the camera undetectable until the USB is unplugged and re-plugged. This issue has occurred in the past with using RealSense cameras for logging into Windows with the face using a program called Windows Hello.
The first thing I would advise trying is running an update, even if you have just freshly installed Ubuntu. Instructions on doing so can be found here:
Thanks for the prompt reply! Wished I had checked back earlier. Would you recommended doing the steps you linked before or after JetsonHack's 3 step process for the Intel RealSense R200, or dont follow JetsonHack at all.
Since the Librealsense installation script provided with the JetsonHack does automated setup of permissions for using the camera with the Jetson, that would seem to be the easiest route to take. And since the article was only published in August 2017, the information in it is probably pretty current.
I would run the JetsonHack script to install Librealsense and the Jetson permissions, and then do an update patch instruction after that to ensure that Ubuntu and the newly installed Librealsense have the latest files.
Am i right to understand that the JetsonHack's scripts are all I'd need to run? And to disregard the link you've sent?
I have done as suggested by the JetsonHacks and have bumped up to the original problem
I haven't got direct experience of using a Jetson, so I can only make educated guesses. Looking at the Jetson information and the link to the installation guide that I provided earlier, I would revise my advice to the following steps:
1. Run the Ubuntu patch update first, as described in step one of the guide I linked to.
sudo apt-get update && sudo apt-get upgrade && sudo apt-get dist-upgrade
sudo update-grub && sudo reboot
2. Skip the rest of the installation guide (which covers the usual installation method for Librealsense) and instead use the JetsonHack's script to install Librealsense and the permissions for Jetson.
Awesome! I'll do just that! Is the RealSenseROSTX2 needed?
Also, could you ask internally on troubleshooting this issue should it not work. Thanks alot!
By the way, I do not have a "sudo update-grub" it's a custom version of ubuntu and some otherwise-available commands are not available
I am not an Intel employee, so do not have access to internal Intel reference sources, unfortunately. The position stated in the past about Jetson inquiries has often been to ask the Jetson forum, since Jetson is not a product that Intel provides official tech support for. Unofficially, advice may be provided by a support team member if they have personal knowledge of the subject..
Regarding ROS, things seem to get a bit complicated at this point. My interpretation of the instructions is:
1. Install the ROS package after Librealsense has been installed.
2. The ROS package's guide says that "the ros-kinetic-librealsense package installs linux-headers in the /usr/src directory. These headers DO NOT match the Jetson TX2, so you should consider deleting them. Same with the uvcvideo realsense directory." The instructions for doing so are:
$ cd /usr/src
$ sudo rm -r linux-headers-4.4.0-70
$ sudo rm -r linux-headers-4.4.0-70-generic
$ sudo rm -r uvcvideo-1.1.1-3-realsense
3. Apparently, when the JetsonHacks script installs ros-kinetic,librealsense, you end up with two separate Librealsense installations on your Jetson. You can remove the original Librealsense installation if you wish (it seems to be optional) with:
$ cd librealsense
$ sudo make uninstall
Oh! Thanks alot for the help!
I tried those commands and it still didnt work and that's why I am here. Dont understand why I am the only one who seem to have it work only ONCE. If we went back to your theory on having it sleeping, do you have other fixes? Updating everything didnt work.
Are you running the stream at a high frames per second (FPS) value such as 60 FPS? With the R200 camera model, apps had a tendency to sometimes freeze up or crash if running at 60 FPS because the amount of data being transmitted through the USB cable overwhelmed the USB port. The fix was to run the stream at 30 FPS instead.
hmmm... How could I reduce that?
You can manually configure the resolution and FPS in a launch file. Lines 14 to 20 on the script in the ROS documentation page linked to below show how to do this,.
yea it's 30 by default
Let's return to the possibility that the camera is going to sleep after its first successful run. In that case, we would want to try to prevent sleep mode from activating at all. The next thing I would suggest trying is turning off all power-saving functions in Ubuntu, setting their activation to 'never'.