Posts made by Jetson Nano

Jetson Nano

Hello @Alex-Kushleyev and @Eric-Katzfey,

I hope you are doing well.

I recently came across the updates regarding the M0189 VOXL 2 Mini ToF sensor, and I am interested in evaluating it for integration into our UAV platform based on VOXL2 mini.

We are currently planning to work on VOXL2 mini-based system and are exploring additional sensing solutions for obstacle detection, terrain following, and navigation-related applications. The Mini ToF sensor appears to be a promising option, and I would like to gather some additional information regarding its integration and availability.

Could you please provide guidance on the following:

Integration Guidelines
- Recommended hardware connections and interfacing requirements with VOXL2 mini.
- Software and SDK support available for the sensor.
- Any required drivers, services, or configuration steps within the VOXL SDK.
- Best practices for mounting, calibration, and deployment on UAV platforms.
- Available documentation, reference designs, or example projects demonstrating integration with VOXL2 mini.
Sensor Performance and Use Cases

*Typical operating range and field-of-view specifications.
- Expected performance in outdoor environments and varying lighting conditions.
- Any known limitations or considerations for autonomous flight applications.
- Whether the Mini ToF sensor provides 2D ranging data (single-point or multi-zone distance measurements) or a 3D depth map / point cloud output. If 3D depth information is available, could you please provide details regarding the depth resolution, output format, field of view, and any supported visualization or processing tools within the VOXL ecosystem?
Availability and Purchasing
- Current availability status of the M0189 VOXL 2 Mini ToF sensor board.
- Recommended purchasing channels and lead times.
- Whether the sensor is available as a standalone module or requires additional interface hardware.

We are currently evaluating sensors for integration into our UAV platform and would appreciate any documentation, recommendations, or resources that could help us better understand the capabilities and integration process of the Mini ToF sensor with VOXL2 mini.

Thank you for your time and support.

I look forward to your guidance.

Jetson Nano

Hello @Alex-Kushleyev and @Eric-Katzfey,

I have a few questions regarding the integration of third-party communication modules with the VOXL2 platform.

We are currently using VOXL2 in our UAV and would like to integrate third-party radio and video transmission systems.

Radio Integration

We are considering using the Silvus StreamCaster Lite 5200 as the air-side radio. Could you please let us know:

Whether the VOXL2 system is compatible with the Silvus StreamCaster Lite 5200.
If there are any recommended integration guidelines, interfaces, configuration requirements, or best practices for using this radio with VOXL2.

Video Transmission (VTX) Integration

We would also like to integrate a third-party video transmission system while continuing to use the camera configuration available on VOXL2.

Could you please advise:

Whether VOXL2 supports integration with third-party VTX systems.
If there are any recommended or validated VTX solutions that are known to work well with VOXL2.
Any available documentation or integration guidelines for such configurations.

We would appreciate any recommendations or references that could help us evaluate these options for our current system configuration.

Thank you for your support and guidance.

Jetson Nano

@Alex-Kushleyev @Eric-Katzfey @Vinny @modaltb
Hi guys,
I had some queries regarding VOXL 2 MINI, ESC, camera break out board and flight core v2

Is Doodle Lab module compatible with the companion board, any additional board required?
Is there any way I can connect ARK optical flow to the voxl 2 mini?
I saw the camera breakout board comes with and without barometer, under what conditions does it help?
Is the VOXL ESC 4 in 1 mini with built in power module, handle a 1.5 kg drone?
I realized the flight core v2 is EOL, are you guys releasing new version?

Thank you for your time. Looking forward to hearing from you guys.

Jetson Nano

@Sean-Hickey

I tested with this firmware modalai_fc-v2_1.14.0-2.0.133.px4 from (http://voxl-packages.modalai.com/dists/fc-v2/sdk-1.6/ ) and it worked, but there is no uavcan thats the only problem.

I checked with the parameters you mentioned.

When i reduce the cp_dist it stops working but with 1.5 m it is working.

Jetson Nano

@Sean-Hickey
sorry to disturb you again .
I am not able to flash with the deb file, could you please share the .px4 file

Jetson Nano

@Eric-Katzfey UAVCAN is working in the latest versions, when enabled. And yes I meant heading error, thats my mistake.
The collision prevention is the major issue I am having.
The heading error is in the latest version, and I also came across it in the issues section and it was shown solved, but I did not test it out still with VIO, I was testing with only Optical flow and it was not working.

Jetson Nano

@Sean-Hickey
I already checked with changing the MPC_POS_MODE, did not work.

Could you share the file, I would like to test it out.

Jetson Nano

@Sean-Hickey that great, just making sure, did you use optical flow with FC?

Also could you let me know which branch you used, or the Px4 built file. i want to test it out in my setup.

Jetson Nano

@Sean-Hickey I am using M0178

Jetson Nano

@Sean-Hickey PMD tof that comes with yellow board M0173 - https://docs.modalai.com/M0173/

Yes optical flow is facing down, it is used for position hold and not for collision prevention.

Jetson Nano

@Sean-Hickey I am using the optical flow sensor for position hold, it is attached directly to the FC.

I am getting the obstacle_distance messages from the TOF sensor and I am able to see it.
I did check with 1 m cp_dist and it was not working.

Jetson Nano

@Eric-Katzfey
I am able to build, my build is not able to have both collision prevention and uavcan working. if i go to the latest version the hearding error is showing up, prearm check is not passing.

I checked with px4 mainline as well as modalai fork,

branches including - voxl-fpv-dev, version 1.17-dev
main branches - release/1.17, 1.16, 1.15

None of the above have the UAVCAN enabled, I do it manually, and the UAVCAN error is solved.

If you could guide me to a version of PX4 where both of this works with Flight core v2, or share the px4 build, if you have it working, i could test it out .

Jetson Nano

@Eric-Katzfey @Alex-Kushleyev

I have the ark flow MR attached to the FC. While I want to check the standard builds, the standard build do not have UAVCAN modules enabled. i have to enable them manually.

If anyone could share the built px4 file for the ModalAi FC v2 along with UAVCAN enabled and collision prevention working, It would mean alot.

Jetson Nano

@Eric-Katzfey I will do that.

Jetson Nano

@Eric-Katzfey @Alex-Kushleyev

I have the ark flow MR attached to the FC. While I want to check the standard builds, the standard build do not have UAVCAN modules enabled. i have to enable them manually.

If anyone could share the built px4 file for the ModalAi FC v2 along with UAVCAN enabled and collision prevention working, It would mean alot.

Jetson Nano

@Alex-Kushleyev @Eric-Katzfey @Vinny

I am using modalai fc v2 with voxl 2 , i am able to see the obstacle_distance message publishing in the mavlink console, but the drone is not slowing down or stopping.

the parameters are
mpc_pos_mode - acceleration based
cp_dist - 1 m
cp_no_go_data - enabled
cp_angle - 0

I checked with various builds and versions of PX4 from both PX4 github and Modalai github.

can anyone help me with which version or fork it works.

nsh> listener obstacle_distance

TOPIC: obstacle_distance
 obstacle_distance
    timestamp: 178940124 (0.026434 seconds ago)
    increment: 10.00000
    angle_offset: 0.00000
    distances: [236, 237, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001]
    min_distance: 0
    max_distance: 2000
    frame: 12
    sensor_type: 4

nsh> listener obstacle_distance 10

TOPIC: obstacle_distance
 obstacle_distance
    timestamp: 184239763 (0.014512 seconds ago)
    increment: 10.00000
    angle_offset: 0.00000
    distances: [236, 236, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001]
    min_distance: 0
    max_distance: 2000
    frame: 12
    sensor_type: 4

nsh> listener obstacle_distance 10

TOPIC: obstacle_distance
 obstacle_distance
    timestamp: 199589325 (0.028254 seconds ago)
    increment: 10.00000
    angle_offset: 0.00000
    distances: [236, 236, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001]
    min_distance: 0
    max_distance: 2000
    frame: 12
    sensor_type: 4

nsh> listener obstacle_distance 10

TOPIC: obstacle_distance
 obstacle_distance
    timestamp: 204539470 (0.012805 seconds ago)
    increment: 10.00000
    angle_offset: 0.00000
    distances: [445, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001]
    min_distance: 0
    max_distance: 2000
    frame: 12
    sensor_type: 4

nsh> listener obstacle_distance 10

TOPIC: obstacle_distance
 obstacle_distance
    timestamp: 206838947 (0.036977 seconds ago)
    increment: 10.00000
    angle_offset: 0.00000
    distances: [435, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001]
    min_distance: 0
    max_distance: 2000
    frame: 12
    sensor_type: 4

nsh> listener obstacle_distance 10

TOPIC: obstacle_distance
 obstacle_distance
    timestamp: 208539592 (0.000817 seconds ago)
    increment: 10.00000
    angle_offset: 0.00000
    distances: [436, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001]
    min_distance: 0
    max_distance: 2000
    frame: 12
    sensor_type: 4

nsh> listener obstacle_distance 10

TOPIC: obstacle_distance
 obstacle_distance
    timestamp: 210039039 (0.006330 seconds ago)
    increment: 10.00000
    angle_offset: 0.00000
    distances: [435, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001]
    min_distance: 0
    max_distance: 2000
    frame: 12
    sensor_type: 4

nsh> listener obstacle_distance 10

TOPIC: obstacle_distance
 obstacle_distance
    timestamp: 223538159 (0.007192 seconds ago)
    increment: 10.00000
    angle_offset: 0.00000
    distances: [114, 102, 98, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 129, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001]
    min_distance: 0
    max_distance: 2000
    frame: 12
    sensor_type: 4

nsh> listener obstacle_distance 10

TOPIC: obstacle_distance
 obstacle_distance
    timestamp: 225588237 (0.036362 seconds ago)
    increment: 10.00000
    angle_offset: 0.00000
    distances: [93, 90, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001]
    min_distance: 0
    max_distance: 2000
    frame: 12
    sensor_type: 4

nsh> listener obstacle_distance 10

TOPIC: obstacle_distance
 obstacle_distance
    timestamp: 227187560 (0.049067 seconds ago)
    increment: 10.00000
    angle_offset: 0.00000
    distances: [2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001]
    min_distance: 0
    max_distance: 2000
    frame: 12
    sensor_type: 4

nsh> listener obstacle_distance 10

TOPIC: obstacle_distance
 obstacle_distance
    timestamp: 228587517 (0.043813 seconds ago)
    increment: 10.00000
    angle_offset: 0.00000
    distances: [2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001, 2001]
    min_distance: 0
    max_distance: 2000
    frame: 12
    sensor_type: 4

nsh>

Jetson Nano

@Alex-Kushleyev

Thank you for your continued support and assistance with this investigation.

Please find attached the system architecture diagram (power flow) of our platform for your review.

We would appreciate it if you could review the architecture and advise whether there are any potential concerns related to the power distribution, grounding scheme, wiring, connectors, ESC installation, or any other aspect that could contribute to the behavior we observed with the VOXL FPV ESC.

Additionally, we would like to highlight a few observations from our testing activities.

The abnormal ESC behavior was not present during the initial flight tests. The aircraft completed multiple successful flights before the failures began to occur. This leads us to believe that a direct short circuit caused by the frame, enclosure, or mounting arrangement may be less likely, as such an issue would typically manifest from the beginning of testing rather than after several successful flight cycles.

To further isolate the issue, we replaced the VOXL FPV ESC with a third-party NeutronRC X-CLASS 4IN1 ESC (70A). Following the replacement, the aircraft has been operating normally and has successfully completed multiple flight tests without any motor shutdown events or ESC-related failures.

At present, the third-party ESC continues to function correctly, and we have not observed any of the symptoms previously encountered with the VOXL FPV ESC. Motor operation, flight stability, and overall system performance remain normal.

This observation is particularly important because the remainder of the system configuration has remained largely unchanged, including:

VOXL2
Flight Controller V2
Power distribution architecture
Motors
Propellers
Battery configuration
Airframe and enclosure

Given that the issue is not reproducible with the third-party ESC, we are trying to better understand whether there may be any specific factors related to the VOXL FPV ESC installation, operation, thermal conditions, configuration, or hardware that could have contributed to the failures we observed.

For reference, the ESC installation includes:

An aluminum heatsink mounted beneath the ESC
Thermal interface material between the ESC and heatsink
Nylon spacers providing electrical isolation
A dedicated 3D-printed mounting structure preventing contact with the aluminum enclosure

Based on the current mechanical arrangement, we do not believe there is any direct electrical contact between the ESC and the enclosure.

We would greatly appreciate your guidance on any additional troubleshooting procedures that you would recommend for the VOXL FPV ESC, including:

Hardware inspections
Diagnostic tests
Additional logging parameters
Thermal validation methods
Power system checks
Known failure modes or common causes for the symptoms observed

If there are any specific measurements, logs, or test procedures that would help narrow down the root cause, we would be happy to perform them and share the results.

Thank you once again for your continued support and technical guidance.

We look forward to your recommendations on the next steps.

Thank you

Jetson Nano

@Alex-Kushleyev

Thank you for your response and for helping us investigate this issue.

Please find our responses below to the questions raised:

Do you have PX4 logs of the VOXL ESC with one of the motors shutting down in flight?

Response:
Yes. The log file previously shared contains the PX4 flight log corresponding to the incident where one of the motors shut down during flight, resulting in loss of stability and the subsequent crash. The attached log is the same dataset we have been using for the failure analysis.

Is it possible that the aluminum enclosure is making contact with the ESC components, causing some kind of short? Especially during a crash, perhaps the ESC is making contact with the enclosure?

Response:
We do not believe there is any direct electrical contact between the ESC and the aluminum enclosure.

The ESC is mechanically isolated as follows:

A dedicated 3D-printed mounting structure is used between the ESC and the aluminum enclosure side walls.
Nylon spacers are used to maintain separation from the bottom-mounted aluminum heatsink.
The ESC is securely mounted and does not have any exposed conductive surfaces in contact with the enclosure during normal operation.

Based on the current mechanical arrangement, an enclosure-induced short circuit appears unlikely. However, we will perform an additional inspection of the assembly to verify clearances and mounting integrity.

Did you check if the motor temperature was OK after successful flights?

Response:
Yes. During successful flight tests, the motor temperatures were observed to be within normal operating limits and no abnormal heating was noticed.

What was the total current draw during flight when the failure occurred?

Response:
We have not yet extracted and analyzed the total current consumption at the exact moment of failure from the PX4 logs.I am currently coordinating with our team to review the logs in detail and obtain the current draw data during the affected flight. Once the analysis is completed, we will share the findings with you for further evaluation.

Please let us know if there are any additional parameters, diagnostic logs, or hardware inspections that you would recommend. We appreciate your continued support and guidance in helping us identify the root cause of this issue.

Thank you.

Jetson Nano

@Vinny @Eric-Katzfey @Alex-Kushleyev @modaltb
Hi Guys,
Any update would be great appreciated.

The requested data is provided above.

Jetson Nano

Hello @Alex-Kushleyev ,

Thank you for getting back to us.

Please find below a detailed summary of the failure scenarios observed during our recent flight testing activities. We would appreciate your assistance in analyzing these events and identifying any potential root causes.

System Configuration

VOXL 2 → Flight Controller V2 → ESC
Motor: T-Motor F60 Pro LV, 2020KV
Propeller: 5-inch Three-Blade Propeller
Battery: 6S, 5000mAh (21700 Cells)

Scenario 1 – VOXL FPV ESC Failure

During flight, the drone was operating normally when the rear-left motor suddenly stopped, causing the aircraft to lose stability and topple.

Following a system reboot, the affected motor exhibited abnormal behavior:

The motor would begin rotating briefly.
It would then stop unexpectedly.
This cycle would continuously repeat.

The same behavior was reproduced while running the ESC spin.py test utility.

As part of troubleshooting, we:

Updated the ESC firmware to the latest available version.
Applied the recommended parameter changes.
Repeated motor and ESC validation tests.

However, the issue persisted, and no improvement was observed.

Scenario 2 – VOXL FPV ESC No Longer Initializes

In a separate flight test using a replacement ESC, the drone was in a stable hover when the front-left motor stopped unexpectedly, causing the aircraft to topple.

Following the incident:

The affected ESC no longer initializes correctly.
During power-up, the ESC LEDs briefly illuminate and then turn off.
The ESC does not appear to complete its startup sequence.

Troubleshooting performed:

Connected the ESC directly to a computer.
Attempted to establish communication and detect the ESC.
Performed multiple power cycles and reconnection attempts.

Unfortunately, the ESC could not be detected, and communication could not be established. The terminal output associated with this issue was shared previously in our earlier correspondence.

Scenario 3 – Third-Party ESC Evaluation

To further isolate the issue, we replaced the VOXL FPV ESC with a NeutronRC X-CLASS 4IN1 ESC V2 (3–8S, 70A) configured using the DShot protocol.

During testing, we observed the following:

ESC temperature increased rapidly, reaching approximately 80°C to 90°C within two minutes of flight.
One motor would subsequently stop during flight.
The aircraft would lose stability and crash.
During or immediately after impact, the ESC appeared to reboot.
Following the reboot, the system would operate normally again.

This behavior has been consistently observed across five separate flight tests, with each flight resulting in a similar failure sequence and crash.

Additional Observations

While reviewing the available flight logs, we observed elevated ESC temperatures:

General ESC operating temperature ranged between 75°C and 88°C during the affected flights.
ESC(0) reached a peak temperature of approximately 88°C.
During earlier flight tests under similar operating conditions, ESC temperatures typically ranged between 60°C and 75°C.

Installation and Thermal Management Details

The ESC is installed inside a closed enclosure with the following thermal arrangement:

Bottom-mounted aluminum heatsink.
Thermal interface material between the ESC and heatsink.
Side walls constructed from aluminum structural members.

Despite the presence of thermal conduction paths, the elevated temperatures observed during flight raise concerns regarding thermal dissipation and potential thermal shutdown behavior.

Flight Logs

Log File:

https://drive.google.com/file/d/1wxv7VZub4-7onK6YdgcJ8kSpGhpZ40mY/view?usp=sharing

Note: Access approval may be required to view the file. If the link is inaccessible, please send an access request and we will grant permissions immediately.

Given that similar symptoms have been observed across both the VOXL FPV ESC and a third-party ESC platform, we would greatly appreciate your guidance on:

Potential root causes of the motor shutdown events.
Whether the observed temperatures are within acceptable operating limits.
Recommended diagnostics or logging parameters to further isolate the issue.
Any known interactions between the motor, propeller, battery, and ESC configuration that could contribute to these failures.

Please let us know if any additional logs, hardware details, configuration files, or test data are required from our side.

Thank you for your continued support and assistance.