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.

AWR1642: AWR1642: Radar studio ramp timing calculator w/o hardware connected

Part Number: AWR1642
Other Parts Discussed in Thread: DCA1000EVM

Hello Team,

I am also facing the same issue. with the help of RADARStudio User Guideline i have installed all the necessary softwares and drivers required. 

still i get the following error once the RADAR studio is launched while keeping hardware is power ON state (I'm using only AWR1642 EVM board, I dont have XWR1xx DevPack since it is not required).

Hello ej99,

Where you found SDK 1.0.2 version? Please share the weblink. 

Please help me to solve this issue as early as possible. 

Regards,

Sonal Chavhan. 

  • Hi,

    Could you please install FTDI's WHQL certified drivers from here and try again?

    Best Regards,

    Anand

  • Hello Sir,

    Thanks for your reply!

    It is already installed, still the same error. 

    Can you please provide me link for SDK  1.0.2 version? 

    Regards,

    Sonal Chavhan. 

  • Hi,

    Could you please let us know why you require SDK 1.0.2? This was not publicly released as far as I can tell.

    Also, why are you using such an old version of Radar Studio? The current version is mmWave Studio 2.0.0.2 available from here:

    Best Regards,

    Anand

  • Hello Sir,

    Thanks for your suggestion.

    I have installed current version of mmWave Studio 2.0.0.2 and again run the setup still having the same issue.

    Software pre-installation done as follows- 

    1. FTDI's WHQL certified drivers - installed.

    2. HSDCPro installed - link suggested in RADAR Studio guideline manual 

    3. MATLAB installed - link suggested in RADAR Studio guideline manual 

    Please let me know what is wrong.

    I will appreciate quick solution on this.

    Regards,

    Sonal Chavhan.  

  • Hi Sonal,


    Can you describe your setup a little? What are you trying to do here?


    You mentioned that you have only the AWR1642 EVM without any other board connected - why do you need Radar Studio for this?

    Best Regards,

    Anand

  • Hello Sir,

    I am working on automotive application using AWR1642 RADAR sensor, For application requirement I want to set chirp configuration settings for following system specification- 

    Parameters

       Specifications

       Maximum range

       80 meter

       Range resolution

       50 cm

       Maximum velocity

       80 Km/h

       Velocity resolution

       1.5 Km/h

    To set chirp configuration,  Ramp timing calculator is required. hence I'm trying to use RADAR Studio app but still I cant resolve the issue. 

    Another option for config setting like mmWave Sensing estimator, this does not accomplish the same thing, as you cannot enter arbitrary chirp parameters directly. You are limited to computed parameters based on the constraints you enter.

    If you have any other solution for chirp settings for specified system requirement, please let me know. OR else how can I resolve RADAR studio error?

    Please help to solve this issue as early as possible.

    waiting for your solution.

    Regards,

    Sonal R. Chavhan. 

  • Hi,

    Could you try installing mmWave Studio 2.0.0.2 on another computer? If possible, please install the FTDI drivers and connect a device with an FTDI chip (like the DCA1000 or any other) once to the computer before attempting to start mmWave Studio.

    Alternatively, if you can use the mmWave Sensing Estimator to prepare your desired chirp configuration and provide us the following inputs, we can run them through the Ramp Timing Calculator and provide you the corresponding results from the calculator.

    Best Regards,

    Anand

  • Hello Sir,

    Again I have tried to fix the issue by instruction given in the RADAR Studio user guide (Latest version), but it is showing the same error as follows- 

    As you have suggested in second option, following is the input settings you will required to provide me Ramp timing calculator result - 

    1. ADC full rate mode

    2. DFE mode - complex1x

    3. HPF1 corner frequency - 175K

    4. HPF2 corner frequency - 350K

    5. Slope (MHz/uSec) - 8

    6. ADC Samples - 256

    7. Sample Rate (KSPS) - 5000

    Waiting for your input. 

    Regards,

    Sonal Chavhan. 

  • Hi,

    For the issue you have of not being able to start mmWave Studio, did you try installing the drivers from the FTDI website and connect any device with an FTDI chip (like the DCA1000) to the PC before attempting to start mmWave Studio?

    For the ramp timing parameters, please note that for the AWR1642, only the low power ADC mode is supported.

    The following is a screenshot of the ramp timing parameters for your inputs.

    Best Regards,

    Anand

  • Hello Sir,

    Thank you for your help!

    I have install FTDI driver from and try to launch the RADAR Studio while keeping EVM power ON, but it does not work. I have tried the other solution mention in RADAR Studio User guide -

    But still issue is not resolve. I will try to repeat the same process on another computer. 

    But for now thank you for your argent support ! will get back for further help. 

    Regards,

    Sonal Chavhan. 

  • Hi,

    Could you please let us know which exact FTDI driver you used? Did you use the installer from the FTDI page or just the zip file?

    Best Regards,

    Anand

  • Hello SIr,

    I have used installer from FTDI page -

    mmwave_studio_<ver>\mmWaveStudio\ftdi

    Regards,

    Sonal Chavhan. 

  • Hi Sonal,

    I'm afraid we do not have any more suggestions to get mmWave Studio working.


    We would recommend trying a fresh installation of mmWave Studio 2.0.0.2 on a different computer along with the Matlab Runtime 8.5.1 and the FTDI drivers from their website. It would be a good idea to also connect the DCA1000 EVM to this computer before using mmWave Studio to ensure that the FTDI drivers are correctly installed.

    Best Regards,

    Anand

  • Hello Sir,

    After studding all the required documents for chirp configuration and lot of calculation for setting parameters, I have end up with following chirp configuration for 80 meter object detection using AWR1642 nonOS demo code. 

    sensorStop
    flushCfg
    dfeDataOutputMode 1
    channelCfg 15 3 0
    adcCfg 2 1
    adcbufCfg -1 0 0 1 0
    profileCfg 0 77 2 3.14 56 0 0 8 1 256 5000 0 0 30
    chirpCfg 0 0 0 0 0 0 0 1
    chirpCfg 1 1 0 0 0 0 0 2
    bpmCfg -1 0 0 1
    frameCfg 0 1 32 0 50 1 0
    lowPower 0 1
    guiMonitor -1 1 1 1 0 0 1
    cfarCfg -1 0 2 8 4 4 0 5120
    cfarCfg -1 1 0 8 4 4 0 5120
    peakGrouping -1 1 0 0 1 224
    multiObjBeamForming -1 1 0.5
    calibDcRangeSig -1 0 -5 8 256
    extendedMaxVelocity -1 0
    clutterRemoval -1 1
    compRangeBiasAndRxChanPhase 0.0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0
    measureRangeBiasAndRxChanPhase 0 1.5 0.2
    nearFieldCfg -1 0 0 0
    CQRxSatMonitor 0 3 4 127 0
    CQSigImgMonitor 0 63 8
    analogMonitor 1 1
    lvdsStreamCfg -1 0 0 0
    sensorStart

    But this configuration can detect upto 16m object only. I have attached output rangevalue file herewith for your reference. 

    RangeValue output data.txt

    please help me to update the configuration settings for 80m range object detection.

    I'll appreciate quick response on this.

    Regards,

    Sonal R. Chavhan.  

  • Hi,

    Could you please try using higher rxGain - say 48dB - in the profile config.

    Best Regards,

    Anand

  • Hello Sir,

    Thanks for your reply!

    I have check with increasing Rx gain upto 48DB in profile configuration, by this config setting it can detect upto 23 meter distance. 

    Output range value attached herewith -

    RangeValue output data with incresing Rx gain.txt

    Please let me know other settings I have to update for 80 meter range detection.

    And also I want to know about ''nearFieldCfg'' command setting, because I check bit setting for this command in cli.c in ''AWR16xx_mss_nonOS'' file, it has following bits,

    but in default config file it has 4 bits to set, can I get detail bit setting information for ''nearFieldCfg'' command (I have also checked in MMWAVE SDK User Guide- 3. 4. Configuration (.cfg) File Format, but it don't have any information for this command). Also I want to ask few questions regarding -

    1. If I set startRangeIndex and endRangeIndex in ''nearFieldCfg'', can it help to increase the detection range? If yes, what is threshold values to set?

    2. What is the max Rx gain value of AWR1642 can we set in profile config?

    Please help me to resolve my queries as early as possible to update the config settings for 80 meter max distance.  

    Thanks in advance!

    Regards,

    Sonal Chavhan. 

  • Hello Team,

    Waiting for response from your side.

    Regards. 

  • Sonal,

    For your reference, TI provides a reference design for a Short Range Radar with a maximum range of ~80 meters. You can find the design guide here: http://www.ti.com/lit/ug/tidud36b/tidud36b.pdf

    Specifically, refer to "Table 2. Chirp Configuration" in section "2.3.2 Chirp Configuration and System Performance" for an example chirp configuration that can detect objects up to 80 meters. Although it does not explicitly state in the table, the start frequency for the SRR chirp is 76 GHz.

    You can find the example chirp here: C:\ti\mmwave_automotive_toolbox_2_5_0\labs\lab0002_short_range_radar\src\common\srr_config_chirp_design_SRR80.h

    This file comes from the latest release of the Automotive Toolbox in TI's Resource Explorer.

    Also, you will continue to see the error message you were referencing when mmWave Studio starts up until you plug either an mmWave DevPack or DCA1000EVM into your PC for the first time. Your PC will then install the FTDI drivers for the four COM ports that will show up in Windows Device Manager. This error will continue to display until you do this step.

    Regards,
    Kyle