Posts made by Jetson Nano

Hello @Vinny @Eric-Katzfey @Alex-Kushleyev @modaltb

I am facing an error with my Voxl FPV ESC. The ESC is not responding to any command. While plug in power the ESC is only blinking 3 LED for the initialization, then there is no LED blinking.
The ESC was working fine, during a flight test the motor suddenly stopped and the drone was landed safely somehow, but after that the motors are not starting, there are no visible damages.
I am attaching the terminal results, I tried to upgrade the firmware, alchange the parameter file, but the ESC is not responding. I also checked with various baudrate, the result is same, no response.

:~/Downloads/voxl-esc-master/voxl-esc-tools$ sudo python3 voxl-esc-scan.py
Detected Python version : 3.10.12 (main, Mar  3 2026, 11:56:32) [GCC 11.4.0]
Found voxl-esc tools bin version: 1.10
INFO: All COM ports:
	/dev/ttyUSB0 : FT232R USB UART - FT232R USB UART
INFO: UART Port Candidates:
	/dev/ttyUSB0
INFO: Scanning for ESC firmware: /dev/ttyUSB0, baud: 2000000
INFO: Scanning for ESC bootloader: /dev/ttyUSB0, baud: 230400
WARNING: No ESC(s) detected
INFO: All COM ports:
	/dev/ttyUSB0 : FT232R USB UART - FT232R USB UART
INFO: UART Port Candidates:
	/dev/ttyUSB0
INFO: Scanning for ESC firmware: /dev/ttyUSB0, baud: 250000
INFO: Scanning for ESC bootloader: /dev/ttyUSB0, baud: 230400
WARNING: No ESC(s) detected
INFO: All COM ports:
	/dev/ttyUSB0 : FT232R USB UART - FT232R USB UART
INFO: UART Port Candidates:
	/dev/ttyUSB0
INFO: Scanning for ESC firmware: /dev/ttyUSB0, baud: 921600
INFO: Scanning for ESC bootloader: /dev/ttyUSB0, baud: 230400
WARNING: No ESC(s) detected
INFO: All COM ports:
	/dev/ttyUSB0 : FT232R USB UART - FT232R USB UART
INFO: UART Port Candidates:
	/dev/ttyUSB0
INFO: Scanning for ESC firmware: /dev/ttyUSB0, baud: 57600
INFO: Scanning for ESC bootloader: /dev/ttyUSB0, baud: 230400
WARNING: No ESC(s) detected

ERROR: not all ESCs found

please help me out here, is there any way to figure out why is this happening and how to solve it, I had a similar instance earlier, but the ESC was responsive and one motor was glitching. it was stopping during rotation. changing motor did not help, so i changed the ESC and it worked.

what I do to maintain the ESC safety and working.

@Vinny @Alex-Kushleyev @Eric-Katzfey

Hello ModalAI Team,

I am writing to request information regarding the Mean Time To Failure (MTTF) for several hardware components that we have procured from your team for our ongoing development program.

The components include:
VOXL2
ESC
Flight Controller (V2)
Front-End Board (Camera Interface)
Camera Modules

We would appreciate it if you could share any available MTTF data, reliability reports, or qualification/test standards associated with these products.

If detailed MTTF values are not readily available, any indicative data such as MTBF estimates, environmental test results, or reliability benchmarks would also be helpful.

Please let us know if any additional information is required from our side to process this request.

Thank you for your continued support.

Hey @Alex-Kushleyev @Vinny @Eric-Katzfey ,

I had query regarding the mating cycles of the components.

Does Voxl2 and M0173 board have mating cycle limit?
Also how much is the mating cycle of the camera cables for hire, tracking and TOF?
Is there any mating cycles for flight core v2 connectors?

I would really appreciate a clarity on this
With regards

Hello @Alex-Kushleyev, @Vinny, @Tom, @Eric-Katzfey,
An update to the above query will be deeply appreciated.

Thank you

Hello @Alex-Kushleyev, @Vinny, @Tom, @Eric-Katzfey,

Greetings.

We recently came across the newly launched Teledyne FLIR Lepton XDS thermal module and are currently evaluating its suitability for integration into our UAV platform architecture based on VOXL2.

We would like to understand the feasibility of integrating the Lepton XDS with VOXL2 and request your guidance on the recommended hardware and software approach for interfacing the module and retrieving the video feed.
we seek clarification on the following points:
Are there any plans to support or officially integrate the Lepton XDS module within the VOXL2 ecosystem in future releases?
If so, is there any tentative timeline or reference documentation available?
What would be the recommended interface method for integration (e.g., MIPI-CSI, SPI, USB, or alternative interface)?
We would greatly appreciate your technical inputs, recommended configuration workflow, and any limitations we should be aware of before proceeding further.
Looking forward to your guidance.
Thank you.

@Alex-Kushleyev Thank you for reverting back. I will go through the documentation. If I disable the shutter will it work with causing any issue with respect to FFC.
Also I would wish use any other thermal camera with usb camera support, can it be used for localisation through QVIO, I will be required to create a MIPI communication, right?

I will find some documentation regarding the feature tracker question.- looking forward for your response.

Hello @Alex-Kushleyev @Vinny @Eric-Katzfey @tom

I would know whether boson is completely supported by voxl2 or is it still under development for J8 pinout.
Can I use the boson for tracking ?

Could you share what is the purpose voxl-feature-tracker, voxl-flow-server and voxl-lepton-tracker.

@Alex-Kushleyev Could you please share the pinouts of the serial console port. I am not able to find it anywhere.

@Alex-Kushleyev sure , i will test it out , thank you for your support. I will get back to you with the result once I test it out.

@Alex-Kushleyev will the microhard add-on board support it?

@Alex-Kushleyev thank you for reverting back, I will check what you suggested. Try to run diagnostics by myself. I will have to check whether I have M0130, and M0017. I have M0151, will that work.

@Alex-Kushleyev Thank you for your reply. I have a old voxl2 as well as new revised voxl 2, the one not booting is the new one, When I compared it to the old design I didn't find the barometer, but I also had noticed that the new design do not have them, i asked just in case whether it would be the cause. Thank you for clearing the query.

Please discuss with your team and let me know how can I proceed, If you need anymore data from me I can provide it.

@Alex-Kushleyev

Could you verify that this issue is due to missing sensor at U18 port

successfully\n[PROGRAM] flashed \"PrimaryGPT\" successfully\n[PROGRAM] flashed \"BackupGPT\" successfully\n[PROGRAM] flashed \"PrimaryGPT\" successfully\n[PROGRAM] flashed \"BackupGPT\" successfully\nqdl: firehose operation timed out\n\nFlash flat build passed\n"}

this is full log
this is the end line

@Alex-Kushleyev Thank you for reverting back.
While I attempt to unbrick the process is displaying as completed but after the reboot and waiting for almost 10 - 15 minutes the board is not booting.
I have turned on and off the Switch 2 for the process. I followed every step mentioned in the website.

@Eric-Katzfey @Alex-Kushleyev @tom @Vinny

Hey guys, do you think my board is damaged.

@Eric-Katzfey @Alex-Kushleyev @tom @Vinny
Hello guys,
I had a crash after which the voxl2 is not booting up. The board is powered sensors and fans are getting powered but the voxl 2 is not completing the boot. I tried unbricking but did not resolve the issue. there is no visible damage to the board, i had checked it.
could any help me out here.

@Eric-Katzfey

Thank you for reverting back. I am trying to proceed with the same approach.
I am facing some errors while going with this approach , I am trying to debug them.

Another approach :-
I am also thinking to hardcode the joystick based turtle mode to the voxl_esc.cpp.
The manual control values will be monitored and once the value of the assigned button is clicked, the turtle mode will be enabled.
Do you think it is a good approach?

@Eric-Katzfey

I am sorry for the confusion , I started the thread for another ESC, that is cleared.

Now I am asking with respect to modal ai FPV ESC.

The issue I am facing now is, the VOXL-FPV-DEV fork of px4 has turtle mode for joystick and button.
The Main fork of the PX4 do not carry this feature.
I would like to incorporate this feature in the Main fork.

The reason I switched from fpv-dev to main, was collision prevention error. The VOXL-FPV-DEV do not have collision prevention working properly.

I hope my questions are clear now.