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.

@Kessie Excellent, glad to hear you got it working! And thanks for adding the details on what you had to do to the posting!

@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.

@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.

@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.

@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.

@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.

@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.

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.

@Alex-Kushleyev If I log the vehicle_imu topic within PX4 at full rate I see exactly the same distribution of timestamps.

@KLindgren Why do you think there are dropped messages? That is just the rate that the data is being produced within PX4. The Mavlink HIGHRES_IMU message is constructed based on the internal vehicle_imu topic which publishes at that rate. It is slower than the rate that IMU samples are being generated by the IMU driver.

@Steven-Girouard Are you using PX4? ArduPilot? You could run that directly on the VOXL 2 mini depending on what your IO needs are.

@Sam-Kiley No need for any voxl-io configuration. voxl-io-server is for use with PX4, not ArduPilot. The ArduPilot firmware will detect if there is a VOXL ESC connected or a VOXL 2 IO board connected. If it detects the IO board then you will have up to 8 channels of PWM available.

@ravi The documentation has been updated. If you are running a recent release from us then you will be using the ICP-20100 barometer. The BMP388 will not be started.

@ravi The ICP barometer should be working. The issues on the VOXL2 mini are related to temperature since it is on the same board as the Qualcomm device that creates a lot of heat on it's own so not applicable to flight core. Why do you say that it is not working? Is the sensor_baro topic being published? What software version do you have loaded on the flight core?

@psafi Unfortunately, the Mavlink module is not available on the DSP side. We tried it in the past and there were a lot of issues so we only have it on the apps side. You are welcome to try to add it into the DSP side and see how it goes.

@roy-crosthwaite Can you swap GPS units with the working one and verify that it fixes the issue?

@psafi I just built voxl-px4 with the lis3mdl driver and when I run it the command fails because it fails the probe (I don't have that magnetometer) but otherwise runs normally.

@psafi And how did you load your updated build to the VOXL 2?