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.

IWR1443: Can VitalSignsRadar_Demo.exe support IWR1443?

Part Number: IWR1443

Hello Champs,

The C:\ti\mmwave_industrial_toolbox_4_1_0\labs\vital_signs\14xx_vital_signs\gui\vitalSignsDemo_GUI.exe can't reach 20Hz.

It seems that the 68xx GUI resolved this issue. 

Can the mmwave_industrial_toolbox_4_1_0\labs\vital_signs\68xx_vital_signs\gui\gui_exe\VitalSignsRadar_Demo.exe support IWR1443?

If yes, does it need to do some special configuration?

Thanks.
Rgds
Shine

  • Hi Shine

    The two labs use different visualizers. They are not cross-compatible.

    Please see the Support Guide for further queries.

    Regards,

    AG

  • Hi AG,

    Thanks for you help.

    The 14xx_vital_signs\gui\vitalSignsDemo_GUI.exe can't reach 20Hz, is there any methods to speed up the sample rate?

    Where to get the framePeriodicity value in vital_signs?

    rl_sensor.h

    rlUInt16_t numAdcSamples;
    /**
    * @brief Frame repitition period \n
    1 LSB = 5 ns\n
    Typical range 1 ms to 1000 ms \n
    */
    rlUInt32_t framePeriodicity;
    /**
    * @brief Selects the mode for triggering start of transmission of frame \n
    0x0001 SWTRIGGER (Software API based triggering): \n
    Frame is triggered upon receiving rlSensorStart\n
    There could be several tens of micro seconds uncertainty in triggering. \n
    Note: This mode is not applicable if this mmwave device is configured as \n
    MULTICHIP_SLAVE in rlChanCfg_t \n
    0x0002 HWTRIGGER (Hardware SYNC_IN based triggering): \n


    Thanks.
    Rgds
    Shine

  • Hello Shine

    This is set in the chirp configuration parameter set as part of Frame Cfg.

    Regards,

    AG