Flicker Mitigation on Sekonix SF3325

The Sekonix camera seems to run in HDR mode. However I’d like to switch to flicker mitigation mode, on runtime if possible.
The parameters passed on to dwSensorSerializer_initialize don’t seem to describe these modes. Is there some document you can point me to which describes how to do this or some code snippet?
I found details on the various modes here: http://www.onsemi.com/pub/Collateral/AR0231-D.PDF
But that doesn’t cover the DriveWorks side obviously.
Thanks in advance.

Dear nbussaa,
Unfortunately, we do not support LFM mode.
May I know why you are looking for it?

Hello,
I am also very interested in using this mode. (see also: https://devtalk.nvidia.com/default/topic/1029679/drive-hardware/led-flicker-mitigation-with-nvidia-sekonix-cameras/post/5242514/#5242514)

Our application is traffic sign reading. And our tests showed, that some LED traffic signs are really not readable in the HDR mode configured by the NVIDIA driver. Therefor, we hope to get a significant improvement by this mode.

For this reason, I started to implement my own driver.
Unfortunately, I found no guidline how to do this. Some posts in this forum says, that Nvidia is working on such a guide, but it seems to be not published yet. @NVIDIA: Or is there an update regarding this topic now?
Some of the posts mentioning this :
https://devtalk.nvidia.com/default/topic/1024390/?comment=5211084
https://devtalk.nvidia.com/default/topic/1026721/?comment=5244905

One thread by myself regarding camera-driver implementation, which has no reply by nvidia until now:
https://devtalk.nvidia.com/default/topic/1031821/?comment=5249598

If there are any informations how to use a self-implemented camera-driver with DriveWorks and how to get the LED Flicker Mitigation mode up and running, please, please share it!
(My current status with the LFM Mode is: Camera-register description changed, is loaded to camera, but when streaming starts, I get PIXEL_SHORT_LINE errors

captureGetErrorStatus: ChanselFault: stream=0 vc=0 frame=1 data=0x00000200 SofTs=4314806875584 ErrTs=4314806901056
NvViErrorDecode Stream 0.0 failed: ts 4316771218304 frame 1 error 4 data 0x00000200
NvViErrorDecode CaptureError: ChanselFault (4)
NvViErrorDecode See https://wiki.nvidia.com/wmpwiki/index.php/Camera_Debugging/CaptureError_debugging for more information and links to documents.
ChanselFault : 0x00000200
    PIXEL_SHORT_LINE            [ 9]: 1
        A line ends with fewer pixels than expected.
    Current line in frame    [31:16]: 0
        
captureGetErrorStatus: ChanselFault: stream=0 vc=0 frame=1 data=0x00000200 SofTs=4316771192832 ErrTs=4316771218304
captureGetErrorStatus: ChanselFault: stream=0 vc=0 frame=2 data=0x00000200 SofTs=4315107745504 ErrTs=4315107770944
NvViErrorDecode Stream 0.0 failed: ts 4317072088192 frame 2 error 4 data 0x00000200
NvViErrorDecode CaptureError: ChanselFault (4)
NvViErrorDecode See https://wiki.nvidia.com/wmpwiki/index.php/Camera_Debugging/CaptureError_debugging for more information and links to documents.
ChanselFault : 0x00000200
    PIXEL_SHORT_LINE            [ 9]: 1
        A line ends with fewer pixels than expected.
    Current line in frame    [31:16]: 0
        
captureGetErrorStatus: ChanselFault: stream=0 vc=0 frame=2 data=0x00000200 SofTs=4317072062752 ErrTs=4317072088192
captureGetErrorStatus: ChanselFault: stream=0 vc=0 frame=3 data=0x00000200 SofTs=4315373147552 ErrTs=4315373173024
NvViErrorDecode Stream 0.0 failed: ts 4317337490272 frame 3 error 4 data 0x00000200
NvViErrorDecode CaptureError: ChanselFault (4)
NvViErrorDecode See https://wiki.nvidia.com/wmpwiki/index.php/Camera_Debugging/CaptureError_debugging for more information and links to documents.
ChanselFault : 0x00000200
    PIXEL_SHORT_LINE            [ 9]: 1
        A line ends with fewer pixels than expected.
    Current line in frame    [31:16]: 0
        
captureGetErrorStatus: ChanselFault: stream=0 vc=0 frame=3 data=0x00000200 SofTs=4317337464800 ErrTs=4317337490272

Does anybody have a hint how to solve this? By the way: The URL given by NvViErrorDecode is not valid. Perhaps somebody can point me to the new address for this?
Thank you very much!

@SivaRamaKrishna In HDR mode some traffic lights and signs that use LEDs flicker. In some cases quite significantly. LFM mode should suppress this.

@felix.elrod Have you been in contact with Sekonix about this problem? If yes, have they been helpful?

Dear nbussas,
Could you file a bug for this feature request?
Please login to https://developer.nvidia.com/drive with your credentials. Please check MyAccount->MyBugs->Submit a new bug to file bug.
Please share ID here to follow up. Thanks.

Bug-ID: 2100941

Hi,
I am having the exact same error - unfortunately, I do not seem to be able to access bug 2100941 to follow the discussion.

captureGetErrorStatus: ChanselFault: stream=0 vc=0 frame=89 data=0x00000200 SofTs=15691222569536 ErrTs=15691222571776
NvViErrorDecode Stream 0.0 failed: ts 15691255899776 frame 90 error 4 data 0x00000200
captureGetErrorStatus: ChanselFault: stream=0 vc=0 frame=90 data=0x00000200 SofTs=10241645697171 ErrTs=10241645699443
NvViErrorDecode CaptureError: ChanselFault (4)
NvViErrorDecode See https://wiki.nvidia.com/wmpwiki/index.php/Camera_Debugging/CaptureError_debugging for more information and links to documents.
ChanselFault : 0x00000200
    PIXEL_SHORT_LINE            [ 9]: 1
        A line ends with fewer pixels than expected.
    Current line in frame    [31:16]: 0

I have not been in contact to Sekonix, but I fixed it one time by myself.

If I remember it the right way, this was fixed by some modifications to clock-divider and syncronization settings.

I compared it with the template of ON Semiconductors and one time, it worked :-).

But I am sorry, I don’t remember exactly, what to set and the code is not available from my desk at the moment.

Hi Felix,
that helps a lot - I am trying to implement a different device but get the exact same error. I cannot see anywhere in the code where “1920” is defined/used (assuming PIXEL_SHORT_LINE means it is expecting a certain number of pixels in a row and receiving fewer) so it must come from some sort of calculation.

I will have a play but if you could point me to what exactly you modified (when you have time) so I can try finding the matching parameters for my device it would be extremely useful!