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.

TSW1400EVM: Post processed example matlab script code

Part Number: TSW1400EVM


I try the post processed example matlb script code named

read_Post_process_ADC_Capture_data_LVDS.m

in the .m file, it requires n_tx, but when I change the value, it won't change the size of adc_data.bin file which still is 4096KB.

I check SDK, DFP and studio's document and pdf files and the mmwave Radar Device ADC Raw Data Capture (Rev. B).pdf and so on,

but I don't find the reason, I don't know whether I missed the content in these files.

So I want to know the effect of n_tx and which document or pdf file I need to check, then I can understand the script well.

Thank you

 

  • FrogLu,

    We are looking into this.

    Regards,

    Jim

     

  • Hi Jim,

    Thank you for replying me so soon.

    I wait for your solution after checking.

    Regards,

    Froglu

  • Froglu,

    We are not aware of the Matlab script (shared in the previous mail). Is this part of mmWave Studio?

     

    We don’t see reference of any HSDC Pro Automation APIs in the script. Can you please brief how “n_tx” parameter is linked to HSDC Pro Data capture?

     

    Please let us know if there are any Matlab scripts, which has HSDC Pro Automation APIs, are executed before this script.

     

    Regards,

     

    Jim

  • Hi Jim,

    I get the matlab script from this post:

    http://e2e.ti.com/support/sensors/f/1023/p/627112/2312037#2312037

    and the point is that I don't know what "n_tx" parameter is linked to.

    I change the "n_tx" parameter's value, but it doesn't matter the .bin size.

    e.g. line 91 in the matlab script:

    dat = fread(fid,n_adc_samples*n_chirps*n_rx*n_tx,'uint16');

    n_tx should be a factor that determines the bin size,

    and I reconfig tx number in the channel profile and chirp profile in mmwave studio,

    but the .bin file captured by mmwave studio and HSDC pro data capture doesn't change.

    Regards,

    Froglu

  • Froglu,

    As per our understanding of the Matlab script (read_Post_process_ADC_Capture_data_LVDS.m), it is used to post process the data captured by mmWave Studio or HSDC Pro from ADC.

     

    The parameter “n_tx” is used to determine the amount of data that has to be read from the .bin file for further post processing (created by mmWave Studio or HSDC Pro), which has the Capture data from the ADC. It is not used to determine the size of the .bin file.

     

    The size of the .bin file is determined by the Number of Samples (configured in mmWave Studio or HSDC Pro) to be captured from the ADC. Please refer to section “3.1.3.1 Capture Option” in HighSpeedDataConverterPro.pdf ,which will be available at the following location, to configure the Number of Samples to be captured in HSDC Pro software.

     

    [HSDC Pro Install location]\High Speed Data Converter Pro\HighSpeedDataConverterPro.pdf

     

    Default HSDC Pro Install location: C:\Program Files (x86)\Texas Instruments\High Speed Data Converter Pro

    Regards,

    Jim

  • Hi Jim,

    Thank you for your reply about n_tx.

    So what you mean is that "n_tx" can be regarded as a parameter of the module which is the way how to post process ADC data?

    Regards,

    Froglu

  • Froglu,

    Yes, the “n_tx” parameter is used to post process the ADC Data. As per the statements (see attached) in “read_Post_process_ADC_Capture_data_LVDS.m” Matlab script, it is used to mention how much of data has to be read from the Bin file and process the same.

     

    Regards,

     

    Jim

    n parameter.pptx