@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

@Moderator Much appreciated !

@Kyuhyong-You I think they want you to use an external flight control for all that stuff.

@Moderator Apologies for the lack of clarity. It's mentioned in an earlier version of the SDK (pre SDK 0.9.5), here in fact: https://docs.modalai.com/voxl-camera-server-0_9/ (search for "flip"). I added "flip" to the .conf file, but it didn't have an effect it seems. I haven't checked out 1.0 or 1.1 yet (I'm holding off on going past 0.9.5 until VOXL IO board is supported) but I'm hoping such basic image manipulation is available in those versions as well.

@RykerBarthold OV9782 is definitely supported on VOXL 2

@Jeremy-Frederick I would look at this being a radio thing. I would try get some distance between the radios. if they are too close together there might be too much noise in the system monitor the radio health when you see the cut out (should be able to see that from the menu of microhard 192.168.168.2) see if this happens if you connect over straight ethernet (use this cable: https://www.amazon.com/USB-Ethernet-Adapter-Gigabit-Switch/dp/B09GRL3VCN/ref=sr_1_2_sspa?crid=1ZBIC6DOI8DB5&keywords=ethernet+to+usb+adapter&qid=1699997723&sprefix=ehternet+to+usb%2Caps%2C124&sr=8-2-spons&sp_csd=d2lkZ2V0TmFtZT1zcF9hdGY&psc=1). If you dont see the issue, i would look closer into how the radios are configured antennas: make sure you have the right radio antennas suggested by microhard

@Jetson-Nano hello! which tutorial are you referring to?

Hi @Sonoaero That is a valid electrical connection scheme. If you plug into either J6 or J7 of V2 Mini, you'll match the configuration shown here: https://docs.modalai.com/voxl2-mini-image-sensors/#tracking Keeping in mind M0076 only picks up the "lower" CSI group functions. I cannot advise as to how SW will work on this config switching from M0014 (OV7251) to M0113 (OV9782), but it is valid electrically. Hope this helps. Thanks!

@AP123 I'm guessing that voxl-px4 is running and the voxl-esc commands are not able to stop it. You can try to do this manually. Run systemctl disable voxl-px4 and then reboot. You should then be able to use the voxl-esc tools. After you are done use systemctl enable voxl-px4 to get voxl-px4 on auto start again.