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
    2288
    Topics
    11417
    Posts

    N

    @Eric-Katzfey Appreciate your help!

  • Commonly asked questions we get from the community

    68
    Topics
    297
    Posts

    Eric KatzfeyE

    @JB1 Our voxl-remote-id software with WiFi dongle is intended only for reference and is not meant to be a commercially ready system for our customers who need a remote id solution for their VOXL2 based drone products. Integration, testing, validation, and FAA registration with desired hardware is up to the end user. At a minimum the manufacturer id would need to be changed from ModalAI's id to your companies issued manufacturer id.

  • Questions by Product

    2179
    Topics
    11446
    Posts

    Hector GutierrezH

    @Eric-Katzfey : I'm not running any custom software other than voxl-vision-hub.
    If I stop and disable voxl-vision-hub, the "set_position_target_local_ned: coordinate frame 0 unsupported" error goes away !
    With this I am able to complete calibration (compass and IMU) successfully in GQC, BUT drone fails to arm in Position mode even though QGC shows "Ready to Fly" and all Sensor status show as "normal".
    Checking VIO in VOXL Portal shows correct operation of VIO: VIO plot follows drone motion, which seems to indicate that VIO is working fine, but
    QGC shows "Yaw estimate error" , and "--" as altitude estimate, which prevent the drone from arming in Position mode.
    Then I re-enable and restart voxl-vision-hub.
    Now GQC receives altitude estimates and I'm able to arm the drone in position mode !
    So the trick seems to be to disable/stop voxl-vision-hub, calibrate IMU if needed, and enable/restart voxl-vision-hub, to be able to arm in Position mode.
    Seems odd but I'll take it ! Let me know if you have any comments or suggestions. Thanks.

  • 497
    Topics
    2441
    Posts

    Eric KatzfeyE

    @bschulzhf PX4 will only correct incoming messages. Something external will have to also run TIMESYNC with PX4 to estimate the offset and correct and incoming PX4 message timestamps that it wants to align. voxl-mavlink-server does this for a few messages.

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

    PCB Design Reviews System Architecture Design Reviews
    15
    Topics
    39
    Posts

    Alex KushleyevA

    @Eyal , sorry for the delay. Here is some additional information regarding Stinger FPV:

    https://docs.modalai.com/stinger-vision-datasheet/ base weight with battery : ~570g maximum thrust per motor : 650g @ 15V, 2600g total theoretical theoretical max thrust to weight ratio: 4.5:1, lots of extra margin, but if you add a LOT of weight, will need to check motor temps, etc. CAD model for stinger (may be slightly outdated) : https://forum.modalai.com/topic/5180/looking-stinger-fpv-cad-models -- you can attach your payload to carbon fiber I think that Stinger will be easier to tune up with additional payload because of more responsive and powerful propulsion system than Starling 2. i dont know what your sensor package is so, it is hard to comment about which platform is better. Starling 2 has landing gear that offsets it from the floor. Stringer is much lower to the ground.

    Alex