SOLVED Hardware Triggering for the CS-MIPI-SC132
-
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
-
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.
-
@ess said in Hardware Triggering for the CS-MIPI-SC132:
is there a way for the SC132 cameras, to notify the psu (jetson) that a picture was taken. How can I access this information?
Do you need notifications for software, or for hardware? If it's a hardware notification, I think the J7-3 strobeout pin might meet your needs.
@ess said in Hardware Triggering for the CS-MIPI-SC132:
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)?
Are you using the jetson platform? As I understand it, it's not a v4l2 problem, but a problem with nvidia's vi driver. Nvidia mentioned in their forum that their drivers don't support trigger mode now. I've made some attempts to fix this issue, and it's not completely done yet. However, this problem is solvable.
-
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.
-
@ess
Hi, thank you, it is indeed typo.
jetson supports trigger mode, which I have done research on and it has worked. The plan is to organize it and release it along with our new machine vision product line. Estimated 15 days or so. -
Thank you @veye_xumm,
that are grade news!
Is there a chance that you could send us the a beta version?Thank you.
ess -
@ess
Our company discussed and decided to bring this forward. It is expected that the version will be available to you within 10 days. -
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. -
@ess Thank you for your trust.
Sorry to inform you that we have another recent COVID-19 outbreak on our side. There will be a delay in the timing. But I will push this as soon as possible. -
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.
-
@ess
Hi, We have released our version.
http://wiki.veye.cc/index.php/VEYE_CS_Camera_source_for_Jetson#kernel_patch_for_MV_seriesPlease refer to our MV series applications document.
http://wiki.veye.cc/index.php/Mv_series_camera_appnotes_4_jetson#Trigger_mode_2I think you can just use this feature.
v4l2-ctl --set-ctrl vi_time_out_disable=1 -
@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
-
@ess You are welcome.