ModalAI Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    tracking down pipe switching to images of traccking front camera

    Video and Image Sensors
    2
    5
    43
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • M
      mark
      last edited by

      Hello I am encountering a weird issue using the M0173 with 2 IMX412 cameras and 2 AR0144 cameras.
      The streams of the tracking cameras start out correct when (re)starting the voxl-camera-server, but after some point the tracking_down seems to copy the tracking_front images. Do you maybe know a solution for this problem? or have you seen this happen before? any help would be appreciated.
      ce3bed50-1dd2-4ab6-aff7-4f8601369c14-image.png
      cb9e567d-4186-4094-9d02-b39f257a0c0e-image.png
      I am using sdk 1.4.5 on the drone.

      Alex KushleyevA 1 Reply Last reply Reply Quote 0
      • Alex KushleyevA
        Alex Kushleyev ModalAI Team @mark
        last edited by

        @mark , we have seen this issue when using 10- or 12-bit drivers for the AR0144 tracking cameras. These drivers are shipped with the SDK but are not stable (for this exact reason).

        Can you please confirm which ar0144 sensormodules you are using - you can check in /usr/lib/camera.

        Alex

        M 1 Reply Last reply Reply Quote 0
        • M
          mark @Alex Kushleyev
          last edited by

          hi @Alex-Kushleyev, i am not using the 10 or 12 bit drivers, everything was set up using voxl-configure-cameras 28 this is what the /usr/lib/camera folder looks like (the .tuned files of the 412 camera were renamed in order to use the default .tuned files, which gave the best image for our application)
          f03b48ab-2f62-4c9e-ad4b-cc0db17ce51b-image.png

          M 1 Reply Last reply Reply Quote 0
          • M
            mark @mark
            last edited by

            @Alex-Kushleyev, By the way, as i was comparing this VOXL2 to one which does not have this same issue, i noticed that the board seemed to be an older one, could this have anything to do with it?
            VOXL with the issue:
            69799746-8bb1-463f-ba1a-b99c16e24a59-Screenshot from 2025-11-27 09-03-38.png
            VOXL which behaves as expected:
            a27a1ef5-0ddb-450f-8ba4-ce97641b6cf1-Screenshot from 2025-11-27 09-03-24.png

            Alex KushleyevA 1 Reply Last reply Reply Quote 0
            • Alex KushleyevA
              Alex Kushleyev ModalAI Team @mark
              last edited by

              @mark, thank you for the details. It should not matter whether M0054 or M0154 voxl is used.

              Can you please do a test and disable both hires cameras and see if the issue is still reproducible? If the issue is gone, then enable one hires camera and test again.

              Also, does setting cpu to perf mode help with this? (Voxl-set-cpu-mode perf)

              I have never seen this happen with out stable camera configs, such as C28, so this is very odd!

              Alex

              1 Reply Last reply Reply Quote 0
              • First post
                Last post
              Powered by NodeBB | Contributors