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.

@Dan-Jennings Honestly, I don't think updating the SDK version will help this issue. But, we highly encourage everyone to be on the latest SDK, regardless, since that's where you'll get the latest fixes and features. And it's how you'll get the best support from us. but in this case I don't think a newer SDK will get you the battery_status. It's probably a hardware issue or a parameter issue. You swapped boards and that didn't help. What about the cable? Those 4 wire cables are notoriously fragile. Can you swap it out and see if that helps? The other item is parameters. You saw that other post about setting BATT_MONITOR to 21 and BATT_I2C_BUS to 1. If you don't see the BATT_I2C_BUS parameter then it must mean that BATT_MONITOR hasn't been set to 21. Make sure it is set to 21, then reboot, then you should see the BATT_I2C_BUS parameter. Then set it to 1, reboot, then you should see correct battery_status.

@Daehan-Won You would need to add the support to PX4 since you are using the DSP I2C pins and only PX4 can access those while it is running. There is some useful developer documentation here: https://docs.modalai.com/voxl-px4-dev-build-guide/. Also visit the PX4 documentation as well. At a high level you'll need to fork our repo, make a branch off of voxl-dev, add the driver to the default.px4board file for voxl2-slpi, build the image, and add a start command into the startup script voxl-px4-start

@minhthinh The params are in our voxl-px4-params repo. For example: https://gitlab.com/voxl-public/voxl-sdk/utilities/voxl-px4-params/-/blob/master/params/v1.13/Platforms/M500_FCV2.params?ref_type=heads

@Aniruddha Did you follow this guide: https://docs.px4.io/main/en/config/level_horizon_calibration

@Aniruddha Can you use level calibration in QGC instead? Are you saying that you are crashing after running voxl-calibrate-px4-horizon or in your attempt to run it? What flight mode are you using in your flight? If you fly in manual mode is everything okay?

@Daehan-Won The mb12xx px4 driver is not in our build so you would need to add it to the voxl2-slpi build. Which pins are you attaching it to on J19?

@Dan-Jennings I'm also guessing that the driver may not be detecting the hardware so is not able to get the data for the battery_status. Have you tried swapping some other hardware to see if the problem is associated with a particular unit?

@RyanH You don't need to fly the drone to get a log. Perhaps take off the props, arm it, throttle it up a few times, then disarm.

@RyanH I'll let another of my associates comment on the purchase of a new motor. But can you also share a px4 log file from such a flight. It would be helpful for us to take a look at it.

@Nikos-Mavr You're welcome! And can you please start a new forum post for this new issue? Thanks!