ModalAI Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login
    1. Home
    2. AidanGallagher
    3. Topics
    A
    • Profile
    • Following 0
    • Followers 0
    • Topics 4
    • Posts 21
    • Best 0
    • Controversial 0
    • Groups 0

    Topics created by AidanGallagher

    • A

      VOXL 2 Ethernet and USB Hub Add-on with Doodle lab radio

      VOXL Accessories
      • • • AidanGallagher
      14
      0
      Votes
      14
      Posts
      231
      Views

      VinnyV

      Hi @AidanGallagher
      That USB2 port Port, J12, on M0062 is not much different than many other expansion board USB ports. It goes through a HUB, and as Tom pointed out, if you use M0130, your setup will simplify.
      M00130 is the only USB2 product we have that can power the Doodle directly: https://docs.modalai.com/expansion-design-guide/#usb-expansion-over-j3--j5
      a205f92a-157c-434b-a197-e935fa7ed148-image.png
      I'm not entirely sure either why your M0062 will not work, but I'm thinking it may be something with the grounding and VBUS connection due to the external board you use for power, and it not sharing a ground with the M0062 where the USB comes from. For example, our MCBL-00085-1 handles all that: https://docs.modalai.com/cable-datasheets/#mcbl-00085
      Our USB3 debug board does not have a current limiting IC like M0062 has, and will not impact USB operations. However, with M0062, since it goes through the hub, and it has power control, if anything goes wrong with power or ground, the port may be disabled.
      I would first try to see if your J12 port works normally, with a thumb drive for example (or I think you did that with a WiFi and were good). Then, if you want to try to share some more ground connections between your M0062 and the external power supply, that could be a good test.

      But, we do suggest you change to an M0130 as you will have a much nicer setup long term.
      Hope that helps.

    • A

      IMX412-FPV

      Image Sensors
      • • • AidanGallagher
      11
      0
      Votes
      11
      Posts
      364
      Views

      Alex KushleyevA

      @AidanGallagher , I have updated the IMX412 drivers to support stable 4040x3040 60FPS.

      Just for full disclosure, the camera in this mode is slightly overclocked from 2.1Gbps / lane to 2.2Gbps MIPI bit rate (voxl2 supports up to 2.5Gbps) in order to allow sufficient time between EOF and SOF. This is within 5% of the camera spec and seems to work fine.. If you do not feel comfortable using this mode, don't :). (only the specific 4040x3040 60fps mode has been changed).

      We are going to continue testing this mode because it allows doing things like EIS at 4K60 without losing any vertical stabilization margin. If there are any issues with it, I will report back.

      By the way, for best image quality, even if you don't need 4K output, but lets say 1080p, in the case of unstabilized video (no EIS), you should select 3840x2160 input and 1920x1080 output. The debayering process loses sharpness, so going from 1920x1080 RAW -> 1920x1080 RGB is going to be worse quality than 3840x2160 RAW -> 1920x1080 RGB. For unstabilized video you do not need the full frame because the top and bottom will be cropped out anyway, so reduce the waste and not select the full frame resolution (4040x3040). You can experiment using the different input resolutions to see what output quality (sharpness) you get. There is currently no option to do output sharpening when using MISP, but we will look into in the future. The down side of using higher resolution input is increased GPU usage (should not be an issue) and longer readout time (the rolling shutter artifacts will be more pronounced).

      https://storage.googleapis.com/modalai_public/temp/imx412_test_bins/20250409/imx412_fps_eis_20250409_drivers.zip

      - 4056x3040 @ 30 16.5ms readout time - 4040x3040 @ 30, 60 16.5ms readout time - 3840x2160 @ 30, 60, 80 11.8ms readout time - 1996x1520 @ 30, 60, 120 5.5ms readout time - 1936x1080 @ 30, 60, 90, 120, 240 4.0ms readout time - 1996x480 @ 30, 480 1.8ms readout time - 1996x240 @ 30, 800 0.9 - 1.0 ms readout time
    • A

      Change the default frame rate of IMX412 and the image fov changes

      Image Sensors
      • • • AidanGallagher
      5
      0
      Votes
      5
      Posts
      171
      Views

      A

      Thanks a million @Alex-Kushleyev that certainly explains the effect - I really appreciate you taking the time

    • A

      AR0144 Tracking Camera FPS

      Image Sensors
      • • • AidanGallagher
      5
      0
      Votes
      5
      Posts
      177
      Views

      A

      I understand now @Alex-Kushleyev thanks for the explanation