@Irfan-Usman I don't work for ModalAI but a few notes that might help you. https://gitlab.com/voxl-public/voxl-sdk/services/voxl-tflite-server is a good starting point -- it runs Tensorflow Lite on the VOXL/VOXL2 directly and has some built in models such as MobileNet and YoloV5. https://gitlab.com/voxl-public/voxl-sdk/services/voxl-tflite-server/-/tree/master/misc_files/usr/bin/dnn I am doing similar with ModalAI's platform -- you can reach me through the email in my profile.

Hey @ahmed-mustahid, This is a version mismatch error. The voxl-ceres-solver (v1.14.0-7) package on your voxl is two versions behind what you built against (v1.14.0-9) since you pulled in the latest from dev. When building our packages from source, make sure you use the same repo that your voxl is sourcing packages from via opkg otherwise issues like this will arise.

@modaltb I figured it out this weekend. It had to do with a swap file in streamer config. I deleted the file and rtsp showed up. However now im trying to get rtsp stream quality to match the quality on voxl portal. Its really grainy. I tried the config files in streamer at 1920X1080 and increased the bitrate by a factor of 5. Will try the camera server today. Also; is there a way to stream to both vlc and gcs at same time. The feed cuts when i try a second viewer. Lastly; is there a way to keep the rtsp stream connected to gcs from bootup. It seems like when i close the shell; the rtsp stream to gcs gets lost. Many thanks again.

after mkdir /data/docker and /usr/bin/docker daemon -g /data/docker, I saw there is file /data/docker/network/files/local-kv.db. So I just rm /data/network/files/local-kv.db. Now the docker daemon will start. But anyway I think it is better make change in /etc/systemd/system/docker-daemon.service, from ExecStart=/usr/bin/docker daemon -g /data to ExecStart=/usr/bin/docker daemon -g /data/docker So next time if we want to remove all docker images and clean up the docker, just remove everything under /data/docker.

The partial packet read error usually occurs when there is a version mismatch between packages (i.e. the size of the packet has been updated and one package has the new size but another doesn't). If you update all of your packages together this issue should go away.

In flight you should not have any thermal issues. On the bench please use a fan to cool the device The OS kills processes when the chip gets too hot. Rebooting should bring it all back

On VOXL1, we've done this via a Docker image. The image might be a bit out of date, but the idea remains the same: https://gitlab.com/voxl-public/voxl-docker-images/voxl-docker-mavsdk-cpp

Hello @Matt-Turi Thank you for your response. For some reason, I can not use the latest version voxl-mapper. I want to know how to generate mesh.ply in old version of voxl-mapper. I clicked the 「save map」button by voxl-portal and I went to the path /data/voxl_mapper/. I found the tsdf file and esdf file and both are not empty files. However, I found the mesh.ply file is empty. Do you know why the mesh.ply is empty file ? And how could I solve it ? Sample Photo (sorry for that I forget to get a screenshot with 3D View) [image: 1665052578742-voxl-web-portal-resized.png]

There are some defaults setup here, which get set on first run: https://github.com/modalai/px4-firmware/blob/voxl-dev/boards/modalai/rb5-flight/voxl-px4-set-default-parameters.config Now other settings depend on the airframe etc, but this is for our Sentinel reference drone, as reference: https://gitlab.com/voxl-public/flight-core-px4/px4-parameters/-/blob/master/platforms/v1.12/Sentinel/Sentinel_v1_param_rev_C.params

@Eric-Katzfey @tom Digging a bit deeper into this, I see that the voxl-build procedure does patch the qmi_wwan.c file, and after the patch, the VID/PID for EM7565 is in there. On one hand this is good news because it implies that the kernel does have support for the modem I'm trying to use; however, its not-so-good news for me because running with that modem has not reliable on VOXL. Aside from verifying that I am actually running the same version on my VOXL-Flight-Deck as is being built in voxl-build (see below), I'm at a loss regarding other things to do to debug this. Any thoughts on this? Following is the output of voxl-version on my board: / # voxl-version cat: /etc/modalai/voxl-software-bundle-version.txt: No such file or directory -------------------------------------------------------------------------------- system-image: ModalAI 3.3.0 BUILDER: ekatzfey BUILD_TIME: 2021-06-06_19:28 kernel: #1 SMP PREEMPT Sun Jun 6 19:41:01 UTC 2021 3.18.71-perf factory-bundle: 1.0.1 (Yocto installation) -------------------------------------------------------------------------------- architecture: aarch64 processor: apq8096 os: GNU/Linux -------------------------------------------------------------------------------- voxl-suite: Package: voxl-suite Version: 0.5.0 Depends: libjpeg_turbo (>= 9.0.4), libmodal_exposure (>= 0.0.2), libmodal_json (>= 0.3.6), libmodal_pipe (>= 2.1.1), lib rc_math (>= 1.1.5), libvoxl_cutils (>= 0.0.2), libvoxl_io (>= 0.5.4), mavlink-camera-manager (>= 0.0.2), mongoose (>= 7. 3.0), opencv (>= 4.5.2-2), openmp (>= 10.0.2), voxl-camera-calibration (>= 0.1.1), voxl-camera-server (>= 0.8.1), voxl-c pu-monitor (>= 0.2.0), voxl-dfs-server (>= 0.2.2), voxl-docker-support (>= 1.1.3), voxl-gphoto2 (>= 0.0.5), voxl-imu-ser ver (>= 0.9.1), voxl-mavlink (>= 0.0.2), voxl-modem (>= 0.12.0), voxl-mpa-tools (>= 0.3.6), voxl-nodes (>= 0.2.0), voxl- portal (>= 0.1.2), voxl-qvio-server (>= 0.3.4), voxl-streamer (>= 0.2.6), voxl-tag-detector (>= 0.0.2), voxl-tflite (>= 2.2.3), voxl-tflite-server (>= 0.1.5), voxl-utils (>= 0.8.4), voxl-vision-px4 (>= 0.9.5), voxl-vpn (>= 0.0.3) Status: install user installed Section: base Architecture: all Maintainer: james@modalai.com MD5Sum: 172dd2541a4b01ec415651b5ded3afab Size: 1956 Filename: voxl-suite_0.5.0_202111041852.ipk Description: meta-package for voxl-suite software collection Installed-Time: 144 --------------------------------------------------------------------------------

@gauravshukla914 I also noticed it. Somehow on the drone's ROS indigo system. roslaunch voxl_mpa_to_ros voxl_map_to_ros.launch won't honor the existing ROS_MASTER_URI, it always source ROS_MASTER_URI etc from my_ros_env.sh

@modaltb Yes, we used r14.1a_1.1.2-M0054-14.1a-FLAT-V3.zip as well. We will make a try with removing all the hardware connection.

@Alex-Gardner Thanks!

@Ed-Sutter Ok, I see in the actual busybox code for udhcpc it uses /usr/share/udhcpc/default.script, and I just verified that this script does execute on VOXL. Still I don't understand why /etc/resolv.conf gets overwritten. I don't know a lot about this, does anyone know if it is supposed to overwrite?

Yes, Very! We've got everything working internally and are just cleaning up a few last system image tweaks allowing the sensor writebacks then we'll publish everything!

@Anton-Gereles If you have a specific question that we can help you with please open a new forum post and we'd be more that happy to help get you going.

@Chad-Sweet thanks!

@tom Thank you! @Jeremy-Schmidt I see that you recommend the racerstar 2216/810kv motors, do you know if the propellers from m500 match this motors?