Just tried to run it on Rpi4 (bookworm 6.12)
It is same: no image for setting 1 but for 0 - no jitter!

Probably this issue only for Rpi5 (trixie 6.18).

Not sure how it works for you with value 1, I tested on 2 devices and it same no image for value 1

@veye_xumm said:

Are you viewing the image via remote desktop?

yes, also just tried with hdmi - same

@veye_xumm said:

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?

yes, it works if set 0 with jitter and no image with value 1, I recorded video to demo

test_3x264.mp4.txt

@veye_xumm said:

use -w, not -r.

Yes, I know, I just wanted to confirm that nondiscontinuousmode is set to 1 :

Read Nondiscontinuous_mode is 1

I installed new driver and no differences - no video for value 1

My PiOs : 6.18.39+rpt-rpi-2712
dmesg log:

[    2.624024] gxcam 10-003b: veye gx series camera driver version: 01.00.04
[    2.624247] gxcam 10-003b: no reset gpio provided
[    2.685103] gxcam 10-003b: camera is: GXC-MIPI-IMX662
[    2.688265] gxcam 10-003b: VideoModeCap: 0x2
[    2.706466] gxcam 10-003b: gxcam_enum_controls success

example of veye_viewer and no video

Hi @veye_xumm
I tried to set value to 1

rms@raspberrypi10:~/source/raspberrypi_v4l2/gx_i2c_tools $ ./gx_mipi_i2c.sh -r nondiscontinuousmode -b 6
Read Nondiscontinuous_mode is 1

But when click "Start Show" - no video in veye_viewer (same as in python) just nothing happened (it works when back value to 0)

Maybe need also change some another parameter?

@veye_xumm said:

veye_viewer

Hi @veye_xumm, all videos captured from veye_viewer (you can see it on first video)

Hi @veye_xumm,
As I wrote - camera is static, no vibration. Turning off of 3D Noise Reduction didn't help. I also tried with test image - it also has this issue on the last line at the bottom of frame (see attached renamed to txt video file)
test_2x264.mp4.txt

Hi @veye_xumm,
I’ve just received your new sensor. While testing it, I noticed that the image keeps jumping for some reason, even though the camera is completely static. I’ve attached a sample video (renamed to txt). It looks like the image is stretching near the bottom of the frame, which creates a twitching/jittering effect. Is there any way to fix this?

Rpi5, drivers updated to recent, sensor firmware version 01.32 2.19

test_x264.mp4.txt

Hi @veye_xumm ,
All my tests for parameters denoise2d, denoise3d and sharppen already have 0 value.
Also played with all parameters in veye_viewer (very useful app) - no luck

@veye_xumm
the version is same :

rms@raspberrypi10:~/source/raspberrypi_v4l2/gx_i2c_tools $  ./gx_mipi_i2c.sh -r version
Read version is C 01.32 and L 01.19

Also updated and rebuilt source code - same result (only one difference I see : you are using gx_product_tool folder, for me it is gx_i2c_tools)

We use F0.95 lenses on our cameras and remove the IR-cut filter to capture more starlight. The downside is that we can only achieve perfect focus for either visible or infrared light, though sharp focus is still possible for each individually. In our setup, we compromise by focusing somewhere in between.

We see this exact behavior on our IMX462, IMX462 mono (VEYE), and IMX662 mono (another vendor ) sensors. However, on the color IMX662 sensor, I am unable to get a sharp focus at all. It feels as if the visible light and infrared light from the star interfere with each other simultaneously, making the image constantly blurry.

I thought I could at least use this camera with an IR-cut filter, but for some reason, the stars became extremely dim. I am not sure if this is a software issue, or if the color Starvis 2 sensor simply handles light differently.

See the sample photos below (please note - it is stack of 8 seconds) :

imx662 without IR filter and no focus

imx662 with IR filter and stars extremely dim

and my imx662 mono sensor, without IR filter

@veye_xumm yes, I want to verify camera sensors but this command doesn't work for me, that is why I asked example.

 $ sudo ./gx_mipi_i2c.sh -r snsreg 0x3070 -b 6
 Read Sensor Reg 0x3070, val=0xffffffffffffffff

Unfortunately, my night sky tests failed:

• Without an IR filter, I can't get the stars into focus for some reason—they are always blurry and haloed.

• With an IR filter, the stars are in focus but they become extremely dim.

I'll probably stick with the old IMX462 sensor for my projects.

Hi @veye_xumm,
Thank you for new update and letting me know!

On first look - the original issue was fixed - now I can save fps parameter and we could close this topic.

About night sky image, I don't see visible differences and want to play with parameters one more time and monitor camera registers.

I see was added new feature:

./gx_mipi_i2c.sh -r snsreg [sensor reg addr] -b your_i2c_bus_number

I tried check sensor gain (register 0x3070) but not sure what should be reg address, tried 0x3070 and 0x70 (seems like it is expecting value less than 0x100)

if you could provide example - it would be helpful

Thanks

Hi @veye_xumm, I'm still trying to configure imx662 for night capturing (meteor detection) and probably you can help me to clarify what is wrong.

I have several cameras from VEYE (imx462 and imx462 mono) and also imx662 mono from another vendor.

And for all cameras configuration pretty same - use 30fps, exposure time 33333 and gain 30Db for mono version and up to 34Db color version (this range approximately within analog gain).

What I see in GX imx662 - for same parameters image too dark, some brightness I can get from gamma_index (with value 5 or 10) but it still not enough

To get required brightness of image I have to increase gain to 45 which leads to boost digital gain and as result more noise, more hot pixels and overbrighted (oversized) stars.

Questions:

1. What could be wrong? (imx662 mono works as expected, not sure it is sensor issue)
2. Can I read sensor registors same as on imx462?

My current config (Raspberry Pi 5, Trixie) :

./gx_mipi_i2c.sh -w fps 30 -b $i2cBus
./gx_mipi_i2c.sh -w expmode 0 -b $i2cBus
./gx_mipi_i2c.sh -w metime 33333 -b $i2cBus
./gx_mipi_i2c.sh -w mgain 34 -b $i2cBus
./gx_mipi_i2c.sh -w denoise_strength_3D 0 -b $i2cBus
./gx_mipi_i2c.sh -w denoise_strength_2D 0 -b $i2cBus
./gx_mipi_i2c.sh -w sharppen 30 -b $i2cBus
./gx_mipi_i2c.sh -w gamma_index 5 -b $i2cBus
./gx_mipi_i2c.sh -w daynightmode 1 -b $i2cBus

Example of image in same time and same parameters (gain 34) for:
GX IMX662

VEYE IMX462

Hi @veye_xumm, I didn't say that this is issue, this parameter needs to be changed only in case video recording of the night sky (meteor detection)

From issues what I noticed:

• can't save fps - always 60 after power on

• Sometimes saved parameters resets to default (noticed when set metime to 33333 but forgot set fps 30 before) and manual expmode switched back to auto

@veye_xumm found what was wrong,
high level of noise produced gamma_index = 1 (default value), other looks good.

@veye_xumm yes, you are right, I checked image in 25 and 26 dB - and it is switching.

Probably I used high digital gain (because brightness low than from IMX462 in same gain value) and it produces high level of noise.

About denoise, in IMX462 I'm using 0x02, but not sure what is MIDDLE value, because in IMX662 denoise_strength_3D with 128 produces different picture and I decreased to 40 to have something similar

0x02	NR 2D Mode = OFF; NR 3D Mode = MIDDLE

Will test couple nights. Thank you.

@sheko
As I see your standard camera parameters are: 1080x1280 120fps
And as it configured in python script for first step try:

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

if still failing try with passing parameters to gstreamer:

cap = cv2.VideoCapture('v4l2src device=/dev/video0 ! video/x-raw,format=UYVY, width=1080, height=1280,framerate=120/1 ! videoconvert ! video/x-raw,format=GRAY8 ! appsink sync=1')

or from command line to check if gstreamer works without python

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

if still failing try RAW8 format

gst-launch-1.0 v4l2src device=/dev/video0 ! video/x-raw,format=RAW8, width=1080, height=1280,framerate=120/1 ! appsink sync=1

if still failing, can't help, I don't have this sensor.

@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