ModalAI Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login
    1. Home
    2. Jetson Nano
    • Profile
    • Following 2
    • Followers 1
    • Topics 91
    • Posts 442
    • Best 4
    • Controversial 0
    • Groups 0

    Jetson Nano

    @Jetson Nano

    5
    Reputation
    76
    Profile views
    442
    Posts
    1
    Followers
    2
    Following
    Joined Last Online

    Jetson Nano Unfollow Follow

    Best posts made by Jetson Nano

    • Offboard mode not working

      Hey @Eric-Katzfey @James-Strawson ,

      Thanks a lot for helping me with the integration of my VOXL2 with Cube Orange. It is working well. I am also using it with the ToF, HighRes, and tracking camera from ModalAI.
      Position hold using VIO and Semi-Autonomous (VOA) are also working well.

      Now, I am facing an issue with the offboard mode. The moment I switch to offboard, the drone aggressively moves and crashes. (in both "figure_eight and "trajectory"). [In the offboard mode = "off", I am not able to switch to offboard. ]

      There are no error messages in QGC or otherwise. Except offboard everything else works.
      Could please help with this issue?
      I'm working on this as a priority, so any suggestion will be quickly tested. I hope to hear from you.

      Thank you

      posted in VOXL 2
      Jetson NanoJ
      Jetson Nano
    • Odometry message not displayed with VIO

      Hey @Alex-Kushleyev @Eric-Katzfey @tom

      I'm using a VOXL2 compute along with Flight Core V2 as external flight controller.

      PX4 version: v1.15.1 (Stable)

      The VOXL2 communicates with FC as mentioned in this documentation.

      For position hold I have set EV parameter using tracking camera fusing with a Optical Flow with Rangefinder onboard. I'm able to see the odometry message being shown in mavlink console on QGC. Also, I try streaming the message from VOXL2,

      mavlink stream -r 30 -s ODOMETRY -d /dev/ttyS1

      In voxl-vision-hub I have set the mode to figure_eight. But once, I switch to offboard mode from position mode the drone stays at the same place and does not perform figure 8.

      Once I ssh into VOXL2, and check for mavlink status, I get the LOCAL_POSITION_NED but not #331 ODOMETRY message. How can I get that message?

      Without that message I'm not sure if VIO inputs from tracking camera would be passed on to FC for fusion on switching to offboard mode of flight.

      posted in GPS-denied Navigation (VIO)
      Jetson NanoJ
      Jetson Nano
    • ToF Depth Sensor support

      We have been looking out for VOXL Time of Flight (TOF) Depth Sensor from ModalAI products page to integrate with our VOXL2 board. But the sensor is currently unavailable for the critical time period.

      The sensor provided is ToF Depth sensor from PMD. Could the same sensor module provided by PMD(ie. PMD Flexx2 3D Camera Sensor module) be directly integrated with VOXL2?

      posted in Ask your questions right here! voxl2 tof depth sensor
      Jetson NanoJ
      Jetson Nano
    • Drift issue with Openvins

      @zauberflote1 @Cliff-Wong @Alex-Kushleyev @Eric-Katzfey

      Hey guys, I am using voxl-open-vins-server.
      I facing an issue of constant drift, the drone is drifting while takeoff itself. Once I take off itself the vins values varies from 1 m to 80 m. I take off in stabilised for safety. The drone once changed to position mode, constantly moves in one direction, until pilot gives different command, again it will continue in the direction of the pilot command.
      I am mentioning my config file here, please guide me to achieve strong position hold.

      /**
       * This file contains configuration that's specific to voxl-open-vins-server.
       * 
       * *NOTE*: all time variables are measured in seconds
       * 
       * OpenVins param breakdown:
       * 
       * do_fej: whether or not to do first estimate Jacobians
       * imu_avg: whether or not use imu message averaging
       * use_rk4_integration: if we should use Rk4 imu integration.
       * cam_to_imu_refinement: whether or not to refine the imu-to-camera pose
       * cam_intrins_refinement: whether or not to refine camera intrinsics
       * cam_imu_ts_refinement: whether or not to calibrate cam to IMU time offset
       * max_clone_size: max clone size of sliding window
       * max_slam_features: max number of estimated SLAM features
       * max_slam_in_update: max number of SLAM features in a single EKF update
       * max_msckf_in_update: max number of MSCKF features used at an image timestep
      
       * 
       * Feature Reps can be any of the following:
       * 0 - GLOBAL_3D
       * 1 - GLOBAL_FULL_INVERSE_DEPTH
       * 2 - ANCHORED_3D
       * 3 - ANCHORED_FULL_INVERSE_DEPTH
       * 4 - ANCHORED_MSCKF_INVERSE_DEPTH
       * 5 - ANCHORED_INVERSE_DEPTH_SINGLE
       * feat_rep_msckf: (int) what representation our msckf features are in
       * feat_rep_slam: (int) what representation our slam features are in
      
       * cam_imu_time_offset: time offset between camera and IMU
       * slam_delay: delay that we should wait from init before estimating SLAM features
       * gravity_mag: gravity magnitude in the global frame
       * init_window_time: amount of time to initialize over
       * init_imu_thresh: variance threshold on our accel to be classified as moving
       * 
       * imu_sigma_w: gyroscope white noise (rad/s/sqrt(hz))
       * imu_sigma_wb: gyroscope random walk (rad/s^2/sqrt(hz))
       * imu_sigma_a: accelerometer white noise (m/s^2/sqrt(hz))
       * imu_sigma_ab: accelerometer random walk (m/s^3/sqrt(hz))
       * imu_sigma_w_2: gyroscope white noise covariance
       * imu_sigma_wb_2: gyroscope random walk covariance
       * imu_sigma_a_2: accelerometer white noise covariance
       * imu_sigma_ab_2: accelerometer random walk covariance
       * 
       * ****_chi2_multiplier: what chi-squared multipler we should apply
       * ****_sigma_px: noise sigma for our raw pixel measurements
       * ****_sigma_px_sq: covariance for our raw pixel measurements
       * use_stereo: if feed_measurement_camera is called with more than one
       * image, this determines behavior. if true, they are treated as a stereo
       * pair, otherwise treated as binocular system
       * if you enable a camera with stereo in the name, this will be set to true
       * automatically
       * 
       * try_zupt: if we should try to use zero velocity update
       * zupt_max_velocity: max velocity we will consider to try to do a zupt
       * zupt_only_at_beginning: if we should only use the zupt at the very beginning
       * zupt_noise_multiplier: multiplier of our zupt measurement IMU noise matrix
       * zupt_max_disparity: max disparity we will consider to try to do a zupt
       * *NOTE*: set zupt_max_disparity to 0 for only imu based zupt, and
       * zupt_chi2_multipler to 0 for only display based zupt
       * 
       * num_pts: number of points we should extract and track in each image frame
       * fast_threshold: fast extraction threshold
       * grid_x: number of column-wise grids to do feature extraction in
       * grid_y: number of row-wise grids to do feature extraction in
       * min_px_dist: after doing KLT track will remove any features closer than this
       * knn_ratio: KNN ration between top two descriptor matchers for good match
       * downsample_cams: will half image resolution
       * use_nultithreading: if we should use multi-threading for stereo matching
       * use_mask: if we should load a mask and use it to reject invalid features
       */
      {
      	"en_auto_reset":	true,
      	"auto_reset_max_velocity":	20,
      	"auto_reset_max_v_cov_instant":	0.10000000149011612,
      	"auto_reset_max_v_cov":	0.10000000149011612,
      	"auto_reset_max_v_cov_timeout_s":	0.5,
      	"auto_reset_min_features":	1,
      	"auto_reset_min_feature_timeout_s":	3,
      	"auto_fallback_timeout_s":	3,
      	"auto_fallback_min_v":	0.600000023841858,
      	"en_cont_yaw_checks":	false,
      	"fast_yaw_thresh":	5,
      	"fast_yaw_timeout_s":	1.75,
      	"do_fej":	true,
      	"imu_avg":	true,
      	"use_rk4_integration":	true,
      	"cam_to_imu_refinement":	true,
      	"cam_intrins_refinement":	true,
      	"cam_imu_ts_refinement":	true,
      	"max_clone_size":	8,
      	"max_slam_features":	35,
      	"max_slam_in_update":	10,
      	"max_msckf_in_update":	10,
      	"feat_rep_msckf":	4,
      	"feat_rep_slam":	4,
      	"cam_imu_time_offset":	0,
      	"slam_delay":	1,
      	"gravity_mag":	9.80665,
      	"init_window_time":	1,
      	"init_imu_thresh":	1,
      	"imu_sigma_w":	0.00013990944749616306,
      	"imu_sigma_wb":	4.1189724174615527e-07,
      	"imu_sigma_a":	0.0038947538150776763,
      	"imu_sigma_ab":	5.538346201712153e-05,
      	"msckf_chi2_multiplier":	1,
      	"slam_chi2_multiplier":	40,
      	"zupt_chi2_multiplier":	1,
      	"msckf_sigma_px":	4,
      	"slam_sigma_px":	4,
      	"zupt_sigma_px":	4,
      	"try_zupt":	true,
      	"zupt_max_velocity":	0.02,
      	"zupt_only_at_beginning":	true,
      	"zupt_noise_multiplier":	1.5,
      	"zupt_max_disparity":	8,
      	"init_dyn_use":	true,
      	"triangulate_1d":	false,
      	"refine_features":	true,
      	"max_runs":	5,
      	"init_lamda":	0.001,
      	"max_lamda":	10000000000,
      	"min_dx":	1e-06,
      	"min_dcost":	1e-06,
      	"lam_mult":	10,
      	"min_dist":	0.1,
      	"max_dist":	60,
      	"max_baseline":	40,
      	"max_cond_number":	600000,
      	"use_mask":	false,
              "use_multithreading": true,
      	"use_stereo":	true,
      	"use_baro":	false,
      	"num_opencv_threads":	4,
      	"fast_threshold":	30,
      	"histogram_method":	1,
      	"knn_ratio":	0.7,
      	"takeoff_accel_threshold":	0.80,
      	"takeoff_threshold":	0.3,
      	"use_stats":	false,
      	"max_allowable_cep":	1,
      	"en_force_init":	false,
      	"en_force_ned_2_flu":	false,
      	"track_frequency":	40,
      	"publish_frequency":	15,
      	"en_vio_always_on":	false,
      	"en_ext_feature_tracker":	false,
              "en_gpu_for_tracking": true,
      	"num_features_to_track":	40
      }
      
      posted in Ask your questions right here!
      Jetson NanoJ
      Jetson Nano

    Latest posts made by Jetson Nano

    • RE: Voxl ESC not responding and not detected

      @Alex-Kushleyev

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

      Please find our responses below to the questions raised:

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

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

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

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

      posted in ESCs
      Jetson NanoJ
      Jetson Nano
    • RE: Voxl ESC not responding and not detected

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

      The requested data is provided above.

      posted in ESCs
      Jetson NanoJ
      Jetson Nano
    • RE: Voxl ESC not responding and not detected

      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.

      posted in ESCs
      Jetson NanoJ
      Jetson Nano
    • RE: Voxl ESC not responding and not detected

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

      posted in ESCs
      Jetson NanoJ
      Jetson Nano
    • Voxl ESC not responding and not detected

      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.

      posted in ESCs
      Jetson NanoJ
      Jetson Nano
    • RE: mating cycle query

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

      posted in Ask your questions right here!
      Jetson NanoJ
      Jetson Nano
    • mating cycle query

      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

      posted in Ask your questions right here!
      Jetson NanoJ
      Jetson Nano
    • RE: Feasibility & Integration Inquiry – FLIR Lepton XDS with VOXL2

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

      Thank you

      posted in Ask your questions right here!
      Jetson NanoJ
      Jetson Nano
    • Feasibility & Integration Inquiry – FLIR Lepton XDS with VOXL2

      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.

      posted in Ask your questions right here!
      Jetson NanoJ
      Jetson Nano
    • RE: BOSON camera

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

      posted in Ask your questions right here!
      Jetson NanoJ
      Jetson Nano