@Chad-Sweet Thanks for responding to my post. is 32 GB the limit of what the VOXL can take as far as SD card size is concerned? Also, by auxiliary computer I mean an FPGA that is interacting with the VOXL/PX4. Regards

Hey @Patrick-Hinchey would you please send that board in for an RMA diagnostic. Details on our RMA process are here Before shipping the unit, please purchase an RMA via the link above and fill out the RMA form here. If you have any questions please let me know. Thank you!

@Maxim-Temp Also please upload the voxl-cross docker image v2.2 .

@Ed-Sutter That is correct, modemmanager is not used. As you can see in the patch here: https://gitlab.com/voxl-public/system-image-build/meta-voxl/-/blob/master/recipes-kernel/linux-quic/files/qmi_wwan2.patch The path to the qmi_wwan.c file that is being modified / used is drivers/net/usb/qmi_wwan.c

@hmlow I believe this is normal. You're utilizing some CPU hungry programs so they would indeed spike the CPU load. @modaltb @Vinny can chime in on this

Ok... whatever you did seems to have fixed it. Thanks

@Steve-Turner voxl-build allows you to build the kernel only which you can then flash on top of an existing system. Qualcomm licenses are required in order to build a full system image.

@modaltb This worked for me. Removing the USBC cable, booting up, and then plugging in.

Hey @ahmed-mustahid, pipe_client_send_control_cmd is a function provided by libmodal-pipe that you could use from another C/C++ application (not within voxl-mapper) to send commands, thats likely why you didn't see it. As for the syntax of the plan to command, messages are constructed as such: const msg = "plan_to: " + (pos[0] + plan_pt.position.x) + "," + (pos[1] + plan_pt.position.y) + "," + (pos[2] + plan_pt.position.z); i.e. message starts with "plan_to: ", and is followed by a comma separated (X,Y,Z) point. If you can follow this syntax you should be able to send commands using whichever method works best in your workflow.

@Steve-Turner Glad to hear you were able to make substantial progress!

@wilkinsaf No, took out usb0 entry and it still didnt set the correct ip

Hi Boyzie, maybe you could run the figure 8 with voxl-tflite-server? Can you please share the serial number of your drone? We can try to find the calibration files What light is flashing? Can you share a video? If the unit needs to be reflashed, you should install the system image and then perform camera calibration

Hey @ahmed-mustahid, To clarify, the image in the gitlab repo is a bit outdated and you will no longer see these red and blue lines in voxl-portal, but rather one black line showing the RRT path. [image: 1665591998296-a86ad8c8-3ad5-497d-a106-8c6dd0445b0b-image.png] In terms of not receiving a path, I am unable to reproduce this issue naturally on my end. A trajectory will be shown in the UI as long as a solution is found, and the point you selected should also still be viewable within the map. The second image you shared does not show any of this, and the only way I was able to recreate this was by killing voxl-portal before selecting a point to plan to. Make sure you have an active connection to your drone, the network, and voxl-portal before attempting to use the path-planning capabilities of voxl-mapper.

@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