1. Home
  2. Categories

Categories

  • Note sure where to post? Ask questions here for direct access to the ModalAI engineering team

    Support Request Format for Best Results Feature Requests 3D Models
    2155
    Topics
    10840
    Posts

    YUUJI INOUEY

    @YUUJI-INOUE said in Persistent PX4 Sensor/Accel Failure on Stinger (D0013) with SDK 1.6.2 + Dev IMU/OV Servers:

    @Eric-Katzfey

    Updated Support Request: Parameter Fix Attempt & Remaining Accelerometer/Position Mode Issues

    Following the advice to update parameters, we have made progress but still cannot enter Position Mode due to persistent sensor checks failures.

    Actions Taken Parameter Reset & Load: Executed voxl-configure-px4-params --wizard and selected D0013 (Stinger). Confirmed that /data/px4/param/parameters is now created and populated. Battery Configuration Fix: Manually corrected BAT_N_CELLS to 4 (was defaulting to 6) and BAT_LOW_VOLT to 14.0V. This successfully resolved the "Low Voltage" warning in QGC. Re-Calibration: Performed fresh Accelerometer, Level Horizon, and Compass calibrations in QGC. Performed Camera calibration. Current Status Manual Mode: OK. We can Arm the drone and spin motors in Manual Mode. We have also performed a successful test flight in Manual Mode. VIO: OK. The virtual drone in Web Portal follows the real drone perfectly. Position Mode: FAILED. QGC shows "Ready for flight" briefly after reboot, but rejects Arming (Command denied). After disarming from a Manual Mode test, Position Mode switches to "Not Ready". Web Portal System Check: FAILED. voxl-px4 still reports sensor_accel: result false. Values (e.g., z: 9.70) seem correct, but the check fails. Persistent Logs Errors (New Logs Attached)

    Despite the parameter fix, voxl-px4.log still shows communication timeouts with the sensors:

    ERROR [muorb] [sensors] Accel #0 fail: TIMEOUT! ERROR [qshell] Command failed ERROR [muorb] [drivers__device] i2c probe failed Questions Since we can Arm in Manual Mode (suggesting the IMU hardware is working) and have loaded the correct D0013 parameters, why does voxl-px4 still report sensor_accel: result false with timeouts? Is there a specific driver or timing parameter in SDK 1.6.2 (with the dev branch IMU server) that causes these spurious timeouts on the Stinger? What is preventing Position Mode Arming even when VIO is healthy and Manual Arming works?

    We have attached the latest logs (voxl-px4.log, voxl-vision-hub.log) from this new configuration state.
    voxl-px4.log
    voxl-vision-hub.log

    I've been hooked on this for two weeks now. Can someone tell me how to set up STINGER VER1 from scratch?

  • Commonly asked questions we get from the community

    61
    Topics
    283
    Posts

    Alex KushleyevA

    @chengyouzen , have you tried building OpenSSL from source (you should be able to do it directly on VOXL1)? That may be the only way..

    Alex

  • Questions by Product

    2067
    Topics
    10995
    Posts

    A

    @Alex-Kushleyev Thanks for detailed information and analysis. I am going ahead with further testing with this ESC as per your suggestion.

    I have changed my propulsion system as follows: Emax Eco II seroes 2306 2400kv motor, propeller Gemfan 5177 and 15000 mah 4S battery.

    Here is my file with ESC calibration : https://drive.google.com/file/d/1uzbx9MGwF1EvRqJx6tXBqqc-j3XZSgu_/view?usp=sharing

    All the motor directions are checked and they are correct as per airframe reference. My UAV is able to takeoff a bit but at around 0.5 meters it again decreases its altitude and then after scratching the surface is flipping over.

    Here is the logs : https://review.px4.io/plot_app?log=08691d7d-887d-41d8-b00d-d543febeea59

    Can you spot is my ESC configuration wrong or anything I am missing in PX4 configuration? This flip happened twice in a row and all motor direction are verified to be correct since UAV is able to takeoff. Also any advantage of RPM vs PWM control in VOXL ESC PX4 parameter setup?

    Also my voxl2 is unpside down so I have set ROLL_180 in Autopilot orientation, but is this creating some problem anywhere is unknown since I can see yaw reset EKF2 estimator flag set as soon as I takeoff.

  • 451
    Topics
    2185
    Posts

    Alex KushleyevA

    @l05 , when in doubt, you can add a print statement in your app as a sanity check to make sure you are running the correct version of the application. Then check your print statement at run time.

    If you are modifying an existing app in voxl-mpa-tools, you just need to use the voxl-cross docker image to

    build the source code build the package (deb) deploy the package (either manually pushing and dpkg -i <package.deb> on target) or using a convenience script deploy_to_voxl.sh which is typically present in most voxl projects -- this script will push the deb to voxl2 and install the deb. run your new application on voxl and confirm functionality

    If you are adding a new app to voxl-mpa-tools project, you will need to modify the CMakeLists.txt file in the tools folder, it should be self explanatory how to add a simple app. Once you build and deploy, your new app will be installed into /usr/bin on voxl2.

    If you have any other questions, let me know.

    Alex

  • Please request review from ModalAI before building your drone or custom add-on PCB

    PCB Design Reviews System Architecture Design Reviews
    11
    Topics
    30
    Posts

    Eric KatzfeyE

    @mkeyno You need to work with the PX4 community on this project, not ModalAI.