@Jeremy-Frederick Thanks for reverting. In your setup do you have the Radio directly paired or connected with ground unit of the MH carrier without having to any other workarounds?

@Viktor-Gal I am troubling localization with QVIO. So I wanted to change vio algorithm to OpenVINS. I flashed my drone to nightly version but openvins still very unstable. Could you give me some guidance for openvins? Questions openvins configuration & versions Did you enable the voxl-feature-tracker? camera settings (single or multi, camera model, etc) My status voxl-suite: 1.4.1-202502132201 Camera: old-version of tracking camera (640x480) - link voxl-open-vins-server: 0.3.0-202502061726 voxl-feature-tracker: 0.5.2-202412171357

@Moderator said in Retrieving Apriltag offset from MAV local frame offset: We love incorporating merge requests if you do end up with something useful! Reply I've made a quick fix here for anyone looking for it, ill try to make a merge request/real fix for it soon https://github.com/Joe1Ontiveros/ApriltagPublisher_Starling

@modaltb As far as I can tell, I'm building a perf kernel. These are my changes: MODAL_REPO_BRANCH=v1.8.02 in bin/qrb5165-common.sh I've added the following lines to ./lu.um.1.2.1/apps_proc/poky/meta-voxl2-bsp/recipes-kernel/linux-msm/files/fragments/m005x.cfg: CONFIG_MACVLAN=y CONFIG_VLAN_8021Q=y And then building: ./qrb5165-build.sh -m M0054

@Eric-Katzfey Ahh that makes more sense, thankyou for explaining!

@Alex-Kushleyev Thank you, appreciate it!

Hello @Janelletran , Please reach out to https://www.modalai.com/pages/contact-us since the specific project details may need to be discussed directly via email. Alex Kushleyev

Hi @dew54 , Are you willing to share your schematic with us? We always perform a courtesy review of any customer design. What Alex said is true but there are some more subtle nuances because our Microhard design pre-dates Voxl 2. Everything was designed to be backwards compatible but a custom design can certainly step on some toes of the 5V network. Let us know if you are willing to share and we'll email you to exchange the Sch. Thanks!

@Gary-Holmgren I managed to finally get it working after flashing a few times with the web portal when the receiver and transmitter were in WiFi mode. It helped to connect instantaneously after flashing when making a binding phrase on both the receiver and transmitter.

@Gary-Holmgren Great to hear, new SDK release with that fix coming soon

@tom Thanks!

@ravi , sounds good. The updated opencv deb is the same that i posted a while ago, but i fixed a small issue related to installation of a symlink as part of deb install (which was mentioned in the other thread, i believe) Alex

@Gary-Holmgren , The esc driver in px4 receives data from a “mixer” module. There are different mixers for different vehicle types. It is possible that the mixer for your UGV vehicle type is not compiled for or not running on voxl2. Px4 support of these vehicle types is supposedly experimental, so additional investigation may be required on your end :). We have not tried the ground vehicle mixer. Alex

Hi @voxl-phoenix Yes, that M0177 flex you have plugs direct into the M0173 board 40-pin connector here: [image: 1738469389563-2a2a4f8f-6b90-4ea5-937e-d0b0426ccf36-image.png] Please pay attention to the "+" and "-" notes in silkscreen for proper orientation. Hope this helps! Thanks!

@RSAUser1 said in Sierra Modem not showing in Device Manager/wds errors: @tom I just heard back from Sierra wireless and they are stating this is an issue on your guys side. Not sure how to proceed. Any insight on the path forward is appreciated. Maybe if we can speak with you and Sierra wireless in a joint chat that would be easiest? Thanks. Sorry just want to add. We were able to get a connection to our emulator but only when the modem status shows: voxl2:/$ systemctl status -l voxl-modem ● voxl-modem.service - Modem Initialization Loaded: loaded (/etc/systemd/system/voxl-modem.service; enabled; vendor preset: enabled) Active: inactive (dead) Which seems to have confused me more. What we did was disable the vision-hub , just to allow another service to start (in theory) but then disabled modem, adb rebooted, enabled modem all while we were injecting the 5G signal (only band n5 works but handovers to supported bands do work). Any deviation from these steps does not work, like if we reboot then inspect-services or anything besides just enabling modem it will not connect. Is this because if the drone loses power or anything the first thing it needs to do is find the network (another theory)? Even if we are connected and turn of the 5G cell from our side and turn it back on the chipset does not reconnect and it looks like it is not trying to find a cell. Looks like this is on sierra wireless, is there anyway we can have a joint chat to troubleshoot this? Thanks!

@RSAUser1 yeah i'd probably pass to @tom . The modem is seems connected, otherwise you wouldnt see wwan0 come up. Once I had access to AT commands I ditched QMI which I think is more or less a wrapper for those commands anyway.