Navigation

    VEYE IMAGING Forum
    • Register
    • Login
    • Search
    • Categories
    • Tags
    • Recent
    • Popular
    • Users
    • WIKI
    • veye.cc

    longest exposure time

    VEYE MIPI camera
    2
    10
    547
    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
      martin last edited by

      The longest exposure time is when I use

      a) lowlight = 0x11
      b) mshutter = 0x53
      c) videoformat = PAL

      Then the exposure time should be 1/30 * 25 = 1.2 seconds.

      Is this correct?

      veye_xumm 1 Reply Last reply Reply Quote 0
      • veye_xumm
        veye_xumm @martin last edited by

        @martin
        For VEYE series, the longest exposure time is 1 second.
        For CS-MIPI-IMX307, it is 7 seconds.

        M 3 Replies Last reply Reply Quote 0
        • M
          martin @veye_xumm last edited by

          @veye_xumm thank you for the fast reply. I have a board VEYE-IMX385 using it with RPi / Buster. The settings configured with veye_mipi_i2c.sh seem to have no effect on any preview or still image generation. It always seems to set exposure time and frame rate automatically.

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

            @veye_xumm in addition I now made a new installation with Bullseye and v4l2 mode. When I use VLC for preview the camera control changes with veye_mipi_i2c.sh do apply to the preview.
            I do not understand. When using Debian Buster with driver with it's standard camera driver the veye_mipi-i2c.sh control commands do not have an effect?

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

              @veye_xumm and one more question: the c_demo codes obviously do not work in Bullseye with V4L2 drivers. Are there any c-demo codes for using the camera without any third party application (e.g. VLC, gstreamer, etc.) ?

              veye_xumm 1 Reply Last reply Reply Quote 0
              • veye_xumm
                veye_xumm @martin last edited by

                @martin said in longest exposure time:

                @veye_xumm in addition I now made a new installation with Bullseye and v4l2 mode. When I use VLC for preview the camera control changes with veye_mipi_i2c.sh do apply to the preview.
                I do not understand. When using Debian Buster with driver with it's standard camera driver the veye_mipi-i2c.sh control commands do not have an effect?

                Please use ./ camera_i2c_config to control the camera's reset pin first.

                1 Reply Last reply Reply Quote 0
                • veye_xumm
                  veye_xumm @martin last edited by

                  @martin said in longest exposure time:

                  @veye_xumm and one more question: the c_demo codes obviously do not work in Bullseye with V4L2 drivers. Are there any c-demo codes for using the camera without any third party application (e.g. VLC, gstreamer, etc.) ?

                  http://wiki.veye.cc/index.php/V4L2_mode_for_Raspberry_Pi#V4l2-ctl_usage_examples
                  Part9 and part10.

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

                    @veye_xumm thank you for your answers.
                    Is there any chance that the IMX385 sensor will be available with a CS-MIPI-IMX307-like board? I would like to have longer exposure time with sensor IMX385.

                    veye_xumm 1 Reply Last reply Reply Quote 0
                    • veye_xumm
                      veye_xumm @martin last edited by

                      @martin We are developing a new model using IMX662 on CS series platform.

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

                        @veye_xumm Glad to hear that! I would like to test it as soon as possible.

                        1 Reply Last reply Reply Quote 0
                        • First post
                          Last post