Connecting the Physical Twin with a Digital Shadow
In this example, we demonstrate how the PiCar-X can be connected to a digital shadow. For this purpose, we created a special Docker container that contains a ROS node, which does not send any commands to the physical twin. The communication between both is established via MQTT. The MQTT server is part of the digital shadow and you have to allow connections to port 1883 on the system where the MQTT server runs. This may requires adjustments to your firewall.
Adjust the environemnt files
There are three environment files with relevant variables:
- picarx.env (on the Picar-X)
- picarx-ds.env
In this files you have to adjust the I2C devices (see Getting Started) and the MQTT server IP.
Start the Digital Shadow
We assume at this point that the digital shadow runs on a X64 Linux system (e.g. a server).
# Build and execute the Docker Containers
docker compose -f docker-compose-core.yml build
docker compose -f docker-compose-ds.yml build
docker compose -f docker-compose-ds.yml up
Start the Physical Twin
- arm32v7 (RPi3)
- arm64v8 (RPi4)
Execute Commands on the Physical Twin
The digital shadow can only receive data. To let the PiCar-X move and monitor the behavior in the GAZEBO simulation, you have to execute on the PiCar-X:
# Connect to the RaspberryPi
ssh <user>@<picarx-ip>
# SWITCH INTO THE CONTAINER
docker exec -it picar-x-ackermann_skill-pt-1 /bin/bash
# INSIDE CONTAINER
source /root/catkin_ws/devel/picarx_ackermann_drive/setup.bash
# PUBLISH A MESSAGE TO TURN RIGHT WITH 50 percent motor speed
rostopic pub /picarx/drive/command picarx_msgs/Drive "{speed: 50, angle: 20}"
The model in the simulation should turn right and drive in circles until you send a different command.