@nimadibaj
You have implemented the function of writing 0xff to 0x000b. Similarly, proceed to write the subsequent registers as well.
The method for writing the subsequent registers is the same as that for writing the 0x0b register, but they must be written in sequence.
Addr--->data
0x10 0xDE
0x11 0xC2
0x12 0x00
0x13 0x00
@nimadibaj said in Saving VeyeMIPI parameters:
1_ Writing 0xff to 0x000b solved our problem and now the CSI-2 output of the module is in HS mode not LP mode. Thank you. Please give us a command to save this change.
Sorry, this command cannot save settings during a power outage.
@nimadibaj said in Saving VeyeMIPI parameters:
2_ We are trying to change video frame rate (now is 30fps and we need 25fps).
by these commands we cannot do this :
0x10 0xDE
0x11 0xC2
0x12 0x00
0x13 0x00
(sending Two byte, then sending next two byte and ... ).
write_videoformat()
{
local videoformat=0;
local res=0;
res=$(./i2c_write $I2C_DEV $I2C_ADDR 0x10 0xDE );
res=$(./i2c_write $I2C_DEV $I2C_ADDR 0x11 0xC2 );
if [ $PARAM1 = "PAL" ] ; then
res=$(./i2c_write $I2C_DEV $I2C_ADDR 0x12 0x0);
elif [ $PARAM1 = "NTSC" ] ; then
res=$(./i2c_write $I2C_DEV $I2C_ADDR 0x12 0x1);
fi
res=$(./i2c_write $I2C_DEV $I2C_ADDR 0x13 0x00 );
printf "w videoformat is %s\n" $PARAM1;
}
The detailed code of the i2c_write function in the above example shows the actual bytecode it sends. Specifically, i2c_write sends multiple bytes in a single standard I2C transaction to modify register values.The specific steps are the same as writing 0xff to 0x000b.
@nkos I will attempt to build a 6.x version system based on the original BSP approach.
@nimadibaj
I don't know which platform your motherboard is using, but if you have used the veye_mipi_i2c.sh script, there is an i2c_write file in that directory. You can use this file to modify the aforementioned registers.
@nimadibaj
Use the i2c_write command to change 0x000b to 0xff.
Only ISP-related parameters can be persistently saved after power-off through the paramsave command. Therefore, I recommend that you reconfigure your desired parameters in the startup script during program design.
As for which commands can be saved, you can refer to the veye_mipi_i2c.sh source code. If the corresponding read/write functions contain operations like './i2c_write $I2C_DEV $I2C_ADDR 0x10 0xDA', it indicates that the function's register belongs to the ISP category and can be saved using paramsave.
@lpcq2000 抱歉现在MCU bypass模式已经不再被支持了。我们的资料有一些迟滞，回头会更新到上面。
@siderat I think this one will work.
@siderat said in VEYE-MIPI-327E lens YT1.8-2.8I poor picture quality in the dark:
If I buy the YT0.95-4I lens with an f.095 aperture, will it improve my camera's low-light sensitivity, as in that video? Or maybe there are some other settings I'm missing.
@nimadibaj
UYVY 30fps
@nimadibaj said in Veye MIPI imx462 Defaults:
It seems that between each video line, the CSI-2 output from your module enters Low-Power (LP) mode, which causes the video stream to continuously drop in and out.
This complies with the MIPI CSI-2 standard.
@nkos Our driver code is developed based on Radxa's BSP, and the BSP development documentation can be found at the following URL:
https://docs.radxa.com/en/zero/zero3/low-level-dev/kernel
To address the issue you raised, we attempted to set up a Yocto development environment for the Radxa ZERO 3. Unfortunately, we were unsuccessful in this endeavor.
Later, we noticed Radxa's documentation regarding building Linux images with Yocto:
https://github.com/radxa/yocto-manifests
In the "List of Radxa Boards supported" section, the Radxa ZERO 3 is not listed among the supported development boards.
Therefore, we do not recommend using Yocto to build a Linux image for the Radxa ZERO 3.
@dan
Please refer to the two links below to upgrade the firmware of your camera. Then test it again.
https://wiki.veye.cc/index.php/Mvcam_firmware_update_manual
https://wiki.veye.cc/index.php/MV-MIPI-SC130M_Version_Log
@dan Please read the version number of the camera you are using and send it to me.
@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:
@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.
@nkos Apologies for the delay. I've just returned from the National Day holiday and will follow up on this matter as soon as possible.
@barbanevosa Actually, if you need to use video stream mode, it is recommended to use our color camera VEYE-MIPI-IMX462, which also supports monochrome image output.
https://wiki.veye.cc/index.php/VEYE-MIPI-IMX462_Data_Sheet
@barbanevosa
Sorry, I just got back from the National Day holiday. The images from the RAW-MIPI-IMX462M module are directly output by the sensor and do not support RAW8, only RAW10 and RAW12 data formats. This indeed makes it incompatible with universal players.
@dan
Generally, in external trigger mode, manual exposure is recommended.
This is because the algorithm of the automatic exposure mode relies on regular image input, whereas the trigger intervals in external trigger mode may be random or even very long.
If the ambient lighting in your application scenario is stable, it is still advisable to use manual exposure mode.
@stiwana
Please refer to the section below, part 8, for checking. Additionally, run sudo dmesg | grep mvcam to see if there is any output.