@Bilal-Hussain , can you please clarify: "if it's possible to step up voltage." - what do you mean? which voltage? Regarding maximum current per motor, the mini ESC can output continuous current at least 10A per channel at 15-16V input battery voltage (we tested at 15A+ with direct cooling from the propellers). The mini ESC is recommended for small drones 300-500g range or small fpv drones (300g). Maximum input voltage is 16.8V (4S LiPo). This ESC is very small, so when you are building a new drone, you should conduct tests to monitor the ESC temperature which should to stay below 80C. If you are exceeding that and getting close to 100C, it is a bad sign. The ESC should be rated to operate at least 110C but if you are getting that hot, it is a sign that something is wrong (motors are drawing too much current for the ESC or insufficient cooling). We typically use the mini ESC in the drone designs that use less than 5A per motor during hover and may reach up to 15A per motor at full thrust for some time. The ESC reports temperature via UART feedback and it is available in PX4 esc status message. We will update the current specifications in the datasheet (https://docs.modalai.com/voxl-mini-esc-datasheet/) Alex

@Darshit-Desai Hi Darshit, you will need to modify the code to support what you would like to achieve. If you'd like to mainline, we accept merge requests

If we are not able to resolve this soon, i would recommend replacing the ESC, you could then submit RMA form : https://www.modalai.com/pages/rma . In majority of cases, the scanning script should find the ESC even if it is missing firmware or params, so I am slightly confused why this is happening. It could be a hardware issue on the ESC. The ESC you have now is board version M0049, which is older than the current version of the ESC and is no longer in production. If you are going to request a replacement of the ESC, you will most likely receive M0134-1 which is just a newer revision (not really better or worse, the functionality is the same). https://www.modalai.com/products/voxl-esc In order to rule our the RB5 UART issues, if you are open to continuing to debug, i would recommend making an adapter using a USB-to-serial adapter and Hirose DF13 6-pin connector, then you could use voxl-esc tools on a PC and there is more flexibility in debugging. Please let me know if you would like to explore this option.

@Sravan-Parakala we have emailed you directly

@SMRazaRizvi We can only comment on what we have tested with and that is the Commando 8.

@leonardo-Andrade-0 It should be possible. Have you seen this https://docs.px4.io/main/en/config/flight_mode.html?

@SMRazaRizvi Issue resolved. I connected one of the camera ports in a wrong orientation.

@Alex-Kushleyev Alright, thanks.

@wetherbeej oh, yes.. that would do it. I was just going to ask about that. By the way we are working on some camera-specific tuning tuning files, should be coming soon. The default may result in image colors appearing a bit off. However, we don't have a tuning file ready for IMX678 just yet. If the current image quality is of a big concern, please let me know.

Hi @nickyblanch Anytime. yeah, we had quite a bit of cables and mods to get to FCv2, but we think it's worth it, and now much more aligned with Dronecode and present/future hardware we make. FCv1 was a bit of a anomaly from it's early design inputs and constraints, so we do view FCv2 as much easier now to work with (if you are starting from scratch). We do have on our roadmap a much more "standard" drone mounting pattern w/o changing any other functions, but that effort keeps moving to the right... haha

@Ethan-Wu Not sure about Ethernet. UVC is specific to USB.

@Moderator Perfect. Thanks.

Hi @andrea_seock That set of connections does appear to be correct now. Keep us posted!

@Riccardo-Franceschini We were not able to resolve this issue. However because our control stack is sending TRPY commands to mavros, this didn't come into play at all. The concern for us originated when the drone was taking off significantly higher than commanded. It turned out the propeller coefficients we received from ModalAI were insufficient.

@modaltb Great to know. I needed at least 2.1 to get layer support for RAUC. Which I hope ModalAI will support RAUC or SWUpdate out of the box at some point. Or another framework for OTA updates.

@Vinny Oh, thanks for the advice!

@Alex-Kushleyev No. This was a test for the RTK GPS. I'll try.

@Ariel-Saez Can you describe your hardware setup a bit more? Are you using voxl1 or voxl2? Are you using the Sierra 4G LTE add-on board?