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.

@jeremyrbrown5 Ah, yes, that'll do it.

@jeremyrbrown5 It doesn't look like there is any problem with the RC. The log shows the throttle stick being moved up. And it shows the motor actuators being set based on that throttle input. But, for some reason, the commands going to the ESC are all 0 so the motors don't spin. It kind of points to a configuration issue but I'm not able to see anything obviously wrong in the parameters. Which ESC are you using? Is this in a custom vehicle? Are you using any of the px4 parameter sets from the voxl-px4-params package?

@jeremyrbrown5 What type of RC are you using?

@jeremyrbrown5 Can you attach a px4 log?

@brandon Agreed, the code has a fixed port but should use the source port. We will fix that and also add configurable ports for the gcs IP addresses in the configuration file.

@Jetson-Nano Another thing you can do is attach an oscilloscope to the rx and tx lines of the UART. You may be able to sport obvious signal quality issues with that.

@Jetson-Nano It's best to try to determine what exactly is the cause first. If you determine that it is interference from a cable then the solution may be as simple as rerouting the cable. But you haven't determined for sure that EMI is even causing the issue. A good approach when designing a new vehicle is to first gather all of the electronic components and hook them together on a bench top as spread out from each other as possible and make sure that everything all works before trying to mount them inside the drone.

@emarcphera Huh, interesting. Okay, thanks for posting the update!

@ndwe -z in the voxl-logger command, not the voxl-replay command. But looks like voxl-replay sees the data and there is a raw data file for it to parse. Are you still having an issue?

@emarcphera I cannot reproduce the issue with v1.14.0-2.0.94 nor one of our most recent builds v1.14.0-2.0.105.