Initialization of Sekonix SF3325-100 camera by ini file

Hi there, our institute recently obtained a Sekonix SF3325-100 camera as part of an automotive research project. Unfortunately, we are experiencing some problems operating the camera, and hope that someone can help us.

Our situation looks like this: with low lighting (simple ceiling light in a larger room) the received camera images look apparently good (see top image with a simple testboard). But as soon as we increase the lighting with the help of a lamp, the camera will very quickly start clipping and outshine (picture in the middle).

From the data sheet of the camera we can see that the camera has a 14 bit sensor (ONSEMI CMOS Image Sensor AR0231) that outputs the pixel values in Bayer-12 format through a 12 bit serializer (MAX96705). The individual pixel values should therefore have the structure illustrated in the image at the bottom.

However, a closer analysis of the received raw data shows us that every second byte in the byte stream is always 0x00, even when the camera looks directly into a light source. Our assumption is that the camera is not properly initialized. Solectrix provided us with the attached INI file (changed ini extension to txt for upload purpose), which we load into the proFrame grabber card to initialize the camera. Is it possible that line 396 (“ADR_SENSOR 4 0x31 0xAC 0x0C 0x08 # DATA_FORMAT_BITS bayer-8bit”) in this INI file instructs the camera to provide clipped 8bit values?

GSML-CAM-SF332x.txt (24.1 KB)

Furthermore we are surprised that in the INI file many sensor commands like “ANALOG_GAIN” and “RED_GAIN” are set several times with different values. Unfortunately we don’t have any documentation about the structure of the INI file, especially which commands are possible, which registers have to be written and which value ranges are allowed in each case to initialize the sensor in a proper way.

We were suggested to ask Luke Harvey here at the Developer Forum. Hopefully someone can help us.

Hi @dahmen,

can you please provide the following info:
Hardware Platform: [Example: DRIVE AGX Xavier™ Developer Kit, DRIVE AGX Pegasus™ Developer Kit]
Software Version: [Example: DRIVE Software 10, DRIVE Software 9]
Host Machine Version: [Example: native Ubuntu 18.04]
SDK Manager Version: [Example:]

We use a setup provided by Solectrix. So I’m not sure, if ich can get all information you expect. The setup looks like this:


  • Windows 10 Pro 64bit development PC
  • The PC has a Solectrix grabber card as capture card installed
  • The capture card has an adapter installed (MAX96706 deserializer, matching the MAX96705 serializer inside the SF3325 camera)


  • We use the Solectrix proFRAME driver and API, accessed via C++

I hope this is helpful.

Hi dahmen,

Can you clarify if you are using the camera connected to a DRIVE AGX platform?

It sounds like you may need to speak with Solectrix for support on this.

Hi, a collegue initially tested the camera with a DRIVE AGX paltform and according to his statement the captured pictures were apparently good. However, the project now requires the following setup using the Solectrix capture card.

We already asked Solectrix the same questions. But we were told that they do not manipulate the camera’s sensor data, but only take care of de-/serialization and that we should therefore contact the supplier of the camera.

As already mentioned, our current setup loads the ini file attached above for initialization into the camera. The hardware commands used therein should actually be independent of Solectrix.

Doesn’t there exist some kind of interface control document for the SF3325, that documents the possible hardware commands (registers and instructions to set for example Red_Gain, Exposure, etc.) used during initialization of the sensor?

Best regards, Ulrich

Hello everyone, I wanted to ask once again if anyone has a documentation of the SF3325, in which the camera commands are documented. I need to know more about commands like this:

ADR_SENSOR 4 0x30 0x56 0x00 0x80 # GREEN1_GAIN
ADR_SENSOR 4 0x30 0x58 0x01 0x8F # BLUE_GAIN
ADR_SENSOR 4 0x30 0x5A 0x01 0x35 # RED_GAIN
ADR_SENSOR 4 0x30 0x5C 0x00 0x80 # GREEN2_GAIN
ADR_SENSOR 4 0x33 0x66 0x22 0x22 # ANALOG_GAIN

(note: ADR_SENSOR is an alias for 0x20 as sensor adress)

Hi Dahmen,

We don’t have any component involved in the setup you have described so it will be difficult for us to help. I can direct you towards Sekonix’s website, with datasheet and contact info there.