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.

IWR6843: advanced frame configuration

Part Number: IWR6843

Hi expert.

My name is Jeong.

I want to detect (tx1-tx2) 60m and (tx3) 200m using the advanced frame.

The following configuration has led to a strange phenomenon.

sensorStop
flushCfg
dfeDataOutputMode 3
channelCfg 15 7 0
adcCfg 2 1
adcbufCfg -1 0 1 1 1
profileCfg 0 61 3 1 41 0 0 4 1 256 6500 0 0 48
profileCfg 1 61 3 1 100 0 0 6 1 256 2689 0 0 48
chirpCfg 0 0 0 0 0 0 0 4
chirpCfg 1 1 0 0 0 0 0 0
chirpCfg 2 2 1 0 0 0 0 1
chirpCfg 3 3 1 0 0 0 0 2
advFrameCfg 2 0 0 1 0
subFrameCfg 0 0 0 2 128 100 0 1 1 100
subFrameCfg 1 0 2 2 64 100 0 1 1 100

1) ProfileCfg 0 is 200m, but all subframes( 0 and 1) are detected 60m (profilecfg 1).
2) If profileCfg 1 is changed to 100m, all subframes detect 100m.

3)If the chirpCfg is changed as follows, the radar does not operate.

chirpCfg 0 0 0 0 0 0 0 1
chirpCfg 1 1 0 0 0 0 0 2
chirpCfg 2 2 1 0 0 0 0 4
chirpCfg 3 3 1 0 0 0 0 0

Please tell me the advanced frame configuration used by dividing tx1-tx2, tx3.

  • Former Member
    0 Former Member

    Hello,

    Why do you have have chirpCfg commands with 0 TX enabled?

    chirpCfg 1 1 0 0 0 0 0 0

    and 

    chirpCfg 3 3 1 0 0 0 0 0

    If I remove the 0TX chirps then the cfg is able to run. profile_ISK_e2e_adv_sf.cfg

  • Thanks for your answer.

    1. Why do you have have chirpCfg commands with 0 TX enabled?

       -> I downloaded 1 TX CFG from TI VISUALIZER.

    % ***************************************************************
    % Created for SDK ver:03.02
    % Created using Visualizer ver:3.2.1.0
    % Frequency:60
    % Platform:xWR68xx
    % Scene Classifier:best_range_res
    % Azimuth Resolution(deg):30
    % Range Resolution(m):0.044
    % Maximum unambiguous Range(m):9.02
    % Maximum Radial Velocity(m/s):1
    % Radial velocity resolution(m/s):0.13
    % Frame Duration(msec):100
    % Range Detection Threshold (dB):15
    % Doppler Detection Threshold (dB):15
    % Range Peak Grouping:enabled
    % Doppler Peak Grouping:enabled
    % Static clutter removal:disabled
    % Angle of Arrival FoV: Full FoV
    % Range FoV: Full FoV
    % Doppler FoV: Full FoV
    % ***************************************************************
    sensorStop
    flushCfg
    dfeDataOutputMode 1
    channelCfg 15 1 0
    adcCfg 2 1
    adcbufCfg -1 0 1 1 1
    profileCfg 0 60 1192 7 57.14 0 0 70 1 256 5209 0 0 30
    chirpCfg 0 0 0 0 0 0 0 1
    chirpCfg 1 1 0 0 0 0 0 0
    -------------------------------------------------------------------------------

    So I also enabled 0TX.

    2. 

    My cfg file only applies profileConfig 1(60meters) to all tx.
    The cfg file you sent applies only profileConfig 0(200meters) to all tx.
    My intention is proFileCfg 0 for Tx3, and profileCfg1 for Tx1 and Tx2 sequentially; i.e.
    At time 0, profileCfg 0 through Tx3, At time 1, profileCfg1 through Tx1, and at time 2, profileCfg1 through Tx2.
    Please let me know an appropriate configuration to acheive the goal.

  • My intention is proFileCfg 0 for Tx3, and proFileCfg 1 for Tx1 and Tx2 sequentially.

    Please let me know an appropriate configuration to acheive the goal

  • Former Member
    0 Former Member in reply to YOUNG JEONG

    Hello,

    The config I have provided does:

    64 chirps of profile 0 on TX3

    64 loops of: profile 1 on TX1 and then profile 1 on TX2

    This is based on the example CFG you provided.

    I think there is a misunderstanding in the meaning of the various parameters as well as the purpose of advanced subframe config. Please refer to the user's guide of the SDK to clarify what each of the parameters mean. 

    The bitmask to enable TX1 is 1, TX2: is 2 and TX3 is 4. You should not be providing a bitmask of 0 as I indicated previously.

    chirpCfg 1 1 0 0 0 0 0 0 

    Amanda

  • Hello.

    I revised the cfg according to your advice, but not all points exceed 67 meters.
    Profile 0 does not apply to subframe 0 and profile 1 appears to apply to all subframe.

    In the video attached below, subframe 0 is blue points and subframe 1 is red points.

    My intention is proFileCfg 0 for Tx3, and proFileCfg 1 for Tx1 and Tx2 sequentially.

    Please let me know an appropriate configuration to acheive the goal.

    sensorStop
    flushCfg
    dfeDataOutputMode 3
    channelCfg 15 7 0
    adcCfg 2 1
    adcbufCfg -1 0 1 1 1
    profileCfg 0 61 3 1 41 0 0 4 1 256 6500 0 0 48
    profileCfg 1 61 3 1 100 0 0 6 1 256 2689 0 0 48
    chirpCfg 0 0 0 0 0 0 0 4
    chirpCfg 1 1 1 0 0 0 0 1
    chirpCfg 2 2 1 0 0 0 0 2
    advFrameCfg 2 0 0 1 0
    subFrameCfg 0 0 0 2 64 100 0 1 1 100
    subFrameCfg 1 0 2 1 64 100 0 1 1 100
    lowPower 0 0
    guiMonitor 0 1 1 0 0 0 1
    guiMonitor 1 1 1 0 0 0 1
    cfarCfg 0 0 2 8 4 3 0 10 0
    cfarCfg 0 1 0 4 2 3 1 10 0
    cfarCfg 1 0 2 8 4 3 0 10 0
    cfarCfg 1 1 0 4 2 3 1 10 0
    aoaFovCfg 0 -90 90 -90 90
    aoaFovCfg 1 -90 90 -90 90
    cfarFovCfg 0 0 0 250
    cfarFovCfg 1 0 0 250
    cfarFovCfg 0 1 -30 30
    cfarFovCfg 1 1 -30 30
    clutterRemoval -1 0
    multiObjBeamForming 0 1 0.5
    multiObjBeamForming 1 1 0.5
    calibDcRangeSig 0 0 -5 8 256
    calibDcRangeSig 1 0 -5 8 256
    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
    measureRangeBiasAndRxChanPhase 0 1.5 0.2
    bpmCfg -1 0 0 1
    extendedMaxVelocity -1 0
    CQRxSatMonitor 0 3 4 67 0
    CQSigImgMonitor 0 127 4
    CQRxSatMonitor 1 3 4 67 0
    CQSigImgMonitor 1 127 4
    analogMonitor 0 0
    lvdsStreamCfg -1 0 0 0
    sensorStart

  • If the range of subframe 1 is changed by adjusting the frequency slope of profile 1, subframe 0 is also affected.

  • Former Member
    0 Former Member in reply to YOUNG JEONG

    Hello,

    • The subframecfg commands you have used are incorrect. Please check against the example file I provided. You have configured # of chirp cfgs to 2 when it should be 1 and vice versa.
    • The main issue is I cannot debug your device firmware and visualizer.
      • Are you running your own custom demo code? And are you using your own EVM?
      •  You've configured subframe 0 to only be 1 transmitter (TX3) This means of course that you will only have range information and not angle. There cannot be a 2D scatter plot for SF0.
      • For a 2D point cloud if you are using the same antenna layout/config as the IWR6843ISK the azimuth TX's are TX1 and 3. I assume since you are wanting to get a 2D scatter from TX1 and TX2 you have your own antenna layout or you are running your own demo code with angle estimation modfied to support the TX1-TX2 config you are using.

    I would recommend that you follow and use the chirp cfg example of advanced SF usage provided in the mmwave SDK. You can use the mmWave Demo Visualizer and see how different profiles are applied for the subframes.

    Amanda

  • Hello,

    This is the cfg you sent me.

    profileCfg 0 61 3 1 41 0 0 4 1 256 6500 0 0 48
    profileCfg 1 61 3 1 100 0 0 6 1 256 2689 0 0 48

    % Chirps for SF0 w/ TX3 only and Profile 0
    chirpCfg 0 0 0 0 0 0 0 4
    %chirpCfg 1 1 0 0 0 0 0 4

    % Chirps for SF1 w/ TX1 TX2 only and Profile1
    chirpCfg 2 2 1 0 0 0 0 1
    chirpCfg 3 3 1 0 0 0 0 2

    advFrameCfg 2 0 0 1 0

    % SF0
    subFrameCfg 0 0 0 1 64 100 0 1 1 100
    % SF1
    subFrameCfg 1 0 2 2 64 100 0 1 1 100

    Using TI EVM(IWR6843ISK) and SDK 3.2, to apply TX2 to SUB0 and TX1-TX3 to SUB1 do the following?

    profileCfg 0 61 3 1 41 0 0 4 1 256 6500 0 0 48
    profileCfg 1 61 3 1 100 0 0 6 1 256 2689 0 0 48
    chirpCfg 0 0 0 0 0 0 0 2
    chirpCfg 2 2 1 0 0 0 0 1
    chirpCfg 3 3 1 0 0 0 0 4
    advFrameCfg 2 0 0 1 0
    subFrameCfg 0 0 0 1 64 100 0 1 1 100
    subFrameCfg 1 0 2 2 64 100 0 1 1 100

  • SUB 0 TX3, SUB 1 TX1-TX2

  • SUB 0 TX2, SUB 1 TX1-TX3

    SubFrame 1 (red point) is applied to profileConfig 1 and has to be 67m long but the red point is 240m long.
    profileConfig0 appears to apply to all subframe.
    How should we solve this?

  • Former Member
    0 Former Member in reply to YOUNG JEONG

    Hello,

    Can you please test your demo and visualizer with the example subframe cfg provided in the SDK?

    This is to check whether the issue is with the particular cfg you are using or the visualization.

    Amanda

  • Former Member
    0 Former Member in reply to Former Member

    Hello,

    This thread has been resolved offline. I'll be closing the thread.

    Amanda