Hello @Vinny

After checking with my coworkers, we confirmed that the Doodle Nano radio receives 5 V power through its connection to the ModalAI ESC, not as I previously described. Sorry for the earlier confusion.

Does this clarification help you suggest the next step we can take for verification?

We also refreshed the SDK on the VOXL2, but the issue persists, so we can likely rule out software as a potential root cause.

Looking forward to hearing from you. Please let me know if any further questions.

Hello @Vinny
thank you for the clear guidance and I will keep you posted after our experiment.

Hello @Vinny
thank you for the response.

I understand and appreciate your point about the incorrect power configuration,
and we will definitely work on addressing that.

However,
the same board with the same Doodle Nano works properly on other VOXL2 units.
This suggests that even with the incorrect power, the Doodle Nano remains functional and can still communicate with other Doodle Nano devices.

For this reason, we’d like to investigate whether the J port itself is still functioning.
Could you suggest any methods we can use in our lab to verify if the J port on this particular VOXL2 is operational?
Or besides the power configuration part, any other spec you would recommend we investigate?

@tom
Thank you for the quick response.
However,
it doesn't explain why the same board with the same doodle lab nano radio works with the VOXL 2 previously ( just suddenly doesn't work anymore ) and work with other VOXL 2.

And
we are using
https://techlibrary.doodlelabs.com/doodle-labs-nano-oem-mesh-rider-radio-24002482-mhz

It doesn't require that much power

please let me know if any misunderstanding, any suggestion, or any command/method we can use to verify the J port
Thank you.

@tom

we use this board
https://www.modalai.com/products/m0151?variant=47083939791152
with the Doodle lab nano radio
https://doodlelabs.com/product/nano-mesh-rider-radio/

Thank you for the quick response and please let me know if any further quesitons.

To whom it may concern,

Is there a command or diagnostic procedure to verify the operational status of the J port on a VOXL2?

Details:
We have integrated a board that includes a radio device with the VOXL2 via the J port. Initially, the VOXL2 detected the connection and the interface appeared as eth0. However, this VOXL2 has since stopped recognizing the connection. When the same board and radio device are tested with a different VOXL2, the connection is detected normally, which suggests the problem is isolated to this particular unit.

Could you advise on tools, commands, or logs that can be used to determine whether the J port hardware or the associated network interface on this VOXL2 is functioning correctly?

Please let me know if you need more details or questions
Thank you.

@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.