OPT3101: Calibration Issue

Hi Alex,

This is a separate question.

Now the register read write are ok.

Previously I think is hardware problem.

Thanks.

Hi Alex,

For the magnitude, previously I did not set the linker flag for printf_float on my compiler.
But even I have set that, it still cannot print out double, so I change the magnitude to float.

So these are the crosstalk reports:

----------------------
Crosstalk Class Report 0
----------------------
I=-14517
Q=2100
xtalkScale=0
illumXtalk=0
illumScale=0
illumDac=0
tmain=0
tillum=0
shiftIllumPhase=0
commonScale=0
Magnitude=48.19
----------------------

----------------------
Crosstalk Class Report 1
----------------------
I=-22176
Q=18431
xtalkScale=0
illumXtalk=1
illumScale=0
illumDac=2
tmain=2314
tillum=2458
shiftIllumPhase=0
commonScale=0
Magnitude=92.54
----------------------

----------------------
Crosstalk Class Report 2
----------------------
I=-16478
Q=10653
xtalkScale=0
illumXtalk=1
illumScale=2
illumDac=1
tmain=2312
tillum=2458
shiftIllumPhase=0
commonScale=0
Magnitude=63.52
----------------------

And the phase offset reports:

-------------------------
Phase Offset Class Report-1
-------------------------
phaseOffset=39823
referenceDistanceInCodes=0
illumScale=0
illumDac=0
illumDCdac=0
freqCount=16384
shiftIllumPhase=0
data=
-----------------------

-------------------------
Phase Offset Class Report-2
-------------------------
phaseOffset=16685
referenceDistanceInCodes=0
illumScale=0
illumDac=0
illumDCdac=0
freqCount=16384
shiftIllumPhase=0
data=
-----------------------

So according to the user guide, crosstalk lover than 200 supposed to be very good.

I will try to use the new SDK.

Thanks.

Hi Alex,

I have a quick look at the new SDK, in the calibrationSession_firstTimeBringUp() now it has the loadIllumCrosstalkSet() loadPhaseOffsetSet() which write the values into the chip registers.

Previously I have modified the old SDK to do this as well. However the phase reading is still random.

In the new SDK Users Guide, in step 1 simple bring-up, it requires calibration for a few known fixed distances. However, i check the SDK code, the manuallySetReferenceDistances() function is only called by PhaseTemp calibration and PhaseAmbient calibration. According to the user guide, these two are not mandatory for testing and evaluation. Is there a mistake in the user guide or SDK?

So must I to do this phase offset calibration for different distances for a quick test? And how to do it without varying the temperature and ambient?

Ok, I noticed that there are some new functions in the calibrationSession_firstTimeBringUp() which are not available in the previous SDK.

this->measureIllumCrosstalkSet();
this->loadIllumCrosstalkSet();
this->measurePhaseOffsetSet();
this->loadPhaseOffsetSet();

Now, I can do a simple calibration. I can have phase reading changing according to distance.

If I use HDR mode, other than doing calibration for TX0, do I need to calibrate TX1 as well?
So for near distance the TX0 is illuminated and for far distance the TX1 current is diverted to the same diode. Does it work like that.

But my TX1 is set to inactive so the calibration does not go into the loop.

Another question is: Is there any register that indicates whether low or high current is being used? So that I can know at what distance it switches the illumination current.

Hi,

Do i need to perform calibration for TX1 if i am using HDR mode? In the sample TX0 is short distance and TX1 is long distance.

this->refDistancesInMM[0][0]=10;
this->refDistancesInMM[0][1]=20;
this->refDistancesInMM[1][0]=80;
this->refDistancesInMM[1][1]=120;
this->refDistancesInMM[2][0]=0;
this->refDistancesInMM[2][1]=0;