yahboom
HomeLearn
Solution
Blog
Online Store
About Us
EN/中文
SLAM LiDAR📖
01.Version differences
  • 1.About SLAM Lidar
02.SLAM Lidar (A1, A2, S1, S2, S3, C1)
  • 1.How to use lidar
03.Linux basic course
  • 1.Introduction to Linux system
  • 2.Ubuntu file system
  • 3.Ubuntu common commands
  • 4.Ubuntu common editors
  • 5.Ubuntu software operation commands
  • 6.Virtual machine installation
  • 7.SSH remote control
  • 8.VNC remote control
  • 9.Transfer files remotely
  • 10.Driver library and communication
  • 11.Static IP and hotspot mode
  • 12.Bind device ID
  • 13.Capacity expansion and resource allocation
  • 14.Update system software sources
  • 15.Set root user password
  • 16.sudo free password
  • 17.Connect to WiFi network
  • 18.View system version
  • 19.Customized service management
  • 20.Back up system image
04.ROS1 basic course
  • 1.ROS introduction
  • 2.ROS installation
  • 3.ROS common command tools
  • 4.ROS workspace
  • 5.ROS function package
  • 6.ROS node
  • 7.ROS topic publisher
  • 8.ROS topic subscribers
  • 9.ROS service client
  • 10.ROS service server
  • 11.ROS action client
  • 12.ROS action server
  • 13.ROS custom message reception
  • 14.ROS-launch file
  • 15.ROS-TF transformation
  • 16.ROS parameter service
  • 17.ROS-rviz use
  • 18.ROS-rqt tool usage
  • 19.Topic message recording and playback
  • 20.urdf model introduction
  • 21.gazebo introduction
  • 22.ROS distributed communication
05.ROS1 lidar course
  • 0.ReadMe
  • 1.Preparation
  • 2.Handheld lidar mapping
  • 3.Lidar avoiding
  • 4.Lidar guard
  • 5.Lidar follow
  • 6.Lidar mapping
  • 7.rrt_exploration mapping algorithm
  • 8.Navigation and avoiding
  • 9.APP Mapping and Navigation
  • 10.RTAB 3D mapping and navigation
06.ROS2 basic course
  • 1.Introduction to ROS2
  • 2.ROS2 install Humble
  • 3.ROS2 development environment
  • 4.ROS2 workspace
  • 5.ROS2 function package
  • 6.ROS2 node
  • 7.ROS2 topic communication
  • 8.ROS2 service communication
  • 9.ROS2 action communication
  • 10.ROS2 custom interface message
  • 11.ROS2 parameter service case
  • 12.ROS2 meta-function package
  • 13.ROS2 distributed communication
  • 14.ROS2 DDS
  • 15.ROS2 time related API
  • 16.ROS2 common command tools
  • 17.ROS2 rviz2 use
  • 18.ROS2 rqt toolbox
  • 19.ROS2 Launch startup file configuration
  • 20.ROS2 recording and playback tool
  • 21.ROS2 URDF model
  • 22.ROS2 Gazebo simulation platform
  • 23.ROS2 TF2 coordinate transformation
07.ROS2 lidar course
  • 0.ReadMe
  • 1.Preparation
  • 2.Handheld lidar mapping
  • 3.Lidar avoiding
  • 4.Lidar follow
  • 5.Lidar guard
  • 6.gmapping mapping
  • 7.cartographer mapping
  • 8.Navigation and avoiding
  • 9.APP Mapping and Navigation
  • 10.RTAB 3D mapping and navigation
  • 11.Lidar patrol
08.Mapper M2 lidar course
  • 1.How to use M2M2lidar
09.High-speed version A1 lidar usage tutorial
  • 1.Preparation before using the high-speed version of A1 lidar
10.RaspberryPi5 Docker course
  • 1.Overview and installation
  • 2.Common commands
  • 3.Understand and publish images
  • 4.Hardware interaction data processing
  • 5.Enter docker container
  • 6.Update docker images
  • 7.Docker container to install ROS using accessories
Download
  • Code
  • VM File
  • Data Sheet
  • Just for Mapper M2 Lidar
  • Model File
  • PC_Software
  • ROS2_Basic_VM
Download ZIP

Welcome to SLAM LiDAR repository

4.Hardware interaction data processing

4.Hardware interaction data processing

 

4.Hardware interaction data processing4.1、Hardware mounting (port binding)4.2、GUI display in docker4.3、docker containers and hosts transfer files to each other4.3.1、use cp command4.3.1.1、Copy files from the container to the host4.3.1.2、Copy files from the host to the container4.3.2、Using Data Volumes4.3.2.1、Data Volume Overview4.3.2.2、Data volume use

 

4.1、Hardware mounting (port binding)

1、Connect the device you need to mount to the board,Create udev rules in the host (/etc/udev/rules.d/)

The following is the ROS control board and Radar equipment mounting as an example, the actual situation according to their own equipment mounting

2、Then, when opening the container, mount the devices with rules set on the rules into the docker container through parameters such as --device=/dev/myserial --device=/dev/rplidar

docker run -it --device=/dev/myserial --device=/dev/rplidar ubuntu:latest /bin/bash

3、The device can be found in the docker container

​x
jetson@ubuntu:~$ docker images
REPOSITORY                   TAG       IMAGE ID       CREATED             SIZE
ubuntu                       1.0       78ca7be949b6   About an hour ago   69.2MB
pengan88/ubuntu              1.0       78ca7be949b6   About an hour ago   69.2MB
hello-world                  latest    46331d942d63   13 months ago       9.14kB

jetson@ubuntu:~$ ll /dev | grep ttyUSB*
lrwxrwxrwx   1 root   root           7 Apr 23 18:07 myserial -> ttyUSB0
lrwxrwxrwx   1 root   root           7 Apr 23 18:07 rplidar -> ttyUSB1
crwxrwxrwx   1 root   dialout 188,   0 Apr 23 18:07 ttyUSB0
crwxrwxrwx   1 root   dialout 188,   1 Apr 23 18:07 ttyUSB1

jetson@ubuntu:~$ docker run -it   --device=/dev/myserial --device=/dev/rplidar ubuntu:latest  /bin/bash

root@03522257ba30:/# ls /dev  #There are myserial and rplidar device in docker
console  fd  full  mqueue  myserial  null  ptmx  pts  random  rplidar  shm  stderr  stdin  stdout  tty  urandom  zero

 

4.2、GUI display in docker

1、Install in the host (Factory image has been installed by default):

xxxxxxxxxx
sudo apt-get install tigervnc-standalone-server tigervnc-viewer
sudo apt-get install x11-xserver-utils

2、Execute in the host: xhost +

After the following image is displayed, perform 3 steps:

0

3、Execute the command in the host to enter the container:

xxxxxxxxxx
docker run -it \                        # Run docker images interactively
--env="DISPLAY" \                       # Open the display GUI interface
--env="QT_X11_NO_MITSHM=1" \            # Port 1 of X11 is used for display
-v /tmp/.X11-unix:/tmp/.X11-unix \      # map shows the service node directory
yahboomtechnology/ros-foxy:1.0.0        # The name of the image to start
/bin/bash                    # Executes the /bin/bash command in the container

4、Test

xxxxxxxxxx
Execute in container:rviz2

 

 

4.3、docker containers and hosts transfer files to each other

4.3.1、use cp command

4.3.1.1、Copy files from the container to the host

xxxxxxxxxx
# command
docker cp [container id:Intra-container path] [Destination host path]

# test
# Execute inside the container, create a file test
jetson@ubuntu:~$ docker ps -a
CONTAINER ID   IMAGE           COMMAND       CREATED       STATUS                   PORTS     NAMES
c54bf9efae47   ubuntu:latest   "/bin/bash"   2 hours ago   Up 9 minutes                       funny_hugle
3b9c01839579   hello-world     "/hello"      3 hours ago   Exited (0) 3 hours ago             jovial_brown
jetson@ubuntu:~$ docker attach c5
root@c54bf9efae47:/# cd
root@c54bf9efae47:~# ls
root@c54bf9efae47:~# touch test.txt
root@c54bf9efae47:~# ls
test.txt
root@c54bf9efae47:~# pwd
/root 
root@c54bf9efae47:/# (read escape sequence)   #ctrl+P+Q The container does not stop exiting
jetson@ubuntu:~$ docker cp c54bf9efae47:/root/test.txt ~/
jetson@ubuntu:~$ ls      # The test .txt file has been copied in
Desktop  Documents  Downloads  fishros  Music  openvino  Pictures  Public  rootOnNVMe  run_docker.sh  sensors  snap  temp  Templates  test.txt  Videos

example:

4.3.1.2、Copy files from the host to the container

xxxxxxxxxx
# command
docker cp [host_file_path] [container id:the path within the docker]

# test
jetson@ubuntu:~$ docker ps -a
CONTAINER ID   IMAGE           COMMAND       CREATED       STATUS                   PORTS     NAMES
c54bf9efae47   ubuntu:latest   "/bin/bash"   2 hours ago   Up 5 minutes                       funny_hugle
3b9c01839579   hello-world     "/hello"      3 hours ago   Exited (0) 3 hours ago             jovial_brown
jetson@ubuntu:~$ ls
Desktop  Documents  Downloads  fishros  Music  openvino  Pictures  Public  rootOnNVMe  run_docker.sh  sensors  snap  temp  Templates  test.txt  Videos
jetson@ubuntu:~$ touch 11.txt
jetson@ubuntu:~$ ls
11.txt  Desktop  Documents  Downloads  fishros  Music  openvino  Pictures  Public  rootOnNVMe  run_docker.sh  sensors  snap  temp  Templates  test.txt  Videos
jetson@ubuntu:~$ docker cp 11.txt c54bf9efae47:/root/
jetson@ubuntu:~$ docker exec -it c54b /bin/bash
root@c54bf9efae47:/# ls
bin  boot  dev  etc  home  lib  media  mnt  opt  proc  root  run  sbin  srv  sys  tmp  usr  var
root@c54bf9efae47:/# cd /root/
root@c54bf9efae47:~# ls     # 11.txt The file has been copied in
11.txt  test.txt

example:

 

4.3.2、Using Data Volumes

4.3.2.1、Data Volume Overview

Package the application and the running environment to form a container to run, and the run can be accompanied by the container, but our data requirements are expected to be persistent! For example, if you install a mysql and you delete the container, it is equivalent to deleting the library and running away, which is definitely not okay! So we hope that it is possible to share data between containers, and the data generated by docker containers, if a new image is not generated through docker commit, so that the data is saved as part of the image, then when the container is deleted, the data will naturally be gone! This will not work!

In order to save data, we can use volumes in Docker! Let the data be mounted locally to us! So that the data is not lost due to container deletion!

Peculiarity:

  1. Data volumes can share or reuse data between containers
  2. Changes in the volume can take effect directly
  3. Changes in the data volume will not be included in the update of the image
  4. The lifecycle of a data volume lasts until no container uses it

4.3.2.2、Data volume use

xxxxxxxxxx
# command
docker run -it -v host absolute path directory: directory inside the container image name

# Test  
docker run -it -v /home/jetson/temp:/root/temp yahboomtechnology/ros-foxy:3.4.0 /bin/bash

The /home/jetson/temp directory in the host and the /root/temp directory in the container can share data

 

Understand and publish images
Enter docker container

COMPANY

  • About us
  • Team Style
  • Blog

LEARNING & EXPLORATION

  • Tutorials
  • Edge AI hardware
  • Educational robots
  • Embedded intelligent hardware

WHERE TO BUY

  • Yahboom Online Store
  • Amazon
  • Alibaba
  • AliExpress
  • Mercado

TECHNOLOGY SUPPORT

  • Email: support@yahboom.com

BE A DISTRIBUTOR

  • Email: sales@yahboom.com
QR Code

Copyright © 2017-2026 Yahboom. All Rights Reserved.

EN/中文