The TI E2E™ design support forums will undergo maintenance from Sept. 28 to Oct. 2. If you need design support during this time, contact your TI representative or open a new support request with our customer support center.

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: The image built by CCS with the vital_signs_68xx source provided by TI does not work in the GUI.

Part Number: AWR6843AOPEVM

Hi. Everyone.

I confirmed that if I flash the image (vital_signs_demo_68xx.bin) of the prebuilt_binaries folder of 68xx_vital_signs provided by mmwave_industrial_toolbox_4_11_0 to AWR6843AOPEVM,
it works normally on the GUI.

However, if I tried to the build the src (vital_signs_68xx_dss.projectspec, vital_signs_68xx_mss.projectspec) in the 68xx_vital_signs folder with CCS 11.2.0.00007 and
the built image is flashed to the AWR6843AOPEVM, it does not work on the GUI.

I don't know the difference between the provided image and the built image and why the built image with the source provided by TI does not work on the GUI.

Any help about this problem would be appreciated.

Thank you in advance.

  • Hi,

    I was able to replicate this issue on my end and we will be looking into this.

    For now, I would recommend looking at our vitals signs with people tracking binary in the industrial toolbox. This is our latest algorithm developed for vital signs. Please reach out to your sales representative at TI to access the source code for this lab.

    Thank you,

    Angie

  • Hi, Angie.

    First of all, thank you for quick reply.

    I applied the image in the folder you recommended to AWR6843AOPEVM and

    confirmed that it works normally in Vital_Signs_GUI.exe and requested the source code.

    Additionally, it was confirmed that the above image, which reflects the latest TI algorithm, does not operate normally in VitalSignsRadar_Demo.exe.

    In the case of several vital sign GUIs provided by TI, it is understood that each operating image exists separately.

    However, we want to use VitalSignRadar_Demo.exe with the GUI source (QT-based) open as an image with the latest TI algorithm applied.

    Maybe there is no way?

    Thank you in advance.

    Regards.

  • Hi Hyung,

    Thank you for requesting our new source code.

    LG would have to modify the source code for the VitalSignRadar_Demo.exe to correspond with the latest output format of our latest vital signs algorithm. What specific features of the VitalSignRadar_Demo.exe is LG needing?

    Thank you,

    Angie

  • Hi, Angie.

    Thank you very much for your sincerely and quick reply.

    We currently have used the TI AWR6843AOPEVM to measure the vital signs(HR, BR) of drivers and passengers in the vehicle, and based on the obtained data, we would like to promote the proposed mobility service based on various in-vehicle experiences to automotive OEMs.

    And I have one question regarding the vital signs with people tracking that TI provides. Currently, the HR and BR values measured using the prebuilt image are displayed on the GUI(Vital_Signs_GUI.exe).

    Is it correct to understand that the values are updated every 300ms?

    In case of the default values related to the vital sign in vital_signs_AOP_6m.cfg in the chirp_configs folder, there are 15 and 300 values. I have understood that 300 is understood as the window size and the HR and BR value is updated according to the value(300).

    Thank you in advance.

  • Hi Hyung,

    The 15 and 300 values are related to the number of frame. 15 is the refresh frame rate, meaning every 15 frames the vital signs processing is calculated. 300 is the window size, meaning when vital signs processing is done, it uses the last 300 frames of information to make a vital signs decision.

    Thanks,

    Angie

  • Hi, Angie

    First of all, thank you very much for your sincerely support and quick reply.

    I don't understand, but I have solved this problem. I think this problem is caused by company security tools.

    I have confirmed that this problem does not occur on other PCs that don't have installed company security tools.

    I am very sorry for asking unintentionally questions during this time.

    In addition, thank you for promptly answering questions about parameter values and requests for source code.

    In the case of the latest source code you provided, I have built the source code and then I have checked the board applied

    the built image is operated normally.

    Thank you.