2,008
edits
Changes
Jump to navigation
Jump to search
Line 347:
Line 347: + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
→mshutter
|}
|}
=====cameramode=====
Requirements：hdver >= 0x3
<code>./veye_mipi_i2c.sh -r -f cameramode</code>
<code>./veye_mipi_i2c.sh -w -f cameramode -p1 [value]</code>
{| class="wikitable"
!value
!description
|-
|0x0
|Stream mode
|-
|0x1
|Capture mode
|}Stream mode: stream output
Caputre mode: output the next frame each '''capture''' cmd.
=====notf=====
Requirements：hdver >= 0x3, effective in Stream mode
Number of dropped frames
It is a method of framerate control, output one frame,discard '''notf''' frames,output next frame, and so on.
''actual framerate = original framerate /（1+notf）''
For example，if the original framerate is 30fps, set '''notf''' to 2, then ''actual framerate'' is 10fps.
<code>./veye_mipi_i2c.sh -r -f notf</code>
<code>./veye_mipi_i2c.sh -w -f notf -p1 [value]</code>
'''ntof''' range is [0-0xFF]， default 0.
=====capture=====
Requirements：hdver >= 0x3, effective in Capture mode
<code>./veye_mipi_i2c.sh -w -f capture</code>
Output the next frame. This cmd does not interfere the sensor, it just output the next frame (the newest frame).
So it is not trigger mode, there will be a delay[0,1/framerate] between the cmd and the frame exposure.
It is applicable to those that do not require a high level of real-time performance.
=====csienable=====
Requirements：hdver >= 0x3
<code>./veye_mipi_i2c.sh -r -f csienable</code>
<code>./veye_mipi_i2c.sh -w -f csienable -p1 [value]</code>
{| class="wikitable"
!value
!description
|-
|0x0
|suspend csi output
|-
|0x1
|enable csi output
|}default: 0x0
Note: This is not low power mode, the camera is still working.
<br />
<br />