• State TI Thinks Resolved
  • Locked Locked
  • Replies 4 replies
  • Answers 1 answer
  • Subscribers 30 subscribers
  • Views 588 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.

IWR1843BOOST: The range resolution and velocity resolution calculations in mmWave-Studio

Cherry Zhou
Mastermind 22235 points
Part Number: IWR1843BOOST

Hi team,

Here's an issue from the customer may need your help:

The radar parameters are as follows:

For the range resolution, use the formula d_res = C/2B (C is the speed of light and B is the actual frequency-modulated bandwidth bandwidth) to get 3e8/2/3.2483e9 = 0.0461m, which does not match the results in the diagram.

And when calculating the velocity resolution, the formula v_res = lambda_wave / Tchirp / Nchirps / 2 gives a 0.0394 m/s difference from the figure result of 0.001 m/s;

The other parameters get the same result.

Could you help check this case? Thanks.

Best Regards,

Cherry

  • 0
    TI__Mastermind 21141 points

    Hi Cherry,

    Can you please provide the version of mmWave studio which is being used? Can you please also provide the list of programmed parameters which are being used?

    Additionally, you can direct the customer to this thread which details the equations used to calculate range and velocity resolution. 

    Best Regards,

    Josh

  • 0 in reply to Josh Dye
    TI__Mastermind 22235 points

    Hi Josh,

    Thanks for your support.

    Josh Dye said:
    Can you please provide the version of mmWave studio which is being used?

    mmWave Studio 02.01.01.00.

    Josh Dye said:
    Can you please also provide the list of programmed parameters which are being used?
    startFreq = 77e9
    freqSlope = 70.006e12
    Idle_time = 7e-6
    ADC_start_time = 10e-6
    ADC_samples = 580
    sampleRate = 12.5e6
    Ramp_End_Time = 57e-6
    B_set = 3990.34e6
    T_frame = 50e-3
    Nchirp = 255
    Nframe = 100
    NTx = 3
    NRx = 4
    C = 299792458
    Tchirp = Ramp_End_Time + Idle_time
    real_start_freq = startFreq + freqSlope * ADC_start_time
    lambda_wave_len = C / real_start_freq
    Tchirp_cycle = Tchirp * 3
    d_res = C * sampleRate / 2 / freqSlope / ADC_samples
    v_res = lambda_wave_len / Tchirp_cycle / Nchirp / 2
    And the results are as follows:
    Tchirp =6.4000e-05
    real_start_freq =7.7700e+10
    lambda_wave_len =0.0039
    Tchirp_cycle =1.9200e-04
    d_res =0.0461
    v_res =0.0394
    Thanks and regards,
    Cherry
  • 0 in reply to Cherry Zhou
    TI__Mastermind 22235 points

    Hi,

    May I know is there any updates?

    Thanks and regards,

    Cherry

  • 0 in reply to Cherry Zhou
    TI__Mastermind 21141 points

    Hi Cherry,

    Very sorry about the delay here. We are investigating a potential bug in the values reported by mmWave Studio. In the meantime, the customer can use mmWave Sensing Estimator to calculate chirp parameters.

    Best Regards,

    Josh