@Alex-Kushleyev , I think that is plenty for now. We will order a couple and test them. Thanks a lot!

@Vinny , Thanks for the speedy response and for the recommendations. I will discuss the options with my team. That dongle sounds like a good alternative for this use case. Jacob

@MChehadeh yeah it is simply 1/1024. Powers of 2 for faster calculations Integral is scaled down a lot because it accumulates fast at 10khz update rate

@MChehadeh , thank you for being flexible

Hi @Jetson-Nano, we only support flashing the 915Mhz BetaFPV Nano Rx via voxl2. You will need to follow the instructions on the ELRS website to flash the 2.4G RX that you have, search on this quickstart page in the receivers section and follow the instructions for your particular rx. You can download the ELRS configurator which is the tool provided by ELRS for flashing transmitters and receivers. -Jacob

@Abdullah01 , the original issue was that ESC calibration was actually done without propellers mounted, you can see the current at 94% power was very small, 0.4A However, the script still produced the a0, a1, a2 parameters (which would have been wrong to use because calibration was done without a propeller..) The error at the end was a result of attempted plot - since voxl2 does not have a display attached, the plot failed. Since that version, we have transitioned to using plotly for plotting, and calibration plots are saved to disk in addition to attempt to plot it to display. The plot feature was updated after SDK 1.1.2 release, but you can get it directly from gitlab here : https://gitlab.com/voxl-public/voxl-sdk/utilities/voxl-esc/-/blob/dev/voxl-esc-tools/voxl-esc-calibrate.py (just get the whole voxl-esc repo from dev branch on your voxl2 and run the calibration procedure). Meanwhile, we will add additional checking of the calibration to catch the conditions that do not look like proper calibration (when propeller is not mounted, etc..).

@Jeremy-Frederick Can you try to lower the bitrate or resolution to see if it's a bandwidth issue? I understand that, in theory, the rendering software (VLC or QGC) shouldn't matter for your issue. But, it typically helps to see if there is a config that will work reliably and then push it from there.

@Alex-Kushleyev I ran voxl-configure-mpa and was able to get the ESC to function again. Of course it caused other issues due to resetting files and params so I am now trying to work through setting everything back up. Im not sure what would have caused the mpa to need to be reconfigured because I had just done that obviously with the flash of SDK 1.1.2.

@Matthew-Wellner FYI

We do not have a clean solution for this combination of parts since VOXL 2 Mini does not have a 5V power module. The approach will be "clunky" at best at the moment by using an additional 5V power source somewhere in your system. When our Voxl2 dedicated version of the new ToF adapter is ready (M0171) we should have better integration to support at least 1 ToF module using our on-board 5V regulator, but it will be limited to only 1 ToF, and may prevent high-current USB use cases. Once we have the working solution(s), we can explain better. Please stay tuned. Thanks!

@tom When running our algorithm or doing voxl-streaming while connected to a microhard, the drone is experiencing a random reboot. This issue is difficult to see when connected via wifi (station mode). When the drone reboots, it is disconnected from qgc and reconnected to qgc about 1 minute later. I think they had the same problem, can you tell me how they solved it?

You can add Boson via USB, but no more MIPI-CSI image sensors would be supported. You could use USB on a hub for the other high-res camera

@hanzichi , esc_status in px4 would contain individual current for each ESC and since this is not possible to measure on the mini ESC, the esc_status message does not contain any current measurements. So the total current goes into the Battery Status message. Please make sure you enable publishing of battery status in the voxl-esc driver here : param_get(param_find("VOXL_ESC_PUB_BST"), &params->publish_battery_status); and the status is published here

@AP123 please contact us before testing a replacement ESC - we need to figure out what happened and prevent such failure in the future. I am working on enabling thermal protection on the ESC, which will reduce power and shut off ESC in order to prevent catching on fire. Before you test again, I would like you to use the updated firmware with such protection. Thank you Alex

HI @AP123, you can find information about calibration for M0134 here. The calibration procedure in voxl2_io driver in voxl-px4 is not designed to work with 4 in 1 ESC, it is for off the shelf ESCs such as BLHeli. Additional information about if you need to calibrate your 4 in 1 ESC can be found in this repo. I believe we already provide parameters (calibration) for 4 in 1 ESC for certain motor/propeller combinations which can be loaded via voxl-esc utility on voxl2. From tech docs: Q: When is ESC Calibration Required? A: When switching battery types (from 3S LiPo to 4S LiPo, etc), or when a new type of motor or new type of propeller is used.

@Will , this is great to hear! Thank you for your patience as we are resolving this issue. It does sound like you are ready for flight testing. Meanwhile we will continue testing of the fix and will release an official firmware update to resolve the issue soon (probably this week). However, you don't need to wait for it, the test firmware you already have should be sufficient. If you run into any other ESC-related issues, please let us know! Alex

I will continue to use HDMI to USB: https://www.amazon.com/gp/product/B097D5CJ4T/ref=ppx_yo_dt_b_search_asin_title?ie=UTF8&psc=1

@Chase-Riley this is most likely a hardware / cabling issue. Often cables are plugged in backwards or not fully seated