cam does not seem to be alive issue

Alex Kushleyev

@giladWDS , this is strange. I can set IMX412 to any rate I want, however I am using different sensormodule files - can you please try to use ones from :

/usr/share/modalai/chi-cdk/imx412-fpv/com.qti.sensormodule.imx412_fpv_0.bin
/usr/share/modalai/chi-cdk/imx412-fpv/com.qti.sensormodule.imx412_fpv_2.bin

instead of com.qti.sensormodule.imx412_0.bin com.qti.sensormodule.imx412_2.bin (remove or rename these first).

please note that it is possible that the "fpv" version of the sensormodules may not have the full resolution in your older system image (latest ones do), which you can check using voxl-camera-server -l, but i think it should..

Edit: i also tried the modules you used, and works fine for me (i tested using a single camera)

One more thing to try is to lock camera server to faster cpu cores, which can be done in the following way from command line (you should stop the camera server service first):

taskset --cpu-list 4-7 voxl-camera-server

If this still does not work, please provide output of dmesg and logcat saved to separate files, so i can potentially see the reason for the crash. Thanks! (well, even if one of the solutions works, i would still be curious what error you were getting before!)

Alex

giladWDS

@Alex-Kushleyev
It would take some time to do this since I found a workaround compiling the camera server from source with a small fix:
I changed the hal3_camera_mgr.cpp
from:
int32_t frame_rate_rate[] = {fps,fps};
into:
int32_t frame_rate_rate[] = {1,30};
I know this is hacky and will probably bite me if I try to put higher fps for low fps cameras like a tof or something but it works for now.
I will get back to it and update.

Alex Kushleyev

@giladWDS , thanks for the udpate!

I believe we had to use the following line in order to enable fps higher than 30 (or higher than 60, i forget), otherwise the high fps was not working.

int32_t frame_rate_rate[] = {fps,fps};

We will keep this in mind, however I am not able to reproduce your issues, so we'll just keep this conversation open.

Alex

giladWDS

@Alex-Kushleyev hi
I just stumbled upon the same bug with our voxl-flight-deck module that also refuses to downscale the fps.

Alex Kushleyev

@giladWDS , can you please provide minimal instructions to reproduce on voxl2? I can try it from sdk install, then configure cameras, modify config to lower fps and test.

Regarding flight deck, is it voxl2 flight deck or voxl1?

Alex

Alex Kushleyev

Perhaps the solution will be to check if desired fps is less than 30, then use the different fps range, but I would like to reproduce first, since i am able to set the fps correctly below 30 as is.

giladWDS

@Alex-Kushleyev
the flight-deck is a voxl2 unit (qrb chip)
with voxl-camera-server 1.8.9 on 1.1.2 SDK
other than that one imx412 is enough for the server to crash but let me know if you want the full config and/or driver list

Alex Kushleyev

@giladWDS ,

Is it possible for you to try the same test on the latest SDK, at least 1.3.3 or 1.3.5 ?

There have been many fixes and updates since 1.1.2 and 1.2.0.

I just tested again on our latest camera server and no issue running 5 or 10hz preview at full resolution 4056x3040.

Alex

giladWDS

@Alex-Kushleyev
I will test it with the flight deck and let you know as soon as I can

Alex Kushleyev

@giladWDS , I believe i was able to reproduce the issue. It seems you cannot set the fps lower than 15fps only when you have raw preview enabled and no other streams that use ISP are running. Can you please confirm that this is the case?

If you have non-raw preview or other streams enabled like small or large video, then what happens the pipeline will actually drop frames to achieve the desired fps. So it is not ideal, that is to say that the camera is still sending higher fps, but the frames are dropped. However, the overhead for receiving extra frames and dropping them at lowest level is not too big. I will investigate if we can actually set the camera to run at the desired lower fps.

I am pretty sure that i can fix it, perhaps using the fix you already found, but can you please confirm that this is your camera configuration, if possible just paste your hires camera config here. Thanks!

Alex