• State TI Thinks Resolved
  • Locked Locked
  • Replies 10 replies
  • Answers 1 answer
  • Subscribers 33 subscribers
  • Views 650 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.

AWR6843AOPEVM: Configuration file settings for CPD on AWR6843AOPEVM

Hsiu Che Chang
Prodigy 30 points
Part Number: AWR6843AOPEVM
Other Parts Discussed in Thread: AWR6843

Tool/software:

Dear sir:

We saw in the LRPD documentation for the 6843AOP that the 6843AOP can achieve a chirp configuration containing three TXs in the same frame, as shown in the image below.



If we want to achieve the same effect in CPD, how should we modify the configuration file, or do we need to flash additional firmware?

Here is the configuration file we are currently using:

sensorStop
flushCfg
dfeDataOutputMode 1
channelCfg 15 7 0
adcCfg 2 1
adcbufCfg -1 0 1 1 1
lowPower 0 0
profileCfg 0 60.00 2789 11 41 0 0 97.0 1 64 2200 0 0 36
profileCfg 1 60.00 20 11 41 0 0 97.0 1 64 2200 0 0 36
chirpCfg 0 0 0 0 0 0 0 1
chirpCfg 1 1 1 0 0 0 0 2
chirpCfg 2 2 1 0 0 0 0 4
frameCfg 0 2 54 0 200 1 0
 
 
dynamicRACfarCfg   -1 5 29 1 1 8 8 4 6 4 1 8.00 6.00 0.40 1 15
staticRACfarCfg -1 4 4 2 2 8 16 4 6 6.00 13.00 0.50 0 
dynamicRangeAngleCfg -1 7.000 0.03 2 0
dynamic2DAngleCfg -1 5 1 1 1.00 8.00 2
staticRangeAngleCfg -1 0 1 1
antGeometry0 -1 -1 0 0 -3 -3 -2 -2 -1 -1 0 0
antGeometry1 -1 0 -1 0 -3 -2 -3 -2 -3 -2 -3 -2
antPhaseRot -1 1 -1 1 -1 1 -1 1 -1 1 -1 1
compRangeBiasAndRxChanPhase 0 0.9929 -0.1188 -0.9842 -0.1769 0.9994 0.0349 -0.9981 -0.0623 0.6777 -0.7353 -0.8517 0.5241 0.7782 -0.6280 -0.8004 0.5995 0.6842 -0.7293 -0.8495 0.5275 0.7969 -0.6041 -0.8090 0.5877 
fovCfg -1 64.0 64.0
 
numZones 5
totNumRows 2
sensorPosition 0 1.2 1.1 90 0 0
% state machine threshold first parameter is #zoneType 
occStateMach  0 10 10 3 50 1 3 12 20 4 700.0
occStateMach  1 10 10 3 50 3 3 12 15 3 700.0
classParam  0 50 36 36 36 40 36 0.025 0.025 0.025 0.022 0.025 
 
% seat zone definition, independent of mounting location
% Origin = -X to psngr, +X to driver, yStart, yEnd (0 = start of first row footwell), zStart, zEnd (z: 0 start of the floor)
interiorBounds -0.9 0.9 0.0 2.2
 
% zone 1 (driver) cuboids
 
cuboidDef 1 1   0.00  1.00 -0.50  1.00  0.80  1.20
cuboidDef 1 2   0.00  1.00 -0.50  1.00  0.40  0.80
cuboidDef 1 3   0.00  1.00 -0.50  1.00 -0.20  0.40
 
% zone 2 (front passenger) cuboids
 
cuboidDef 2 1  -1.00 -0.00 -0.50  1.00  0.80  1.20
cuboidDef 2 2  -1.00 -0.00 -0.50  1.00  0.40  0.80
cuboidDef 2 3  -1.00 -0.00 -0.50  1.00 -0.20  0.40
 
% zone 3 (2nd row driver side) cuboids
 
cuboidDef 3 1   0.30  1.00  1.00  2.50  0.80  1.20
cuboidDef 3 2   0.30  1.00  1.00  2.50  0.40  0.80
cuboidDef 3 3   0.30  1.00  1.00  2.50 -0.20  0.40
 
% zone 4 (2nd row middle) cuboids
 
cuboidDef 4 1  -0.30  0.30  1.00  2.50  0.80  1.20
cuboidDef 4 2  -0.30  0.30  1.00  2.50  0.40  0.80
cuboidDef 4 3  -0.30  0.30  1.00  2.50 -0.20  0.40
 
% zone 5 (2nd row passenger side) cuboids
 
cuboidDef 5 1  -1.00 -0.30  1.00  2.50  0.80  1.20
cuboidDef 5 2  -1.00 -0.30  1.00  2.50  0.40  0.80
cuboidDef 5 3  -1.00 -0.30  1.00  2.50 -0.20  0.40
 
% zoneType and zone neighbor definition, 
% zoneNeighDef #zoneID, #zoneType, #number of Neighbor needs to consider, #the list of neighbors, 
% zoneType=0: normal seat, zoneType=1: middle seat; users can add other zoneType for footwell door and etc
% when adding new zoneType, you will need to add a new line of occStateMach 
zoneNeighDef 1  0 0        
zoneNeighDef 2  0 0        
zoneNeighDef 3  0 1  4     
zoneNeighDef 4  1 2  3 5   
zoneNeighDef 5  0 1  4     
 
sensorStart

Additionally, I would like to ask about the idleTime parameter in the profileCfg section of the configuration file. Why is one set to 2789 while the other is set to 20?

Best regards
Hsiu-Che Chang

  • 0
    TI__Genius 13046 points

    Hello,

    Thanks for reaching out regarding configuring the CPD demo. One of our experts on CPD will get back to you within one to two days, but for now, I would recommend looking into the advFrameCfg and subFrameCfg found in the MMWAVE SDK User Guide (<MMWAVE_SDK_INSTALL_DIR>/docs/) and the profile_advanced_subframe.cfg (<MMWAVE_SDK_INSTALL_DIR>/packages/ti/demo/xwr68xx/mmw/profiles) for the 6843 as an example of their usage.

    Regards,

    Kristien

  • 0 in reply to Kristien Everett
    Prodigy 200 points

    Dear Kristien,

    I am the RD partner of Mr. Chang.

    Let me describe this issue more detailed.

    (1). We think the chirp_config in CPD example(below) is to submit antenna signal one by one: TX1 -> TX2 -> TX3.

    However, for beamforming purpose, we think it’s necessary to submit all antenna(TX1 + TX2 + TX3) signal simultaneously.

    -------------------------------------------------------------------------------------------------------------

    dfeDataOutputMode 1 => frameCfg

    profileCfg 0 60.00 2789 11 41 0 1871872 97.0 1 64 2200 0 0 36

    profileCfg 1 60.00 20 11 41 0 1871872 97.0 1 64 2200 0 0 36

    chirpCfg 0 0 0 0 0 0 0 1 => Submit TX1 signal

    chirpCfg 1 1 1 0 0 0 0 2 => Submit TX2 signal

    chirpCfg 2 2 1 0 0 0 0 4 => Submit TX3 signal

    frameCfg 0 2 54 0 200 1 0

    -------------------------------------------------------------------------------------------------------------

     

    Therefore, we change the parameter of “chripcfg” to submit(TX1+TX2+ X3) signal simultaneously(blow), but it can’t work. (No signal received)

    -------------------------------------------------------------------------------------------------------------

    dfeDataOutputMode 1 => frameCfg

    profileCfg 0 60.00 2789 11 41 0 1871872 97.0 1 64 2200 0 0 36

    profileCfg 1 60.00 20 11 41 0 1871872 97.0 1 64 2200 0 0 36

    chirpCfg 0 0 0 0 0 0 0 7 => Submit (TX1 + TX2 + TX3) signal simultaneously

    chirpCfg 1 1 1 0 0 0 0 7 => Submit (TX1 + TX2 + TX3) signal simultaneously

    chirpCfg 2 2 1 0 0 0 0 7 => Submit (TX1 + TX2 + TX3) signal simultaneously

    frameCfg 0 2 54 0 200 1 0

    -------------------------------------------------------------------------------------------------------------

     

    (2). Then, we try another way to follow “Long Range Detection” example to use (dfeDataOutputMode=3, advFrameCfg) in CPD Example below.

    However, it still not work. (No signal received)

    -------------------------------------------------------------------------------------------------------------

    dfeDataOutputMode 3 => advFrameCfg

    profileCfg 0 61.0 10 6 135 0 14970880 1.8 1 256 2000 0 0 48

    profileCfg 1 61.0 10 6 135 0 10276864 1.8 1 256 2000 0 0 48

    profileCfg 2 61.0 10 6 135 0 6565888 1.8 1 256 2000 0 0 48

    profileCfg 3 61.0 10 6 135 0 1871872 1.8 1 256 2000 0 0 48

    chirpCfg 0 0 0 0 0 0 0 7 => Submit (TX1 + TX2 + TX3) signal simultaneously

    chirpCfg 1 1 1 0 0 0 0 7 => Submit (TX1 + TX2 + TX3) signal simultaneously

    chirpCfg 2 2 2 0 0 0 0 7 => Submit (TX1 + TX2 + TX3) signal simultaneously

    chirpCfg 3 3 3 0 0 0 0 7 => Submit (TX1 + TX2 + TX3) signal simultaneously

    advFrameCfg 4 0 0 1 0

    subFrameCfg 0 0 0 1 128 80 0 1 1 80

    subFrameCfg 1 0 1 1 128 80 0 1 1 80

    subFrameCfg 2 0 2 1 128 80 0 1 1 80

    subFrameCfg 3 0 3 1 128 160 0 1 1 160

    -------------------------------------------------------------------------------------------------------------

    For this issue, could you share your suggestion with us ? If we want to submit(TX1+TX2+ X3) signal simultaneously in CPD example,

    except for chrip_config, which code(mss_code or dss_code) are needed to be modified ? If yes, how to modify it ?

    Many thanks again for your great assistance.

    Sincerely,

    TC.Chou

  • 0 in reply to TC Chou
    TI__Genius 13235 points

    Hi,

    Thanks for providing the additional details. Have you put your cfg file into the sensing estimator and confirmed it's valid? Could you also provide more information on what's happening with the device when you configure and start it? Do you know it's chirping? If it's erroring out somewhere, could you provide any CLI messages or where it's failing in the code?

    https://dev.ti.com/gallery/view/mmwave/mmWaveSensingEstimator/ver/2.4.0/ 

    Thanks,

    Clinton

  • 0 in reply to Clinton Rodgers
    Prodigy 30 points

    Dear Clinton,

    So far, as mentioned earlier, after changing the chirpCfg parameters in the cfg file, the GUI cannot open properly, but it also does not show any errors. As shown in the figure below:



    Best regards,

    Hsiu-Che Chang

  • 0 in reply to Hsiu Che Chang
    TI__Genius 13235 points

    Hi,

    Thanks for the screenshot. Could you open a command prompt in the folder where the visualizer is located and run it this way? That way the print output from the visualizer will remain even after the GUI window is closed. Could you post back what information is there?

    For the sensing estimator check I mentioned above, please go to the site and load in your config as shown below.

    Thanks,

    Clinton

  • 0 in reply to Clinton Rodgers
    Prodigy 200 points

    Hi Clinton,

    Thanks for your help.  Let's describe our question more detailed.

    We want to implement beamforming/beansteering feature(using 3Tx to focus on some direction) in the example of AWR6843 CPD With Classification [https://dev.ti.com/tirex/explore/node?node=A__AFyu5Yo-D70r9.H36JskpA__radar_toolbox__1AslXXD__LATEST&placeholder=true]

    Currently, we can change TxPhaseShifter to focus on some direction.

    However, in CPD example, we find that each chirp is triggered by only one TX. In fact, we want to transmits a chirp with all 3 TX.

    Therefore, we change the parameter of "tx antenna enable mask" in chirpCfg command below:

    chirpCfg 0 0 0 0 0 0 0 1 => chirpCfg 0 0 0 0 0 0 0 7
    chirpCfg 1 1 1 0 0 0 0 2 => chirpCfg 1 1 1 0 0 0 0 7
    chirpCfg 2 2 1 0 0 0 0 4 => chirpCfg 2 2 1 0 0 0 0 7

    After this modification and run this configuration, CLI console is hung and doesn't show any error message. Please see the following picture.

    By following your suggestion, we also put this configuration in mmWaveSEnsingEstimator:

    In [Advanced Chrip Design and Tuing], no error message is showed.

    In [Power Estimator], it only supports xWRL6432 and xWRL1432.

    Do you have any suggestion if we want to transmits a chirp with all 3 TX in the example of AWR6843 CPD With Classification. How to implement this feature ? 

    Many thanks again for your great help.

    Sincerely,

    TC.Chou

  • 0 in reply to TC Chou
    TI__Genius 13235 points

    Hi,

    Thanks for the additional details. Please allow a day or so for follow up.

    Thanks again,

    Clinton

  • 0 in reply to Clinton Rodgers
    Prodigy 200 points

    Hi Clinton,

    May I check with you whether any updated information on this issue ? 

    Many thanks again.

    Sincerely,

    TC.Choy

  • 0 in reply to TC Chou
    Prodigy 200 points

    Dear Clinton,

    Do you have any updated information on this issue ? Many thanks again.

    Sincerely,

    TC.Choy

  • 0 in reply to TC Chou
    TI__Mastermind 40025 points

    HI, Chou:

    First, in order to use three TX at the same time, enough power will be needed.   (https://dev.ti.com/tirex/explore/node?node=A__AGy9KKoTXLUQGK6tKHm8oQ__com.ti.mmwave_devices__coGQ502__LATEST, section 9.3.1).  Customer can connect the EVM with the mmwave IC booster to get enough power for three TX beamforming. 

    Second, each demo has its limitation, so you will need to dig into the code to see whether more than one subframes are supported; can it support TX beamforming and etc.  Maybe it is always assuming 12 virtual antennas.

    For research purpose, I would suggest the customer to do raw data capture through mmwave studio through DCA1000 + IC booster + EVM, and then do all the signal processing off-line (for example in the MATLAB) to validate the concept and performance impact.  Please do not jump into CPD demo and assuming it will work with TX beamforming. 

    Best,

    Zigang