Skip to content

VOXL 2

593 Topics 3.3k Posts

VOXL 2 Support Forum

  • Calibrating tracking camera doesn't work

    2
    1
    0 Votes
    2 Posts
    391 Views
    ModeratorM
    @Gdanan Do you have other services running? Maybe try to disable unneeded services while calibrating?
  • How to write data to vvhub_fixed_pose_input pipe

    1
    0 Votes
    1 Posts
    463 Views
    No one has replied
  • imu_apps seems to be publishing in bursts

    5
    0 Votes
    5 Posts
    1k Views
    tomT
    @tanguy-sagere I wonder if you upgrade to SDK 1.0 if the issue resolves itself
  • 0 Votes
    35 Posts
    9k Views
    Alex KushleyevA
    @John-Nomikos-0 Thank you. OK, here is the big difference that is most likely the reason for your behavior. In your new params you used kp, ki, max_kpe, max_kpi terms set to zero, but old params have nonzero: <param name="kp" value="130"/> <!-- RPM controller proportional gain --> <param name="ki" value="30"/> <!-- RPM controller proportional gain --> <param name="max_kpe" value="300"/> <!-- maximum proportional erorr term (max is 999) --> <param name="max_kie" value="100"/> <!-- maximum integral error term (max is 999) --> <param name="max_rpm_delta" value="1200"/> <!-- cap for maximum rpm error used in RPM controller --> Considering that you have not calibrated the ESC for your motor and propeller (meaning that the feed-forward term in the RPM controller is wrong), if you also disable the feedback terms of the RPM controller (kp, ki) then the behavior of the ESC will be completely off from what is desired. Even with incorrect feed forward term (pwm_vs_rpm_curve terms), if feedback terms are enabled, they can compensate, to some degree, but with the feedback terms set to zero, there is no hope for the ESC to turn the motor at the desired speed. You can keep using the old firmware and params if that works for you, but if you wanted to switch to latest ESC firmware and params, then i suggest trying to use the same non-zero RPM controller params. Alex
  • Question about USB on J13 Port

    3
    0 Votes
    3 Posts
    648 Views
    Aaron PorterA
    @Moderator Thank you
  • QVIO Issues with y and z values flipped

    3
    0 Votes
    3 Posts
    589 Views
    Aaron PorterA
    So this is the correct functionality, and that the Data is updated relative to the IMU and not to the Body of the Drone.
  • voxl-px4 service

    4
    0 Votes
    4 Posts
    1k Views
    R
    @Eric-Katzfey yes
  • VOXL2 IO (M0065) support on PX4 1.14 in SDK 1.0.0

    8
    0 Votes
    8 Posts
    2k Views
    J
    @Eric-Katzfey said in VOXL2 IO (M0065) support on PX4 1.14 in SDK 1.0.0: @Jon305Johnson I would estimate about a month for RC functionality (SBus) and another month for PWM @Eric-Katzfey any updates or projections on the M0065 integration into 1.14?
  • Image Flashing Error

    10
    0 Votes
    10 Posts
    2k Views
    J
    @tom Confirmed, installing the normal way doesn't corrupt the apt repo..... THANKS!
  • Time appears to move back on reboot when not connected to internet

    3
    0 Votes
    3 Posts
    691 Views
    John Nomikos 0J
    @Eric-Katzfey Makes sense to me. Thank you for the info. Threw me off because journalctl was showing most recent logs were from the future.
  • VOXL2 stop motors from beeping

    1
    0 Votes
    1 Posts
    518 Views
    No one has replied
  • I/O board with 1.0.0 SDK

    4
    0 Votes
    4 Posts
    731 Views
    Eric KatzfeyE
    @Abdullah01 Yes, ESC should be fine.
  • Can we use GPS and voxl2 IO board with voxl2 simultaneouly ?

    11
    0 Votes
    11 Posts
    2k Views
    Adrian HidalgoA
    @Chase-Riley, The IO board has the Spektrum plug, so that could be used(MCBL-00005-1) between receiver and IO board.
  • No RGB LED and Missing Mag with VOXL2 and VOXL2 GPS (MDK-M0094-2-02)

    10
    0 Votes
    10 Posts
    2k Views
    Adrian HidalgoA
    @Chase-Riley Nice find! Let us know how the testing goes.
  • trying to work with Mro Ist8308 gps+compass on voxl2 sdk 0.9.5

    2
    0 Votes
    2 Posts
    528 Views
    Eric KatzfeyE
    @bensusana No, but it has been very recently added in version 1.14.0-2.0.43. The latest version is available here: http://voxl-packages.modalai.com/dists/qrb5165/dev/binary-arm64/voxl-px4_1.14.0-2.0.45-202308151518_arm64.deb. You will need to be on SDK 1.0 to use it.
  • Most VOXL 2 hires-capable camera ports nonfunctional after SDK 1.0 flash

    6
    0 Votes
    6 Posts
    1k Views
    Chad SweetC
    For future reference, this is the doc to follow https://docs.modalai.com/voxl2-image-sensors/
  • How would I change the area that lidar is capturing?

    2
    0 Votes
    2 Posts
    523 Views
    ModeratorM
    @John-Nomikos-0 No, you will need to ignore that portion of the data in your code making use of the data.
  • This topic is deleted!

    1
    0 Votes
    1 Posts
    2 Views
    No one has replied
  • This topic is deleted!

    1
    0 Votes
    1 Posts
    1 Views
    No one has replied
  • 4208x3120 resolution with IMX214 M0025-2 hires cam on VOXL 2

    7
    0 Votes
    7 Posts
    1k Views
    modaltbM
    @Jeff-Delaune-_ This is a little late, but we have 4208x3120 working now. The changes weren't in the camera driver itself but the camera pipeline and camera-server... we have it available in a nightly build if you're up to trying a pre-release out! [image: 1691793013727-182da38b-69b1-45f1-b775-d8f2f0bc2ec5-image.png]