@Alex-Kushleyev
Thank you so much for the detailed explanation!
I will keep you posted with the update shortly.

Hello @Alex-Kushleyev and @Moderator ,
Thank you for the response!!!

As Alex pointed out, the baud rate seems to be the issue preventing the motors from spinning through the Actuator Testing feature in QGC. I have another ESC configured with a 2M baud rate, and it works as expected with Actuator Testing.

My question now is: how can I update the baud rate on the ESC?

In QGC, the baud rate is already set to 2M.

In https://gitlab.com/voxl-public/voxl-sdk/utilities/voxl-esc/-/tree/master/voxl-esc-tools,
I came across the command:

./voxl-esc-upload-params.py --params-file ../params/esc_params_modalai_4_in_1.xml

However, I wasn’t able to locate this XML file on the VOXL.
Here's what I found in the VOXL:

In the repo I found is esc_params_modalai_4_in_1_revb_mn1804_2400kv_gemfan5040.xml
Should I upload this xml to /usr/share/modalai/voxl-esc-params/boards/, rename it to esc_params_modalai_4_in_1.xml, and use the python command above?

I also tried to manually change the baud rate to 2M in those XML files but it gets overwritten after a reboot.

Could you please provide more detailed instructions on how to properly update the ESC baud rate?

Thank you.

To whom it may concern,

My VOXL2 Flight Deck is currently running the following SDK version:

The ESC Mini 4-in-1 is using the following firmware version:

I am able to successfully spin the motors using the command:

voxl-esc 3) spin

However, I am unable to spin the motors in QGroundControl using the Actuator Testing feature.
Could you advise if there are any steps I might have missed?

====

Additionally, I have connected the VOXL2 to a QGC instance running on an Ubuntu machine within the same network.
I noticed that the ESC PWM Minimum and Maximum Calibration in QGC requires a USB connection.

I attempted to connect the VOXL2 to the Ubuntu machine via the USB-C port labeled "U" in the VOXL2 datasheet, but it did not establish a connection.

Could you clarify which port should be used for this USB connection to ensure proper calibration support in QGC?

Thank you for your assistance and please let me know if you need more details.

@Eric-Katzfey
Very sorry for the late response and thank you for pointing out the mavlink-router approach, https://github.com/mavlink-router/mavlink-router.
I will try it and keep you posted here.
Thank you for answering my quesiton.

Hello @Nathan-Raras and @Nathan-Raras ,

I don't see any Qualcomm device with running "lsusb".
I also have confirmed that the USB-C cable is able to access another VOXL device.
So I have submitted the RMA

Please let me know if any questions or suggestions.
Thank you very much for supporting.

Hello ModalAI Team,
Here is the HW and SDK info

• ModalAI Flight Deck M0054
• VOXL system image 1.8.02-M0054-14.1a-perf
• VOXL suite 1.4.1

Thank you.

Hello ModalAI Team,
If you need any additional information regarding the issue I’m currently experiencing, please don’t hesitate to let me know.
I appreciate your time and support on this matter.

Hello,
if you need any other information for this question,
please don't hesitate to let me know.
Thank you for helping!

To whom it may concern,

following this instruction to https://docs.modalai.com/voxl2-unbricking/

slide the SW2 switch into the ON position,

but in QDL Tool, it shows QDL device not connected.

I have confirmed that the USB-C cable works with other VOXL devices.

Any suggestions or anything I missed?

Thank you for your precious time on this.

Re: MAVLink custom port to GCS

Hello @Eric-Katzfey ,
is there any plan for ModalAI to support this request?
I am also interested in having this feature.
Thank you for your precious time on this matter.
Best,