up_board_setup
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
up_board_setup [2017/01/05 18:51] – [Step 3: Provide Kernel Source Access and Install Latest RealSense Patches] jadintredup | up_board_setup [2017/01/05 20:01] (current) – [Step 5: Verify Functionality by Launching a Nodelet] jadintredup | ||
---|---|---|---|
Line 37: | Line 37: | ||
sudo reboot | sudo reboot | ||
uname -r | uname -r | ||
- | </ | + | </ |
---- | ---- | ||
==== Step 3: Provide Kernel Source Access and Install Latest RealSense Patches ==== | ==== Step 3: Provide Kernel Source Access and Install Latest RealSense Patches ==== | ||
Line 47: | Line 47: | ||
</ | </ | ||
- | Now we can move onto installing ROS with RealSense support. | + | Now we can move onto installing ROS with RealSense support.\\ |
+ | ---- | ||
+ | ==== Step 4: Install ROS Kinetic Distribution ==== | ||
+ | The board used in the Development kit only support Linux distributions and so we can not use the official RealSense SDK, as it is only supported for Windows systems. Instead, we use ROS, as it has packages for RealSense compatibility and is an easy method to interface with robotic platforms.\\ | ||
+ | |||
+ | Launch a terminal shell and run the following commands to add the ROS repository to Ubuntu and update the package lists. | ||
+ | < | ||
+ | sudo add-spt-repository http:// | ||
+ | sudo apt-key adv --keyserver hkp:// | ||
+ | | ||
+ | sudo apt update | ||
+ | </ | ||
+ | Now run these commands to install the base ROS software and RealSense packages | ||
+ | < | ||
+ | sudo apt -y install ros-kinetic-desktop-full python-rosinstall ros-kinetic-realsense-camera | ||
+ | sudo rosdep init | ||
+ | rosdep update | ||
+ | echo " | ||
+ | source ~/.bashrc | ||
+ | </ | ||
+ | Adding setup.bash to the .bashrc file ensures that the ROS framework is available in the active environment. The ros-kinetic-librealsense package adds patches to the kernel that can not take effect until the system has been rebooted. Run a reboot command then ensure the UPboard kernel is still in place. | ||
+ | < | ||
+ | sudo reboot | ||
+ | uname -r | ||
+ | </ | ||
+ | ---- | ||
+ | ==== Step 5: Verify Functionality by Launching a Nodelet ==== |
up_board_setup.1483671083.txt.gz · Last modified: by jadintredup