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

@bendraper We use Google Fi data SIMs for all of our testing

@paynej Hi, I know this is very old topic. Did you manage to find a solution (or reason) yet?

@Mohammad-Goli I had a really hard time building it. This is basically what I did: [image: 1737588525707-mavsdk.png] I had to manually build it. After that, I just followed the instructions and this is what I got, but I found an error at the end. [image: 1737588622237-mavsdk2.png] I had to use this command to be able to import the image: cat /data/tmp/voxl-mavsdk:v1.2.tar.gz | docker import - voxl-mavsdk:v1.2 But now I can't run it. Hopefully, someone on here can help with this.

@bkim1301 I would start by connecting the VOXL 2 UART 7 to a PC with a serial to USB cable. Make sure you can communicate back and forth using that setup and then do the same with the Teensy before connecting the Teensy and the VOXL 2 together. It's often very helpful to use an oscilloscope on the rx / tx lines to verify that there is actually data flowing.

@Zachary-Lowell-0 I am not sure how I resolved this, but as far as I remember there was px4_msgs versioning issue where I wasn't using either the correct ones or something

@Jetson-Nano Instead of listening to the input_rc topic with the listener function you can now monitor the RC_CHANNELS Mavlink message from the FC v2.

Unsure, if you have resolved this so I am going to attempt to help but I am going to need more information if possible. I am unsure how the setup is for the drone seems like you have one camera (Tracking_rear) pointed straight backwards and two cameras (Tracking_front, Tracking_down) facing forward at a 30 degree downward angle? I am not sure that you are showing with the log output. Have you tried hand testing using the command voxl-inspect-pose -l and seeing how RPY and translational movement (moving the drone up, right, forward) are behaving for the local frame?

@Jacob-Camarillo @wilkinsaf Hi guys, I tested turtle mode out with internal FC and it is working. Now I have updated the system with Flight core V2 external FC, and I would like to achieve the same with this configuration. could you help me out here. Since we can not use px4-listener anymore. I am bit confused with what approach to go take.

@Kessie Not exactly, but the important data to retain lives in /data/ or /data/modalai The SDK flash will attempt to retain this partition, but in certain cases it requires a wipe. I would take note of /data/modalai/sku.txt as well as pull off any calibration files in /data/modalai, you can see if you have any onboard currently by running voxl-check-calibration If you have this data saved you'll have no issue getting back to your previous state, I can help guide you through it if you run into any issues.

@czarsimon When you run through the QDL process how long does it take for the flash to finish? seconds? minutes? Also, are you able to ADB onto functional devices on this machine? Want to rule it weird permission issues

@Jia-Wan Yes, you should be able to do your testing with SITL before trying it on Starling.