@Zachary-Lowell-0 after turning off open-vins and rebooting it works. thanks!

@rnunna at this point I would recommend either creating a python or cpp script that leverages mavsdk to probe the logs and get it into the format you are desiring.

Zach

@jared-upshaw the voxl mini also runs the flight stack, so ensure if you are leveraging the flight core v2 and plan on using the voxl2 mini purely for onboard compute, that you disable voxl-px4 on the voxl2 mini as to not get conflicting mavlink messages (serially connect the two over a uart)

As for camera setup, please find the link to the documentaiton on which cameras work with the voxl2 mini and how to wire them up!

https://docs.modalai.com/voxl2-mini-image-sensors/

@jmltt

Looks the same bug as here: https://github.com/PX4/PX4-Autopilot/issues/22148

Added the change from this commit and it looks like it works now: https://github.com/PX4/PX4-Autopilot/pull/22194/commits/38f3c711084b349cb9ed82cf44ff181c6a40738a

@Alex-Kushleyev Gotcha, thanks!

@Eric-Katzfey
Thanks Eric, building directly on the Voxl2 platform works.

Hello @Alex-Kushleyev ,

Thank you for your quick response!
I thought this might be the case, but I still wanted to confirm.

I appreciate your help with the matter.

@YUUJI-INOUE
I made a mistake in the file name
diagnostic_info

@leandro , documentation for M0187 has been updated to include the 3D CAD file :

https://docs.modalai.com/M0187/#3d-drawings

Alex

@Zachary-Lowell-0 thanks.

@minhthinh Documentation for the original VOXL Flight can be found here. The guide will link back to the original VOXL and the original Flight Core as those are the boards it was built around. You can also refer to the release notes of the previous sdks to see what was available in the specific release that you are using

Hi @rpowerscat ,

You may be looking for these?

https://docs.modalai.com/vtx-air-unit-datasheet/ https://docs.modalai.com/vrx-ground-unit-datasheet/

Will check availability and get back to you..

Alex

@Eric-Katzfey I updated to SDK 1.6.0, which fixed the power display issue. I was still getting no valid local position preflight fail, but after I ran apt update && apt upgrade, things seemed to work.

@Alex-Kushleyev
Thank you very much for your reply!

We bought the USB C adapter from Flir and followed your guide to enable MIPI. Now it works and I can get the video from the Boson over MIPI.

Thanks for your help!

I did some additional testing and was able to narrow things down a bit. After reconfiguring the WiFi as a SoftAP using voxl-wifi and then rebooting the VOXL, the network now shows up consistently again. So the broadcast issue seems to be resolved for the moment. However, the core problem remains: I still can’t actually connect to the AP — the connection attempt starts, prompts for the password, and then fails just like before.

If anyone has ideas on what else I could check or has seen similar behavior with this setup, I’d really appreciate the help.

@remill
You can also add a FetchContent CMake declaration that will build your library during compilation. Here is an example for yaml-cpp

include(FetchContent) # Fetch yaml-cpp from GitHub FetchContent_Declare( yaml-cpp GIT_REPOSITORY https://github.com/jbeder/yaml-cpp.git GIT_TAG yaml-cpp-0.6.3 ) # Disable yaml-cpp tests set(YAML_CPP_BUILD_TESTS OFF CACHE BOOL "" FORCE) set(YAML_BUILD_SHARED_LIBS ON CACHE BOOL "" FORCE) #cross 4.0 quits the chat if building static FetchContent_MakeAvailable(yaml-cpp) # Confirm target exists if (TARGET yaml-cpp) add_library(yaml-cpp::yaml-cpp ALIAS yaml-cpp) endif() install(FILES ${yaml-cpp_BINARY_DIR}/libyaml-cpp.so ${yaml-cpp_BINARY_DIR}/libyaml-cpp.so.0.6 ${yaml-cpp_BINARY_DIR}/libyaml-cpp.so.0.6.3 DESTINATION ${CMAKE_INSTALL_LIBDIR} )

To clarify, our current platforms are shipped with voxl-open-vins-server as the default VINS solution; however, QVIO is still available (SDK 1.6.2).

@jonathankampia ,

Here is something i tried, you can try as well. You are right, there is a background service that may be taking over, I think i found how to disable it:

systemctl disable QCMAP_ConnectionManagerd systemctl disable qti_pppd systemctl disable qtid rm /lib/systemd/system/multi-user.target.wants/QCMAP_ConnectionManagerd.service rm /lib/systemd/system/multi-user.target.wants/qti_pppd.service rm /lib/systemd/system/multi-user.target.wants/qtid.service #edit: instead of disabling the above 3 services and removing the entries from `multi-user.target.wants`, it seems you can do the following: systemctl mask QCMAP_ConnectionManagerd systemctl mask qti_pppd systemctl mask qtid # you may want to disable dhcpcd as well, but i dont think that is strictly necessary: systemctl disable dhcpcd

Now, set up static connection:

#create a new network interface file vi /etc/systemd/network/10-eth0.network [Match] Name=eth0 [Network] Address=192.168.xx.xx/24 Gateway=192.168.xx.1 DNS=8.8.8.8 1.1.1.1

enable networkd

systemctl enable systemd-networkd

Then reboot voxl2...

I think if dhcpcd is enabled, it may first take over the interface, but then networkd takes it back.. For example, here is the log from networkd when dhcpcd is enabled:

... Dec 10 06:01:00 m0054 systemd-networkd[1126]: dummy0: Gained carrier Dec 10 06:01:00 m0054 systemd-networkd[1126]: dummy0: Gained IPv6LL Dec 10 06:01:11 m0054 systemd-networkd[1126]: eth0: Gained carrier Dec 10 06:02:13 m0054 systemd-networkd[1126]: eth0: Gained IPv6LL Dec 10 06:02:13 m0054 systemd-networkd[1126]: eth0: Configured Dec 10 06:02:13 m0054 systemd-networkd[1126]: docker0: Link UP Dec 10 06:02:21 m0054 systemd-networkd[1126]: eth0: Lost carrier Dec 10 06:02:36 m0054 systemd-networkd[1126]: eth0: Gained carrier Dec 10 06:02:38 m0054 systemd-networkd[1126]: eth0: Gained IPv6LL Dec 10 06:02:38 m0054 systemd-networkd[1126]: eth0: Configured

and the log with dhcpcd disabled:

... Dec 10 06:02:13 m0054 systemd-networkd[1126]: bond0: Link is not managed by us Dec 10 06:02:13 m0054 systemd-networkd[1126]: sit0: Link is not managed by us Dec 10 06:02:14 m0054 systemd-networkd[1126]: eth0: Link UP Dec 10 06:02:38 m0054 systemd-networkd[1126]: eth0: Gained carrier Dec 10 06:09:56 m0054 systemd-networkd[1126]: eth0: Gained IPv6LL Dec 10 06:09:56 m0054 systemd-networkd[1126]: eth0: Configured Dec 10 06:09:56 m0054 systemd-networkd[1126]: docker0: Link UP

Can you try and see if that solves your issue?

Alex