There is a new module under development that allows you to pipe VGA (640x480) video from the hires camera at 30fps via MPA so that it can be streamed with voxl-streamer using RTSP while simultaneously saving 4k HD video at 30fps encoded as h265 into a file, preferably on the SD card on voxl. This module is now available in beta and will be officially released in upcoming releases of the voxl SDK for voxl, rb5-flight, and voxl 2. The beta package is available using wget https://storage.googleapis.com/modalai_public/modal_packages/archive/voxl-hires-server_0.0.1.ipk. It is meant for use on voxl only and is compatible with voxl platform release 3-3-0-0.5.0-a. In order to use it with voxl-camera-server, reconfigure voxl-camera-server to not use the hires camera. For example, call voxl-configure-cameras and choose option 1 Tracking + Stereo to allow voxl-camera-server to access the tracking and stereo cameras but not the hires camera. Then you can use voxl-hires-server for the hires camera. Use voxl-hires-server -h to see the available options. More documentation will be available upon official release of this new package.

@kitkatSG Yes, we have enabled most resolutions in that sensor now and are preparing a release to address this issue.

@JoeC Seems like it is an SD card issue. I was able to recreate the problem when using a SanDisk Extreme 32GB card. But when using a SanDisk Ultra 16GB card everything works fine.

@Andre-Moura Thanks for all of the testing! We really appreciate it, this is all great feedback! It seems that Holybro may have changed the default configuration of the units and that could be why it wasn't coming up properly.

@Hammas-Ali We have not tried either of those streaming protocols. Voxl is a Linux computer so it is likely that you can implement RTMP or DASH. voxl-streamer uses GStreamer so, if there are RTMP or DASH GStreamer elements available, it shouldn't be too hard to incorporate them.

@Sam-Kiley When on public 3G / 4G / 5G networks we use a VPN and assign fixed addresses to each system component with our VPN configuration. You should be able to do a similar thing with your 5G private network. Does your private network have a connection to the Internet or is it self contained? I don't know anything about 5G private networks but I'd be surprised if it didn't have a way to assign the same IP address to a device on the network so that you effectively have a static IP. Earlier versions of the RB5 SDK set the MAV_BROADCAST parameter in PX4 to 1 and PX4 would then use the network broadcast address to send out it's initial messages. Any QGC instance running on the network will receive that broadcast and respond so that you get automatic connection. However, this can be problematic if there are more than one instance of QGC running since you may connect to an instance that you don't want. Also, some wireless networks do not support broadcast.

An update to UVC camera support has been started. It will increase number of supported cameras by allowing MJPEG and will increase number of supported viewers including latest QGroundControl versions. Target availability is mid-December.

@Dan It's not really documented anywhere other than the source code. The best place to look is at the muorb module code. That is what implements the uorb communicator interface to allow advertisements, subscription requests, and topic data to flow between the DSP and the Linux side.

@JoeC SDK 1.1.1 is now available. Please use the installer in the voxl2_SDK_1.1.1.tar.gz archive to install this.

@Brendon There is a UART available to the apps processor on VOXL2 mini on connector J10. But by default this is shipped with the default configuration of that being a SPI port instead of a UART. So, we are looking into the best way to support switching modes between SPI and UART so that customers can choose what function to have on J10. In order to use a SLPI UART you won't be able to have PX4 running on VOXL2 mini.

@ejohnson01 You said you are running a modified version of voxl-px4. Does this problem still happen with the unmodified version of voxl-px4 that came with the SDK release?

@LucaVertiq Yep, that is correct.

@Jetson-Nano Do you have the new bootloader? The legacy bootloader (SDKs before 1.1.1) and the new firmware are not compatible, you won't be able to update the firmware on your Voxl2 IO using the legacy bootloader (it doesn't support flashing via UART). The new bootloader will enable firmware updates for Voxl2 IO board via Voxl2 (removing the need for STLink). We aren't currently distributing the new bootloader so you will need to send your Voxl2 IO back to us and we can send you replacement(s) with the new bootloader and firmware already loaded. You can email contact@modalai.com to get this process started.

@LucaVertiq Yes, you have a choice of where to put the driver depending on what UART port you are planning to use. If you use a UART available to the applications processor then you would use the standard voxl2 build. If you use a DSP UART then you would use the voxl2-slpi build.

@Anubhav The J19 ports are only mapped to the SLPI DSP. You cannot access them directly from the applications processors. Are you running PX4 on VOXL2? If not then you can use libqrb5165_io (https://gitlab.com/voxl-public/voxl-sdk/core-libs/libqrb5165-io) to access the SLPI DSP UARTs from the applications processors.

@Eric-Katzfey There is a new dev version of voxl-px4 located here: http://voxl-packages.modalai.com/dists/qrb5165/dev/binary-arm64/voxl-px4_1.14.0-2.0.61-202312011240_arm64.deb. Can you wget that and then load it on top of SDK 1.1.1? You can then modify the /etc/modalai/voxl-px4.conf file to specify RC=M0065_SBUS to use M0065 with SBUS. Once you restart you should have it working with M0065 SBUS. It has received very minimal testing at this point but you are welcome to give it a shot.

@dscott Unfortunately, we overlooked that particular configuration and it is not supported yet. We are looking at the best ways to support this configuration to try and get you something that you can use.

@JoeC Ah, yes, that is an excellent question! Rather than try to update the firmware in your existing voxl io board(s) we will send you new one(s) with the updated firmware. These new ones will also be upgradeable in the future. Contact us at http://modalai.com/contact to request your updated module(s).

@Jetson-Nano SDK 1.1.1 is now available. Please use the installer in the voxl2_SDK_1.1.1.tar.gz archive to install this. This should fix this issue.

@JoeC SDK 1.1.1 is now available. Please use the installer in the voxl2_SDK_1.1.1.tar.gz archive to install this.