Navigation

    VEYE IMAGING Forum

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

    SOLVED VEYE-MIPI-IMX462 - manual gain not consistent

    VEYE MIPI camera
    2
    21
    1956
    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
      milank @milank last edited by

      @milank

      the same procedure runs on many installations using the IP camera without strange phenomenons like on the picture.
      This is the attempt to replace them by a MIPI camera.

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

        @milank Can you tell us about your curve generation method?

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

          @veye_xumm
          for this, please see:
          https://github.com/CroatianMeteorNetwork/RMS/blob/master/Utils/PlotFieldsums.py

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

            @milank

            I have provided a script in the attachment which can read the sensor registers.
            Can you please add a monitoring program in your system to monitor the following registers of the sensor: 0x14, 0x20, 0x21, 0x22, and 0x09.

            The usage of the script is: ./veye_inner.sh -r -f sns_reg -p1 [sns_reg_addr].

            Especially pay attention to whether the registers of the sensor have changed when a sudden change in brightness is detected.

            veye_inner.sh.txt

            ba48e698-8a39-4744-8157-775110757c03-image.png
            2b77e2ec-da6b-419b-b4bd-365cbef980f4-image.png
            8e18454e-7860-4fb7-a5e3-0f2b8ad933e5-image.png

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

              @veye_xumm

              fine, understood, now it is running in the background for spoken registers.
              I will come back with the results once I see the spike again.

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

                @milank
                Another change has been detected last night, around 20:44:25 UTC.
                Unfortunatelly, no change detected in spoken registers.
                The reading interval was set to 5 seconds.
                I am also attaching two full BMP images just before/after the change of brightness.![1_1678948719448_FF_CZ0004_20230315_204426_226_0277248.fits_maxpixel.bmp](Nahrávám 100%) ![0_1678948719448_FF_CZ0004_20230315_204416_011_0276992.fits_maxpixel.bmp](Nahrávám 100%)
                9743efa8-07c6-413e-8dc1-5d4275e7a452-image.png
                03/15/2023 20:44:11 reg addr 0x14 val is 0x53
                03/15/2023 20:44:11 reg addr 0x20 val is 0x1
                03/15/2023 20:44:11 reg addr 0x21 val is 0x0
                03/15/2023 20:44:11 reg addr 0x22 val is 0x0
                03/15/2023 20:44:12 reg addr 0x9 val is 0x11
                03/15/2023 20:44:17 reg addr 0x14 val is 0x53
                03/15/2023 20:44:17 reg addr 0x20 val is 0x1
                03/15/2023 20:44:18 reg addr 0x21 val is 0x0
                03/15/2023 20:44:18 reg addr 0x22 val is 0x0
                03/15/2023 20:44:18 reg addr 0x9 val is 0x11
                03/15/2023 20:44:24 reg addr 0x14 val is 0x53
                03/15/2023 20:44:24 reg addr 0x20 val is 0x1
                03/15/2023 20:44:24 reg addr 0x21 val is 0x0
                03/15/2023 20:44:25 reg addr 0x22 val is 0x0
                03/15/2023 20:44:25 reg addr 0x9 val is 0x11
                03/15/2023 20:44:30 reg addr 0x14 val is 0x53
                03/15/2023 20:44:30 reg addr 0x20 val is 0x1
                03/15/2023 20:44:31 reg addr 0x21 val is 0x0
                03/15/2023 20:44:31 reg addr 0x22 val is 0x0
                03/15/2023 20:44:31 reg addr 0x9 val is 0x11
                03/15/2023 20:44:36 reg addr 0x14 val is 0x53
                03/15/2023 20:44:37 reg addr 0x20 val is 0x1
                03/15/2023 20:44:37 reg addr 0x21 val is 0x0
                03/15/2023 20:44:37 reg addr 0x22 val is 0x0
                03/15/2023 20:44:38 reg addr 0x9 val is 0x11
                03/15/2023 20:44:43 reg addr 0x14 val is 0x53
                03/15/2023 20:44:43 reg addr 0x20 val is 0x1
                03/15/2023 20:44:43 reg addr 0x21 val is 0x0
                03/15/2023 20:44:44 reg addr 0x22 val is 0x0
                03/15/2023 20:44:44 reg addr 0x9 val is 0x11

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

                  @milank
                  FF_CZ0004_20230315_204426_226_0277248.fits_maxpixel.jpg FF_CZ0004_20230315_204416_011_0276992.fits_maxpixel.jpg

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

                    @milank
                    Hi, we guess it might have something to do with an "extra" gain in ISP, which is a bug in new_expmode that doesn't completely turn off the automatic control of the image in ISP.
                    You can try to configure it with this command and then test it again

                    . /veye_mipi_i2c.sh -w -f brightness -p10
                    

                    BTW,since you are using the camera to capture the starry sky, it is recommended that you run the following script to turn off the automatic bad point correction.

                    ./i2c_write 10 0x3b 0x0007 0xFE
                    ./i2c_write 10 0x3b 0x0010 0xDB
                    ./i2c_write 10 0x3b 0x0011 0x9F
                    ./i2c_write 10 0x3b 0x0012 0x00
                    ./i2c_write 10 0x3b 0x0013 0x00
                    ./i2c_read 10 0x3b 0x0014 1
                    
                    M 1 Reply Last reply Reply Quote 0
                    • M
                      milank @veye_xumm last edited by

                      @veye_xumm
                      fine, thank you, I will test, my init script now looks like:

                      ./veye_mipi_i2c.sh -w -f new_expmode -p1 1
                      sleep 1
                      ./veye_mipi_i2c.sh -w -f new_mshutter -p1 40000 # fixed 40 ms
                      sleep 1
                      ./veye_mipi_i2c.sh -w -f new_mgain -p1 23 # between 20 and 25
                      sleep 1
                      ./veye_mipi_i2c.sh -w -f brightness -p1 0
                      sleep 1

                      special code for sky imaging, to turn automatic bad point correction off

                      ./i2c_write 10 0x3b 0x0007 0xFE
                      ./i2c_write 10 0x3b 0x0010 0xDB
                      ./i2c_write 10 0x3b 0x0011 0x9F
                      ./i2c_write 10 0x3b 0x0012 0x00
                      ./i2c_write 10 0x3b 0x0013 0x00
                      sleep 1
                      ./i2c_read 10 0x3b 0x0014 1
                      ./veye_mipi_i2c.sh -w -f paramsave

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

                        @milank Okay, looking forward to the results of your test.

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

                          @veye_xumm
                          Hello,
                          now, it seems that this additional line did the trick.
                          No brightness drop seen anymore.
                          Thank you for your help.

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

                            @milank OK. You are welcome.

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