Touptek ITR3CMOS01300KMA (GLUX9701BSI)

[lateralus35]

Hi,

I have a touptek ITR3CMOS01300KMA(gpixel GLUX9701BSI sensor) camera and I'm trying to run a sensor analysis on it. It keeps giving me the error that the "Exposure is too short. Reduce lighting to increase exposure to at least 0.1s". I've set my phone to the dimmest and also used multiple layer of Kleenex(to the point it is extremally dim) but still the same issue.

Also, when I use the ascom drive Sharpcap is crashing. Native drivers seems to work fine.


Thanks

[admin]

Hi,

the exposure needs to be relatively long at the start of the analysis process, since during the analysis the gain will be increased and that will reduce the exposure quite a lot. If the initial exposure is too short then the minimum exposure might be reached later on which would spoil the measurements.

You could try a sheet (or 2 or 3) of white A4 paper between the phone screen and the camera to dim the light level down, or just do away with the phone (they are a bad choice for this, since they tend to auto-adjust the screen brightness based on the environment light level, and that's the last thing you want to happen). Wait until it is dark out so that interiour room lighting is the only contribution to light, and then try experimenting with the camera in different places (under a desk, behind a monitor, in a shadowed corner, etc) until you find one with the right level. In that sort of set up it's best to sit still during the process so you don't change the light level by moving about.

It's usually best to ignore the ASCOM option for cameras that are directly supported in SharpCap. The ASCOM drivers are a great option when you want to use a camera in an application that doesn't support it directly, but the direct support almost always gives more of the camera features and better performance.

cheers,

Robin

[lateralus35]

Ended up having to use 8 layers of paper sheets.My phone was set to the lowest brightness (auto brightness turned off). That sensor is crazy sensitive.

[lateralus35]

Hi,

the exposure needs to be relatively long at the start of the analysis process, since during the analysis the gain will be increased and that will reduce the exposure quite a lot. If the initial exposure is too short then the minimum exposure might be reached later on which would spoil the measurements.

You could try a sheet (or 2 or 3) of white A4 paper between the phone screen and the camera to dim the light level down, or just do away with the phone (they are a bad choice for this, since they tend to auto-adjust the screen brightness based on the environment light level, and that's the last thing you want to happen). Wait until it is dark out so that interiour room lighting is the only contribution to light, and then try experimenting with the camera in different places (under a desk, behind a monitor, in a shadowed corner, etc) until you find one with the right level. In that sort of set up it's best to sit still during the process so you don't change the light level by moving about.

It's usually best to ignore the ASCOM option for cameras that are directly supported in SharpCap. The ASCOM drivers are a great option when you want to use a camera in an application that doesn't support it directly, but the direct support almost always gives more of the camera features and better performance.

cheers,

Robin

Here are my result. Looks like running the camera in HDR mode is the way to go. In HDR its weird that the read noise and full well do not change relative to the gain. Looks like the gain setting is locked in HDR so there is no point in changing gain in that mode? Also, sensor linearity does not look great.

Also, is the MONO16(Ultra Low Noise) the same as the Touptek "Low Noise" option?

HDR

HDR

HDR.jpg (101.58 KiB) Viewed 88 times

HDR+MONO16 (Ultra Low Noise)

HDR+LowNoise.png (69.79 KiB) Viewed 84 times

HCG

HCG

HCG.jpg (96.79 KiB) Viewed 88 times

[admin]

Hi,

I would guess that there is a bug in the SDK that is stopping the gain from working properly in HDR mode (unless that particular sensor has a fixed gain HDR mode - I have now experience with that sensor, so maybe that is the reason). You are correct that the 'Ultra Low Noise' option is the same as 'Low Noise Mode'.

Usually the cause of low linearity scores is variable illumination during the calibration process - I would tend to assume that is the cause until proven otherwise by calibrating with alternate light sources that you can be sure do not vary.

Otherwise, the two lower graphs look fairly reasonable.

cheers,

Robin