@Chad-Sweet @modaltb what should be the fcu url for the updated mavlink server for mavros connection? Please help me to fix this

I believe you first need to enable SFTP functionality in ssh server on the drone, for example https://www.pcwdld.com/setup-sftp-server-on-ubuntu seems to provide instructions (i did not verify the correctness of the instructions). A better solution, in my opinion, would be to use scp from your python client. You can copy the ssh key directly to the drone, so you don't have to enter the password in the script. Then you could call the scp command directly from Python using a system call or using Paramiko like in this example : https://stackoverflow.com/questions/250283/how-to-scp-in-python . Installing the ssh key on the drone will avoid storing plain text password on your PC. Is there a reason why you are trying SFTP instead of SCP?

@Chad-Sweet thank you

switch to wifi station mode - https://docs.modalai.com/wifi-setup/ It fixed for me

Each service is using MPA, so there are many pipes going at any given time. With two TOF, you are likely overheating the CPU Do you have airflow on the board? Are you using voxl-inspect-cpu to monitor how hot you are getting the CPU?

Apologies. I actually have the simulator running on ROS1 Melodic.

Hi, would there be any way to classify the feature points used for QVIO based on some metric so that voxl could be able to handle points that are from reflected surfaces. I mean there could be some variable that measures the feature point as a potential point from reflection.

With regards to camera server, the "types" that it takes define behavior more than actual reading of drivers. The underlying camera layer will deal with the actual querying of the sensor and using those drivers that you've posted, and the type in the camera server config file will define a few behaviors like resolutions, image format, allowable streams, etc, some of which are customizable in the config file. The imx214 type in there is named as such because initially that was the only imx sensor that we used, and its behavior is applicable to (at the very least that we've tested) the 377 and 412 as well; and would likely work on some of the others that you've mentioned.

The pipes that voxl-camera-server publishes should be accessible in a Docker. You should be able to access them that way inside of a Docker. A voxl-mpa-to-ros2 service would be a good addition, we don't have that implemented yet.

You can find the code for that TensorFlow Lite build here https://gitlab.com/voxl-public/voxl-sdk/third-party/qrb5165-tflite There are just few patches applied to get it to build correctly. You could try rebasing it to 2.11

With the updates to this page (specifically running the setup script voxl-configure-docker-support), this issue is resolved. Thank you @Chad-Sweet for updating the page!

Would love a solution to this too, having the same problem

@tom Now it's working again, but might be worth a look, it's important that it always works. Parsing seems fine: apq8096 detected... 'v2' len: 2 Initializing v2 modem... Waiting for ttyUSB2... ttyUSB2

@marian Oh yes, thanks for letting us know. When you are using raw frames over USB 2.0 you have to go to a much lower frame rate or else there isn't enough bandwidth to transfer them.

@modaltb Any suggestion ?

@Chad-Sweet Great, very exciting!

@Philemon-Benner This is where the voxl-wifi source code lives for VOXL1: https://gitlab.com/voxl-public/voxl-sdk/utilities/apq8096-system-tweaks/-/blob/dev/scripts/voxl-wifi Since you've already put in effort toward the resolution you could attempt to fork this repo, make your suggested tweaks and create a merge request so that the team could take a look! Otherwise it may take a little bit longer for the team to take a chance to look into the bug

@Eric-Katzfey OK good to know. Thanks for looking into that. Is there a good email I can reach out to discuss further with you?

Hi @Nishkala , With the warning that I've not yet tried in python but I'm sure it will work This is the source code for our voxl-inspect-qvio tool, and from there we can see it's looking for a pipe QVIO_EXTENDED_LOCATION https://gitlab.com/voxl-public/voxl-sdk/services/voxl-qvio-server/-/blob/master/clients/voxl-inspect-qvio.c#L51 That's defined here: https://gitlab.com/voxl-public/voxl-sdk/services/voxl-qvio-server/-/blob/master/common/voxl_qvio_server.h#L64 The other place to look for defines is in libmodal-pipe: https://gitlab.com/voxl-public/voxl-sdk/core-libs/libmodal-pipe/-/blob/master/library/include This is where the inspect tool consumes data: https://gitlab.com/voxl-public/voxl-sdk/services/voxl-qvio-server/-/blob/master/clients/voxl-inspect-qvio.c#L259 Here's where we parse and print the info: https://gitlab.com/voxl-public/voxl-sdk/services/voxl-qvio-server/-/blob/master/clients/voxl-inspect-qvio.c#L184