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.

AWR1443BOOST: vital signs lab frame data loss

Part Number: AWR1443BOOST

Hi,

For the vital signs lab from mmwave_industrial_toolbox_4_1_0, I used the matlab file 'main_readGUISavedBinary.m' from mmwave_automotive_toolbox_2_7_1. Then, I had the same issue that from the other users posted in here: https://e2e.ti.com/support/sensors/f/1023/t/739935?tisearch=e2e-sitesearch&keymatch=%25252525252520user%2525252525253A352628

https://e2e.ti.com/support/sensors/f/1023/t/748737?tisearch=e2e-sitesearch&keymatch=vital%25252525252525252520sign%252525252525252525201443%25252525252525252520gui 

I tried to print out variable 'framecountDummy' from the GUI source file, it turns out that the value is not the same as 'outGlobalCount' from UART. It is also not the same as number of columns of 'dataAll' in 'main_readGUISavedBinary.m' file.

I don't know why this situation happens. Could you please help me?

Thank you.

Hongqiang

  • Hi,

    We will be able to get back to you by end of the week

    thank you
    Cesar

  • Cheers, I'm looking forward to your reply

  • Hi,

    The data formats for the two demos are not the same.

    The matlab file 'main_readGUISavedBinary.m' must be updated to support vital signs lab from mmwave_industrial_toolbox_4_1_0.

    This can be done by checking the output data format for the demo included in the mmwave_industrial_toolbox_4_1_0.

    You would need to compare the file 'main_readGUISavedBinary.m'  with "mmwave_industrial_toolbox_3_6_1\labs\lab0002-vital-signs\lab0002_vital_signs_gui\vitalSigns_demo_gui.m" and update accordingly

    thank you

    Cesar

  • Hi,

    I modified the GUI source code 'vitalSigns_demo_gui.m' and don't have zero columns of between each frame anymore.

    However, I still have packet loss issue. I found that when I enable plot function of GUI, there will be packet loss.

    If I disable the plotting function, there's only packet loss when initializing. So the number of packet loss remains '13' for whole process.

       

    I think the plot function slowdown the CPU to get the new data packet from UART. Do you have any suggestions to solve this issue? Like setting priority of serial port or interrupt.

    Thank you.

    Hongqiang