How can I Remove sdk 2.34 ? #6451
Comments
|
If you installed using a Debian distribution then you can remove all Librealsense related packages with this command: dpkg -l | grep "realsense" | cut -d " " -f 3 | xargs sudo dpkg --purge A RealSense support team member from Intel Support (not the GitHub RealSense team) said that the folders remain though after the packages are removed with the command above. They thought that starting with a fresh install was preferable if possible. If you installed 2.34.0 by compiling from source on Linux ... removing a previous installation and installing a new one is not honestly something I have done myself yet (I am primarily a Windows user). I would think (not certain) that following the standard process for compiling the SDK from source, with a small change to the instructions, may accomplish what you want to do. https://github.com/IntelRealSense/librealsense/blob/master/doc/installation.md The part that I would change is that instead of downloading the zip file of the latest stable version from the master branch (master.zip), I would instead download the source-code zip file from the list of files in the Assets list at the base of the release notes for 2.33.1. https://github.com/IntelRealSense/librealsense/releases/tag/v2.33.1
I would then speculate (again, not with certainty) that the command later in the instructions for installing Librealsense from source would remove the existing 2.34.0 version and install 2.33.1 using the unzipped source code for it that was downloaded .
|
|
Hi @Eslamrady42 Do you require further assistance with this case please or can it be closed? Thanks! |
|
I’m sorry to answering you late, because I didn’t have enough time to work on this but I’ll return back to work tomorrow and I’ll continue the case with you . |
|
Thanks very much for the update! I will be happy to resume the case with you when you are ready. Good luck! |
|
Hi @MartyG-RealSense I'm back and I'll start at the steps you said but I see it's the same as I used before !! |
|
Welcome back. I read the case again and see that there is no information about the installation method that you use. Do you install using source code or with a Debian package, please? |
|
I installed it as 2.352 IDK why !! |
|
Okay, that is fine. Are you using Windows or Linux? |
|
Linux Ubuntu18 |
|
Ok. And have you tried using the camera with any programs such as the RealSense Viewer now that you have installed 2.35.2 (which is the newest SDK version that was released yesterday)? |
|
Yes, it's 2.35.2 and I used it on realsense-viewer and worked well, but now I'll try it with ROS. |
|
Okay, I look forward to hearing about your ROS results. |
|
I tried and this the result, I ignored the error and continued with Rviz but I can't see any results on it after I added all parameters. eslam@root:~$ roslaunch realsense2_camera rs_d400_and_t265.launch started roslaunch server http://root:35401/ SUMMARYPARAMETERS
NODES auto-starting new master setting /run_id to 564f5db0-ac18-11ea-a1e1-64006afb8a06 |
|
If you are not using ROS wrapper version 2.2.13 (the most recent available right now), please try using it with SDK 2.35.2. https://github.com/IntelRealSense/realsense-ros/releases/tag/2.2.13 |
|
I did it now and I have another error eslam@root:~/catkin_ws$ roslaunch realsense2_camera rs_d400_and_t265.launch started roslaunch server http://root:44449/ SUMMARYPARAMETERS
NODES auto-starting new master setting /run_id to 027a1e10-ac1c-11ea-a1e1-64006afb8a06 [ INFO] [1591904719.651902284]: Device with physical ID /sys/devices/pci0000:00/0000:00:14.0/usb2/2-2/2-2:1.0/video4linux/video2 was found. [ INFO] [1591904719.703405752]: Device with physical ID /sys/devices/pci0000:00/0000:00:14.0/usb2/2-2/2-2:1.0/video4linux/video2 was found. [ INFO] [1591904719.712806024]: Device with physical ID 2-1-17 was found. |
|
What happens if you only have the D435 plugged in and use a single-camera launch instruction like roslaunch realsense2_camera rs_camera.launch |
|
this error : |
|
I have not experienced the ROS error corrupted size vs prev_size before. Research suggests that it is related to memory corruption. Does the error occur if you run the launch instruction again a second time after the launch crashes? |
|
It’s didn’t crash but I can’t access any thing from the parameters of rviz or the camera itself. |
|
You would not get any IMU topics from a D435 as it does not have an IMU. Can you receive anything in RViz from camera/infra1/image_rect_raw |
|
All I can see noimages |
|
Please see if the link below provided useful guidance for getting output from RViz: |
|
I did it in every time I used rviz. |
|
I am not in work time now as it is night time where I am. I will come back to your case when my next work day starts in 9 hours from now. I apologise for the wait until then and hope you can make progress. |
|
No problem I’ll wait for you tomorrow with another errors ^^ |
|
I tried all of the launch files and I see the same error as this : #6451 (comment) |
|
I recalled that there was a case 9 days ago about problems regarding using ROS with SDK 2.35.0. IntelRealSense/realsense-ros#1191 @doronhi the ROS wrapper developer has seen it. IntelRealSense/realsense-ros#1191 (comment) In that case, the RealSense user got a working SDK and ROS wrapper combination by using SDK 2.33.1 with firmware 12.3.0. Presumably, the ROS wrapper version is 2.2.13, since that is one that is compatible with SDK 3.33.1. IntelRealSense/realsense-ros#1228 (comment) If ROS is critical to your work and only being able to use Librealsense is not sufficient, then the options available are: (1) To wait until there is an updated ROS wrapper that is matched with SDK 2.35.0; or |
|
First of all thank you for your efforts, I deleted the SDK with the libraries 3 times until now, then I installed SDK 2.33.1 in each time but what happened is the same result all I can see is the newest SDK version!!!, all I need now from you to tell me how can I remove everything for the fourth time and reinstall SDK 2.33.1. Also I Don’t know how can you release a new version of the SDK and the previous one have errors !!!! |
|
The Librealsense SDK and the ROS wrapper are not developed in sync, and so updates to the ROS wrapper may follow behind the schedule of SDK updates. The ideal situation is to have a specific ROS wrapper version to match with a specific SDK version (e.g SDK 2.33.1 / ROS wrapper 2.2.13). It was found though that ROS wrapper 2.2.13 also worked with SDK 2.34.0, so there was not a need for a dedicated wrapper version for 2.34.0 in that case. It is possible that as the latest SDK versions move further away from 2.33.1, a new ROS wrapper version may become needed to take account of changes made in the recent Librealsense SDKs (of which there were a lot of changes in SDK 2.35.0). I am on the Support team though and not involved in Development, so I cannot comment on release plans. As I said earlier, the best way to ensure a clean build as a stable base for a new SDK / wrapper installation would be to wipe Ubuntu 18 and reinstall it from the beginning, so that there is no hidden left-overs from previous installations that could cause conflicts with new installations. I appreciate that this may not be a good option if you have a lot of stuff on the computer that you do not want to lose. Since you were able to install SDK 2.35.2, I am guessing that you built the SDK from source code and not a Debian package. Let's try and clean up your previous Librealsense installations by going to the build folder then and running this command from within it: sudo make uninstall && make clean Once the build folder is clean, delete the Librealsense folder, as you should not need it after the next step because you will be using an entirely new Librealsense source code folder to build 2.33.1. Next, build SDK 2.33.1 from source code using the "backend" method, which requires an internet connection but has no patching and is not dependent on Linux versions or kernel versions. |
|
Doronhi the RealSense ROS developer has mentioned that a new realsense2_camera version is planned to be arriving in the coming week to match with SDK 2.35.2. |
|
I'm glad to hear that #6451 (comment) rosrun tf static_transform_publisher 0 0 0 0 0 0 0 map camera_depth_optical_frame 100 rosrun rviz rviz Add -> by topic -> depth -> /color -> /points -> pointCloud2 -> ok Add -> by topic -> (camera: depth, color or infra) -> /image_raw -> Image -> ok this the steps I used but unfortunately not working with new errors. the source that I used : https://github.com/IntelRealSense/librealsense/blob/master/doc/distribution_linux.md and this one to download the latest version of realsense-ros-development : and this the error I found : eslam@root:~$ roslaunch realsense2_camera rs_camera.launch filters:=pointcloud started roslaunch server http://root:46749/ SUMMARYPARAMETERS
NODES auto-starting new master setting /run_id to cbdf6f3e-aed9-11ea-a6d8-64006afb8a06 [ INFO] [1592206135.093869032]: Device with physical ID 1-2-5 was found. |
|
When debugging, I focus on the first error that occurs in the log. This is because once one error occurs, it can create a "cascade" of errors following afterwards that make it appear as though there are multiple problems. When in fact, if you fix that first error then the others can just disappear. Continuously generating control_transfer returned errors (the first error that appears in the log) suggests that there are serious communication problems between the camera and the USB port. Do you have a different USB port that you can try the camera in, please? Also, are you using the official short USB cable that came with the camera or are you using your own longer cable? |
|
I tried USB-3.2 USB-3.1 USB-2 |
|
eslam@root:~/catkin_ws$ roslaunch realsense2_camera rs_camera.launch filters:=pointcloud started roslaunch server http://root:34247/ SUMMARYPARAMETERS
NODES auto-starting new master setting /run_id to 75dda930-af32-11ea-9f8d-64006afb8a06 [ INFO] [1592244216.171301890]: Device with physical ID 2-2-29 was found. |
|
Do you have the option of using a mains electricity powered USB hub with the camera instead of plugging the camera directly into the computer or into a hub not powered by a mains electricity wall socket? RealSense cameras are very sensitive to the state of the USB port. If the problem is related to the USB ports of the computer not being supplied with power stably enough by the computer's power supply unit for good communication with the camera then a mains powered USB hub may help to make the control_transfer returned errors disappear. |
|
It’s the main USB ports from the laptop !!! |
|
USB ports that are built into the computer draw their power from the computer's power supply components and so are vulnerable to any instabilities in that supplied power. USB ports that are supplied power by the mains electricity socket have greater stability of supplied power. |
|
So what is the solution in this case ? |
|
Intel have successfully tested the AmazonBasics mains powered USB 3 hub with the 400 Series cameras. I have one myself and have no problem with it. They are available with full size USB-A connectors and micro USB-C connectors for connecting the hub to the computer, so if you consider purchasing one, make sure that you get the USB-A type if your computer does not have a USB-C micro USB port on it. https://support.intelrealsense.com/hc/en-us/community/posts/360046835933/comments/360011483694 |
|
Ok that’s sounds great, but it’s working with me on realsense-viewer And I tried on another laptop before with lower performance and worked well with me ... Also my application can’t support 36w for only USB hub !! |
|
My understanding is that there are differences between how the RealSense SDK and the ROS wrapper handle the camera. You can manually define in the ROS wrapper the USB port that the wrapper looks for a particular camera at by using the usb_port_id instruction instead of a serial number. It may not help if the problem is with communication between the port and the camera though. "usb_port_id: will attach to the device with the given USB port (usb_port_id). i.e 4-1, 4-2 etc. Default, ignore USB port when choosing a device." https://github.com/IntelRealSense/realsense-ros#launch-parameters |
|
Ok thank you @MartyG-RealSense for your time, you can close this case, I’ll try with the USB hub and I’ll creat new case if there is any errors . |
|
Thank you very much for your patience during this case @Eslamrady42 - good luck! |
Kindly please I want to remove all SDK 2.34 with everything with it , then reinstall SDK 2.33 .
The text was updated successfully, but these errors were encountered: