Navigation

    VEYE IMAGING Forum

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

    I2c tools failed

    VEYE MIPI camera
    2
    21
    2041
    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.
    • V
      Viktor last edited by Viktor

      Hi,

      Trying to set fixed fps. First try to read:
      sudo ./veye_mipi_i2c.sh -r -f devid
      ====I2C write:<0x3b> <0x7> <0xfe>====
      device id is 0x 0
      Failed to write register index 0

      Device is on the bus 6 addr 3b present UU

      Have copied i2c folder from git bsp for veye and chmod +x.

      Dmesg:

      [25639.695508] i2c i2c-6: Setting clock rate 100000 on next transfer
      [25639.698513] tegra-vii2c 546c0000.i2c: no acknowledge from address 0x3b
      [25639.711008] tegra-vii2c 546c0000.i2c: no acknowledge from address 0x3b
      [25639.720439] tegra-vii2c 546c0000.i2c: no acknowledge from address 0x3b
      [25639.731618] tegra-vii2c 546c0000.i2c: no acknowledge from address 0x3b
      [25639.760191] tegra-vii2c 546c0000.i2c: no acknowledge from address 0x3b

      V 1 Reply Last reply Reply Quote 0
      • V
        Viktor @Viktor last edited by Viktor

        Have added -d -b:

        sudo ./veye_mipi_i2c.sh -r -f devid -b 6 -d 0x3b
        ====I2C write:<0x3b> <0x7> <0xfe>====
        device id is 0xc8
        Failed to write register index 0

        sudo ./veye_mipi_i2c.sh -r -f hdver -b 6 -d 0x3b
        ====I2C write:<0x3b> <0x7> <0xfe>====
        hardware version is 0xc8
        Failed to write register index 0

        Direct bin run:
        out=$(./i2c_read 6 0x3b 0x01)
        echo $out
        Using i2C device /dev/i2c-6 ====I2C read:<0x3b> <0x1> <0x1>==== Read i2c addr 3B

        Tell me please, what is default AE/framerate state?

        V 1 Reply Last reply Reply Quote 0
        • V
          Viktor @Viktor last edited by Viktor

          Tried bus 7:

          sudo ./veye_mipi_i2c.sh -r -f devid -b 7
          ====I2C write:<0x3b> <0x7> <0xfe>====
          device id is 0x 6
          sudo ./veye_mipi_i2c.sh -r -f hvdev -b 7
          ====I2C write:<0x3b> <0x7> <0xfe>====
          sudo ./veye_mipi_i2c.sh -r -f hdver -b 7
          ====I2C write:<0x3b> <0x7> <0xfe>====
          hardware version is 0x 3

          It works now.

          V 1 Reply Last reply Reply Quote 0
          • V
            Viktor @Viktor last edited by Viktor

            I wrote mshutter to 0x41 for constant 25 fps, am i right?

            Cause in low light i have high exposure.

            night

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

              @viktor
              This camera is fixed frame rate. You do not need to change the exposure time for that.
              I suggest you use default parameters first, and change if necessary.

              Please use videofmt for 25fps. It is 30fps by default.
              http://wiki.veye.cc/index.php/VEYE-MIPI-290/327_i2c/zh#videoformat

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

                @veye_xumm Ok, I tryed wdmode, Pal and mshutter. And now it is good night picture.

                V 1 Reply Last reply Reply Quote 0
                • V
                  Viktor @Viktor last edited by Viktor

                  Hi Meng,

                  Can you explain what parameter makes that effect with multiple shadows on image?

                  alt text

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

                    @viktor

                    Please try close wdr.
                    http://wiki.veye.cc/index.php/VEYE-MIPI-290/327_i2c/zh#wdrmode

                    Because WDR uses two frames of data at different time points to be merged into one frame.
                    If the exposure time is long and the vehicle is fast, there will be problems in your image.You can also try to reduce ghosting by reducing the exposure time without turning off WDR.

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

                      Ok, and which parameter controls exposure in i2c?

                      Like on CS?

                      ./cs_mipi_i2c.sh -w -f aetime -p1 XXX
                      range:(100,1/framerate]

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

                        @viktor
                        The parameters of the veye series are not as flexible as those of the cs series, and the parameter you want is mshutter.

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

                          Ok. Have tried mshutter, but shadows presents in all cases.

                          If i write mshutter 0x46( 1/1000 ) i expect very short exposure and more dark image. It is ok because we are using light at night.

                          But at daylight frame is over exposured. So works only 0x40 (auto shutter). Then at night we have this effect: http://forum.veye.cc/post/185

                          Here is only mshutter auto:

                          alt text

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

                            @viktor said in I2c tools failed:

                            Have tried mshutter, but shadows presents in all cases.

                            Pls try close wdr as I suggested before.

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

                              Wdr already closed.
                              May be i should restart system?

                              Pal i set before run programm.
                              But other controls can i set before too?

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

                                @viktor

                                1. pls post your cmd to close wdr.
                                2. pls try close 3d denoise.
                                V 2 Replies Last reply Reply Quote 0
                                • V
                                  Viktor @veye_xumm last edited by

                                  This post is deleted!
                                  1 Reply Last reply Reply Quote 0
                                  • V
                                    Viktor @veye_xumm last edited by

                                    Here is cmd:
                                    sudo ./veye_mipi_i2c.sh -w -f videoformat -p1 PAL
                                    sudo ./veye_mipi_i2c.sh -w -f wdrmode -b 7 -p1 0x00
                                    sudo ./veye_mipi_i2c.sh -w -f mshutter -b 7 -p1 0x40

                                    alt text

                                    So it is a daylight. Sensor has auto shutter mode, cars speed is slow because it is parking barrier.

                                    Why is double image?

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

                                      @viktor said in I2c tools failed:
                                      please add this one :
                                      ./veye_mipi_i2c.sh -w -f denoise -p1 x00 -b7

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

                                        Thanks. Looks like fixed.
                                        alt text

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

                                          @viktor
                                          OK. So 3D denoise is the key. You can try to have a low level 2d denoise.

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

                                            Thank you Meng.

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