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.

AWR1243: implementing calibDcRangeSig algorithm

Part Number: AWR1243


hi im using  AWR1243 and i am process the raw adc data by myself but i got struggled with implement of an algorithm 

i hope that someone could help me

i want to implement  The algorithm  of "calibDcRangeSig" that  is only implemented in the mmWave SDK demo which runs on the device and performs all the processing of the raw ADC data on the device.

can someone elaborate exactly  what  this algorithm do.

  • Hi,

    Please review the description in the mmwave SDK demo documentation section "Antenna coupling signature removal"

    Here is the location for SDK 2.1

    file:///C:/ti/mmwave_sdk_02_01_00_04/packages/ti/demo/xwr16xx/mmw/docs/doxygen/html/index.html

    Thank you

    Cesar

  • Hello cesar

    tanks for your response but  unfortunately there is not such file in this directory cause of this if you could send me the file hear that i could access that it would be nice.

    Thank you

    Farhad

  • Whatever SDK you have, all modules documentation can be seen by opening docs\mmwave_sdk_module_documentation.html.

  • Hi,

    Here is some more information on the "calibDcRangeSig" algorithm and how it is different from another algorithm support by the SDK "Clutter Removal"

    calibDcRangeSig

    Estimate once in a controlled environment where you know there are no true objects that you want to detect and there should be no motion also i.e only what you want to remove during normal operation (hence “calibration”). Remove (subtract) continuously post calibration. Number of range bins in the vicinity of zero (on “either side”) as specified by user are individually accumulated over time (and individually subtracted) i.e if range FFT output of a chirp k is x(1,k),x(2,k)..x(N,k), then during calibration say you want to estimate over K chirps and say you have first F range bins (F << N) and last L range bins (L << N) configured in calib DC (it is a subset of the full N) then estimates are s1,..sF,s(N-F+1),..sN where si = sum(x(i,1),..x(i,K))/K.  During regular (post calibration) operation, you perform a transformation on range FFT output of each chirp x1,x2,..xN to x1’,x2’..XF’, x(N-F+1)’..xN’ where xi’ = xi – si, before feeding to Doppler FFT.

    Clutter Removal

    Continuously remove all static clutter from the scene. So estimation and removal are done continuously. Two methods A) If Doppler FFT is done with rectangular window (basically no windowing), then zeroing out the Doppler FFT bin 0 does the job. B) If Doppler FFT is done with non-rectangular window, then zeroing out the Doppler bin 0 can take out some very slow moving objects along with the pure static clutter due to wider main lobe. So for this case, we estimate and subtract dc from all the samples before performing Doppler FFT i.e when doing Doppler FFT on x1,x2,..xN, you first do a transformation of the signal to x1’, x2’,..xN’ (before feeding to Doppler FFT) where xi’ = xi - sum(x1,..xN)/N.

    Thank you

    Cesar

  • hello cesar 

    Thanks for your answer

    could you please explain to me deeply how could i have  postproc calibration?????????

    Thank you

    Farhad

  • Hi,

    I am not clear what you denote by "postproc" calibration. Do you have in mind what was mentioned in above post as "post calibration"

    What the above post is trying to explain regarding "calibDcRangeSig" is that this algorithm is used to perform a "background subtraction" for the first range bin(s). The reason why this is needed is that usually in the first range bin(s) there is an antenna coupling effect that will make detections difficult.

    Thank you

    Cesar