Mv series camera appnotes 4 rpi - Revision history

Xumm: /* Install yavta */

2026-05-07T03:42:25Z

Install yavta

Xumm: /* Connection of MV series camera and ADP-MV1-V2 */

2026-04-08T08:31:05Z

Connection of MV series camera and ADP-MV1-V2

Bluewhale: /* Connection of MV series camera and ADP-MV1-V2 */

2026-04-08T06:36:48Z

Connection of MV series camera and ADP-MV1-V2

Bluewhale: /* Hardware Setup */

2026-04-07T10:34:31Z

Hardware Setup

Bluewhale: /* Raspberry Pi 5 Setting */

2026-02-04T01:50:46Z

Raspberry Pi 5 Setting

Show changes

Xumm: /* veye_viewer */

2025-07-02T03:43:46Z

veye_viewer

Xumm: /* Check system status */

2025-07-02T03:43:25Z

Check system status

Liujiazhen: Legacy model manual There is no need for roi to set the resolution configuration. Only the built-in resolution of the camera is required

2025-05-06T09:18:04Z

Legacy model manual There is no need for roi to set the resolution configuration. Only the built-in resolution of the camera is required

Xumm at 02:52, 8 April 2025

2025-04-08T02:52:26Z

Xumm: /* Save image to file */

2025-03-23T07:20:20Z

Save image to file

@@ Line 68: / Line 68: @@
 Both are connected by a 0.5mm pitch * 30P FFC flat cable on the same surface. Pay attention to the silver contacts facing side, [https://wiki.veye.cc/index.php/ADP-MV1-V2_Adapter_Board_Data_Sheet Please refer to the physical connection diagram of the camera and the adapter plate ADP-MV1-V2.]<br />
-===== Raspberry Pi 5, Raspberry Pi Zero 2W And other Raspberry Pis with 22-pin interfaces =====
+=====Raspberry Pi 5, Raspberry Pi Zero 2W And other Raspberry Pis with 22-pin interfaces=====
 Pay attention to the silver contacts facing side.
 <br />
@@ Line 256: / Line 256: @@
 <code>sudo apt-get install v4l-utils</code>
 =====Install yavta=====
-<code>git clone <nowiki>git://git.ideasonboard.org/yavta.git</nowiki></code>
+<code>git clone <nowiki>https://github.com/veyeimaging/yavta.git</nowiki></code>
 <code>cd yavta;make</code>

@@ Line 66: / Line 66: @@
 =====Connection of MV series camera and ADP-MV1-V2=====
-Both are connected by a 0.5mm pitch * 30P FFC flat cable on the same surface. Pay attention to the silver contacts facing side, [https://wiki.veye.cc/index.php/ADP-MV1-V2_Adapter_Board_Data_Sheet Please refer to the physical connection diagram of the camera and the adapter plate ADP-MV1-V2.]<br />Raspberry Pi 5, Raspberry Pi Zero 2W And other Raspberry Pis with 22-pin interfaces
+Both are connected by a 0.5mm pitch * 30P FFC flat cable on the same surface. Pay attention to the silver contacts facing side, [https://wiki.veye.cc/index.php/ADP-MV1-V2_Adapter_Board_Data_Sheet Please refer to the physical connection diagram of the camera and the adapter plate ADP-MV1-V2.]<br />
 Pay attention to the silver contacts facing side.
 <br />

@@ Line 66: / Line 66: @@
 =====Connection of MV series camera and ADP-MV1-V2=====
-Both are connected by a 0.5mm pitch * 30P FFC flat cable on the same surface. Pay attention to the silver contacts facing side.
+Both are connected by a 0.5mm pitch * 30P FFC flat cable on the same surface. Pay attention to the silver contacts facing side, [https://wiki.veye.cc/index.php/ADP-MV1-V2_Adapter_Board_Data_Sheet Please refer to the physical connection diagram of the camera and the adapter plate ADP-MV1-V2.]<br />Raspberry Pi 5, Raspberry Pi Zero 2W And other Raspberry Pis with 22-pin interfaces
 Pay attention to the silver contacts facing side.
 <br />

@@ Line 62: / Line 62: @@
 ===Hardware Setup===
-====MV series cameras use the ADP-MV1 connection====
+====MV series cameras use the ADP-MV1-V2 connection====
-MV series cameras need to use ADP-MV1 adapter board in order to connect to Raspberry Pi.
+MV series cameras need to use ADP-MV1-V2 adapter board in order to connect to Raspberry Pi.
-=====Connection of MV series camera and ADP-MV1=====
+=====Connection of MV series camera and ADP-MV1-V2=====
-The two are connected using 0.5 mm pitch*30P FFC cable with opposite-side contacts. The cable must be inserted with the silver contacts facing outside.
+Both are connected by a 0.5mm pitch * 30P FFC flat cable on the same surface. Pay attention to the silver contacts facing side.
-{| class="wikitable"
+<br />
-!TOP
+[[File:ADP-MV1-V2 to MV-MIPI-X.png|center|thumb|ADP-MV1-V2 to MV-MIPI-X]]
-=====Raspberry Pi 5=====
+=====Raspberry Pi 5, Raspberry Pi Zero 2W And other Raspberry Pis with 22-pin interfaces=====
-The two are connected using 15Pto22P FFC cable with Same-side contacts. Pay attention to the silver contacts facing side.
+Pay attention to the silver contacts facing side.
-{| class="wikitable"
+<br />
-|-
+[[File:Pi5 compressed 4x compressed.png|alt=ADP-MV1-V2 to RPI5|center|thumb|707x707px|ADP-MV1-V2 to RPI5]]
-|[[File:ADP-MV1 to RPI5.jpg|link=http://wiki.veye.cc/index.php/File:ADP-MV1%20to%20RPI5.jpg|center|thumb|600x600px|ADP-MV1 to RPI5]]
+<br />
-====RAW series cameras directly connected to Raspberrypi====
+=====Raspberry Pi 4 And other Raspberry Pis with 15-pin interfaces=====
 ===piOS Configuration===

@@ Line 188: / Line 188: @@
 And the /dev/video0 node exists, which proves that the camera status is normal.
-===veye_viewer ===
+====veye_viewer ====
 [https://github.com/veyeimaging/veye_viewer veye_viewer] is an open-source Qt-based client application for VEYE IMAGING cameras.
 ==== State Detection and Environment Variable Configuration ====

@@ Line 188: / Line 188: @@
 And the /dev/video0 node exists, which proves that the camera status is normal.
+===veye_viewer ===
-==== '''State Detection and Environment Variable Configuration''' ====
+[https://github.com/veyeimaging/veye_viewer veye_viewer] is an open-source Qt-based client application for VEYE IMAGING cameras.
 [https://github.com/veyeimaging/raspberrypi_v4l2/tree/main/mv_tools_rpi Here], we provide an <code>mv_probe.sh</code> script that automatically detects the connected camera and configures environment variables with its default model, width, height, frame rate, and other information.
@@ Line 761: / Line 762: @@
 === Document History ===
 * 2025-03-21

@@ Line 595: / Line 595: @@
 ==== Preview ====
-<code>./mv_raspicam -t -1 -roi 0,0,3088,2064 -md 0</code>
+<code>./mv_raspicam -t -1 -md 0</code>
 where -md specifies the pixel data format.
@@ Line 616: / Line 616: @@
 ==== Save image ====
-<code>./mv_raspicam -t 1000 -roi 0,0,3088,2064 -md 0 -sr 10 -o /dev/shm/y8-3104x2064_%04d.yuv</code>
+<code>./mv_raspicam -t 1000 -md 0 -sr 10 -o /dev/shm/y8-3104x2064_%04d.yuv</code>
 -sr is the interval for storing images, one image is saved every 10 images here.
@@ Line 643: / Line 643: @@
 <code>./mv_mipi_i2c.sh -w -f trginterval -p1 1000</code>
 ====== Start acquisition ======
-<code>./mv_raspicam -t -1 -roi 0,0,3088,2064 -md 0</code>
+<code>./mv_raspicam -t -1 -md 0</code>
 ====== Perform soft trigger operation ======
@@ Line 675: / Line 675: @@
 In addition, rich trigger attributes can be set for hard triggering, such as trigger delay, signal filtering, etc.
 ====== Start acquisition ======
-<code>./mv_raspicam -t -1 -roi 0,0,3088,2064 -md 0</code>
+<code>./mv_raspicam -t -1 -md 0</code>
 ====== Perform hardware trigger operation ======

@@ Line 412: / Line 412: @@
 *raw8
-<code>v4l2-ctl -d /dev/video0 --set-fmt-video=width=$WIDTH,height=$HEIGHT,pixelformat=GREY --stream-mmap --stream-count=1 --stream-to=y8-$WIDTHx$HEIGHT.raw</code>
+<code>v4l2-ctl -d /dev/video0 --set-fmt-video=width=$WIDTH,height=$HEIGHT,pixelformat=GREY --stream-mmap --stream-count=1 --stream-to="y8-${WIDTH}x${HEIGHT}.raw"</code>
 or
@@ Line 420: / Line 420: @@
 *raw10
-<code>v4l2-ctl -d /dev/video0 --set-fmt-video=width=$WIDTH,height=$HEIGHT,pixelformat='Y10 ' --stream-mmap --stream-count=1 --stream-to=y10-$WIDTHx$HEIGHT.raw</code>
+<code>v4l2-ctl -d /dev/video0 --set-fmt-video=width=$WIDTH,height=$HEIGHT,pixelformat='Y10 ' --stream-mmap --stream-count=1 --stream-to="y10-${WIDTH}x${HEIGHT}.raw"</code>
 *raw12
-<code>v4l2-ctl -d /dev/video0 --set-fmt-video=width=$WIDTH,height=$HEIGHT,pixelformat='Y12 ' --stream-mmap --stream-count=1 --stream-to=y12-$WIDTHx$HEIGHT.raw</code>
+<code>v4l2-ctl -d /dev/video0 --set-fmt-video=width=$WIDTH,height=$HEIGHT,pixelformat='Y12 ' --stream-mmap --stream-count=1 --stream-to="y12-${WIDTH}x${HEIGHT}.raw"</code>
@@ Line 493: / Line 493: @@
 ====== Start acquisition ======
-<code>v4l2-ctl --set-fmt-video=width=$WIDTH,height=$HEIGHT,pixelformat=GREY --stream-mmap --stream-count=5 --stream-to=y8-$WIDTHx$HEIGHT.yuv</code>
+<code>v4l2-ctl --set-fmt-video=width=$WIDTH,height=$HEIGHT,pixelformat=GREY --stream-mmap --stream-count=5 --stream-to="y8-${WIDTH}x${HEIGHT}.raw"</code>
 ====== Perform soft trigger operation ======
@@ Line 513: / Line 513: @@
 ====== Start acquisition ======
-<code>v4l2-ctl --set-fmt-video=width=$WIDTH,height=$HEIGHT,pixelformat=GREY --stream-mmap --stream-count=5 --stream-to=y8-$WIDTHx$HEIGHT.yuv</code>
+<code>v4l2-ctl --set-fmt-video=width=$WIDTH,height=$HEIGHT,pixelformat=GREY --stream-mmap --stream-count=5 --stream-to="y8-${WIDTH}x${HEIGHT}.raw"</code>
 ====== Perform hardware trigger operation ======

← Older revision		Revision as of 07:20, 23 March 2025
Line 425:		Line 425:

	<code>v4l2-ctl -d /dev/video0 --set-fmt-video=width=$WIDTH,height=$HEIGHT,pixelformat='Y12 ' --stream-mmap --stream-count=1 --stream-to=y12-$WIDTHx$HEIGHT.raw</code>		<code>v4l2-ctl -d /dev/video0 --set-fmt-video=width=$WIDTH,height=$HEIGHT,pixelformat='Y12 ' --stream-mmap --stream-count=1 --stream-to=y12-$WIDTHx$HEIGHT.raw</code>
		+