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.

IWR6843ISK: How does IWR6843ISK extend max velocity and the problem encounter in improved velocity resolution

Part Number: IWR6843ISK

Hello I have some question about IWR6843ISK

1)We know IWR6843ISK support to extend maximum velocity to 2x, we want to know what principle is used. And does it needs to operate in a specific mode (e.g.: MIMO).

2)Known radar cube size is 768kB in IWR6843ISK, we want to improve velocity resolution. Now we encounter some terrible by increase chirp numbers(M) in a frame.

Our goal is to achieve max range is 90m, range resolution 40cm, max velocity 90km/hr, and velocity resolution 1km/hr at the same time.

Below is the cfg. file setting we want to tune: 

profileCfg 0 60 22 7 28 0 0 20 1 256 12500 0 0 48

frameCfg 0 1 96 0 50 1 0

we calculate N=256 and M=96 will not exceed 768kB, but now we only can set M=80, which can let radar work.

The error report return by MATLAB tm_visualizer is:

The original M is 64, we also tune M value within 64 to 80 but most of the value can not let the radar work. The error report is the same as the above.

Looking forward to your reply.

  • The error report return by MATLAB tm_visualizer is:

  • Hello

    Can you please confirm if you have tired the extendedMaxVelocity feature in the SDK's OOB demo and confirmed that it provides the velocity extension.

    Please see the User's guide and relevant implementation in the DPU for  Velocity estimation.

    https://software-dl.ti.com/ra-processors/esd/MMWAVE-SDK/latest/exports/mmwave_sdk_user_guide.pdf

    Thank you,

    Vaibhav

  • Former Member
    0 Former Member in reply to Vaibhav Mahimkar

    Can you provide the full log file of the console? It should be in the same path as the gui

  • Hi Amanda:

    Here is the full log file of the console.

    tm_console_log.txt
    Fullscreen
    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    12
    13
    14
    15
    16
    17
    18
    19
    20
    21
    22
    23
    24
    25
    26
    27
    28
    29
    30
    31
    32
    33
    34
    35
    36
    37
    38
    39
    40
    41
    42
    43
    44
    45
    46
    47
    48
    49
    50
    51
    52
    53
    54
    55
    56
    57
    58
    59
    60
    61
    62
    63
    64
    65
    66
    67
    COM6 opened.
    COM7 opened.
    Warning: Directory already exists.
    > In tm_visualizer_modify_0902 (line 49)
    Opening tm_demo_uart_stream_1.txt. Ready to log data.
    Opening configuration file
    Parsing configuration file...
    Skip parsing for: sensorStop command
    Skip parsing for: flushCfg command
    Skip parsing for: sensorStart command
    COM6 opened.
    COM7 opened.
    Sending cfg file to device...
    sensorStop
    flushCfg
    Done
    dfeDataOutputMode 1
    Done
    channelCfg 15 5 0
    Done
    adcCfg 2 1
    Done
    adcbufCfg -1 0 1 1 1
    Done
    profileCfg 0 60 22 7 28 0 0 20 1 256 12500 0 0 48
    Done
    chirpCfg 0 0 0 0 0 0 0 1
    Done
    chirpCfg 1 1 0 0 0 0 0 4
    Done
    frameCfg 0 1 96 0 50 1 0
    Done
    lowPower 0 0
    Done
    guiMonitor -1 1 0 0 0 0 0
    Done
    cfarCfg -1 0 2 8 4 3 0 10 0
    Done
    cfarCfg -1 1 0 4 2 3 1 12 0
    Done
    multiObjBeamForming -1 1 0.5
    Done
    clutterRemoval -1 1
    Done
    calibDcRangeSig -1 0 -5 8 256
    Done
    extendedMaxVelocity -1 1
    Done
    bpmCfg -1 0 0 1
    Done
    lvdsStreamCfg -1 0 0 0
    Done
    compRangeBiasAndRxChanPhase 0.0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0
    Done
    measureRangeBiasAndRxChanPhase 0 1.5 0.2
    Done
    CQRxSatMonitor 0 3 4 63 0
    Done
    CQSigImgMonitor 0 127 4
    Done
    analogMonitor 0 0
    Done
    aoaFovCfg -1 -90 90 -90 90
    Done
    cfarFovCfg -1 0 0 80
    Done
    cfarFovCfg -1 1 -30 30.00
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

  • Former Member
    0 Former Member in reply to Chia Hsing Yang

    Hello,

    Does the same profile and frameCfg work with the out of box demo? 

    Please try the chirp with the out of  box demo first. There are instructions in the UG for running the demo in CCS debug mode please do so and provide the error message that occurs in the console window.

    It appears from the log you provided that the device is crashing. This could be do to a timing issue - you can try increasing the frame period from 50ms to 100ms and see if this resolves the error. Depending on what output and processing options you have enabled you may be running out of interframe period.

    Amanda