Topics created by Philemon Benner

@Philemon-Benner Seems like some else had the same issue but there was no further investigation on the problem. https://forum.modalai.com/topic/2125/voxl-mavlink-server-external-fc-bus-error?_=1688565579723

@Chad-Sweet what is the reason for using Gralloc allocator on apq8096 for buffer allocation instead of ION memory allocator used in the qrb5165 implementation ?

@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

For any of our projects, there should be a LICENSE file in the root directory that dictates the terms of use.

Most of our software has a license that limits to use with ModalAI hardware. There are a few exceptions, like libmodal_pipe, which have different licenses for compatibility purposes.

You can see the license for libmodal_pipe here: https://gitlab.com/voxl-public/voxl-sdk/core-libs/libmodal-pipe/-/blob/master/LICENSE

@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

Ok i resolved the issue. You actually need to run voxl-mavlink-server and voxl-vision-px4 to get Autopilot enabled for Mavsdk.

@Matt-Turi Ah ok that sounds interesting might be worth a try. Good to know that. Thanks for the fast answer as always.

Hey @Philemon-Benner,

As of a few minutes ago, the latest voxl-tflite-server (v0.3.0) is now running with tensorflow v2.8.0 for apq8096. This means that you can now run any of the models that were included with qrb5165 on VOXL without dealing with these headaches. You can pull this from the dev apq8096 packages repo, or directly from here: http://voxl-packages.modalai.com/dists/apq8096/dev/binary-arm64/voxl-tflite-server_0.3.0_202207212215.ipk

@Philemon-Benner We build this as part of our Yocto system image build. It is 32 bit. We have not tried to build this outside of the Yocto build.

@Chad-Sweet Ok thanks for your time.

@Philemon-Benner No problem. But that's exactly why the decimator is there. It's often nicer to see lower frame rate with higher image quality.

Thank you for the Answer

@Alex-Gardner Thank you for the fast answer

Glad to hear someone's building our packages themselves!

Yes, we're most of the way through migrating to a more platform independent build system that will let us use these packages on the qrb5165 platform as well. This is one of the things we've had to change, the next voxl system image will have a tweak allowing these packages, but if you want to install them in the meantime, you can manually add the tweak by adding the line arch arm64 7 to /etc/opkg/arch.conf on your voxl and running opkg update

https://gitlab.com/voxl-public/voxl-sdk/services/voxl-portal/-/blob/master/src/video_manager.cpp#L77

Is an example of allocating a buffer and copying the frame into it. There are some other good examples in that file as well for processing frames and converting them to various formats within the callback. Hope that helps!

@Eric-Katzfey Ok thanks for the fast answer.

@Matt-Turi Thank you

@Philemon-Benner Our qrb5165 based platforms put 64 bit libraries into /usr/lib. On Voxl the 64 bit libraries go into /usr/lib64. So the 64 bit support is specifically for our qrb5165 based platforms (e.g. RB5 Flight).