@veye_xumm
Hi and thank you sou much!
I am Sorry for the late answer. But I am really thankful for your help.

Greetings ess

Hello @veye_xumm,

I hope you are well and the COVID-19 outbreak takes a mild course. And you stay save and healthy.
I wanted to tell you that I made a fix work with the Kernel from Allied Vision. It is just hacked together when you update your kernel we will back to switch your kernel.

Greetings ees.

Thank you so much @veye_xumm!
That would be a great help for us! We are kind of stuck.
Do we need to update the kernel then?
We actually have quite a view dozen of your cameras, and are really happy with them.

Thank you @veye_xumm,

that are grade news!
Is there a chance that you could send us the a beta version?

Thank you.
ess

Thanks for your reply @veye_xumm and sorry for the late answer.

So we got a fix with our first problem regarding the notifications.
But we are stuck with the Nvidia trigger issue. We are using Nvidea Jeston Nano.
We have stumped upon an example from Allied Vision, but they seem to solve the problem within theyer camera driver.
How have you attempted to fix this issue? Do you thin it is fixable for us without touching the camera firmware? Or do we need your Help with this?

Thank you many thanks in advance!

Greetings ess

A small side Note:
Ther is a typo in the CS-MIPI-SC132 I2C.sh user guide at the Trigger denounce section. The listed code is:

./cs_mipi_i2c.sh -w -f triggeredge -p1 enable -p2 [value]
./cs_mipi_i2c.sh -r -f triggeredge

We used:

./cs_mipi_i2c.sh -w -f tgdebncr -p1 1 -p2 [value]
./cs_mipi_i2c.sh -r -f tgdebncr 

We could not yet verify in hardware if this works but the readout seemed to work.

Hello,

we need synchronously triggered images from multiple cameras for our project.
Since we have more than one processing unit (psu) we thought to use the external hardware trigger of the SC132 cameras to trigger the cameras across the different psu simultaneously.
Now we stumbled upon tow different issues:

• is there a way for the SC132 cameras, to notify the psu (jetson) that a picture was taken. How can I access this information?
• we can read the images only after multiple triggers, a individual trigger wont be recognized. I have read that v4l2 is optimized for camera streams, not for asynchronous image streams, so the image buffer is filled with at least 3 images. Is there a way in v4l2 to directly read individual triggered images without buffering? Is there a way without v4l2 (our code is in cpp)?

I am aware that this is not directly a issue with the veye hardware but I thought maybe you have an idea.

Many thanks in advance!

Greetings ess

@veye_xumm I am sorry but I still have issues.

It seems to me like the videofmt function is not working properly. I can change the UYVY to YUYV and back with:

$  ./cs_mipi_i2c.sh -w -f yuvseq -p1 UYVY -b 8
$  ./cs_mipi_i2c.sh -w -f yuvseq -p1 YUYV  -b 8

but with vodepfmt in different versions

$ ./cs_mipi_i2c.sh -w -f videofmt -p1 1080 -p2 1280 -p3 45 -b 8
$ ./cs_mipi_i2c.sh -w -f videofmt -p1 1280 -p2 1080 -p3 45 -b 8

or even

$ ./cs_mipi_i2c.sh -w -f videofmt -p1 480 -p2 640 -p4 45  -b 8

the resolution allays stays 1080 in width and 1280 in height. It is not affected by the function.
I am grabbing and saving the images with a python script:

import cv2
cam =0 # and 1 
vid = cv2.VideoCapture(cam)
ret, frame = vid.read()
cv2.imwrite(f'cam{cam}.png',frame)	
vid.release()
cv2.destroyAllWindows()

I also tried

$ v4l2-ctl --device /dev/video0 --stream-mmap --stream-to=frame_0.raw --stream-count=1
$ convert -size 1080x1280 -depth 8 uyvy:frame_0.raw frame_0.png

and

$ convert -size 1280x1080 -depth 8 uyvy:frame_0.raw frame_0.png

but I get wrongly interpreted images.

Do you have an idea? Can I provide you with more Information?

I am sorry, but I have a further question.
I wanted to rotate the image from the sensor, from portrait to landscape.
The data sheet mentions the possibility to specify a resolution of 1280x1080@max45fps which is what I need but the images are 1080x1280.
How do you set the rotation?
I have tried it via specifying the resolution's as mentioned in my first post (this time without the Permission denied error), and tried the flipping and mirroring described in 3.33 imagedir.

Greetings and thanks in advance

@veye_xumm
Thank you so much!

I am trying to set the SC132 Camera in an landscape orientation. With resolution 1280x1080.
Sadly i am not able to read or write from the camera via the cs_mipi_i2c script. I have to cameras connekted to a Jetson Nano B01 and have verified that the Cameras are connektet and even read images from them.

dmesg | grep cssc132
[    1.848018] cssc132 7-003b: probing v4l2 sensor
[    1.848579] cssc132 7-003b: tegracam sensor driver:cssc132_v2.0.6
[    1.849221] cssc132 7-003b: read sensor id 0132 
[    1.853871] cssc132 7-003b:  camera id is cs-mipi-sc132
[    1.859165] cssc132 7-003b: Detected CS_MIPI_SC132 camera
[    1.859242] cssc132 8-003b: probing v4l2 sensor
[    1.859700] cssc132 8-003b: tegracam sensor driver:cssc132_v2.0.6
[    1.860309] cssc132 8-003b: read sensor id 0132 
[    1.864963] cssc132 8-003b:  camera id is cs-mipi-sc132
[    1.870246] cssc132 8-003b: Detected CS_MIPI_SC132 camera
[    2.030421] vi 54080000.vi: subdev cssc132 7-003b bound
[    2.031276] vi 54080000.vi: subdev cssc132 8-003b bound

sudo i2cdetect -r 8
WARNING! This program can confuse your I2C bus, cause data loss and worse!
I will probe file /dev/i2c-8 using receive byte commands.
I will probe address range 0x03-0x77.
Continue? [Y/n] y
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00:          -- -- -- -- -- -- -- -- -- -- -- -- -- 
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
30: -- -- -- -- -- -- -- -- -- -- -- UU -- -- -- -- 
40: UU -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
70: -- -- -- -- -- -- -- --                         

sudo i2cdetect -r 7
[sudo] password for schubert: 
WARNING! This program can confuse your I2C bus, cause data loss and worse!
I will probe file /dev/i2c-7 using receive byte commands.
I will probe address range 0x03-0x77.
Continue? [Y/n] y
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00:          -- -- -- -- -- -- -- -- -- -- -- -- -- 
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
30: -- -- -- -- -- -- -- -- -- -- -- UU -- -- -- -- 
40: UU -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
60: -- -- -- -- -- -- -- -- -- -- 6a -- -- -- -- -- 
70: -- -- -- -- -- -- -- --  

But I keep getting erros like :

sudo ./cs_mipi_i2c.sh -w -f videofmt -p1 1280 -p2 1080 -p3 45 -b 7
./cs_mipi_i2c.sh: 495: ./cs_mipi_i2c.sh: ./i2c_write: Permission denied
./cs_mipi_i2c.sh: 496: ./cs_mipi_i2c.sh: ./i2c_write: Permission denied
./cs_mipi_i2c.sh: 499: ./cs_mipi_i2c.sh: ./i2c_write: Permission denied
./cs_mipi_i2c.sh: 500: ./cs_mipi_i2c.sh: ./i2c_write: Permission denied
./cs_mipi_i2c.sh: 515: ./cs_mipi_i2c.sh: ./i2c_write: Permission denied
./cs_mipi_i2c.sh: 518: ./cs_mipi_i2c.sh: ./i2c_write: Permission denied
./cs_mipi_i2c.sh: 519: ./cs_mipi_i2c.sh: ./i2c_write: Permission denied
w old videofmt width 1280 height 1080 framerate 45


sudo ./cs_mipi_i2c.sh -r -f videofmt -b 7
./cs_mipi_i2c.sh: 444: ./cs_mipi_i2c.sh: ./i2c_read: Permission denied
./cs_mipi_i2c.sh: 446: ./cs_mipi_i2c.sh: ./i2c_read: Permission denied
./cs_mipi_i2c.sh: 450: ./cs_mipi_i2c.sh: ./i2c_read: Permission denied
./cs_mipi_i2c.sh: 452: ./cs_mipi_i2c.sh: ./i2c_read: Permission denied
./cs_mipi_i2c.sh: 456: ./cs_mipi_i2c.sh: ./i2c_read: Permission denied
./cs_mipi_i2c.sh: 466: ./cs_mipi_i2c.sh: ./i2c_read: Permission denied
./cs_mipi_i2c.sh: 468: ./cs_mipi_i2c.sh: ./i2c_read: Permission denied
r new type videofmt width 32382 height 32382 framerate 323.82 

I have tried all combinations with -b 7, -b 8 , -d 0x3b, -d 3b, -d 003b, with and without sudo priviledges.
Do you have an idea?

Thankyou in advance