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.

@nickanick Also, you can run voxl-mavlink-server with some of the debug options which will show you which packets are coming in and going out.

@nickanick What is the IP of the computer running QGC? Can you ping the VOXL2 from that computer? Can you see the Mavlink heartbeat packets on that computer with tcpdump or other protocol analyzer when you setup the QGC connection?

@Mustafa_Cayci Yes, you can run ROS2 and OpenCV on a VOXL2. Can you give more details about the RFID reader? What type of I/O does it use? What type of software interfaces with the reader?

@PatkirkMartin Mavlink over a DSP mapped UART won't work. However, if you have an accessory board with an apps processor UART available then you should be able to configure that to work with Mavlink.

@Hector-Gutierrez Well, I'm happy that worked, but you shouldn't have to disable voxl-vision-hub like that. I only suggested that as a debug step. We'll take a look and see if we can reproduce the error and come up with a better solution.

@Hector-Gutierrez What calibration step is not working? Are you running any custom software, like ROS or MAVSDK based applications? If you disable voxl-vision-hub does the error go away?

@bschulzhf PX4 will only correct incoming messages. Something external will have to also run TIMESYNC with PX4 to estimate the offset and correct and incoming PX4 message timestamps that it wants to align. voxl-mavlink-server does this for a few messages.

@nickanick That was what I responded with previously. Did that documentation not address your question?

@nickanick It's best if you ask each question in a separate post. For QGC over the ADB USB: https://docs.modalai.com/qgc-via-adb/

@jon You can use a J19 UART from the apps processor. Take a look at the code in voxl-elrs (https://gitlab.com/voxl-public/voxl-sdk/utilities/voxl-elrs/-/tree/dev?ref_type=heads), specifically the file src/elrs_slpi.c. This project accesses SLPI UARTs from an AP userspace process through voxl_io, not through POSIX termios. You cannot have a flight controller running at the same time though so PX4 / ArduPilot / etc. would need to be stopped first.