@xlwvu7mx
I don't think it's a cable length issue or a DTS problem. Have you tried testing with a different adapter board or a different mainboard? I tested it with an Orange Pi CM5, using a 50cm FFC cable plus a 20cm FPC cable, and the image was very stable.
@xlwvu7mx
Based on our experience, under normal circumstances an FFC cable length within 50 cm does not cause any issues. We have tested a setup with a 20 cm FFC cable + an adapter board + a 50 cm FFC cable, and it worked normally. Could you please provide some photos of the actual setup so we can take a look?
@xlwvu7mx
Hello, the MIPI data rate of the GX series products is indeed higher than that of the VEYE series: GX: 1188 Mbps, VEYE: 594 Mbps. Based on the issues you are experiencing, I mainly suspect the MIPI signal quality. Please pay special attention to the following:
What is the length of your FFC cable?
About your adaptor board:
@sheko It looks like nothing is abnormal. You haven’t installed a lens, right?
cd veye_viewer
chmod +x ./*
chmod 755 ./config/*.sh
./start_veye_viewer.sh
@sheko
Hi,
It looks like you downloaded the source code, but didn’t compile it. You can download the precompiled binary from the link below and run it directly.
https://github.com/veyeimaging/veye_viewer/releases/download/v1.1.4_rpi/veye_viewer_RaspberryPi_bin.zip
You have successfully loaded the driver and detected the camera. Please refer to the instructions for the veye_viewer client software in the previous link to directly preview the images:
https://wiki.veye.cc/index.php/Mv_series_camera_appnotes_4_rpi#veye_viewer
@sheko
The RAW-MIPI-SC132M module requires the mvcam driver, not cssc132.