• State
  • Locked Locked
  • Replies 6 replies
  • Subscribers 32 subscribers
  • Views 670 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

Original question:

OPT9221: Change of diode illumination power

OPT9221: De-aliasing frequency

Viktor Meshcheriakov
Prodigy 165 points
Part Number: OPT9221

Hi TI,

My question is related to the previous topic. In the second table in this message  

You could see that de aliasing frequency differs from the regular frequency. But I used your excel file for the sequence, and try to change the MOD_F2 PARS, it was always the same as the first one. De-aliasing is ON.

For example, it is the image then we use 

ind_freq_data_en = false:


ind_freq_data_en = true and first or second  freq choosen (same pictures):

Then we use one freq without de aliasing it looks like a good image appropriable for work.

The diode signal is:

It seems like only one frequency again.

How we can fix this de aliasing frequency?

 

 

  • 0
    TI__Expert 3975 points

    Hi Viktor, 

    Can you share your register settings as well? 

    Suramya

  • 0 in reply to Suramya Gupta
    Prodigy 165 points

    Hi Suramya,

    Please find all reg in attachment excel and same information (dec matrix) in Matlab (.mat) files in 7z archives.

    Settings  Image Registers content
    ind_freq_data_en = false

    5857.reply_to_TI_all_fmod.xls

    all_freq.7z
    ind_freq_data_en = true  freq 1 choosen

    reply_to_TI_fmod1.xls

    fmod1.7z

  • 0 in reply to Suramya Gupta
    Prodigy 165 points

    Hi Suramya,

    Is it a good format of regs data? Coul you please suppose why it works in that way?

  • 0 in reply to Viktor Meshcheriakov
    TI__Expert 3975 points
    Viktor,

    Register writes are okay. Can you give the write sequence as well?

    Suramya
  • 0 in reply to Suramya Gupta
    TI__Expert 3800 points
    Viktor,

    In case you still observe this issue, can you please share the register write sequence with us?

    Regards,
    Subhash
  • 0 in reply to Subhash Chandra Sadhu
    Prodigy 165 points

    Sorry for the delay, I miss previous reply notification.

    Sequence same like in Nithin's reply But we use Matlab for programming :

    %% List of commands
%%                      addr        r/w length reg_addr           7:0       15:8            23:16     
TOF_00_SOFTWARE_RESET_W = {'5C' 'w' '00' '000001'};
TOF_00_SOFTWARE_RESET_R = {'5C' 'r' '00' '000000'};
TOF_80_TG_DIS_HIGH_W    = {'58' 'w' '80' '000001'};
TOF_80_TG_DIS_LOW_W     = {'58' 'w' '80' '000000'};
TOF_80_TG_DIS_R         = {'58' 'r' '80' '000000'};
TOF_1F_ROW_SETTINGS_W   = {'58' 'w' '1F' 'EF0000'};
TOF_20_COL_START_W      = {'58' 'w' '20' '000000'};
TOF_21_COL_END_W        = {'58' 'w' '21' '40009F'};
TOF_39_OP_CONF_W        = {'5C' 'w' '39' '000000'};
TOF_25_OP_CONF2_W       = {'5C' 'w' '25' '080001'};
TOF_27_PIXEL_CONF_W     = {'5C' 'w' '27' '002000'};
TOF_3C_FRM_SETTINGS1_W  = {'5C' 'w' '3C' '005000'};
TOF_3D_FRM_SETTINGS2_W  = {'5C' 'w' '3D' '0001C0'};% recommended {'5C' 'w' '3D' '000030'};
TOF_3E_VD_ACTIVE_W      = {'5C' 'w' '3E' '0000F0'};% recommended {'5C' 'w' '3E' '4B0F00'};
TOF_3F_FRM_FR_W         = {'5C' 'w' '3F' '0000FA'};
TOF_02_DEALIAS1_W       = {'5C' 'w' '02' '901063'};
TOF_B2_DEALIAS2_W       = {'5C' 'w' 'B2' '000C00'};
TOF_03_DEALIAS3_W       = {'5C' 'w' '03' '200800'};
TOF_83_DEALIAS4_W       = {'58' 'w' '83' '000016'};
TOF_37_PHASE_CORR1_W    = {'5C' 'w' '37' '00EA20'};
TOF_38_PHASE_CORR2_W    = {'5C' 'w' '38' '000A20'};
TOF_82_PIX_CNT_MAX_W    = {'58' 'w' '82' '145855'};
TOF_4C_INTEG_SETTINGS_W = {'5C' 'w' '4C' 'C0000D'};
TOF_29_IND_FREQ_PHY_T_W = {'5C' 'w' '29' '304040'};

TOF_0C_PLL_SETTINGS1_W =  {'58' 'w' '0C' '12C000'};
TOF_0D_PLL_SETTINGS2_W =  {'58' 'w' '0D' '10A666'};
TOF_0F_PLL_SETTINGS3_W =  {'58' 'w' '0F' '0004AA'};
TOF_02_PLL_UPD_HIGH_W  =  {'58' 'w' '02' '00001C'};
TOF_02_PLL_UPD_LOW_W   =  {'58' 'w' '02' '000018'};

TOF_2E_TEMP_SENS_W     =  {'5C' 'w' '2E' '000872'};
TOF_51_DIS_TEMP_CAL_W  =  {'5C' 'w' '51' '162424'};
TOF_47_COEFF_ILLUM_W   =  {'5C' 'w' '47' '000000'};
TOF_48_COEF_SENSOR_W   =  {'5C' 'w' '48' '000000'};

TOF_29_IND_FREQ_2nd_W  = {'5C' 'w' '29' '304048'};

TOF_29_IND_FREQ_1st_W  = {'5C' 'w' '29' '304048'};
TOF_02_DEALIAS1_FR_EN_W= {'5C' 'w' '02' 'D01063'};

rw2c(TOF_00_SOFTWARE_RESET_W,tof2);
rw2c(TOF_80_TG_DIS_HIGH_W,tof2);
rw2c(TOF_1F_ROW_SETTINGS_W,tof2);
rw2c(TOF_20_COL_START_W,tof2);
rw2c(TOF_21_COL_END_W,tof2);
rw2c(TOF_39_OP_CONF_W,tof2);
rw2c(TOF_25_OP_CONF2_W,tof2);
rw2c(TOF_27_PIXEL_CONF_W,tof2);
rw2c(TOF_3C_FRM_SETTINGS1_W,tof2);
rw2c(TOF_3D_FRM_SETTINGS2_W,tof2);
rw2c(TOF_3E_VD_ACTIVE_W,tof2);
rw2c(TOF_3F_FRM_FR_W,tof2);
rw2c(TOF_02_DEALIAS1_W,tof2);
rw2c(TOF_B2_DEALIAS2_W,tof2);
rw2c(TOF_03_DEALIAS3_W,tof2);
rw2c(TOF_83_DEALIAS4_W,tof2);
rw2c(TOF_37_PHASE_CORR1_W,tof2);
rw2c(TOF_38_PHASE_CORR2_W,tof2);
rw2c(TOF_82_PIX_CNT_MAX_W,tof2);
rw2c(TOF_4C_INTEG_SETTINGS_W,tof2);
rw2c(TOF_29_IND_FREQ_PHY_T_W,tof2);
rw2c(TOF_80_TG_DIS_LOW_W,tof2);
rw2c(TOF_0C_PLL_SETTINGS1_W,tof2);
rw2c(TOF_0D_PLL_SETTINGS2_W,tof2);
rw2c(TOF_0F_PLL_SETTINGS3_W,tof2);
rw2c(TOF_02_PLL_UPD_HIGH_W,tof2);
pause(0.5);
rw2c(TOF_02_PLL_UPD_LOW_W,tof2);
rw2c(TOF_2E_TEMP_SENS_W,tof2);
rw2c(TOF_51_DIS_TEMP_CAL_W,tof2);
rw2c(TOF_47_COEFF_ILLUM_W,tof2);
rw2c(TOF_48_COEF_SENSOR_W,tof2);

    Now it seems, that problem might be in data acquisition driver.

    But the main question is: how it must look on an oscilloscope, and is our characteristic right for this configuration?