ModalAI Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login
    1. Home
    2. david.moro
    3. Topics
    D
    • Profile
    • Following 1
    • Followers 0
    • Topics 14
    • Posts 43
    • Best 0
    • Controversial 0
    • Groups 0

    Topics created by david.moro

    • D

      EIS merge

      VOXL 2
      • • • david.moro
      28
      0
      Votes
      28
      Posts
      1613
      Views

      Alex KushleyevA

      Hello @SKA,

      I just posted the IMX214 sensormodules here : https://storage.googleapis.com/modalai_public/temp/imx214_test_bins/imx214_eis_drivers_20250815.zip

      These support the new resolutions 4196x3120 and 2096x1560 needed for MISP / EIS.

      IMX214 (M0025-2) 4196x3120 - calibration file resolution 4196x3120 or 2098x1560 2096x1560 - calibration file resolution 2096x1560 or 2098x1560

      (calibration file is optional, EIS will run without one)

      I also just updated the voxl camera server (dev branch) to enable MISP support for these resolutions and also a new feature to allow specifying the bayer pattern (in case you use the flipped sensormodule).

      Here is an example snipped of voxl-camera-server.conf. The parameter bayer_type is optional and hidden by default. you can use rggb or bggr for IMX214. You can change this parameter if you see that your colors are flipped (red and blue).

      "type": "imx214", "name": "hires0", "bayer_type": "rggb"

      The performance of EIS with IMX214 has not been tuned - specifically the behavior of the ROI controller. We can come back to that if there is interest.. Mostly focusing on IMX412 with the fisheye lens for now.

      Please try and make sure you can at least make it work and we can discuss performance tuning.

      Alex

    • D

      Doodle labs Nimble radio

      Ask your questions right here!
      • • • david.moro
      3
      0
      Votes
      3
      Posts
      181
      Views

      tomT

      @david-moro We have not used that specific radio before, only the nano and mini

    • D

      Flex cable design review

      PCB Design Reviews
      • • • david.moro
      2
      0
      Votes
      2
      Posts
      342
      Views

      ModeratorM

      @david-moro Yes, absolutely. if you are OK posting it here we can take a look or if you'd like to email the schematic to contact --at-- modalai.com we could take a look that way as well

    • D

      Fisheye stereo

      Image Sensors
      • • • david.moro
      10
      0
      Votes
      10
      Posts
      501
      Views

      D

      @Alex-Kushleyev , this is fantastic. Thanks so much!

    • D

      voxl2 mini, ov9782 + hires on J6

      Image Sensors
      • • • david.moro
      7
      0
      Votes
      7
      Posts
      513
      Views

      modaltbM

      Hi @Trinadh

      Can you confirm (using voxl-version) what version you have?

      e.g. should paste this info:

      -------------------------------------------------------------------------------- system-image: kernel: -------------------------------------------------------------------------------- hw platform: mach.var: -------------------------------------------------------------------------------- voxl-suite: --------------------------------------------------------------------------------

      To confirm, you are using:
      VOXL2 Mini -> J6 -> M0135 --> JL for ov9282, and JU for IMX214?

      We don't have a binary setup for IMX214 or ov9782 on J6 upper, which is "ID 1".

      ls /usr/share/modalai/chi-cdk/ov9782 com.qti.sensormodule.ov9782_0.bin com.qti.sensormodule.ov9782_2.bin com.qti.sensormodule.ov9782_3.bin com.qti.sensormodule.ov9782_4.bin voxl2:/usr/lib/camera$ ls /usr/share/modalai/chi-cdk/imx214 com.qti.sensormodule.imx214_0.bin com.qti.sensormodule.imx214_2.bin com.qti.sensormodule.imx214_3.bin com.qti.sensormodule.imx214_4.bin

      So it seems like you would need a binary built for imx214 on "slot1", correct?

    • D

      Python MPA image example

      Modal Pipe Architecture (MPA)
      • • • david.moro
      8
      0
      Votes
      8
      Posts
      613
      Views

      Meytal LempelM

      @Alex-Kushleyev Thank you, it works!

    • D

      Next-gen TOF sensor specs

      Image Sensors
      • • • david.moro
      12
      0
      Votes
      12
      Posts
      1200
      Views

      D

      @Alex-Kushleyev , I think that is plenty for now. We will order a couple and test them. Thanks a lot!

    • D

      M0113 Image fipped

      Image Sensors
      • • • david.moro
      1
      0
      Votes
      1
      Posts
      204
      Views

      No one has replied

    • D

      Voxl2 mini support for OV9782 tracking sensor

      VOXL 2 Mini
      • • • david.moro
      2
      0
      Votes
      2
      Posts
      308
      Views

      ModeratorM

      @david-moro Yes, the VOXL 2 Mini supports OV9782

    • D

      Add mask file to QVIO algorithm

      Feature Requests
      • • • david.moro
      9
      0
      Votes
      9
      Posts
      1109
      Views

      Alex KushleyevA

      @Aaky ,

      Please check the following thread for more information: https://forum.modalai.com/topic/3459/masking-qvio/

      My suggestion:

      download the test mask from here : https://gitlab.com/voxl-public/voxl-sdk/services/voxl-qvio-server/-/blob/master/misc/mask_example_160x120.pgm . which has top half of image black (0), and bottom half white (255). values of 0 is where new features will be allowed to be detected You can use gimp, to modify the mask and before saving you can threshold it so that the values are all 0 and 255 (nothing in between, just in case). export from gimp as pgm (raw) do a test with the original mask example, make sure no features are picked up in the bottom image. This is the baseline test then try your new mask, you can also overlay the mask on top of the QVIO overlay, just like the other user did for checking.

      Also please note (from the other thread) to pay attention to the fact that QVIO mask path is relative to where qvio server starts. So if you start it as a service, it's working directory will be / but if you run it manually, the working directory will be your current directory in the terminal - the other thread explains that issue.

      Alex

    • D

      OV9782 VIO parameters

      GPS-denied Navigation (VIO)
      • • • david.moro
      7
      0
      Votes
      7
      Posts
      809
      Views

      P

      @david-moro That is my impression too, that and, it does not seem to be all that robust in general. I am very interested in using an open source VIO solution, and build it to be a mostly drop-in replacement for Qvio. I need it for high-altitude flight too, in mostly texture-less environments, a most robust solution seems necessary. I only just started looking into which methods could be interesting to use, and came across DM-VIO: Delayed Marginalization Visual-Inertial Odometry which seems to be very modern and robust. The paper for this states that it was run in real time on a 2013 mobile i7 at 2.3GHz, so I am hopeful that it could run on the VOXL 2. I would be interested in following along if any of you decide to go in another direction than Qvio.

    • D

      OV9782 VIO jumps but does not reset

      GPS-denied Navigation (VIO)
      • • • david.moro
      3
      0
      Votes
      3
      Posts
      323
      Views

      D

      @Moderator will try to on our next flight. Do you have an easy way to trigger a capture when certain conditions are met? It is hard to correlate hundred of images to the autopilot logs to find these instances. We are working on streaming the qvio-overlay as an RTSP stream down to the GCS. That might be easier.

      Unrelated question. Can the VIO algorithm use the colored images coming from the camera? If yes, is there an advantage at all?

    • D

      OV9782 tracking configuration

      Ask your questions right here!
      • • • david.moro
      8
      0
      Votes
      8
      Posts
      722
      Views

      ?

      @david-moro

      Awesome! Glad we were able to get this resolved 🙂

      Thinking about it more, this makes a lot of sense. A higher resolution camera is going to be ultra-precise in its pixel-to-world mapping meaning small inaccuracies in the grid would probably cause the model to blow up. I'll make a note to make this very clear on our documentation.

      Don't hesitate to reach out if you have any other questions. Best of luck!!

      Thomas