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.

Best posts made by Eric Katzfey
-
How to stream hires camera at VGA resolution and simultaneously capture 4k30 to a file
-
RE: Streaming 4K video from Qualcomm RB5 drone
@kitkatSG Yes, we have enabled most resolutions in that sensor now and are preparing a release to address this issue.
-
RE: Ardupilot : connection with Mission Planner
@Kessie Excellent, glad to hear you got it working! And thanks for adding the details on what you had to do to the posting!
-
RE: having trouble using docker on the sdcard
@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.
-
RE: Maximum I2C Clock Frequency
@Morten-Nissov 1MHz is a supported clock rate for i2c on the DSP based on what I can see in the code. But we have never tried running a device at 1MHz on i2c so it's tough to say why it wouldn't be working for you.
-
RE: VOXL2 I2C access from FC
@ceu-gomez PX4 on VOXL2 is composed of two separate applications. One is on the applications processor (running Ubuntu) and the other is on the DSP (running Qurt RTOS). They use the muorb module to communicate topic data back and forth. The spare i2c on J19 is mapped to the DSP, not the applications processor, so Ubuntu has no access to it. To gain access to it on Ubuntu side with PX4 running would require some new code. This is something that is on our development roadmap but no definitive answer on when we will be able to get to it.
-
RE: voxl-tag-detector fails to start on V3.3 "Missing lens_cal_file"
@PawelJ Bear with us. Our subject matter experts are out on summer vacation this week.
-
RE: ModalAI uORB topic file handle location
@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.
-
RE: VOXL2: Adjusting bandwith of video streaming
@Curious By default the voxl-streamer application assumes a wireless link. But you can change the configuration as needed. See https://docs.modalai.com/voxl-streamer/
-
RE: voxl-streamer client repetitive connect/disconnect
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.
-
RE: Custom px4-firmware build on StarlingV2
@smilon Yes, in order to build you can follow the README in the voxl-px4 project. The Docker provides the build environment so you need to use it.
-
RE: ModalAI uORB topic file handle location
@Dan You have to look for the definition of the px4_open function. On Nuttx it is defined as the OS open function. Otherwise it is defined as an external function. Look at src/lib/cdev/posix/cdev_platform.cpp
-
RE: voxl-streamer client repetitive connect/disconnect
@wilkinsaf The configuration file for voxl-streamer is documented here: https://docs.modalai.com/voxl-streamer/#configuration-file-format
-
RE: Voxl 2 SDK 1.1.1
@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.
-
RE: Is there an on board way to access DSP logs?
@Aidan-Dempster The PX4 messages from the DSP side are sent over to the applications processor side to be displayed along with the PX4 messages generated on the applications processor side. The ones from the DSP side are prefixed with the
[SLPI]
tag. -
RE: voxl-streamer client repetitive connect/disconnect
@wilkinsaf The configuration for voxl-camera-server is discussed here: https://docs.modalai.com/voxl-camera-server/#configuration
-
RE: Voxl 2 mini UARTs from Linux
@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.