voxl-docker-mavsdk-python build issues
-
@Vinny @brahim @Eric-Katzfey We're still running into the issue of no meaningful data being sent to gazebo. The only data is still the heartbeat packets.
We're referencing: https://docs.modalai.com/voxl2-PX4-hitl/We've done the steps up to: docker run --rm -it --net=host --privileged -e DISPLAY=$DISPLAY -v /dev/input:/dev/input:rw -v /tmp/.X11-unix:/tmp/.X11-unix:ro voxl-gazebo-docker ./run_gazebo.bash
and
qshell dsp_hitl status which is telling us about the heartbeat only.
Also, we tried the archived instructions to see if we would get a different output.
The FTDI cable used is the same, but the serial port closed issue has stopped. Don't know why.
The warning for SDF I feel like is the source of the problem.
The warning when running docker run --rm:
Status output:
@Alexander-Saunders Are you doing
xhost +before running docker? -
@Alexander-Saunders Are you doing
xhost +before running docker?@Eric-Katzfey The latest attempts, yes. After running that and
docker run --rm -it --net=host --privileged -e DISPLAY=$DISPLAY -v /dev/input:/dev/input:rw -v /tmp/.X11-unix:/tmp/.X11-unix:ro voxl-gazebo-docker ./run_gazebo.bashgazebo will open up. The issue is connect gazebo with VOXL2 to run in HITL mode. I've followed two of the video from Modalai and Ascend exactly with no luck. Also went through the documentation again.
All instances are being ran on the host computer. When comparing the image from above to docs, we are only getting heartbeat packets.
-
@Eric-Katzfey The latest attempts, yes. After running that and
docker run --rm -it --net=host --privileged -e DISPLAY=$DISPLAY -v /dev/input:/dev/input:rw -v /tmp/.X11-unix:/tmp/.X11-unix:ro voxl-gazebo-docker ./run_gazebo.bashgazebo will open up. The issue is connect gazebo with VOXL2 to run in HITL mode. I've followed two of the video from Modalai and Ascend exactly with no luck. Also went through the documentation again.
All instances are being ran on the host computer. When comparing the image from above to docs, we are only getting heartbeat packets.
@Alexander-Saunders The heartbeat counter is the amount of heartbeat messages being sent out, not received. So you are not getting anything on the serial port.
-
@Eric-Katzfey The latest attempts, yes. After running that and
docker run --rm -it --net=host --privileged -e DISPLAY=$DISPLAY -v /dev/input:/dev/input:rw -v /tmp/.X11-unix:/tmp/.X11-unix:ro voxl-gazebo-docker ./run_gazebo.bashgazebo will open up. The issue is connect gazebo with VOXL2 to run in HITL mode. I've followed two of the video from Modalai and Ascend exactly with no luck. Also went through the documentation again.
All instances are being ran on the host computer. When comparing the image from above to docs, we are only getting heartbeat packets.
-
@Eric-Katzfey The latest attempts, yes. After running that and
docker run --rm -it --net=host --privileged -e DISPLAY=$DISPLAY -v /dev/input:/dev/input:rw -v /tmp/.X11-unix:/tmp/.X11-unix:ro voxl-gazebo-docker ./run_gazebo.bashgazebo will open up. The issue is connect gazebo with VOXL2 to run in HITL mode. I've followed two of the video from Modalai and Ascend exactly with no luck. Also went through the documentation again.
All instances are being ran on the host computer. When comparing the image from above to docs, we are only getting heartbeat packets.
@Alexander-Saunders Definitely looks like a permissions issue of some sort in your system.
-
@Alexander-Saunders Definitely looks like a permissions issue of some sort in your system.
@Eric-Katzfey Are you suggesting giving the file/repo permissions with
xhost si:localuser:rootAlso we are using the FDTI cable provided with the ESC AND USB C to A to connect to host.
-
@Eric-Katzfey Are you suggesting giving the file/repo permissions with
xhost si:localuser:rootAlso we are using the FDTI cable provided with the ESC AND USB C to A to connect to host.
@Alexander-Saunders I'm only suggesting that there is a permissions problem of some sort. I don't see that on my machine so just trying to figure out what is different in your environment.
-
@Alexander-Saunders I'm only suggesting that there is a permissions problem of some sort. I don't see that on my machine so just trying to figure out what is different in your environment.
@Eric-Katzfey I tried giving permission to user with no change.
-
@Alexander-Saunders I'm only suggesting that there is a permissions problem of some sort. I don't see that on my machine so just trying to figure out what is different in your environment.
@Eric-Katzfey Is it possible to see a picture of your terminal of the commands you sent?
-
@Alexander-Saunders I'm only suggesting that there is a permissions problem of some sort. I don't see that on my machine so just trying to figure out what is different in your environment.
-
@Alexander-Saunders iris_hitl.sdf is part of the docker image so it will be the same.
-
@Eric-Katzfey Is it possible to see a picture of your terminal of the commands you sent?
modalai@modalai-XPS-15-9570:~$ docker run --rm -it --net=host --privileged -v /dev/input:/dev/input:rw voxl-gazebo-docker root@modalai-XPS-15-9570:/usr/workspace/voxl2_hitl_gazebo# ls CMakeLists.txt build-gazebo.bash include package.xml scripts Dockerfile build-mavlink.bash mavlink resources src README.md cmake mavlink-libs run-docker-image.bash unit_tests build docker-commands.txt models run_gazebo.bash worlds build-docker-image.bash external msgs run_headless.bash root@modalai-XPS-15-9570:/usr/workspace/voxl2_hitl_gazebo# ls /dev/ttyUSB0 /dev/ttyUSB0 root@modalai-XPS-15-9570:/usr/workspace/voxl2_hitl_gazebo# ls -l /dev/ttyUSB0 crw-rw---- 1 root dialout 188, 0 Jun 3 16:02 /dev/ttyUSB0 root@modalai-XPS-15-9570:/usr/workspace/voxl2_hitl_gazebo# ./run_headless.bash GAZEBO_PLUGIN_PATH :/usr/workspace/voxl2_hitl_gazebo GAZEBO_MODEL_PATH :/usr/workspace/voxl2_hitl_gazebo/models LD_LIBRARY_PATH :/usr/workspace/voxl2_hitl_gazebo/build Warning [parser.cc:833] XML Attribute[version] in element[sdf] not defined in SDF, ignoring. Warning [parser.cc:833] XML Attribute[version] in element[sdf] not defined in SDF, ignoring. Opened serial device /dev/ttyUSB0 -
@Eric-Katzfey Is it possible to see a picture of your terminal of the commands you sent?
modalai@modalai-XPS-15-9570:~$ docker images | grep gazebo voxl-gazebo-docker latest 1c8ce4f31e4f 3 months ago 3.73GB voxl-gazebo-docker v1.2 1c8ce4f31e4f 3 months ago 3.73GB -
@Eric-Katzfey Is it possible to see a picture of your terminal of the commands you sent?
@Alexander-Saunders We have quite a few customers using HITL successfully and they are using the instructions in the document so I'm thinking there is something in your environment that is causing the issue. Do you have access to a different Linux machine that you can use?
-
@Alexander-Saunders We have quite a few customers using HITL successfully and they are using the instructions in the document so I'm thinking there is something in your environment that is causing the issue. Do you have access to a different Linux machine that you can use?
@Eric-Katzfey Update:
We switched some of the wires for the FTDI cable and now receiving data. We went back to following the HITL docs along with https://forum.modalai.com/topic/3511/serial-port-closed-and-other-hitl-errors/9 . We have the drone running in HITL via QGC and running the voxl-px4-hitl command. Despite this, gazebo is still not showing the drone or connecting. Could the issue possibly be with the Dockerfile that reflects bionic instead of focal since that had to be changed for the image to be pulled? We also tried running ./run-docker.sh within the directory and received docker run --help.
-
@Eric-Katzfey Update:
We switched some of the wires for the FTDI cable and now receiving data. We went back to following the HITL docs along with https://forum.modalai.com/topic/3511/serial-port-closed-and-other-hitl-errors/9 . We have the drone running in HITL via QGC and running the voxl-px4-hitl command. Despite this, gazebo is still not showing the drone or connecting. Could the issue possibly be with the Dockerfile that reflects bionic instead of focal since that had to be changed for the image to be pulled? We also tried running ./run-docker.sh within the directory and received docker run --help.
@Alexander-Saunders Looks better now. What does the
dsp_hitl startcommand look like now? Seems like it is setup for VIO only.
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login