• State TI Thinks Resolved
  • Locked Locked
  • Replies 12 replies
  • Answers 3 answers
  • Subscribers 30 subscribers
  • Views 508 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.

AWR6843AOP EVM

Sarah A
Prodigy 80 points
Other Parts Discussed in Thread: IWR1443, AWR6843AOP

Question 1: How can I get a complex range profile by using mmwave demo visulizer GUI, which can be saved and processed for vital signs evaluation.?

As I know, the data I got just the Magnitude of the range profile not the phase information in order to resolve distances as small as breathing/heartbeats.

Question 2: I select the Range Azimuth Heat Map in Visualizer I presumed it Has the data in pairs as Real: Imaginary after extracting but How can I get it and parse it?

Question 3: What is the possible way to increase capturing the sample rate?

 

I hope to hear from you with as details as possible that could help my project progress. Thank you

Regards,

Sarah

  • 0
    TI__Genius 14415 points

    Hello Sarah,

    Please see the following information on vital signs processing, it will have more info on the data. This document is for the IWR1443 device, but the principles are the same.

    https://dev.ti.com/tirex/explore/node?a=VLyFKFf__4.10.1&node=AC.hKZgzwSto75.dHoe8fg__VLyFKFf__4.10.1&r=VLyFKFf__4.1.0 
    https://dev.ti.com/tirex/explore/node?a=VLyFKFf__4.10.1&node=AMQsAyKeqwmAPb8jes1nWw__VLyFKFf__4.10.1&r=VLyFKFf__4.1.0 

    In addition, it seems you are looking for the complex ADC data from the radar front end to do your own processing of the data? Please see the DCA1000 user guide for info on collecting raw data. https://www.ti.com/lit/pdf/spruij4 

    It also sounds like you are using the mmWave Demo Visualizer, which runs the out of box demo. For info on the data format of the OOB demo, please see the following document. The range azimuth heatmap should give you the information you are looking for. 
    https://dev.ti.com/tirex/explore/node?a=VLyFKFf__4.10.1&node=AH-2SVYArR7wfP9cuNOm0w__VLyFKFf__4.10.1&r=VLyFKFf__4.1.0 

    To increase the sample rate, you will need to adjust the ADC sample frequency in the CFG file. Please see the profileCfg command in the SDK User's Guide located at the following location
    C:\ti\mmwave_sdk_[VER]\docs

    Regards,

    Jackson

  • 0
    Prodigy 80 points

    Hi Jackson,

    For Question 2: I select the Range Azimuth Heat Map in mmwave Visualizer I presumed it Has the data in pairs as Real: Imaginary after extracting but How can I get it and parse it?

    I open The mmwave Visualizer software> I Select range profile, scatter plot and Range Azimuth Heat Map > then I start recording the data. I am interested in the processed data from the software. Then I use the Python code provided by TI to read the processed file. In the python code, I only can get number of frames, number of detected objects, xyz coordinates, velocity, noise and SNR. the processed .dat file gives the amplitude of range profile not complex number? 

    What shall I do to get the Range Azimuth Heat Map? or should I modify the Python code to do so? what information do I need to get and steps to follow?

    I hope to hear from you soon. Thank you

    Regards,

    Sarah

  • 0 in reply to Sarah A
    TI__Genius 14415 points

    Hi Sarah,

    Yes, to use the python parser you will need to add to the code yourself. The TLV parsing functionality is only included for the pointcloud data. You will need to add a function for parsing TLV8, the heatmap data, based on the format in the OOB data format document linked above.

    Regards,

    Jackson

  • 0 in reply to Jackson Thomas
    Prodigy 80 points

    Hi Jason,

    I will do so. Thank you very much for your advice.

  • 0 in reply to Sarah A
    Prodigy 80 points

    Hi Jason,

    I have a question: in regards to the excel sheet I got after parsing the data. There are two columns with SNR and noise. What the importance of them and what indication it can lead me to? the noise column including what types of noise in the system? what is the reference point to know I got good SNR or no? Thank you

  • 0 in reply to Sarah A
    TI__Genius 14415 points

    Hi Sarah,

    The three signals are related, SNR, noise floor, and point strength. The SNR tells you generally how strong the point is and you can set a threshold for what SNR designates a detected point. The noise is the measured noise floor of the radar signal near the detected point. 

    What SNR is good enough depends on your design. Again this is configurable in the CFAR cfg command. Typically at long distances an SNR of 10-20 can be observed, while at shorter distances an SNR of >100 can be observed.

    Regards,

    Jackson

  • 0 in reply to Jackson Thomas
    Prodigy 80 points

    Hi, Thank you.

    The output of range azimuth heatmap is going to be as real numbers? or real numbers plus complex number?

    frame DetObj# x y z v snr noise azimuth heat
    0 0 0.027254 0.391166 0.190777 0 166 714 3.985545
    0 1 1.373593 0.721681 0.972961 0 136 607 62.28271
    0 2 2.031773 2.079585 1.064262 0 126 700 44.33371
    0 3 -5.35946 4.921086 1.631141 0 156 580 -47.4417

    How do I make sure if I get the range azimuth heatmap values right or wrong? I s there a way to confirm it?

    Just want to make sure if I understand this right: there are two ways to find range azimuth and range-doppler heatmaps either by to look at mmWave visualizer GUI or write a function in python to convert the value in the processed file to excel sheet is that correct? both way will lead to the same result?

  • 0 in reply to Sarah A
    TI__Genius 14415 points

    Hi Sarah,

    Yes either using the demo visualizer or writing a script to parse the output will give the same result, as the visualizer is just doing this function as well. The output for the heatmaps is complex data, as detailed in the data format document linked above. Although it will be a large list of numbers making up the heatmap, not a single number as indicated in your table directly above.

    Regards,

    Jackson

  • 0 in reply to Jackson Thomas
    Prodigy 80 points

    Hi Jackson, 

    Thank you so much for your help.

    I was reading about the calibration process: Range Bias and RX Channel Gain/Phase Measurement and Compensation and I am not sure I got the instruction right. I open the profile_calibration.cfg and I change measureRangeBiasAndRxChanPhase 1 1.0 0.2 TO measureRangeBiasAndRxChanPhase 1 X D and I save it. When I open mmWave Demo Visualizer and LOAD CONFIG FROM PC AND SEND, the sensor does not work.

    Can you please provide the steps that I have to follow. I would be thankful

    Thanks again

    Regards,

    Sarah

  • 0 in reply to Sarah A
    TI__Genius 14415 points

    Hello Sarah,

    It seems that you have the steps. I would make sure of a few things.

    1)You have the OOB demo binary flashed. The compensation parameters can be used in any of the demos, but only the OOB demo supports measuring them. The values will be the same across demos.
    2)You have the corner reflector at the right location
    3)The rest of the settings in the CFG are correct for your device. You may want to try that same upload process without the measureRangeBiasAndRxChanPhase command included to make sure the sensor will also start.
    4)When you use the load from PC button, you should see the CFG commands being sent in the console on the configure tab. DO you see this and do you see any errors? This is also where the calibration values will be output.

    The best instructions are below under prerequisite 3:
    https://dev.ti.com/tirex/explore/node?a=VLyFKFf__4.1.0&a=VLyFKFf__4.10.1&node=ABFqvXkIw19j7aQ2mxIQQA__VLyFKFf__4.10.1

    Regards,

    Jackson

  • 0 in reply to Jackson Thomas
    Prodigy 80 points

    Hi Jackson, 

    Thank you for your great help. I will try that and will see how is it going.

    Question: in OOB demo with mmwave industrial tool box 4_10_1 for AWR6843AOP. Is this Demo, is it using 3 transmitting and 4 receiving antenna in total 12 virtual antenna ? or 2 transmitting and 4 receiving antenna which are 8 virtual antenna ? where can I found this information.

    Thanks again

    Regards,

    Sarah

  • 0 in reply to Sarah A
    TI__Genius 14415 points

    This is configurable, but most demos will use 3 by 4 with 12 virtual antennas. You can see this in the CFG file. More info is available in the SDK user's guide.

    There are 3 chirpCfg commands, each corresponding to a different Tx antenna. All 4 Rx antennas are always used in the OOB demos.

    Regards,

    Jackson