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.

Hi @jcai , I am not sure about this one.. If a higher kernel version is required and the existing driver does not actually work, then maybe it is not a big surprise! the kernel module is in the build, as specified in the config file here : https://gitlab.com/voxl-public/system-image-build/qrb5165-kernel/-/blob/qrb5165-ubun1.0-14.1a/arch/arm64/configs/vendor/kona-perf_defconfig#L328 Some info about the driver : https://gitlab.com/voxl-public/system-image-build/qrb5165-kernel/-/blob/qrb5165-ubun1.0-14.1a/arch/arm64/boot/dts/vendor/bindings/net/microchip,lan78xx.txt You could try to pull source code from updated driver for this device from a newer kernel, drop it into the voxl2 kernel build and build the kernel with new driver. I think some users on this forum were able to do something similar with another device (not ethernet adapter). Maybe try another ethernet adapter? For example, voxl2-mini:/$ lsusb -t /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 10000M |__ Port 1: Dev 2, If 0, Class=Vendor Specific Class, Driver=ax88179_178a, 5000M voxl2-mini:/$ ethtool eth0 Settings for eth0: Supported ports: [ TP MII ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Half 1000baseT/Full ... Speed: 1000Mb/s Duplex: Full ... voxl2-mini:/$ iperf -c <my desktop machine ip> ------------------------------------------------------------ Client connecting to <my desktop machine ip>, TCP port 5001 TCP window size: 85.0 KByte (default) ------------------------------------------------------------ [ 3] local <my voxl2 local ip> port 52708 connected with <my desktop machine ip> port 5001 [ ID] Interval Transfer Bandwidth [ 3] 0.0-10.0 sec 339 MBytes 284 Mbits/sec Did not quite get 1 gig (about 300Mbit/s), maybe there is a bottleneck somewhere, but maybe that will work for you.. Alex

@KnightHawk06 , please upgrade your VOXL2 SDK, as you have very old release, you can get the latest SDK 1.4.0 and then configure your cameras. https://docs.modalai.com/sdk-1.4-release-notes/ After installing latest SDK and configuring cameras, confirm via ADB shell that camera server is getting camera data: #this test app will subscribe to all camera streams and report stream resolution, fps, etc #please note that this test can put unnecessary stress on the system because it will stream ALL the possible camera streams, so normally you would not run this test all the time voxl-inspect-cam -a after that, if you want to view the camera stream using voxl-portal but you do not have internet connection, you can do that using adb port forwarding trick : https://docs.modalai.com/voxl-portal-via-adb/ Let us know if you have any other questions. Alex

@Alex-Kushleyev The new board works well now after updating the firmware. We'll also update the original board soon and see if that resolves the issue with it, too. Thanks for your help!

@bendraper Mini can get power via USB so it's not out of the question

@JP-Drone , Please try to upgrade to latest voxl-portal version from here : http://voxl-packages.modalai.com/dists/qrb5165/dev/binary-arm64// I just tested on iphone displaying individual and multi view, it works. What camera feed are you selecting (name)? The non "encoded" feeds are compressed to mjpeg format which should play on majority of browsers. I will check regarding the video recording feature in voxl-portal. Alex

@mkriesel Great, thanks for the update