The kinect application series based on Dragonboard 410c - the principle and problem of automatic following robot

Following the release of the last article "One of the kinect application series based on the Dragonboard 410c - automatic robotic follow-up", I did not expect many children's shoes to be interested in this, and configured according to this article. Of course, the basic children's shoes are successful at one time, and some children's shoes that have had little contact with them have encountered many problems. They have consulted me privately. Here, I specially opened a new post for the problem set, and explained the solution and principle in detail, hoping to reduce the difficulty encountered in the development of everyone.

First, the problem point:

1. How does the dragonboard410c development board install the ubuntu core system?

A: This is a relatively junior problem. The 410c boards that many children's shoes have in their hands are pre-installed with the android system. Everyone sees that my previous blog is uploaded and the images to be burned belong to the Linux system class. Instructions are inevitably different, here we directly summarize the burning instructions in the following flash.sh, after you download and set to fastboot mode, you can run directly.

#!/bin/sh
Fastboot flash parTITIon gpt_both0.bin
Fastboot flash hyp hyp.mbn
Fastboot flash modem NON-HLOS.bin
Fastboot flash rpm rpm.mbn
Fastboot flash sbl1 sbl1.mbn
Fastboot flash sec sec.dat
Fastboot flash tz tz.mbn
Fastboot flash aboot emmc_appsboot.mbn
Fastboot erase boot
Fastboot erase rootfs
Fastboot erase devinfo
Fastboot flash boot boot-linaro-jessie-qcom-snapdragon-arm64-20160630-110
Fastboot flash rootfs linaro-jessie-developer-qcom-snapdragon-arm64-20160630-110

Figure 1 flash.sh

2.install_ros_410c.sh has a problem running.

2.1. "./ install_ros_410c.sh:bad interpreter: No such file or directory":

A: Mainly because everyone copied the install_ros_410c.sh from the windows system to our Linux system and caused a format error!

Solution:

#sh>vi filename

Use the following command to view the file format

:set ff or :set fileformat

Can see the following information

Fileformat=dos or fileformat=unix

Use the following command to modify the file format

:set ff=unix or :set fileformat=unix

:wq (Save and exit)

Finally, execute the file again.

2.2./install_ros_410c.sh:

The following packages have unmet dependencies:

Ros-kineTIc-audio-capture : Depends: libgstreamer-plugins-good1.0-0 but it is not installable

Ros-kineTIc-audio-play : Depends: libgstreamer-plugins-good1.0-0 but it is not installable

Ros-kinetic-people : Depends: ros-kinetic-leg-detector but it is not installable

Depends: ros-kinetic-people-velocity-tracker but it is not installable

Ros-kinetic-sound-play : Depends: libgstreamer-plugins-good1.0-0 but it is not installable

E: Unable to correct problems, you have held broken packages.

A: This is because the ros library is not updated, but it does not affect the function of our turtlebot. Here we can ignore it directly. In order to install the turtlebot more quickly and easily, here we re-upload the new update script and name it as :turtlebot_follower.sh

#turtlebot update manual
Set -e
# add ros debian sources
Sudo sh -c 'echo "deb http://packages.ros.org/ros-shadow-fixed/ubuntu $(lsb_release -sc) main" > /etc/apt/sources.list.d/ros-latest.list '
# setup the keys
sudo apt-key adv --keyserver hkp: //ha.pool.sks-keyservers.net: 80 --recv-key 0xB01FA116
# update repo list
Sudo apt-get update
# tmux
Sudo apt-get install tmux
Sudo apt-get install ros-kinetic-desktop-full
#initialize rosdep
Sudo rosdep init
Rosdep update
# install tools
Sudo apt-get install python-rosinstall
# source ROS environment
Source /opt/ros/kinetic/setup.bash
# Specialized installation for certain turtlebot packages
Rosinstall_generator --rosdistro indigo --exclude RPP --deps --repos turtlebot_apps > ~/turtlebot_overlay.rosinstall
Mkdir -p ~/turtlebot/src
Wstool init ~/turtlebot/src ~/turtlebot_overlay.rosinstall
# blacklist some packages we don't want to build
Cd ~/turtlebot/src
Mkdir -p warehouse_ros openni2_camera openni2_launch turtlebot_apps/pano_py turtlebot_apps/turtlebot_panorama turtlebot_apps/pano_ros turtlebot_apps/turtlebot_rapps turtlebot_apps/pano_core freenect_stack/freenect_launch freenect_stack/freenect_camera world_canvas_server
touch ./warehouse_ros/CATKIN_IGNORE ./openni2_camera/CATKIN_IGNORE ./openni2_launch/CATKIN_IGNORE ./turtlebot_apps/pano_py/CATKIN_IGNORE ./turtlebot_apps/turtlebot_panorama/CATKIN_IGNORE ./turtlebot_apps/pano_ros/CATKIN_IGNORE ./turtlebot_apps/turtlebot_rapps/CATKIN_IGNORE ./turtlebot_apps/pano_core/ CATKIN_IGNORE ./freenect_stack/freenect_launch/CATKIN_IGNORE ./freenect_stack/freenect_camera/CATKIN_IGNORE ./world_canvas_server/CATKIN_IGNORE
a
# add rosdeps
Cd ..
Rosdep install --from-path src --ignore-src -y --skip-keys freenect_launch --skip-keys openni2_launch
# install kobuki udev rules
Rosrun kobuki_ftdi create_udev_rules
Echo "source /opt/ros/kinetic/setup.bash" >> $HOME/.bashrc
Echo "export TURTLEBOT_3D_SENSOR=kinect" >> ~/.bashrc
Echo "export TURTLEBOT_3D_SENSOR=kinect" >> .bashrc

Figure 2 turtlebot_follower.sh

3.Dragonboard410c system compiled ros system source crash?

A: Many basic children's shoes take the 410c linux system when used in the build environment, directly used to compile the ros system source code, resulting in system memory crash. Here, we do not recommend using 410c as a compilation environment for the following reasons:

The flash memory of a.410c is only 1G, which is not suitable for the compilation environment of medium and large systems, which may cause memory overflow and cause system crash. Even if you insert a USB flash drive or SD card to do swap zone sharing, it is quite unstable. I have done a lot of actual measurements on this point, so I suggest you put the compilation work on your PC.

B.ros's official website already has ready-made compiled running tools that can be installed. You don't need to manually compile it at the beginning of the functional experience.

4. How does the turtlebot start manually?

A: Here we recommend using the tmux tool for manual startup, as follows:

1).tmux

2).roslaunch turtlebot_bringup minimal.launch

3).Crtl+B, press C again

4).roslaunch turtlebot_follower follower.launch

5). Connect kobuki, kinect to the 410c board and wait for about ten seconds to run.

5. Turtlebot machine debugging is difficult?

A: Many children's shoes feedback 410c does not have an LCD. Usually, it is too inconvenient to connect HDMI to TV display and external keyboard. Here, I recommend using ssh to log in and debug, as follows:

1) Start 410c and log in using linaro user;

2). Use nmcli to connect to wifi and connect your PC to the same wifi;

3). In the PC using ssh (I use win7 SecureCRT) login to the 410c Linux system, the default user and password is linaro.

4). Log in to the linaro system of the 410c board, you can remove the HDMI and keyboard on the board and enter the wireless debugging mode.

Second, update the script link:

1.flash.sh Download link: http://pan.baidu.com/s/1hrD5048

2.turtlebot_follower.sh Download link: http://pan.baidu.com/s/1mhOmF24

Disposable Cbd Vaporizer

Cbd Oil Vape,Disposable Cbd Vaporizer,Disposable Vaporizer Pen,Disposible Vape Cartridges

ALD GROUP LIMITED , https://www.aldvapor.com