@roboticsmick
You can start by checking if these power supplies are working fine. On the software side, I'd recommend restoring the defaults to give it a try.

@alex_ai You are welcome.

@alex_ai

1. Roll back yesterday's driver update. For Raspberry Pi, keep using the MIPI clock discontinuous mode.
2. Upgrade the camera firmware. Please refer to this link: https://wiki.veye.cc/index.php/GX_camera_firmware_update_manual and update the camera to version GXC-MIPI-IMX662_C1.34_L2.19_20261014_upgrade.bin.

This should resolve your issue.

It appears that the piOS update changed the MIPI signal timing requirements on the Raspberry Pi 5 (which uses the RP1 chip to receive the MIPI signal).

@alex_ai
Register 0x44c should indeed be configured to 1.
This is quite strange, as the image preview works perfectly on our end with the exact same configuration.

1. Are you viewing the image via remote desktop?
2. Under the same conditions, does setting register 0x44c to 0 produce an image (with jitter), while setting it to 1 results in no image at all?

@alex_ai
No need to set it up manually anymore! We've updated the driver, so just grab the latest code, compile it, and install it.
https://github.com/veyeimaging/raspberrypi_v4l2

@alex_ai

@alex_ai said:

./gx_mipi_i2c.sh -r nondiscontinuousmode -b 6

use -w, not -r.
-w means write.

@alex_ai
Good news — I've found a solution to the issue. The camera's MIPI signal needs to be switched to continuous clock (non-discontinuous) mode. You can do this by running the following command: https://wiki.veye.cc/index.php/Gx_mipi_i2c.sh_user_guide#nondiscontinuousmode — or alternatively by setting register 0x44c in veye_viewer.
After making the change, please use the paramsave command to save the settings to the camera.

@alex_ai Sorry, I misunderstood your setup. I've verified this on other boards, including Jetson, and it works fine. I now believe the issue is caused by image scaling in the veye_viewer client software on the latest Raspberry Pi OS. We'll fix this as soon as possible — please bear with us.

@alex_ai

I believe the issue does not lie with the camera output, but rather with the compression process after you receive the data. Please verify this using the client software available at the link below. The veye_viewer client is designed to preview raw grey format data directly, without applying any compression.

https://github.com/veyeimaging/veye_viewer

@alex_ai Apologies for the delayed response. I would like to know if there is any vibration or shake in your actual application scenario. Could you please try turning off the 3D Noise Reduction (3DNR) to see if there is any improvement?

@habreu
If you are using the RAW-MIPI-IMX462M camera module, the corresponding script is mv_mipi_i2c_new.sh. Please note that many parameters can only be modified when frame capture is stopped. For details, please refer to the following link:
https://wiki.veye.cc/index.php/Mv_mipi_i2c.sh_user_guide

@Jiangzb said:

问有适配RK3588-Linux6.1的AR0234CS驱动（裸摄像头）？

不好意思，没有。

@lpcq2000 这个不支持输出lvds信号。J1作为我们模组内部的信号，不对外公布其信号定义。

@alex_ai Sure, I'll keep an eye on this issue going forward. Thanks for your feedback.

@alex_ai
For your use case, I'd suggest giving it a try — reduce the denoise2d and denoise3d values, or even set them to 0. At the same time, you can also try lowering the sharpen value.

@alex_ai

I'd like to first confirm your firmware version with you. As shown below, everything is working fine on my end.

pi@raspberrypi:~/gx_product_tool $ ./gx_mipi_i2c.sh -r snsreg 0x3070
Read Sensor Reg 0x3070, val=0x0 
pi@raspberrypi:~/gx_product_tool $ ./gx_mipi_i2c.sh -r snsreg 0x3071
Read Sensor Reg 0x3071, val=0x0 

pi@raspberrypi:~/gx_product_tool $ ./gx_mipi_i2c.sh -r version
Read version is C 01.32 and L 01.19

Regarding the image quality during IR-cut switching, may I ask whether you are using the same IR-cut filter for both the IMX662 and the IMX462? Also, could you share some sample images with me?

@alex_ai
I would recommend using the exptime and curgain functions first to check the current performance of the camera module. If you are familiar with the sensor registers, you can verify the sensor's working status by reading registers 0x3070 and 0x3071.

@robot 有这个可能，我们很久前有一个CS-MIPI-IMX307，在某些板子上有类似的问题。

@alex_ai

We recently updated the ISP tuning. Please give it a try.

https://wiki.veye.cc/index.php/GX-MIPI-IMX662_Version_Log