• State
  • Locked Locked
  • Replies 5 replies
  • Subscribers 31 subscribers
  • Views 246 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: About BPM in vital_signs_tracking demo​

Jerry Chuang
Prodigy 160 points
Part Number: AWR6843AOPEVM

Tool/software:

Hi TI Experts:

Good day~ As we see the default pofile.cfg of  "vital_signs_tracking demo​" , BPM enabled for TX1 and TX3  as below: 

However , if we enable TX1,TX2 and TX3 on chirp 0 and chirp 2  (set to 7 ) and disable BPM in the profile.cfg ,  

neither object nor vital sign were detected.

Is it necessary to enable BPM for object and vital sign detection in this demo ? Is that possible that we could use

3TX beamforming along with phase  shifter to replace BPM function by modifying the corresponding source codes

or the content of profile.cfg?  

6574.vital_signs_AOP_6m.cfg

  • 0
    TI__Genius 13126 points

    Hey Jerry,

    Good to hear from you! I have asked our vital signs expert to take a look into this. Please them a day or two to respond.

    Regards,

    Kristien

  • 0 in reply to Kristien Everett
    Prodigy 160 points

    Hi Kristien : 

    For the project assessment reason , could you help on this case as the first priority ?

    We have to know if BPM is necessary or not for vital sign detection recently.

  • 0 in reply to Jerry Chuang
    TI__Genius 11750 points

    Hi Jerry Chuang,

    BPM is not necessary for Vital signs or tracking. You can do it with TDM only. Using BPM provides better SNR. 

    Do note that in the current demo, the configuration is closely coupled with the vitals chain and hence any changes to the config might break the operation

    Regards

  • 0 in reply to Abhishek Karkisaval
    Prodigy 160 points

    Hi  TI Experts : 

    Thanks for quickly reply~~ Another question , could we use 3TX beamforming on this demo ?  As I modified the profile.cfg as the pics below : 

    There exists  an error  when running "Pcount3DDemo_DPM_ioctl_blocking (gMmwMssMCB.objDetDpmHandle,DPC_OBJDET_IOCTL__STATIC_PRE_START_CFG,&objDetPreStartDspCfg,sizeof (DPC_ObjectDetection_PreStartCfg));" 

    and there is no use to decrease the "number of loops" on framCfg ( the result is the same for 48 ,36 , 24) 

    Is there any way to properly do the DPC setting (DPC_OBJDET_IOCTL__STATIC_PRE_START_CFG) when using 3TX beamforming ?

      

    char *hardCodedConfigCommands[] = {
    "sensorStop",
    "flushCfg",
    "pmicCfg 1 1",
    "dfeDataOutputMode 1",
    "channelCfg 15 7 0",
    "adcCfg 2 1",
    "adcbufCfg -1 0 1 1 1",
    "lowPower 0 0",

    //NTU
    
    "profileCfg 0 60.75 30.00 1.00 10.00 0 0 200.0 1 96 10785.00 2 1 36",
    
    //3D people track only
    //"profileCfg 0 60.75 30 25 59.1 0 0 54.71 1 96 2950 2 1 36", 

    "chirpCfg 0 0 0 0 0 0 0 7",
    "chirpCfg 1 1 0 0 0 0 0 7",
    "chirpCfg 2 2 0 0 0 0 0 7",
    "frameCfg 0 2  48  0 70.00 1 0",
    
    "dynamicRACfarCfg -1 4 4 2 2 8 12 4 12 5.00 8.00 0.40 1 1",
    "staticRACfarCfg -1 6 2 2 2 8 8 6 4 8.00 15.00 0.30 0 0",
    "dynamicRangeAngleCfg -1 0.75 0.0010 1 0",
    "dynamic2DAngleCfg -1 1.5 0.0300 1 0 1 0.30 0.85 8.00",
    "staticRangeAngleCfg -1 0 8 8",
    "fineMotionCfg -1 1",
    "bpmCfg -1 0 0 2",
    
    "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",
    "fovCfg -1 70.0 20.0",

    "compRangeBiasAndRxChanPhase 0.0392068 0.85352 -0.42142 -0.85583 0.31876 0.83612 -0.23291 -0.89639 0.44327 0.40002 -0.59879 -0.44089 0.54626 0.45618 -0.49176 -0.39868 0.62875 0.27008 -0.71771 -0.33118 0.65073 0.36008 -0.58435 -0.28723 0.71649",
    "measureRangeBiasAndRxChanPhase 0 1. 0.2",

    "staticBoundaryBox -1.5 1.5 0.3 1.75 0 3",
    "boundaryBox -1.5 1.5 0.5 2 0 3",
    "sensorPosition 2 0 15",
    "gatingParam 3 2 2 2 4",
    "stateParam 3 3 12 215 50 6000",
    "allocationParam 20 100 0.1 20 0.5 20",
    "trackingCfg 1 2 800 1 46 96 70",
    "presenceBoundaryBox -1.5 1.5 0.3 1.75 0 3",
    "maxAcceleration 0.1 0.1 0.1",

    "vitalsign 15 300",
    "VSRangeIdxCfg 1 6",

    "sensorStart",

    "!!!END_OF_HARD_CODED_COMMANDS"};

#endif

  • 0 in reply to Jerry Chuang
    TI__Genius 11750 points

    Hi 

    I would not recommend changing it to 3 Tx beam forming as the demo is closely linked to the chain and changing any DPC configurations will be difficult to debug. Already the demo is working in BPM configuration with 2Tx simultaneously transmitting. You will not gain significant SNR by changing ii to 3Tx beamforming. It is possible but we have not done it at our end.

    Regards