Navigation

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

    UNSOLVED GX-MIPI-IMX662 can't save fps parameter

    VEYE MIPI camera
    2
    16
    1954
    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.
    • veye_xumm
      veye_xumm @alex_ai last edited by

      @alex_ai

      You need to upgrade your camera firmware. Please refer to the link below to download the firmware, and then follow the subsequent link for the upgrade procedure.

      https://www.mediafire.com/folder/4tov5s500gaif/camera_firmware_upgrade_images

      https://wiki.veye.cc/index.php/GX_camera_firmware_update_manual

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

        Hi @veye_xumm, I'm already on the latest version of firmware:

        $ ./gx_mipi_i2c.sh -r version -b 4
Read version is C 01.14 and L 01.11

        Anyway it is not critical issue for me.
        I'm trying this new GX-MIPI-IMX662 as improved version of VEYE-MIPI-IMX462 for meteors detection and can't configure with same way.

        If turn off denoise_strength_3D the video image is very noisy and as in gx_mipi_i2c no feature to read sensor registers, can I ask to you confirm that:
        In low light environment ISP enables HCG mode (register FDG_SEL0 0x3030 sets to 0x01) ?

        Maybe you have other recommendations like for IMX462 in this post :
        VEYE-MIPI-IMX462 - manual gain not consistent

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

          @alex_ai said in GX-MIPI-IMX662 can't save fps parameter:

          Anyway it is not critical issue for me.
          I'm trying this new GX-MIPI-IMX662 as improved version of VEYE-MIPI-IMX462 for meteors detection and can't configure with same way.
          If turn off denoise_strength_3D the video image is very noisy and as in gx_mipi_i2c no feature to read sensor registers, can I ask to you confirm that:
          In low light environment ISP enables HCG mode (register FDG_SEL0 0x3030 sets to 0x01) ?
          Maybe you have other recommendations like for IMX462 in this post :

          The issue where the FPS setting cannot be saved is likely because your module is our first version, and the firmware is not fully refined. You can try restoring the factory default settings and then test again.
          https://wiki.veye.cc/index.php/Gx_mipi_i2c.sh_user_guide#factoryparam

          The GX series and the VEYE series are completely different. If you would like to manually set the exposure time and gain, that is fully supported as well. Please refer to the section about expmode metime mgainin the following link.

          https://wiki.veye.cc/index.php/Gx_mipi_i2c.sh_user_guide

          I am currently on the Spring Festival holiday. Maybe replay late.

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

            @veye_xumm happy holidays!
            Yes, I tried manual and auto gain/expmode and it works as expected.

            For meteors detection I don't need use denoise3d (or use small value ), as it blurs fast moving objects, but without it the image very noisy, which is probably related to HCG and LCG modes of sensor (as it was for my IMX462M camera and you provided custom firmware with enabled HCG), and it is working perfectly on VEYE IMX462 cameras.

            For now it has quality of usual IP camera with same sensor (with denoise3d for night sky), will wait, probably it will be improved in future.
            Thank you!

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

              @alex_ai In the current program, HCG will be automatically enabled when the gain is higher than 26 dB — you can give it a try.

              Also, please try turning off the 3D noise reduction.

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

                @veye_xumm yes, you are right, I checked image in 25 and 26 dB - and it is switching.

                Probably I used high digital gain (because brightness low than from IMX462 in same gain value) and it produces high level of noise.

                About denoise, in IMX462 I'm using 0x02, but not sure what is MIDDLE value, because in IMX662 denoise_strength_3D with 128 produces different picture and I decreased to 40 to have something similar

                0x02	NR 2D Mode = OFF; NR 3D Mode = MIDDLE

                Will test couple nights. Thank you.

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

                  @alex_ai OK, the GX series and the VEYE series use completely different ISP solutions, so their parameters do not correspond one-to-one. I look forward to your test results.

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

                    @veye_xumm found what was wrong,
                    high level of noise produced gamma_index = 1 (default value), other looks good.

                    veye_xumm 2 Replies Last reply Reply Quote 0
                    • veye_xumm
                      veye_xumm @alex_ai last edited by

                      @alex_ai Thank you for your feedback; we will look into this issue.

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

                        @alex_ai I used firmware version 1.14 for comparison and did not observe any significant noise changes in gamma mode 1 compared to other modes. Could you provide your specific usage parameters and environment?

                        A 2 Replies Last reply Reply Quote 0
                        • A
                          alex_ai @veye_xumm last edited by

                          Hi @veye_xumm, I didn't say that this is issue, this parameter needs to be changed only in case video recording of the night sky (meteor detection)

                          From issues what I noticed:

                          • can't save fps - always 60 after power on

                          • Sometimes saved parameters resets to default (noticed when set metime to 33333 but forgot set fps 30 before) and manual expmode switched back to auto

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

                            Hi @veye_xumm, I'm still trying to configure imx662 for night capturing (meteor detection) and probably you can help me to clarify what is wrong.

                            I have several cameras from VEYE (imx462 and imx462 mono) and also imx662 mono from another vendor.

                            And for all cameras configuration pretty same - use 30fps, exposure time 33333 and gain 30Db for mono version and up to 34Db color version (this range approximately within analog gain).

                            What I see in GX imx662 - for same parameters image too dark, some brightness I can get from gamma_index (with value 5 or 10) but it still not enough

                            To get required brightness of image I have to increase gain to 45 which leads to boost digital gain and as result more noise, more hot pixels and overbrighted (oversized) stars.

                            Questions:

                            1. What could be wrong? (imx662 mono works as expected, not sure it is sensor issue)
                            2. Can I read sensor registors same as on imx462?

                            My current config (Raspberry Pi 5, Trixie) :

                            ./gx_mipi_i2c.sh -w fps 30 -b $i2cBus
./gx_mipi_i2c.sh -w expmode 0 -b $i2cBus
./gx_mipi_i2c.sh -w metime 33333 -b $i2cBus
./gx_mipi_i2c.sh -w mgain 34 -b $i2cBus
./gx_mipi_i2c.sh -w denoise_strength_3D 0 -b $i2cBus
./gx_mipi_i2c.sh -w denoise_strength_2D 0 -b $i2cBus
./gx_mipi_i2c.sh -w sharppen 30 -b $i2cBus
./gx_mipi_i2c.sh -w gamma_index 5 -b $i2cBus
./gx_mipi_i2c.sh -w daynightmode 1 -b $i2cBus

                            Example of image in same time and same parameters (gain 34) for:
                            GX IMX662
                            Screenshot 2026-03-19 at 19.24.55.jpg
                            VEYE IMX462
                            Screenshot 2026-03-19 at 19.21.16.jpg

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

                              @alex_ai First, let me explain the gain configuration logic for the GX-MIPI-IMX662. The IMX662 features 30dB of Analog Gain and supports High Conversion Gain (HCG). The HCG function acts as an amplification during the sensor's analog signal readout, equivalent to 15.3dB.
                              Therefore, when we configure the "Again" parameter, the actual range is [0, 45.3dB]. This means you can set the Analog Gain up to 45dB without enabling Digital Gain (Dgain).
                              Currently, our firmware integrates HCG into the "Again" setting, which may have caused some confusion during your testing.
                              As for the feature to read sensor registers, I have added it to the development roadmap. It will be provided later via a firmware update package.

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