Posts made by alex_ai

@veye_xumm happy holidays!
Yes, I tried manual and auto gain/expmode and it works as expected.

For meteors detection I don't need use denoise3d (or use small value ), as it blurs fast moving objects, but without it the image very noisy, which is probably related to HCG and LCG modes of sensor (as it was for my IMX462M camera and you provided custom firmware with enabled HCG), and it is working perfectly on VEYE IMX462 cameras.

For now it has quality of usual IP camera with same sensor (with denoise3d for night sky), will wait, probably it will be improved in future.
Thank you!

@sheko please update pipeline with your camera parameters (width, height, framerate). I just copied mine.

@sheko
This is pipeline which need place to openCV instead:

cap = cv2.VideoCapture('/dev/video0')

to run it from command line you need use gstreamer, try :

gst-launch-1.0 v4l2src device=/dev/video0 ! video/x-raw,format=UYVY, width=1920, height=1080,framerate=30/1 ! videoconvert ! video/x-raw,format=GRAY8 ! appsink sync=1

Hi @veye_xumm, sorry for confusion, in previous time you guided me to install custom libcamera for veye_mvcam driver and seems like this step is outdated (but I'm still using libcamera).

@Sheko try another pipeline in openCV:

v4l2src device=/dev/video0 ! video/x-raw,format=UYVY, width=1920, height=1080,framerate=30/1 ! videoconvert ! video/x-raw,format=GRAY8 ! appsink sync=1

Hi @sheko, I had same problem with RPi 5, did you build and install libcamera from veye github repository? For some reason it has config json file only for RPi 4.

First step try run it with uncalibrated json :

rpicam-still --tuning-file /usr/local/share/libcamera/ipa/rpi/pisp/data/uncalibrated.json -t 0

Path may be different, if failed to load json file - try to find valid path.

if video opened - we need just put to same folder mvcam_mono.json (or add to libcamera source code, update meson.build and rebuild + reinstall )

and check if rpicam-hello or rpicam-still works without tuning file

I attached my current config (rename it to json) but it adopted for night sky and you need fix in json file section : exposure_modes . normal, copy it for example from se327m12.json
mvcam_mono.txt

Hi @veye_xumm, I'm already on the latest version of firmware:

$ ./gx_mipi_i2c.sh -r version -b 4
Read version is C 01.14 and L 01.11

Anyway it is not critical issue for me.
I'm trying this new GX-MIPI-IMX662 as improved version of VEYE-MIPI-IMX462 for meteors detection and can't configure with same way.

If turn off denoise_strength_3D the video image is very noisy and as in gx_mipi_i2c no feature to read sensor registers, can I ask to you confirm that:
In low light environment ISP enables HCG mode (register FDG_SEL0 0x3030 sets to 0x01) ?

Maybe you have other recommendations like for IMX462 in this post :
VEYE-MIPI-IMX462 - manual gain not consistent

Hi @sheko, I have another mono camera but probably it should be same.
I suppose camera visible by libcamera (should work something like rpicam-hello ).
And according to the error log your openCV uses Gstreamer as backend. Libcamera has plugin for Gstreamer : libcamerasrc and my pipeline looks like:

libcamerasrc camera-name="/base/axi/pcie@120000/rp1/i2c@88000/veyemvcam@3b" ! video/x-raw, width=1920, height=1080, framerate=30/1, format=UYVY ! videoconvert ! video/x-raw,format=GRAY8 ! appsink sync=1

You need just set your camera path (according to mipi port it could be i2c@88000 or i2c@80000 ) , set your camera settings (resolution, format, fps) and remove convert to GREY8 if need color image.

Hi @veye_xumm , thank you for answer, let me clarify my steps.

1. Boot raspberry pi 5
2. check current fps (it is 60):

$ ./gx_mipi_i2c.sh -r fps -b 4
Read FrameRate_Ex is 60.0000 fps

3. set current fps

$ ./gx_mipi_i2c.sh -w fps 30 -b 4
Write FrameRate_Ex is 30.0000 fps

4. check if it is set:

$ ./gx_mipi_i2c.sh -r fps -b 4
Read FrameRate_Ex is 30.0000 fps

5. Video opened with with 30fps correctly
6. save parameters to flash

$./gx_mipi_i2c.sh -w paramsave -b 4
all param saved to flash

7 . Reboot raspberry pi
8. check current fps (it is 60 again):

$ ./gx_mipi_i2c.sh -r fps -b 4
Read FrameRate_Ex is 60.0000 fps

Hi,
On my new camera GX-MIPI-IMX662 I'm trying to set fps parameter (via gx_mipi_i2c.sh from 60 to 30) and save to flash by paramsave and it is working only for current session and after restart it restored back to 60 again.

How to fix it?

@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

IMX462 color with ISP

@veye_xumm
Yes, version is 1.09 after upgrade

@veye_xumm
Hi, thank you for firmware update.
Just to double check, is HCG mode always turn on now?

Also for register 0x3009 I got value 0xffff instead ox11 but seems like HCG enabled anyway.

I need wait for clear sky to test and provide feedback

PS:
After upgrade at the end it writes: "Failed to write register" message but upgrade done , can I just ignore it?

@veye_xumm
By the way, I see that I can read registers of camera by snsreg command but can't find how to write.
Is it possible set register 0x3009 value to 0x11 to enable HCG mode?

@veye_xumm
With metime and mgain parameters I increased sensitive, but it more noisy than color sensor with ISP, anyway issue with pixel format fixed for me, thank you.

@veye_xumm
Thanks,  it means only manual gain/exposure mode.

I have one more question but it is a little bit out of topic.
 
Yesterday I tried to take pictures of the night sky to compare with 462 color sensor, even with high gain value stars are not bright as for the same parameters on 462 color (but mono should be more sensitive) . It looks like there is no switching between  LCG and HCG modes or I need to tune some other parameters.
Can you advise what could be tuned for this case?

@veye_xumm
One more question, I see now all parameters like gain and exposure managed by libcamera software according to json file, Can we use internal camera ISP for it as before?

@veye_xumm
Hi, I noticed that version of libcamera different on my screenshot (it 0.2.0 but I installed 0.3.0)
I uninstalled rpicam-apps and rebuild it from source code again and it uses my version of libcamera now.
if execute rpicam-still -v I have next error:

In commit I see added json file only to vc4 folder (for RPi4) , can we add it to pisp folder (for RPi5) it should have name : "mvcam_mono.json"? it has different format and can't use same file from vc4.

Also I managed start video by this command:
rpicam-still --tuning-file /source/libcamera/src/ipa/rpi/pisp/data/uncalibrated.json -t 0
and it works!

But better run it without additional parameters
Thank you.

@veye_xumm
Hi, it helped but I had to use 1.0.6 tag of libpisp, with the latest version I had compile errors.
Now for command : rpicam-hello -v
I have this error:

I used set media script before:

Maybe forgot something else.

@veye_xumm
Hi, thank you for update.
I'm stuck with compiling libcamera now, with same error as here : https://github.com/raspberrypi/libcamera/issues/151

Did not find solution yet, probably need play with source code, will let you know if any updates.

@sqf121
Hi, I had similar issue with another camera vendor and it was related to overlay file which was from RPi4.

And fixed by replacing :
cam0 = <&i2c_frag>, "target:0=",<&i2c_vc>
to
cam0 = <&i2c_frag>, "target:0=",<&i2c_csi_dsi0>

Did you install driver from "release" folder or built it manually from source code?
if manually you need use dts(dtbo) file from rpi-6.1.y-bookworm folder.

Correct camera location should be:
/axi/pcie@120000/rp1/i2c@88000/veyecam2m@3b
/axi/pcie@120000/rp1/i2c@80000/veyecam2m@3b

As I see your second camera on ic2@70000 similar as I had with wrong overlay file.