• State TI Thinks Resolved
  • Locked Locked
  • Replies 6 replies
  • Answers 3 answers
  • Subscribers 31 subscribers
  • Views 339 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

IWR1642BOOST: Driver's Vital Signs Lab Application Questions

Celine Ertin
Prodigy 90 points
Part Number: IWR1642BOOST

Hi,

I am working on getting the driver's vital signs lab working on my iwr1642boost when connected to an Nvidia Jetson Nano, and I had a few questions:

1. I want the sensor to start collecting data upon startup. Do I have to edit the pre-built binary finals to do that, if so what application do I use to edit those?

2. I was informed that I can find an example of the parser from the GUI source code. When I look in the gui_source folder under the driver's vital sign lab, I see multiple different files. Which one do I use to implement/copy the parser onto the Jetson?

3. When looking at the UART output packet structure, I see that it contains a vital signs output stats. When streaming the data to my nano, do I just need to save this part of the packet in order to get the desired breathing and heart rate values, or do I need other parts of the UART packet as well?

Any help is appreciated. Thanks!

  • 0
    TI__Genius 17265 points

    Hi,

    1. If you want the device to start collecting data without requiring you to send a config over UART, you will want to add a Hard Coded Config. You may want to reference the "68xx_mmwave_sdk_hcc" version of the out-of-box-demo in the Industrial Toolbox, as this version has Hard Coded Config already implemented. 

    2. I believe for this demo, you will want to reference the function "processData" that is contained within "driver_vital_signs\vitalSigns_host\gui\gui_source\mainWindow.cpp"

    3. I believe this demo just outputs a single type of UART packet, so you would just have to parse the header and related information away. Again, looking at the GUI's parser would probably be the best resource in this regard.

    Let me know if you have any further questions.

    Best Regards,
    Alec

  • 0 in reply to Alec May
    Prodigy 90 points

    Hi,

    Thank you that is very helpful. I have a few follow up questions.

    1. So would I just look at the mss and dss files of the 68xx hard coded config out of box demo and implement the Hard Coded Config into the mss and dss files of my demo in CCS? Then after I edit these mss and dss files how do I get them into the pre-built binary format to flash onto the sensor?

    2. When looking at the UART packet, it says that the packet size depends on the number of processed range bins. What is this number? The calculations for finding this number look very complex, so I would rather hard-code the number for now.

    Thanks

  • 0 in reply to Celine Ertin
    TI__Genius 17265 points

    Hi,

    1. The hard coded config will require only modifications to the MSS, as that is where the config is typically loaded via CLI. If you import the hard coded config project to Code Composer Studio, you can then build the project there.
    2. I believe it depends on the chirp/frame parameters in your config, but I will double check which ones

  • 0 in reply to Alec May
    TI__Genius 17265 points

    Hi,

    The number of range bins = number of ADC sample, if it is power of 2. If you do not want to do the calculations to find this, you could also find it through experimentation by doing the following:

    1. Hardcode the config file with the configuration that you want to use.
    2. Add a line that prints out the number of range bins to UART
    3. Run the demo once and write down how many range bins are being used for your configuration
    4. Remove the print line from step 2

    Best Regards,
    Alec

  • 0 in reply to Alec May
    Prodigy 90 points

    Hi,

    Thank you that was my initial thought, but I thought maybe you had the number already, but I will do it through experimentation. In terms of the hardcode config, can you point me to a specific part of the mss_main of the 68xx hcc? The code is over 4000 lines long and I'm having trouble finding which parts I need to copy to my demo. Thanks

  • 0 in reply to Celine Ertin
    TI__Genius 17265 points

    Hi,

    I just went back and looked, and actually the changes are all in mmw_cli.c. If you go to <mmwave_industrial_toolbox>\labs\out_of_box_demo\68xx_mmwave_sdk_hcc\src\mss you can see the files that are added specifically for hard coded config.

    Best Regards,
    Alec