• State TI Thinks Resolved
  • Locked Locked
  • Replies 24 replies
  • Answers 7 answers
  • Subscribers 31 subscribers
  • Views 870 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.

AWR1843BOOST: SRR lab FOV problem

Sriram S
Prodigy 240 points
Part Number: AWR1843BOOST
Other Parts Discussed in Thread: AWR1642BOOST, AWR1843, AWR1642, DCA1000EVM

Tool/software:

Hi,

   I am using SRR lab to AWR1843BOOST module, I need for answer Few Quoins.

1.

  • my object position is y=10 meter, X=-2.5meter but the Sensor data is y=10 meter, X=-2meter.
  • my object position is y=10 meter, X=2.5meter but the Sensor data is y=10 meter, X=1.5meter.

        object position and sensor data is not mating.

2. object not moving (zero doppler condition),but the visualizer doppler plot value is 3.6m/s showing.

3. one object detection the plotter show multiple Dot , i need one dot .

Kindly explain how to resolve the problem.

  • 0
    TI__Expert 4250 points

    What visualizer are you using? Can you share your cfg?

  • 0 in reply to Zorah Ahmad
    TI__Expert 4250 points

    3. It is not possible to show one dot, the object will have reflections from multiple points 

  • 0 in reply to Zorah Ahmad
    Prodigy 240 points

    HI,

    I thanks for the replay, and will use the srr_visualization visualizer.

    I will attach the CFG below.

    /*
 *   @file  srr_config_consts.h
 *
 *   @brief
 *      This file holds constants related to the USRR20 chirp configuration. 
 *
 *  \par
 *  NOTE:
 *      (C) copyright 2020 Texas Instruments, Inc.
 *
 *  Redistribution and use in source and binary forms, with or without
 *  modification, are permitted provided that the following conditions
 *  are met:
 *
 *    Redistributions of source code must retain the above copyright
 *    notice, this list of conditions and the following disclaimer.
 *
 *    Redistributions in binary form must reproduce the above copyright
 *    notice, this list of conditions and the following disclaimer in the
 *    documentation and/or other materials provided with the
 *    distribution.
 *
 *    Neither the name of Texas Instruments Incorporated nor the names of
 *    its contributors may be used to endorse or promote products derived
 *    from this software without specific prior written permission.
 *
 *  THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
 *  "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
 *  LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
 *  A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
 *  OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
 *  SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
 *  LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
 *  DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
 *  THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
 *  (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
 *  OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
 */

/*! @brief Ultra short range chirp profile - 20 m range, 4.3cm resolution. better angular resolution,  approximately 18kmph max - vel. */
#define PROFILE_USRR_PROFILE_ID              (1U)
#define PROFILE_USRR_HPFCORNER_FREQ1_VAL     RL_RX_HPF1_175_KHz
#define PROFILE_USRR_HPFCORNER_FREQ2_VAL     RL_RX_HPF2_350_KHz
#define PROFILE_USRR_RX_GAIN_VAL             (44U)
#define PROFILE_USRR_DIGOUT_SAMPLERATE_VAL   (6222U)
#define PROFILE_USRR_ADC_SAMPLE_VAL          (512U)
#define PROFILE_USRR_IDLE_TIME_VAL           (700U)
#define PROFILE_USRR_RAMP_END_TIME_VAL       (8728U)
#define PROFILE_USRR_START_FREQ_GHZ		  (77.01f)
#define PROFILE_USRR_START_FREQ_VAL          (CONV_FREQ_GHZ_TO_CODEWORD(PROFILE_USRR_START_FREQ_GHZ))
#define PROFILE_USRR_TXOUT_POWER_BACKOFF     (0U)
#define PROFILE_USRR_TXPHASESHIFTER_VAL      (0U)
#define PROFILE_USRR_FREQ_SLOPE_MHZ_PER_US   (42.0f)
#define PROFILE_USRR_FREQ_SLOPE_VAL          (CONV_SLOPE_MHZ_PER_US_TO_CODEWORD(PROFILE_USRR_FREQ_SLOPE_MHZ_PER_US))
#define PROFILE_USRR_TX_START_TIME_VAL       (100U)  // 1us
#define PROFILE_USRR_ADC_START_TIME_VAL      (480U)  // 4.8 us

#define CHIRP_USRR_0_PROFILE_ID                (1U)
#define CHIRP_USRR_0_START_INDEX               (128U + 0U)
#define CHIRP_USRR_0_END_INDEX                 (128U + 0U)
#define CHIRP_USRR_0_START_FREQ_VAL            (0U)
#define CHIRP_USRR_0_FREQ_SLOPE_VAL            (0U)
#define CHIRP_USRR_0_IDLE_TIME_VAL             (0U)
#define CHIRP_USRR_0_ADC_START_TIME_VAL        (0U)
#define CHIRP_USRR_0_TX_CHANNEL                (TX_CHANNEL_1_ENABLE)

#define CHIRP_USRR_1_PROFILE_ID                (1U)
#define CHIRP_USRR_1_START_INDEX               (128U + 1U)
#define CHIRP_USRR_1_END_INDEX                 (128U + 1U)
#define CHIRP_USRR_1_START_FREQ_VAL            (0U)
#define CHIRP_USRR_1_FREQ_SLOPE_VAL            (0U)
#define CHIRP_USRR_1_IDLE_TIME_VAL             (0U)
#define CHIRP_USRR_1_ADC_START_TIME_VAL        (0U)
#define CHIRP_USRR_1_TX_CHANNEL                (TX_CHANNEL_2_ENABLE)

/* SUBFRAME Configuration */
#define SUBFRAME_USRR_CHIRP_START_IDX           (CHIRP_USRR_0_START_INDEX)
#define SUBFRAME_USRR_CHIRP_END_IDX             (CHIRP_USRR_1_END_INDEX)
#define SUBFRAME_USRR_LOOP_COUNT                (32U)
#define SUBFRAME_USRR_PERIODICITY_VAL           (6000000U) // 30ms
#define SUBFRAME_USRR_TRIGGER_DELAY_VAL         (0U)
#define SUBFRAME_USRR_NUM_REAL_ADC_SAMPLES      (PROFILE_USRR_ADC_SAMPLE_VAL * 2)
#define SUBFRAME_USRR_NUM_CMPLX_ADC_SAMPLES     (PROFILE_USRR_ADC_SAMPLE_VAL)
#define SUBFRAME_USRR_CHIRPTYPE_0_NUM_CHIRPS    ((CHIRP_USRR_0_END_INDEX - CHIRP_USRR_0_START_INDEX + 1)*SUBFRAME_USRR_LOOP_COUNT)
#define SUBFRAME_USRR_CHIRPTYPE_1_NUM_CHIRPS    ((CHIRP_USRR_1_END_INDEX - CHIRP_USRR_1_START_INDEX + 1)*SUBFRAME_USRR_LOOP_COUNT)
#define SUBFRAME_USRR_NUM_TX					(2U)
#define SUBFRAME_USRR_NUM_VIRT_ANT				(SUBFRAME_USRR_NUM_TX*NUM_RX_CHANNELS)
#define SUBFRAME_USRR_NUM_ANGLE_BINS			(32U)
#define SUBFRAME_USRR_NUM_CHIRPS_TOTAL			((SUBFRAME_USRR_CHIRP_END_IDX - SUBFRAME_USRR_CHIRP_START_IDX + 1) * SUBFRAME_USRR_LOOP_COUNT)

/*! @brief Derived parameters. */
#define PROFILE_USRR_RANGE_RESOLUTION_METERS        ((MMWDEMO_SPEED_OF_LIGHT_IN_METERS_PER_USEC * PROFILE_USRR_DIGOUT_SAMPLERATE_VAL)/ (2000.0f * PROFILE_USRR_FREQ_SLOPE_MHZ_PER_US * SUBFRAME_USRR_NUM_CMPLX_ADC_SAMPLES))

#define SUBFRAME_USRR_CHIRPTYPE_0_CHIRP_REPETITION_PERIOD_US (((CHIRP_USRR_0_IDLE_TIME_VAL + PROFILE_USRR_IDLE_TIME_VAL + PROFILE_USRR_RAMP_END_TIME_VAL)/100.0f))
#define SUBFRAME_USRR_CHIRPTYPE_1_CHIRP_REPETITION_PERIOD_US (((CHIRP_USRR_1_IDLE_TIME_VAL + PROFILE_USRR_IDLE_TIME_VAL + PROFILE_USRR_RAMP_END_TIME_VAL)/100.0f))

#define SUBFRAME_USRR_CHIRPTYPE_0_VEL_RESOLUTION_M_P_S       (((1000.0f/(SUBFRAME_USRR_CHIRPTYPE_0_CHIRP_REPETITION_PERIOD_US + SUBFRAME_USRR_CHIRPTYPE_1_CHIRP_REPETITION_PERIOD_US))/SUBFRAME_USRR_CHIRPTYPE_0_NUM_CHIRPS)*(PROFILE_SRR_LAMBDA_MILLIMETER/2.0f))
#define SUBFRAME_USRR_CHIRPTYPE_0_MAX_VEL_M_P_S     (SUBFRAME_USRR_CHIRPTYPE_0_VEL_RESOLUTION_M_P_S*SUBFRAME_USRR_CHIRPTYPE_0_NUM_CHIRPS/2)

#define SUBFRAME_USRR_CHIRPTYPE_1_VEL_RESOLUTION_M_P_S       (((1000.0f/(SUBFRAME_USRR_CHIRPTYPE_0_CHIRP_REPETITION_PERIOD_US + SUBFRAME_USRR_CHIRPTYPE_1_CHIRP_REPETITION_PERIOD_US))/SUBFRAME_USRR_CHIRPTYPE_1_NUM_CHIRPS)*(PROFILE_SRR_LAMBDA_MILLIMETER/2.0f))
#define SUBFRAME_USRR_CHIRPTYPE_1_MAX_VEL_M_P_S     (SUBFRAME_USRR_CHIRPTYPE_1_VEL_RESOLUTION_M_P_S*SUBFRAME_USRR_CHIRPTYPE_1_NUM_CHIRPS/2)
#define SUBFRAME_USRR_MIN_SNR_dB (12.0f)

#define SUBFRAME_USRR_NUM_CHIRPTYPES (2U)

  • 0 in reply to Sriram S
    Prodigy 240 points 

    "sensorStop",
"advFrameCfg",

"sensorStart",

    this visualizer send cfg.

  • 0 in reply to Sriram S
    Prodigy 240 points

    Hi ,

     

       Gentle Reminder...

     

    Thanks !

  • 0 in reply to Sriram S
    TI__Intellectual 2522 points

    Hi Sriram,

    To clarify, the SRR lab (lab0002_short_range_radar) is intended for the AWR1642BOOST EVM. Are you using a modified version of the demo to run on the AWR1843BOOST EVM?

    Thank you,

    Jin

  • 0 in reply to Jin Lee
    Prodigy 240 points

    Yes I will use AWR1843 EVM .

    AWR1843& AWR1642 EVM only the  different is antana

    2 TX,3TX? 

  • 0 in reply to Sriram S
    Prodigy 240 points

    Hi ,

     

       Gentle Reminder...

     

    Thanks !

  • 0 in reply to Sriram S
    TI__Intellectual 2522 points

    Hi Sriram,

    While the AWR1843 is a superset device that can run demos for on the AWR1642, performance will not be optimal without some modifications due to the different antenna arrays. 

    Please refer to this thread: https://e2e.ti.com/support/sensors-group/sensors/f/sensors-forum/965085/ccs-awr1843boost-compatibility-between-labs-for-awr1642-and-awr1843

    and this FAQ: https://e2e.ti.com/support/sensors-group/sensors/f/sensors-forum/965635/faq-awr1843-running-awr1642-code-on-awr1843

    Thank you,

    Jin

  • 0 in reply to Jin Lee
    Prodigy 240 points

    Hello

    I appreciate your response. I'll attempt to change the SRR lab from AWR1642 to AWR1843, but it's not functioning. Kindly help with the modifications.

    thank you,

  • 0 in reply to Sriram S
    TI__Intellectual 2522 points

    Hi Sriram, 

    Hi Sriram, could you specify what is not functioning? While we do not have the SRR lab ported from AWR1642 to AWR1843, there are a number of previous threads by previous engineers that have done similar porting that may be of help. e.g: 

    If the demo is properly ported, but you are still seeing mismatch between sensor position/speed and the data, there might be offsets in the .cfg file. You can refer to the Sensing Estimator (https://dev.ti.com/gallery/view/mmwave/mmWaveSensingEstimator/ver/2.4.0/) to check and configure your config.

    Thank you,

    Jin

  • 0 in reply to Jin Lee
    Prodigy 240 points

    Hello

    I appreciate your response.  i will tray to modify the profilecfg and chirpCfg but the sensor not give the data.

    Thank you,

  • 0 in reply to Sriram S
    TI__Intellectual 2522 points

    Hi Sriram,

    You can also refer to this FAQ on running AWR1642 code on AWR1843 linked in the E2E thread above: https://e2e.ti.com/support/sensors-group/sensors/f/sensors-forum/965635/faq-awr1843-running-awr1642-code-on-awr1843

    In addition to modifying the chirp config for the additional Tx on the AWR1843, please also update the .projectspecs for both DSS and MSS as described in the FAQ. The rest of the demo should not need to be changed. 

    You can find an example of this porting in the Occupancy Detection lab in the Radar Toolbox - the config files and .projectspec files can be diffed to show the exact changes made.

    Thank you,

    Jin

  • 0 in reply to Jin Lee
    Prodigy 240 points

    Hi,

    What has to be altered in the.projectspecs file and how to update it

  • 0 in reply to Sriram S
    TI__Intellectual 2522 points

    Hi Sriram,

    It seems that the Occupancy Detection lab mentioned in the E2E above is no longer available online. Another demo that shows the porting from AWR1642 to AWR1843 is the Interference Mitigation lab in the Radar Toolbox.

    This can be found: $TOOLBOX_INSTALL/source/ti/examples/interference_mitigation/victim

    There are .projectspec files available for both the AWR1642 and AWR1843 that can be diffed to show the updates needed.

    Thank you,

    Jin

  • 0 in reply to Sriram S
    TI__Guru*** 148514 points

    Hi,

    What is your objective with this activity?

    The SRR demo has been ported to 1843 already. The new demo is called MRR and it is available in the radar toolbox.

    Please try it

    Thank you

    Cesar

  • 0 in reply to Cesar
    Prodigy 240 points

    Hi,

    I'm going to the MRR demo, but it doesn't detect static objects, and the USRR data is offset to one side, like this: the object is straight in the sensor for two meters, but the plotter shows a blue dot on the left or right side for a few meters.

  • 0 in reply to Sriram S
    TI__Intellectual 2522 points

    Hi Sriram,

    Glad to hear the demo is running. The demo might not be showing static objects because of range-based pruning implemented in the DSS. Please refer to this older thread (https://e2e.ti.com/support/sensors-group/sensors/f/sensors-forum/1064312/awr1843boost-can-lab-demo-mrr-detect-the-short-range-static-objects) on how it can be bypassed.

    Regarding the offset, it may help to calibrate the sensor as the MRR demo does not do this. Please find instructions in the SDK doxygen: C:/ti/mmwave_sdk_03_06_02_00-LTS/packages/ti/demo/xwr18xx/mmw/docs/doxygen/html/index.html#Calibration_section

    Thank you,

    Jin

  • 0 in reply to Jin Lee
    Prodigy 240 points

    Hi,

    Thank you for the replay. I'm going to utilize the SRR lab in AWR1843, and I'm going to change the code TX antenna in AWR1843. I'm going to enable on TX1 and TX3, is that right?

      

  • 0 in reply to Sriram S
    TI__Intellectual 2522 points

    Hi Sriram,

    I recommend using the MRR demo as that is the same demo already ported to AWR1843. You shouldn't need to disable any antennas to run the MRR demo. 

    Please try the fixes mentioned above for the performance issues you are having (range-based pruning bypass and calibration).

    Thank you,

    Jin

  • 0 in reply to Jin Lee
    Prodigy 240 points

    Hi,

        

    The SRR project mostly fulfilled our needs; the only thing that needs improvement is that the speed and direction data for X is not matching.that reson I will still asking the SRR lab solution.

    The MRR lab I will disabled the range-based pruning It's working, but it can also detecting false alarms and ground clusters.

    And, the MRR lab uses a hard coded calibration. so kindly explain how to apply the calibration.

    Kindly give the solution.

  • 0 in reply to Jin Lee
    Prodigy 240 points

    Is DCA1000 required for EVM calibration?

  • 0 in reply to Sriram S
    TI__Intellectual 2522 points

    Hi Sriram,

    With the MRR demo we have today, yes, a DCA1000EVM would be needed to follow the calibration steps linked above.

    However, our team is also working on updating the MRR demo with the calibration implementation, that would not require the DCA1000EVM. This should be publicly available in a few weeks on the Radar Toolbox. 

    Thank you,

    Jin