ModalAI Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login
    1. Home
    2. Software Development
    3. Video and Image Sensors
    Log in to post
    • Newest to Oldest
    • Oldest to Newest
    • Most Posts
    • Most Votes
    • Most Views
    • ModeratorM

      Accessing the PMD TOF Data Programmatically

      • • Moderator
      3
      0
      Votes
      3
      Posts
      485
      Views

      Alex KushleyevA

      and also a simple example here : https://gitlab.com/voxl-public/voxl-sdk/utilities/voxl-mpa-tools/-/blob/master/tools/voxl-inspect-tof.c?ref_type=heads

    • S

      DFS undistort issue

      • • SKA
      2
      0
      Votes
      2
      Posts
      533
      Views

      Alex KushleyevA

      @SKA , this is most likely due to the max disparity value being too large - for 1280x800 resolution the maximum value is 32.

      the max disparity parameter limit is as follows:

      width <= 640 : max disparity = 64 (or less, in steps of 4) 640 < width <= 1280 : max disparity 32 (or less in steps of 4) 1280 < width <= 1920: 16, 12,8, or 4

      So in your case, you should update your max disparity parameter to 32 or less.

      I have been testing AR0144 DFS recently and i also found that i needed to increase the min_threshold and cost_threshold from the default of 10 that was used for OV7251. I found that values in the range of 50-80 produced good results.

      Here is some additional information regarding DFS:

      min_threshold:
      Lower bound for adjusting occlusion cost threshold.
      When set to < cost_threshold, the occlusion penalty
      is varied linearly from this minimum value from the first row
      to the last row.
      The last row takes cost_threshold.
      Range: 0 to 100
      Recommended range: 50 to 75
      min_threshold <= cost_threshold

      cost_threshold:
      Occlusion cost threshold.
      The higher the value, more smoothness is enforced.
      Range: 0 to 100
      Recommended range: 50 to 75

      Alex

    • N

      TOF Sensor on Starling 2 Sample Data, Application, & Specs

      • • newdroneflyer
      2
      1
      Votes
      2
      Posts
      551
      Views

      Alex KushleyevA

      @newdroneflyer

      The different operating TOF modes (for the TOF V2 sensor on Starling 2) are described here in terms of power usage and fps : https://docs.modalai.com/M0178/#irs2975-operating-modes . We do not have exact information, but the different modes emit different amount of IR power and using different modulation schemes. The operating modes are tuned for the different ranges as stated (ultra short, short, mid long), which means depending on your application, you can choose one or the other.

      The number of sampling points per frame is the same for each mode, but FPS can be chosen based on what you need and it has to be within the provided specs (short range allows you to use higher fps).

      We have not done specific studies to measure the performance of the sensor to the detail that you are asking about.

      I can collect some data for you if you need. What format? There are also some tuning parameters, that can be tuned (can be found here with some comments : https://gitlab.com/voxl-public/voxl-sdk/services/voxl-camera-server/-/blob/master/src/tof_interface.cpp?ref_type=heads#L1033) . You would probably need to experiment yourself if you wanted to get the best performance out of the sensor.

      Alex

    • Evan PalmisanoE

      Camera Issues, Missing Pipes, Lots of fun.

      • • Evan Palmisano
      10
      0
      Votes
      10
      Posts
      1179
      Views

      Evan PalmisanoE

      @Alex-Kushleyev Yeah it was the cable. Getting hires feed now.

    • Matthew WellnerM

      Low Latency IMX412 Driver

      • • Matthew Wellner
      32
      0
      Votes
      32
      Posts
      6470
      Views

      Alex KushleyevA

      @Matthew-Wellner , I am glad you got it working! When you used M0076 single camera interposer connected to VOXL2 J7, actually you were connecting to the "lower" camera slot, so that would be J7L, meaning slot ID 2, not 3. That is why your camera was not detected in that case.

      Regarding your M0084 not working, it could be a hardware issue in the flex cable or it's connectors. In order to figure this out, some more testing would be needed. Also, typically we suggest avoiding daisy chaining flex cables, so M0076 / M0135 allows you to do just that. It is possible that a combination of M0084 and another extension cable create sufficient signal distortion of the MIPI lines to cause CRC errors.

      Alex

    • S

      Micro-coax dual interposer board for M0166 cameras

      • • SKA
      3
      0
      Votes
      3
      Posts
      468
      Views

      VinnyV

      Hi @SKA
      Alex's instincts are correct, we do not have a smaller plug in board for just tracking in a synce'd config. We only had an M0155 for one image sensor for a while, so your best bet is what Alex said and get the new M0188 for VOXL 2 Mini (VOXL 2 uses M0173, whereas VOXL 2 Mini uses M0188)
      It's quite cost competitive for what it does!!
      https://www.modalai.com/collections/all/products/m0188

    • Rowan DempsterR

      Do "tracking" cameras (e.g. ar0144) support the snapshot command?

      • • Rowan Dempster
      1
      0
      Votes
      1
      Posts
      367
      Views

      No one has replied

    • V

      Hires image sensors and FPV goggles

      • • victochen
      3
      0
      Votes
      3
      Posts
      666
      Views

      V

      @Moderator That's exciting, I'll be on the lookout. Thanks!

    • Rowan DempsterR

      Camera server: Preview stream stops when Large video activated

      • • Rowan Dempster
      11
      0
      Votes
      11
      Posts
      1739
      Views

      Rowan DempsterR

      @Alex-Kushleyev Gotcha, thanks for the info Alex and your help resolving this issue!

    • A

      Adding a new camera sensor

      • • anttukoski
      8
      0
      Votes
      8
      Posts
      1049
      Views

      Alex KushleyevA

      @anttukoski , yes I think you are right. I will work with your team via email to provide what you need. I believe we already have a thread.

      Alex

    • Kerry SnyderK

      Boson 640 MIPI M0153: 16-bit Pre-AGC

      • • Kerry Snyder
      3
      0
      Votes
      3
      Posts
      625
      Views

      Kerry SnyderK

      @Alex-Kushleyev Thank you! For the moment we have decided to stick with USB since we can fit that into the current electrical architecture, but I appreciate the offer and may take you up on it at some point in the future if our design changes.

      Thanks,
      Kerry

    • D

      voxl-camera-server behaving differently

      • • dvz
      5
      0
      Votes
      5
      Posts
      799
      Views

      tomT

      @dvz https://gitlab.com/WondesenB/voxl-tag-detector

    • Idan FikselI

      Camera not being identified on J7U

      • • Idan Fiksel
      7
      0
      Votes
      7
      Posts
      1031
      Views

      Alex KushleyevA

      @Idan-Fiksel , it looks like it worked since your machine variant is now 1.0.0 . I assume it was 1.0.1. Sorry the numbering in the name of the kernel is 00.0 vs 00.1…

    • Idan FikselI

      video streaming with herelink 1.1

      • • Idan Fiksel
      3
      0
      Votes
      3
      Posts
      637
      Views

      Q

      @Riley-Dove would you have any insight on this? Thanks!

    • S

      Stereo Image sensor selection

      • • SKA
      7
      0
      Votes
      7
      Posts
      1065
      Views

      S

      @Alex-Kushleyev This worked! Thank you

    • Manoj KashyapM

      Frame Dropping with PMD TOF LIOW2 (M0169) on VOXL2 Flight Deck - Royale SDK Warnings Persist After Troubleshooting

      • • Manoj Kashyap
      1
      0
      Votes
      1
      Posts
      369
      Views

      No one has replied

    • A

      Voxl 2 Mini with Starvis 2 not detected

      • • aheyne
      6
      0
      Votes
      6
      Posts
      911
      Views

      Alex KushleyevA

      @aheyne ,

      Thank you for the update.

      Please note that our standard configuration 50 has the IMX664 camera in slot 3, as shown in the link below ( J7 upper = slot ID 3). Since it is the only camera connected in this config, it would still show up as ID 0 in the voxl-camera-server.conf file.

      https://gitlab.com/voxl-public/voxl-sdk/services/voxl-camera-server/-/blob/master/misc_files/usr/share/modalai/voxl-camera-server/standard_configs/platform_config_2/50 - MVX-T0001 voxl2 mini hires imx664

      Also, i think you meant that you copied the com.qti.sensormodule.imx664_1.bin file, not 3 after running voxl-configure-cameras.

      The extra sensormodule file for slot number 3 in this case does not do anything because there is no camera actually connected in slot 3, so the camera pipeline will just try to probe the camera in this slot and will fail and move on. In general. I would recommend having only the sensormodule files that you are actually using in /usr/lib/camera in order to avoid any confusion in the future.

      Also, thank you for letting me know what happened when you connected the camera to the wrong ucoax port (J1L, which is designed for a Boson camera, which needs 5V). Yes, the camera shorted the 5V rail to ground inside the camera, but it seems it has survived? Don't try it again 🙂

      By the way, did you have to update the kernel?

      Is there anything else I can help you with, so you can get the most use of the IMX664 camera?

      Alex

    • T

      Rotate imx412 stream

      • • TomP
      16
      0
      Votes
      16
      Posts
      1860
      Views

      Jetson NanoJ

      @Alex-Kushleyev Thank you for sharing the files and the support, I was able to flip the video by using the flip file for camera 1. Now it is working fine.

    • P

      voxl-camera-server segmentation fault

      • • psafi
      4
      0
      Votes
      4
      Posts
      564
      Views

      Alex KushleyevA

      @psafi ,

      There was a libmodal-pipe library update earlier this week, so if you have updated that library on your VOXL2, then any other library or app (which uses libmodal-pipe) that you deploy to that VOXL2 needs to be built against the same version of libmodal-pipe.

      So if you want use the latest dev version, you would update the drone.

      make sure you are using dev for apt sources:
      in /etc/apt/sources.list.d/modalai.list:

      deb [trusted=yes] http://voxl-packages.modalai.com/ ./dists/qrb5165/dev/binary-arm64/

      then update libmodal-pipe on VOXL2, this should also update any other packages that depend on it.

      apt update apt install libmodal-pipe

      When building your application using voxl-cross docker, make sure you run the following in order to get the latest deps from dev:

      ./install_build_deps.sh qrb5165 dev

      Most of the time you can get away not doing this, but this time there was an interface change in libmodal-pipe, so a mismatch occurred.

      Alex

    • Y

      VOXL2 IMX412 Camera "Received 0 buffers" Error

      • • ysc
      14
      0
      Votes
      14
      Posts
      1932
      Views

      VinnyV

      Hi @ysc
      We do not need it back. Please keep it for mechanical reference.
      Glad we were able to help you out here.

      Thanks!

    Powered by NodeBB | Contributors