• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Answers 1 answer
  • Subscribers 29 subscribers
  • Views 808 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.

AWR1642: Find the best profile settings for AWR1642 VitalSigns application

Jonathan Ibera
Prodigy 200 points
Part Number: AWR1642
Other Parts Discussed in Thread: IWR6843, IWR6843ISK, AWR1443

1) Are there better profile settings for the VitalSigns program that are tested?  Please share your the values used for let's say vitalSignsCfg and motionDetection parameters.

2) Are there tweaks done on settings to make it good for VitalSigns detection? Here is the included profile in the VitalSigns demo, Let me know your thoughts on the choice for chirps and frame design that you found to be good.    For VitalSigns demos, the test subject is within 0.3 to 1m away from sensor (very close) and is not moving as much with a chair on his back, and we are measuring the small vibrations on the chest displacement. 

sensorStop
flushCfg
dfeDataOutputMode 1
channelCfg 15 3 0
adcCfg 2 1
adcbufCfg -1 0 0 1 0
profileCfg 0 60.25 7 6 57 0 0 65 1 200 4000 0 0 40
chirpCfg 0 0 0 0 0 0 0 1
frameCfg 0 0 2 0 50 1 0
lowPower 0 1
guiMonitor 0 0 0 0 1
calibDcRangeSig -1 0 0 0 0
vitalSignsCfg 0.3 0.9 256 512 4 0.1 0.05 100000 300000
motionDetection 1 20 2.0 0
sensorStart

Thanks.

  • 0
    TI__Guru*** 147964 points

    Hi

    The best settings are provided with the demo.

    The demo is provided as a starter point to be further improved by users.

    Thank you

    Cesar

  • 0 in reply to Cesar
    Prodigy 200 points

    Cesar,

    Thanks for reply. Here are some followup questions for this Vital Signs project,

    1) What changes in algorithm happened across the various SDK versions? I started on AWR1642 ES1, then ES2, then move on to IWR6843 ES1, and then ES2 and their respective SDK thru those times. Was there a change notice on Vital Signs specifically (or there was no change in algo)?   

    2) Next, for the AWR/IWR SOC versions, where there specific features in the hardware IC that improve or changes VitalSign project performance? 

    3) Next, for the antenna system of  IWR6843 that has 3TX/4RX anatennas, were these being exercised in VitalSigns project code in general? Or it is always using 1TX/1RX?    I understand to increase phase precision, we can increase antenna we use (more is better), please comment.

    4) What power levels is the IWR6843ISK + carrier board using when used at around 50% and 100% DC?  What surge current/power has to be alloted especially at startup?  I am thinking which power supply is sufficient for testing this board for like 24hrs study let's say.  I think this question 4 might be another thread topic. 

    Thanks,

    Jonathan

  • 0 in reply to Jonathan Ibera
    TI__Guru*** 147964 points

    Answer #1

    There are two vital signs code bases. One that uses the HWA for example on AWR1443) and a second one that uses the DSP (for example on xWR1642). The performance is the same for both code bases

    The same code bases are ported to different platforms. There are no differences in the target code

    Answer #2

    No, performance is the same for both HWA and DSP implementations

    Answer #3

    No the IWR6843 implementation uses only 1Tx/1Rx

    Answer #4

    We recommend for all our EVMs to use a 5V/3A power supply.

    I will close this thread now, for all new questions please start a new thread

    thank you

    Cesar

  • 0 in reply to Cesar
    Prodigy 200 points

    Hi Cesar,

    Thanks for the reply. It cleared up some of my questions. Here are some followup questions: 

    1) How about the the Vital sign base for IWR6843ISK? How different is it from AWR1642?  We might have to move to IWR6843 to use the 60GHz as per a FCC compliance reason. 

    2) We customized the UART data being as output of the MSS unit and it worked well in AWR1642. Then, we ported to the IWR6843, we notice that their a hiccup (glitch) that throws it off at random times typically after 120sec run time. Prior, we can reach a long test time of 900s on this UART with AWR1642 with no issue.    What do you think might had caused this one? 

    When I did the porting, I started with the base IWR6843 Vitalsigns code and then added all the changes we did from AWR1642 (pretty much in the algorithm code sections that we added). 

    Thanks,

    Jonathan

  • 0 in reply to Jonathan Ibera
    TI__Guru*** 147964 points

    Hi,

    Sorry for late reply

    Can you please create a new thread for IWR6843 related questions? A different team will be able to help you

    thank you

    Cesar