Topics created by psafi

@psafi ,

There was a libmodal-pipe library update earlier this week, so if you have updated that library on your VOXL2, then any other library or app (which uses libmodal-pipe) that you deploy to that VOXL2 needs to be built against the same version of libmodal-pipe.

So if you want use the latest dev version, you would update the drone.

make sure you are using dev for apt sources:
in /etc/apt/sources.list.d/modalai.list:

deb [trusted=yes] http://voxl-packages.modalai.com/ ./dists/qrb5165/dev/binary-arm64/

then update libmodal-pipe on VOXL2, this should also update any other packages that depend on it.

apt update apt install libmodal-pipe

When building your application using voxl-cross docker, make sure you run the following in order to get the latest deps from dev:

./install_build_deps.sh qrb5165 dev

Most of the time you can get away not doing this, but this time there was an interface change in libmodal-pipe, so a mismatch occurred.

Alex

@psafi the html file is saved in the same folder where you run voxl-esc-spin* scripts if you have --enable-plot 1 . on VOXL2, the plot wont show up on screen, since there is no screen attached to VOXL2 (which would work on a linux pc), but it will be saved to html. In order to save to html, you will need to have plotly installed. You may first need to install pip3

apt update apt install python3-pip pip3 install plotly --upgrade

Alex

@Alex-Kushleyev Ok great. Thanks.
One more question, to configure VIO/QVIO for a custom frame with a single (downward) camera, how should I go about following the documentations?

I am starting with https://docs.modalai.com/open-vins/

However I came across this:
"This documentaion will assume that there are some steps that have already be taken. ...Assuming that we are working with between two and three camera tracking."

are there different procedures for a system with single camera? Also a high-level roadmap on how to go about configuring VIO/QVIO for a custom frame would be appreciated in case information is in multiple places in documentation. Thank you for your support.

@psafi Unfortunately, the Mavlink module is not available on the DSP side. We tried it in the past and there were a lot of issues so we only have it on the apps side. You are welcome to try to add it into the DSP side and see how it goes.

@psafi In this case we don't use voxl-mavlink-server directly because we are essentially setting up a "mavlink device" straight into px4.