<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Machine Vision camera]]></title><description><![CDATA[Machine Vision camera]]></description><link>http://forum.veye.cc/category/10</link><generator>RSS for Node</generator><lastBuildDate>Thu, 04 Jun 2026 13:02:05 GMT</lastBuildDate><atom:link href="http://forum.veye.cc/category/10.rss" rel="self" type="application/rss+xml"/><pubDate>Tue, 14 Apr 2026 08:49:59 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Cant set RAW12 on IMX178]]></title><description><![CDATA[@sanlu 
]]></description><link>http://forum.veye.cc/topic/720/cant-set-raw12-on-imx178</link><guid isPermaLink="true">http://forum.veye.cc/topic/720/cant-set-raw12-on-imx178</guid><dc:creator><![CDATA[veye_xumm]]></dc:creator><pubDate>Tue, 14 Apr 2026 08:49:59 GMT</pubDate></item><item><title><![CDATA[MV-MIPI-SC130M autoexposure problem]]></title><description><![CDATA[@veye_xumm Hi,
Firmware update does not solve the problem, after software reset auto exposure mode works normal
]]></description><link>http://forum.veye.cc/topic/702/mv-mipi-sc130m-autoexposure-problem</link><guid isPermaLink="true">http://forum.veye.cc/topic/702/mv-mipi-sc130m-autoexposure-problem</guid><dc:creator><![CDATA[Dan]]></dc:creator><pubDate>Wed, 08 Oct 2025 09:55:08 GMT</pubDate></item><item><title><![CDATA[Assistance Needed with RAW-MIPI-IMX462M Camera Integration on NVIDIA AGX Orin]]></title><description><![CDATA[@barbanevosa
Please refer to part8:
https://wiki.veye.cc/index.php/Mv_series_camera_appnotes_4_jetson/
]]></description><link>http://forum.veye.cc/topic/701/assistance-needed-with-raw-mipi-imx462m-camera-integration-on-nvidia-agx-orin</link><guid isPermaLink="true">http://forum.veye.cc/topic/701/assistance-needed-with-raw-mipi-imx462m-camera-integration-on-nvidia-agx-orin</guid><dc:creator><![CDATA[veye_xumm]]></dc:creator><pubDate>Fri, 03 Oct 2025 11:06:05 GMT</pubDate></item><item><title><![CDATA[Capture MV-MIPI-IMX178M with OpenCV]]></title><description><![CDATA[@barbanevosa
The issue occurs because the camera sensor outputs a resolution of 3088 × 2064, but the receiving side (V4L2 buffers) aligns each line to a stride of 3136 bytes for memory alignment. When OpenCV is used directly with cv2.CAP_V4L2, it applies the width setting (3088) both to the sensor and to the buffer interpretation. Since the actual buffer has padding (3136 vs. 3088), OpenCV misinterprets the data layout, which results in visible image artifacts (stripes).
We recommend using a GStreamer pipeline to handle the stride and alignment internally, so that OpenCV receives a clean image with the correct resolution.
]]></description><link>http://forum.veye.cc/topic/697/capture-mv-mipi-imx178m-with-opencv</link><guid isPermaLink="true">http://forum.veye.cc/topic/697/capture-mv-mipi-imx178m-with-opencv</guid><dc:creator><![CDATA[veye_xumm]]></dc:creator><pubDate>Wed, 10 Sep 2025 13:37:16 GMT</pubDate></item><item><title><![CDATA[MV-MIPI-GMAX4002M compatibility with Jetson Xavier NX, Orin NX]]></title><description><![CDATA[@stiwana
@stiwana said in MV-MIPI-GMAX4002M compatibility with Jetson Xavier NX, Orin NX:

Can I use the commonly available RPi-zero Mipi camera FPC to connect the camera to Jetson Orin NX?

Yes.
@stiwana said in MV-MIPI-GMAX4002M compatibility with Jetson Xavier NX, Orin NX:

Is there anything else I can do to increase the low-light performance? Did i miss another setting that can help?

To improve performance in low-light conditions, the main methods are:

Use a lens with a smaller F-number.
In either automatic or manual exposure mode, extend the exposure time to the maximum duration you can tolerate. (Note that the exposure time cannot exceed the reciprocal of the frame rate, so you may need to adjust it accordingly based on your specific situation.)
Increase the gain.

@stiwana said in MV-MIPI-GMAX4002M compatibility with Jetson Xavier NX, Orin NX:

I do notice that at higher gain the images get these fixed patterns probably due to the FPNU or PRNU of pixel array. Is there a way to do a calibration on the image sensor to make the image response more uniform?

Sorry, we don't offer this algorithm yet.
@stiwana said in MV-MIPI-GMAX4002M compatibility with Jetson Xavier NX, Orin NX:

Is there any gstreamer pipeline I can use to get 12 bit image stream out and display it as 8bit in real time?

Sorry, we don't provide this kind of program either.
]]></description><link>http://forum.veye.cc/topic/685/mv-mipi-gmax4002m-compatibility-with-jetson-xavier-nx-orin-nx</link><guid isPermaLink="true">http://forum.veye.cc/topic/685/mv-mipi-gmax4002m-compatibility-with-jetson-xavier-nx-orin-nx</guid><dc:creator><![CDATA[veye_xumm]]></dc:creator><pubDate>Thu, 05 Jun 2025 06:53:42 GMT</pubDate></item><item><title><![CDATA[IMX296在RK3588上不出图]]></title><description><![CDATA[使用脚本可以，感谢
]]></description><link>http://forum.veye.cc/topic/670/imx296在rk3588上不出图</link><guid isPermaLink="true">http://forum.veye.cc/topic/670/imx296在rk3588上不出图</guid><dc:creator><![CDATA[xym]]></dc:creator><pubDate>Sun, 15 Dec 2024 03:27:41 GMT</pubDate></item><item><title><![CDATA[MV cameras and RK3576]]></title><description><![CDATA[@veye_xumm Thank you, graet news
]]></description><link>http://forum.veye.cc/topic/669/mv-cameras-and-rk3576</link><guid isPermaLink="true">http://forum.veye.cc/topic/669/mv-cameras-and-rk3576</guid><dc:creator><![CDATA[Dan]]></dc:creator><pubDate>Thu, 05 Dec 2024 09:53:42 GMT</pubDate></item><item><title><![CDATA[IMX178 roi problem - rpi5]]></title><description><![CDATA[@veye_xumm
Perfect. Now is working as expected. Thanks!
]]></description><link>http://forum.veye.cc/topic/655/imx178-roi-problem-rpi5</link><guid isPermaLink="true">http://forum.veye.cc/topic/655/imx178-roi-problem-rpi5</guid><dc:creator><![CDATA[sanlu]]></dc:creator><pubDate>Fri, 15 Nov 2024 15:40:42 GMT</pubDate></item><item><title><![CDATA[To get videomatrix temperature of MV-MIPI-SC130M]]></title><description><![CDATA[@victor Sorry for the late reply.
After communicating with the sensor manufacturer, I found that the built-in temperature sensor in the SC130GS is extremely inaccurate and cannot be used properly.
]]></description><link>http://forum.veye.cc/topic/639/to-get-videomatrix-temperature-of-mv-mipi-sc130m</link><guid isPermaLink="true">http://forum.veye.cc/topic/639/to-get-videomatrix-temperature-of-mv-mipi-sc130m</guid><dc:creator><![CDATA[veye_xumm]]></dc:creator><pubDate>Mon, 07 Oct 2024 06:10:54 GMT</pubDate></item><item><title><![CDATA[IMX265 -RK3568]]></title><description><![CDATA[@zang 相机是支持这个分辨率配置的。你的整个操作报什么错误吗？
可以用mv_mipi_i2c.sh脚本读取一下相机实际roi确认是否已经配置到camera里面。
另外300不利于对齐，你可以试试304
]]></description><link>http://forum.veye.cc/topic/638/imx265-rk3568</link><guid isPermaLink="true">http://forum.veye.cc/topic/638/imx265-rk3568</guid><dc:creator><![CDATA[veye_xumm]]></dc:creator><pubDate>Wed, 25 Sep 2024 02:12:23 GMT</pubDate></item><item><title><![CDATA[MV-MIPI-130M throw V-by-one]]></title><description><![CDATA[@dan
Please try this image.
export I2C_BUS=7
export WIDTH=1280
export HEIGHT=1024
export FPS=108

media-ctl -d /dev/media0 --set-v4l2 '"m00_b_mvcam '"$I2C_BUS"'-003b":0[fmt:Y8_1X8/'"$WIDTH"'x'"$HEIGHT"'@1/'"$FPS"']'

v4l2-ctl -d /dev/video0 --set-fmt-video=width=$WIDTH,height=$HEIGHT,pixelformat=GREY --stream-mmap --stream-count=-1 --stream-to=/dev/null


[image: 1721129322062-93427bda-d9b6-4263-be24-30aac77b3df5-image.png]
]]></description><link>http://forum.veye.cc/topic/616/mv-mipi-130m-throw-v-by-one</link><guid isPermaLink="true">http://forum.veye.cc/topic/616/mv-mipi-130m-throw-v-by-one</guid><dc:creator><![CDATA[veye_xumm]]></dc:creator><pubDate>Wed, 26 Jun 2024 14:10:03 GMT</pubDate></item><item><title><![CDATA[IMX462M pixelformat on RPi5]]></title><description><![CDATA[@alex_ai said in IMX462M pixelformat on RPi5:

I need wait for clear sky to test and provide feedback

Finally tested, for gain value 20 it is looks pretty same with color sensor with ISP, but background no so black as for color sensor.
For me this issue resolved, attached examples to compare  (10 seconds stacks)
IMX462 mono
[image: 1723360275505-imx462m_small.jpg]
IMX462 color with ISP
[image: 1723360306335-imx462c_small.jpg]
]]></description><link>http://forum.veye.cc/topic/606/imx462m-pixelformat-on-rpi5</link><guid isPermaLink="true">http://forum.veye.cc/topic/606/imx462m-pixelformat-on-rpi5</guid><dc:creator><![CDATA[alex_ai]]></dc:creator><pubDate>Mon, 03 Jun 2024 18:12:48 GMT</pubDate></item><item><title><![CDATA[IMX178M 触发模式，软触发会概率性无法触发]]></title><description><![CDATA[@xym 可能是pipeline效率的原因，buffer不够用导致丢帧了。
]]></description><link>http://forum.veye.cc/topic/592/imx178m-触发模式-软触发会概率性无法触发</link><guid isPermaLink="true">http://forum.veye.cc/topic/592/imx178m-触发模式-软触发会概率性无法触发</guid><dc:creator><![CDATA[veye_xumm]]></dc:creator><pubDate>Sat, 27 Apr 2024 15:35:57 GMT</pubDate></item><item><title><![CDATA[Do you have any plans to support color machine vision cameras?]]></title><description><![CDATA[@stiwana Sorry, we do have this in mind, but no actual plans or projected time of completion at this time.
]]></description><link>http://forum.veye.cc/topic/583/do-you-have-any-plans-to-support-color-machine-vision-cameras</link><guid isPermaLink="true">http://forum.veye.cc/topic/583/do-you-have-any-plans-to-support-color-machine-vision-cameras</guid><dc:creator><![CDATA[veye_xumm]]></dc:creator><pubDate>Fri, 05 Apr 2024 06:58:45 GMT</pubDate></item><item><title><![CDATA[Can I use YT1.8-2.1I lens with RAW-MIPI-AR0234M?]]></title><description><![CDATA[@veye_xumm Thanks, this should be enough I think
]]></description><link>http://forum.veye.cc/topic/576/can-i-use-yt1-8-2-1i-lens-with-raw-mipi-ar0234m</link><guid isPermaLink="true">http://forum.veye.cc/topic/576/can-i-use-yt1-8-2-1i-lens-with-raw-mipi-ar0234m</guid><dc:creator><![CDATA[Roman]]></dc:creator><pubDate>Mon, 25 Mar 2024 09:00:48 GMT</pubDate></item><item><title><![CDATA[IMX287 - 1000+ FPS Python &amp; OpenCV]]></title><link>http://forum.veye.cc/topic/572/imx287-1000-fps-python-opencv</link><guid isPermaLink="true">http://forum.veye.cc/topic/572/imx287-1000-fps-python-opencv</guid><pubDate>Wed, 20 Mar 2024 07:30:01 GMT</pubDate></item><item><title><![CDATA[硬触发设置Trigger Delay  没有起作用]]></title><description><![CDATA[@nb
https://wiki.veye.cc/index.php/Mv_mipi_camera_manual/zh#Sony.27s_Global_shutter.EF.BC.88.E5.85.A8.E5.B1.80.E6.9B.9D.E5.85.89.EF.BC.89
2.4.3
]]></description><link>http://forum.veye.cc/topic/571/硬触发设置trigger-delay-没有起作用</link><guid isPermaLink="true">http://forum.veye.cc/topic/571/硬触发设置trigger-delay-没有起作用</guid><dc:creator><![CDATA[veye_xumm]]></dc:creator><pubDate>Wed, 20 Mar 2024 07:20:23 GMT</pubDate></item><item><title><![CDATA[执行编译出来的.&#x2F;video12    800 800 60  得到的图像。像是按照4:3拉伸得到的图像，  并不是裁剪出来的800 *800的正方形]]></title><description><![CDATA[@veye_xumm 好的 感谢
]]></description><link>http://forum.veye.cc/topic/567/执行编译出来的-video12-800-800-60-得到的图像-像是按照4-3拉伸得到的图像-并不是裁剪出来的800-800的正方形</link><guid isPermaLink="true">http://forum.veye.cc/topic/567/执行编译出来的-video12-800-800-60-得到的图像-像是按照4-3拉伸得到的图像-并不是裁剪出来的800-800的正方形</guid><dc:creator><![CDATA[nb]]></dc:creator><pubDate>Mon, 11 Mar 2024 03:04:45 GMT</pubDate></item><item><title><![CDATA[获取图像的测试代码，依赖opencv4.2的动态库，测试可以正常出图，用opencv4.6的库出现cap.isOpened()返回false]]></title><description><![CDATA[@nb 您好，我遇到了类似的问题，请问一下您的解决方案就是将4.6的opencv更换成4.2的opencv吗？
]]></description><link>http://forum.veye.cc/topic/561/获取图像的测试代码-依赖opencv4-2的动态库-测试可以正常出图-用opencv4-6的库出现cap-isopened-返回false</link><guid isPermaLink="true">http://forum.veye.cc/topic/561/获取图像的测试代码-依赖opencv4-2的动态库-测试可以正常出图-用opencv4-6的库出现cap-isopened-返回false</guid><dc:creator><![CDATA[w88121446]]></dc:creator><pubDate>Fri, 23 Feb 2024 09:30:40 GMT</pubDate></item><item><title><![CDATA[yavta 工具获取的帧率只有34fps,  实际设置的是60fps的帧率]]></title><description><![CDATA[@nb 不客气。
]]></description><link>http://forum.veye.cc/topic/560/yavta-工具获取的帧率只有34fps-实际设置的是60fps的帧率</link><guid isPermaLink="true">http://forum.veye.cc/topic/560/yavta-工具获取的帧率只有34fps-实际设置的是60fps的帧率</guid><dc:creator><![CDATA[veye_xumm]]></dc:creator><pubDate>Wed, 21 Feb 2024 01:29:13 GMT</pubDate></item><item><title><![CDATA[MV-MIPI-IM256M数据格式]]></title><description><![CDATA[@张志伟 不好意思，我们现在相机本身没有图像矫正功能，也没有使用板块的ISP模块的方案。
]]></description><link>http://forum.veye.cc/topic/559/mv-mipi-im256m数据格式</link><guid isPermaLink="true">http://forum.veye.cc/topic/559/mv-mipi-im256m数据格式</guid><dc:creator><![CDATA[veye_xumm]]></dc:creator><pubDate>Mon, 19 Feb 2024 06:32:10 GMT</pubDate></item><item><title><![CDATA[RAW-MIPI-AR0234M配置为4lane模式]]></title><description><![CDATA[@veye_xumm 好的，感谢
]]></description><link>http://forum.veye.cc/topic/546/raw-mipi-ar0234m配置为4lane模式</link><guid isPermaLink="true">http://forum.veye.cc/topic/546/raw-mipi-ar0234m配置为4lane模式</guid><dc:creator><![CDATA[lizi]]></dc:creator><pubDate>Fri, 19 Jan 2024 03:06:35 GMT</pubDate></item><item><title><![CDATA[Issues with RAW-MIPI-SC132M on Jetson Nano Dev Kit]]></title><description><![CDATA[@antony
You've made a very accurate analysis and testing, which is admirable.
For this camera model, to save space, we use a double-sided contact connector, which indeed has caused some issues.  We are planning to improve this module by replacing it with a 22-pin single-sided contact connector.
I, together with our hardware colleagues, conducted an analysis, and the results align with your test findings.
After reconnecting the FFC cable correctly following a reversal, the sensor's registers and error codes did not indicate a damaged state for the camera.
[image: 1702970334043-0cc7b86d-d1f6-4833-b373-dc0dc445c5ed-f5b019a3f2a6617992ded7348331e2b.png]
In the case of reversed power connection, the pins that are actually damaged are CON_CS_D1P and CON_CSI_CLKP. Unfortunately, this issue cannot be detected through software.
]]></description><link>http://forum.veye.cc/topic/506/issues-with-raw-mipi-sc132m-on-jetson-nano-dev-kit</link><guid isPermaLink="true">http://forum.veye.cc/topic/506/issues-with-raw-mipi-sc132m-on-jetson-nano-dev-kit</guid><dc:creator><![CDATA[veye_xumm]]></dc:creator><pubDate>Tue, 12 Dec 2023 16:18:55 GMT</pubDate></item><item><title><![CDATA[orin nano4g板卡使用MV-MIPI-IMX264M的问题]]></title><description><![CDATA[@lakers
@lakers said in orin nano4g板卡使用MV-MIPI-IMX264M的问题:

我用您提供的sample中的 show.grey.py文件可以看见图像但帧率极低，用qv4l2却看不到图像，显示一片黑

python这个demo是帧率很低的。因为是纯软件跑到cpu上作的数据搬移。你回头开发自己的程序的时候，可以避免这一点。
qv4l2这个可能是因为分辨率太高了，qv4l2这个软件的兼容性的问题。
整体来看，我觉得驱动已经通了，你可以跑跑我们wiki上其他的例子了。
]]></description><link>http://forum.veye.cc/topic/473/orin-nano4g板卡使用mv-mipi-imx264m的问题</link><guid isPermaLink="true">http://forum.veye.cc/topic/473/orin-nano4g板卡使用mv-mipi-imx264m的问题</guid><dc:creator><![CDATA[veye_xumm]]></dc:creator><pubDate>Wed, 08 Nov 2023 02:07:04 GMT</pubDate></item></channel></rss>