• State TI Thinks Resolved
  • Locked Locked
  • Replies 5 replies
  • Answers 2 answers
  • Subscribers 30 subscribers
  • Views 593 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

CCS/OPT3101: OPT3101 Calibration

Pritesh Patel
Intellectual 335 points
Part Number: OPT3101

Tool/software: Code Composer Studio

We have implemented OPT3101 on our custom board maintaining physical implementation of sensor IC, components and transmitter/emitters as close as possible to OPT3101EVM implementation. Now I am trying to calibrate our custom board and I have few questions regarding the calibration process:

1. In doc "How to set up and calibrate OPT3101 based systems for proximity sensing", for internal cross talk measurement using method measureAndCorrectInternalCrosstalk(), it is expected to have amplitude codes to be lower than 30 amplitude code. While running measureAndCorrectInternalCrosstalk() SDK method, the output display Magnitude. Is Magnitude in display output referred to as amplitude codes in documentation?

This is what I am getting measureAndCorrectInternalCrosstalk() SDK method for my custom board.

INFO::Performing Internal Cross talk Measurement...
INFO::Internal Cross talk Measurement Completed
      I,      Q,S, ScaledI, ScaledQ,tMain,tIlum,tMain(C),  tIlum(C),Magnitude
-008223,+004611,0,-0008223,+0004611, 8192, 0265,     +00, -111.4375, 31.7

2. To compare custom board calibration data with OPT3101EVM is it possible to run these SDK calibration steps on OPT3101EVM to see its output?

3. The calibration process is very extensive specially per design calibration to correct phase and xtalk for temperature and ambient. The temperature chamber and open space requirement are difficult to achieve. Is there any service for hire to perform full calibration for custom boards for us?

  • 0
    TI__Mastermind 25895 points

    Hi Pritesh,

    1) Yes this is magnitude. 31 or 32 is fine. What I would really be interested in is the illumination crosstalk step which is next. This depends on PCB layout which has some requirements so will show if PCB design will perform well

    2) Yes you can wire i2c from lauchpad to the EVM and run the same steps

    3) We do not have any contacts for calibration as a service currently. If you do not have a thermal chamber and unable to rent one you can use a heat gun, just making sure to have no air flow so the unit should be heated and then data collected while it self cools. This is not the best but will at least allow you to get some calibration. For open space, I assume you mean for phase calibrations, if you use a darker target it does not have to be as far away.

    I would also like to learn more about this application and use case to see if I can help further. Please send a direct message to my profile on this forum if you are able to share more details.

    Best,

    Alex

  • 0
    Intellectual 335 points

    Hi Alex,

    Here are the internal and illumination crosstalk results. I am only using one transmitter connected to TX0. Looks like Illumination Cross talk is very high.

    [Cortex_M3_0] INFO::Resetting Host
    INFO::Writing Initialization sequence I2C registers
    INFO::Performing Internal Cross talk Measurement...
    INFO::Internal Cross talk Measurement Completed
          I,      Q,S, ScaledI, ScaledQ,tMain,tIlum,tMain(C),  tIlum(C),Magnitude
    -008404,+005551,0,-0008404,+0005551, 8192, 41543,     +00, -1627.5625, 32.5

    INFO::Cover Photodiode with optical shied for illumination Cross talk measurement
    Press any Key to continue:


    INFO:Performing Illum Crosstalk for TX0 HDR 0
          I,      Q,S, ScaledI, ScaledQ,tMain,tIlum,tMain(C),  tIlum(C),Magnitude
    -009173,+029815,1,-0018346,+0059630, 2288, 0000,     +30, -128.0000,199.9

    INFO:Performing Illum Crosstalk for TX0 HDR 1
          I,      Q,S, ScaledI, ScaledQ,tMain,tIlum,tMain(C),  tIlum(C),Magnitude
    -006249,-032095,3,-0049992,-0256760, 2296, 0000,     +31, -128.0000,841.9

    WARN:Illumination Cross talk is very high. Check if Photo diode is covered well.. if so increase [force_scale_val] register by 1 count and add it to initialization method
    INFO:Performing Illum Crosstalk for TX1 HDR 0
          I,      Q,S, ScaledI, ScaledQ,tMain,tIlum,tMain(C),  tIlum(C),Magnitude
    +000069,-005205,0,+0000069,-0005205, 2288, 0000,     +30, -128.0000, 18.1

    INFO:Performing Illum Crosstalk for TX1 HDR 1
          I,      Q,S, ScaledI, ScaledQ,tMain,tIlum,tMain(C),  tIlum(C),Magnitude
    +001429,-000985,0,+0001429,-0000985, 2288, 0000,     +30, -128.0000,  4.7

    INFO:Performing Illum Crosstalk for TX2 HDR 0
          I,      Q,S, ScaledI, ScaledQ,tMain,tIlum,tMain(C),  tIlum(C),Magnitude
    +002094,-001271,0,+0002094,-0001271, 2288, 0000,     +30, -128.0000,  8.2

    INFO:Performing Illum Crosstalk for TX2 HDR 1
          I,      Q,S, ScaledI, ScaledQ,tMain,tIlum,tMain(C),  tIlum(C),Magnitude
    +002027,-001032,0,+0002027,-0001032, 2288, 0000,     +30, -128.0000,  7.0

    INFO:Completed Illumination cross talk measurement for all channels
    INFO::Loading Illumination cross talk Set
    INFO::Set target at a reference distance
    Press any Key to continue:

  • 0 in reply to Pritesh Patel
    Intellectual 335 points

    Hi Alex,

    I posted my calibration results too soon. I found the cap I was using to cover photodiode was leaking some IR light. After adding additional layers of electrical tape over the cap that covers photodiode, I am getting much lower optical crosstalk. Let me know what you think and how it compares to OPT3101EVM.

    [Cortex_M3_0] INFO::Resetting Host
    INFO::Writing Initialization sequence I2C registers
    INFO::Performing Internal Cross talk Measurement...
    INFO::Internal Cross talk Measurement Completed
          I,      Q,S, ScaledI, ScaledQ,tMain,tIlum,tMain(C),  tIlum(C),Magnitude
    -007750,+004955,0,-0007750,+0004955, 8192, 41543,     +00, -1627.5625, 30.2

    INFO::Cover Photodiode with optical shied for illumination Cross talk measurement
    Press any Key to continue:


    INFO:Performing Illum Crosstalk for TX0 HDR 0
          I,      Q,S, ScaledI, ScaledQ,tMain,tIlum,tMain(C),  tIlum(C),Magnitude
    +007940,+001389,0,+0007940,+0001389, 2296, 0000,     +31, -128.0000, 24.9

    INFO:Performing Illum Crosstalk for TX0 HDR 1
          I,      Q,S, ScaledI, ScaledQ,tMain,tIlum,tMain(C),  tIlum(C),Magnitude
    +021962,+012444,0,+0021962,+0012444, 2304, 0000,     +32, -128.0000, 79.6

    INFO:Performing Illum Crosstalk for TX1 HDR 0
          I,      Q,S, ScaledI, ScaledQ,tMain,tIlum,tMain(C),  tIlum(C),Magnitude
    +001217,+000238,0,+0001217,+0000238, 2288, 0000,     +30, -128.0000,  3.3

    INFO:Performing Illum Crosstalk for TX1 HDR 1
          I,      Q,S, ScaledI, ScaledQ,tMain,tIlum,tMain(C),  tIlum(C),Magnitude
    +000423,-000264,0,+0000423,-0000264, 2288, 0000,     +30, -128.0000,  1.6

    INFO:Performing Illum Crosstalk for TX2 HDR 0
          I,      Q,S, ScaledI, ScaledQ,tMain,tIlum,tMain(C),  tIlum(C),Magnitude
    +001351,-000336,0,+0001351,-0000336, 2288, 0000,     +30, -128.0000,  3.7

    INFO:Performing Illum Crosstalk for TX2 HDR 1
          I,      Q,S, ScaledI, ScaledQ,tMain,tIlum,tMain(C),  tIlum(C),Magnitude
    +001023,-000981,0,+0001023,-0000981, 2288, 0000,     +30, -128.0000,  3.7

    INFO:Completed Illumination cross talk measurement for all channels
    INFO::Loading Illumination cross talk Set
    INFO::Set target at a reference distance
    Press any Key to continue:

  • 0 in reply to Pritesh Patel
    TI__Mastermind 25895 points

    Hi Pritesh,

    Is this thread the most up to date on this same issue? https://e2e.ti.com/support/sensors/f/1023/t/927017?tisearch=e2e-sitesearch&keymatch=%2520user%253A90644

    If so we can work on that thread and close this one.

    Best,

    Alex

  • 0 in reply to Alex Bhandari-Young
    Intellectual 335 points

    Yes you can close this thread. I did not know if new information added to the thread is responded and that is why I created new thread with new test results.